Package: wnpp
Severity: wishlist
Owner: Lev Lamberov
* Package name: engine-mode
Version : 2.0.0
Upstream Author : Harry R. Schwartz
* URL : https://github.com/hrs/engine-mode
* License : GPL-3+
Programming Lang: Emacs Lisp
Description : define and que
On Wed, 2016-12-28 at 04:13 +, Scott Kitterman wrote:
>
> On December 27, 2016 11:10:55 PM EST, Adam Borowski
> wrote:
> > On Wed, Dec 28, 2016 at 04:04:21AM +, Scott Kitterman wrote:
> > > > FTR, it's #739636.
> > > >
> > >
> > > Postfix has no way to know it's temporary, so I think a
On Dec 29, Simon Richter wrote:
> As long as there is still a way to have working "netstat" and "ifconfig"
> commands, that is fine.
I do not think that anybody sane wants to remove the package from the
archive: the idea is to stop using it in script in other packages since
iproute is a) better
Hi,
On 29.12.2016 12:49, Marco d'Itri wrote:
>> As long as there is still a way to have working "netstat" and "ifconfig"
>> commands, that is fine.
> I do not think that anybody sane wants to remove the package from the
> archive: the idea is to stop using it in script in other packages since
On Dec 26, Martín Ferrari wrote:
> I am currently the Debian maintainer for net-tools, but note that I have
> not forked, nor I am developing net-tools. Upstream got active again,
> somehow.
Thank you for your clarification.
I think that we have a consensus about this: can you switch to optional
On Wed, Dec 28, 2016 at 01:38:48PM +1000, Russell Stuart wrote:
> I don't know whether "crap" is the right word, but it is certainly
> baggage from a bygone era. "Baggage" here means that if we are nice to
> our users (ie, Debian sysadmins), we should not force them to know two
> tools. We only h
On Thu, Dec 29, 2016 at 10:30:26AM -0500, Theodore Ts'o wrote:
>Ifconfig has been deprecated; you should probably use "ip a show
>dev lo" instad of the shorter and more convenient "ifconfig lo"
... and often wrong
> OK, you can remove the last half, but keep in mind there are plenty of
> p
Hi,
the python-numpy package in unstable has an RC bug:
https://bugs.debian.org/849196
however, today it migrated to testing, the migration status still says
however "valid candidate".
I thought that RC bugs would prevent packages from migration -- what is
the exception here?
Best regards
Ole
On 29/12/16 17:24, Ole Streicher wrote:
> Hi,
>
> the python-numpy package in unstable has an RC bug:
>
> https://bugs.debian.org/849196
>
> however, today it migrated to testing, the migration status still says
> however "valid candidate".
>
> I thought that RC bugs would prevent packages from
Emilio Pozuelo Monfort writes:
> On 29/12/16 17:24, Ole Streicher wrote:
>> Hi,
>>
>> the python-numpy package in unstable has an RC bug:
>>
>> https://bugs.debian.org/849196
>>
>> however, today it migrated to testing, the migration status still says
>> however "valid candidate".
>>
>> I thou
On Thu, Dec 29, 2016 at 10:30:26AM -0500, Theodore Ts'o wrote:
> OK, you can remove the last half, but keep in mind there are plenty of
> people who aren't using the exotic features provided by iproute2, and
> are very happy using the more convenient and shorter BSD-style
> commands. If you're goi
On 12/29/2016 07:04 PM, Lars Wirzenius wrote:
> For stretch+1, what I'd like to see is a tool that a) works b) has
> output that's nice for a human to read and c) has output that can be
> easily processed by programs. None of the current tools comes anywhere
> near. Bonus points if the command line
On Thu, Dec 29, 2016 at 08:17:01PM +0100, Bernd Zeimetz wrote:
> In my opinion ip provides all the things you are mentioning - what are
> you missing? with -o as option the output is rather easy to parse.
I find ip's output hard to read. I have to take time to visually parse
it every time, I can't
Bernd Zeimetz writes:
> On 12/29/2016 07:04 PM, Lars Wirzenius wrote:
>> For stretch+1, what I'd like to see is a tool that a) works b) has
>> output that's nice for a human to read and c) has output that can be
>> easily processed by programs. None of the current tools comes anywhere
>> near. Bo
On Thu, Dec 29, 2016 at 2:38 PM, Russ Allbery wrote:
> Also, this is not at all easy to parse:
>
> # ip -o address
> 1: loinet 127.0.0.1/8 scope host lo\ valid_lft forever
> preferred_lft forever
> 1: loinet6 ::1/128 scope host \ valid_lft forever preferred_lft
> forever
> 3:
Russ Allbery writes:
> I have never managed to work out how to use dcut […] in fewer than
> five tries each time I've needed to use it. I'm not sure what it is
> with that command, but I find it completely baffling to use correctly.
This should be addressed by, at least, improving the ‘dcut(1)’
"Paul R. Tagliamonte" writes:
> FWIW, I don't think any of the dput-ng hackers particularly mind if it
> changes, changing API could just happen for both together, at the same
> time. Or maybe just consolidate :)
Much appreciated. Yes, one aspiration I eventually hope to achieve have
is to resol
On 12/29/2016 08:38 PM, Russ Allbery wrote:
> It certainly doesn't provide a man page that doesn't start with a BNF
> syntax description. The iproute2 documentation is awful.
Ack.
> Also, this is not at all easy to parse:
>
> # ip -o address
> 1: loinet 127.0.0.1/8 scope host lo\ vali
Afif Elghraoui writes:
> Hi, Ben,
Thanks for the feedback. One specific suggestion appears to already have
a bug report; I'm redirecting this sub-thread there.
> على الثلاثاء 27 كانون الأول 2016 20:31، كتب Ben Finney:
> > The ‘dput-ng’ package is one alternative that is sometimes suggested
> >
Christian Seiler writes:
> On 12/29/2016 08:38 PM, Russ Allbery wrote:
>> ip address also has one of the worst output UI decisions I've ever seen,
>> namely this line:
>>
>> inet 192.168.0.195/24 brd 192.168.0.255 scope global dynamic wlan0
>>
>> specifically "192.168.0.195/24", which is no
Russ Allbery, on Thu 29 Dec 2016 12:24:28 -0800, wrote:
> >> specifically "192.168.0.195/24", which is notation (IIRC) invented by this
> >> command,
>
> It's possible that some other tool has abused CIDR notation in this way,
> but ip is still the only place I ever see it. It's definitely not co
❦ 29 décembre 2016 12:24 -0800, Russ Allbery :
> No, I'm not talking about CIDR notation, which of course is long-standing
> and familiar. I'm talking about randomly appending a CIDR suffix to
> something that is obviously *not* the base for that CIDR block.
>
> In other words, 192.168.0.0/24 i
]] Russ Allbery
> It's possible that some other tool has abused CIDR notation in this way,
> but ip is still the only place I ever see it. It's definitely not common.
I picked a few arbitrary networking platforms:
From
http://www.juniper.net/techpubs/software/junos-es/junos-es93/junos-es-jseri
[Russ Allbery]
> ip address also has one of the worst output UI decisions I've ever seen,
> namely this line:
>
> inet 192.168.0.195/24 brd 192.168.0.255 scope global dynamic wlan0
>
> specifically "192.168.0.195/24", which is notation (IIRC) invented by this
> command, used nowhere else in
Tollef Fog Heen writes:
> ]] Russ Allbery
>> It's possible that some other tool has abused CIDR notation in this way,
>> but ip is still the only place I ever see it. It's definitely not common.
> I picked a few arbitrary networking platforms:
Meh. Okay, thanks, I'm apparently just not well-
Bjørn Mork writes:
> I believe that is a mis-interpretation of that RFC. The examples are
> all network addresses, but I don't think there is anything there that
> restricts the CIDR notation only to that class of IPv4 addresses.
> FWIW, the notation is much older and has been used for IPv4 add
Russ Allbery writes:
> Christian Seiler writes:
>> On 12/29/2016 08:38 PM, Russ Allbery wrote:
>
>>> ip address also has one of the worst output UI decisions I've ever seen,
>>> namely this line:
>>>
>>> inet 192.168.0.195/24 brd 192.168.0.255 scope global dynamic wlan0
>>>
>>> specifically
Emilio Pozuelo Monfort wrote...
> Unforunately, the BTS exported a broken/incomplete RC bug list, and britney
> used
> that and didn't see that some packages had an RC bug, so it allowed them to
> migrate.
Ouch, that's quite a nightmare. While I'm curious to learn how this
happened and what is
Eduard Bloch wrote...
> I volunteer as test subject for that experiment. I would appreciate even
> small steps, considering the current laptop in front of me with average
> magnetic HDD. Over a minute boot time, which is insane and IMHO mostly
> caused by the storm of IO operations required nowada
On 2016-12-29 11:38 -0800, Russ Allbery wrote:
> Bernd Zeimetz writes:
> > On 12/29/2016 07:04 PM, Lars Wirzenius wrote:
>
> Also, this is not at all easy to parse:
>
> # ip -o address
> 1: loinet 127.0.0.1/8 scope host lo\ valid_lft forever
> preferred_lft forever
> 1: loinet6 ::
On Fri, 30 Dec 2016 06:49:07 +1100, Ben Finney wrote:
> > I always have to use dput-ng in order to be able to use the dcut dm
> > […] command and grant DMs upload permissions.
>
> There is not ‘dm’ command is not mentioned at the upload queue Read Me
> document ftp://ftp.upload.debian.org/pub/Upl
On Thu, 2016-12-29 at 11:38 -0800, Russ Allbery wrote:
> It certainly doesn't provide a man page that doesn't start with a BNF
> syntax description. The iproute2 documentation is awful.
>
> Also, this is not at all easy to parse:
>
> # ip -o address
> 1: loinet 127.0.0.1/8 scope host lo\ vali
Russell Stuart writes:
> To me this thread looks like a bunch of old men grumbling that the
> young'ins have taken over what they created and turned the tools they
> were comfortable with into something unrecognisable. It's true - they
> did do that, and it's true it was unnecessary. They could
Package: wnpp
Severity: wishlist
Owner: Toni Mueller
* Package name: ansible-doc
Version : 2.2.0.0-1
Upstream Author : RedHat
* URL : http://www.ansible.com/
* License : GPL-3
Programming Lang: HTML, JavaScript
Description : Documentation for Ansible
On Thu, Dec 29, 2016 at 09:01:51PM +0500, Andrey Rahmatullin wrote:
> > OK, you can remove the last half, but keep in mind there are plenty of
> > people who aren't using the exotic features provided by iproute2
> ... like two IPs on one iface.
Actually, that is only a problem if you re-use label
Package: wnpp
Severity: wishlist
Owner: Daniel Manila
* Package name: weresync
Version : 0.2
Upstream Author : Daniel Manila
* URL : https://github.com/DonyorM/weresync
* License : Apache2
Programming Lang: Python3
Description : A program to easily cl
❦ 30 décembre 2016 09:47 +1000, Russell Stuart :
> [0] Now I've started, the Linux kernel's networking stack is a mess.
> From the outside it looks like a mob of warning tribes, each
> developing with their own way of doing the same thing. To people
> not familiar with it this wil
❦ 29 décembre 2016 23:09 GMT, Wookey :
> I still don't know what a qdisc is or a default group, but it's a lot
> easier to find things I do recognise. Before this discussion I just
> saw it as a mysterious jumble of 10 things (after a set of things in
> CAPITALS that were somewhat mysterious too
Hello all,
I am wondering if it is possible for a downstream mirror site to mirror files
in the debian-debug repository. [1] (of course, via rsync not http)
I searched the Internet but could not find any instruction or explanation about
mirroring that repo.
A quick access to -dbgsym packages ma
On Thu, Dec 29, 2016 at 11:09:35PM +, Wookey wrote:
> Yeah I think that mess is why I've never felt any need to move away
> from ifconfig. I ran ip something a few times, went 'huh?' at the cryptic
> output and stayed with the rather more civilised /sbin/ifconfig.
>
> So it seem that the outpu
40 matches
Mail list logo
