On Sat, Dec 31, 2016 at 12:13:54AM +, Ian Jackson wrote:
> newsmas...@chiark.greenend.org.uk writes ("(bogus mailing list message)"):
> > 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.
>
> OK then, I
Don Armstrong writes ("Re: Migration despite an RC bug?"):
> I'm still not quite sure how the script was failing. The outer shell
> invocation which calls a perl script to do the versioning database
> update is run with set -e, and the perl script should exit with non-zero
> if it fails to work pro
On Thu, 29 Dec 2016, Christoph Biedl wrote:
> 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 nightmar
Hi,
2016-12-30 12:53 GMT+01:00 Guillem Jover :
> Hi!
>
> On Fri, 2016-12-30 at 09:25:20 +0100, Emilio Pozuelo Monfort wrote:
>> On 29/12/16 23:36, Christoph Biedl wrote:
>> > Emilio Pozuelo Monfort wrote...
>> >> Unforunately, the BTS exported a broken/incomplete RC bug list, and
>> >> britney us
newsmas...@chiark.greenend.org.uk writes ("(bogus mailing list message)"):
> 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.
OK then, I'll bite. I just got my `ip -o addr show' on my laptop to
produce, amo
Lars Wirzenius writes ("Re: Can we kill net-tools, please?"):
> I find ip's output hard to read. I have to take time to visually parse
> it every time, I can't just skim it. The ip -o output seems parseable,
> but no easily extensible (I'd prefer something like YAML instead).
ip's output is certai
Hi Toni,
On Fri, Dec 30, 2016 at 12:58:02AM +0100, Toni Mueller wrote:
> 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 :
Hi Yang,
On Fri, Dec 30, 2016 at 03:23:14PM +0800, Boyuan Yang wrote:
> 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
Am 28. Dezember 2016 05:31:39 MEZ, schrieb Ben Finney :
>Howdy all,
>
>I recently donned the mantle of maintaining ‘dput’ and am carefully
>making improvements. I am conscious of the special need for backward
>compatibility so I am taking care to understand how the Debian
>developer
>community uses
Russell Stuart writes:
> 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: loine
On Mon, 26 Dec 2016 13:29:00 +0100, 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
Hi!
On Fri, 2016-12-30 at 09:25:20 +0100, Emilio Pozuelo Monfort wrote:
> On 29/12/16 23:36, Christoph Biedl wrote:
> > 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
On Fri, 2016-12-30 at 10:42 +0100, Vincent Bernat wrote:
> > I bet the bash authors use that argument when they add another
> > feature. In reality all code has a cost.
>
> The only additional cost is the cost to check if the routing entry is
> a blackhole (while the check for anything else alrea
Andrey Rahmatullin writes:
> 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/ifconf
On Fri, Dec 30, 2016 at 2:32 AM, Andrey Rahmatullin wrote:
>
> Do you really think that
>
> wlp3s0: flags=4163 mtu 1500
> inet 192.168.** netmask 255.255.255.0 broadcast 192.168.**
> inet6 fe80::** prefixlen 64 scopeid 0x20
> ether e4:**:ca txqueuelen 1000 (Ethernet)
❦ 30 décembre 2016 18:55 +1000, Russell Stuart :
>> When you need to decide how to route the packet, you need to do a
>> route lookup. If the route entry you find happens to be a blackhole
>> route, you drop the packet. You didn't do any additional work.
>
> I bet the bash authors use that argum
On 12/29/2016 11:47 PM, Christoph Biedl wrote:
> 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
On Fri, 2016-12-30 at 07:51 +0100, Vincent Bernat wrote:
> The same work is not repeated over and over again. The kernel keeps
> the needed information in a structure to avoid parsing the packet
> several times.
Yes, it does indeed keep the offset of the headers for the various
protocol layers (li
On 29/12/16 20:49, Ben Finney wrote:
> 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
On 29/12/16 23:36, Christoph Biedl wrote:
> 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. Whi
20 matches
Mail list logo
