Bug#867869: ITP: beautify-bash -- Beautifier for Bash shell scripts written in Python

Package: wnpp Severity: wishlist Owner: Mike Mestnik -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 * Package name: beautify-bash Version : 1.0 Upstream Author : Paul Lutus , Shriram V * URL : https://arachnoid.com/python/beautify_bash_program.html https://github.

Re: Upcoming stable point release (9.1)

On 07/10/2017 07:00 AM, Pirate Praveen wrote: > [Moving to -devel] Not sure why, as this seems to be a release matter. > I'd like this fix > (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=865316) to be part of > 9.1, but one of the maintainers of the package seems to not agree with > the seve

Re: Upcoming stable point release (9.1)

On 07/10/2017 01:38 PM, Philipp Kern wrote: > On 07/10/2017 07:00 AM, Pirate Praveen wrote: >> [Moving to -devel] > > Not sure why, as this seems to be a release matter. Because I wanted to get inputs from other developers on how to proceed. >> I'd like this fix >> (https://bugs.debian.org/cgi-b

Re: Upcoming stable point release (9.1)

On 2017-07-10 10:32, Pirate Praveen wrote: On 07/10/2017 01:38 PM, Philipp Kern wrote: On 07/10/2017 07:00 AM, Pirate Praveen wrote: [Moving to -devel] Not sure why, as this seems to be a release matter. Because I wanted to get inputs from other developers on how to proceed. Without involvi

Re: P.S. Re: Debian 9 in a VM with Proxmox 5 system

Hi Nicholas! Thanks for this information, I will change my configuration to the new one. Cheers, Maximilian Nicholas D Steeves 10. July 2017 at 1:49 AM P.S. That cheat sheet isn't nearly as nice...as I'd like it to be I wish it was a compact printable two or three c

Re: P.S. Re: Debian 9 in a VM with Proxmox 5 system

Hi! Okay, I understand! But I have the problem that the Debian 9 VM can not get an internet connection. This is because the network configuration (/etc/network/interfaces) fail, because Debian 9.0 could not found a device named eth0, but with Debian 8.8 with the same configuration I have no p

Re: P.S. Re: Debian 9 in a VM with Proxmox 5 system

On Mon, Jul 10, 2017 at 01:44:00PM +0200, Maximilian Althaus wrote: >Okay, I understand! But I have the problem that the Debian 9 VM can not No, you don't. You already got told about ip -r. "route" and "ifconfig" are not installed per default anymore. >get an internet connection. This is

Re: P.S. Re: Debian 9 in a VM with Proxmox 5 system

On Mon, Jul 10, 2017 at 01:57:08PM +0200, Rene Engelhard wrote: > On Mon, Jul 10, 2017 at 01:44:00PM +0200, Maximilian Althaus wrote: > >Okay, I understand! But I have the problem that the Debian 9 VM can not > > No, you don't. You already got told about ip -r. "route" and "ifconfig" are > no

Re: P.S. Re: Debian 9 in a VM with Proxmox 5 system

Hi! Thanks, but this do not help me. I have still the same error. http://prntscr.com/ftv2uj This is a screenshot when I start the networking service and it failed, because of there is no route command! -- This is the config for (/etc/network/interfaces) auto lo iface lo inet loopba

New network interface naming scheme [was Re: P.S. Re: Debian 9 in a VM with Proxmox 5 system]

First, the original thread belongs on debian-user, not debian-devel. Please move the "how do I use the new (more than a decade old) networking tools" user question there. * Rene Engelhard [170710 08:03]: > https://www.debian.org/releases/stable/amd64/release-notes/ch-whats-new.de.html#new-interfa

Re: P.S. Re: Debian 9 in a VM with Proxmox 5 system

On Mon, Jul 10, 2017 at 01:57:08PM +0200, Rene Engelhard wrote: > eth0 will be kept on upgrades, but new installs get new interface names > (that is good, that removed unpredictability if you add a new network card.) Interface names are, unfortunately, as unpredictable in stretch as they were in

Bug#867915: ITP: xsimd -- C++ wrappers for SIMD intrinsics

Package: wnpp Severity: wishlist Owner: Ghislain Antony Vaillant * Package name: xsimd Version : 3.0.0 Upstream Author : Johan Mabille and Sylvain Corlay * URL : https://github.com/QuantStack/xsimd * License : BSD Programming Lang: C++ Description : C++

Bug#867920: ITP: libjlargearrays-java -- Java library for one dimensional arrays up to 2^63 elements

Package: wnpp Severity: wishlist Owner: =?utf-8?q?Carn=C3=AB_Draug?= * Package name: libjlargearrays-java Version : 1.6 Upstream Author : Piotr Wendykier * URL : https://gitlab.com/ICM-VisLab/JLargeArrays * License : BSD-2-Clause Programming Lang: Java Des

Re: New network interface naming scheme [was Re: P.S. Re: Debian 9 in a VM with Proxmox 5 system]

❦ 10 juillet 2017 09:38 -0400, Marvin Renich  : > The cost of a state file (/etc/udev/rules.d/70-persistent-net.rules) is > extremely small, even in the very worst case where a user continually > plugs in many, many different usb network dongles, which is a very > unrealistic case to begin with.

Re: P.S. Re: Debian 9 in a VM with Proxmox 5 system

On Mon, Jul 10, 2017 at 03:47:14PM +0200, Guus Sliepen wrote: > On Mon, Jul 10, 2017 at 01:57:08PM +0200, Rene Engelhard wrote: > > > eth0 will be kept on upgrades, but new installs get new interface names > > (that is good, that removed unpredictability if you add a new network card.) > > Interf

Re: New network interface naming scheme [was Re: P.S. Re: Debian 9 in a VM with Proxmox 5 system]

On Mon, Jul 10, 2017 at 06:05:06PM +0200, Vincent Bernat wrote: > ❦ 10 juillet 2017 09:38 -0400, Marvin Renich  : > > > The cost of a state file (/etc/udev/rules.d/70-persistent-net.rules) is > > extremely small, even in the very worst case where a user continually > > plugs in many, many differe

Re: P.S. Re: Debian 9 in a VM with Proxmox 5 system

On Jul 10, Adam Borowski wrote: > Predictability is important, thus let's actually have _predictable_ > interface names. The kernel default, eth0 and wlan0, is good enough for > most users, why not keep that? Even just ignoring the issue completely Because you cannot know how many interfaces a

Re: New network interface naming scheme [was Re: P.S. Re: Debian 9 in a VM with Proxmox 5 system]

❦ 10 juillet 2017 18:37 +0200, Adam Borowski  : >> > The cost of a state file (/etc/udev/rules.d/70-persistent-net.rules) is >> > extremely small, even in the very worst case where a user continually >> > plugs in many, many different usb network dongles, which is a very >> > unrealistic case to

Re: P.S. Re: Debian 9 in a VM with Proxmox 5 system

On Mon, Jul 10, 2017 at 07:11:58PM +0200, Marco d'Itri wrote: > On Jul 10, Adam Borowski wrote: > > > Predictability is important, thus let's actually have _predictable_ > > interface names. The kernel default, eth0 and wlan0, is good enough for > > most users, why not keep that? Even just igno

Naming of network devices (was: Re: Debian 9 in a VM with Proxmox 5 system)

Hola. Adam Borowski - 10.07.17, 18:22: > On Mon, Jul 10, 2017 at 03:47:14PM +0200, Guus Sliepen wrote: > > On Mon, Jul 10, 2017 at 01:57:08PM +0200, Rene Engelhard wrote: > > > eth0 will be kept on upgrades, but new installs get new interface names > > > (that is good, that removed unpredictabilit

Re: P.S. Re: Debian 9 in a VM with Proxmox 5 system

m...@linux.it (Marco d'Itri) writes: > On Jul 10, Adam Borowski wrote: > >> Predictability is important, thus let's actually have _predictable_ >> interface names. The kernel default, eth0 and wlan0, is good enough for >> most users, why not keep that? Even just ignoring the issue completely > B

Re: P.S. Re: Debian 9 in a VM with Proxmox 5 system

* Marco d'Itri [170710 13:12]: > On Jul 10, Adam Borowski wrote: > > > Predictability is important, thus let's actually have _predictable_ > > interface names. The kernel default, eth0 and wlan0, is good enough for > > most users, why not keep that? Even just ignoring the issue completely > Be

Re: P.S. Re: Debian 9 in a VM with Proxmox 5 system

❦ 10 juillet 2017 14:36 -0400, Marvin Renich  : > The only benefit I have seen between the new scheme and the previous > one is that there is no state file. While getting rid of the state > file is a nice goal, it is extremely minor compared to having short, > simple names in common use cases li

Bug#867968: ITP: ign-transport3 -- Ignition Transport library v3

Package: wnpp Severity: wishlist Owner: Jose Luis Rivero * Package name: ign-transport3 Version : 3.0.1 Upstream Author : Open Source Robotics Foundation * URL : http://ignitionrobotics.org/libraries/transport * License : Apache Programming Lang: C++ Descri

Bug#867969: ITP: sdformat5 -- Simulation Description Format (SDF) parser

Package: wnpp Severity: wishlist Owner: Jose Luis Rivero * Package name: sdformat5 Version : 5.1.0 Upstream Author : Open Source Robotics Foundation * URL : http://sdformat.org * License : BSD Programming Lang : C++ Description : Simulation Description F

Naming of network devices (was: Re: Debian 9 in a VM with Proxmox 5 system)

* Vincent Bernat [170710 14:56]: > ❦ 10 juillet 2017 14:36 -0400, Marvin Renich  : > > > The only benefit I have seen between the new scheme and the previous > > one is that there is no state file. While getting rid of the state > > file is a nice goal, it is extremely minor compared to having

Re: Naming of network devices

On 07/10/2017 07:31 PM, Martin Steigerwald wrote: > Which fails to mention how the feature can be configured and some mechanisms > like relying on BIOS name, can be disabled, for example: > > https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/ > Networking_Guide/sec-Con

Re: Naming of network devices

❦ 10 juillet 2017 15:53 -0400, Marvin Renich  : >> > With the new scheme, if I want to rename the interface to something more >> > meaningful, I have to go find an older machine that already has a >> > persistent-net.rules file or read through a lot of documentation to >> > figure out the correct

Bug#867993: RFP: pyscada -- SCADA system with web interface

Package: wnpp Severity: wishlist * Package name: pyscada Version : 0.7.0b17 Upstream Author : Martin Schröder * URL : https://github.com/trombastic/PyScada * License : GPL3 Programming Lang: Python Description : SCADA system with web interface >From th

Re: P.S. Re: Debian 9 in a VM with Proxmox 5 system

Vincent Bernat, on lun. 10 juil. 2017 20:55:29 +0200, wrote: > but there is nothing difficult in identifying the right interface with > the new naming scheme. Errr, it may not look difficult to *you*, but to someone who is learning how to tinker Linux, things like enp0s25f1 looks really difficult