** Changed in: bzr/2.2
Status: Fix Released => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/693880
Title:
bzr under python2.7 fails: _ReportingFileSocket.readline lacks size
arg
This doesn't appear to be properly fixed in the 2.2 series. Or at a
minimum, I'm unable to reproduce *this* bug because of another bug.
Looking at the Traceback of the bug, it seems to be a mismatch between
xmlrpclib and bzr's implementation of the XMLRPCTransport. However, with
bzr 2.2.[1,2,3,4,5
I can do this manually and it works. Based on the test case that Andrew
proposed. The basic script is:
1) Create a repository with a few commits in it.
bzr init foo
cd foo
echo bar > bar
bzr add; bzr commit -m "bar"
bzr commit --unchanged -m "two"
bzr commit --unchanged -m "three"
2) At thi
Martin, your patch for this is considered landed in trunk, but Rejected
for 2.1. So I'm going to mark this as such, and change the In Progress
setting.
** Changed in: bzr
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, whi
Hey Martin, what's your status on this? Anything we can do to help you
along?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/686161
Title:
bzr crashed with UnicodeEncodeError in run()
--
ubuntu-bug
I'm guessing Declan didn't manage to follow up on this, so it shouldn't
be considered "In Progress". It can be considered "patch available that
needs some tweaking".
** Changed in: bzr
Status: In Progress => Confirmed
** Tags added: patch-needswork symlink
--
You received this bug notifi
** Changed in: bazaar (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/617503
Title:
Dead link in documentation to Glossary
--
ubuntu-bugs mailing li
Quick answer. (I thought this was a dupe, but couldn't find the other
bug.)
Say you have 4 pack files in your repository. And 4 revisions. However,
revision 3 shares the exact inventory of revision 2.
Autopack decides it needs to combine just packs 3 & 4 together.
The Packer code is then exposed
Just to finish, it should be quite rare, and 'bzr pack' should always
fix it. (Since it will put all inventories and revisions into a single
pack, and it never sees a 'partial' repository.)
--
bzr crashed with ErrorFromSmartServer (We are missing inventories for revisions)
https://bugs.launchpad.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/28/2010 7:16 AM, Martin Pool wrote:
> Thanks for the report. There are other similar bugs in other commands.
>
> Perhaps we should check for a 'reliable' user id only in commit?
I believe the trigger is that bzr wants to be able to annotate th
Public bug reported:
Binary package hint: update-manager
I'm not 100% sure about the package.
Update manager gave me a big red warning symbol in the application
indicators section. When I moused over it, it told me there was some
sort of problem updating, and to click here and request "Check for
** Attachment added: "Dependencies.txt"
https://bugs.edge.launchpad.net/bugs/619463/+attachment/1496200/+files/Dependencies.txt
--
update-manager app indicator gives incorrect tooltip ('check for updates'
should be 'check')
https://bugs.launchpad.net/bugs/619463
You received this bug notifi
** Package changed: bzr (Ubuntu) => bzr-git (Ubuntu)
--
TypeError: expected string or buffer
https://bugs.launchpad.net/bugs/597456
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Loïc Minier wrote:
> Public bug reported:
>
> Binary package hint: bzr
>
> Hey
>
> I think we need a way to prevent bzr push from replacing the history
> when it think it can do so; this might not be the right thing to do for
> local branches, but i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 8/27/2010 2:57 PM, ComputerJy wrote:
> Public bug reported:
>
> Binary package hint: bzr
>
> Whenever I run the following command: bzr branch lp:ubuntu/apache2
> while the terminal is in an empty directory (owned and with permission to
> write to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Martin Pool wrote:
> On 14 July 2010 10:57, John A Meinel wrote:
>> Isn't the original fix for this setting "append_revisions_only" on the
>> trunk? (Preventing this sort of behavior).
>
> That would prohibit unc
seems like 'recommends' vs 'depends' to me.
--
loggerhead package should depend on python-pygments to support
syntax-highlighting
https://bugs.launchpad.net/bugs/607775
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mai
My guess is that vzctl is setting $HOME to /etc now.
** Changed in: bzr
Importance: Undecided => Medium
** Changed in: bzr
Status: New => Incomplete
--
bzr via etckeeper logs to /etc/.bzr.log in OpenVZ containers
https://bugs.launchpad.net/bugs/622898
You received this bug notificatio
Public bug reported:
Binary package hint: gnome-keyring
To start with, I'm assuming this is gnome-keyring. It is whatever dialog
pops up when I auto-login telling me that it didn't get a chance to
unlock my keyring (because I haven't entered my password yet).
Once it is up, if I click the dialog
** Attachment added: "Dependencies.txt"
https://bugs.edge.launchpad.net/bugs/632543/+attachment/1554171/+files/Dependencies.txt
--
gnome-keyring password entry allows cursor outside of password entry
https://bugs.launchpad.net/bugs/632543
You received this bug notification because you are a
I should also note that the ssh-agent entry (pinetry perhaps?) has the
same problem. When it requests my ssh passphrase, it does not constrain
me to typing in the text entry box, but lets me put the cursor on any of
the text.
--
gnome-keyring password entry allows cursor outside of password entry
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
...
> dlopen("/usr/lib/python2.6/dist-packages/bzrlib/_chunks_to_lines_pyx.so", 2);
> import bzrlib._chunks_to_lines_pyx # dynamically loaded from
> /usr/lib/python2.6/dist-packages/bzrlib/_chunks_to_lines_pyx.so
...
> dlopen("/usr/lib/python2.6/dist-
I think downgrading it to a warning would be ok. I've noticed other
systems do the same thing.
That said, if you are upgrading 400 machines to a newer version of bzr,
can't that same mechanism be used to call 'bzr whoami' one time on each
of those machines? (It doesn't have to happen on every comm
** Changed in: bzr (Ubuntu)
Status: New => Confirmed
** Changed in: bzr (Ubuntu)
Assignee: (unassigned) => John A Meinel (jameinel)
--
Dead link in documentation to Glossary
https://bugs.launchpad.net/bugs/617503
You received this bug notification because you are a member of
** Changed in: bzr
Importance: Undecided => High
** Changed in: bzr
Status: New => Confirmed
--
bzr crashes on 'bzr status'
https://bugs.launchpad.net/bugs/617224
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
James Troup wrote:
> John A Meinel writes:
>
>> I think downgrading it to a warning would be ok. I've noticed other
>> systems do the same thing.
>>
>> That said, if you are upgrading 400 machines to a newer
** Changed in: juju
Importance: Undecided => High
** Changed in: juju
Status: New => In Progress
** Changed in: juju
Milestone: None => 2.9.16
** Changed in: juju
Assignee: (unassigned) => Joseph Phillips (manadart)
--
You received this bug notification because you are a mem
201 - 227 of 227 matches
Mail list logo
