I have opened bug 220385.
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu
Security concerns: while people using Envy are already directly
installing software from a non-official repository, if they switch to
EnvyNG, they are no less safe. However, since EnvyNG is installable
from the repo directly now, it is likely there will be more people
installing it, which means mo
stefan, was my, norsetto's, and scottk's n'acks not enough? Do we need
to actually use the word "veto" now, rather than saying "we don't want
this to go in"?
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
You received this bug notification because you are a member of Ubuntu
Bugs, which
please close freeze exceptions in uploads... otherwise the karma is all
mine :P. Closing.
** Changed in: ubuntu
Status: Fix Committed => Fix Released
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: ubuntu
Status: Confirmed => Fix Committed
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
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
https://li
Thanks, uploaded.
I'll take care of the bribing, thanks guys. ;-)
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
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
https:/
ok, since I haven't seen veto's here, my ACK together with Luke's make
two, setting to confirmed.
Oh, please make sure to talk to archive-admins when uploading, thanks.
** Changed in: ubuntu
Status: New => Confirmed
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
You received th
If SRUs are required, I will be happy to assist with them (being a
member of the sru-verficiation team) and help sponsoring the fixes.
I think its better to have the package in the archive and to be able to
issue regular SRUs that people get through the regular channels than if
we do not provide a
Sarah: Envyng won't need to be updated unless there are bugs (reported
by users) like any other package. When a new driver is released, I will
only have to update my PPA (without touching EnvyNG).
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
You received this bug notification because
How many uploads of EnvyNG will you want to make before release?
By the planet spam (which I still think is ridiculous - a lot of people
really don't care each time envy gets updated, especially when they
don't use it - but i digress), it appears that this is a package which a
high number of uploa
Luke: thank you very much. I have corrected envyng.list as you
suggested.
Daniel, Bryce, Michael: the correction is in revision 39 of my bzr
branch.
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
You received this bug notification because you are a member of Ubuntu
Bugs, which is subsc
Alberto: can you take a look at envyng.list and see what needs to be
fixed?
Bryce and Michael: would you take over the task of helping Alberto with
uploads and SRUs (if necessary) together with me?
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
You received this bug notification becau
I'm willing to give this an ack, due to what it offers users for newer
hardware/drivers in the future, especially for an LTS. A couple of
things I noticed with the envyng-core branch though.
In envyng.list, as far as I understand it, PPAs only put packages in main,
there is no restricted.
There i
Although this hasn't gone through the standard 'revu' process, it has
had eyes on it from several folks that are core-dev which should be
equivalent if not better. I've corresponded with Alberto over a few of
these things that went into this, and he is very committed to providing
an interim soluti
I've been thinking about this yesterday when I was under the shower. My
conclusion is, that it's very late in the cycle for a new package, which
worries me quite a bit. However it would imho still be very nice to
have. Now, if someone with upload rights would promise commitment to
EnvyNG (i.e. prom
I won't object if someone else from motu-release wants to ack this.
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
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
https:
- Regarding bzr: you can't really say that people have not looked at it yet. I
mentioned a couple of times who helped with the integration of it. Also
regarding "standarized on": lots of pieces that are developed for the distro
are in bzr - how is it relevant to the FFe discussion?
- Regarding
On Wednesday 09 April 2008 10:06, Daniel Holbach wrote:
> The source is in bzr ...
Chosing to use tools that aren't the ones we've standarized on will limit the
number of people who look at it.
I'm against adding this to Universe.
1. It's only purpose is to support proprietary software.
2. B
The source is in bzr and was worked on for weeks collaboratively. If you
want the email threads of ~70 emails about the review of it, I can
forward it to you.
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
You received this bug notification because you are a member of Ubuntu
Bugs, which
I just looked on REVU and there's still no package.
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
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
https://lists.ubuntu.c
Scott: Ben Collins, Michael Vogt, Bryce Harrington and I reviewed the
package not only for the packaging but the code base. I subscribed them
all to the bug.
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
You received this bug notification because you are a member of Ubuntu
Bugs, which
Based on the MOTU sponsoring process, nothing has been submitted to be
reviewed.
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
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.ubu
If the decision is to review it some more, it'd be good to know what
should be reviewed or what is unclear.
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
For background, some of the discussion/plans were captured at
https://wiki.ubuntu.com/EnvyNG. Not sure if that's still 100% up to
date though.
I've reviewed the Xorg portions of the package in depth, and the
remaining portion of the code in brief. All issues I raised were
addressed and I have no
I still don't see a compelling rationale for a new package now vice
using the regular review process for Intrepid and then backporting.
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
"Ben Collins, Bryce Harrington, Daniel Holbach and Michael Vogt reviewed
EnvyNG."
The packaging is really simple, but that's not what took so long to be
reviewed - it was the integration of the code.
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
You received this bug notification beca
So, this has been in the making from December.
Did i miss the correspondence over this package being up for review back
in December or so? I'm aware that i'm not subscribed to the REVU list,
but I would have expected to see something in #ubuntu-motu, as it's a
commonly used package.
If so, I apo
Stefan:
The md5sums are still there but are no longer used (the md5 were necessary when
used to EnvyNG built the packages locally). I can comment out that part of the
code if you deem it necessary.
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
You received this bug notification becau
Ok, I've taken a closer look now.
First off, there is no policy problem: The package itself doesn't do anything
that's not coming from an official mirror in the *packaging*. Programs that the
package ships do so, but that's perfectly allowed (a webbrowser with javascript
also downloads code fro
1) Directory: pool/multiverse/g/googleearth-package
2) I don't see how it could go into 'partner' - 'partner' is for Business
partners of Canonical.
3) Alberto agreed to send out a notice to solicit testing of packages in PPA.
Lots of work has been put into making EnvyNG a maintainable solution
w
I tend to agree with Scott on this. This might well be one of the most
used universe packages and stuffing this in at the last moment without
any evidence of any testing doesn't look very wise.
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
You received this bug notification because you
Thinking about this some more, I think Canonical sponsoring this through
Partner would probably be the best solution.
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bu
In the case of other package like the nonfree Flash, we upload a set
package based on md5sum. When Flash gets updated, we update the package
via -proposed and then -updates. IIRC the Google packages are distributed
by Canonical in Partner and are not part of Ubuntu.
A PPA is not an Ubuntu rep
The packaging is already done, it's in bzr too.
The old envy used to build kernel module packages from the binary blobs
on the net. What EnvyNG does is rely on packages that are distributed
over PPA. This makes life easier for people who rely on the latest and
greatest drivers to make use of their
Scott:
Just to make things clear, we've been working on this since December 2007. It's
not something we decided yesterday.
If by "3rd party repositories" you refer to my PPA, I really fail to see
your point.
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
You received this bug notifica
>The code was reviewed and we worked together so that EnvyNG could not
>cause any problem to Ubuntu. Furthermore EnvyNG relies upon my PPA
>(reviewed by Ben Collins), thanks to which I can update the versions of
>the drivers without having to update EnvyNG. The drivers in the repo use
>DKMS and don
What significant advantage is there to stuffing this in at the last minute
over an early backport fron Intrepid?
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs ma
I don't think the package needs to be perfect, but there ought to at least
be a draft.
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
I have changed the status of my branches.
A brief explanation:
This branch contains the main program, the textual interface and the
translations:
https://code.launchpad.net/~albertomilone/envy/envyng-core
This branch contains only the QT4 interface:
https://code.launchpad.net/~albertomilone/envy
Scott: iirc it's the other way round, first FFe then reviews. Or do I
remember s.th. incorrectly?
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubunt
No, the old Envy never was in the archive, but one of the most used 3rd
party apps around: http://www.albertomilone.com/nvidia_scripts1.html
Alberto put a lot of effort into getting https://wiki.ubuntu.com/EnvyNG
into shape and comply with ideas Ben, Michael and Bryce had about the
topic.
--
FFe
We're supposed to have a reviewed and tested package before we do the FFe.
I'd suggest whoever is packaging this upload to REVU so it's clear what's
being discussed.
Is the old Envy in the archive?
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
You received this bug notification bec
Sorry Alberto, can you please update the branch status in LP then?
https://code.launchpad.net/~albertomilone/envy/envyng/+edit
** Description changed:
Ben Collins, Bryce Harrington, Daniel Holbach and Michael Vogt reviewed
EnvyNG and would like to see it in Universe for Hardy:
- - https://cod
Sure. ACK #1.
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
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
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Can you exclude this branch (since I've moved its content to envyng-core),
please?
https://code.launchpad.net/~albertomilone/envy/envyng
Thanks
--
FFe for EnvyNG
https://bugs.launchpad.net/bugs/210112
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
45 matches
Mail list logo
