Accepted orbit-predictor 1.9.3-2 (source) into unstable
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Sat, 02 Jan 2021 18:31:15 -0600
Source: orbit-predictor
Architecture: source
Version: 1.9.3-2
Distribution: unstable
Urgency: low
Maintainer: Debian Astronomy Maintainers <debian-astro-maintainers@lists.alioth.debian.org>
Changed-By: Josue Ortega <josue@debian.org>
Closes: 974518
Changes:
orbit-predictor (1.9.3-2) unstable; urgency=low
.
[Debian Janitor]
* Trim trailing whitespace.
* debian/copyright: use spaces rather than tabs to start continuation lines.
* Set upstream metadata fields: Bug-Database, Bug-Submit, Repository,
Repository-Browse.
* Update standards version to 4.5.0, no changes needed.
.
[Josue Ortega]
* Add tlelines autopkgtest run time test instead of running
superficial test (Closes: #974518)
* Bump debhelper-compat to use (= 13)
* Bump Standards-Version to 4.5.1. No changes required
* debian/watch: Bump file standard version to 4
Checksums-Sha1:
81ce3980bc0605b0cba0d6bf739a394e558e00b3 2168 orbit-predictor_1.9.3-2.dsc
979f0da0d4369b47dae2d54ad1da5b7333fbf84c 2772 orbit-predictor_1.9.3-2.debian.tar.xz
96e0f5dfc610c4c093a11d7fc6beda735228d511 6468 orbit-predictor_1.9.3-2_amd64.buildinfo
Checksums-Sha256:
7891dfd5cee006705749ecd89f875941c23fc4227edb403dbe64029b60a69120 2168 orbit-predictor_1.9.3-2.dsc
38421d80cdc88b0a8ba7358d06dc68b9cbe7dc6e22ec0dad31c9e57adeff51bd 2772 orbit-predictor_1.9.3-2.debian.tar.xz
4b2a88052cdd23a796731779e8c73998835c5652ed790d66537d3e693fb35782 6468 orbit-predictor_1.9.3-2_amd64.buildinfo
Files:
b8dee6c622b8888abdcbca496f66fb71 2168 python optional orbit-predictor_1.9.3-2.dsc
c22f81d8b4985b28f8c51c0993faf321 2772 python optional orbit-predictor_1.9.3-2.debian.tar.xz
7b853357aab43fedc76e16816845d469 6468 python optional orbit-predictor_1.9.3-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQJFBAEBCAAvFiEEdzOzKNJ5X1viMlrdAVCdXKtK/T8FAl/xEToRHGpvc3VlQGRl
Ymlhbi5vcmcACgkQAVCdXKtK/T/xuRAAkQemMNzlpJOkXCU20qXPIVA3eqFan+PZ
aXaChn5XseJSNWz6/klob90IrFojWfzOqWNJVVmdXIPBHC1zJKg3EwZp/u+DAeNP
/zlhSQCmQbImYkeTYBnzhjpV7EhoOa2QAGlIZiTEYTxMSu+lUQVE7VhjKbizXYkW
7hVkm9GrY7kToDjfuX4czaNYNI64E+70pFrNc3zoMXTXEEOCMjT312aI3DAd7H18
wOogfoHM6o77L2tm1iRp4JiL/LvbGziORjxKeTMqOxsV93+7LVXTX/DZPDqzFrj2
5T24boyc46ej8FHvuhEmWgWk1UpBqC9vuPCMfOQK9UfC9iA+1QARpCNe5TDwrdP0
gz2Dscws74nLKUXr+lYPWWtIpZgJJuwbklZIflq1ej+WMuEDLOXvztton85Np9Pt
GmfkF5uGDx16tVkRMQiDMJNrBs1psuDFE4NDQWbJlQeIr5B6QdC7zEIpQMRvaPBP
/ImCpjFqBbHMBH7IIR4qtfYAZ4+J1ummDRsBfguvAJt+OIKCZy4BJmvAzKko53Xp
+sncdk9wUcRMhNNGn6IHJSvLEM/KrQ5ZlY2TscT1+9pD2q4V/yZMoU21f/GhxMu0
0PHhbSvdqvssYNs2AIQLje4nTVGdzDJt8eGiv5auoI9OuJ/Z/1YgSnc7w/Plib1D
XeQfrEU9shU=
=3PME
-----END PGP SIGNATURE-----
Reply to: