On Thu, Dec 2, 2010 at 14:02:27 +0100, Alexander Reichle-Schmehl wrote:
> I fail to reproduce this bug. I tried current sid and current squeeze
> (which actually means: The very same versions you tried), using apt-get
> as well als aptitude. It always got installed and set up without any
> err
Hi!
On 02/12/2010 14:31, Alexander Reichle-Schmehl wrote:
Hi!
Am 02.12.2010 14:21, schrieb Mehdi Dogguy:
Given that the maintainer is not responding, that the package is
not present in Lenny and that it has two RC bugs... maybe it's
better to just not ship it in Squeeze?
Also note that it's
Hi!
Am 02.12.2010 14:21, schrieb Mehdi Dogguy:
>> Can you reproduce this error?
> I just tried and it fails (on my testing box):
[..]
Thanks.
> but it doesn't fail in a clean sid chroot.
Ah, makes it quite hard to debug. I just tried it on some of my real
machines, and can reproduce it on one
On 02/12/2010 14:02, Alexander Reichle-Schmehl wrote:
Hi!
* Lucas Nussbaum [101121 11:07]:
While testing the installation of all packages in unstable, I ran
into the following problem:
Setting up mercurial-common (1.6.4-1) ...
Setting up mercurial (1.6.4-1) ...
[..]
Setting up mercurial-
Hi!
* Lucas Nussbaum [101121 11:07]:
> While testing the installation of all packages in unstable, I ran
> into the following problem:
> > Setting up mercurial-common (1.6.4-1) ...
> > Setting up mercurial (1.6.4-1) ...
[..]
> > Setting up mercurial-server (1.0.1-1.1) ...
> > abort: couldn't fi
Package: mercurial-server
Version: 1.0.1-1.1
Severity: serious
User: debian...@lists.debian.org
Usertags: instest-20101120 instest
Hi,
While testing the installation of all packages in unstable, I ran
into the following problem:
> Reading package lists...
> Building dependency tree...
> Reading
6 matches
Mail list logo
