Hello,
On Thu 14 Feb 2019 at 08:45PM +01, Christian Kastner wrote:
> On 2012-08-21 14:34:50 +0200 Andreas Tille wrote:> I
> would propose the following addition to
>>
>> http://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
>>
>> --- 8< -
Processing control commands:
> tag -1 +pending
Bug #917431 [debian-policy] debian-policy: virtual packages: logind,
default-logind
Added tag(s) pending.
--
917431: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917431
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
control: tag -1 +pending
Hello Simon,
On Sun 30 Dec 2018 at 03:52PM +00, Simon McVittie wrote:
> Maybe "via D-Bus and " or "via D-Bus and sd-login(3)"?
I've committed the latter.
> If a logind provider such as elogind doesn't result in the libsystemd
> sd-login APIs working (at least as well a
Processing control commands:
> tag -1 +pending
Bug #920355 [debian-policy] debian-policy: Permit branch specifications ("-b")
in Mercurial Vcs-Hg headers
Bug #897217 [debian-policy] debian-policy: Vcs-Hg should support -b too
Added tag(s) pending.
Added tag(s) pending.
--
897217: https://bugs.d
control: tag -1 +pending
Hello,
On Thu 24 Jan 2019 at 05:05PM +01, Chris Lamb wrote:
> diff --git a/policy/ch-controlfields.rst b/policy/ch-controlfields.rst
> index 44080c9..013aae4 100644
> --- a/policy/ch-controlfields.rst
> +++ b/policy/ch-controlfields.rst
> @@ -973,10 +
Processing commands for cont...@bugs.debian.org:
> unarchive 824495
Bug #824495 {Done: Sean Whitton } [debian-policy]
debian-policy: Source packages "can" declare relationships
Unarchived Bug 824495
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
824495: https://
Hello,
Use of the Build-Conflicts field is currently mostly optional, but Ian
Jackson and I have been working on text for Debian Policy that would
require its use in certain cases. See #824495 for the discussion.
There are two cases which we think that everyone would agree that there
is a bug, b
On Friday, February 15, 2019 08:59:41 PM Sean Whitton wrote:
> Hello,
>
> Use of the Build-Conflicts field is currently mostly optional, but Ian
> Jackson and I have been working on text for Debian Policy that would
> require its use in certain cases. See #824495 for the discussion.
>
> There ar
Sean Whitton writes:
> Use of the Build-Conflicts field is currently mostly optional, but Ian
> Jackson and I have been working on text for Debian Policy that would
> require its use in certain cases. See #824495 for the discussion.
>
> There are two cases which we think that everyone would agree
9 matches
Mail list logo
