Package: wnpp
Severity: wishlist
Owner: Dmitry Smirnov
X-Debbugs-CC: debian-devel@lists.debian.org,
pkg-go-maintain...@lists.alioth.debian.org
Package name: golang-github-hashicorp-go-hclog
Version: 0.0~git20180402.69ff559-1
Upstream Author: HashiCorp
License: Expat
Package: general
Followup-For: Bug #871613
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome of this actio
On Mon, Jun 25, 2018 at 08:04:01AM +0100, Simon McVittie wrote:
> On Sun, 24 Jun 2018 at 17:05:54 -0600, Daniele Nicolodi wrote:
> > Packages that will use dh_installsystemduser will have maintainer
> > scripts that will depend on the next relese of init-system-helpers.
> > dh_installsystemduser wi
Hi Chris,
[This question came up multiple times already in my e-mails about
regressions in autopkgtests.]
On 27-06-18 23:48, Chris Lamb wrote:
> (Paul, might make more sense to file bugs in future? Much easier to
> track and/or re-assign if necessary..)
I do that when I am *somewhat* confident w
Hi all
On 28-06-18 19:50, Paul Gevers wrote:
> Hi Chris,
^^ this was from my original response, the mail I send half an hour ago
is meant for all.
Paul
signature.asc
Description: OpenPGP digital signature
Hi Paul,
On Thu, Jun 28, 2018 at 07:50:39PM +0200, Paul Gevers wrote:
> Proposal:
> If one (me) can't determine the likely principle package that needs
> fixing after some effort [1], one bug (per upload of the triggering
> package) can be filed against the trigging package with the other
> packa
On 06/28/2018 07:50 PM, Paul Gevers wrote:
> If one (me) can't determine the likely principle package that needs
> fixing after some effort [1], one bug (per upload of the triggering
> package) can be filed against the trigging package with the other
> packages in X-Debbugs-CC and in Affects at nor
Hi Paul,
> > (Paul, might make more sense to file bugs in future? Much easier to
> > track and/or re-assign if necessary..)
Sorry, was not aware that this was something that had already been
discussed, possibly to death.
Totally understand that being confident about where/if the bug exists
will
Hi
On 28-06-18 20:50, Sebastiaan Couwenberg wrote:
> On 06/28/2018 07:50 PM, Paul Gevers wrote:
>> If one (me) can't determine the likely principle package that needs
>> fixing after some effort [1], one bug (per upload of the triggering
>> package) can be filed against the trigging package with t
On Thu, 28 Jun 2018 at 19:50:39 +0200, Paul Gevers wrote:
> This fall-out may be real (it appears to me that the current
> python3-defaults may be an example of that as packages seem to be not
> ready for Python3.7)
Any package that builds a native-code extension is not going to work
with python3.
Processing commands for cont...@bugs.debian.org:
> severity 871613 important
Bug #871613 [general] general: Kernel Panic caused by smp.c:127
check_preempt_curr
Severity set to 'important' from 'critical'
> tags 871613 + moreinfo
Bug #871613 [general] general: Kernel Panic caused by smp.c:127
che
Paul Gevers writes ("Re: Bug filing for autopkgtest regressions? [Was: Re:
appears to break multiple autopkgtests]"):
> On 28-06-18 20:50, Sebastiaan Couwenberg wrote:
> > Please don't file bugs until the triggering package is a single package.
> > Case in point, the upload of gdal (2.3.1+dfsg-1)
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: 1261 (new: 0)
Total number of packages offered up for adoption: 160 (new: 1)
Total number of packages reques
On 06/29/2018 01:41 AM, Ian Jackson wrote:
> Paul Gevers writes ("Re: Bug filing for autopkgtest regressions? [Was: Re:
> appears to break multiple autopkgtests]"):
>> On 28-06-18 20:50, Sebastiaan Couwenberg wrote:
>>> Please don't file bugs until the triggering package is a single package.
>>> C
14 matches
Mail list logo
