Re: Processed: reopening 897204, found 897204 in 4.15.17-1, tagging 897204

Path	csiph.com!news.redatomik.org!aioe.org!bofh.it!news.nic.it!robomod
From	Romain Perier <romain.perier@gmail.com>
Newsgroups	linux.debian.kernel
Subject	Re: Processed: reopening 897204, found 897204 in 4.15.17-1, tagging 897204
Date	Fri, 04 May 2018 21:40:01 +0200
Message-ID	<vLOIF-3xi-11@gated-at.bofh.it> (permalink)
References	<vLsRQ-5JT-5@gated-at.bofh.it> <vLsRQ-5JT-3@gated-at.bofh.it> <vLCHv-42D-5@gated-at.bofh.it> <vLD0R-4p7-3@gated-at.bofh.it>
X-Original-To	Romain Perier <romain.perier@gmail.com>, debian-kernel@lists.debian.org
X-Mailbox-Line	From debian-kernel-request@lists.debian.org Fri May 4 19:38:14 2018
Old-Return-Path	<romain.perier@gmail.com>
X-Amavis-Spam-Status	No, score=-7.799 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, LDO_WHITELIST=-5, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
X-Policyd-Weight	using cached result; rate: -7
Dkim-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=sB0aBjNTHM7bxNxr5Cx1XAOWrrC1L0BBTF1LGDGOkP0=; b=WblTR4nV8ENfGxGwCao3ahmwI0uIaE8xy9qXj3LR7/hpM565NFw9TP9gBw9hAdk1tj vUMEADRIj/H1Ch4kFA/5Fz8HR0INUclsYp9N4yyiPj/XnBWRDsjNDo02EvgCHXY22Vxj VmfmK+yLgBeSBzF5wVYJbtDH28t4E0qH3Wo+e3pTAJvbxDb3x5N0D7aPI2KpXsQVPKUj gUe2o04QEDRlfmUZjkBllKQ85vSDxU0Yun0Q5gCArLqvq2vHcmA7YA/DxnvPVcYivRnF T/Uo40y6rdM48MlFhVRieRs6uvqWKdEMz5H082zhq0G6vQ9Rcu07afOKvMV8LEQChPvT FzJQ==
X-Google-Dkim-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=sB0aBjNTHM7bxNxr5Cx1XAOWrrC1L0BBTF1LGDGOkP0=; b=ZFyHPTMOrmG+vXKbCoLkR7YkFFWm6zItxk7+PeSNunY0q6q8PpqQL1tAAAUYrKGszp Kz3FJhLPabpaEv6+fnlnMcQzTNilT+SzgArlsH0Roje33uqcVUYoECNhO3qtwEqCXQvs lLE/oqIbuh3iKRh0trhdqQiuU8rCGcpRLX4u5KkoTTVw4yIzKCn85pR8d8kCZ7xwWS2K amSuhYRo7osEXVlpF72Ac5qwcqVEhnnKSsXn8qai8XtMZGu3tqgodL36KGsDUaDJyt/e J2/9HkF1SpOsYvM8bThOU587lPzFmJVVcSRngdIG5HNRHvovV8ZtE40BkeLXW4nGTcEj 2iBQ==
X-Gm-Message-State	ALQs6tAv2KighOKQUt9C2Yd6xwZGgwYUep72TeEF2jXH9wvP8Ok7ihH+ NCUY9qqq8UN8w4Df/VzrTWN64v01itCLkHOygUM=
X-Google-SMTP-Source	AB8JxZoJgej0j+ylzqKxpRd1B5Yg4qEQefEoT6Szmoc77Emss+P+I6/Ysak0zIdCKiL/xFuIalbcOsWulxqZdubocMc=
X-Received	by 2002:a50:ae46:: with SMTP id c64-v6mr38681011edd.166.1525462676423; Fri, 04 May 2018 12:37:56 -0700 (PDT)
MIME-Version	1.0
Content-Type	text/plain; charset="UTF-8"
X-Mailing-List	<debian-kernel@lists.debian.org> archive/latest/116516
List-ID	<debian-kernel.lists.debian.org>
List-URL	<https://lists.debian.org/debian-kernel/>
List-Archive	https://lists.debian.org/msgid-search/CABgxDoJUzOxo0v-bfSQ99b7NcuK3=_DTHW+CsEpJSP6KacqdwA@mail.gmail.com
Approved	robomod@news.nic.it
Lines	34
Organization	linux.* mail to news gateway
Sender	robomod@news.nic.it
X-Original-Date	Fri, 4 May 2018 21:37:55 +0200
X-Original-Message-ID	<CABgxDoJUzOxo0v-bfSQ99b7NcuK3=_DTHW+CsEpJSP6KacqdwA@mail.gmail.com>
X-Original-References	<1525378576-2061-bts-carnil@debian.org> <handler.s.C.152537858123570.transcript@bugs.debian.org> <CABgxDo+DMfPBVprmAqhvYgWpdkPGeTyG8cv4dMUNZp+XNZ0Dzg@mail.gmail.com> <20180504070419.GA11155@eldamar.local>
Xref	csiph.com linux.debian.kernel:60838

Show key headers only | View raw

Hi,


2018-05-04 9:04 GMT+02:00 Salvatore Bonaccorso <carnil@debian.org>:
> Hi Romain,
>
> On Fri, May 04, 2018 at 08:44:32AM +0200, Romain Perier wrote:
>> Hello,
>>
>> Whoops, I did something wrong apparently, sorry.
>> So I only fixed the issue in sid (4.16), I have to wait that the
>> package is in buster before closing this bug, I guess, right ?
>
> My point was to reopen the bug, the closer is marked correctly in the
> debian/changelog file and it is actually not yet fixed, only in the
> packaging repository commited. Once 4.16.5-2 or maybe an iteration
> with an 4.16.7 import on top, will enter the archive, the BTS will
> correctly handle the closing of the bug (and with correct version, say
> we have then 4.16.7-1 at the time including your change, then the bug
> will bie closed with that version on upload and archive entering
> time).

Ah, I see. I did not know that BTS closes bugs automatically (I need
to continue to read documentation about it).
It makes sense, yes.

>
> Hope this explains my reopening, marking yet as unfixed, tagging as
> pending.

It does, yes :)

Thanks,
Romain

Back to linux.debian.kernel | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Processed: reopening 897204, found 897204 in 4.15.17-1, tagging  897204 "Debian Bug Tracking System" <owner@bugs.debian.org> - 2018-05-03 22:20 +0200
  Re: Processed: reopening 897204, found 897204 in 4.15.17-1, tagging 897204 Romain Perier <romain.perier@gmail.com> - 2018-05-04 08:50 +0200
    Re: Processed: reopening 897204, found 897204 in 4.15.17-1, tagging  897204 Salvatore Bonaccorso <carnil@debian.org> - 2018-05-04 09:10 +0200
      Re: Processed: reopening 897204, found 897204 in 4.15.17-1, tagging 897204 Romain Perier <romain.perier@gmail.com> - 2018-05-04 21:40 +0200

csiph-web