Re: Jessie will need Linux 3.18!
On 5 February 2015 at 00:03, Thomas Goirand wrote: > > On 02/04/2015 08:36 PM, Martinx - ジェームズ wrote: > > Guys, > > > > I was facing a Linux BUG that was fixed only in 3.18. > > > > Here it is: > > > > https://bugs.launchpad.net/linux/+bug/1362755 > > > > So, with Linux 3.16, it will not be possible to use Jessie to create a > > "VLAN tagged Virtual Network" within a KVM hypervisor itself. > > > > It will not route VLAN tagged packets. > > > > I manually backported Linux 3.18 from Ubuntu Vivid, into Trusty: > > > > https://launchpad.net/~martinx/+archive/ubuntu/linux > > > > Then, the problem solved! > > > > I tested the Linux versions from 3.13, to 3.16, all have the same > > problem... Linux 3.18 is okay. > > > > I must say that I did not tested Jessie this days but, I know that > > Linux 3.16 doesn't work. > > > > Basically, Jessie can not be used in a production environment on a > > Corporate Network, for example... All my firewalls, VPN servers, proxies > > are KVM Virtual Machines. The VLAN tagged packets does not get routed, > > it started to work only when with Linux 3.18. > > > > Please, pay attention into this problem before Debian Jessie release! > > > > Best! > > Thiago > > Hi Thiago, > > The best way forward for this kind if issue is to: > 1/ Open a bug against the Debian linux kernel. > 2/ Provide a patch to fix the issue, attached to the bug. > > Bug keep this in mind when doing so: You need to test under *debian*, > and not just under Ubuntu. From the launchpad bug you've opened, it's > looking like you've had the issue in Ubuntu, and there's no way to tell > what will happen in Debian. Also, you issue seems related to kvm/qemu, > and not only to the kernel. > > Cheers, > > Thomas Goirand (zigo) > Okay Thomas, got it! I'll do the required tests under *debian* and fill a bug against Debian Linux Kernel. But, the Kernel code related to this part of it (network and etc), is very different in Linux 3.18, I'm guessing that it will *easier* to just provide Jessie with Linux 3.18, instead of a patch, but, I'm seeing that it might be too late for that... :-( Yes, I tested it with Ubuntu but, I also tested it using Linux from kernel.org, compiled by myself... Only Linux 3.18 solve that issue. Cheers! -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/cajsm8j1jkgcyuwpyjg8djf2cssjbjm5tfsrbw1jexzpvah_...@mail.gmail.com
Re: Jessie will need Linux 3.18!
On 02/04/2015 08:36 PM, Martinx - ジェームズ wrote: > Guys, > > I was facing a Linux BUG that was fixed only in 3.18. > > Here it is: > > https://bugs.launchpad.net/linux/+bug/1362755 > > So, with Linux 3.16, it will not be possible to use Jessie to create a > "VLAN tagged Virtual Network" within a KVM hypervisor itself. > > It will not route VLAN tagged packets. > > I manually backported Linux 3.18 from Ubuntu Vivid, into Trusty: > > https://launchpad.net/~martinx/+archive/ubuntu/linux > > Then, the problem solved! > > I tested the Linux versions from 3.13, to 3.16, all have the same > problem... Linux 3.18 is okay. > > I must say that I did not tested Jessie this days but, I know that > Linux 3.16 doesn't work. > > Basically, Jessie can not be used in a production environment on a > Corporate Network, for example... All my firewalls, VPN servers, proxies > are KVM Virtual Machines. The VLAN tagged packets does not get routed, > it started to work only when with Linux 3.18. > > Please, pay attention into this problem before Debian Jessie release! > > Best! > Thiago Hi Thiago, The best way forward for this kind if issue is to: 1/ Open a bug against the Debian linux kernel. 2/ Provide a patch to fix the issue, attached to the bug. Bug keep this in mind when doing so: You need to test under *debian*, and not just under Ubuntu. From the launchpad bug you've opened, it's looking like you've had the issue in Ubuntu, and there's no way to tell what will happen in Debian. Also, you issue seems related to kvm/qemu, and not only to the kernel. Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54d2cf60.4010...@debian.org
Bug#777089: ITP: python-moto -- Mock framework for boto AWS library
Package: wnpp Severity: wishlist Owner: Russ Allbery * Package name: python-moto Version : 0.4.0 Upstream Author : Steve Pulec * URL : https://github.com/spulec/moto * License : Apache 2.0 Programming Lang: Python Description : Mock framework for boto AWS library Moto is a library that allows your Python tests to easily mock out the boto library (used to talk to the Amazon AWS API). It supports most of the major AWS services and can be used as a decorator, context manager, or via explicit calls. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150204224226.5389.46796.reportbug@lothlorien.eyrie.local
Re: Jessie will need Linux 3.18!
On 4 February 2015 at 19:08, Ben Hutchings wrote: > > [Redirecting to debian-kernel] Cool! Tks! > > > On Wed, 2015-02-04 at 17:36 -0200, Martinx - ジェームズ wrote: > > Guys, > > > > > > I was facing a Linux BUG that was fixed only in 3.18. > > Did you find out what change fixes this? No, I did not bisected the issue... Vlad Yasevich from Redhat (comment #2 at LP #1362755) told me that it is something related to TSO/GSO implementation in the kernel. > > Does this configuration work in wheezy (with Linux 3.2)? I did not tested it with Linux 3.2 but, I can try it next week. > > [...] > > Basically, Jessie can not be used in a production environment on a > > Corporate Network, for example... > [...] > > Please, don't exaggerate. Debian is already widely used with the Linux > 3.16. Apparently certain configurations don't work properly, but we can > probably fix that. Okay, sorry... I was just trying to raise up the drama to catch attention... hehe... To make it clear, Jessie KVM guest, acting as a router, can not be used on top of Jessie KVM host, when you have tagged VLANs... I guess that this topology might be pretty common out there... I worked on a lot of companies that are purely based on Debian / Ubuntu (both hypervisors and VMs). Drama off...:-) Jessie is great! > > Ben. Thiago -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAJSM8J37tuFbkFWHE4_58wS=_-HtMCre=9-mgadrhsoc_cu...@mail.gmail.com
Re: Jessie will need Linux 3.18!
[Redirecting to debian-kernel] On Wed, 2015-02-04 at 17:36 -0200, Martinx - ジェームズ wrote: > Guys, > > > I was facing a Linux BUG that was fixed only in 3.18. Did you find out what change fixes this? Does this configuration work in wheezy (with Linux 3.2)? [...] > Basically, Jessie can not be used in a production environment on a > Corporate Network, for example... [...] Please, don't exaggerate. Debian is already widely used with the Linux 3.16. Apparently certain configurations don't work properly, but we can probably fix that. Ben. -- Ben Hutchings Hoare's Law of Large Problems: Inside every large problem is a small problem struggling to get out. signature.asc Description: This is a digitally signed message part
Jessie will need Linux 3.18!
Guys, I was facing a Linux BUG that was fixed only in 3.18. Here it is: https://bugs.launchpad.net/linux/+bug/1362755 So, with Linux 3.16, it will not be possible to use Jessie to create a "VLAN tagged Virtual Network" within a KVM hypervisor itself. It will not route VLAN tagged packets. I manually backported Linux 3.18 from Ubuntu Vivid, into Trusty: https://launchpad.net/~martinx/+archive/ubuntu/linux Then, the problem solved! I tested the Linux versions from 3.13, to 3.16, all have the same problem... Linux 3.18 is okay. I must say that I did not tested Jessie this days but, I know that Linux 3.16 doesn't work. Basically, Jessie can not be used in a production environment on a Corporate Network, for example... All my firewalls, VPN servers, proxies are KVM Virtual Machines. The VLAN tagged packets does not get routed, it started to work only when with Linux 3.18. Please, pay attention into this problem before Debian Jessie release! Best! Thiago
Bug#777055: ITP: ruby-whenever -- Ruby library to abstract writing and deploying cron jobs
Package: wnpp Severity: wishlist Owner: Antonio Terceiro * Package name: ruby-whenever Version : 0.9.4 Upstream Author : Javan Makhmali * URL : https://rubygems.org/gems/whenever * License : Expat Programming Lang: Ruby Description : Ruby library to abstract writing and deploying cron jobs whenever provides a clean ruby syntax for writing and deploying cron jobs. It provides commands to install and uninstall cronjobs, so for example an application can install its cronjobs when it starts, and uninstall them when it stops for maintaince, without messing up unrelated cron jobs for the same user. -- Antonio Terceiro signature.asc Description: Digital signature
Re: network-manager-strongswan kicked out from Jessie, even though there is a fix?
On Wed, Feb 04, 2015 at 01:46:19PM +0100, Harald Dunkel wrote: > On 02/04/15 12:22, Dominique Dumont wrote: > > > > According to PTS [1], this package was kicked out because of > > a FTBS [2]. Is this bug fixed ? > > Sorry, I had built network-manager-strongswan on Wheezy > to use it on Wheezy and Jessie. I didn't notice the FTBFS > on sid. > > Building on Jessie I still get the error about using > deprecated header files. The package built on Wheezy > installs and runs fine on both. > > Upstream seems to be aware of the problem (see > https://wiki.strongswan.org/issues/797), but it is pretty > unlikely that there will be a fix for 1.3.0, so I wonder > what is the recommended procedure to make an exception and > to override the deprecated-declarations error for Jessie > at build time? The package FTBFSes only because its build is sabotaged with -Werror. Drop that and the deprecation warnings become harmless. On stable or soon-to-be-stabled there's no way a deprecated interface can disappear. -- // If you believe in so-called "intellectual property", please immediately // cease using counterfeit alphabets. Instead, contact the nearest temple // of Amon, whose priests will provide you with scribal services for all // your writing needs, for Reasonable and Non-Discriminatory prices. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150204132401.ga15...@angband.pl
Bug#777048: ITP: prometheus -- A systems and service monitoring system.
Package: wnpp Severity: wishlist Owner: "Martín Ferrari" * Package name: prometheus Version : 0.10.0 Upstream Author : The Prometheus Authors * URL : http://prometheus.io/ * License : Apache 2.0 Programming Lang: go Description : A systems and service monitoring system. Prometheus is a systems and service monitoring system. It collects metrics from configured targets at given intervals, evaluates rule expressions, displays the results, and can trigger alerts if some condition is observed to be true. Prometheus' main distinguishing features as compared to other monitoring systems are: * A multi-dimensional data model (timeseries defined by metric name and set of key/value dimensions). * A flexible query language to leverage this dimensionality. * No dependency on distributed storage; single server nodes are autonomous. * Timeseries collection happens via a pull model over HTTP. * Pushing timeseries is supported via an intermediary gateway. * Targets are discovered via service discovery or static configuration. * Multiple modes of graphing and dashboarding support. * Federation support coming soon. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150204130009.2893.37085.report...@aine.tincho.org
Re: network-manager-strongswan kicked out from Jessie, even though there is a fix?
On 02/04/15 12:22, Dominique Dumont wrote: > > According to PTS [1], this package was kicked out because of > a FTBS [2]. Is this bug fixed ? > Sorry, I had built network-manager-strongswan on Wheezy to use it on Wheezy and Jessie. I didn't notice the FTBFS on sid. Building on Jessie I still get the error about using deprecated header files. The package built on Wheezy installs and runs fine on both. Upstream seems to be aware of the problem (see https://wiki.strongswan.org/issues/797), but it is pretty unlikely that there will be a fix for 1.3.0, so I wonder what is the recommended procedure to make an exception and to override the deprecated-declarations error for Jessie at build time? Regards Harri -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54d2149b.5000...@aixigo.de
Bug#777043: ITP: libshark -- Shark Machine Learning Library
Package: wnpp Severity: wishlist Owner: Goswin von Brederlow * Package name: libshark Version : 3.0.11 Upstream Author : Institut fuer Neuroinformatik, Ruhr-Universitaet Bochum * URL : http://image.diku.dk/shark/ * License : GPL-3.0+ Programming Lang: C++ Description : Shark Machine Learning Library SHARK is a modular C++ library for the design and optimization of adaptive systems. It provides methods for linear and nonlinear optimization, in particular evolutionary and gradient-based algorithms, kernel-based learning algorithms and neural networks, and various other machine learning techniques. SHARK serves as a toolbox to support real world applications as well as research indifferent domains of computational intelligence and machine learning. The sources are compatible with the following platforms: Windows, Solaris, MacOS X, and Linux. - libshark is a dependency of sailfish - the package will be maintained under the Debian-Med team -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150204123715.23837.14254.reportbug@frosties.localnet
Re: network-manager-strongswan kicked out from Jessie, even though there is a fix?
On Wednesday 04 February 2015 11:00:35 Harald Dunkel wrote: > Currently it seems it has been kicked out due to #773764, > even though the report provides an easy fix to make it work at least > for xfce4 and gnome on Jessie. According to PTS [1], this package was kicked out because of a FTBS [2]. Is this bug fixed ? All the best [1] https://tracker.debian.org/pkg/network-manager-strongswan [2] http://bugs.debian.org/759826 -- https://github.com/dod38fr/ -o- http://search.cpan.org/~ddumont/ http://ddumont.wordpress.com/ -o- irc: dod at irc.debian.org -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/5015649.if6nvdUsq6@ylum
network-manager-strongswan kicked out from Jessie, even though there is a fix?
Hi folks, Do you think it would it be possible to fix network-manager-strongswan for Jessie? Currently it seems it has been kicked out due to #773764, even though the report provides an easy fix to make it work at least for xfce4 and gnome on Jessie. I have pushed an NMU (1.3.0-1.2) to mentors for your consideration. http://mentors.debian.net/package/network-manager-strongswan Thanx in advance. Keep on your good work Harri -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/54d1edc3.90...@aixigo.de
