Bug#929600: slurm-llnl: FTBFS on 32-bit architectures
Hi Andreas,
On Sun, May 26, 2019 at 10:31:14PM +0200, Andreas Beckmann wrote:
> the stretch update of slurm-llnl FTBFS on the 32-bit architectures:
thank you very much for filing this bug report.
I have prepared an updated version of the package available here:
https://people.debian.org/~oliva/slurm-llnl-16.05.9-1+deb9u4/
debdiff attached, diffstat follows:
changelog | 6 ------
patches/CVE-2019-6438 | 11 -----------
2 files changed, 17 deletions(-)
Best regards,
--
Gennaro Oliva
diff -Nru slurm-llnl-16.05.9/debian/changelog slurm-llnl-16.05.9/debian/changelog
--- slurm-llnl-16.05.9/debian/changelog 2019-05-27 09:48:30.000000000 +0200
+++ slurm-llnl-16.05.9/debian/changelog 2019-02-12 23:34:26.000000000 +0100
@@ -1,9 +1,3 @@
-slurm-llnl (16.05.9-1+deb9u4) stretch-security; urgency=medium
-
- * Fix build regression on 32-bits architecture (Closes: #92960)
-
- -- Gennaro Oliva <oliva.g@na.icar.cnr.it> Mon, 27 May 2019 09:48:30 +0200
-
slurm-llnl (16.05.9-1+deb9u3) stretch-security; urgency=high
* Fix CVE-2019-6438 by adding mitigation for a potential
diff -Nru slurm-llnl-16.05.9/debian/patches/CVE-2019-6438 slurm-llnl-16.05.9/debian/patches/CVE-2019-6438
--- slurm-llnl-16.05.9/debian/patches/CVE-2019-6438 2019-05-27 09:07:56.000000000 +0200
+++ slurm-llnl-16.05.9/debian/patches/CVE-2019-6438 2019-02-12 23:32:08.000000000 +0100
@@ -65,14 +65,3 @@
void *slurm_try_xmalloc(size_t , const char *, int , const char *);
void slurm_xfree(void **, const char *, int, const char *);
void *slurm_xrealloc(void **, size_t, bool, const char *, int, const char *);
---- slurm-llnl-16.05.9.orig/contribs/perlapi/libslurm/perl/slurm-perl.h
-+++ slurm-llnl-16.05.9/contribs/perlapi/libslurm/perl/slurm-perl.h
-@@ -17,7 +17,7 @@
- #endif
-
- extern void slurm_xfree(void **, const char *, int, const char *);
--extern void *slurm_xmalloc(size_t, bool, const char *, int, const char *);
-+extern void *slurm_xmalloc(uint64_t, bool, const char *, int, const char *);
-
- extern void slurm_api_clear_config(void);
-
Reply to: