Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.bugs.dist > #1165096

Bug#1049999: vagrant: the future of packaging vagrant in Debian

From Antonio Terceiro <terceiro@debian.org>
Newsgroups linux.debian.bugs.dist
Subject Bug#1049999: vagrant: the future of packaging vagrant in Debian
Date 2023-08-22 17:10 +0200
Message-ID <H5Bb3-3E62-3@gated-at.bofh.it> (permalink)
References (1 earlier) <H41jj-2Fcq-3@gated-at.bofh.it> <H45wB-2I8w-3@gated-at.bofh.it> <H4me5-2SpY-13@gated-at.bofh.it> <H41jj-2Fcq-3@gated-at.bofh.it> <H4me5-2SpY-13@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


[Multipart message — attachments visible in raw view] - view raw

On Sat, Aug 19, 2023 at 06:46:06AM +0200, Lucas Nussbaum wrote:
> Hi,
> 
> This license change is so disappointing...
> 
> On 18/08/23 at 08:07 -0300, Antonio Terceiro wrote:
> > > Plan B.
> > > 
> > > - Drop vagrant because of that changed licence and no need to
> > >   keep older vagrant.
> > > - No vagrant avaiable in Debian. Just use upstream's package.
> > 
> > I think keeping a stale version of vagrant in the archive is worse than
> > telling people to just use upstream packages.
> 
> A follow-up question, especially in the case of Plan B, is: what do we
> do about Debian Vagrant images provided on Vagrant Cloud
> (https://app.vagrantup.com/debian/) ?
> 
> A/ continue to maintain them. But as the main uploader of those images
>    in the recent times, I might not continue to maintain them, especially
>    if I move to another tool for my own uses, so we might need to look
>    for other volunteers.
> B/ stop maintaining them
>    B.1/ ... and remove existing images from the 'debian' Vagrant Cloud
>    account
>    B.2/ ... and leave the 'debian' Vagrant Cloud account as it is
>    currently
> 
> I don't think B.2 is a good idea.

I agree. Just as we provide cloud images for proprietary platforms, I
think we as a project want to control what is available as "Debian" for
Vagrant users, just like we do with images targetted at proprietary
cloud platforms.

> > Hopefully, being burned a second time will teach me to not put my
> > volunteer time in non-copyleft packages provided by a single
> > corporation.
> 
> Note that the fact that Vagrant was using a non-copyleft license is not
> entirely relevant. The same relicensing could be achieved by
> organizations using a copyleft licence with a copyright transfer
> agreement for external contributions. (I suspect that this is how it was
> achieved for other Hashicorp products, but I haven't checked).

Yes, that's true.

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Bug#1049999: vagrant: the future of packaging vagrant in Debian Kentaro HAYASHI <kenhys@xdump.org> - 2023-08-18 08:40 +0200
  Bug#1049999: vagrant: the future of packaging vagrant in Debian Gwili.Stifter@EasyMailer.live - 2023-08-18 11:40 +0200
    Bug#1049999: vagrant: the future of packaging vagrant in Debian Antonio Terceiro <terceiro@debian.org> - 2023-08-18 13:10 +0200
      Bug#1049999: vagrant: the future of packaging vagrant in Debian Lucas Nussbaum <lucas@debian.org> - 2023-08-19 07:00 +0200
        Bug#1049999: vagrant: the future of packaging vagrant in Debian Antonio Terceiro <terceiro@debian.org> - 2023-08-22 17:10 +0200
      Bug#1049999: vagrant: the future of packaging vagrant in Debian Guillem Jover <guillem@debian.org> - 2023-08-24 02:00 +0200
        Bug#1049999: vagrant: the future of packaging vagrant in Debian Antonio Terceiro <terceiro@debian.org> - 2023-08-24 14:10 +0200
  Bug#1049999: vagrant: the future of packaging vagrant in Debian Gwili.Stifter@EasyMailer.live - 2023-08-18 15:40 +0200

csiph-web