Bug#868494: ITP: dtksettings -- Deepin Tool Kit Settings library

2017-07-15 Thread Boyuan Yang
Package: wnpp
Severity: wishlist
Owner: Boyuan Yang <073p...@gmail.com>

* Package name: dtksettings
  Version : 0.1.7
  Upstream Author : Deepin Technology Co., Ltd.
* URL : https://github.com/linuxdeepin/dtksettings
* License : GPL-3+
  Programming Lang: C++
  Description : Deepin Tool Kit Settings library

DtkSettings is a powerful tool to generate config form json.

This source package provides several libraries needed by various softwares
developed by Deepin Linux.

Deepin Linux is a derivative distribution of Debian, developed mainly by Deepin
Technology Co., Ltd.

I intend to co-maintain this package inside Debian Chinese Team and put
packaging Git repository under collab-maint.



Re: Naming of network devices - how to improve it in buster

2017-07-15 Thread Henrique de Moraes Holschuh
On Sat, 15 Jul 2017, Adam Borowski wrote:
> > This will match any interface that has MAC address 01:23:45:67:89:ab,
> > and will use the "foo" stanzas to configure it.
> 
> Awesome!  This sounds like the best solution so far.

It is indeed Very Cool, but it might not solve one little thing:
iptables firewalling.

Is that a way to trigger an ifrename using this, so that the network
device ends up being named "foo" ?

-- 
  Henrique Holschuh



Bug#868482: ITP: sokochez -- two players puzzle game

2017-07-15 Thread Baptiste Pouget
Package: wnpp
Severity: wishlist
Owner: Baptiste Pouget 

* Package name: sokochez
  Version : 0.6.2
  Upstream Author : Baptiste Pouget 
* URL : https://github.com/Sokochez/sokochez
* License : GPLv3+
  Programming Lang: C++
  Description : two players puzzle game

 Sokochez is a two players puzzle game inspired by Sokoban, it contains a map
editor, there are three gamemodes and many different maps.

This package is useful for one to distract himself and does not require any
dependency as it is made in pure C++. I played this game and created it with
friends so I know it quite well.
By the way it can also be played by a single person even though the gameplay is
meant for two players.
I am planning to maintain it alone since it is a small package.



Re: Naming of network devices - how to improve it in buster

2017-07-15 Thread Adam Borowski
On Sat, Jul 15, 2017 at 10:30:59PM +0200, Guus Sliepen wrote:
> On Tue, Jul 11, 2017 at 06:04:29PM +0200, Guus Sliepen wrote:
> 
> > This is not impossible to do. I actually have some code to make ifupdown
> > use interface matching, I'm afraid I was too late in the stretch cycle
> > to have a well-tested implementation. I will try to add this early in
> > buster so it can be tested properly and any kinks resolved.
> 
> Initial support for interface matching has been uploaded, so once it
> hits your mirror you can apt-get upgrade to ifupdown 0.8.20 and use it.
> An example to match an interface by MAC address:
> 
> allow-hotplug mac/01:23:45:67:89:ab/=foo
> 
> This will match any interface that has MAC address 01:23:45:67:89:ab,
> and will use the "foo" stanzas to configure it.

Awesome!  This sounds like the best solution so far.

I haven't yet looked at the implementation (did not hit my mirror yet, and
I got other stuff to finish at the moment), but from your description it
sounds like this would fit most use cases.

Especially if you could somehow add "first and only wired/wifi interface in
the system", that doesn't fail in case it is used erroneously when there's
more than one interface after all.  This would fix most of SoC/VM use cases
I've seen "predictable" names fail horribly.

We'd also need something that generates the interfaces file (during d-i?)
using your syntax, but let's have your system tested and finished first.


Big fat kudos!  Add this to the pool of beers I owe you. :þ

Meow!
-- 
⢀⣴⠾⠻⢶⣦⠀ 
⣾⠁⢠⠒⠀⣿⡁ A dumb species has no way to open a tuna can.
⢿⡄⠘⠷⠚⠋⠀ A smart species invents a can opener.
⠈⠳⣄ A master species delegates.



O: sendxmpp -- commandline XMPP (jabber) utility

2017-07-15 Thread Guus Sliepen
Package: wnpp
Severity: normal

I intend to orphan the sendxmpp package.

The package description is:
 sendxmpp is a perl script to send XMPP (jabber) messages, similar to what
 mail(1) does for mail. XMPP is an open, non-proprietary protocol for instant
 messaging. See www.jabber.org for more information.

Unfortunately, I cannot give it the help it needs since I do not use
Jabber myself. The package is very useful if you want to send messages
to a Jabber service via the command line. However, it suffers from
several RC bugs which need attention. Upstream is also not very active.

If noone steps up, I will file a RM request in the current release
cycle.



Re: Naming of network devices - how to improve it in buster

2017-07-15 Thread Guus Sliepen
On Tue, Jul 11, 2017 at 06:04:29PM +0200, Guus Sliepen wrote:

> This is not impossible to do. I actually have some code to make ifupdown
> use interface matching, I'm afraid I was too late in the stretch cycle
> to have a well-tested implementation. I will try to add this early in
> buster so it can be tested properly and any kinks resolved.

Initial support for interface matching has been uploaded, so once it
hits your mirror you can apt-get upgrade to ifupdown 0.8.20 and use it.
An example to match an interface by MAC address:

allow-hotplug mac/01:23:45:67:89:ab/=foo
iface foo inet dchp
iface foo inet6 auto

auto type/1/2=bar
iface bar inet static
address 192.168.1.1/24

This will match any interface that has MAC address 01:23:45:67:89:ab,
and will use the "foo" stanzas to configure it. It will also match the
second Ethernet interface (whose /sys/class/net/interfaces/$IFACE/type
file contains the line "1") and bring it up using the "bar" stanza.
Details are in the interfaces(5) manpage.

You can also use pattern matching on the ifup and ifdown command line.
You cannot use pattern matching in "iface" stanzas (yet).

The reason I used the / is that this is, as far as I know, the only
character that is never allowed in interface names on Linux. On that
note, the above examples will not work on Hurd and FreeBSD, support for
pattern matching on those platforms besides just the interface name will
follow later.

-- 
Met vriendelijke groet / with kind regards,
  Guus Sliepen 


signature.asc
Description: PGP signature


Re: Inclusion of best practices for packaging database applications in Debian policy

2017-07-15 Thread Paul Gevers
Hi all,

On 06/25/17 16:05, Paul Gevers wrote:
> This e-mail is meant for maintainers of applications that use databases
> and for those of you that are interested in how packages should handle
> those.
>
> In bug 845255¹ I started the discussion for inclusion of the "best
> practices for packaging database applications" in the Debian policy.
> These practices were written down by Sean Finney more than 12 years ago
> after discussion that started on this list (see links in the
> documentation). These best practices have always been part of the
> dbconfig-common package and are available on debian.org/doc² for a year
> now. After consulting the audience of my talk at Debconf, I think these
> practices (or an altered form if required after discussion) should be
> part of the Debian policy. In the bug it is said I should ask for
> seconds of this proposal from database application maintainers, which I
> am hereby seeking.

Shameful ping. Is there really nobody interested in documenting this in
policy? That would also be valuable input to the bug report, so don't be
shy to state that.

Paul



signature.asc
Description: OpenPGP digital signature


ITP: node-color-name -- list of color names and its values

2017-07-15 Thread gazalam
Package: wnpp
Severity: wishlist
Owner: Gazala M 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name : node-color-name
 Version : 1.1.2
 Upstream Author : DY 
* URL : https://github.com/dfcreative/color-name
* License : Expat
 Programming Lang: JavaScript
 Description : list of color names and its values
 Given a color name, this package outputs its corresponding RGB value
 Based on https://dev.w3.org/csswg/css-color/#named-colors
 .
 Node.js is an event-based server-side JavaScript engine.
 .
 This package is a dependency of npm, node package manager. I plan to join 
Javascript packaging team.
 Pirate Praveen has agreed to sponser this package.


Bug#868444: ITP: node-umask -- convert umask from string <-> number

2017-07-15 Thread olive
Package: wnpp
Severity: wishlist
Owner: Olive 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name : node-umask
 Version : 1.1.0
 Upstream Author : Sam Mikes 
* URL : https://github.com/smikes/umask
* License : Expat
 Programming Lang: JavaScript
 Description : convert umask from string  number

Convert umask from string  number. It has the following functions:
 toString( val ) converts 'val' to a 0-padded octal string.
 fromString(val, [cb]) converts 'val' to a Number that can be used as a umask.
 validate(data, k, val) is a validation function of the form expected by 'nopt'.
 If 'val' is a valid umask, the function returns true and sets 'data[k]'.
 If 'val' is not a valid umask, the function returns false.
 .
 This package is a dependency of npm, node package manager.
 .
 Node.js is an event-based server-side JavaScript engine.

I wish to join javascript packaging team.
Pirate Praveen has agreed to sponsor this package.


ITP: node-dot-prop --Get, set, or delete a property from a nested object using a dot path

2017-07-15 Thread archana
Package: wnpp
Severity: wishlist
Owner: Archana N 
X-Debbugs-CC:   debian-devel@lists.debian.org

* Package name : node-dot-prop
 Version : 4.1.1
 Upstream Author : Sindre Sorhus  (sindresorhus.com)
* URL : https://github.com/sindresorhus/dot-prop#readme
* License : Expat
 Programming Lang: JavaScript
 Description : Get, set, or delete a property from a nested object using a dot 
path
 Get, set, or delete a property from a nested object using
 a dot path
 This package is a dependency of npm, node package manager.
 The types are 'object','string','any'.
 .
 Node.js is an event-based server-side JavaScript engine.

 I plan to join Javascript packaging team. Pirate Praveen has agreed to sponsor 
this package.


Bug#868443: ITP: node-is-object -- Checks whether a value is an object

2017-07-15 Thread Visakh S
Package: wnpp
Severity: wishlist
Owner: VISAKH S 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-is-object
  Version : 1.0.1
  Upstream Author : Raynos 
* URL : https://github.com/ljharb/is-object
* License : Expat
  Programming Lang: JavaScript
  Description : Checks whether a value is an object

 Checks whether a value is an object
 .
 Node.js is an event-based server side javascript engine
 .
 The assert module provides a way of testing expressions. If the expression
 evaluates to 0, or false, an assertion failure is being caused
 and the program is terminated.
 .
 This package is a useful dependency of npm
 .
 I am planning to maintain this package as part of a javascript maintainers
team
 Pirate Praveen has agreed to sponser this package
 I would like to join the javascript maintainers team


Re: Naming of network devices - how to improve it in buster

2017-07-15 Thread Russell Stuart
On Sat, 2017-07-15 at 07:46 +0200, Tollef Fog Heen wrote:
> Doesn't something like:
> 
> [Unit]
> Description=My hook for foo.link
> After=foo.link
> BindsTo=foo.link
> 
> [Service]
> Type=oneshot
> ExecStart=/usr/local/sbin/whatever
> RemainAfterExit=yes
> 
> [Install]
> WantedBy=multi-user.target
> 
> work to hook into when a link unit is activated?
> 
> (Or just a Wants and Before in the foo.link unit)

When I discovered .link and .network files the first thing I looked up
in the doco was whether that sort of thing was possible.  I decided it
wasn't and wrote it off as useless for me.

Now you've made me check for real.  After setting up the unit files you
suggested I get this message in journalctl:

  Failed to add dependency on foo.link, ignoring: Invalid argument

So now I'm fairly convinced the above isn't a thing.  systemd unit
files and udev unit files live in two different worlds - they can't
refer to each other.

That aside, it wouldn't work for my most advance use case anyway.  My
issue is I have boxes literally 1000's of km's away.  Occasionally it
all goes wrong, the only way to fix it is ssh in but "all" includes the
internet connection.

My fix was to detect when a mobile phone was plugged in via USB, then
create a vpn connection home. This is all doable with a few lines in
/etc/network/interfaces - the hard bit is detecting when some random
USB device is a mobile phone.  Standard udev rules can't do it, and so
systemd.link being less powerful doesn't have a hope.  This isn't a
reflection on either of them really - it's a very specialised use case.
  However, I do expect them to provide an escape route.  Udev does - it
can run a program to decide.  systemd.link can't.

signature.asc
Description: This is a digitally signed message part


Naming of network devices

2017-07-15 Thread Ivan Shmakov
> Marvin Renich  writes:

[…]

 > 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 like inserting a wifi usb dongle.

 > And no, enp2s0f1 is neither short nor simple.  It requires
 > remembering three numbers and three letters that identify internal
 > parts of the hardware hierarchy that are irrelevant to the sysadmin.

 > With the previous scheme, an interface would be assigned a short,
 > simple name the first time it was seen.  The sysadmin could easily
 > edit the state file to give it a more meaningful name, if desired.
 > The state file already had all the other information needed to
 > identify the interface; a simple one-word change in the file was
 > sufficient.  Whatever name was in the state file was used for that
 > piece of hardware from then on.  The names were at least as
 > predictable as they are with the new scheme.

Somewhat recently I’ve got a bunch of nearly identical servers
to care about.  With the /persistent/ (pre-Stretch) interface
names, were I to, say, move an HDDs from one box and into
another, I'd likely to end up with some “new” ethN interface
names unaccounted to in interfaces(5), and possibly other
places.  Some manual intervention would be required.

With the /predictable/ (Stretch) interface names, I’d get a
fully operational system outright.

I admit that the new scheme makes considerably less sense for
the cases where you have /no/ spare identical hardware.

(As such, I’ve added a -persistent-net.rules to the udev
configuration on my few new Debian installs.)

 > 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 syntax.  I then have to determine the correct
 > ATTR elements to identify the interface in question, and type all of
 > that information by hand, hoping I type everything correctly.

I concur that there ought to be some more user-visible
documentation concerning the differences and how to get the
behavior the user desires.

 > There is an easy fix to revert the default behavior while still
 > allowing knowledgeable sysadmins to get the new behavior.  On the
 > other hand, those who need to administer systems but are not
 > sysadmins by trade (and thus will have to do significantly more
 > research to even know that the older behavior is possible) are the
 > ones who need the older behavior as the default.

-- 
FSF associate member #7257  np. Home (Instrumental) — Jeff Burgess   230E 334A



Bug#868439: ITP: node-url-parse-lax -- Lax url.parse() with support for protocol-less URLs & IPs

2017-07-15 Thread icyfire
Package: wnpp
Severity: wishlist
Owner: Rajeev R Menon 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name : node-url-parse-lax
  Version : 1.0.0
  Upstream Author : Sindre Sorhus  (sindresorhus.com)
* URL : https://github.com/sindresorhus/url-parse-lax#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Lax url.parse() with support for protocol-less URLs & IPs

 url.parse() with support for protocol-less URLs & IPs
 Lax url.parse() with support for protocol-less URLs & IPs
 .
 Usage
 .
 var urlParseLax = require('url-parse-lax');
 The url.parse() method takes a URL string, 
 parses it, and returns a URL object.
 A TypeError is thrown if urlString is not a string.
 A URIError is thrown if the auth property is present 
 but cannot be decoded.
 .
 Node.js is an event-based server-side JavaScript engine.

It is a dependency of npm.

Pirate Praveen has agreed to sponsor this package. I am 
interested to join the Debian Javascript Maintainers team.



Bug#868438: ITP: node-p-timeout -- Timeout a promise after a specified amount of time

2017-07-15 Thread a6
Package: wnpp
Severity: wishlist
Owner: Ansal Muhammed 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name : node-p-timeout
Version : 1.2.0
Upstream Author : Sindre Sorhus  (sindresorhus.com)
* URL : https://github.com/sindresorhus/p-timeout#readme
* License : Expat
  Programming Lang: JavaScript
  Description: timeout a promise after a specified amount of time

 pTimeout(input,ms,[message[fallback]])
 input is returned after ms time
 message specify a custom error message or error
 for custom error,it is recommended to sub-class pTimeout.TimeoutError
 default message 'Promise timed out after 50 milliseconds'
 for doing something other than rejecting with an error on timeout
 .
 Node.js is an event-based server-side JavaScript engine

It is a dependancy of npm.

Pirate Praveen has agreed to sponsor. I am interested to join the Debian
JavaScript maintainers team.



Bug#868436: ITP: node-builtins -- lists nodejs builtin modules

2017-07-15 Thread Amruth Lal
Package: wnpp
Severity: wishlist
Owner: Amruth Lal 
X-Debbugs-CC: debian-devel@lists.debian.org

 *Package name: node-builtins
  Version : 1.0.3
  Upstream Author : Julian Gruber 
* URL : https://github.com/juliangruber/builtins#readme
* License : Expat
  Programming Lang: JavaScript
  Description : This library provides a list of node.js builtin modules.

 This is a dependency for npm,  Node.js package manager.
 Node.js is an event based server-  side package manager.

 I plan to join Javascript package team. Pirate Praveen has agreed to
sponser this package.



Bug#868434: ITP: node-crypto-random-string -- Generate a cryptographically strong random string

2017-07-15 Thread Vishnu poothery
Package: wnpp
Severity: wishlist
Owner: Vishnu Poothery 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-crypto-random-string
  Version : 1.0.0
  Upstream Author : Sindre Sorhus  (sindresorhus.com
)
* URL :
https://github.com/sindresorhus/crypto-random-string#readme
* License : Expat
  Programming Lang: JavaScript
  Description : Generate a cryptographically strong random string

 This library can be useful for creating an identifier, slug, salt,
fixture, etc.
 .
 This library is a dependency of npm, Node.js package manager.
 .
 Node.js is an event-based server-side JavaScript engine.

I'am planing to maintain this package as a part of a javascript maintainers
team.
Pirate Praveen has accepted to sponsor this package.
I would like to join a javascript maintainers team.


Bug#868432: ITP: parsington -- expression parser for SciJava

2017-07-15 Thread Ghislain Antony Vaillant
Package: wnpp
Severity: wishlist
Owner: Ghislain Antony Vaillant 

* Package name: parsington
  Version : 1.0.1
  Upstream Author : Board of Regents of the University of Wisconsin-Madison
* URL : https://github.com/scijava/parsington
* License : BSD
  Programming Lang: Java
  Description : expression parser for SciJava

Long-Description:
 Parsington is an infix-to-postfix (or infix-to-syntax-tree) expression parser
 for mathematical expressions written in Java. It is simple yet fancy, handling
 (customizable) operators, functions, variables and constants in a similar way
 to what the Java language itself supports.
 .
 Parsington is part of the SciJava project for scientific computing in Java.

This software is part of the SciJava / Fiji / ImageJ v2 stack. It will be
maintained by the Debian Science Team.



Re: Naming of network devices - how to improve it in buster

2017-07-15 Thread Luca Capello
Hi there,

On Fri, 14 Jul 2017 23:55:09 -0400, Anthony DeRobertis wrote:
> On 07/11/2017 03:08 PM, Nikolaus Rath wrote:
> > 
> > I wonder if anyone actually uses /dev/disk/by-path?
> 
> It's useful for a quick "ls -l /dev/disk/by-path | grep 'sda$;" to figure
> out which port a disk is plugged into. I'm sure there are other ways,
> probably better ones... but that one is easy to remember when I've been
> paged by a disk failure.

Fully agree, which is the reason at work we decided to use names as in
/dev/disk/by-path for disks in ZFS pools, it is easier then to match a
failed disk when needed to replace it.

Thx, bye,
Gismo / Luca


signature.asc
Description: PGP signature


Bug#868428: ITP: libtime-mock-perl -- shift and scale time

2017-07-15 Thread Hideki Yamane
Package: wnpp
Severity: wishlist
Owner: Hideki Yamane 

* Package name: libtime-mock-perl
  Version : 0.0.2
  Upstream Author : Eric Wilhelm 
* URL : https://metacpan.org/release/Time-Mock
* License : Artistic or GPL-1+
  Programming Lang: Perl
  Description : shift and scale time Perl module

 Test::MockTime is nice, but doesn't allow you to accelerate the timestep
 and doesn't deal with Time::HiRes or give you any way to change the time
 across forks. Time::Mock speed up your sleep(), alarm(), and time() calls.

 (it needs to build libselenium-remote-driver-perl (Bug#839569)



Bug#868381: ITP: imglib2 -- multidimensional image processing library in Java

2017-07-15 Thread Ghislain Antony Vaillant
Package: wnpp
Severity: wishlist
Owner: Ghislain Antony Vaillant 

* Package name: imglib2
  Version : 4.3.0
  Upstream Author : Tobias Pietzsch, Curtis Rueden et al.
* URL : http://imglib2.net/
* License : BSD
  Programming Lang: Java
  Description : multidimensional image processing library in Java

Long-Description:
 ImgLib2 is a general-purpose, multidimensional image processing library.
 .
 It provides an interface-driven design that supports numeric and non-
 numeric data types (8-bit unsigned integer, 32-bit floating point, etc.)
 in an extensible way. It implements several data sources and sample
 organizations, including one single primitive array, one array per
 plane, N-dimensional array "cells" cached to and from disk on demand,
 and planes read on demand from disk.

This software is a dependency of Fiji / ImageJ v2 and the scientific Java
stack. The packaging will be maintained by the Debian Science Team.



Bug#868375: ITP: node-semver-diff -- get the diff type of two semver versions

2017-07-15 Thread srud
Package: wnpp
Severity: wishlist
Owner: Sruthi Chandran 
X-Debbugs-CC: debian-devel@lists.debian.org

* Package name: node-semver-diff
  Version : 2.1.0
  Upstream Author : Sindre Sorhus  (http://sindresorhus.com)
* URL : https://github.com/sindresorhus/sem
ver-diff
* License : Expat
  Programming Lang: JavaScript
  Description : get the diff type of two semver versions

  Returns the difference type between two semver versions, or `null` if they're
  identical or the second one is lower than the first.

  Possible values: 'major', 'minor', 'patch', 'prerelease', 'build', 'null'.

  Node.js is an event-based server-side JavaScript engine.

  This is a dependency of npm.
-BEGIN PGP SIGNATURE-

iQJFBAEBCgAvFiEEsclPZxif+sAmSPvz1N6yL8C5bhUFAlh9FhwRHHNydWRAZGlz
cm9vdC5vcmcACgkQ1N6yL8C5bhWeoQ//bzHXLt9wL8qoV8VN+hWowblH7NfLO/bn
J8y7BqCqyWkinDux16OOyfxC7e4BCw2t1rgAgUj4X0/Y+9LWFsx3wPHseb/u2TWC
Wqz1k9LLjF0XYvi/oeNA2v7Tot1WvTZCcKyQssItTclJ1UbCxhSY8dhovwrk8cKK
hu1FL+vMVaTxcifYpSdXxRmXP7zCKVt2Wp871OjgRJ40leHHqsNT0jgMRgCmMsXB
vLIMCTpyMbnm8NuPoyLdc6Khr+oEqyUXTnxkyMPtN0bR7kxo57PQ/Y0QiFvW6+19
dMaGIGS1ii9jTr98txoLYzVxd1rKHElVOnhJWSxZ+0PnnZVCvBRhbYoRlceZ+4e1
P5Ocesg9OVerO/0F4yBh4sUczVc4d0hFs7QPrYmNjnzEdmHsp+lgNNQfbaZlkG6L
Nc8gKUefZnIB66o7+/7zDsITU76dVnTKv13FxlWa0rBFRAf469aa7atRe9265SgS
hMe1/6vM8kHtwtCnrK5JbwFBjZ3G+fLtNgkILihJMhk5rlgudkhZUVO4LhnChmlS
HotjzJNnuNfruRx4l92bZDZLlR3U4zKfc8Hgc4lPHEEN+aD07EJFQgf+rtTfvmW1
9HRqzk3OBWcKYD6qiXgOZvB77eRwQSq/oGYi73nvl0P2c+CqffwWFrr2GK+OYGlK
F8YfEPRhpS0=
=FVw1
-END PGP SIGNATURE-


Re: Naming of network devices - how to improve it in buster

2017-07-15 Thread Ian Campbell
On Sat, 2017-07-15 at 10:46 +0200, Marc Haber wrote:
> On Thu, 13 Jul 2017 09:36:58 -0700, Josh Triplett
>  wrote:
> >But if you run into a command that accepts filenames but for which
> >bash-completion doesn't complete filenames, *please* report it as a
> bug
> >on the package providing the bash completions for that command.
> 
> To have it end up like #685223?

One (or even multiple) bad experience(s) does not invalidate the
recommendation to file bugs when you find them. Leaving aside whether
or not #685223 is representative of the corpus of such bugs as a whole,
if everyone took such a defeatist attitude towards the possibility of
bugs being fixed then no bugs would ever be filed and the quality of
Debian would be crap.

Ian.



Re: Naming of network devices - how to improve it in buster

2017-07-15 Thread Tollef Fog Heen
]] Marc Haber 

> On Thu, 13 Jul 2017 19:37:52 +0200, Tollef Fog Heen 
> wrote:
> >]] Marc Haber 
> >> My finger memory will still type tcpdump -i eth0 before the brain can
> >> intervene ten years from now.
> >
> >In that particular case, I'll recommend you either leaving out the -i
> >switch completely or just doing `-i any`.  I find it's rare I care about
> >what interface traffic happens on.  YMMV, of course.
> 
> As a general paranoid type of guy, my foot nails curl up when I see a
> tcpdump command line without -i. I don't know where this originates
> from. Did tcpdump support the "listen on all interfaces" semantics
> without -i from the beginning?

I don't think it listens on all interfaces without -i, it just listens
on the first one (I think the first one with a configured address, which
in the trivial case is the one you want).  I don't know why it tickles
your spider sense to run it without -i.

-- 
Tollef Fog Heen
UNIX is user friendly, it's just picky about who its friends are



Re: Naming of network devices - how to improve it in buster

2017-07-15 Thread Marc Haber
On Thu, 13 Jul 2017 09:36:58 -0700, Josh Triplett
 wrote:
>But if you run into a command that accepts filenames but for which
>bash-completion doesn't complete filenames, *please* report it as a bug
>on the package providing the bash completions for that command.

To have it end up like #685223?

Greetings
Marc
-- 
-- !! No courtesy copies, please !! -
Marc Haber |   " Questions are the | Mailadresse im Header
Mannheim, Germany  | Beginning of Wisdom " | http://www.zugschlus.de/
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834



Re: Naming of network devices - how to improve it in buster

2017-07-15 Thread Marc Haber
On Thu, 13 Jul 2017 19:37:52 +0200, Tollef Fog Heen 
wrote:
>]] Marc Haber 
>> My finger memory will still type tcpdump -i eth0 before the brain can
>> intervene ten years from now.
>
>In that particular case, I'll recommend you either leaving out the -i
>switch completely or just doing `-i any`.  I find it's rare I care about
>what interface traffic happens on.  YMMV, of course.

As a general paranoid type of guy, my foot nails curl up when I see a
tcpdump command line without -i. I don't know where this originates
from. Did tcpdump support the "listen on all interfaces" semantics
without -i from the beginning?

Greetings
Marc
-- 
-- !! No courtesy copies, please !! -
Marc Haber |   " Questions are the | Mailadresse im Header
Mannheim, Germany  | Beginning of Wisdom " | http://www.zugschlus.de/
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fon: *49 621 72739834