from the bzr NEWS file, 0.90rc1 release::
* RevisionTree.get_weave is now deprecated. Tree.plan_merge is now used
for performing annotate-merge. (Aaron Bentley)
Unfortunately, the Tree object does not have a plan_merge() method
--
Does not work with bzr 1.6
https://bugs.launchpa
It looks like there's a fix on this branch::
http://bazaar.launchpad.net/~menesis/trac-bzr/menesis-dev/revision/50
I'm not sure it's the correct fix, though. I think it's removing
functionality to work around the problem. I'm not intimately familiar
with either bzr or trac, though, so that mi
Okay, try this patch. It gets ancestry information from the repository
instead of from the weave. It stops the tracebacks here.
** Attachment added: "Get ancestry from repo"
http://launchpadlibrarian.net/17989677/trac-bzr-get-ancestry.patch
--
Does not work with bzr 1.6
https://bugs.launchp
from the traceback, this looks to be a bug in bzrlib. I'm not sure how
to retarget this bug there, though:
Summary: TB4b0c976f patches.py:76:get_patch_names:MalformedPatchHeader:
Malformed patch header. No orig name
'diff --git
a/funambol-mozilla-plugin/extension/chrome/content/funambol/funamb
Here's my fix for the problem. The patch handling code in bzrlib is not
allowing "junk" before and after the individual patches in the file.
This patch makes that code more lenient.
This needs to be applied to bzr, not bzr-gtk. If someone knows how to
retarget this bug that would help out.
** A
New patch against lp:bzr (looks the same for 2.0.x) that gives
parse_patches() and the necessary functions that it calls an allow_dirty
parameter. allow_dirty turns on the new behaviour of allowing junk at
the beginning and end of individual patches within the patch file.
The default is to use t
Patch to bzr-gtk that uses the allow_dirty parameter to bzr to handle
patches with comments and other text than bzr puts in.
** Attachment added: "bzr-gtk-bzr-handle-patch-allow-dirty.patch"
http://launchpadlibrarian.net/38308517/bzr-gtk-bzr-handle-patch-allow-dirty.patch
--
bzr-handle-patch
lp:~toshio/bzr-gtk/handle-patch-fix has become corrupt.
New branch lp:~toshio/bzr-gtk/handle-patch-dirty
** Branch linked: lp:~toshio/bzr-gtk/handle-patch-dirty
** Branch unlinked: lp:~toshio/bzr-gtk/handle-dirty-patches
--
bzr-handle-patch doesn't like patch files containing "diff" lines bef
** Branch linked: lp:~toshio/bzr/allow-dirty-patches
--
bzr-handle-patch doesn't like patch files containing "diff" lines before each
patch
https://bugs.launchpad.net/bugs/502076
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubunt
** Branch linked: lp:~toshio/bzr-gtk/handle-dirty-patches
--
bzr-handle-patch doesn't like patch files containing "diff" lines before each
patch
https://bugs.launchpad.net/bugs/502076
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Two branches proposed for merge.
BTW, this seems like a better page for learning how to submit a branch for
merge from a bug report:
https://help.launchpad.net/Code/BugAndBlueprintLinks
it follows the workflow of someone who is starting from fixing an issue
in a bug report and links out to the p
I can't tell if phatch still has this problem from the comments but if
needed, here's a patch for it:
http://pkgs.fedoraproject.org/cgit/phatch.git/plain/phatch-pillow.patch
When Fedora switched over to Pillow about the same time as Ubuntu, a
group of us took care of generating all the patches
If this is the same bug as I'm experiencing using GNU tar on a different
system, this tarfile should reproduce the problem:
http://pypi.python.org/packages/source/n/nose/nose-1.1.2.tar.gz#md5=144f237b615e23f21f6a50b2183aa817
Note that I'm not using Ubuntu -- I just came across this bug report
whi
Note: there's now a backports module on pypi for this function:
https://pypi.python.org/pypi/backports.ssl_match_hostname/
However, it hasn't fixed this CVE upstream as fast as you have :-)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubu
Jelmer, this hasn't been fixed in paramiko upstream -- did you perhaps
mean to change paramiko (Ubuntu) to Fix Committed?
** Changed in: paramiko
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
15 matches
Mail list logo
