Processed: closing 958430

2020-04-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> close 958430
Bug #958430 [cloud.debian.org] Vagrant libvirt image debian/buster64 version 
10.3.0 grub error
Marked Bug as done
> # error on user side, the libvirt box is fine.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
958430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958430
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Processed: tagging 958430

2020-04-22 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org:

> tags 958430 + unreproducible
Bug #958430 [cloud.debian.org] Vagrant libvirt image debian/buster64 version 
10.3.0 grub error
Added tag(s) unreproducible.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
958430: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958430
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems



Re: Presenting Debian to the user at cloud provider marketplaces (round 2)

2020-04-22 Thread Bastian Blank
On Mon, Apr 20, 2020 at 07:57:19PM -0400, Noah Meyerhans wrote:
> Product title: For older releases, the title is listed as (e.g.) "Debian
> GNU/Linux 9 (Stretch)".  For buster, it is "Debian 10 Buster".  I prefer
> the formating used for stretch, and would like to update buster to
> match.

What do you mean with "formating"?  "GNU/Linux" is now irrelevant.
"Debian Linux", maybe, but redundant.

> I'm open to the idea of listing only the version number, and
> dropping the code name, but don't feel strongly either way.  Opinions?

Well.  People search for both?

>  Is there existing text that
> would work better here?

Sadly, no.

I looked at other distributions on Azure and found for example:
https://azuremarketplace.microsoft.com/en-us/marketplace/apps/canonical.ubuntuserver

>  Buster is only "The universal operating system."  I
> think pulling some snippets in from the release notes makes sense for
> buster. Agree?

Should this be highlights of the release?  Hightlights of the software?
I don't know.

> The AWS Marketplace requires some text for a "EULA".  Currently we link
> to the Social Contract for that, but that's not at all written like a
> EULA and doesn't specifically discuss legal rights or restrictions.
> IMO, as suggested in #696596 [4], we should replace the EULA text with
> something similar to what's in the default MOTD.  Thoughts?

We need something on our website.  This is also relevant for Azure.

> Support information: The stretch listing says "Debian is developed and
> supported by a diverse global community. It can be reached through a
> variety of means including email, IRC, and web forums." and links to
> www.debian.org/support.  Buster indicates that "No Support is offered
> for this product"  I'd like to make buster match the stretch listing.

Ah, this is a freetext field.  Feel free.

Regards,
Bastian

-- 
I've already got a female to worry about.  Her name is the Enterprise.
-- Kirk, "The Corbomite Maneuver", stardate 1514.0



Bug#958430: (no subject)

2020-04-22 Thread Manu Ka
Thank you for your interest in the vagrant boxes.

A fresh vagrant env with libvirt and 10.3 works for me (see:
http://paste.debian.net/1142057/)

Can you reproduce the problem in a fresh environment ?

ie erase your current box and create a new vagrant env

vagrant box remove debian/buster64
vagrant init debian/buster64
vagrant up --provider=libvirt

and post here the commands output.

-- 
/*
parttimelog.wordpress.com
Part time pictures
*/