Hi Santiago,
On Sat, 15 Aug 2015, Santiago Vila wrote:
1. This seems a mass-bug filing, which last time I checked it is
something that should not be done before asking in -devel. Did I
miss the announcement about this mass bug filing?
no, you did not miss anything.
An announcement is only
On Sun, 16 Aug 2015, Santiago Vila wrote:
2. Why would policy say should instead of must, if we then do not
allow for exceptions? (packages generating copyright file at build time).
This is not my area, but why should there be an exception?
To allow for the file to be automatically
On Sun, 23 Aug 2015, Julien Cristau wrote:
On Sun, Aug 23, 2015 at 18:09:16 +0200, Thorsten Alteholz wrote:
On Sun, 23 Aug 2015, Julien Cristau wrote:
FWIW I disagree with this change, I don't think making a new requirement
for source packages is the way to solve NEW review workflow
On Sun, 23 Aug 2015, Julien Cristau wrote:
FWIW I disagree with this change, I don't think making a new requirement
for source packages is the way to solve NEW review workflow.
Oh, lintian already complains about a missing debian/copyright in the
source package. So this change is not a new
On Sun, 16 Aug 2015, Russ Allbery wrote:
I think this has come up before, and my recollection of where we ended up
in the past is that there probably isn't any *legal* reason to require
debian/copyright in source packages.
Hmm, lots of licenses require their text distributed together with
On Sun, 16 Aug 2015, Simon McVittie wrote:
I would love to not have to do this (see
https://bugs.debian.org/768292, https://bugs.debian.org/795402) but
at the moment it's the only way I can see to have debian/copyright in a
form that is easy to modify. At the moment, I also include the
On Tue, 25 Aug 2015, Santiago Vila wrote:
On Sun, 23 Aug 2015, Thorsten Alteholz wrote:
But policy says that there should be such a copyright file. Violating such a
clause is at least an important bug.
I guess you refer to policy when it says that we could match must
with serious
Hi,
is the description[1] on howto incorporate changes to the policy still
valid? So the first step would be to add tags to all bugs?
Would it be possible to push the changes for 3.9.8.0 to the git repository?
Thorsten
[1]https://wiki.debian.org/PolicyChangesProcess
On Thu, 1 Feb 2018, Guillem Jover wrote:
diff --git a/common.ent b/common.ent
index 1bbed6a..561af11 100644
--- a/common.ent
+++ b/common.ent
@@ -48,6 +48,7 @@
+
I think using ssh.upload.debian.org here would be the more correct fix?
Oh, yes, you are right.
Thorsten
Package: developers-reference
Version: 3.4.19
Severity: normal
Tags: patch
Hi,
in paragraph 5.6.5 you recommend to login to ssh.debian.org to find the
logfile for queued. This seems to be no longer true. Nevertheless the
logfiles can be found on usper.
Thorstendiff --git a/common.ent
10 matches
Mail list logo
