Hi,
I'm not personally familiar with the changes in the latest Debian release, but
please check that all the password, shadow password files etc. are all copied
into the chroot and are self-consistent with one another. Are the host files
using a hash type not supported by the chroot environmen
On 25 Feb 2021, at 12:00, Christoph Biedl
wrote:
>
> Roger Leigh wrote...
>
>> I was having a think about this last night. To be completely
>> realistic, schroot maintenance is very low on my list of my
>> priorities. Work on it is sporadic at best. My interest
On 23 Feb 2021, at 22:51, Johannes Schauer Marin Rodrigues
wrote:
>
> Hi Roger,
>
> Quoting Roger Leigh (2021-02-23 22:41:32)
>> On 22 Feb 2021, at 12:00, Johannes Schauer Marin Rodrigues
>> wrote:
>>>
>>>>> Michael, your change in qe
On 22 Feb 2021, at 12:00, Johannes Schauer Marin Rodrigues
wrote:
>
>>> Michael, your change in qemu introduced this problem. Schroot is currently
>>> orphaned. Since you are responsible for this change in qemu, could you make
>>> an
>>> NMU of schroot with above fix? Thanks!
>>
>> Oww.. orpha
On 27 Jan 2021, at 20:39, David Bremner wrote:
>
> Package: schroot
> Version: 1.6.10-11+b1
> Severity: normal
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> As you can see with session below, schroot throws away the processor
> affinities present in the parent process. This breaks
On 19 Jan 2021, at 15:56, jf...@posteo.net wrote:
>
> I've also seen that I can launch schroot interactively, but that
> (understandably by default) seems to have no access to the host, but it would
> be much more comfortable to mount the host directory where I am debugging the
> package so tha
On 2 Dec 2020, at 08:46, Anthony Fok wrote:
>
> And, sure enough, we can find in /usr/bin/sbuild-debian-developer-setup:
>
>
> https://sources.debian.org/src/sbuild/0.80.0/bin/sbuild-debian-developer-setup/#L56-L57
>
> when it calls sbuild-createchroot, it indiscriminately adds the flags
>
On 05/01/2020 19:54, Steve Langasek wrote:
On Sun, Jan 05, 2020 at 09:16:34AM +, Roger Leigh wrote:
sbuild::chroot::ptr
chroot_zfs_snapshot::clone_source () const
{
ptr clone(new chroot_zfs_snapshot(*this));
...
should be
chroot_zfs_snapshot::clone_source () const
{
ptr clone(new
On 05/01/2020 02:23, Steve Langasek wrote:
Hi Roger,
On Sat, Jan 04, 2020 at 12:54:56PM +, Roger Leigh wrote:
When you clone a source snapshot, we want to make that snapshot the
default
state for the original dataset when you end the session. The "file" chroot
type i
On 04/01/2020 12:54, Roger Leigh wrote:
When you clone a source snapshot, we want to make that snapshot the
default state for the original dataset when you end the session. The
"file" chroot type is the most comparable here; the LVM and Btrfs
snapshots operate directly on the ori
On 03/01/2020 20:44, Steve Langasek wrote:
Package: schroot
Followup-For: Bug #947919
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu focal ubuntu-patch
Attached is an updated patch which implements source chroots as well.
Dear Steve,
I've had a look over the patch, and have a f
On 04/01/2020 08:35, Giovanni Mascellani wrote:
Package: schroot
Version: 1.6.10-7
Severity: important
Hi,
with today's update (1.6.10-7), schroot does not work anymore for
non-root users (which are still authorized by mean of the "users"
directive)
I suspect the problem might be related t
On 07/09/2019 10:30, Simon McVittie wrote:
On Thu, 17 May 2018 at 19:36:11 +0200, Ansgar Burchardt wrote:
On systems with libpam-systemd installed using common-session will
create a logind session which schroot should not do.
In particular, creating a logind session results in $XDG_RUNTIME_DIR
On 12/12/2018 15:25, Aurelien Jarno wrote:
On 2018-12-12 10:06, Helmut Grohne wrote:
Hi Aurelien,
On Sun, Sep 06, 2015 at 07:28:40PM +0200, Aurelien Jarno wrote:
The buildd flavour of the configuration mount a tmpfs in /dev/shm. AFAIK
this is not done for the default flavour as too options
On 15/10/18 19:43, Peter Maydell wrote:
Roger Leigh wrote:
Please see https://gitlab.com/codelibre/schroot/merge_requests/38 for a
patch containing the fixes. This looks like an oversight/mis-design
which is corrected by this merge request to make the behaviour
consistent for all environment
tags 911087 + patch
forwarded 911087 https://gitlab.com/codelibre/schroot/merge_requests/38
thanks
On 15/10/18 15:00, Peter Maydell wrote:
The schroot --preserve-environment is supposed to preserve the
user's environment variables. However it does not pass through
environment variables which ar
the build directory. Unlikely, but possible,
so a potential security problem on the buildd.
Is this possible to fix in ivtools using the -u option to undefine
things as suggested in the FAQ? Given the package-specific nature
of the problem, I feel this would be a more appropriate place for
a fix.
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/
`-GPG Public Key: 0x25BFB848 Please GPG sign your mail.
signature.asc
Description: Digital signature
ners <[EMAIL PROTECTED]>
shadow
Vladimir Shakhov <[EMAIL PROTECTED]>
wdm
Guus Sliepen <[EMAIL PROTECTED]>
rsh-redone
Jonas Smedegaard <[EMAIL PROTECTED]>
libmail-cclient-perl
uw-imap
Roger So <[EMAIL PROTECTED]>
im-sdk
Manoj Srivastava <[EM
x27;s not a great deal of work--I already provided patches for
other packages as examples. Alternatively, given that the upstream
maintainer has abandoned it, it might be better to remove it from the
archive altogether.
Regards,
Roger
--
Roger Leigh
Printing on GNU/Linux? htt
Frank Lichtenheld <[EMAIL PROTECTED]> writes:
> On Tue, Dec 27, 2005 at 07:20:10PM +0000, Roger Leigh wrote:
>> I suggest depending upon w3-el-e21 unconditionally, which would make
>> things robust, even if it's not strictly required in all cases.
>> xemacs
Package: doxymacs
Version: 1.6.0-3
Severity: serious
Justification: Fails to configure due to missing dependencies
Configuration of the package fails:
Setting up doxymacs (1.6.0-3) ...
install/doxymacs: Handling install for emacsen flavor emacs21
Loading 00debian-vars...
Loading 20apel (source)..
e the use of GET_SINGLE_VALUE_ACTION and
+GET_SINGLE_VALUE for bitfield values in structs. The latter
+use the GCC typeof extension, which does not work with bifields.
+
+ -- Roger Leigh <[EMAIL PROTECTED]> Sun, 24 Jul 2005 14:13:33 +0100
+
ftape-tools (1:1.09.2002.03.21-0.3) unstable; urgency=
L)) {
- fprintf(stderr, __FUNCTION__ " %s", _("failed!\n"));
+ fprintf(stderr, "%s %s", __func__, _("failed!\n"));
return -1;
}
trk = 0;
Regards,
Roger
--
Roger Leigh
Printing on GNU/Linux? http://gimp-print.source
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ryan Underwood <[EMAIL PROTECTED]> writes:
> On Thu, Sep 16, 2004 at 10:09:57PM +0100, Roger Leigh wrote:
>>
>> Both Sarge installs are OK. The Sid one is not.
>
> I've not idea why this would be the case. The dose
Ryan Underwood <[EMAIL PROTECTED]> writes:
> On Wed, Sep 15, 2004 at 08:19:03PM +0100, Roger Leigh wrote:
>> On Tue, Sep 07, 2004 at 09:18:45PM +0100, Roger Leigh wrote:
>> >
>> I think I've now got the environment thing working on the work machine,
>&
On Tue, Sep 07, 2004 at 09:18:45PM +0100, Roger Leigh wrote:
>
> Removing the /e:1024 in config.sys makes the failure occur much sooner
> (and then it goes crazy):
[...]
> if "/home/roger" == "" goto nodrived [Enter=Yes, ESC=No]
> lredir d: linux\fs/home/roger
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ryan Underwood <[EMAIL PROTECTED]> writes:
> On Mon, Sep 06, 2004 at 03:25:39PM +0100, Roger Leigh wrote:
>> Package: dosemu
>> Version: 1.2.1-3
>> Severity: normal
>>
>> If I want to import environment varia
Ryan Underwood <[EMAIL PROTECTED]> writes:
> On Mon, Sep 06, 2004 at 03:25:39PM +0100, Roger Leigh wrote:
>> Package: dosemu
>> Version: 1.2.1-3
>> Severity: normal
>>
>> If I want to import environment variables from the Linux environment
>> into the
Package: dosemu
Version: 1.2.1-3
Severity: normal
If I want to import environment variables from the Linux environment
into the dosemu session using "unix -s varname", only variables without
an underscore are imported.
My /etc/freedos/autoexec.bat
@echo off
[snip lredired standard setup]
share
u
p; COM4
If I set
$_com1 = "/dev/ttyS0"
$_com2 = "/dev/ttyS1"
$_com3 = "/dev/ttyS2"
$_com4 = "/dev/ttyS3"
then the error goes away. If I don't source global.conf with -F, then I
don't get the error either. Does the global.conf not match t
Package: dosemu
Version: 1.2.1.0
Severity: normal
I'm using dosemu-1.2.1.0 together with freedos.
Now I have dosemu correctly configured (and running like a charm!) I'd
like to disable the startup dos banner, since I generally run commands
from the bash shell (e.g. "dosemu myprog") and the startu
31 matches
Mail list logo
