bug-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: problems with daily images


From: Samuel Thibault
Subject: Re: problems with daily images
Date: Sat, 23 Jan 2021 17:32:51 +0100
User-agent: NeoMutt/20170609 (1.8.3)

Paul Dufresne, le sam. 23 janv. 2021 11:13:12 -0500, a ecrit:
> I did found:
> [1]https://buildd.debian.org/status/package.php?p=vim&suite=sid#problem-4
> which seems related to what you said about vim segfaulting during build.

That is it, yes.

> I care that the installation process fail on daily images (maybe for months)
> (in part because of vim).

Yes, but the real answer is that we should fix vim.

> current seems to be the last released version:
> [2]https://www.debian.org/ports/hurd/hurd-news (July 7 2019)

That's only the buster release.


The hurd-cd page
https://www.debian.org/ports/hurd/hurd-cd

points to that release, but also points to the latest published image:
https://cdimage.debian.org/cdimage/ports/latest/hurd-i386/

which did get tested. That page also points to the daily builds, but
tells them as not being tested.

> I don't expect current to be the latest released version.
> 
> Maybe the term I expect is:
> stable: latest released version
> testing: latest build version where "default" installation does not fail.

I don't think we want to use the word "testing", because that would be
confusing with the testing distribution, which this is not about.


More to the point: what pointed you to the daily builds?

In general that's really *not* what webpages, wiki, etc. should point
at, since there is no guarantee that they would work, not only because
of vim, but also because that's the unstable distribution, which keeps
being non-installable.



> Could we modify the installation process to make vim not in the base packages
> until it build again?

I have now dropped it from the explicit list of the daily build, I don't
know if that will be enough.
And again, that will definitely not guarantee installability, since
that's the unstable distribution, it keeps getting broken, that's its
normal state.

Samuel



reply via email to

[Prev in Thread] Current Thread [Next in Thread]