I don't remember where I got it from. Probably from the last time this sort of
thing happened (only the current episodes have been much worse).
I can't think of a stronger case for using an alias than the present situation,
where using the wrong machine can corrupt the repository. Where several
On Wed, 2 Jan 2013, Lawrence Paulson wrote:
I have been using
hgbroy.informatik.tu-muenchen.de
under the assumption that the name hgbroy could be expected to refer to
a suitable machine.
From where did you get that? hgbroy seems to be an alias of the old
cvsbroy, and probably refe
I have been using
hgbroy.informatik.tu-muenchen.de
under the assumption that the name hgbroy could be expected to refer to a
suitable machine.
Can I continue to do that?
Larry
On 1 Jan 2013, at 21:52, Makarius wrote:
> Thanks again for picking up the bright weapons of empirical scie
On Tue, 25 Dec 2012, Alexander Krauss wrote:
On 12/20/2012 06:22 PM, Makarius wrote:
> I just had a long phone call with Franz Huber, the local system admin
> person. All the macbroy20..29 and lxlabbroyX machines involved here
> use the same OpenSuse 12.2 with that hg 2.4. So just empiricall
A very impressive analysis. Thanks.
Larry
On 25 Dec 2012, at 10:38, Alexander Krauss wrote:
> I would say that this points to the SUSE NFS client driver as the source of
> the problem. If we use lxbroy10 exclusively for pushes, we should be safe
> until the issue is fixed.
___
Thanks a lot for that thorough analysis!
Florian
--
PGP available:
http://home.informatik.tu-muenchen.de/haftmann/pgp/florian_haftmann_at_informatik_tu_muenchen_de
signature.asc
Description: OpenPGP digital signature
___
isabelle-dev mailin
On 12/20/2012 06:22 PM, Makarius wrote:
I just had a long phone call with Franz Huber, the local system admin
person. All the macbroy20..29 and lxlabbroyX machines involved here
use the same OpenSuse 12.2 with that hg 2.4. So just empirically that
looks like the problem -- breakdowns started appr
On Fri, 21 Dec 2012, Jasmin Christian Blanchette wrote:
Am 20.12.2012 um 21:30 schrieb Alexander Krauss:
On 12/20/2012 12:20 AM, Alexander Krauss wrote:
(2) The local sysadmins are working on replacement of the Mercurial
2.4 from SuSE 12.2, which is potentially the cause problems here.
Rep
Agree.
Larry
On 21 Dec 2012, at 12:43, Jasmin Christian Blanchette
wrote:
> Skipping a version can be a good solution in the long run. If the bug is in
> Mercurial, then chances are that other people will start reporting similar
> bugs to the Mercurial mailing list, that the maintainers will
Am 20.12.2012 um 21:30 schrieb Alexander Krauss:
> On 12/20/2012 12:20 AM, Alexander Krauss wrote:
>
>> (2) The local sysadmins are working on replacement of the Mercurial
>> 2.4 from SuSE 12.2, which is potentially the cause problems here.
>
> Replacement with what? Going to an older version is
On Thu, 20 Dec 2012, Alexander Krauss wrote:
On 12/20/2012 12:20 AM, Alexander Krauss wrote:
I am now writing this up for the hg mailing list, since we now may
have enough information to get help tracking it down...
I posted a question here:
http://www.selenic.com/pipermail/mercurial/2012-Dec
On Thu, 20 Dec 2012, Alexander Krauss wrote:
(2) The local sysadmins are working on replacement of the Mercurial
2.4 from SuSE 12.2, which is potentially the cause problems here.
Replacement with what? Going to an older version is no solution in the
long run. The changes between 2.4 and 2.4.1
ascha
Von: Christian Sternagel
Gesendet: 21.12.2012 04:08
An: isabelle-dev
Betreff: [isabelle-dev] Repository trouble
Dear all,
just now, when I tried
hg in
in the development repo, I got the error below. My mercurial versi
I'm looking intro it.
Dmitriy
On 21.12.2012 04:07, Christian Sternagel wrote:
Dear all,
just now, when I tried
hg in
in the development repo, I got the error below. My mercurial version
is 2.2.3 (for at least some weeks). Did anybody else experience
similar problems?
cheers
chris
com
Hi,
It could have been caused by my commit last night. I am not sure what I did
wrong, though.
Cheers,
Sascha
- Ursprüngliche Nachricht -
Von: Christian Sternagel
Gesendet: 21.12.2012 04:08
An: isabelle-dev
Betreff: [isabelle-dev] Repository trouble
Dear all,
just now, when I tried
Dear all,
just now, when I tried
hg in
in the development repo, I got the error below. My mercurial version is
2.2.3 (for at least some weeks). Did anybody else experience similar
problems?
cheers
chris
comparing with http://isabelle.in.tum.de/repos/isabelle
searching for changes
change
On 12/20/2012 12:20 AM, Alexander Krauss wrote:
I am now writing this up for the hg mailing list, since we now may
have enough information to get help tracking it down...
I posted a question here:
http://www.selenic.com/pipermail/mercurial/2012-December/044783.html
and there are some answers,
On Thu, 20 Dec 2012, Makarius wrote:
I just had a long phone call with Franz Huber, the local system admin
person. All the macbroy20..29 and lxlabbroyX machines involved here use
the same OpenSuse 12.2 with that hg 2.4. So just empirically that looks
like the problem -- breakdowns started app
On Thu, 20 Dec 2012, Alexander Krauss wrote:
On 12/19/2012 11:34 PM, Alexander Krauss wrote:
On 12/11/2012 10:56 AM, Johannes Hölzl wrote:
Am Montag, den 10.12.2012, 15:27 +0100 schrieb Makarius:
On Tue, 27 Nov 2012, Johannes Hölzl wrote:
We had again a problem with the repository. We fixed
On 12/19/2012 11:34 PM, Alexander Krauss wrote:
On 12/11/2012 10:56 AM, Johannes Hölzl wrote:
Am Montag, den 10.12.2012, 15:27 +0100 schrieb Makarius:
On Tue, 27 Nov 2012, Johannes Hölzl wrote:
We had again a problem with the repository. We fixed it by using again
We're there again. The mai
On 12/11/2012 10:56 AM, Johannes Hölzl wrote:
Am Montag, den 10.12.2012, 15:27 +0100 schrieb Makarius:
On Tue, 27 Nov 2012, Johannes Hölzl wrote:
We had again a problem with the repository. We fixed it by using again
We're there again. The main repos is broken. Will try to fix and report
ba
Am Montag, den 10.12.2012, 15:27 +0100 schrieb Makarius:
> On Tue, 27 Nov 2012, Johannes Hölzl wrote:
>
> > We had again a problem with the repository. We fixed it by using again
> >
> > hg verify
> > hg strip
> >
> > now it works again (at least on my machine and on the web server)
> >
> > I u
On Tue, 27 Nov 2012, Johannes Hölzl wrote:
We had again a problem with the repository. We fixed it by using again
hg verify
hg strip
now it works again (at least on my machine and on the web server)
I used Mercurial 2.0.2 (installed with Ubuntu 12.04).
I updated now to Mercurial 2.4 and ho
We had again a problem with the repository. We fixed it by using again
hg verify
hg strip
now it works again (at least on my machine and on the web server)
I used Mercurial 2.0.2 (installed with Ubuntu 12.04).
I updated now to Mercurial 2.4 and hope that it does not happen again.
Sorry for
On 09/06/2012 01:48 AM, Alexander Krauss wrote:
This seems to be happening regularly now, which is really very annoying.
The testboard is not the main repository; so far the problem did not
occur again on the latter. I am still hoping that the main repository is
clean.
Unfortunately, the sam
On 08/16/2012 11:03 PM, Makarius wrote:
It could be an NFS corruption of the repository, or just the server
feeling too hot. I've no real idea.
This seems to be happening regularly now, which is really very annoying.
The testboard is not the main repository; so far the problem did not
occur
On Sun, 12 Aug 2012, Alexander Krauss wrote:
On 08/12/2012 06:50 PM, Makarius wrote:
I am just waiting for Alex (or anybody else who might potentially apply
some administrative operations to the bare metal repository) to confirm
that we are ready for the exchange.
Do go ahead! I have a copy o
On 08/12/2012 06:50 PM, Makarius wrote:
I am just waiting for Alex (or anybody else who might potentially apply
some administrative operations to the bare metal repository) to confirm
that we are ready for the exchange.
Do go ahead! I have a copy of the old clone, but it does not tell me
much
On Sun, 12 Aug 2012, Makarius wrote:
Since we have had 2-3 incidents recently, it is time now to make a fresh
clone using a recent version of Mercurial (not the 1.0 we've had in
2008). I have already recovered most of the meta-information that is
required for this (Unix permissions etc.).
Th
On Sun, 12 Aug 2012, Alexander Krauss wrote:
It seems that the main Isabelle repository got corrupted again and is
currently unavailable.
OK, it's back for now...
Since we have had 2-3 incidents recently, it is time now to make a fresh
clone using a recent version of Mercurial (not the 1.0
It seems that the main Isabelle repository got corrupted again and is
currently unavailable.
OK, it's back for now...
Alex
___
isabelle-dev mailing list
isabelle-...@in.tum.de
https://mailmanbroy.informatik.tu-muenchen.de/mailman/listinfo/isabelle-dev
Hi all,
It seems that the main Isabelle repository got corrupted again and is
currently unavailable.
Since the error seems to be the same as last time, I expect to be able
to fix it quickly. Apparently, the error is correlated with me pushing
some changes in, so I guess I'll have to try to r
32 matches
Mail list logo
