ng these
branches and start to use C++11?
Regards
Markus Wanner
signature.asc
Description: OpenPGP digital signature
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel
least 10.9 (Mavericks) and Xcode 5.0, but I could try again
on my Mountain Lion - its clang version (3.3) should theoretically
suffice. I don't remember what went wrong.
Regards
Markus Wanner
signature.asc
Description: OpenPGP digital signature
__
dual-operation should be supported when it
> does.
I think the answer to the dual-operation duration is obvious: Zero. We
just don't have the man-power.
What do you think would be a good time to switch to C++11?
I'm a bit concerned that botan is switching to C++11. (And just notice
1 feels like a new language [0]. I
personally don't think of it as new, but to me C++11 feels more like
what I always wanted C++ to feel like. I absolutely agree with his
follow-up statement: "The pieces just fit together better".
Regards
Markus Wanner
[0]: Bjarne Stroustrup'
rms. I'm certainly not
willing to test gccs back to version 3.2. Nor boost as of 1.33, for
example. (As currently stated in INSTALL.) I'd also like to drop support
for botan 1.6, maybe even 1.8.
Three years after release 1.0, I think it's about time to discuss the
set of supported
Jack,
over here at the monotone mailing list, we're discussing a move to
C++11, partly inspired by botan's move.
On 05/13/2014 07:29 PM, Markus Wanner wrote:
> I'm a bit concerned that botan is switching to C++11. (And just notice
> that botan even states gcc-4.7 as the mi
lking, it almost seems the C++11 is itself a new
> platform.
It mostly is an extension of the existing standards. There are very few
legal C++98 constructs that C++11 doesn't tolerate. Monotone doesn't use
any of those.
Regards
Markus Wanner
signature.asc
Description: OpenPGP
XX11' blocks. Any
platform that doesn't support C++11 is highly unlikely to ever ship
botan 1.12. And for the others, we need to support multiple stable
versions of botan, anyways.
Regards
Markus Wanner
signature.asc
Description: OpenPGP digital signature
__
On 05/15/2014 03:30 PM, Stephen Leake wrote:
> You left out Windows:
Yes, sorry, that's not due to my aversion against that OS, but because I
assumed those to be more of a "rolling release" style, where you usually
have a pretty recent gcc.
For the very same reason, I left out Gentoo and Arch Lin
xtensions?
The m4 script is supposed to use -std=gnu++11 only if -std=c++11 is not
supported. I haven't ever seen -std=iso9899:2011, before, but certainly
prefer the shorter variant.
Does your g++ support -std=c++11? If so, it looks like the m4 macro is
failing to do its job properly.
looks fine from here. Cleared to land.
Regards
Markus Wanner
signature.asc
Description: OpenPGP digital signature
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel
std=gnu++11) or a strict conformance mode (e.g.
# -std=c++11). If neither is specified, you get whatever works, with
# preference for an extended mode.
I left it unspecified, as I'm fine with whatever works (tm).
I corrected the order of tests, now. So for gcc, it now yields th
On 05/12/2014 09:51 PM, Markus Wanner wrote:
> net.venge.monotone.optional-cxx11: enables C++11 features on
> compilers supporting it. Doesn't change anything for
> compilers that do not provide C++11.
Given the consensus on enabling C++11 if available, I land
ndling concept very different from C++ exceptions, for example.)
Regards
Markus Wanner
signature.asc
Description: OpenPGP digital signature
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel
x27;s quite an improvement.
In the past, there certainly were efforts to get rid of boost. I'm not
sure about the exact benefits, as of now, but C++11 would certainly get
us a huge step towards that goal.
Regards
Markus Wanner
signature.asc
Description: OpenPGP digital signature
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel
r that we better remain netsync compatible back
to (at least) 0.48.
> (Why, why, couldn't they haave picked wheezy for this?)
Quoting from your link: "Importantly, the success of Squeeze-LTS will be
used to judge the viability of LTS support for [wheezy and [jessie]." So
there
On 05/16/2014 05:17 PM, Stephen Leake wrote:
> Markus Wanner writes:
>
>> Interesting, I thought I tested that. But you're right, this looks like
>> the macro doesn't do what it's supposed to do. It itself claims:
>>
>> # The first argument, if
I'm currently providing quite a few build animals to hit my targets and
to make my wishes come true. If you want to keep a platform supported,
please consider contributing a buildbot or at least run occasional tests
on that platform.
Regards
Markus Wanner
P.S: in the above list, I counted
ase class?
> Can we use a unique_ptr here?
That doesn't make the void pointer any more type safe. We should get rid
of void*, that's supposed to be C++, after all.
Regards
Markus Wanner
signature.asc
Description: OpenPGP digital signature
___
On 05/16/2014 01:54 PM, Markus Wanner wrote:
> Given the consensus on enabling C++11 if available, I landed that
> branch, yesterday.
Looks like that upset some build animals. Interestingly, Debian/sid runs
into some boost issue, when C++11 is enabled. I don't see that issue on
Debian/
;re
better off using gnu++11.
Build animal wallaby (using bleeding edge clang) isn't quite happy, either.
Regards
Markus Wanner
signature.asc
Description: OpenPGP digital signature
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://
orts
-std=gnu++11, though.
Regards
Markus Wanner
signature.asc
Description: OpenPGP digital signature
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel
he
configure script. I personally prefer the former, but we need to
consider that it has no effect on the embedded netxx sources. (Actually
an argument to get rid of those...)
Regards
Markus Wanner
signature.asc
Description: OpenPGP digital signature
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel
On 05/18/2014 08:18 PM, Stephen Leake wrote:
> Markus Wanner writes:
>
>> We can put such things in src/base.hh or add to CXXFLAGS via the
>> configure script.
>
> I added to src/base.hh:
I did that, already. And the Cygwin build animal confirms it works (it
shows
On 05/18/2014 10:02 PM, Stephen Leake wrote:
> Markus Wanner writes:
>
>> We can put such things in src/base.hh or add to CXXFLAGS via the
>> configure script. I personally prefer the former, but we need to
>> consider that it has no effect on the embedded netxx sources.
On 05/18/2014 10:02 PM, Stephen Leake wrote:
> Markus Wanner writes:
>> (Actually an argument to get rid of those...)
>
> Is that what the nvm.asio branch is for?
Yes. Back then, Zack started with that branch, but discontinued after
adding an m4 macro to detect asio [0].
AFAICT
On 05/19/2014 12:51 AM, Stephen Leake wrote:
> done, tested, pushed.
Thanks. I back-patched that to nvm, as I think it's useful there as
well. IMO boost::shared_ptr is equally bogus - even if the
compiler doesn't seem to complain in that case.
Regards
Markus Wanner
signature.as
On 05/16/2014 07:12 PM, Markus Wanner wrote:
> Stephen wants these (and supports them by occasional manual testing):
> * RHEL 6
Minor update on the RHEL front: build animal armadillo (effectively
running CentOS 6.5) now uses a g++ 4.8.2 from the devtools-2 package.
With that, it now fa
st<> for
now. Therefore, I reverted the corresponding changes in nvm.mandatory-cxx11.
Regards
Markus Wanner
signature.asc
Description: OpenPGP digital signature
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel
On 05/20/2014 05:42 PM, Markus Wanner wrote:
> Yeah, I noticed these as well. Build animal porcupine (build 29) shows
> pretty much that same error. So does the alpaca (a NetBSD 6.1 box, see
> its build 25).
FWIW, that was with gcc-4.5. The build animal is now using gcc48 from
pkgsrc, wh
Hi,
On 05/16/2014 07:12 PM, Markus Wanner wrote:
> On my wishlist (for minimum requirements):
> * Mac OS X 10.8 (Mountain Lion) / XCode 5
I successfully compiled and run tests of nvm.mandatory-cxx11 on Mountain
Lion, now.
As it turned out, the major stumbling block was that Appl
On 05/28/2014 01:32 AM, Stephen Leake wrote:
> Markus Wanner writes:
>> Given the above successes, the lack of offers to help with other
>> platforms and baring further objections, I plan to land
>> nvm.mandatory-cxx11 within the next few days.
>
> +1
Land
ediate
step. But one that doesn't need to be visible to others.
Regards
Markus Wanner
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel
On 06/17/2014 06:18 PM, J Decker wrote:
> isn't it just as simple as adding a comment?
Well, that adds a comment. That's a) not the same as a changelog cert
and b) doesn't delete the existing changelog cert.
Regards
Markus Wanner
e. 1.9.x or 1.11.x). You shouldn't
compile monotone against one of those (unless you know what you're doing).
Regards
Markus Wanner
signature.asc
Description: OpenPGP digital signature
___
Monotone-devel mailing list
Monotone-devel@nongnu.or
rate status information - rather than forcing the user to fix
these issues, first.
The nvm.revamp-status branch addresses these issues. It doesn't quite
pass all tests, yet. And there still are minor issues and other UI
issues that I'd like to address, eventually. However, I think it'
On 10/18/2014 10:40 PM, Stephen Leake wrote:
> Markus Wanner writes:
>> it's been a while since the C++11 refactoring, but as promised, here's
>> some actually useful work: I scratched a couple of itches I had with
>> recent monotone's status command and star
this bike shed?
Regards
Markus Wanner
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel
Hi,
On 03/30/2015 08:48 PM, Markus Wanner wrote:
> To argue a bit more objectively: I tried to make the default colors
> readable on black as well as white background. And I reduced noise a bit
> by un-coloring a couple of things. Colorization can be adjusted via a
> lua hook.
I just
ell. I'll change that. Thanks for your input.
The same argument could be applied for '--pager', though, where I have a
bit of a hard time coming up with a valid use case.
Regards
Markus Wanner
___
Monotone-devel mailing list
Monotone-de
On 04/12/2015 09:15 PM, Timothy Brownawell wrote:
> Oops, I meant "other" as in "not monotone". With my example being "ls"
> (which I have the GNU coreutils version, on current Debian testing).
Oh, I see, that makes more sense, now. And yes, I agree, it's a good
idea to be consistent with other un
,
anyways) and only run 'mtn db info' if it is known to exist. (Or
skip the existence test and properly parse stderr. However, that
seems prone to error, IMO.)
The patch as attached applies to buildbot release 0.8.10. I'm happy to
test an improved variant of it, if neces
Pierre,
On 04/18/2015 02:17 PM, Pierre Tardy wrote:
> As an open-source project, buildbot is dependant on its community to
> make all its features work. As you seem like a monotone expert, we would
> greatly appreciate if you could contribute a fix to the monotone master
> side step, that would in
Lapo,
it looks like monotone.ca is unreachable. Could you please revive it?
Thanks.
Regards
Markus
signature.asc
Description: OpenPGP digital signature
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listin
is tool tells me the authoritative DNS are mostly not anwesring:
> http://www.squish.net/dnscheck/
>
> 18.7% Answered from ns3.zonomi.com <http://ns3.zonomi.com> (128.199.213.165)
>
> www.monotone.ca <http://www.monotone.ca>. 3600IN A
> 144.76.18
Hi,
monotone isn't compatible with development branches of botan (i.e. x.y
for odd values of y). Please compile against 1.10, instead.
Regards
Markus Wanner
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/ma
On 10/07/2015 09:58 AM, Lapo Luchini wrote:
> JTLUK I'm preparing mtn support for password-store
Cool!
Markus
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel
On 10/09/2015 11:36 AM, Hugo Cornelis wrote:
> Hi, is there anyone on this list who has experience using monotone on
> the AS400?
Not that I've heard of, before.
Does it compile? Pass tests? Could you possibly provide a buildbot slave?
Regards
Ma
n works.)
That's certainly not the case for monotone, where certs reference the
revision id (a sha-1 hash).
> https://github.com/jayphelps/git-blame-someone-else
WTF is that? You're not trying to blame monotone for git's usage of
SHA-1, are you?
Kind Regards
Markus Wanne
oncerned, because there we have integrated certs, which check
against the full hash. And just to identify a revision out of the set of
already validated revisions, 5-7 chars usually are enough. (Sounds
suspiciously similar to Linus' argument
as well. Just out of curiosity: Why would you want
that? And what's the important difference to an ordinary checkout (maybe
to a tmpfs)?
> I dunno maybe it's not so hard?
Given I don't even partly grasp what you're trying to accomplish, it's
hard to say...
Kind Regar
u insist.)
Plus: archaurwiki even reported he created a botan-stable and a matching
monotone package for arch.
Regards
Markus Wanner
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel
On 03/24/2016 03:51 PM, Lapo Luchini wrote:
> mtn: error: '.gnupg/S.gpg-agent' is neither a file nor a directory
Yeah, that sucks...
Therefore, I just thought monotone to cope with special files in working
directories, please give the recent rev a35938 a spin.
Regards
and ssuch to mark the conflicts?
Well, you can always commit the file including these markers. However,
they have no special meaning for monotone and things might get messy
with further merges on that same file.
Regards
Markus Wanner
___
Monotone
adable one?
I appreciate your feedback.
Regards
Markus Wanner
signature.asc
Description: OpenPGP digital signature
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel
* really care what serialization format
monotone uses underneath?
Regards
Markus Wanner
signature.asc
Description: OpenPGP digital signature
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel
However, reducing the amount of data to be hashed, cached and moved
around (in memory, network, etc..) sounds like a generally good idea to
me (performance wise). However, it's equally clearly a bad idea from a
usability perspective. So there's a balance. That's why I started this
currently prefer to try something canonical
that's still valid YAML.
Kind Regards
Markus Wanner
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel
With these restrictions, base58 is about as space efficient as you can get.
Kind Regards
Markus Wanner
signature.asc
Description: OpenPGP digital signature
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel
mention base58... ;-)
Regards
Markus Wanner
signature.asc
Description: OpenPGP digital signature
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel
new format, for certificates. Certainly something
that monotone-1.1 doesn't understand. So 1.2 might still need to write
the old format/version, at least by default.
Kind Regards
Markus Wanner
signature.asc
Description: OpenPGP digital signature
___
Mo
cert: "1249123840182028934801az"
Idunno: "blah"
}
> and that itself is in utf-8... which emans any value is storable in a
> rune (to borrow a type name from Go)
Well, yes, we're already using utf-8 for commit messages and such. So
any human-readable, text
iced that the recently added colorization feature breaks
things on (non-cygwin-)Windows, so I guess I'll have to look at that OS
rather sooner than later.
Kind Regards
Markus Wanner
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://
ion 1.1. Out of interest: what changes were
necessary to support 1.1 (versus 1.0)?
Kind Regards
Markus Wanner
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel
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).
Okay, thanks for elaborating.
Regards
Markus Wanner
___
Monotone-devel mailing list
Monotone-devel@n
oost variant, it's a
headers-only library, so it's trivial to "install" as well.
I'd appreciate your feedback and comments.
Regards
Markus Wanner
[0]: To be fair, I should probably mention that I myself am the
maintainer of the asio standalone package for Debain, see:
ht
'do nothing if already the same'
We had discussions about merging nodes or "stitching". But merge
semantics for things like that are far from trivial...
I agree this is not an optimal solution.
Kind Regards
Markus Wanner
signature.asc
Description: OpenPGP digital signatur
nvinced that monotone's approach has its benefits and it
would be worth implementing proper stitching, but... as a matter of fact
nobody implemented it so far.
Kind Regards
Markus Wanner
signature.asc
Description: OpenPGP digital signature
__
tall mtn-browse under /opt and the installer will highlight
> missing dependencies.
Mind filing a RFP (request for packaging)?
I already maintain monotone and monotone-viz for Debian.
Regards
Markus Wanner
signature.asc
Description: OpenPGP digital signature
_
yes,
please file the "official" RFP. Thanks.
Regards
Markus Wanner
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel
On 06/28/2016 04:53 PM, Hendrik Boom wrote:
> Sorry. I wasn't clear. I was referring to the problem with
> monotone-viz being unable to parse dot output.
Well, for that it would be better to file a bug for that specific project.
> Or should I invesigate the problem myself? If so, where do I f
On 06/28/2016 04:55 PM, Hendrik Boom wrote:
> I tried to update my repository for monotone that I had downloaded
> a few years ago, and it seems not to be able to find the main repository.
> Where is inowadays?
Hm.. the website seems down. I'll take care soon-ish.
>From the top of my head:
"monot
On 28.06.2016 17:22, Hendrik Boom wrote:
> On Tue, Jun 28, 2016 at 05:14:44PM +0200, Markus Wanner wrote:
>> On 06/28/2016 04:55 PM, Hendrik Boom wrote:
>>> I tried to update my repository for monotone that I had downloaded
>>> a few years ago, and it seems not
On 09.09.2016 17:56, Lapo Luchini wrote:
> Works for me. :)
>
> monotone 1.2dev (base revision: ad1a31e0c32511a094308eb6b9c03089e4b66b83)
Thanks for your confirmation.
Markus
signature.asc
Description: OpenPGP digital signature
___
Monotone-devel m
tone is anywhere nearly as active as
Botan.
Notably, it won't compile with the newest Botan version.
Kind Regards
Markus Wanner
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel
fic 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
___
Monotone-devel mailing li
eleases should
> be forward compatible. It is anticipated 2.x will be supported until
> at least 2021.
+1, I welcome that simplification.
Kind Regards
Markus Wanner
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel
7;ll have to defer further work
on that branch to next week.
Kind Regards
Markus Wanner
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel
#x27;m
currently testing against: 1.8.15, 1.10.17, 2.0.1, 2.1.0, 2.2.0, and
2.3.0. However, I'm still facing Botan-version dependent failures on
various functional tests. I'll investigate on those, next.
Kind Regards
Markus Wanner
___
Monotone-
On 11/08/2017 10:39 PM, Markus Wanner wrote:
> All of the unit tests now pass with the following Botan versions I'm
> currently testing against: 1.8.15, 1.10.17, 2.0.1, 2.1.0, 2.2.0, and
> 2.3.0. However, I'm still facing Botan-version dependent failures on
> various
On 11/11/2017 11:24 AM, Markus Wanner wrote:
> I corrected the PKCS #5 key writing by specifying "SHA-160" instead of>
> "SHA-1" for Botan versions 2.0 and newer.
I figured I forgot to actually commit this (had the commit log prepared
and everything, but...). Done
On 11/11/2017 11:24 AM, Markus Wanner wrote:
> With that last fix all functional tests now pass and nvm.botan is ready
> to be merged on mainline. Anybody up for a quick review?
I count the lack of objections as a frantic "Hell, yes, go merge!" and
did so. The main branch sh
On 02/28/2018 07:24 PM, Hendrik Boom wrote:
> When I use monotone-viz I get the message
> Could not parse dot output
IIRC I have similar issues with monotone-viz (Debian stable). I'm not
aware of any replacements.
Kind Regards
Ma
e annoying your users by having to throw away and re-fetch the
entire repository.
Kind Regards
Markus Wanner
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel
re's tools to automate that. Doing it by hand certainly isn't worth
the trouble.
Kind Regards
Markus Wanner
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel
sions available in Debian testing. So it
looks like we'll have to bundle 1.2, first.
Kind Regards
Markus Wanner
___
Monotone-devel mailing list
Monotone-devel@nongnu.org
https://lists.nongnu.org/mailman/listinfo/monotone-devel
Hello Petr,
On 07.05.2018 14:24, Petr Pisar wrote:
> monotone-1.1 fails to build with PCRE 8.42:
> By the way, PCRE is obsoleted by PCRE2.
thanks a lot for these hints. I'll eventually take a look. A monotone
1.2 release is way overdue.
Kind Regards
Markus Wanner
signature.asc
Hi,
On 10.08.19 10:58, Thomas Moschny wrote:
as Botan 1.10 has gone EOL 2018-12-31 [1], has anybody already looked
into porting Monotone to Botan 2.x?
I did, a few months ago. I'd have to check how far I got, but it seemed
doable.
Regards
Markus
__
301 - 388 of 388 matches
Mail list logo
