Your message dated Sat, 03 Feb 2018 13:05:36 +0000
with message-id <[email protected]>
and subject line Bug#889174: fixed in vagrant 2.0.2+dfsg-2
has caused the Debian Bug report #889174,
regarding Please honor http_proxy in autopkgtests
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 [email protected]
immediately.)


-- 
889174: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=889174
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: vagrant
Version: 2.0.0+dfsg-1
Severity: wishlist
User: [email protected]
Usertags: origin-ubuntu bionic

Hi Antonio,

The vagrant 2.0.0+dfsg-1 package has been synced to Ubuntu for the bionic
release, but is not considered releasable here because its autopkgtests fail
on Ubuntu infrastructure.  This is because the vagrant autopkgtest tries to
access network resources without using the http_proxy configured in the
environment:

Bringing machine 'default' up with 'libvirt' provider...
==> default: Box 'debian/artful64' could not be found. Attempting to find and in
stall...
    default: Box Provider: libvirt
    default: Box Version: >= 0
The box 'debian/artful64' could not be found or
could not be accessed in the remote catalog. If this is a private
box on HashiCorp's Vagrant Cloud, please verify you're logged in via
`vagrant login`. Also, please double-check the name. The expanded
URL and error message are shown below:

URL: ["https://vagrantcloud.com/debian/artful64";]
Error: The requested URL returned error: 404 Not Found
+ cleanup
+ vagrant halt
==> default: Domain is not created. Please run `vagrant up` first.
+ vagrant destroy -f

(https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/amd64/v/vagrant/20171221_100053_c03fd@/log.gz)

Could these autopkgtests be adjusted to honor the http_proxy environment?

-- 
Steve Langasek                   Give me a lever long enough and a Free OS
Debian Developer                   to set it on, and I can move the world.
Ubuntu Developer                                    http://www.debian.org/
[email protected]                                     [email protected]

Attachment: signature.asc
Description: PGP signature


--- End Message ---
--- Begin Message ---
Source: vagrant
Source-Version: 2.0.2+dfsg-2

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 [email protected],
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Antonio Terceiro <[email protected]> (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 [email protected])


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 03 Feb 2018 10:44:25 -0200
Source: vagrant
Binary: vagrant
Architecture: source
Version: 2.0.2+dfsg-2
Distribution: unstable
Urgency: medium
Maintainer: Debian Ruby Team 
<[email protected]>
Changed-By: Antonio Terceiro <[email protected]>
Description:
 vagrant    - Tool for building and distributing virtualized development enviro
Closes: 884104 889174
Changes:
 vagrant (2.0.2+dfsg-2) unstable; urgency=medium
 .
   * New upstream release.
     - Removes usage of setting name deprecated by ruby-net-ssh (Closes: 
#884104)
   * debian/tests/integration-test: make sure box pulled for testing is a
     Debian one to avoid failures on non-Debian hosts (Closes: #889174)
   * Refresh patches:
     - 0001-Disable-Checkpoint.patch: removed as checkpoint integration was
       dropped upstream
     - 0007-Virtualbox-5.2-support.patch: removed, applied upstream
     - Renumbered remaining patches
   * Bump Standards-Version to 4.1.3; no changes needed
   * Change Maintainer to the Debian Ruby Team
   * Point Vcs-* to salsa.debian.org
   * debian/rules: check dependencies during the build
     - added dependencies as build dependencies
   * debian/vagrant.lintian-overrides: override warning about shebang in
     upstream bash completion file
Checksums-Sha1:
 304d495cffa7be1c7c9b12e5021d8de9ed336e4e 2296 vagrant_2.0.2+dfsg-2.dsc
 dc952753e6463e27dce18f899bbb43413031ce6e 694476 vagrant_2.0.2+dfsg.orig.tar.gz
 6dc50485341ab69c0e6915700c86f5852731c08e 12076 
vagrant_2.0.2+dfsg-2.debian.tar.xz
 2637421ad70c2f4e40b9e6de2f29072af973399c 7267 
vagrant_2.0.2+dfsg-2_source.buildinfo
Checksums-Sha256:
 a779040aeea106f8a42f859a56ef7fb6fb3d60c1a6d5441884a637222c4851ee 2296 
vagrant_2.0.2+dfsg-2.dsc
 7d475bc9b2f50e37b9338e2b6ddc3c8b3e0cb97640183cbd47226dc5a45a8775 694476 
vagrant_2.0.2+dfsg.orig.tar.gz
 e844e3410eeaee76e1ec44ae1768d93959cabe9b224dc409ca93c225420fac86 12076 
vagrant_2.0.2+dfsg-2.debian.tar.xz
 1950e0cd9e3da117851db682854c9aad2d07cb34d902afe05f6443000fbd0922 7267 
vagrant_2.0.2+dfsg-2_source.buildinfo
Files:
 2ab2d179ab5aa00f60d0e5a5aee9c8f3 2296 admin optional vagrant_2.0.2+dfsg-2.dsc
 cbaf5f5c919d6236f3ef42332e62c91d 694476 admin optional 
vagrant_2.0.2+dfsg.orig.tar.gz
 e72380a1de4c09e33d53ada953eb1ce2 12076 admin optional 
vagrant_2.0.2+dfsg-2.debian.tar.xz
 b69f9acce68f77c6c4dff77ceed372d9 7267 admin optional 
vagrant_2.0.2+dfsg-2_source.buildinfo

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

iQIzBAEBCAAdFiEEst7mYDbECCn80PEM/A2xu81GC94FAlp1r2UACgkQ/A2xu81G
C95z6g//enmyDGKjKM2YQYM8frm0rivUqyc3uSakZOqVXVucNSumm5xCJ0O6O1ze
KFKFfoI3GiHUTRM7Vb3NMqpXY/D2LUJz7P726lgGseQ5fpyrA5m4qveXyF9W9g6J
UE0KaOstm8fQcoJ9W1dnoDzZ6kT7C6C1jQ+CUMfP7r7Hc/FkXhr96w/QbADb0MiR
w+85IefW+HQd2SbqSSEKq0voOLrS4jcS6uZmrCC4/IBLjNKH/LsUKdYedfsNbYoF
aJEQUgct06RYBpdaGBy6mwGiPMT1FgdCiGLpgWS22sOsQ0k7DTDi0faev2fdRDTk
Rgn53IwFMMvwBjwzKszICWb17Ko197xjNWcQktYFK0halqMWnaJKrrrd9ULjzoV3
S8DuQgSzd3E3+dLsmSAWERt64fsoGY/5KdbNgYdABQ/jExNXW1j6UTm5e/r3+D6w
nGHxdvrW62jj2CjdHwQSELiEn/AVo+g2CVJdLvYPRHTd13BZ8Da4HytUXrOZXMUk
muSmwLiGf6iPOdLT4mrHRtSBXdB5fpDT0LmPsamOnhQvuT5nhWwQx5FU5xMn8gRc
hsBQkO601p8BsXMux01ODG/L2SrAkiwfY+lBfC1wE1dTGVlDjyTQjrNW2W3Wb2je
2+LocUboKGAiMm0XgSVhjXR+U5FyUpY4upcXGo5zKrqo8oTmdLs=
=/Qbh
-----END PGP SIGNATURE-----

--- End Message ---

Reply via email to