Re: [Monotone-devel] monotone botan-stable AUR
To be fair I didn't really investigate as I was distracted by other things at the time, it could have been a binary incompatibility only. On 29 January 2017 19:13:44 GMT+00:00, Markus Wannerwrote: >Hi, > >On 29.01.2017 09:46, CooSoft Support wrote: >> Oh it's more serious then. For sometime monotone hasn't work with the >> version of Botan that ships with Ubuntu 14.04, I had to regress the >> botan version back to get it to work. > >that surprises me and doesn't quite match the dates I have in mind. > >Current monotone releases (certainly 1.0 and 1.1) are compatible with >botan 1.8 and 1.10. > >Botan 2.0 was released just a few days ago (Friday, 13th, to be >precise) >and certainly isn't part of Ubuntu 14.04 (or any Ubuntu or Debian >release, yet). > >If you have a specific issue with monotone 14.04, please file a >specific >bug report. Otherwise I'd assume monotone to work just fine on Ubunut >14.04. (And yes, I have used monotone on *that* Ubuntu release.) > >Kind Regards > >Markus Wanner -- See www.coosoft.plus.com.___ Monotone-devel mailing list Monotone-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] monotone-viz problem
On 24 June 2016 23:04:38 BST, Hendrik Boom <hend...@topoi.pooq.com> wrote: >On Fri, Jun 24, 2016 at 10:50:56PM +0100, Anthony Edward Cooper wrote: >> Yes the dot format does change and get tweaked/updated. It has >> probably changed too much for the aging monotone-viz. Is monotone-vis > >> still maintained? It's written in Occaml and as such I don't think it > >> has been touched for years and is probably not maintained at all now. > >Ocaml does not scare me. Then you could update monotone-viz... > >> I'm being completely biased but mtn-browse also does graph >visualization like monotone-viz and much more besides. You could give >that a go... > >I neither was aware that mtn-browse existed, nor know where to find >it. You can find it under GUI tools on the main monotone site and more specifically: https://sourceforge.net/projects/mtn-browse/ > >It does not appear to be in the Debian repositories, I wrote mtn-browse but haven't got involved in the packaging. There's only so much free time... Others have fine excellent work on packaging it for redhat, but that doesn't help you. One can easily install mtn-browse under /opt and the installer will highlight missing dependencies. and googling it >provides me with methods to cheat MTN (whatever that is) to browse for >free. Yes I've noticed that as well... > >What *is* the dot output, anyway? Dot is a part of graphviz and as such is a layout processor, given a list of geometric shapes and their links, it will generate an optimized graph layout. Both monotone-viz and mtn-browse use it the generate the graphs. > >-- hendrik > >> >> Tony. >> >> On 23 June 2016 23:58:45 BST, Hendrik Boom <hend...@topoi.pooq.com> >wrote: >> >On my devuan jessie system, when I start monotone-viz, it always >pops >> >up a message, >> > >> >Could not parse dot output >> > >> >Is there some subtle version copatibility problem here? Or some >thing >> >weirder? >> > >> >hendrik@notlookedfor:~/dv/im/slides$ mtn --version >> >monotone 1.1 (base revision: >81fa9664405655b13bde971bddd802de25096073) >> >hendrik@notlookedfor:~/dv/im/slides$ monotone-viz --version >> >monotone-viz 1.0.2 (base revision: ) >> >Copyright (C) 2004-2006 Olivier Andrieu <oandr...@gmail.com> >> >hendrik@notlookedfor:~/dv/im/slides$ >> > >> >-- hendrik >> > >> > >> >___ >> >Monotone-devel mailing list >> >Monotone-devel@nongnu.org >> >https://lists.nongnu.org/mailman/listinfo/monotone-devel >> >> -- >> See www.coosoft.plus.com. -- See www.coosoft.plus.com. ___ Monotone-devel mailing list Monotone-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] Mtn-Browse Version 1.20 And AutomateStdio 1.10
On 09/05/16 20:42, Markus Wanner wrote: On 05/08/2016 01:57 PM, Anthony Edward Cooper wrote: Just a quick announcement to say that new versions of mtn-browse and AutomateStdio have been released. Cool, thanks for the heads up. The latter now provides support for Monotone version 1.10 I think you rather mean version 1.1. Out of interest: what changes were necessary to support 1.1 (versus 1.0)? Are I'd assumed that since historically the versions were to 2 decimal places that was a truncated 1.10 rather than 1.01 etc. Anyway yes I'm referring to the latest official 1.1 release :-). The changes for AutomateStdio centred around erase_descendants() and the extra rev arg to get_attributes(). Mtn-Browse's changes were simply the inclusion of the min() and not() selector functions. The main work in mtn-browse was fixing breakage introduced by Ubuntu/later Linux versions etc. I'll have to give it a spin on the latest Ubuntu LTS that has just come out (tested on 14.04 KDE 4.x and Unity as well as Debian 6 and RHEL 4). Cheers, Tony. Kind Regards Markus Wanner -- "Always forgive your enemies - nothing annoys them so much." Oscar Wilde. Pay a visit to my home pages at: http://www.coosoft.plus.com/ http://coosoft.wordpress.com/ ___ Monotone-devel mailing list Monotone-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Mtn-Browse Version 1.20 And AutomateStdio 1.10
Just a quick announcement to say that new versions of mtn-browse and AutomateStdio have been released. The latter now provides support for Monotone version 1.10 and the former, in addition, has fixes in it for running on later Linuxs and KDE 4.x. Cheers, Tony Cooper. ___ Monotone-devel mailing list Monotone-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Mtn-Browse
Just a short email to announce the 1.00 release of mtn-browse. Main improvements include a history graphing tool and new and improved combo-box entries fields. For more details please go to: http://www.coosoft.plus.com/software.html Please download from: http://sourceforge.net/projects/mtn-browse/ This application is supported for Linux, Mac OSX, and most Unixes. Regards, Tony Cooper. ___ Monotone-devel mailing list Monotone-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Monotone::AutomateStdio Perl Library
I'm please to announce that version 1.01 of the Perl Monotone::AutomateStdio is now available for download at CPAN. As you would expect this supports Monotone version 1.00 and previous versions as far back as 0.35. Regards, Tony. ___ Monotone-devel mailing list Monotone-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] New BETA RC 1 Version Of Mtn-Browse
Hello All, If you don't use Mtn-Browse or have no intention of doing so ordinarily then please delete... I'm looking for any mtn-browse users to volunteer to give this new version of Mtn-Browse a go and see how they get on. I have tested it on RH4.3 Debian 5 6. If you are a translator or package maintainer then please do not do either for this tar ball as it won't be released. All being well a release will will come shortly. The main change in this version is a new history graphing tool integrated into mtn-browse. The code should be production quality, at least that is my intent. The only reason this is at beta (is one allowed a beta release candidate? :-)) is because as yet there is no help for this graphing tool. This tool now has a dependency on Gnomes Canvas widget. If you have used monotone-viz then you'll have the library, but you may still need the Perl binding. Your distro or CPAN will be able to provide that for you. Usage: As before but the monotone-viz button now calls up the new graphing window. There are tooltips that will hopefully help and a right click menu. Boxes with grey borders are unselected but have been included for clarity (propagate nodes). Blue borders signify that the revision is on a suspended branch. Double clicking on a box with a grey border will graph that branch for you. Things To Test: Have a play and see how you get on :-). One particular thing I would like you to test is how reliably text is drawn on the graph. The version that runs by default should have no problems. However it is not particularly fast. There is another version that uses Gtk2::Labels widgets that runs a whole lot faster. To use this simply go to the lib/perl directory and rename the HistoryGraph-With-Labels.pm file to HistoryGraph.pm. Using labels is much faster but on some platforms (Debian 5) it doesn't really work. You need a really long history (but simple) and one can be found in mtn-browse's test branch in it's database: https://code.monotone.ca/p/mtn-browse/source/tree/h:net.venge.monotone.contrib.mtn-browse.test.long-graph/ If it works then all boxes should have text in the, when you graph it. If this is a bit much to ask then just have a play and see how you get on. If you do do the above test then please let me know how you got on and which OS you were using. mtn-browse runs on Linux and other assorted Unixes and Mac OSX. Richard - could you please test to see if your branch names with / characters issue has been fixed please. Thomas K - Could you give it a spin on OSX please... The tar ball can be got from here: http://www.coosoft.plus.com/downloads/mtn-browse-1.00-Beta-RC1.tgz MANY thanks in advance. Tony. ___ Monotone-devel mailing list Monotone-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] New BETA RC 1 Version Of Mtn-Browse
Hia Thomas :-), Many thanks for giving this a spin. Ok the easy stuff first. As for an option to specify a custom dot. Do you mean a preference option? I only did that for the comparison program as there are a lot to choose from and people are bound to want to use different ones (not only settable on installation but via user preferences as well). However, no so with dot. I am happy with hardwiring a path via the installer. Also if someone is using a custom version then they can always write a wrapper script to amend the path before running it (if they are running with custom versions of software then a wrapper script is something they would get used to writing :-)). I can think of lots of other apps that do this. Now the hard bit. The rendering. Performance: The slow bits are getting the revision information from mtn (predictable and not too bad), dot going mental because of a large graph and using the canvas to draw text. From what you say this is the thing slowing you down. Render issue. I have just tried dot version 2.28 (graphviz_2.28.0-1_i386.deb) just before writing this email. It works perfectly on Deb5. From the pic you sent it seems to be putting stuff in the right place but it looks like dot is not giving any height/diameter to the merge nodes and rectangles. My reasoning is as follows. The canvas is capable of drawng rectangles with a width and height as shown by the selected node (red blob). Yet the arrows and my selection box are all drawn as if the nodes are of zero height (think black lines through the text). If I had failed to say read in the size of the nodes then the arrows would still be drawn leaving a gap for the nodes. Weird one. I take it that monotone-viz works fine with that version of dot. Anyway I have attached a perl script that I used to interpose and capture dot's output. Could you please edit it to point to your version of dot and then make sure that it is run instead of your real dot. Graph something out of the monotone.mtn database that I can refer to and then email me the output. I'll have a look at it. Many thanks once again. Tony. Thomas Keller wrote: Hi Tony! Thank you for this new version. I tried it out and while its not blazingly fast, the draw speed is still very acceptable (approx. 20 to 30 seconds for roughly one and a half year of nvm history on my Core 2 Duo). I'm facing a rendering problem, though (screenshot attached): Merge nodes aren't visible at all and normal revisions are only shown as bar, but not as rectangular box. The -No-Labels version did not help here at all, but it was surely faster during the rendering phase and did not create any other problems than the one mentioned above. dot is from graphviz 2.28.0 (20110702.2211), by the way. I also noticed that mtn-browse will recognize if no dot is available, but it will not allow me to set a custom path to a custom dot version in a settings dialog in case its not in PATH. This should probably be easy to fix. Please drop me a note if you freeze the strings, so I can finalize the German translation for it. Thanks, Thomas. dot.tgz Description: application/compressed-tar ___ Monotone-devel mailing list Monotone-devel@nongnu.org https://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] Release Of mtn-browse Version 0.70 and Monotone::AutomateStdio 0.08
Hello Philipp, The README file contains a list of all the dependencies required. I don't know about Gentoo but all of the listed dependencies can be found on CPAN (http://www.cpan.org/). They may also be hosted elsewhere (as in your glib example) but you will find them all on CPAN as well (as that is where I downloaded them from in the first place :-)). There is also a `meta' or `bundle' package on CPAN that will download all of the Gtk2/Gnome2 packages. That will leave you with libintl-perl for internationalisation support and Monotone::AutomateStdio (the latter is included in the tar file that you have downloaded). From what I know, Gentoo is a compile and install from source code distro... They probably have packages for this stuff already set up... Hope this helps and good luck. Tony. Philipp Gröschler wrote: On 31.05.2010 19:43, Anthony Edward Cooper wrote: I would like to announce the 0.70 release of mtn-browse: I tried to compile this one here, and it states Can't locate Glib.pm in @INC ... As I don't have the slightest clue about Perl, I can only guess that it is dev-perl/glib-perl (from http://gtk2-perl.sf.net) which is wanted here. At least the package is named so on Gentoo. Besides this one, are there any other dependencies which I would possibly have to resolve manually? And as I am trying to write an ebuild for it, could you please include the minimum required versions? Thanks, Philipp ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Release Of mtn-browse Version 0.70 and Monotone::AutomateStdio 0.08
I would like to announce the 0.70 release of mtn-browse: Monotone browser (mtn-browse) is an application for browsing Monotone VCS databases without the need for a workspace. The interface allows one to: * Easily select a revision from within a branch * Find a revision using complex queries * Navigate the contents of a revision using a built in file manager * Display file contents, either using the internal viewer or an external helper application * Compare the changes between different revisions or versions of a file either using the internal difference viewer or an external application * Find files within a revision based on detailed search criteria * Display file annotations and easily refer back to the corresponding change documentation * Save files to disk * Browse remote databases via the netsync protocol. * Support for Monotone version 0.35 up to 0.47 * Extensive built in help * In English with additional German locale This version brings many bug fixes and locale support improvements along with support for the newer versions of Monotone. The source can be downloaded from here: http://sourceforge.net/projects/mtn-browse Currently supported platforms: Linux Mac OSX, should work on Solaris and other Unixes. Monotone::AutomateStdio is an object oriented Perl library module that allows Perl applications to easily interface with Monotone's automate stdio interface. This library supports Monotone versions 0.35 up to and including 0.47. All of the automate stdio functions are available via this library. The source and documentation can be downloaded from here: http://search.cpan.org/perldoc?Monotone::AutomateStdio Currently supported platforms: Linux Mac OSX, should work on Solaris and other Unixes. Both projects are considered stable (well at least by me) so let me know if you run into problems. Regards, Tony. ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Issue With remote_stdio
Hi all, Just tried out the new mtn au remote_stdio and it insists on a local database (ran command outside of a workspace). Presumably a bug, anyone reported/fixed this already? Cheers, Tony. -- If at first you don't succeed... Delegate. Pay a visit to my home page at: http://www.coosoft.plus.com/ ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] Issue With remote_stdio
Issue now raised as #28885 Thomas Moschny wrote: Hi! Am Sat, 13 Feb 2010 10:15:43 + schrieb Anthony Edward Cooper aecoo...@coosoft.plus.com: Just tried out the new mtn au remote_stdio and it insists on a local database (ran command outside of a workspace). Presumably a bug, anyone reported/fixed this already? That's known albeit not in the ticket system yet. Care to open a bug? Meanwhile you can use -d :memory: as a workaround. Regards, Thomas -- If at first you don't succeed... Delegate. Pay a visit to my home page at: http://www.coosoft.plus.com ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Monotone::AutomateStdio Patched to work with Monotone 0.46
Please delete if you don't use the above Perl library or don't use mtn-browse. For anyone that uses the above library the head revision of the net.venge.monotone.contrib.lib.automate-stdio branch now `works' with Monotone 0.46. However this has not been formally tested and does not include the new commands added in 0.46 (like the pull/push/sync/remote stdio). This is work in progress, but I have made this announcement to help mtn-browse users that have switched to 0.46. use view-mtn or mtn itself to get the fix. I haven't released a patch as people probably have differing versions of the library. Cheers, Tony. -- If at first you don't succeed... Delegate. Pay a visit to my home page at: http://www.coosoft.plus.com ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] Version 0.46 breaks monotone-viz and mtn-browse
Hello, I am aiming to look at this this weekend. Hopefully this will be the biggest break in protocol for some time. I can see the need. I will not be supporting the ticker stream stuff other than perhaps, at most shoving the raw data down a file descriptor (i.e. a pipe), as to do more does not make much sense in a function call-return paradigm. Nuno - Can you not stick with 0.45 for the time being? Also how did that code set menu work out? (Can reply to me directly). Cheers, Tony. Am 28.01.2010 14:42, schrieb Nuno Lucas: [Re-sent with the right, subscribed to the list, e-mail] It seems both monotone-viz and mtn-browse get stuck with the automate stdio changes on 0.46. Is this intentional? I know monotone is still not considered stable, but shouldn't at least strive to remain compatible with such useful programs? At least for monotone-viz, I consider it to be essential when using monotone, and mtn-browse is on the way to be the same. I've contacted Anthony E. Cooper (the author of mtn-browse and the underlying perl lib) before the release of 0.46 and he said he was willing to provide an updated version shortly after the release. I don't know what his current status is however. The issue with monotone-viz is a bit different. Olivier told me that he cannot actively develop on this application anymore, but is still willing to provide smallish updates. Thomas Moschny contacted him already afaik because he packages monotone with Fedora and has a broken monotone-viz package as well... In general the modifications to both programs / libs should be rather smallish - I've adapted the code for guitone in about half an hour (while ignoring out-of-band chatter and especially tickers, but even that should be doable in less than a day). If anybody seeks for implementation help on any of these two clients, drop me a note via IRC, I'm happy to help out. Thomas. -- GPG-Key 0x160D1092 | tommyd3...@jabber.ccc.de | http://thomaskeller.biz Please note that according to the EU law on data retention, information on every electronic information exchange might be retained for a period of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] viewMtn?
Does anyone know about what's happened to http://viewmtn.angrygoats.net. It's not responding and it wasn't last weekend... :-( Cheers, Tony. -- If at first you don't succeed... Delegate. Pay a visit to my home page at: http://www.coosoft.plus.com ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] FYI - mtn-browse
Hi Nuno, Many thanks for your kind comments about mtn-browse. I hope people will find it useful :-). Unfortunately, there will be some issues that need ironing out that I have slipped up on or have not personally encountered. Installation Instructions: Although the INSTALL file is very small it does refer you to the README file for more detailed instructions. The installation process for Perl CPAN modules is nearly always a standard: perl Makefile.PL [PREFIX=PATH] make make test make install and although mtn-browse is an application and not a module I thought the above approach would be the best to use as it is written in Perl and will at least be consistent with CPAN. Whilst the above is documented on the CPAN FAQ I have also included the same instructions in more detail in the README file under the installation section. If my instructions are unclear of confusing then please send me specific issues and I can hopefully improve upon what is there (probably best to send such corrections/queries just to me directly so as not to both others on this distro). Looking at it now it might be better to have the dependency section before the installation one for a start. The Monotone::AutomateStdio library is actually included in the mtn-browse tar ball and so if you don't say otherwise, this will be installed and used in preference to any other version that you may happen to have lying around, it will live in mtn-browse's lib/perl/Monotone directory. So your second concern should not arise. GtkSourceView: I developed the application on WhiteBox 4 (think RedHat AS 4 Update 3 - I heard about Centos after this!). Anyway this is not bleeding edge at about 3 years old. When starting on this project 18 months ago I deliberately didn't upgrade so as to help minimise dependency hell (i.e. you need the latest GTK/GNome libs etc). However the Perl bindings were current as RH do not ship them by default, or at least not in that version of REL. Hopefully you should find using slightly older versions of the Perl bindings will be fine as the underlying libraries that I use are even older than Ubuntu 8.04. I test mtn-browse on Whitebox and also Ubuntu 8.10 and it works fine. I assume that you are using the LTS release of Ubuntu? You could try: perl -e 'use Gtk2::SourceView; print Gtk2::SourceView-VERSION . /n;' What does that give? Is it 1.000? If not you could try running with the version you have installed and see how you get on. To bypass dependency checking, not normally recommended, use the linux-installer script directly with --dep-level=0. Also use linux-installer -m to get help on the other options (the Makefile.PL script is simply a wrapper that uses linux-installer to do the installation whilst presenting it to the end user like a standard CPAN package). Alternatively and better, use the normal perl Makefile.PL approach and each time it complains about a dependency then use the perl command above, substituting the package name, to get the version number and then update the linux-installer script (see line 142). At least this way if you are actually missing a package then this will be trapped rather than getting some nasty runtime error when you run the application. Hopefully when you do get it running and its not too much trouble, I would like you to run a script to dump out the versions that you have got on your Ubuntu system so I can update the dependency versions. I'll send you the script sometime soon. Hope this helps. Tony. Nuno Lucas wrote: Hello, On Mon, May 4, 2009 at 9:14 AM, Anthony Edward Cooper aecoo...@coosoft.plus.com wrote: Just a quick email to say that I have been developing a Linux desktop application called mtn-browse that allows browsing of Monotone databases without the need of a workspace. This works on Linux and Mac's OSX. It is written in Perl/Gtk+ and makes use of Monotone::AutomateStdio, a CPAN Perl library I have written that gives full access to the au stdio i/f. For further details please go to: http://www.coosoft.plus.com/software.html The application seems very nice, but could there be some more detailed installation instructions for those mortals that don't know nothing about perl and CPAN (other than reading about it on the internet)? The perl Makefile.PL thing complains about missing Gtk2::SourceView 1, but already installed it, as can be seen here: $ dpkg -l | grep SourceView ii libgtk2-sourceview-perl1.000-0ubuntu3 Perl wrappers for the GtkSourceView widget I'm using [K]Ubuntu 8.04. If I resolve this I will probably be blocked next on the AutomateStudio thing, as I have no idea on how to install a CPAN module. Anyway, the screen shots are pretty impressive, so good job. Regards, ~Nuno Lucas Cheers, Tony. -- If at first you don't succeed... Delegate
[Monotone-devel] FYI - mtn-browse
Just a quick email to say that I have been developing a Linux desktop application called mtn-browse that allows browsing of Monotone databases without the need of a workspace. This works on Linux and Mac's OSX. It is written in Perl/Gtk+ and makes use of Monotone::AutomateStdio, a CPAN Perl library I have written that gives full access to the au stdio i/f. For further details please go to: http://www.coosoft.plus.com/software.html Cheers, Tony. ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Possible Minor Bug With Automate Stdio I/F select...
Hi all :-), Just noticed that when you do something like: $ mtn automate stdio l6:select2:x:e mtn: warning: unknown selector type: x 0:0:m:32768:0005a23e30a9c2d3024d94773eec433bf9acb770 000645e7c050166ae0aba4d8ff3320f016da68ea 0006d609f3fe96a8fe3375d26d1a2de0bc93e882 . . . The warning message comes up as free format text on stderr. Whereas I would have expected the error message to be handled the same way as in this example: $ mtn automate stdio l6:select22:l:2009-02-22Tz16:47:00e 0:2:l:82:misuse: selector '2009-02-22Tz16:47:00' is not a valid date (2009-02-22Tz16:47:00) Seems a simple enough change: # # old_revision [6c12b62baa30a1abbe32e8d0463337b8a03eb8af] # # patch selectors.cc # from [91d924b52e55b60329cba63adac1af6d874014d0] #to [02aa7dcfb35cd604d3917b903f7effee906fdf6f] # --- selectors.cc91d924b52e55b60329cba63adac1af6d874014d0 +++ selectors.cc02aa7dcfb35cd604d3917b903f7effee906fdf6f @@ -117,7 +117,7 @@ decode_selector(project_t project, type = sel_update; break; default: - W(F(unknown selector type: %c) % sel[0]); + E(false, origin::user, F(unknown selector type: %c) % sel[0]); break; } sel.erase(0,2); I can submit to head if you want/agree with the proposed change. MTIA, Tony. ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Mtn automate select p: Bug
Hi peeps, Don't know if this one has been fixed already, but try doing `mtn au select p:0' on the net.venge db, it doesn't like it! My db sync details are: database: default-exclude-pattern database: default-include-pattern net.venge* database: default-server monotone.ca known-servers: monotone.ca . Version on mtn is 0.42 running on a 32 bit WhiteBox 4 Respin 1 (very similar to RHAS4U3). Did the command: mtn --db=test-0.40.mtn au select p:0 And got: mtn: fatal: std::logic_error: selectors.cc:251: invariant 'I(!value.empty())' violated mtn: this is almost certainly a bug in monotone. mtn: please send this error message, the output of 'mtn version --full', mtn: and a description of what you were doing to monotone-de...@nongnu.org. mtn: wrote debugging log to /home/aecoope/.monotone/dump mtn: if reporting a bug, please include this file mtn version --full gives: monotone 0.42 (base revision: 75ac12dd5b02025981edd6cd03caebb54721e481) Running on : Linux 2.6.9-34.ELsmp #1 SMP Sun Mar 19 13:54:02 CST 2006 i686 C++ compiler: GNU C++ version 3.4.5 20051201 (Red Hat 3.4.5-2) C++ standard library: GNU libstdc++ version 20051201 Boost version : 1_33_1 Changes since base revision: format_version 1 new_manifest [f2786e133906a73481e19a7e8d94ccaccaa977a6] old_revision [00862d40b30f11d972198ffb53e61986d3ce7aac] add_dir tests/p_selector add_file tests/p_selector/__driver__.lua content [07d038ba0783f318b8a2f0f308b230d1076e3000] patch selectors.cc from [42d6f2ba123ad9887a14ba28d9e6bc0a0bac5148] to [6ed76563cb3eb25fd04fa557b4a618a8f3b3ce3a] patch work.cc from [772e23f689e6523ca680a9dcd5d5889637eeb816] to [de879cd6058f54689874d6e06b8f23af423193ca] patch work.hh from [3a96efd140b80cfafff521c5c99bb187b16faed3] to [cd117c8295b2bdf48db35e92aaf29842c27a1b7f] Generated from data cached in the distribution; further changes may have been made. On older versions of mtn (0.3x) the first line of the output was blank. Cheers, Anthony. -- If at first you don't succeed... Delegate. Pay a visit to my home page at: http://www.coosoft.plus.com Current work set: 4 items - begin 'system_flavour' (in virtual void sanity::initialize(int, char**, const char*), at sanity.cc:75) Linux 2.6.9-34.ELsmp #1 SMP Sun Mar 19 13:54:02 CST 2006 i686 - end 'system_flavour' (in virtual void sanity::initialize(int, char**, const char*), at sanity.cc:75) - begin 'cmdline_string' (in virtual void sanity::initialize(int, char**, const char*), at sanity.cc:89) 'mtn', '--db=test-0.40.mtn', 'au', 'select', 'p:0' - end 'cmdline_string' (in virtual void sanity::initialize(int, char**, const char*), at sanity.cc:89) - begin 'string(lc_all)' (in virtual void sanity::initialize(int, char**, const char*), at sanity.cc:94) C - end 'string(lc_all)' (in virtual void sanity::initialize(int, char**, const char*), at sanity.cc:94) - begin 'full_version_string' (in virtual void mtn_sanity::initialize(int, char**, const char*), at mtn-sanity.cc:23) monotone 0.42 (base revision: 75ac12dd5b02025981edd6cd03caebb54721e481) Running on : Linux 2.6.9-34.ELsmp #1 SMP Sun Mar 19 13:54:02 CST 2006 i686 C++ compiler: GNU C++ version 3.4.5 20051201 (Red Hat 3.4.5-2) C++ standard library: GNU libstdc++ version 20051201 Boost version : 1_33_1 Changes since base revision: format_version 1 new_manifest [f2786e133906a73481e19a7e8d94ccaccaa977a6] old_revision [00862d40b30f11d972198ffb53e61986d3ce7aac] add_dir tests/p_selector add_file tests/p_selector/__driver__.lua content [07d038ba0783f318b8a2f0f308b230d1076e3000] patch selectors.cc from [42d6f2ba123ad9887a14ba28d9e6bc0a0bac5148] to [6ed76563cb3eb25fd04fa557b4a618a8f3b3ce3a] patch work.cc from [772e23f689e6523ca680a9dcd5d5889637eeb816] to [de879cd6058f54689874d6e06b8f23af423193ca] patch work.hh from [3a96efd140b80cfafff521c5c99bb187b16faed3] to [cd117c8295b2bdf48db35e92aaf29842c27a1b7f] Generated from data cached in the distribution; further changes may have been made. - end 'full_version_string' (in virtual void mtn_sanity::initialize(int, char**, const char*), at mtn-sanity.cc:23) ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Locking Issues
Please ignore the bit about locking issues in the previous email that I sent out a few days ago. Sorry :-(. -- If at first you don't succeed... Delegate. Pay a visit to my home page at: http://www.coosoft.plus.com ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Light The Touch Paper And RUN! :-)
Hi peeps, A small question. Why is monotone at version 0.42 (listed as alpha on freshmeat)? I know that development is ongoing and all that. But what is there now (bar that little bugget to do with select that reports errors on syncing), is VERY stable. In fact dare I say, more stable than some other similar products that have been released for some time. Would it not be an idea to have a bug fix only release and release it at 1.0? I have a nasty feeling that other systems are going to get more widely adopted just because of a release number... On another completely different point. I heard rumours about a locking issue when using mtn au and syncing. Is this still an issue (I haven't had any issues myself with 0.42)? If there are issues with mtn au keeping the database open, then this may have been related to a request by me to make things go faster when using mtn au get_content_changed (slowed right down in 0.40 and 0.41). I believe that db context is now left open between au commands. If locking is an issue, could one not introduce a lock/unlock command via mtn au that would keep context whilst locked and would only unlock when the unlock command was given or the process exited. If au commands were given without a lock then locking would be done just for that command (as before). Therefore I as a user of mtn au can choose to use a lock/unlock sequence when I know I am going to be making zillions of requests. As I said, 0.42 is fine performance wise and I have had no issues with locking myself. It's just that a friend of mine has been using mtn trac and setting that up and apparently that has an issue. Sorry if this is out of date info or wrong Many thanks, Tony. -- If at first you don't succeed... Delegate. Pay a visit to my home page at: http://www.coosoft.plus.com ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Sync Issue
Hello, We use monotone 0.35 at work and have been having some minor issues when syncing databases. The problem seems to happen when a database has a couple of revisions to upload and several hundred revisions to download (at a minimum). The sync sometimes locks up the client and the server locks out other clients while the offending client is left running. The server is idle waiting on poll, presumably waiting for some subtransaction to complete. It resumes normal operation once the faulty client is terminated. Once the client has done this once it does it again when rerun. It has only happened twice so far in 10 months or so. On the last occasion I tried doing separate pushes and pulls, both of which worked first time. The user was then able to carry on syncing as normal. The database is about 1GB in size. Is this a known problem that has been fixed? I looked in the update notes and your bug tracking system but didn't come across anything like this. Many thanks in advance, Tony Cooper. ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Alerting People To New Stuff
Hi again, I have been knocking up a few utilities etc in dedicated branches under the contrib branch in monotone.ca's database. Where is the best place to highlight these things so that it avoids duplication and helps others? Is the monotone Wiki the best place? Tony. -- If at first you don't succeed... Delegate. Pay a visit to my home page at: http://www.coosoft.freeserve.co.uk/ ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Stange Behaviour In Version 0.37
Just thought you would like to know... I was testing my perl automate stdio library when I noticed some odd behaviour. My test database is the one from monotone.ca, synced using mtn version 0.35. What I have seen: 1) mtn ls branches takes much longer. 2) Above command does not give the same results as 0.35. 0.37 reports 86 branches and 0.35 reports 187. 3) Because of I suspect point 2 `mtn update -r h: -b net.venge.monotone.types' from branch net.venge.monotone also fails where it used to work for 0.35. This seems to have been introduced in 0.37 as 0.36 works as expected. I have raised this as PR no 21513. Cheers, Tony. ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Write Access To net.venge.monotone....
Hi all, Not sure if this is the right way of going about it but... I'm writing/have been writing a number of perl utilities for use with mtn and would like to store them in your db. I will probably put them onto CPAN as well. I have been writing C code on Unix since the mid 80's and C++ for say about a year, perl ~ 6 months. Written things from linux device drivers (1 USB and 1 PCI) to GUIs. I have no desire to fiddle around with the main code, you seem to be doing just fine without me :-), but I would like to contribute utilities etc that may help others. Done so far/in progress: mtn-cleanup - perl utility that completely reverts a workspace to a clean state, basically removes everything not in the manifest and then does a revert. Monotone.pm - Module for using perl with mtn automate stdio. Hopefully coming up at some point: Simple cvsweb style front end. I know about viewMTN but when I tried it, it was too slow and kept leaving mtn processes lying about the place (was on Solaris 2.9 Apache/1.3 though). Simple browser/utility in perl/Gtk. I'm thinking perhaps somewhere under contrib like net.venge.monotone.contrib/perl Would it be possible to give me write access to contrib and below? Will send pubkey if/when you are happy. Cheers, Tony Cooper. -- If at first you don't succeed... Delegate. Pay a visit to my home page at: http://www.coosoft.freeserve.co.uk/ ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Files Changing During Commit.
Hi again, Just recently had an odd one. A developer on our team got a `file modified during commit, aborting' message. On the second attempt he exited the editor, KWrite, touched the file and it still failed. However, upon the third attempt, where he needlessly added a line to the file, he succeeded. Unfortunately he did all this before speaking to me. When I went over there I recommitted the original file with no problems. This is under 64 bit RedHat AS4U2 over NFS. The only other application running was konsole. I suspect this is some sort of NFS caching nasty and the inode timestamps are getting updated during the commit. I thought of suggesting doing a touch followed by a sync but NFS writes should not cache on the client side... Have you come across this and what is the best way of dealing with it? By the way we are using mtn Version 0.35. Many thanks in advance. Tony Cooper. ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Corruption Spreading Through Sync
Hi again, One question I was asked at work yesterday... What happens if a database gets corrupted due to an underlying hardware failure and the user, not knowing this, syncs his database? Not such a stupid question as I have had situations where drivers don't report disk errors, you just get weird behaviour (e.g. IDE disks under Solaris). We are not bothered about the one corrupted database - just that corruption spreading. Am I correct in assuming that the either one party or both involved with the sync exchange checks the data being received/sent. Say by rechecking the hashes on all data transferred? Many thanks in advance. Cheers, Tony Cooper. ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] Corruption Spreading Through Sync
Markus, Excellent, many thanks for that very informative reply. Thank you once again :-). Tony. Markus Schiltknecht wrote: Hello Anthony, Anthony Edward Cooper wrote: One question I was asked at work yesterday... What happens if a database gets corrupted due to an underlying hardware failure and the user, not knowing this, syncs his database? Not such a stupid question as I have had situations where drivers don't report disk errors, you just get weird behaviour (e.g. IDE disks under Solaris). We are not bothered about the one corrupted database - just that corruption spreading. Monotone is pretty strong in ensuring consistency. Most probably, the user on the box with disk failures would notice way before syncing. AFAICT mtn does not do excessive checks on 'mtn status' for performance reasons. But at least on commit, it quite certainly checks for validity of the parent revision. A quick example, which does not prove anything: [EMAIL PROTECTED]:/home/markus# mtn -d test.db setup test -b test [EMAIL PROTECTED]:/home/markus# cd test [EMAIL PROTECTED]:/home/markus/test# mtn add fileA mtn: adding fileA to workspace manifest [EMAIL PROTECTED]:/home/markus/test# mtn commit -m initial import mtn: beginning commit on branch 'test' mtn: committed revision 072fe56e02d71c686e9ff1139004497b370b40ea [EMAIL PROTECTED]:/home/markus/test# mtn status Current branch: test Changes against parent 072fe56e02d71c686e9ff1139004497b370b40ea no changes [EMAIL PROTECTED]:/home/markus/test# ls -lha ../test.db -rw-r--r-- 1 markus markus 288K 2007-09-20 11:18 ../test.db # okay, at that point I've set up a quick test repository, which # weights 288kb. I'm now going to manually 'corrupt' one single # byte somewhere in the middle of the file: [EMAIL PROTECTED]:/home/markus/test# dd if=/dev/random of=../test.db seek=144000 bs=1 count=1 1+0 records in 1+0 records out 1 byte (1 B) copied, 6.6073e-05 seconds, 15.1 kB/s [EMAIL PROTECTED]:/home/markus/test# mtn status Current branch: test Changes against parent 072fe56e02d71c686e9ff1139004497b370b40ea no changes # 'mtn status' didn't notice. Now let's try to change a test # file and commit a new revision. [EMAIL PROTECTED]:/home/markus/test# echo aoeu fileA [EMAIL PROTECTED]:/home/markus/test# mtn status Current branch: test Changes against parent 072fe56e02d71c686e9ff1139004497b370b40ea patched fileA # 'mtn status' still didn't notice, it simply sees the modification [EMAIL PROTECTED]:/home/markus/test# mtn commit mtn: error: sqlite error: SQL logic error or missing database mtn: error: make sure database and containing directory are writeable mtn: error: and you have not run out of disk space # 'mtn commit' clearly failed. While this looks like SQLite already # complains, because I have corrupted it's internal data structures, # and not real monotone data, I'm pretty sure monotone would notice # other corruptions as well. However, rest assured that during a sync, both nodes re-check the revisions they get from the other one. This is absolutely necessary in such a distributed system, so that corruptions aren't propagated around. Regards Markus -- If at first you don't succeed... Delegate. Pay a visit to my home page at: http://www.coosoft.freeserve.co.uk/ ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Assorted DB Admin Questions
Hello all :-), We use Monotone at work, were using CVS, and we are very impressed with the system :-). A couple of questions if I may that I have been unable to get answers to... Background: Running monotone version 0.35 on Solaris 9.0 and RHAS4U2 (32 bit binaries running on 32 and 64 bit systems). We have one `master' repository (so everyone knows where to go to pick up the latest changes, network bandwidth, storage capacity, backups (being paranoid)) with developers storing their own databases on the workstation's local hard disk. Every time they commit, they sync. We have specific coding standards and procedures that must be adhered to. I administer Monotone and I have decided to have an error free policy for the db. The size of the db is 1GB with about 40K revisions. 1) I did a routine db check on the database and got 3 minor problems relating to two date certs on three revisions (when there was only one author cert). I know this isn't an issue. However I want to have a clean database. The only way I could remove the certs was to do a db dump, sed (to remove them) and then db load. This then passed. I supposed I could have used the SQL interface but I felt that there was probably a greater chance of mucking things up. A) Is there a better way of removing the certs? I know I could double up the author certs to keep it happy but then this would not reflect what happened (these revisions were created by the merging process that our build manager kicked off). b) I have been assuming that db dump, db load is absolutely completely lossless, is this a correct assumption? I'm just being paranoid! 2) A number of mistakes have been made by developers whereby they have used tag and branch names that are not consistent with our project standards. I have been asked to rectify these user mistakes. So when I have made these changes etc I need to stop people from syncing their databases to the master without downloading the new corrected database first (which they can do via scp and then they get it up to date with an mtn sync). I had thought that the best way of doing this would be to change the epochs of the affected branches. Those users not interested in those branches (projects) just carry on as before, whilst the ones affected have to download a new db. However how do I generate the new epoch hash? Does it have to be unique or just different from the previous one? Is there a better way of invalidating a user's database WRT to the master such that a sync is guaranteed to fail until they download the new one? Many thanks in advance, Tony Cooper. -- If at first you don't succeed... Delegate. Pay a visit to my home page at: http://www.coosoft.freeserve.co.uk/ ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
Re: [Monotone-devel] Assorted DB Admin Questions
Timothy, Many thanks for your quick and complete reply :-) Just one thing if I may. You say `the branch epoch has to be unique for that branch' is that unique amongst all branch epochs or unique amongst the hash ids used on that branch? WRT the db check, perhaps have 3 levels: informational, minor problem, major problem. When looking at the revisions they did look a bit odd having two dates. Anyway I wouldn't be doing anything about them if it weren't for the standardising the branch names bit. Many thanks once again for your help. Regards, Tony Cooper. On Sat, 2007-09-01 at 12:55 +0100, Anthony Edward Cooper wrote: Hello all :-), We use Monotone at work, were using CVS, and we are very impressed with the system :-). A couple of questions if I may that I have been unable to get answers to... Background: Running monotone version 0.35 on Solaris 9.0 and RHAS4U2 (32 bit binaries running on 32 and 64 bit systems). We have one `master' repository (so everyone knows where to go to pick up the latest changes, network bandwidth, storage capacity, backups (being paranoid)) with developers storing their own databases on the workstation's local hard disk. Every time they commit, they sync. We have specific coding standards and procedures that must be adhered to. I administer Monotone and I have decided to have an error free policy for the db. The size of the db is 1GB with about 40K revisions. 1) I did a routine db check on the database and got 3 minor problems relating to two date certs on three revisions (when there was only one author cert). I know this isn't an issue. However I want to have a clean database. Really I suppose we should just make db check not complain about mismatched certs ever. It doesn't break things, and it's an expected result of normal operations. The only way I could remove the certs was to do a db dump, sed (to remove them) and then db load. This then passed. I supposed I could have used the SQL interface but I felt that there was probably a greater chance of mucking things up. A) Is there a better way of removing the certs? I know I could double up the author certs to keep it happy but then this would not reflect what happened (these revisions were created by the merging process that our build manager kicked off). Well, the SQL interface is the only other way to remove arbitrary certs right now. It's not really something that's meant to be needed during normal operation. b) I have been assuming that db dump, db load is absolutely completely lossless, is this a correct assumption? I'm just being paranoid! Yes. 2) A number of mistakes have been made by developers whereby they have used tag and branch names that are not consistent with our project standards. I have been asked to rectify these user mistakes. So when I have made these changes etc I need to stop people from syncing their databases to the master without downloading the new corrected database first (which they can do via scp and then they get it up to date with an mtn sync). I had thought that the best way of doing this would be to change the epochs of the affected branches. Those users not interested in those branches (projects) just carry on as before, whilst the ones affected have to download a new db. However how do I generate the new epoch hash? Monotone does it by basically pulling hex characters from /dev/random. Does it have to be unique or just different from the previous one? It should be unique for that branch. Is there a better way of invalidating a user's database WRT to the master such that a sync is guaranteed to fail until they download the new one? No, that's exeactly what epochs were designed for. -- If at first you don't succeed... Delegate. Pay a visit to my home page at: http://www.coosoft.freeserve.co.uk/ ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel
[Monotone-devel] Failure To Complete Tests With Monotone Version 0.34 And 0.35
Dear Sir/Madam, I am trying to get monotone to build and it is having problems with the self tests, i.e. make check. System is SlackWare 9.0 running with a multi-processor kernel, gcc version 3.2.2, Boost library version 1.33.1. I am am also getting similar problems trying to build it, using the same version of the compiler and Boost library, on SPARC Solaris 9.0. The Boost library is built exactly according to the instructions given in the INSTALL file contained within monotone's tar file, and monotone is built as follows: ./configure CPPFLAGS=-I../boost_1_33_1 LDFLAGS=-L../boost_1_33_1/libs --prefix=/opt/GNU make make check make install DESTDIR=/home/aecoope/monotone/mtn-3.5 I have attached the output from `make check' for both monotone version 0.34 and 0.35. What can I do to get this to work? Many thanks in advance. Yours sincerely, Tony Cooper. logs.tar.gz Description: application/gzip ___ Monotone-devel mailing list Monotone-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/monotone-devel