Update changelogs, final build

CITATION.cff

@@ -5,7 +5,7 @@ authors:
     location: "Computer Sciences Department, University of Wisconsin-Madison"
     city: "Madison"
     region: "Wisconsin"
-title: HTCondor 8.8.1
+title: HTCondor 8.8.2
 references:
   - type: article
     authors:
@@ -26,8 +26,8 @@ references:
 license: Apache-2.0
 # --- Updates happen below this line. ---
 # Required.
-date-released: 2019-02-19
+date-released: 2019-04-11
 # Required.
-version: 8.8.1
+version: 8.8.2
 # Strongly recommended.  Really ought to correspond to the version above.
-doi: 10.5281/zenodo.2572014
+doi: 10.5281/zenodo.2636523

build/packaging/new-debian/changelog

@@ -1,3 +1,18 @@
+condor (8.8.2-1) stable; urgency=medium
+
+  * Fixed problems with condor_ssh_to_job and Singularity jobs
+  * Fixed a problem that could cause condor_annex to crash
+  * Fixed a problem where the job queue would very rarely be corrupted
+  * condor_userprio can report concurrency limits again
+  * Fixed the GPU discovery and monitoring code to map GPUs in the same way
+  * Made the CHIRP_DELAYED_UPDATE_PREFIX configuration knob work again
+  * Fixed restarting HTCondor from the Service Control Manager on Windows
+  * Fixed a problem where local universe jobs could not use condor_submit
+  * Restored a deprecated Python interface that is used to read the event log
+  * Fixed a problem where condor_shadow reuse could confuse DAGMan
+
+ -- Tim Theisen <tim@cs.wisc.edu>  Thu, 11 Apr 2019 07:48:19 -0500
+
 condor (8.8.1-1) stable; urgency=medium
 
   * Fixed excessive CPU consumption with GPU monitoring

build/packaging/srpm/condor.spec

@@ -1960,6 +1960,18 @@ fi
 %endif
 
 %changelog
+* Thu Apr 11 2019 Tim Theisen <tim@cs.wisc.edu> - 8.8.2-1
+- Fixed problems with condor_ssh_to_job and Singularity jobs
+- Fixed a problem that could cause condor_annex to crash
+- Fixed a problem where the job queue would very rarely be corrupted
+- condor_userprio can report concurrency limits again
+- Fixed the GPU discovery and monitoring code to map GPUs in the same way
+- Made the CHIRP_DELAYED_UPDATE_PREFIX configuration knob work again
+- Fixed restarting HTCondor from the Service Control Manager on Windows
+- Fixed a problem where local universe jobs could not use condor_submit
+- Restored a deprecated Python interface that is used to read the event log
+- Fixed a problem where condor_shadow reuse could confuse DAGMan
+
 * Tue Feb 19 2019 Tim Theisen <tim@cs.wisc.edu> - 8.8.1-1
 - Fixed excessive CPU consumption with GPU monitoring
 - GPU monitoring is off by default; enable with "use feature: GPUsMonitor"

doc/version-history/8-8.history.tex

@@ -23,8 +23,7 @@ \subsection*{\label{sec:New-8-8-2}Version 8.8.2}
 
 \begin{itemize}
 
-\item HTCondor version 8.8.2 not yet released.
-%\item HTCondor version 8.8.2 released on Month Date, 2019.
+\item HTCondor version 8.8.2 released on April 11, 2019.
 
 \end{itemize}
 
@@ -44,8 +43,8 @@ \subsection*{\label{sec:New-8-8-2}Version 8.8.2}
 \Ticket{5884}
 
 \item The Python bindings \Code{ClassAd} module has
-	a new \Procedure{printJson} method to serialize a ClassAd
-	into a string in JSON format.
+a new \Procedure{printJson} method to serialize a ClassAd
+into a string in JSON format.
 \Ticket{6950}
 
 \end{itemize}
@@ -54,27 +53,27 @@ \subsection*{\label{sec:New-8-8-2}Version 8.8.2}
 
 \begin{itemize}
 
-\item Included a patch from the development series that fixes problems that
-could crash \Condor{annex} to crash.
-\Ticket{6980}
+\item Support for the \Condor{ssh\_to\_job} command, when ssh'ing to a 
+Singularity job, requires the nsenter command.  Previous versions of HTCondor
+relied on features of nsenter not universally available.  8.8.2 now
+works with all known versions of nsenter.
+\Ticket{6934}
 
 \item Moved the execution of \Macro{USER\_JOB\_WRAPPER} with Singularity jobs
 to be executed outside the container, not inside the container.
 \Ticket{6904}
 
-\item Fixed a bug where local universe jobs where unable to run
-\Condor{submit} to their local schedd.
-\Ticket{6920}
-
-\item Fixed a bug where condor\_ssh\_to\_job would not work to a Docker 
+\item Fixed a bug where \Condor{ssh\_to\_job} would not work to a Docker 
 universe job when file transfer was off.
 \Ticket{6945}
 
-\item Support for the condor\_ssh\_to\_job command, when ssh'ing to a 
-singularity job, requires the nsenter command.  Previous versions of HTCondor
-relied on features of nsenter not universally available.  8.8.2 now
-works with all known versions of nsenter.
-\Ticket{6934}
+\item Included a patch from the development series that fixes problems that
+could crash \Condor{annex} to crash.
+\Ticket{6980}
+
+\item Fixed a bug that could cause the \File{job\_queue.log} file to
+be corrupted when the \Condor{schedd} compacts it.
+\Ticket{6929}
 
 \item The \Condor{userprio} command, when given the -negotiator and -l options
 used to emit the value of the concurrency limits in the one large ClassAd it
@@ -95,15 +94,22 @@ \subsection*{\label{sec:New-8-8-2}Version 8.8.2}
 prefixes or via wildcards.
 \Ticket{6958}
 
-\item In some situations, the bytes sent and bytes received values in
-the termination event of the job event log could be reversed.
-This has been fixed.
-\Ticket{6914}
+\item The Condor{master} now waits until the \Condor{procd} has exited before exiting itself. This change
+helps to prevent problems on Windows with using the Service Control Manager to restart the Condor service.
+\Ticket{6952}
 
-\item For grid universe jobs of type \Expr{batch}, the job now receives a
-signal when the batch system wants it to exit, giving the job a chance to
-shut down gracefully.
-\Ticket{6915}
+\item Fixed a bug on Windows that could cause a delay of up to 2 minutes in responding
+to \Condor{reconfig}, \Condor{restart} or \Condor{off} commands when using shared port.
+\Ticket{6960}
+
+\item Fixed a bug that could cause the \Condor{schedd} on Windows to to restart with the message
+"fd\_set is full".  This change reduces that maximum number of active connections that
+a \Condor{collector} or \Condor{schedd} on Windows will allow from 1023 to 1014.
+\Ticket{6957}
+
+\item Fixed a bug where local universe jobs where unable to run
+\Condor{submit} to their local schedd.
+\Ticket{6920}
 
 \item Restored the old Python bindings for reading the job event log
 (\Code{EventIterator} and \Code{read\_events()}).
@@ -112,28 +118,20 @@ \subsection*{\label{sec:New-8-8-2}Version 8.8.2}
 Users should transition to the replacement bindings (\Code{JobEventLog})
 \Ticket{6939}
 
-\item Fixed a bug that could cause the \File{job\_queue.log} file to
-be corrupted when the \Condor{schedd} compacts it.
-\Ticket{6929}
-
 \item Fixed a bug that could cause entries in the job event log to be
 written with the wrong job id when a \Condor{shadow} process is used to
-run multiplejobs.
+run multiple jobs.
 \Ticket{6919}
 
-\item Fixed a bug on Windows that could cause a delay of up to 2 minutes in responding
-to \Condor{reconfig}, \Condor{restart} or \Condor{off} commands when using shared port.
-\Ticket{6960}
-
-\item Fixed a bug that could cause the \Condor{schedd} on Windows to to restart with the message
-"fd\_set is full".  This change reduces that maxumum number of active connections that
-a \Condor{collector} or \Condor{schedd} on Windows will allow from 1023 to 1014.
-\Ticket{6957}
-
-\item The Condor{master} now waits until the \Condor{procd} has exited before exiting itself. This change
-helps to prevent problems on Windows with using the Service Control Manager to restart the Condor service.
-\Ticket{6952}
+\item In some situations, the bytes sent and bytes received values in
+the termination event of the job event log could be reversed.
+This has been fixed.
+\Ticket{6914}
 
+\item For grid universe jobs of type \Expr{batch}, the job now receives a
+signal when the batch system wants it to exit, giving the job a chance to
+shut down gracefully.
+\Ticket{6915}
 
 \end{itemize}
 
@@ -162,7 +160,7 @@ \subsection*{\label{sec:New-8-8-1}Version 8.8.1}
 \Ticket{6857}
 
 \item Discovered a bug in DAGMan where graph metrics reporting could sometimes 
-send the \condor{dagman} process into an infinite loop. We worked around this 
+send the \Condor{dagman} process into an infinite loop. We worked around this 
 by disabling graph metrics reporting by default, via the new  
 \Macro{DAGMAN\_REPORT\_GRAPH\_METRICS} configuration knob.
 \Ticket{6896}

nmi_tools/glue/build/build_uw_deb.sh

@@ -57,10 +57,10 @@ echo "Distribution is $dist"
 cp -pr build/packaging/new-debian debian
 
 # Nightly build changelog
-dch --distribution $dist --newversion "$condor_version-0.$condor_build_id" "Nightly build"
+#dch --distribution $dist --newversion "$condor_version-0.$condor_build_id" "Nightly build"
 
 # Final release changelog
-#dch --release --distribution $dist ignored
+dch --release --distribution $dist ignored
 
 dpkg-buildpackage -uc -us
 

nmi_tools/glue/build/build_uw_rpm.sh

@@ -79,9 +79,9 @@ update_spec_define git_build 0
 update_spec_define tarball_version "$condor_version"
 update_spec_define condor_build_id "$condor_build_id"
 # Set HTCondor base release for pre-release build
-update_spec_define condor_base_release "0.$condor_build_id"
+#update_spec_define condor_base_release "0.$condor_build_id"
 # Set HTCondor base release to 1 for final release.
-#update_spec_define condor_base_release "1"
+update_spec_define condor_base_release "1"
 
 VERBOSE=1
 export VERBOSE