Quoting Simon McVittie (2022-04-29 10:58:34)
> On Fri, 29 Apr 2022 at 08:34:48 +0100, Julian Gilbey wrote:
> > So can I suggest that
> > sbuild-setup(7) explains this a bit more and discusses setting up a
> > meaningful HOME directory?
>
> I'm sure patches are accepted, but the problem with this
On Fri, 29 Apr 2022 at 08:34:48 +0100, Julian Gilbey wrote:
> So can I suggest that
> sbuild-setup(7) explains this a bit more and discusses setting up a
> meaningful HOME directory?
I'm sure patches are accepted, but the problem with this is that what you
want for sbuild does not match what you
On Fri, 29 Apr 2022 at 10:43:40 +0800, Paul Wise wrote:
> Does that mean that autopkgtests that directly or indirectly use the
> dbus-run-session tool to setup a temporary D-Bus session are buggy?
There's no single answer to that. For unit-test-style testing, it's
often more convenient to start a
On Thu, Apr 28, 2022 at 02:32:49PM +0100, Simon McVittie wrote:
> > That's interesting; I don't find any code that sets HOME in
> > autopkgtest.
>
> The purpose of autopkgtest is to run the tests in a realistic environment
> that resembles a real Debian desktop or server, but it doesn't know much
On Thu, Apr 28, 2022 at 02:32:49PM +0100, Simon McVittie wrote:
> On Thu, 28 Apr 2022 at 14:02:46 +0100, Julian Gilbey wrote:
> > On Thu, Apr 28, 2022 at 10:16:30AM +0100, Simon McVittie wrote:
> > > According to the autopkgtest spec[1],
> > >
> > > Tests can expect that the $HOME environment
On Thu, 2022-04-28 at 14:32 +0100, Simon McVittie wrote:
> Making the test script set up a mock XDG_RUNTIME_DIR and a mock
> session bus would be a less useful test, because that only proves that
> gnome-keyring can work if you set up a mock environment by hand, and says
> nothing about whether
On Thu, 28 Apr 2022 at 14:02:46 +0100, Julian Gilbey wrote:
> On Thu, Apr 28, 2022 at 10:16:30AM +0100, Simon McVittie wrote:
> > According to the autopkgtest spec[1],
> >
> > Tests can expect that the $HOME environment variable to be set to
> > a directory that exists and is writeable by
Thanks Paul and Simon for your very thoughtful and helpful replies!
Comments on excerpted text below.
On Thu, Apr 28, 2022 at 10:16:30AM +0100, Simon McVittie wrote:
> On Thu, 28 Apr 2022 at 08:33:02 +0100, Julian Gilbey wrote:
> > When I run autopkgtest using sbuild on my own machine, I
On Thu, 28 Apr 2022 at 08:33:02 +0100, Julian Gilbey wrote:
> When I run autopkgtest using sbuild on my own machine, I sometimes get
> warnings or breakages because certain environment variables are either
> unset or have "broken" values, whereas I see that on ci.debian.net and
> the buildds, the
Hi Julian,
On 28-04-2022 09:33, Julian Gilbey wrote:
It would be really useful to be able to set up my local sbuild
environment in the same way as the Debian machines (buildd and
ci.debian.net) for testing purposes.
As I've never used sbuild myself, I can't tell you how to set it up. But
on
When I run autopkgtest using sbuild on my own machine, I sometimes get
warnings or breakages because certain environment variables are either
unset or have "broken" values, whereas I see that on ci.debian.net and
the buildds, the builds run without problem.
So clearly there are certain
11 matches
Mail list logo
