n Experimental,
so that I can package Neutron Newton Beta 1.
Cheers,
Thomas Goirand (zigo)
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
> independently of OVS itself. That way a proper verison could be
> released that includes Python 3 support.
>
> --
> Russell Bryant
I'd very much welcome such a move, and could more easily contribute to
the python module packaging
t; so it seems like a poor choice for anything in Debian.
That's ok though. There's nothing you can do with the Python version
numbers which are kind of incompatible with what we do in Debian (the
char ~ is forbidden in PyPi). So the way to do it in Debian is to rename
2.6.0.dev1 as 2.6.0~
art of the stable-proposed-updates procedure. Please
open a bug against the release.debian.org pseudo-package, and get
approval by the release team (when writing such bug report, you must
send a debdiff between the version in Wheezy and the proposed version).
When the release team has approved you
Ben,
Are you going to work on this issue? I just discover it, and if it isn't
fixed fast enough, it's going to pull Neutron out of Jessie as well. So
we need a fix soon.
Would you accept that I nmu the fix using the provided patch in the BTS?
Cheers,
Thomas Goi
.
>>
>> Simon, would you be able to take care of this?
>
> Sure, I have uploaded a fresh package which attempts to do so.
> It contains no other changes.
Simon,
Did you ask for an unblock to the release team?
Cheers,
Thomas Goirand (zigo)
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
On 12/19/2014 10:25 PM, Simon Horman wrote:
> On Fri, Dec 19, 2014 at 06:39:39PM +0800, Thomas Goirand wrote:
>> On 12/19/2014 11:50 AM, Simon Horman wrote:
>>> On Thu, Dec 18, 2014 at 05:30:42PM -0800, Joe Stringer wrote:
>>>> On 18 December 2014 at 01:00, F
On 12/19/2014 11:32 PM, Thomas Goirand wrote:
> On 12/19/2014 10:25 PM, Simon Horman wrote:
>> On Fri, Dec 19, 2014 at 06:39:39PM +0800, Thomas Goirand wrote:
>>> On 12/19/2014 11:50 AM, Simon Horman wrote:
>>>> On Thu, Dec 18, 2014 at 05:30:42PM -0800, Joe String
e btw that packages.debian.org doesn't show what's
in proposed-updates, but I can tell you that
1.4.2+git20120612-9.1~deb7u1.1 is in (I received the ACK email).
So if you want to have it *now*, just add the wheezy-proposed-update
repository to your sources.list (IM
heezy-proposed-updates if the release
team agrees)?
To the release team: would you accept such bug fix? I believe the fix is
rather small, but it is really important for us that it's applied in
Wheezy: this is the cause of major problems using OpenVSwitch with
OpenStack.
Cheers,
Thomas Goirand (
ou fix all the lintian warning:
that's what experimental is for).
Cheers,
Thomas Goirand (zigo)
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
On 06/29/2013 06:43 PM, Adam D. Barratt wrote:
> On Tue, 2013-06-25 at 22:19 +0800, Thomas Goirand wrote:
>> Mehdi found out the upstream bug fix for this, and I incorporated it as
>> a patch for the Wheezy version. The patch applied cleanly, and we have
>> tested it, it reall
Hi Adam,
Thanks for your explanations about numbering, it makes sense indeed.
On 06/30/2013 01:11 AM, Adam D. Barratt wrote:
> For one thing, the package isn't targetted at squeeze. ;-)
Wooops! :)
It's going to take me a year or 2 until I get used to it. Oh wait,
that's when Jessie will be out.
please write about it in this bug report: both
Goneri or myself would be very happy to help and NMU the fix, if we are
right that a simple mkdir is enough.
Thomas Goirand (zigo)
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
Hi Ben,
it's always a pleasure to see that you are ok with help. I will NMU shortly.
Thomas
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
--pedantic openvswitch__amd64.changes
Cheers,
Thomas Goirand (zigo)
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
On 03/08/2012 07:16 PM, Simon Horman wrote:
> Hi Thomas,
>
> patches for any and all of the problems below would, as always, be
> gratefully appreciated.
Hi,
I'd be happy to provide such patches, but unfortunately, I'm already
overloaded with other packaging work myself. I did fix the dkms issue
nf.db.5.gz (please fix it...)
- I: openvswitch source: debian-watch-file-is-missing (it'd be great to
have a watch file: where's your upstream tarball located?)
I hope that helps,
Cheers,
Thomas Goirand (zigo)
diff -u -r -N openvswitch-1.4.0_2+nmu1/debian/changelog openvswitch-1.
On 03/09/2012 01:09 AM, Ben Pfaff wrote:
> On Thu, Mar 08, 2012 at 04:27:39PM +0800, Thomas Goirand wrote:
>> Before uploading version 1.4.0-2+nmu1, I ran Lintian, as I always do, and
>> I have found out that lots of Lintian warnings and errors were not
>> addressed:
>
&
On 03/09/2012 03:22 AM, Ben Pfaff wrote:
> On Fri, Mar 09, 2012 at 01:47:45AM +0800, Thomas Goirand wrote:
>> As I understand, you are also upstream for openvswitch. If that is the
>> case, then best would be to have the man page fixes to be applied
>> upstream, and the debian
On 03/17/2012 06:57 AM, Simon Horman wrote:
> Understood, in that case I agree that backporting makes sense.
I agree that "backporting" fixes makes sense. I'd like also to highlight
that you'd be backporting a forwarded-port... :)
Thomas
___
dev mailing
Hi,
I missed that one email, just saw it when reviewing the bug.
On Fri, Mar 09, 2012 at 12:06:03AM +0800, Thomas Goirand wrote:
>>> E: openvswitch-datapath-dkms: python-script-but-no-python-dep
usr/src/openvswitch-1.4.0/build-aux/check-structs
[ ... many of the same ...]
Ben Pfa
> [resending to address that doesn't bounce for me with SPF complaint]
Could you please provide me with the SPF error, so that I can fix it? Or
is the issue on your side?
If you send to z...@debian.org, it works because I've white-listed the
Debian mail server, but I would still like to know if m
makes the package unusable", which in Debian books is an RC bug.
A fix correcting this issue ASAP would be really appreciated. :)
Cheers,
Thomas Goirand (zigo)
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
On 02/14/2012 01:22 AM, Ben Pfaff wrote:
> The config.log would be useful too.
>
> Thomas, it's possible that you're hitting the following bug. I
> committed a fix for it to all of our active branches a few minutes
> ago (so obviously it isn't in Debian yet):
> http://openvswitch.org/pipe
On 02/14/2012 02:09 AM, Ben Pfaff wrote:
> There is no point in trying to run "make" if "configure" failed. The
> "make" will fail too and the log will be harder to read.
>
> CC: Thomas Goirand
> CC: Simon Horman
> Signed-off-by: Ben Pfaff
&
On 02/14/2012 07:41 AM, Thomas Goirand wrote:
> On 02/14/2012 02:09 AM, Ben Pfaff wrote:
>> There is no point in trying to run "make" if "configure" failed. The
>> "make" will fail too and the log will be harder to read.
>>
>> CC: Thomas
Hi,
I've reopened this bug, because this didn't fix it. Attached is the
make.log.
Thomas
DKMS make.log for openvswitch-1.4.0 for kernel 3.1.0-1-686-pae (i686)
Thu Feb 16 09:30:27 UTC 2012
checking build number... none
checking for a BSD-compatible install... /usr/bin/install -c
checking whether b
ren't needed at all. Also, with this patch,
openvswitch-datapath-dkms works as expected (eg: it build the kernel
module), because using ${kernel_source_dir} as it should be. Please
apply this patch and upload a new 1.4.0-3 of openvswitch.
Cheers,
Thomas Goirand
diff -u -N -r old/openvswitch-
Hi,
I'm sorry, I think I didn't express myself correctly. Please read this:
http://lintian.debian.org/tags/patch-modifying-debian-files.html
As you can see, lintian did catch issues in your openvswitch package! :)
So, if you have changes to make in let's say debian/control, then edit
the file, d
If you agree with my patch, I can do an NMU. Is that ok?
Thomas
___
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
31 matches
Mail list logo
