conservative attitude.
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
we fixed it while we didn't.
keystone 2014.1.2.1 was just uploaded to fix that. I'm sorry for the
inconvenience this has caused.
No worries Thierry, mistakes do happen.
Though I've already upgraded oslo.config, oslo.messaging, and pycadf. I
hope that's not an issue.
Cheers,
Thomas Goirand
, comment or whatever that may help would be appreciated.
Cheers,
Thomas Goirand (zigo)
P.S: By the way, there's issues with python-oslo.utils with Python 3.4,
after solving the above problem...
___
OpenStack-dev mailing list
OpenStack-dev
of compass-bootstrap-sass-plugin within Horizon.
Thoughts anyone?
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
recently too, as it became a way too
aggressive. I very much prefer to use my laptop to use git review than
having to bounce around servers. :(
Are their alternative IPs that I could use for review.openstack.org?
Cheers,
Thomas Goirand (zigo)
P.S: If a Chinese official read this, an easy way
Julien on that one.
Cheers,
Thomas Goirand (zigo)
P.S: It's to be noted that python-memcached is called
python-memcache in Debian, because that's the name of the module when
doing imports...
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
,
Thomas Goirand (zigo)
Original Message
Subject: [PKG-Openstack-devel] Bug#755651: [openstack-dev] [horizon]
Support for Django 1.7: there's a bit of work, though it looks fixable
to me...
Resent-Date: Wed, 10 Sep 2014 20:45:23 +
Resent-From: Raphael Hertzog hert...@debian.org
...
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
all of
OpenStack to do it there as well.
And no, there's no good excuse here...
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
they have tons of wrong reasons. If they don't want to change
anything, then we can only try to work around the issue, and never use
the embedded version.
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
not
interesting for the OpenStack project.
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
in the future.
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
of 1.4.0, so that it is
greater than 1.4.0.0~a5 (to avoid adding an EPOC, which is ugly and
annoying to maintain). It's going to be the same version though, I just
need to add a new tag, which isn't much of a problem for me (since I use
a git based workflow).
The 1.4.0.0a5 is confusing... :(
Thomas
Hi,
Please see this:
https://review.openstack.org/122993
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
.
That's very good, thanks for taking care of this. However, there's
nothing extraordinarily here. Think about this fact: the Linux kernel
is *always* backward compatible. I don't think you'll argue that
requests is more complex than the kernel.
On 09/18/2014 10:20 PM, Ian Cordasco wrote:
Thomas Goirand
.
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
and added work.
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
directly go back to the idea of using NodeJS then, because that
would be exactly the same.
I much prefer option 1/ where lesscpy gets better and does what's needed
for the project. :)
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
On 12/16/2013 10:32 PM, Jaromir Coufal wrote:
This is important note. From information architecture and user
interaction point of view, I don't think it makes sense to keep all the
three tabs visible together (Project, Admin, Infrastructure). There are
lot of reasons, but main points:
*
Hi,
Sid has Django 1.6. Is it planned to add support for it? I currently
don't know what to do with the Horizon package, as it's currently
broken... :(
Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
On 12/20/2013 04:39 PM, Matthias Runge wrote:
On 12/19/2013 04:45 PM, Thomas Goirand wrote:
Hi,
Sid has Django 1.6. Is it planned to add support for it? I currently
don't know what to do with the Horizon package, as it's currently
broken... :(
Thomas
Yes, there are two patches available
/#django-conf-urls-defaul
ts
-Tim
Indeed, this was the problem. Thanks Tim, I have been able to upload the
package to Sid, without breaking Wheezy backport, thanks to this. \o/
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev
On 12/24/2013 07:49 PM, Sebastien Han wrote:
Hello everyone,
I’ve been working on a new feature for Devstack that includes a native
support for Ceph.
The patch includes the following:
* Ceph installation (using the ceph.com repo)
* Glance integration
* Cinder integration (+ nova virsh
On 11/18/2013 08:19 PM, Salvatore Orlando wrote:
Basically I think we can assume test machines have access to the
Internet
IMO, we should assume test machines doesn't. It's a too dangerous
assumption to make.
I assume you want
to check servers such as www.google.com http://www.google.com are
Hi,
bootstrap-form was rejected by the Debian FTP masters, and I have no
reply from upstream to fix the licensing. I'm not sure what to do next.
Any advice? Could we just stop using bootstrap-form?
Thomas Goirand (zigo)
P.S: Below is the reject message from the FTP masters, and my follow-up
the latest release of bootstrap-form. I would
very much have preferred to have a responsive upstream and/or an
upstream that does things correctly... :(
Anyway, thanks Carl for the pointer. That's really helpful!
Cheers,
Thomas Goirand (zigo)
On 12/27/2013 04:43 PM, Carl Perry wrote:
The github repo has
with Django 1.4 1.5
(which would be the best way forward for me...)?
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 12/30/2013 06:02 PM, Robert Collins wrote:
On 30 December 2013 22:51, Thomas Goirand z...@debian.org wrote:
IMO, switching to ext4 is a very bad idea, because ext4 doesn't support
online resize2fs, while ext3 does, so switching to ext4 is breaking
cloud-init!!!
It supports it just fine
licensing.
Thoughts welcome!
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 01/03/2014 01:03 AM, Ben Nemec wrote:
On 2014-01-01 00:33, Thomas Goirand wrote:
Hi,
I was wondering if it would be possible for NoVNC to switch from
websockify to sockjs-client, which is available here:
https://github.com/sockjs/sockjs-client
This has the advantage of not using flash
On 01/02/2014 03:33 PM, Matthias Runge wrote:
On 12/30/2013 08:31 AM, Thomas Goirand wrote:
Hi,
Currently, in the global-requirements.txt, we have:
Django=1.4,1.6
django-bootstrap-form
However, django-bootstrap-form fail in both Django 1.4 and Django 1.6.
What's the way forward? Would
with concurrent.futures (they would share the same files). I'd
be very happy to have upstream point of view, and probably some help.
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin
On 01/04/2014 07:53 AM, Joshua Harlow wrote:
So another idea that was talked about on IRC.
Taskflow exposes entrypoints for these storage backends (like your storage
callback/interface idea).
It currently provides 3 such 'default' backends [sqlalchemy, file/dir
based, in-memory -- mainly
On 01/13/2014 10:38 PM, Sean Dague wrote:
I know we've been here before, but I want to raise this again while
there is still time left in icehouse.
I would like to propose that the Nova v3 API removes the XML payload
entirely. It adds complexity to the Nova code, and it requires
duplicating
1.3? I haven't seen issues building (most of not all)
core packages using WebOb 1.3. Did I miss the obvious?
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo
On 02/03/2014 11:31 PM, Doug Hellmann wrote:
On Mon, Feb 3, 2014 at 7:31 AM, Monty Taylor mord...@inaugust.com
mailto:mord...@inaugust.com wrote:
On 02/03/2014 11:45 AM, Thomas Goirand wrote:
Hi,
Sorry if this has been already discussed (traffic is high
will work on Debian support in xenserver-core.
Cheers,
Thomas Goirand (zigo)
For reference, see http://bugs.debian.org/738322 and
https://bugs.launchpad.net/bugs/1278352
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
about this situation, and hope it can be solved. I
warmly welcome Citrix to work with me (again) to fix this quickly.
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin
have a *serious* look at this patch, and explain
why it's not ok for it to be approved? If nobody says why, then could
this be approved, so we can move on?
Cheers,
Thomas Goirand (zigo)
[1]
http://anonscm.debian.org/gitweb/?p=openstack/neutron.git;a=blob;f=debian/patches/fix-alembic-migration
On 02/21/2014 06:13 AM, Vincent Untz wrote:
Le jeudi 20 février 2014, à 12:02 -0800, Armando M. a écrit :
No action on a negative review means automatic expiration, if you lose
interest in something you care about whose fault is that?
I beg to disagree. If we let patches go to automatic
Hi,
It's been now more than 40 days that this patch needs review:
https://review.openstack.org/#/c/67096/
Could some core reviewers have a look, and eventually approve the patch?
It's very important to me, since Horizon is currently considered
non-free in Debian, due to the minified javascript
On 02/28/2014 01:18 PM, Thomas Goirand wrote:
Hi,
It's been now more than 40 days that this patch needs review:
https://review.openstack.org/#/c/67096/
Could some core reviewers have a look, and eventually approve the patch?
It's very important to me, since Horizon is currently considered
On 02/28/2014 03:10 PM, Thomas Goirand wrote:
On 02/28/2014 01:18 PM, Thomas Goirand wrote:
Hi,
It's been now more than 40 days that this patch needs review:
https://review.openstack.org/#/c/67096/
Could some core reviewers have a look, and eventually approve the patch?
It's very important
welcome,
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 03/02/2014 12:03 PM, Thomas Goirand wrote:
Hi,
About a week ago, the maintainer of SQLAlchemy uploaded version 0.9.3 in
Debian Sid. This of course broke a lot of OpenStack packages, including
python-migrate.
I do not intend to let this continue on for 7 months like it happened
, fearing to break something.
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 03/03/2014 11:24 AM, Thomas Goirand wrote:
It looks like my patch fixes the first unit test failure. Though we
still need a fix for the 2nd problem:
AttributeError: 'module' object has no attribute 'AbstractType'
Replying to myself...
It looks like AbstractType is not needed except
On 03/03/2014 01:14 PM, Thomas Goirand wrote:
On 03/03/2014 11:24 AM, Thomas Goirand wrote:
It looks like my patch fixes the first unit test failure. Though we
still need a fix for the 2nd problem:
AttributeError: 'module' object has no attribute 'AbstractType'
Replying to myself
On 03/03/2014 11:17 PM, David Ripton wrote:
On 03/02/2014 03:12 AM, Thomas Goirand wrote:
On 03/02/2014 12:03 PM, Thomas Goirand wrote:
I hope to get support from core reviewers here, so that we can fix-up
the SQLA 0.9.x compat ASAP, preferably before b3. Of course, I'll make
sure all we do
On 03/04/2014 06:13 PM, Julien Danjou wrote:
On Tue, Mar 04 2014, James E. Blair wrote:
If there aren't objections to this plan, I think we can propose a motion
to the TC with a date and move forward with it fairly soon.
That plan LGTM, and +1 for OFTC. :)
Same over here, +1 for OFTC.
Hi,
I just tried this:
https://review.openstack.org/#/c/79129/
and it seems everything works. \o/
Shall we lift the SQLA cap right away?
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http
solve these.
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 03/14/2014 05:20 AM, John Dennis wrote:
On 03/13/2014 12:31 AM, Thomas Goirand wrote:
Hi,
Since Havana, I've been ignoring the 5 unit test failures that I always
get. Though I think it'd be nice to have them fixed. The log file is
available over here:
https://icehouse.dev
On 03/14/2014 02:06 AM, Sean Dague wrote:
On 03/13/2014 12:31 PM, Thomas Goirand wrote:
On 03/12/2014 07:07 PM, Sean Dague wrote:
Because of where we are in the freeze, I think this should wait until
Juno opens to fix. Icehouse will only be compatible with SQLA 0.8, which
I think is fine. I
, and I get some unit
tests errors (see below).
Guys, could we stop having this kind of regressions, and make Selenium
tests not mandatory? They aren't runnable in Debian.
Cheers,
Thomas Goirand (zigo)
==
ERROR: Failure
On 03/14/2014 09:11 PM, Julie Pichon wrote:
On 14/03/14 11:31, Thomas Goirand wrote:
Hi,
A few months ago, I raised the fact that Selenium *CANNOT* be a hard
test-requirements.txt build-dependency of Horizon, because it is
non-free (because of binaries like the browser plug-ins not being
in time for new packages.
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 03/18/2014 02:51 PM, Andreas Jaeger wrote:
On 03/18/2014 07:14 AM, Thomas Goirand wrote:
Hi,
We're now 1 month away from the scheduled release date. It is my strong
opinion (as the main Debian OpenStack package maintainer) that for the
last Havana release, the freeze of dependency
On 03/18/2014 06:12 PM, Thierry Carrez wrote:
Thomas Goirand wrote:
We're now 1 month away from the scheduled release date. It is my strong
opinion (as the main Debian OpenStack package maintainer) that for the
last Havana release, the freeze of dependency happened really too late,
creating
On 03/19/2014 02:42 AM, Nikhil Manchanda wrote:
Thomas Goirand writes:
On 03/18/2014 06:12 PM, Thierry Carrez wrote:
Thomas Goirand wrote:
[...]
Trove turned out to not be participating in global requirements, and
has 3 items outside of requirements.
Could you list them?
Hi Thomas
On 03/19/2014 09:25 PM, victor stinner wrote:
Hi,
According to the following table, paste is blocking many OpenStack servers to
be ported to Python 3:
https://wiki.openstack.org/wiki/Python3
I had a look to this, and found it weird that ironicclient is marked as
supporting Python3,
assumption, so
the test failures aren't particularly helpful.
Oh, ok, thanks!
I've added python-memcache *AND* memcached as build-dependency, then
everything is back to working! :)
Thanks again for the above help,
Cheers,
Thomas Goirand (zigo
Hi,
The current version of python-hacking wants python-oslo.sphinx, but
we're moving to python-oslosphinx. In Debian, I made python-oslo.sphinx
as a transition empty package that only depends on python-oslosphinx. As
a consequence, python-hacking needs to be updated to use
python-oslosphinx,
On 03/22/2014 12:58 AM, Joe Gordon wrote:
So it sounds like we need:
* Hacking 0.8.1 to fix the oslo.sphinx oslosphinx issue for Icehouse.
Since we cap hacking versions at 0.9 [1] this will get used in icehouse.
* Hacking 0.9 to release all the new hacking goodness. This will be
:
https://review.openstack.org/82298
I'd really like to have it included in the next stable release of
Horizon. I don't think this one is hard to deal with, and I hope it will
go through even with the lack of time.
Cheers,
Thomas Goirand (zigo)
P.S: I'm not registered to the openstack-stable-maint
! :) ), then
would =0.8 or =0.4,!=0.6,!=0.7 be better?
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 03/29/2014 01:07 AM, Sean Dague wrote:
On 03/28/2014 12:50 PM, Thierry Carrez wrote:
Thierry Carrez wrote:
Julien Danjou wrote:
On Thu, Mar 27 2014, Thomas Goirand wrote:
-happybase=0.4,=0.6
+happybase=0.8
Good for me, and Ceilometer is the only one using happybase as far
as I know
yourself. We'll see if I can make it to Atlanta, and organize
something later on.
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 04/01/2014 04:03 AM, Jeremy Stanley wrote:
On 2014-03-31 10:55:06 +0200 (+0200), Thierry Carrez wrote:
No miracle here... All slots are pretty full as expected. I think our
best bet is still the 30-min morning break on Wednesday or Thursday at
10:30am.
Would finding an available room for
something like this instead?
-# Example:
-# connection = mysql://root:pass@127.0.0.1:3306/neutron
+# Example: connection = mysql://root:pass@127.0.0.1:3306/neutron
It'd be nice if these changes could make it to the Icehouse release.
Thoughts anyone?
Cheers,
Thomas Goirand (zigo
On 04/02/2014 11:01 PM, Solly Ross wrote:
IMHO, having Example: on a separate line from the actual option is a lot
easier for humans:
you just delete a single character or use your editor-of-choice's uncomment
macro to activate
a line.
Please re-read what I wrote. There's things like:
#
On 04/02/2014 06:38 PM, Salvatore Orlando wrote:
Hi Thomas,
it probably won't be a bad idea if you can share the patches you're
applying to the default configuration files.
I think all distros are patching them anyway, so this might allow us to
provide mostly ready to use config files.
need my help.
Could you please point to me to the list of needed patches? I would need
to keep them separated, in debian/patches, rather than pulling from a
different git repository.
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
on, on Debian
Wheezy (backports) and in Debian Sid [1]. Currently all of TripleO but
tripleo-image-elements is uploaded to Debian Experimental. I also have
Trusty packages (it's part of my build process).
If all, I need feedback. I'm quick to fix things if reported correctly.
Cheers,
Thomas Goirand
archive, the plan is still to use [1] Debian PPAMAIN
when this will be available (please do not confuse with Ubuntu PPA, this
is a very different concept), and to keep maintaining the above
non-official repositories until then.
Cheers,
Thomas Goirand (zigo)
[1] https://lists.debian.org/debian-devel
).
I haven't made up my mind yet if we should release Debian Jessie with
OpenStack Icehouse (to have the same release as the Ubuntu LTS), or with
the J release. I'd be happy to gather comments and suggestions about
it, and discuss about it at the HK summit.
Cheers,
Thomas Goirand (zigo
in debian/patches whenever
possible, because this is a major pain.
Your thoughts?
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
did in the packaging, and I wanted to
avoid reporting some false positive.
On 17 October 2013 20:16, Thomas Goirand z...@debian.org wrote:
Hi,
...
These appear in both Sid and Wheezy backports.
* Nova
==
Only a single: FAIL
On 10/17/2013 09:11 PM, Monty Taylor wrote:
I understand what you are saying and I also understand your frustration.
However, OpenStack does not, as of yet, support SQLAlchemy 0.8, and as
you can see, the requirements file does, in fact, communicate reality,
we depend on 0.8.
It does, at the
to not miss that one.
Cheers,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 10/18/2013 12:05 AM, Roman Podolyaka wrote:
4. Everyone's life would be much easier, if we dropped migrations
support for SQLite. Alembic doesn't support ALTER for SQLite at all on
purpose. And I would really like us to switch to using of Alembic in the
following releases.
Except that if
,
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 10/18/2013 03:35 AM, Clint Byrum wrote:
Excerpts from Thomas Goirand's message of 2013-10-17 08:33:44 -0700:
See above. Also, remember that package maintainers are a few (me alone
for Debian, maybe 5 people in Ubuntu/Canonical) fighting hundreds of
developers who wish not to be disturbed.
On 10/18/2013 02:05 AM, Cristian Tomoiaga wrote:
Hello,
It seems Django 1.6 switched from Pickle to Json for session serialization.
https://docs.djangoproject.com/en/1.6/topics/http/sessions/#session-serialization
For anyone getting the error about Token not being serializable, just
add
On 10/18/2013 02:06 AM, Clint Byrum wrote:
A link to instructions on setting up a wheezy box for this testing would
be helpful.
Just install a minimal Wheezy machine, add my repositories (using the
Jenkins one at *.pkgs.enovance.com), then do apt-get install
openstack-toaster. I'll be trying to
. Though that's of course not enough for the
Debian FTP masters.
Your thoughts?
Cheers,
Thomas Goirand (zigo)
Original Message
Subject: [Openstack-devel] python-troveclient_0.1.4-1_amd64.changes REJECTED
Date: Sat, 19 Oct 2013 04:00:19 +
From: Luke Faraone ftpmas...@ftp
On 10/19/2013 08:24 PM, Monty Taylor wrote:
On 10/19/2013 05:49 AM, Michael Still wrote:
On Sat, Oct 19, 2013 at 7:52 PM, Clint Byrum cl...@fewbar.com wrote:
I suggest that we just put Copyright headers back in the source files.
That will make Debian's licensecheck work fairly
On 10/19/2013 11:50 PM, Jeremy Stanley wrote:
On 2013-10-19 23:29:28 +0800 (+0800), Thomas Goirand wrote:
Though the Debian FTP masters seems to insist on having correct
copyright holders in debian/copyright, and I am a bit lost after the 2
rejects I just had.
Well, this is still a fuzzy
On 10/20/2013 05:41 PM, Joe Gordon wrote:
http://ftp-master.metadata.debian.org/changelogs//main/l/linux/linux_3.11.5-1_copyright
Not even the kernel itself has a complete list of all the copyright owners.
best,
Joe
Well, good luck finding all the copyright holders for such a large and
to be a bit more accurate than
second-guessing through git log or reading a few source code files
which represent a wrong view of the reality.
Any thoughts?
Thomas Goirand (zigo)
P.S: I asked the FTP masters to write in this thread, though it seems
nobody had time to do so
to be fixed. A
copyright-holder.txt file would fix it, and I'm guessing that it's
existence only would push companies to add themselves in...
Thomas Goirand (zigo)
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org
On 10/22/2013 04:55 AM, Mark McLoughlin wrote:
Talk to the Trove developers and politely ask them whether the copyright
notices in their code reflects what they see as the reality.
I'm sure it would help them if you pointed out to them some significant
chunks of code from the commit history
On 10/22/2013 05:06 AM, Michael Basnight wrote:
so if this is sufficient, ill fix the copyright headers.
Please do (and backport that to 2013.2...)! :)
Thomas
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
On 10/22/2013 04:48 AM, Mark McLoughlin wrote:
On Tue, 2013-10-22 at 01:55 +0800, Thomas Goirand wrote:
On 10/21/2013 09:28 PM, Mark McLoughlin wrote:
In other words, what exactly is a list of copyright holders good for?
At least avoid pain and reject when uploading to the Debian NEW queue
On 10/22/2013 08:09 AM, Monty Taylor wrote:
b) Thomas should put in debian/copyright what is in our headers, and
should consider them, as they are in our source tarballs, to be correct
c) If Thomas, or anyone else, considers our header attribution to be
incorrect, he or she should submit a
On 10/22/2013 04:45 AM, Mark McLoughlin wrote:
By improve clarity, you mean compile an accurate list of all
copyright holders? Why is this useful information?
Sure, we could also improve clarity by compiling a list of all the
cities in the world where some OpenStack code has been authored
On 10/22/2013 02:12 AM, Jeremy Stanley wrote:
On 2013-10-22 01:45:13 +0800 (+0800), Thomas Goirand wrote:
[...]
The main problem I was facing was that troveclient has a few files
stating that HP was the sole copyright holder, when it clearly was
not (since I have discussed a bit with some
a decision... :)
Cheers,
Thomas Goirand (zigo)
P.S: CC-ing the Debian release team list, to get their opinion.
___
OpenStack-dev mailing list
OpenStack-dev@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
On 10/23/2013 06:32 AM, Michael Basnight wrote:
On Oct 22, 2013, at 10:35 AM, Michael Basnight wrote:
Top posting cuz im a baller. We will get this fixed today. PS clint i like
the way you think ;)
https://review.openstack.org/#/c/53176/
Now that this is merged, and there is no
1 - 100 of 662 matches
Mail list logo
