datalad-container (1.2.5-1) unstable; urgency=medium

  * Fresh upstream release
    - upgraded versioneer so should not cause troubles with recent Pythons
      which removed SafeConfigParser (Closes: #1060979)
  * debian/gbp.conf
    - specify all custom branches and tags

 -- Yaroslav Halchenko <debian@onerussian.com>  Thu, 18 Jan 2024 09:26:50 -0500

datalad-container (1.1.9-1) unstable; urgency=medium

  * Fresh upstream release
    - accounts for the move of @eval_results (Closes: #1030466)

 -- Yaroslav Halchenko <debian@onerussian.com>  Sun, 05 Feb 2023 20:26:19 -0500

datalad-container (1.1.7-1) unstable; urgency=medium

  * Fresh upstream release
    - moved to pytest for testing. d/{control,rules} adjusted.
      (Closes: #1018335)

 -- Yaroslav Halchenko <debian@onerussian.com>  Mon, 29 Aug 2022 20:56:28 -0400

datalad-container (1.1.6-1) unstable; urgency=medium

  [ Adrian Bunk ]
  * New upstream release.
    - Fixes FTBFS. (Closes: #1009381)

  [ Yaroslav Halchenko ]
  * Add debian/source/options to exclude diff in datalad_container/_version.py
    produced by versioneer.

 -- Yaroslav Halchenko <debian@onerussian.com>  Thu, 26 May 2022 10:40:11 -0400

datalad-container (1.1.2-1) unstable; urgency=medium

  [ Michael Hanke ]
  * New upstream release (missed 1.1.1).
    - Now compatible with DataLad 0.14x

 -- Yaroslav Halchenko <debian@onerussian.com>  Mon, 01 Feb 2021 09:58:48 -0500

datalad-container (1.1.0-1) unstable; urgency=medium

  * Recent upstream release
  * d/rules
    - exclude test_custom_call_fmt from running since then system-wide
      datalad fails to find our extension

 -- Yaroslav Halchenko <debian@onerussian.com>  Mon, 14 Dec 2020 22:40:56 -0500

datalad-container (1.0.1-1) unstable; urgency=medium

  * Upstream release which should be compatible with upcoming
    DataLad 0.14 (and current master)

 -- Yaroslav Halchenko <debian@onerussian.com>  Tue, 08 Sep 2020 18:39:27 -0400

datalad-container (1.0.0-2) unstable; urgency=medium

  [ Sandro Tosi ]
  * Use python3-requests; Closes: #942936

 -- Yaroslav Halchenko <debian@onerussian.com>  Sun, 29 Mar 2020 16:26:42 -0400

datalad-container (1.0.0-1) unstable; urgency=medium

  * Fresh upstream release
    - requires datalad >= 0.12
  * boost compat to 10

 -- Yaroslav Halchenko <debian@onerussian.com>  Mon, 24 Feb 2020 10:31:21 -0500

datalad-container (0.5.0-1) unstable; urgency=medium

  * Recent upstream release

 -- Yaroslav Halchenko <debian@onerussian.com>  Mon, 12 Aug 2019 11:38:05 -0400

datalad-container (0.4.0-1) experimental; urgency=medium

  * Fresh upstream release
    - d/control: minimal required datalad version is 0.11.5

 -- Yaroslav Halchenko <debian@onerussian.com>  Wed, 29 May 2019 15:28:39 -0400

datalad-container (0.3.1-1) experimental; urgency=medium

  * Fresh upstream release
  * debian/patches - dropped, upstreamed

 -- Yaroslav Halchenko <debian@onerussian.com>  Wed, 06 Mar 2019 10:09:17 -0500

datalad-container (0.2.2-2) unstable; urgency=medium

  * Re-upload to Debian proper (Closes: #918924)
  * debian/copyright
    - adjusted to reference copyright/license of borrowed code under Python2
      license

 -- Yaroslav Halchenko <debian@onerussian.com>  Mon, 14 Jan 2019 11:52:19 -0500

datalad-container (0.2.2-1) neurodebian; urgency=low

  * Initial packaging
    - source package initiated by stdeb 0.8.5

 -- Yaroslav Halchenko <debian@onerussian.com>  Thu, 10 Jan 2019 11:18:42 -0500