Your message dated Fri, 20 Dec 2024 13:51:23 +0000
with message-id <e1todpx-002pf5...@fasolo.debian.org>
and subject line Bug#1088444: fixed in python-upstream-ontologist 0.2.2-2
has caused the Debian Bug report #1088444,
regarding python-upstream-ontologist FTBFS: error: no matching package named 
`upstream-ontologist` found
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 ow...@bugs.debian.org
immediately.)


-- 
1088444: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088444
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: python-upstream-ontologist
Version: 0.2.0-1
Severity: serious
Tags: ftbfs

https://buildd.debian.org/status/fetch.php?pkg=python-upstream-ontologist&arch=amd64&ver=0.2.0-1%2Bb2&stamp=1732745543&raw=0

...
error: no matching package named `upstream-ontologist` found
location searched: registry `crates-io`
required by package `upstream-ontologist-py v0.2.0 (/<<PKGBUILDDIR>>)`
error: `cargo metadata --manifest-path Cargo.toml --format-version 1` failed 
with code 101

--- End Message ---
--- Begin Message ---
Source: python-upstream-ontologist
Source-Version: 0.2.2-2
Done: Jelmer Vernooij <jel...@debian.org>

We believe that the bug you reported is fixed in the latest version of
python-upstream-ontologist, 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 1088...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Jelmer Vernooij <jel...@debian.org> (supplier of updated 
python-upstream-ontologist 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 ftpmas...@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Format: 1.8
Date: Fri, 20 Dec 2024 13:03:29 +0000
Source: python-upstream-ontologist
Architecture: source
Version: 0.2.2-2
Distribution: unstable
Urgency: medium
Maintainer: Jelmer Vernooij <jel...@debian.org>
Changed-By: Jelmer Vernooij <jel...@debian.org>
Closes: 1088444
Changes:
 python-upstream-ontologist (0.2.2-2) unstable; urgency=medium
 .
   * Merge release 0.2.2.
     + Fixes build. Closes: #1088444
Checksums-Sha1:
 666d072a406f3c447dbafbc3efee306907216d51 1973 
python-upstream-ontologist_0.2.2-2.dsc
 fbade4dcd44fbb7b5c5124867f4818c8a75e6f89 47123 
python-upstream-ontologist_0.2.2.orig.tar.gz
 172560f3080ba67cf6c4923d3bb0c08231167d3c 35328 
python-upstream-ontologist_0.2.2-2.debian.tar.xz
 aff0f870b6ca2d1e599716fbdf4d63b0df3cecae 54366 
python-upstream-ontologist_0.2.2-2_source.buildinfo
Checksums-Sha256:
 f72b66a6d196c173d026c37e49d05e24d781a06b7c74ea32e26c659049a07503 1973 
python-upstream-ontologist_0.2.2-2.dsc
 5e593f488d865c9017ea4146065f6f152c63b50cc1a8e88087a29a021f4df7ad 47123 
python-upstream-ontologist_0.2.2.orig.tar.gz
 fc2dfc14d2a551f3f26660f9b97c12e0d4ee743f290c16dd1c623daa24c5aa9d 35328 
python-upstream-ontologist_0.2.2-2.debian.tar.xz
 147eee2429395583a9b4a543d59bd5b24e323d23b8f993e08be191ace340537f 54366 
python-upstream-ontologist_0.2.2-2_source.buildinfo
Files:
 953770241cacbddcba96a9a9b881c3a3 1973 python optional 
python-upstream-ontologist_0.2.2-2.dsc
 99529f89e4052a4fc8fc75ea758f4623 47123 python optional 
python-upstream-ontologist_0.2.2.orig.tar.gz
 472f9dd0c56e3d98985f261507ed43ee 35328 python optional 
python-upstream-ontologist_0.2.2-2.debian.tar.xz
 7a11f131bb1dcf00cfc2964823745593 54366 python optional 
python-upstream-ontologist_0.2.2-2_source.buildinfo

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

iQEzBAEBCgAdFiEEgIoEfJX3ae+y722SMG8hYYBCUGYFAmdlcU4ACgkQMG8hYYBC
UGYYqwf/VB6GIO8BlfbOCSRxi68JbEOckrPK1g9sYeONrRqtASEIC2dbPtQYAxG/
5rXxzfwVcaOp4zeRPfhAP2nspKNwB8ZltrQSvhsMJXkxN6bs4EhhrCyZkzFVe+7E
9BpAmvZtJiRMrRRA4hix3jUkiN11nPxG9ic4EiCGGQVB8GLtwVqOowuB88iK8UuS
8Q2TRa0JYz1dx9DMBK7ZJU70Y9Cm7nN6pZsyvnl9RfZG3sUC/xZh05J/Eh2rCb8r
79meV2cuAepD68QhTOqUVIWoa1IezniVR5PBacvq13rgnHsyyPo2a+vH8L77Iqij
tTTx4MZAZOvcNdL+2UiYe3znvfkM+g==
=qfJy
-----END PGP SIGNATURE-----

Attachment: pgpBFYAvebbgq.pgp
Description: PGP signature


--- End Message ---

Reply via email to