[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#868497: marked as done (debian-policy: Signed .dsc Files)



Your message dated Sun, 16 Jul 2017 19:27:19 -0700
with message-id <CAJqvfD9-mhKzj=yAZUviMP-Da0mehLNUj157_Q-NfmbYAOnTtQ@mail.gmail.com>
and subject line Re: Bug#868497: debian-policy: Signed .dsc Files
has caused the Debian Bug report #868497,
regarding debian-policy: Signed .dsc Files
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
868497: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=868497
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: debian-policy
Version: 4.0.0.4
Severity: wishlist

--

Debian Policy Manual, Section 5.4, "Debian source control files -
.dsc", states in the first sentence:

"This file consists of a single paragraph, possibly surrounded by a
PGP signature."

This does not state whether someone who is creating a package to be
uploaded by a sponsor can clearsign their own .dsc file, or if only
the sponsor is able to do that without causing upload problems.

What is permissible?  Can you clarify that in a future update to this section?

Thank you,


Paul Hardy

--- End Message ---
--- Begin Message ---
Because the ambiguity in the Debian Policy Manual about whose
signature can appear in a .dsc file does not affect the normal upload
process, I am closing this bug.  See the discussion earlier in this
thread.

Thanks,


Paul Hardy

--- End Message ---

Reply to: