❦ 3 janvier 2018 08:43 +0200, Lars Wirzenius :
> Over the past several years, I've spent less time updating
> Standard-Version in my own packages than I've spent reading this email
> thread. I don't want to ridicule anyone's concerns, but I'm of the
> opinion that when it comes to S-V, the conc
On Tue, Jan 02, 2018 at 09:33:08PM -0800, Steve Langasek wrote:
> These statements are not in contradiction. Saying "this package complies
> with policy version X" doesn't say anything about what version of policy the
> package *should* comply with. Our tooling should absolutely be optimized
> fo
On Wed, Jan 03, 2018 at 10:22:19AM +0500, Andrey Rahmatullin wrote:
> On Tue, Jan 02, 2018 at 04:25:07PM -0800, Steve Langasek wrote:
> > > If S-V is declaring that the package conforms to some older version of the
> > > policy then all the tools should check that package against that policy
> > >
On Tue, Jan 02, 2018 at 04:25:07PM -0800, Steve Langasek wrote:
> > If S-V is declaring that the package conforms to some older version of the
> > policy then all the tools should check that package against that policy
> > and not against the latest one.
>
> No, they should not. S-V is a declarat
On Sunday, December 31, 2017 8:42:29 PM CST Stuart Prescott wrote:
> Vincent Bernat wrote:
> > Lintian is full of opinions. For example, I often get:
> >
> > W: python-pysnmp4-doc: extra-license-file
> > usr/share/doc/python-pysnmp4-doc/html/_sources/license.txt
>
> That is not an opinion, it is
Package: wnpp
Severity: wishlist
Owner: Daniel Ring
X-Debbugs-CC: debian-devel@lists.debian.org
* Package name: node-js-cookie
Version : 2.2.0
Upstream Author : Klaus Hartl
* URL : https://github.com/js-cookie/js-cookie
* License : Expat
Programming Lang: Jav
On Tue, Jan 02, 2018 at 12:55:36PM +0500, Andrey Rahmatullin wrote:
> On Mon, Jan 01, 2018 at 05:26:35PM +, Sean Whitton wrote:
> > IMO the point of the field is to ensure that you /don't/ have to upgrade
> > to the latest version of Policy right away. It allows you to keep track
> > of the ve
Markus Koschany writes:
> I believe that the Standards-Version header should not be part of a
> debian/control file. I understand your reasoning why you want to keep it
> and why it is useful for you. Though in my opinion a debian/control
> file, or generally speaking all information in debian/,
On Tue, 02 Jan 2018 22:19:26 +0100, Vincent Bernat wrote:
> Good to know. Unfortunately, I get "E: x source:
> no-standards-version-field" from Lintian. Won't the package be rejected
> by FTP masters?
Doesn't seem so:
% grep no-standards-version-field
/usr/share/lintian/profiles/debian/
Am 02.01.2018 um 21:57 schrieb Tollef Fog Heen:
> ]] Markus Koschany
>
>> Am 02.01.2018 um 19:38 schrieb Russ Allbery:
>> [...]
>>> I think of the Standards-Version header in a package is a bookmark: this
>>> is where I last left off in updating the packaging. It doesn't change the
>>> standard
Processing control commands:
> reassign -1 coreutils
Bug #886173 [general] general: ls quotes results with special characters in its
output
Bug reassigned from package 'general' to 'coreutils'.
Ignoring request to alter found versions of bug #886173 to the same values
previously set
Ignoring req
Control: reassign -1 coreutils
On Tue, 2018-01-02 at 20:38 +, mqu...@neosmart.net wrote:
[...]
> In particular, `ls` output (both in regular and `-l` modes) wraps in
> single quotes the names of files that contain special characters (or, at
> least, a parenthesis), meaning its output is not an
Hi,
On Sun, 31 Dec 2017, Riku Voipio wrote:
> On Tue, Dec 26, 2017 at 02:17:24PM +0100, Arturo Borrero Gonzalez wrote:
> > Following with your example (pkg-suricata-team) I prefer to make it
> > explicit for people outside debian that this is about packaging.
> > So I usually put the 'pkg' string
On Thu, 28 Dec 2017, Marc Haber wrote:
> On Tue, 26 Dec 2017 14:48:50 +0100, Mattia Rizzolo
> wrote:
> >On Tue, Dec 26, 2017 at 02:45:38PM +0100, Marc Haber wrote:
> >> The time before the last time I asked about tracker, the answer was
> >> that this was not yet possible due to old lintian doing
❦ 2 janvier 2018 21:57 +0100, Tollef Fog Heen :
> Also, the Standards-Version header is only recommended to be included,
> it's not mandatory. If its existence offends you so much and you have
> so few bugs to fix in your packages that the primary effort of
> maintaining your package is updati
Package: wnpp
Owner: Damyan Ivanov
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org, debian-p...@lists.debian.org
* Package name: libmail-transport-perl
Version : 3.001
Upstream Author : Mark Overmeer
* URL : https://metacpan.org/release/Mail-Transport
*
]] Markus Koschany
> Am 02.01.2018 um 19:38 schrieb Russ Allbery:
> [...]
> > I think of the Standards-Version header in a package is a bookmark: this
> > is where I last left off in updating the packaging. It doesn't change the
> > standard by which the package should be judged.
>
> I believe
Package: general
Severity: normal
Dear Maintainer,
On a clean installation of debian buster, I ran into an issue where the
output of `ls` in various modes led me to confusedly attempt to figure
out where my scripting had gone wrong.
In particular, `ls` output (both in regular and `-l` modes) wra
Am 02.01.2018 um 19:38 schrieb Russ Allbery:
[...]
> I think of the Standards-Version header in a package is a bookmark: this
> is where I last left off in updating the packaging. It doesn't change the
> standard by which the package should be judged.
I believe that the Standards-Version header s
Package: wnpp
Severity: wishlist
Owner: Sandro Knauß
* Package name: ksmtp
Version : 17.12.0
Upstream Author : KDE Pim
* URL : https://projects.kde.org/projects/kde/pim/ksmtp
* License : LGPL-2.1+
Programming Lang: C++
Description : library for handling
Package: wnpp
Owner: gregor herrmann
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org, debian-p...@lists.debian.org
* Package name: libmoosex-util-perl
Version : 0.006
Upstream Author : Chris Weyl
* URL : https://metacpan.org/release/MooseX-Util
* Licens
Package: wnpp
Owner: gregor herrmann
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org, debian-p...@lists.debian.org
* Package name: libmoosex-traitfor-meta-class-betteranonclassnames-perl
Version : 0.002003
Upstream Author : Chris Weyl
* URL :
https://m
Andrey Rahmatullin writes:
> On Mon, Jan 01, 2018 at 05:26:35PM +, Sean Whitton wrote:
>> IMO the point of the field is to ensure that you /don't/ have to
>> upgrade to the latest version of Policy right away. It allows you to
>> keep track of the version of Policy you are up-to-date with, s
Package: wnpp
Severity: wishlist
Owner: Guus Sliepen
* Package name: mstch
Version : 1.0.2
Upstream Author : Daniel Sipka
* URL : https://github.com/no1msd/mstch
* License : MIT
Programming Lang: C++
Description : Mustache implementation in C++11
Mstc
On Tue, Jan 02, 2018 at 08:29:00AM +, Niels Thykier wrote:
> > If S-V is declaring that the package conforms to some older version of the
> > policy then all the tools should check that package against that policy
> > and not against the latest one.
> >
>
> Lintian's architecture does not len
Quoting Niels Thykier (2018-01-02 12:19:00)
> Jonas Smedegaard:
> > Quoting Niels Thykier (2018-01-02 09:23:00)
> >> Andrey Rahmatullin:
> >>> On Mon, Jan 01, 2018 at 08:40:38PM +0100, Jérémy Lal wrote:
> wouldn't it be simpler to couple debhelper dependency to
> Standards-Version ?
> >>
Jonas Smedegaard:
> Quoting Niels Thykier (2018-01-02 09:23:00)
>> Andrey Rahmatullin:
>>> On Mon, Jan 01, 2018 at 08:40:38PM +0100, Jérémy Lal wrote:
wouldn't it be simpler to couple debhelper dependency to
Standards-Version ?
>>> There are packages which may break with newer debhelper,
Quoting Niels Thykier (2018-01-02 09:23:00)
> Andrey Rahmatullin:
>> On Mon, Jan 01, 2018 at 08:40:38PM +0100, Jérémy Lal wrote:
>>> wouldn't it be simpler to couple debhelper dependency to
>>> Standards-Version ?
>> There are packages which may break with newer debhelper, but can be
>> easily up
Andrey Rahmatullin:
> On Mon, Jan 01, 2018 at 05:26:35PM +, Sean Whitton wrote:
>> IMO the point of the field is to ensure that you /don't/ have to upgrade
>> to the latest version of Policy right away. It allows you to keep track
>> of the version of Policy you are up-to-date with, so you can
Andrey Rahmatullin:
> On Mon, Jan 01, 2018 at 08:40:38PM +0100, Jérémy Lal wrote:
>> wouldn't it be simpler to couple debhelper dependency to
>> Standards-Version ?
> There are packages which may break with newer debhelper, but can be easily
> updated to the current policy.
>
Also, there are pack
30 matches
Mail list logo
