Work-needing packages report for Jul 14, 2017

2017-07-13 Thread wnpp
The following is a listing of packages for which help has been requested through the WNPP (Work-Needing and Prospective Packages) system in the last week. Total number of orphaned packages: 1101 (new: 5) Total number of packages offered up for adoption: 169 (new: 0) Total number of packages reques

Bug#868274: ITP: lxqt-themes-extra -- Extra themes for LXQt (debian and derivatives)

2017-07-13 Thread Alf Gaida
Package: wnpp Severity: wishlist Owner: Alf Gaida * Package name : lxqt-themes-extra Version : 0.11.96 Upstream Author : Alf Gaida * URL : https://anonscm.debian.org/cgit/pkg-lxqt/lxqt-themes-extra.git/ * License : LGPL Programming Lang: n.A. Description : Extra themes for LXQt (debian

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

2017-07-13 Thread Russell Stuart
On Thu, 2017-07-13 at 09:07 -0700, Russ Allbery wrote: > Er, I saw this all the time without udev persistent naming.  Every > time we rebooted one of our servers, the four onboard NICs (of which > we were only using one -- long story, but basically that's just what > the systems came with out of th

Bug#868271: ITP: erlang-asciideck -- Erlang library for asciidoc

2017-07-13 Thread Nobuhiro Iwamatsu
Package: wnpp Severity: wishlist Owner: Nobuhiro Iwamatsu * Package name: erlang-asciideck Version : 0 Upstream Author : Loïc Hoguin * URL : https://github.com/ninenines/asciideck * License : ISC Programming Lang: Erlang Description : Erlang library fo

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

2017-07-13 Thread Russ Allbery
Philipp Kern writes: > On 13.07.2017 18:07, Russ Allbery wrote: >> The workaround was a bunch of bullshit in our install process to try to >> figure out which NIC got the DHCP response and then pin that one to >> eth0 for subsequent boots. (Which is basically what udev persistent >> naming did.)

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

2017-07-13 Thread Philipp Kern
On 13.07.2017 18:07, Russ Allbery wrote: > The workaround was a bunch of bullshit in our install process to try to > figure out which NIC got the DHCP response and then pin that one to eth0 > for subsequent boots. (Which is basically what udev persistent naming > did.) At least when you netboot t

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

2017-07-13 Thread Alex Muntada
Nikolaus Rath: > I wonder if anyone actually uses /dev/disk/by-path? We used it at work to filter guest LVM VGs out of libvirt hosts: # grep by-path /etc/lvm/lvm.conf filter = [ "r|^/dev/disk/by-path/ip-.*-iscsi|" ] Cheers! Alex signature.asc Description: PGP signature

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

2017-07-13 Thread Tollef Fog Heen
]] Russell Stuart > It's not sysadmin's managing fleets of machines. They need persistent > names, but you rapidly go insane if the lan NIC isn't named "lan0" or > something regardless of the machine your platform is running on. So > you end up dropping your own customer files in /etc/udev/rule

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

2017-07-13 Thread Tollef Fog Heen
]] 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.

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

2017-07-13 Thread Josh Triplett
Adam Borowski wrote: > Alas, having "bash-completion" installed, while adding some > context-sensitive completion, also breaks filename completion. You can always press Alt-/ if you want to use filename completion unconditionally. But if you run into a command that accepts filenames but for which

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

2017-07-13 Thread Marc Haber
On Wed, 12 Jul 2017 18:47:18 +0200, Michael Biebl wrote: >Am 12.07.2017 um 17:35 schrieb Marc Haber: >> My finger memory will still type tcpdump -i eth0 before the brain can >> intervene ten years from now. > >thankfully tcpdump (and lots of other tools) have nice shell completion. >tcpdump -i wo

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

2017-07-13 Thread Russ Allbery
Russell Stuart writes: > On Thu, 2017-07-13 at 11:21 +, Clinton Roy wrote: >> Unfortunately, others have (well, not the kernel, but PCI): >> >> https://lists.freedesktop.org/archives/systemd-devel/2017-May/038924. >> html > If you plug new hardware devices in then of course things are going

Autocad Users List

2017-07-13 Thread madeleine . turner
style="margin-bottom:0.0001pt;line-height:normal">face="Times New Roman, serif">Hello there,style="margin-bottom:0.0001pt;line-height:normal">face="Times New Roman, serif">style="font-size:13.px"> style="margin-bottom:0.0001pt;line-height:normal">face="Times New Roman, serif">Might want to

Re: produce exact package builds?

2017-07-13 Thread Chris Lamb
Hi Lenz, > i have several installations of debian.. and i noted that when i made a > package, that builds are not exactly equals.. > > i heard in some place/site/mailist that now can produce equal package > binary's ? or its impossible! Not at all. Please see: https://wiki.debian.org/Reproduc

produce exact package builds?

2017-07-13 Thread PICCORO McKAY Lenz
i have several installations of debian.. and i noted that when i made a package, that builds are not exactly equals.. i heard in some place/site/mailist that now can produce equal package binary's ? or its impossible! i ask due its important, due binary can/may be affected by the changes of the s

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

2017-07-13 Thread Russell Stuart
On Thu, 2017-07-13 at 11:21 +, Clinton Roy wrote: > Unfortunately, others have (well, not the kernel, but PCI): > > https://lists.freedesktop.org/archives/systemd-devel/2017-May/038924. > html If you plug new hardware devices in then of course things are going to change. The claim really is

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

2017-07-13 Thread Adam Borowski
On Wed, Jul 12, 2017 at 06:47:18PM +0200, Michael Biebl wrote: > Am 12.07.2017 um 17:35 schrieb Marc Haber: > > My finger memory will still type tcpdump -i eth0 before the brain can > > intervene ten years from now. > > thankfully tcpdump (and lots of other tools) have nice shell completion. > tcp

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

2017-07-13 Thread Adam Borowski
On Thu, Jul 13, 2017 at 05:17:57AM -0400, Tom H wrote: > > This caught me out on a recent new installation, which gave me these new > > names which are too complicated to be usable. I wasted hours working out > > what had happened, how to fix it and how to write a udev rules file from > > scratch.

Bug#868061: marked as done (general: Sleep not reliable)

2017-07-13 Thread Debian Bug Tracking System
Your message dated Thu, 13 Jul 2017 12:20:55 +0100 with message-id <1499944855.2707.135.ca...@decadent.org.uk> and subject line Re: Bug#868061: general: Sleep not reliable has caused the Debian Bug report #868061, regarding general: Sleep not reliable to be marked as done. This means that you clai

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

2017-07-13 Thread Clinton Roy
On Thu, 13 Jul 2017 at 20:15 Russell Stuart wrote: > > I've never seen the kernel vary the order it enumerates a PCI bus. Unfortunately, others have (well, not the kernel, but PCI): https://lists.freedesktop.org/archives/systemd-devel/2017-May/038924.html cheers, -- -- Clinton Roy, Softwar

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

2017-07-13 Thread Ben Hutchings
On Thu, 2017-07-13 at 20:14 +1000, Russell Stuart wrote: > On Thu, 2017-07-13 at 05:20 -0400, Tom H wrote: > > Stateless "/etc". > > > > Systems with multiple NICs where the order in which they're > > recognized by the kernel can vary. > > I asked for a person.  I guess I really asking for a use

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

2017-07-13 Thread Ben Hutchings
On Tue, 2017-07-11 at 17:05 +0200, Samuel Thibault wrote: > Simon McVittie, on mar. 11 juil. 2017 15:18:26 +0100, wrote: > > Network devices are (as far as I know) the only class of device managed by > > udev that is not backed by a device node, which means udev cannot provide > > multiple equivale

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

2017-07-13 Thread Russell Stuart
On Thu, 2017-07-13 at 05:20 -0400, Tom H wrote: > Stateless "/etc". > > Systems with multiple NICs where the order in which they're > recognized by the kernel can vary. I asked for a person. I guess I really asking for a use case. "Stateless /etc" isn't either. I've never seen the kernel vary

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

2017-07-13 Thread Tom H
On Thu, Jul 13, 2017 at 12:22 AM, Russell Stuart wrote: > > I still don't understand what use case the current scheme is aimed at. Stateless "/etc". Systems with multiple NICs where the order in which they're recognized by the kernel can vary.

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

2017-07-13 Thread Tom H
On Wed, Jul 12, 2017 at 2:40 PM, Roger Lynn wrote: > On 10/07/17 19:40, Marvin Renich wrote: >> >> 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 sys

Re: Bad interaction between pbuilder/debhelper/dpkg-buildinfo/dpkg-genchanges and dak on security-master

2017-07-13 Thread James Clarke
On 12 Jul 2017, at 10:30, Ian Jackson wrote: > James Clarke writes ("Re: Bad interaction between > pbuilder/debhelper/dpkg-buildinfo/dpkg-genchanges and dak on > security-master"): >> Having the _amd64.buildinfo included in a _source.changes created by >> dpkg-genchanges -S in a tree which has d

Re: Bad interaction between pbuilder/debhelper/dpkg-buildinfo/dpkg-genchanges and dak on security-master

2017-07-13 Thread Ian Jackson
James Clarke writes ("Re: Bad interaction between pbuilder/debhelper/dpkg-buildinfo/dpkg-genchanges and dak on security-master"): > On 12 Jul 2017, at 10:30, Ian Jackson wrote: > > Wait, what ? You're telling me that dpkg-genchanges will pick up > > random .buildinfo files it happens to find lyi

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

2017-07-13 Thread Guus Sliepen
On Wed, Jul 12, 2017 at 07:16:16PM -0300, Henrique de Moraes Holschuh wrote: > > Indeed, the best solution would be to never rename the interfaces and > > simply create aliases / symlinks. Then again, I'm no kernel hacker so I > > have no idea if that would be feasible. > > ip link set dev eth0 a