Your message dated Mon, 06 May 2024 20:15:54 +0000
with message-id <e1s44kc-00adoq...@fasolo.debian.org>
and subject line Bug#1070420: fixed in vagrant 2.3.7+git20230731.5fc64cde+dfsg-1
has caused the Debian Bug report #1070420,
regarding src:vagrant: unsatisfied build dependency in testing: ruby-net-ftp 
(>= 0.2) | ruby-net-ftp (>= 0.2)
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.)


-- 
1070420: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1070420
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: vagrant
Version: 2.3.6+dfsg-1
Severity: serious
Tags: sid trixie
User: debian...@lists.debian.org
Usertags: edos-uninstallable

Dear maintainer(s),

Dose [1] is reporting a build issue with your package, it's missing a
build dependency. Obviously your build dependencies shouldn't be
removed from testing, but unfortunately there are multiple scenarios
where that can happen nevertheless. To uphold our social contract,
Debian requires that packages can be rebuild from source in the suite
we are shipping them, so currently this is a serious issue with your
package in testing. ruby3.2 which provides these versions of ruby-net-ftp is currently blocked by three RC bugs. I also note that the runtime dependency of bin:vagrant is non-versioned.

Can you please investigate the situation and figure out how to resolve
it? Regularly, if the build dependency is available in unstable,
helping the maintainer of your Build-Depends to enable migration to
testing is a great way to solve the issue. If your build dependency is
gone from unstable and testing, you'll have to fix the build process
in some other way.

Paul

Note: this bug report was sent after some quick manual checks using a
template. Please reach out to me if you believe I made a mistake in my
process.

[1] https://qa.debian.org/dose/debcheck/src_testing_main/latest/amd64.html

Attachment: OpenPGP_signature.asc
Description: OpenPGP digital signature


--- End Message ---
--- Begin Message ---
Source: vagrant
Source-Version: 2.3.7+git20230731.5fc64cde+dfsg-1
Done: Lucas Nussbaum <lu...@debian.org>

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

Debian distribution maintenance software
pp.
Lucas Nussbaum <lu...@debian.org> (supplier of updated vagrant 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: Mon, 06 May 2024 21:08:41 +0200
Source: vagrant
Architecture: source
Version: 2.3.7+git20230731.5fc64cde+dfsg-1
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 
<pkg-ruby-extras-maintain...@lists.alioth.debian.org>
Changed-By: Lucas Nussbaum <lu...@debian.org>
Closes: 1070420
Changes:
 vagrant (2.3.7+git20230731.5fc64cde+dfsg-1) unstable; urgency=medium
 .
   [ Antonio Terceiro ]
   * Drop myself from Uploaders
 .
   [ Lucas Nussbaum ]
   * New upstream version 2.3.7+git20230731.5fc64cde+dfsg
     + This is the last commit before the license change to BUSL.
   * Add patch: 0009-Raise-error-if-openssl-headers-not-found.patch
   * Add build-dep on libssl-dev and switch to Architecture: any to build the
     vagrant_ssl extension
   * Fix rubygems-integration path due to the above arch:any change
   * Drop Build-dep on ruby-net-ftp, which is provided by libruby3.X anyway.
     Closes: #1070420
   * Remove watch file: we don't expect upstream updates
   * Add patch 0010-Remove-shebang-from-bash-completion-file.patch to fix
     lintian warning.
Checksums-Sha1:
 eee205a181034b05eb8b9ad83ffb89abaebee5dc 2850 
vagrant_2.3.7+git20230731.5fc64cde+dfsg-1.dsc
 ef0f0bc1a4197501b9a450a29f0c130d4e0a621d 1894748 
vagrant_2.3.7+git20230731.5fc64cde+dfsg.orig.tar.xz
 7eddd398161025cd378398e63e818bcd853a885f 16952 
vagrant_2.3.7+git20230731.5fc64cde+dfsg-1.debian.tar.xz
 f60e9d518236336deae93f016aa0303789f9093f 11025 
vagrant_2.3.7+git20230731.5fc64cde+dfsg-1_source.buildinfo
Checksums-Sha256:
 6efdd239246811af8ca5c35e9278c06539b3707fcf9af8f9f537699d302ad576 2850 
vagrant_2.3.7+git20230731.5fc64cde+dfsg-1.dsc
 ccddc8f97704a7d393d932ec0bd3d46b85ad71a7ca5c6c74ee5d7163b96925d2 1894748 
vagrant_2.3.7+git20230731.5fc64cde+dfsg.orig.tar.xz
 fa67d6c4791d69d3a42e665f404498028f5fb64ca7c3a657ad2822c9f6863305 16952 
vagrant_2.3.7+git20230731.5fc64cde+dfsg-1.debian.tar.xz
 f26896bfbcbc8c7190096ce7ae858f410cd61d91e41569800ab43a23ecad4945 11025 
vagrant_2.3.7+git20230731.5fc64cde+dfsg-1_source.buildinfo
Files:
 715433af7f85bf28756422df908c7bc2 2850 admin optional 
vagrant_2.3.7+git20230731.5fc64cde+dfsg-1.dsc
 f84b399c31b81d743404f32fb8ccef15 1894748 admin optional 
vagrant_2.3.7+git20230731.5fc64cde+dfsg.orig.tar.xz
 cffc43b43cba3be007a95cb4288c7c84 16952 admin optional 
vagrant_2.3.7+git20230731.5fc64cde+dfsg-1.debian.tar.xz
 50e4184cf76bf7bf89a4613eda11c422 11025 admin optional 
vagrant_2.3.7+git20230731.5fc64cde+dfsg-1_source.buildinfo

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

iQIzBAEBCgAdFiEE/t7ByzN7z1CfQ8IkORS1MvTfvpkFAmY5KwAACgkQORS1MvTf
vpkBdg/+K2yUf46TNxmEM23HGGoupQ9xkQeUeK1ot6oDYmQVTZdeE2YYRfwZc4cl
aTkwYfLpVPACcsA7CkxC3mVxJ40oVmZBZ6D8Ty39eaMbXmITViibiWFekVTfxGLD
V9a4z593VM1bJwLTl2edOGJ5/nYyACUpn8LCK7bRgnxYBJPLuiH1vgzom9P91s65
U3ER4LGXks/hjqSQW8qB3ZDbRvNpG7lleK14xSxzUI90NRhQuBTs+4jmIGRcka4I
wlfUPecC7t87i7Dr1SkRI73i/oheIZ/zG8sHPpALputbaTdeppmth8pYEm9YHXth
pdM0DaFiLC47sj5lvFufFopmUvpQBVjuylGDSKbqs4sVk7wnysWwKmV9RdFnWHr3
Y6knPFXu1x/3hGHU+mNpF/yZz3rlFjJ4A6pJyfUPrmxV/2IgWMy1MrkHf16Uf7Ze
HTbtXTopMpQZRO3GeS+cQrpxH6berYiIIpTbmgiWZJZD4qvhnLssxvnD6Ksm8vEP
WRVKrBDgrI/cvqgEMDAkFynXq9OvGfX0K3VbdMIfNm5jrFljf6NwHJhCq7jsjJ1F
HHPStyyWuBH60Arhy4/CloHOfD8ibyUGo9UOz30k9Mr5+5vrpnIKiv+mdWbwGDuO
3n8i+1cAIfsQ3BlEvm7k2O3xsk/HDdUXniW10WcFWNWasImn1vE=
=IC1E
-----END PGP SIGNATURE-----

Attachment: pgpTrFr4fp4I0.pgp
Description: PGP signature


--- End Message ---

Reply via email to