Feel free to mark this as a duplicate of
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675512
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: schroot
Version: 1.6.5
Severity: wishlist
I have a user who would like to create an lvm snapshot session and then
share it with another user. Currently only the root user can access
other user's sessions.
It would be helpful if a non-root user could run a command to grant a
second non-r
> Thanks for the diff. I'm not sure where the different tarballs
> have originated from--maybe one was a prerelease test tarball?
Thanks Roger. Do you have any ideas on the proper way to resolve the
unit test failures I'm seeing with the official tarball?
-Zach
--
To UNSUBSCRIBE, email to
Package: schroot
Version: 1.4.23
The gcc compiler in the Fedora distribution has recently been updated to
gcc 4.7, at which point schroot failed to build.
Official build results can be seen here:
http://koji.fedoraproject.org/koji/taskinfo?taskID=3668529
Specifically, the compile err
On Thursday, February 10, 2011 05:10:06 am Roger Leigh wrote:
> OK, it proved not to require a configure check, just a conditional to
> check the provided filesystem version. Could you try the attached
> patch and see if it builds correctly for you?
Verified, it applies and builds fine with boost
On Tuesday, February 08, 2011 02:49:01 pm Roger Leigh wrote:
> > sbuild-chroot-config.cc: In member function 'void
> > sbuild::chroot_config::add_config_directory(const string&, const
> > string&)': sbuild-chroot-config.cc:170:49: error: no matching function
> > for call to
> > 'std::basic_string:
On Tuesday, February 08, 2011 02:17:12 pm Roger Leigh wrote:
> The provided patch doesn't build with Boost 1.42, and I'd like to
> have backward compatibility if possible. The final .string() is
> not required to build with 1.42, and this might also be the case
> with 1.64. Please could you let
Package: schroot
Version: 1.4.19
When I build schroot with boost 1.46, I get this error:
sbuild-chroot-config.cc: In member function 'void
sbuild::chroot_config::add_config_directory(const string&, const string&)':
sbuild-chroot-config.cc:170:32: error: 'class
boost::filesystem3::directory_entr
On Sunday 05 December 2010 13:25:57 Roger Leigh wrote:
> Can anyone see any downside from being this permissive, or any
> security implication I've not seen? (I'm only looking at pathname-
> based security exploits here--is there anything else we need to
> worry about?)
Like lvm, it might be wise
Package: schroot
Version: 1.4.8
When I create a persistent schroot session, and I do not specify the priority,
the default priority is set to 0. Later on when I access the session, I get
multiple warnings about using a deprecated key.
Example, a simple chroot, with no priority defined:
[cat
On Saturday 07 August 2010 02:43:13 Roger Leigh wrote:
> I just need to work out how to disable boost::regex::collate; is there
> an inverse of that option? Since it's enabled by default for
> extended regexes, I'm not sure how to turn this off.
indeed, from the faq:
"[Note - when regex_constant
On Saturday 07 August 2010 02:43:13 Roger Leigh wrote:
> > Just some additional background info. When I was troubleshooting this
> > issue I noticed some inconsistent behavior in the boost regex
> > logic. Some of my session names were allowed, and some were not, and I
> > was banging my head ag
On Thursday 22 July 2010 02:04:52 Roger Leigh wrote:
> Agreed on all counts and the patch looks great. I'll review it in
> more detail when I have time at the weekend and make a new release
> then.
Cool! thanks.
Just some additional background info. When I was troubleshooting this issue I
not
Package: schroot
Version: 1.4.7
Severity: important
schroot allows me to create a persistent session with a particular name, such
as "zcarter-catalan-build-cb67j4yZoS-16646".
However, when I attempt to access it later on, it fails like this:
$ /usr/bin/schroot -p -v -r -c zcarter-catalan-bu
Package: schroot
Version: 1.4.2
In the fedora build system, the ./configure process fails with this error:
configure: error: libboost_program_options (Boost C++ Libraries) is not
installed, but is required by schroot
It doesn't seem to fail on my local build machine, but it does in the
Package: schroot
Version: 1.2.3
Severity: normal
When a non-root user is accessing an lvm snapshot chroot, the call to lockdev
is made with insufficient permissions, resulting in this error:
E: test-f13-401b1c48-570f-48bb-8389-4b6d44f18577: Failed to lock chroot:
/dev/fastvg/f13lv: Failed to lo
Package: schroot
Version: 1.4.2
Severity: normal
When compiled without uuid support, schroot creates chroot names that include
colon characters in them. When creating a snapshot based on those names, the
lvcreate command fails like this:
E: 05lvm: Logical volume name "f12-2010-05-27T20:35:13
I am using these packages:
# gcc 3
gcc-3.4.6-9
libgcc-3.4.6-9
gcc-c++-3.4.6-9
# also tried gcc 4
gcc4-4.1.2-14.EL4
gcc4-c++-4.1.2-14.EL4
make-3.80-6.EL4
pam-devel-0.77-66.23
boost-devel-1.32.0-6.rhel4
lockdev-devel-1.0.1-6.2
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "
Package: schroot
Version: 1.1.6
Severity: normal
When using the -p option, schroot exits with this error: E: Empty expression
[EMAIL PROTECTED] ~]$ schroot -c bering -- uname -a
I: [bering-2008-07-19T04:58:47Z-13217 chroot] Running command: “uname -a”
Linux nerf 2.4.21-47.0.1.EL #1 Thu Oct 19 11
19 matches
Mail list logo
