[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Accepted singularity-container 2.4.2-4~bpo8+1 (source amd64) into jessie-backports-sloppy, jessie-backports-sloppy

Hash: SHA256

Format: 1.8
Date: Wed, 28 Feb 2018 00:26:18 -0500
Source: singularity-container
Binary: singularity-container
Architecture: source amd64
Version: 2.4.2-4~bpo8+1
Distribution: jessie-backports-sloppy
Urgency: high
Maintainer: Debian HPC Team <debian-hpc@lists.debian.org>
Changed-By: Afif Elghraoui <afif@debian.org>
 singularity-container - container platform focused on supporting "Mobility of Compute"
Closes: 850227 866169 871371 883466 887192
 singularity-container (2.4.2-4~bpo8+1) jessie-backports-sloppy; urgency=medium
   * Rebuild for jessie-backports-sloppy.
   * Switch to debhelper compat 10 (11 not available for jessie)
   * Drop reproducible_build.patch; incompatible
 singularity-container (2.4.2-4) unstable; urgency=low
   * Standards-Version 4.1.3
   * debhelper compat 11
   * Change squashfs tools to Depends from Recommends
   * Recommend e2fsprogs (Closes: #887192)
   * d/rules: add comment explaining why test suite can't be run
 singularity-container (2.4.2-3) unstable; urgency=low
   * Add Recommends: squashfs-tools
   * lintian overrides: update suid binary locations
 singularity-container (2.4.2-2) unstable; urgency=medium
   * Make package build reproducible again by making sure content of
     $HOME doesn't end up in manpages.
   * Fix FTBFS on mips* architectures (Closes: #883466). Thanks to
     James Cowgill for the patch!
   * Set "Debian HPC team" in the maintainer field.
   * Migrate Git repo on Salsa and update Vcs-* fields accordingly
   * Run wrap-and-sort
 singularity-container (2.4.2-1) unstable; urgency=medium
   * New upstream release
     - Fixed an issue for support of older distributions and kernels
       with regards to the setns() function
     - Fixed autofs bug path
   * Get source package's version using /usr/share/dpkg/pkg-info.mk
     instead of calling dpkg-parsechangelog in debian/rules. This is
     possible since dpkg >= 1.16.1.
 singularity-container (2.4.1-1) unstable; urgency=medium
   * Upload to unstable: general functionality is proven to be robust
     and 2.4.x will be needed for upcoming htcondor 8.6.8 with singularity
 singularity-container (2.4.1-1~exp1) experimental; urgency=medium
   * New upstream release
     - Fixed container path and owner limitations
     - Abort if overlay upper/work images are symlinks
     - Addition of APP[app]_[LABELS,ENV,RUNSCRIPT,META] so apps can
       internally find one another
     - Exposing labels for SCI-F in environment
   * debian/patches/reproducible_build
     - Refreshed patch
 singularity-container (2.4-1) experimental; urgency=medium
   * New upstream release
     - atomic 'build' process (no need to pre-create an image)
       - create command is deprecated in favor of image.create
     - new default image format based on SquashFS
     - more info: http://singularity.lbl.gov/release-2-4
   * debian/control
     - fixed Homepage (thanks Afif Elghraoui) (Closes: #850227)
   * debian/patches/reproducible_build
     - thanks tiress Chris Lamb (Closes: #866169)
 singularity-container (2.3.2-1) unstable; urgency=medium
   * New upstream release
     - debian/patches/up_makedirs_cache is no longer pertinent
 singularity-container (2.3.1-2) unstable; urgency=medium
   * Provide version for help2man from this changelog (Closes: #871371)
 singularity-container (2.3.1-1) unstable; urgency=high
   * Fresh upstream minor release
     - A potential escalation pathway was identified that could have
     allowed a malicious user to escalate their privileges on hosts that do not
     support the PR_SET_NO_NEW_PRIVS flag for the prctl() system call. This
     release fixes this as well as several other identified bugs and potential
     race conditions.
 singularity-container (2.3-1) unstable; urgency=medium
   * Fresh upstream minor release
   * debian/patches -- all dropped (upstreamed)
   * debian/copyright -- updated copyright holders/years
   * debian/rules
     - a few path tune ups for permissions tuning as introduced upstream
     - apparently still uses /var as default for localstatedir, so specified
       /var/lib explicitly
     - export SINGULARITY_CACHEDIR env var to instruct singularity
       to not attempt create cachedir somewhere under /nonexistent path
       Also added a patch to not fail to create that cache directory if
       parent doesn't exist
   * debian/control
     - Python to build-depends
 singularity-container (2.2.1-1) experimental; urgency=medium
   * Fresh upstream bugfix release (includes all included in 2.2-2 changesets,
     which are dropped now here)
 a503efbba1aeb6c6a485dcbf63548b03de4ff576 2181 singularity-container_2.4.2-4~bpo8+1.dsc
 789137bf72a94b077f495660a52b8e31a83e0f15 7636 singularity-container_2.4.2-4~bpo8+1.debian.tar.xz
 4ec8a98c623ba32cb43a88548382472fa2d95ee9 316988 singularity-container_2.4.2-4~bpo8+1_amd64.deb
 5fa8991cb95270760d3685ddb81ea05003b0e3b40cddcb0495bc3e15753985af 2181 singularity-container_2.4.2-4~bpo8+1.dsc
 e0d0bf474b342d19ef3ca60d9455b512e399386967b3c8583bb008db0cbbc6e7 7636 singularity-container_2.4.2-4~bpo8+1.debian.tar.xz
 9bacb6ede5c48e559d1d00fee160abbdf545c7f61362619d920d3b1e07a2a1eb 316988 singularity-container_2.4.2-4~bpo8+1_amd64.deb
 9f80487d1d145c9c1ca3496e078bbdf4 2181 admin optional singularity-container_2.4.2-4~bpo8+1.dsc
 190b849c4cfa22b9763e0b4e8f558e05 7636 admin optional singularity-container_2.4.2-4~bpo8+1.debian.tar.xz
 9447c765c89a868f90bf48271d241743 316988 admin optional singularity-container_2.4.2-4~bpo8+1_amd64.deb



Reply to: