Re: [buildd-tools-devel] Bug#608428: Bug#608428: schroot: [kfreebsd-*] cannot handle long (= 14 chars) chroot names

2011-01-01 Thread Roger Leigh
reassign 608428 freebsd-utils severity 608428 serious thanks On Thu, Dec 30, 2010 at 10:18:27PM +, Roger Leigh wrote: On Thu, Dec 30, 2010 at 09:06:28PM +0100, Jakub Wilk wrote: Hi Jakub, On kfreebsd-*, schroot is not able to unmount everything if chroot name is longer than 13

Processed: Re: [buildd-tools-devel] Bug#608428: Bug#608428: schroot: [kfreebsd-*] cannot handle long (= 14 chars) chroot names

2011-01-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: reassign 608428 freebsd-utils Bug #608428 [schroot] schroot: [kfreebsd-*] cannot handle long (= 14 chars) chroot names Bug reassigned from package 'schroot' to 'freebsd-utils'. Bug No longer marked as found in versions schroot/1.4.16-1. severity

Processed: your mail

2011-01-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: retitle 608428 freebsd-utils: mount/umount have 80/85 character path limit breaking mounting Bug #608428 [freebsd-utils] schroot: [kfreebsd-*] cannot handle long (= 14 chars) chroot names Changed Bug title to 'freebsd-utils: mount/umount have

Re: Bug #608428: freebsd-utils: mount/umount have 80/85 character path limit breaking mounting

2011-01-01 Thread Roger Leigh
forwarded 608428 http://www.freebsd.org/cgi/query-pr.cgi?pr=153600 thanks This is also reproducible on vanilla FreeBSD (I tested 8.2-RC1), though the 80-84 character behaviour is absent (only breaks after 85 characters). The test was done using the following shell script. #!/bin/sh chrs=0 1 2

Bug#608428: [buildd-tools-devel] Bug#608428: Bug#608428: schroot: [kfreebsd-*] cannot handle long (= 14 chars) chroot names

2011-01-01 Thread Petr Salinger
severity 608428 important user debian-bsd@lists.debian.org usertag 608428 + kfreebsd -- So, this looks like a bug in the mount/umount utilities and/or the kfreebsd mount/nmount/umount system calls. Possible explanation: there's an 80 char buffer being used which causes the truncation. The

Processed: Re: [buildd-tools-devel] Bug#608428: Bug#608428: schroot: [kfreebsd-*] cannot handle long (= 14 chars) chroot names

2011-01-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: severity 608428 important Bug #608428 [freebsd-utils] freebsd-utils: mount/umount have 80/85 character path limit breaking mounting Severity set to 'important' from 'serious' user debian-bsd@lists.debian.org Setting user to

Processed: Re: Bug #608428: freebsd-utils: mount/umount have 80/85 character path limit breaking mounting

2011-01-01 Thread Debian Bug Tracking System
Processing commands for cont...@bugs.debian.org: forwarded 608428 http://www.freebsd.org/cgi/query-pr.cgi?pr=153600 Bug #608428 [freebsd-utils] freebsd-utils: mount/umount have 80/85 character path limit breaking mounting Set Bug forwarded-to-address to

Bug#608428: [buildd-tools-devel] Bug#608428: Bug#608428: schroot: [kfreebsd-*] cannot handle long (= 14 chars) chroot names

2011-01-01 Thread Roger Leigh
On Sat, Jan 01, 2011 at 07:11:41PM +0100, Petr Salinger wrote: severity 608428 important user debian-bsd@lists.debian.org usertag 608428 + kfreebsd -- So, this looks like a bug in the mount/umount utilities and/or the kfreebsd mount/nmount/umount system calls. Possible explanation: