There are no write restrictions to the syncany trunk so far. As soon
as you're member of the syncany-team, you can commit fixed to the
trunk. However, normally making your own branch would be the way to
go:
But since it's just small fix, I'll fix it in the trunk and the
"newsync" branch.
Cheers,
Philipp
On Mon, Jun 27, 2011 at 9:10 AM, Daniel Kullmann
<email address hidden> wrote:
> I don't know how to "fix the bug in trunk". I have no write access to the syncany repo, so what do I do?
> I attached a patch to fix the problem.
>
> ** Patch added: "Fixes the bug"
> https://bugs.launchpad.net/syncany/+bug/796055/+attachment/2182347/+files/796055.patch
>
> --
> You received this bug notification because you are subscribed to
> Syncany.
> https://bugs.launchpad.net/bugs/796055
>
> Title:
> Can't find bundle for base name org.syncany.i18n.I18n, locale en_us
>
> Status in Syncany:
> New
>
> Bug description:
> This is the error I got when first running syncany from my checked out
> bzr repo. Note the lower case locale name ("en_us"), the file in the
> repo uses "en_US" as locale name. I solved the problem by making a
> copy of the src/org/syncany/i18n/I18n_en_US.properties file to
> src/org/syncany/i18n/I18n_en_us.properties.
>
> The full stacktrace is:
>
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at org.syncany.Syncany.<clinit>(Syncany.java:40)
> Caused by: java.util.MissingResourceException: Can't find bundle for base name org.syncany.i18n.I18n, locale en_us
> at java.util.ResourceBundle.throwMissingResourceException(ResourceBundle.java:1427)
> at java.util.ResourceBundle.getBundleImpl(ResourceBundle.java:1250)
> at java.util.ResourceBundle.getBundle(ResourceBundle.java:777)
> at org.syncany.config.Config.<init>(Config.java:89)
> at org.syncany.config.Config.<clinit>(Config.java:55)
> ... 1 more
> Could not find the main class: org.syncany.Syncany. Program will exit.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/syncany/+bug/796055/+subscriptions
>
Hi Daniel,
There are no write restrictions to the syncany trunk so far. As soon
as you're member of the syncany-team, you can commit fixed to the
trunk. However, normally making your own branch would be the way to
go:
$ bzr branch lp:syncany
$ cd syncany
(make changes)
$ bzr commit -m"my changes"
$ bzr push lp:~myusername/syncany/somename
But since it's just small fix, I'll fix it in the trunk and the
"newsync" branch.
Cheers,
Philipp
On Mon, Jun 27, 2011 at 9:10 AM, Daniel Kullmann /bugs.launchpad .net/syncany/ +bug/796055/ +attachment/ 2182347/ +files/ 796055. patch /bugs.launchpad .net/bugs/ 796055 i18n.I18n, locale en_us syncany/ i18n/I18n_ en_US.propertie s file to syncany/ i18n/I18n_ en_us.propertie s. ExceptionInInit ializerError Syncany. <clinit> (Syncany. java:40) MissingResource Exception: Can't find bundle for base name org.syncany. i18n.I18n, locale en_us ResourceBundle. throwMissingRes ourceException( ResourceBundle. java:1427) ResourceBundle. getBundleImpl( ResourceBundle. java:1250) ResourceBundle. getBundle( ResourceBundle. java:777) config. Config. <init>( Config. java:89) config. Config. <clinit> (Config. java:55) Syncany. Program will exit. /bugs.launchpad .net/syncany/ +bug/796055/ +subscriptions
<email address hidden> wrote:
> I don't know how to "fix the bug in trunk". I have no write access to the syncany repo, so what do I do?
> I attached a patch to fix the problem.
>
> ** Patch added: "Fixes the bug"
> https:/
>
> --
> You received this bug notification because you are subscribed to
> Syncany.
> https:/
>
> Title:
> Can't find bundle for base name org.syncany.
>
> Status in Syncany:
> New
>
> Bug description:
> This is the error I got when first running syncany from my checked out
> bzr repo. Note the lower case locale name ("en_us"), the file in the
> repo uses "en_US" as locale name. I solved the problem by making a
> copy of the src/org/
> src/org/
>
> The full stacktrace is:
>
> Exception in thread "main" java.lang.
> at org.syncany.
> Caused by: java.util.
> at java.util.
> at java.util.
> at java.util.
> at org.syncany.
> at org.syncany.
> ... 1 more
> Could not find the main class: org.syncany.
>
> To manage notifications about this bug go to:
> https:/
>