We never got around to this while 14.04 was the current LTS. It's fixed
in 16.04 LTS. Marking wontfix as it seems unlikely to be a priority
now.
** Changed in: protobuf (Ubuntu Trusty)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
** Changed in: ubuntuone-storage-protocol
Status: Fix Committed => 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/1275826
Title:
Version 2.5.0-5ubuntu1 breaks python code using th
This appears to have been fixed properly with the new C++-based module
in 2.6.0. I've just synced that (actually 2.6.1-1) into vivid after
checking that all our other remaining patches are obsolete.
** Changed in: protobuf (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug
This bug was fixed in the package ubuntuone-storage-protocol -
13.10-0ubuntu3
---
ubuntuone-storage-protocol (13.10-0ubuntu3) trusty; urgency=medium
* debian/patches/00_cpp-tests-check.patch:
- Avoid running the tests with the protobuf cpp module on newer
versions of proto
On Mon, 2014-02-24 at 19:12 +, Steve Langasek wrote:
> Just so I understand: does this mean that somewhere (where - server?),
> you are overriding the default behavior of the protobuf module by using
> this environment variable?
Yes. The cpp module makes things significantly faster on the ser
** Branch linked: lp:ubuntu/trusty-proposed/ubuntuone-storage-protocol
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1275826
Title:
Version 2.5.0-5ubuntu1 breaks python code using the cpp module
To
** Changed in: ubuntuone-storage-protocol
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1275826
Title:
Version 2.5.0-5ubuntu1 breaks python code using the
Hi Rodney,
> the path is relevant to the operation of ubuntuone-storage-protocol as it is
> being
> used on the servers (which are obviously not running on trusty yet). The same
> ubuntuone-storage-protocol code is run on both clients and servers, and so we
> need to
> ensure it does not break o
** Branch linked: lp:~dobey/ubuntuone-storage-protocol/no-cpp-tests
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1275826
Title:
Version 2.5.0-5ubuntu1 breaks python code using the cpp module
To ma
** Also affects: ubuntuone-storage-protocol
Importance: Undecided
Status: New
** Changed in: ubuntuone-storage-protocol
Importance: Undecided => High
** Changed in: ubuntuone-storage-protocol
Assignee: (unassigned) => Rodney Dawes (dobey)
** Changed in: ubuntuone-storage-protoc
ftbfs, see
https://launchpadlibrarian.net/167353879/buildlog_ubuntu-trusty-i386.ubuntuone-storage-protocol_13.10-0ubuntu2_FAILEDTOBUILD.txt.gz
** Changed in: ubuntuone-storage-protocol (Ubuntu)
Importance: Undecided => High
** Changed in: ubuntuone-storage-protocol (Ubuntu)
Status: New
> by an environment variable
Oh, that's the PROTOCOL_BUFFERS_PYTHON_IMPLEMENTATION=cpp thing in run-
tests? I just looked for an env variable and found this, that looks very
plausible. So u1-s-p needs to drop that then, or perhaps better
conditionalize it on the version of protobuf that is install
@Steve, the path is relevant to the operation of ubuntuone-storage-
protocol as it is being used on the servers (which are obviously not
running on trusty yet). The same ubuntuone-storage-protocol code is run
on both clients and servers, and so we need to ensure it does not break
on either place (w
Yes, this is a bug in protobuf for allowing the behavior of the library
to be permuted in an unsupported way by an environment variable.
But equally, it is a bug in ubuntuone-storage-protocol for testing paths
that are irrelevant to its operation.
u1-storage-protocol should be fixed to drop the g
@Martin, that's interesting, since that code is generated by protobuf-
compiler. Looks like it also needs to be updated to not generate code
that imports that module directly. But I think that's a different bug
than this one specifically.
--
You received this bug notification because you are a me
Seems this was not quite sufficient? It now fails differently:
Traceback (most recent call last):
File "/usr/bin/u1trial", line 40, in
main()
File
"/usr/lib/python2.7/dist-packages/ubuntuone-dev-tools/ubuntuone/devtools/runners/__init__.py",
line 277, in main
suite = test_runner.get
This bug was fixed in the package protobuf - 2.5.0-5ubuntu2
---
protobuf (2.5.0-5ubuntu2) trusty; urgency=medium
* Remove cpp_message.py from the python bindings package, since it requires
the C++ module implementation that we're no longer shipping.
LP: #1275826.
-- Steve L
** Branch linked: lp:ubuntu/trusty-proposed/protobuf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1275826
Title:
Version 2.5.0-5ubuntu1 breaks python code using the cpp module
To manage notificati
18 matches
Mail list logo
