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

Bug#893133: marked as done (Could we maintain compatibility with older debhelpers to ease backporting)



Your message dated Sat, 24 Mar 2018 20:54:59 +0000
with message-id <E1ezqBn-0004Jb-OS@fasolo.debian.org>
and subject line Bug#893133: fixed in singularity-container 2.4.5-1
has caused the Debian Bug report #893133,
regarding Could we maintain compatibility with older debhelpers to ease backporting
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 owner@bugs.debian.org
immediately.)


-- 
893133: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=893133
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: singularity-container
Version: 2.4.2-4
Severity: wishlist

Dear Afif

Thanks for maintaining and updating the package through the latest releases.
But I wondered -- since you also had similar (minor but still) pains -- could
we retain/maintain compatibility with previous versions of debhelper, e.g. 10
(or even better 9, which I believe still supported by debhelper in sid).

I am asking because we try to autobuild backports of singularity for all still
supported debian and ubuntu releases in neurodebian:
http://neuro.debian.net/pkgs/singularity-container.html and that is why I
am typically trying to maintain compatibility to avoid need to patch etc, which
becomes painful and thus inefficient.

I see that motivation to jump to 11 from 9 was:

    $> git log debian/compat
    commit 01fd7b1b0ab23b03b424e567342dec180b45e2d7
    Author: Afif Elghraoui <afif@debian.org>
    Date:   Sat Feb 17 15:55:58 2018 -0500

        debhelper compat 11

        Since 10, it's no longer necessary to manually pass `--with-autoreconf`
        or explicitly depend on the autoreconf debhelper plugin.
        The package build is also parallel by default. We'll have to force
        serial build if that becomes a problem.

which I would think is just to make better use of available features of recent
debhelper, and not really due to "demand/necessity".  Would you mind if I
revert it, and thus simplify backporting for both of us? ;)

Thanks in advance for the consideration

-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (600, 'unstable'), (300, 'experimental'), (100, 'unstable-debug'), (100, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.15.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages singularity-container depends on:
ii  libc6           2.27-1
ii  python          2.7.14-4
ii  squashfs-tools  1:4.3-5

Versions of packages singularity-container recommends:
ii  e2fsprogs  1.43.9-2

singularity-container suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: singularity-container
Source-Version: 2.4.5-1

We believe that the bug you reported is fixed in the latest version of
singularity-container, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 893133@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Afif Elghraoui <afif@debian.org> (supplier of updated singularity-container package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 24 Mar 2018 16:24:45 -0400
Source: singularity-container
Binary: singularity-container
Architecture: source
Version: 2.4.5-1
Distribution: unstable
Urgency: medium
Maintainer: Debian HPC Team <debian-hpc@lists.debian.org>
Changed-By: Afif Elghraoui <afif@debian.org>
Description:
 singularity-container - container platform focused on supporting "Mobility of Compute"
Closes: 893133
Changes:
 singularity-container (2.4.5-1) unstable; urgency=medium
 .
   [ Yaroslav Halchenko ]
   * Revert 01fd7b1b0ab23b03b424e567342dec180b45e2d7 to bring back
     compatibility with debhelper 9 to ease backports (Closes: #893133)
 .
   [ Afif Elghraoui ]
   * New upstream version
Checksums-Sha1:
 48bfc9bc61cf6f151895b1ac6bbce6d49c12a3f2 2166 singularity-container_2.4.5-1.dsc
 3502b1524e8e3a8737db1d96f6f3e32d44b9645e 221139 singularity-container_2.4.5.orig.tar.gz
 66c3c2d3ea034132eb0649acf0f64df8762db9ae 7972 singularity-container_2.4.5-1.debian.tar.xz
 7d93ab0fe3aa3fbfd4875bcec2e854903ee633b6 5992 singularity-container_2.4.5-1_source.buildinfo
Checksums-Sha256:
 7cfabaf5f75d10cf185c3d2f0e44b84d4766a9122e019d2a4d9bc8ecce9746e6 2166 singularity-container_2.4.5-1.dsc
 c66af8d0f40a8eceadaeabc6cf7017a72f3de0ebbdc96313fa99eff8af4cc8ed 221139 singularity-container_2.4.5.orig.tar.gz
 a6eda433ade1e59cf95397e741ae9a469644c141651ade723f7b27e9c2d63861 7972 singularity-container_2.4.5-1.debian.tar.xz
 dd2b95c747231ab5a8424841ef76be2bd659a17610575267ddf5a1cd41ebc744 5992 singularity-container_2.4.5-1_source.buildinfo
Files:
 f310f470041a6f5488815642f60085d4 2166 admin optional singularity-container_2.4.5-1.dsc
 3c3b40284f8713d2f1bbc00e146ebc66 221139 admin optional singularity-container_2.4.5.orig.tar.gz
 ddf265c2d693fc687dfcb1e912454625 7972 admin optional singularity-container_2.4.5-1.debian.tar.xz
 dfd52167c919a00f8f572d022c31285f 5992 admin optional singularity-container_2.4.5-1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQJEBAEBCAAuFiEE6rcjomb2J+aAVWFfWbIwbzr53cEFAlq2tCsQHGFmaWZAZGVi
aWFuLm9yZwAKCRBZsjBvOvndwUV4D/9K+qeGWg11mBrzx1GFJ/cY4cQaTAD+GmMm
fpVafIGPDcHN/MnRuv6YH2AnSiouEOluM/yaTiqlnYTxrCUugzVy5hAGJ+lnOFbF
dwTU3sPHq3Wg6+RaKgU3BXXgdHBOSxnrH8Sptq5j3CzKxikFCQ9zI5ORWKao+jQ6
2i22W0lAqYMWYpTefGNGPNw9EniSdxB+1jV2u1wEUPipvZdPoJiGT6ZYK+qUZvRR
7gU1xA9mNYrmuZsgJ/L2+S6pzUjxBWebN0fhhYf6IsWoDKvAJ+AhLctQaOsVxCW6
lp3pEgv/47NRuKpyc9q8TIv1s1bjEFbsS5+kgcnXAOX95L8v4O6kRYDxKMioWAXD
a+7um+R/mrmvR1mS8mdAmbiabdob9pNIB/Wsv4wrBx6JlR+9CslNcUkfiFXCOhl2
cKQdcgf+d3UG4S2ckAyt/XVl55mMJ66J/kPHmM5QmYeH7b+ZNrWXH5rMf91nxxo4
OPl3nfrZR+r2Tq8h1n/ctoB+iy2skvZnmXIVuGSoQI/PYUO9NqxmTeVAFxNHnINX
igwL9yQNpueGj8pFKKeZwGpPMfqYNLZVWBS+mY1v50ZfeBnU4wUDLeU7aO4k6FrD
kOrQJ2ik4ZReC1p25I/s2XGoigw9QVkhuM0C5VI4tquGCR23sjQK1EGrHcAEGYKu
2Bb6NEUgNQ==
=AWe8
-----END PGP SIGNATURE-----

--- End Message ---

Reply to: