@HelderPereira
Had one not voiced his opinion, shall he not have a voice in the matter.
@Krzysztof Klimonda
Well all here, while complaining ravishingly sometimes, very much appreciate
the community effort going into Ubuntu.
What you have highlighted though, is the core of the issue: Backports a
@Scott Kitterman
You do realize that Evolution is THE application on a corporate desktop? The
only market where it is feasible for Linux to generate desktop revenue!
Backporting to Maverick is nice to have. Backporting to Lucid is essential.
Backporting essential apps via PPA's is ok for normal
@Steve
You seem to be correct, I was confused by 2.32 listed as submitted for Maverick
on 2010-10-16:
https://launchpad.net/~jacob/+ppa-packages
I's venture to guess 2.32 is still unstable so he limited public access
or so.
--
Please back port Evolution 2.32 to lucid LTS and maverick
https://bu
@Leon
Even more so for Lucid - just remember that Lucid is the "Ubuntu" for the
business market. _Official_ backport for Lucid is a need there. Lucid is still
stuck at 2.28 !!!
On the other hand an official backport for Maverick is just a
convenience - Jacob's PPA is OK for most casual users.
Could a developer explain what the exact status of this bug is supposed
to be in Jaunty? Since it's been marked as fixed, people have reported
rather contradictory results: should they file separate bugs on a per-
driver basis?
Myself I'm able to experience it with Intel i915, driver 2.7.1, EXA. I
Nice ! Thanks.
--
Please backport libmicrohttpd4 (0.3.1)
https://bugs.launchpad.net/bugs/240136
You received this bug notification because you are a member of Ubuntu
Backports Testing Team, which is subscribed to Hardy Backports.
--
ubuntu-backports mailing list
ubuntu-backports@lists.ubuntu.co
I'd like it to! But given the amount of changes undergone by the source
code, I doubt it will be accepted. This is a completely new release. Not
speaking of the libmicrohttpd4 dependency that should be introduced...
What do you think? Easier to make a backport, isn't it?
--
Please backport gnunet
Public bug reported:
GNUnet is the secured peer-to-peer framework of the GNU project. It has
just released a 0.8.0 version that breaks network protocol compatibility
with 0.7.3, which is packaged in Hardy. Thus, GNUnet in Hardy is almost
useless since less and less peers will be in the old network
See bug 243514 about backporting GNUnet.
--
Please backport libmicrohttpd4 (0.3.1)
https://bugs.launchpad.net/bugs/240136
You received this bug notification because you are a member of Ubuntu
Backports Testing Team, which is subscribed to Hardy Backports.
--
ubuntu-backports mailing list
ubuntu
Public bug reported:
This is a prerequisite to backport gnunet 0.8.0; before considering it,
I guess it can be good to see whether there's any problem with
libmicrohttpd.
libmicrohttpd3 (0.2.0-1) is in Hardy repos, libmicrohttpd4 (0.3.1-1) is in
Intrepid (together with libmicrohttpd3).
In Hardy,
Fixed in Hardy.
** Changed in: gnunet-gtk (Ubuntu)
Status: Fix Committed => Fix Released
--
gnunet-gtk crashed with SIGSEGV
https://bugs.launchpad.net/bugs/158706
You received this bug notification because you are a member of Ubuntu
Backports Testing Team, which is subscribed to Gutsy Bac
Just leave it closed. ;-)
It would be better to concentrate on the new 0.7.4 (replacing 0.8.0) that will
soon introduce a protocol breakage than working on a fix for two months. 0.7.2
will not have any value when 0.7.4 is out.
If 0.7.4 does not enter Hardy, I'll open a new bug report to backport
12 matches
Mail list logo