Your message dated Thu, 04 Apr 2024 11:34:30 +0000
with message-id <e1rslmu-009uxr...@fasolo.debian.org>
and subject line Bug#1068381: fixed in openapi-specification 3.1.0-2
has caused the Debian Bug report #1068381,
regarding openapi-specification: please include examples in Debian package
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.)


-- 
1068381: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068381
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: openapi-specification
Version: 3.1.0-1
Severity: normal

Hi!

Would it be possible to include the OpenAPI-Specification examples in
the Debian package?  (Adding debian/examples with the single line:

examples/*

would do it.)  They're used in the test suite of a package I'm trying
to build, and it would be great to be able to just depend on the
Debian package for this.

Best wishes,

   Julian

--- End Message ---
--- Begin Message ---
Source: openapi-specification
Source-Version: 3.1.0-2
Done: Andrius Merkys <mer...@debian.org>

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

Debian distribution maintenance software
pp.
Andrius Merkys <mer...@debian.org> (supplier of updated openapi-specification 
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: Thu, 04 Apr 2024 07:02:32 -0400
Source: openapi-specification
Architecture: source
Version: 3.1.0-2
Distribution: unstable
Urgency: medium
Maintainer: Andrius Merkys <mer...@debian.org>
Changed-By: Andrius Merkys <mer...@debian.org>
Closes: 1068381
Changes:
 openapi-specification (3.1.0-2) unstable; urgency=medium
 .
   [ Debian Janitor ]
   * Apply multi-arch hints. + openapi-specification: Add Multi-Arch: foreign.
   * Set upstream metadata fields: Bug-Database, Bug-Submit, Repository-Browse.
 .
   [ Andrius Merkys ]
   * Install examples (Closes: #1068381).
   * Add 'Repository' to debian/upstream/metadata.
   * Bump Standards-Version to 4.6.2 (no changes).
   * Bump copyright year.
Checksums-Sha1:
 8ae465ff9afc6e2c9769b834a13d622adab0baed 1979 openapi-specification_3.1.0-2.dsc
 ec05a031f1fd591a475907eed4fff865e210dc06 1916 
openapi-specification_3.1.0-2.debian.tar.xz
 7f62eaffb8cbdc20bff88b4f5e4207af2c1e5a49 6643 
openapi-specification_3.1.0-2_source.buildinfo
Checksums-Sha256:
 44f6c1e8c3f50bf5bd4d8f9a3de5bf38abf3b88571056a1c0eb2a919add52546 1979 
openapi-specification_3.1.0-2.dsc
 c6d486f6d135c8117bf69f8639af1738483cfc99c4534429032765ec1d5a103b 1916 
openapi-specification_3.1.0-2.debian.tar.xz
 fb46904ee1b822a0e1a898aca5ae3f0b58728b1436cf9aa410df3f33e2f8c073 6643 
openapi-specification_3.1.0-2_source.buildinfo
Files:
 e04c753c5338c275baed48d76e5dd2a5 1979 web optional 
openapi-specification_3.1.0-2.dsc
 a321b5c416136e3914bee3988b9fbf60 1916 web optional 
openapi-specification_3.1.0-2.debian.tar.xz
 1cf03a0e38108fbc83826e02ac62d49e 6643 web optional 
openapi-specification_3.1.0-2_source.buildinfo

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

iQJGBAEBCgAwFiEEdyKS9veshfrgQdQe5fQ/nCc08ocFAmYOjEISHG1lcmt5c0Bk
ZWJpYW4ub3JnAAoJEOX0P5wnNPKHOpAQAIDCMppvcxHRkVW2KrFRsvOqG+J253T9
1b0vFq2BJcKXrkgNQUxIJRh4OBP1256WWnGUQhg+3LeyVwEtBPHvRyqi2LIVM809
KSz3ucA+HgdkrONhyk/fC6bhL/7+XlPHGhcf/IerxYJp1CzOfQ8E6ynoSQHzxf1c
7jlCi73WBw7+b4Lkc6d7ZKe8G6JEGstuJc7gy2wQN7teKVyO6xu3k6q2sllaAgfF
9GzduxThAqIekRpW6S2QVrx1+Ciy54QuYvjQPdAtzWJ40YM3QWMdg3DMABEeg2j4
lfO8Zzjy/x269QBX1+hZDvt/ywEgrmZYITW4sVsotHxArHptj1P821DnUxWD/YY8
PtjeztyOPALveZ5NKb1jIWhqd4iiOZ6LVnjcg2kL/4HKylSDtJdkS4XlIXWN1QtZ
km0rWF2tpKzdpHfi9uhSYJanda+vVES1nd5ZRqmyNEcn5s9XFM20UMpXCQe0Yjep
gFIjxg7WolZB/37EKSuUTmXBTQEWLDulFjsYDKd4htleRWF5UTIHSr7wlmk490xK
LqoXyeYfphrKIxiGVechthi7kWea96z5jB/9su88jCceHOnUU9tXIVKH24ar4I/2
GN4Y4IhbascWpnlBX7oA93ry9ja+BOYagTKCLixJ/eeq5EbAQvmUqwIbjgoljf7y
4zVqcfTv0od1
=OD5C
-----END PGP SIGNATURE-----

Attachment: pgpCGe3nqBqGw.pgp
Description: PGP signature


--- End Message ---

Reply via email to