Hi everybody,
I tried to update my bzr inkscape sources directory to the most recent state, using
sudo bzr pull
in the sources directory.
What I get is
Format <RepositoryFormatKnit4> for file:///Users/bub/Desktop/ inkscape/bzr-inkscape-0.47-src/.bzr/ is deprecated - please use 'bzr upgrade' to get better performance
What shall I do?
Yours, Wolf
Hi everybody,
I tried to update my bzr inkscape sources directory to the most recent state, using
sudo bzr pull
in the sources directory.
What I get is
Format <RepositoryFormatKnit4> for file:///Users/bub/Desktop/ inkscape/bzr-inkscape-0.47-src/.bzr/ is deprecated - please use 'bzr upgrade' to get better performance
What shall I do?
sudo bzr pull lp:inkscape
Yours, Wolf
On Mar 19, 2010, at 9:49 AM, Wolf Drechsel wrote:
Hi everybody,
I tried to update my bzr inkscape sources directory to the most recent state, using
sudo bzr pull
in the sources directory.
What I get is
Format <RepositoryFormatKnit4> for file:///Users/bub/Desktop/ inkscape/bzr-inkscape-0.47-src/.bzr/ is deprecated - please use 'bzr upgrade' to get better performance
What shall I do?
If you have it set up as per recommendations, the command I use is
bzr up
(I think "bzr update" will also work, if you prefer more typing)
I also don't use sudo, since that means I'm allowing things to escape my per-user sandboxing.
http://wiki.inkscape.org/wiki/index.php/Working_with_Bazaar#Binding_a_BZR_br...
2010/3/19 Wolf Drechsel <drechsel@...2249...>:
Hi everybody,
I tried to update my bzr inkscape sources directory to the most recent state, using
sudo bzr pull
in the sources directory.
What I get is
Format <RepositoryFormatKnit4> for file:///Users/bub/Desktop/ inkscape/bzr-inkscape-0.47-src/.bzr/ is deprecated - please use 'bzr upgrade' to get better performance
What shall I do?
Yours, Wolf
This message is not an error. It only says that we are using an older branch format that's compatible with older Bazaar releases. You can safely ignore it.
Regards, Krzysztof
On 20/03/10 01:20, Krzysztof Kosiński wrote:
This message is not an error. It only says that we are using an older branch format that's compatible with older Bazaar releases. You can safely ignore it.
Is there any reason why we would not upgrade the branch to the newer version?
Regards,
Marcin Floryan
On Tue, 2010-03-23 at 19:59 +0000, Marcin Floryan wrote:
On 20/03/10 01:20, Krzysztof Kosiński wrote:
This message is not an error. It only says that we are using an older branch format that's compatible with older Bazaar releases. You can safely ignore it.
Is there any reason why we would not upgrade the branch to the newer version?
We've tried to remain very conservative on dependencies. Though, I was going to propose this after 0.48 as the newer version does bring significant speed and size improvements to developers. Emacs in their migration to Bazaar used the latest format. To use the new format you need Bazaar 1.17 or higher.
--Ted
On Mar 23, 2010, at 1:27 PM, Ted Gould wrote:
We've tried to remain very conservative on dependencies. Though, I was going to propose this after 0.48 as the newer version does bring significant speed and size improvements to developers. Emacs in their migration to Bazaar used the latest format. To use the new format you need Bazaar 1.17 or higher.
So that leaves out Intrepid and earlier. According to the info on Ubuntu's website this also is not yet on Jaunty. Then again, it might be if they have a typo.
I guess the main question would be how many developers and potential developers do we have on distros with older versions of bazaar?
And given the glacial performance we've been seeing, especially for new checkouts, having nightly source tarballs and upgrading our bazaar to the latest format might be a good choice.
On Tue, 2010-03-23 at 21:09 -0700, Jon Cruz wrote:
On Mar 23, 2010, at 1:27 PM, Ted Gould wrote:
We've tried to remain very conservative on dependencies. Though, I was going to propose this after 0.48 as the newer version does bring significant speed and size improvements to developers. Emacs in their migration to Bazaar used the latest format. To use the new format you need Bazaar 1.17 or higher.
So that leaves out Intrepid and earlier. According to the info on Ubuntu's website this also is not yet on Jaunty. Then again, it might be if they have a typo.
I guess the main question would be how many developers and potential developers do we have on distros with older versions of bazaar?
And given the glacial performance we've been seeing, especially for new checkouts, having nightly source tarballs and upgrading our bazaar to the latest format might be a good choice.
There are PPAs with the newer versions for the older versions of Ubuntu. So it should be pretty straightforward. From the Ubuntu perspective I would say that we should definitely wait for Lucid to get out the door as some people might only wish to run LTS releases (a very reasonable thing to do) and thus there'd be an LTS to recommend they run.
I imagine that RHEL 6 will include the new Bazaar as well, but I have no information on that (or when RHEL 6 will be out).
--Ted
participants (5)
-
Jon Cruz -
Krzysztof Kosiński -
Marcin Floryan -
Ted Gould -
Wolf Drechsel