Your message dated Sat, 23 Jun 2018 12:32:13 +0100
with message-id <[email protected]>
and subject line Closing bugs for requests included in the EoL jessie point
release
has caused the Debian Bug report #901613,
regarding jessie-pu: package slurm-llnl/14.03.9-5+deb8u2
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
901613: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901613
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: jessie
User: [email protected]
Usertags: pu
Hi,
I just recently noticed a wheezy->jessie upgrade problem in slurm due to
insufficient Breaks+Replaces. The problematic files seem to have been
moved twice during the jessie development cycle, the existing B+R
therefore do not cover direct upgrades from wheezy.
I don't know why this hasn't shown up earlier, since I intensively
search for such upgrade conflicts ... (although I didn't look at
wheezy->jessie for a long time since everything was filed+solved).
The fix is trivial and already uploaded.
Andreas
diff -Nru slurm-llnl-14.03.9/debian/changelog
slurm-llnl-14.03.9/debian/changelog
--- slurm-llnl-14.03.9/debian/changelog 2017-07-31 09:03:40.000000000 +0200
+++ slurm-llnl-14.03.9/debian/changelog 2018-06-15 15:58:33.000000000 +0200
@@ -1,3 +1,11 @@
+slurm-llnl (14.03.9-5+deb8u2) jessie; urgency=medium
+
+ * Team upload.
+ * slurm-client: Add Breaks+Replaces: slurm-llnl-slurmdbd (<< 14.03.9-5) for
+ clean upgrades from wheezy which shipped sacctmgr there. (Closes: #901513)
+
+ -- Andreas Beckmann <[email protected]> Fri, 15 Jun 2018 15:58:33 +0200
+
slurm-llnl (14.03.9-5+deb8u1) jessie; urgency=high
* Fix security issue caused by insecure file path handling triggered by
diff -Nru slurm-llnl-14.03.9/debian/control slurm-llnl-14.03.9/debian/control
--- slurm-llnl-14.03.9/debian/control 2017-07-28 09:25:13.000000000 +0200
+++ slurm-llnl-14.03.9/debian/control 2018-06-15 15:58:33.000000000 +0200
@@ -53,8 +53,8 @@
${misc:Depends},
munge,
ucf
-Replaces: slurm-llnl (<< 14.03), slurmdbd (<< 14.03.9-5)
-Breaks: slurm-llnl (<< 14.03), slurmdbd (<< 14.03.9-5)
+Replaces: slurm-llnl (<< 14.03), slurmdbd (<< 14.03.9-5), slurm-llnl-slurmdbd
(<< 14.03.9-5)
+Breaks: slurm-llnl (<< 14.03), slurmdbd (<< 14.03.9-5), slurm-llnl-slurmdbd
(<< 14.03.9-5)
Conflicts: sinfo
Description: SLURM client side commands
SLURM stands for Simple Linux Utility for Resource Management, it
diff -Nru slurm-llnl-14.03.9/debian/gbp.conf slurm-llnl-14.03.9/debian/gbp.conf
--- slurm-llnl-14.03.9/debian/gbp.conf 2017-07-28 09:24:17.000000000 +0200
+++ slurm-llnl-14.03.9/debian/gbp.conf 2018-06-15 15:58:33.000000000 +0200
@@ -1,3 +1,4 @@
[DEFAULT]
pristine-tar = True
filter-pristine-tar = True
+debian-branch = jessie
--- End Message ---
--- Begin Message ---
Version: 8.11
Hi,
The updates referenced by these bugs were included in today's EoL point
release for jessie (8.11).
Regards,
Adam
--- End Message ---
