Hi josch,
Thanks for putting together the necessary documentation for Build-Depends-
Arch and Build-Conflicts-Arch.
> Could somebody please comment on the patch? I'd like to fix its problems
> if they exist.
Your patch looks good to me.
cheers
Stuart
--
Stuart Presc
ther languages and the name does not include the $. Documentation of the
environment such as environ(7) or the Open Group standards normally omits
the $ as a result. (I can find only one use of $ in Policy outside
shell/make snippets.)
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/
ld file a bug
against debhelper for that, suggesting a cross-reference to the deb-
conffiles(5) page? (It would also be good if the new maintainer's guide
could point at the documentation rather than duplicate it so that people
learn where these things are actually documented -- perhaps yo
on modules team refer to
README.source as the place to document that a package is not using their
standardised tool (git-dpm) and why, for instance.
cheers
Stuart
¹ build-rdeps quilt = 760; build-rdeps dpatch = 108
² https://lintian.debian.org/tags/debian-rules-uses-deprecated-makefile.html
³ https
and
that's not an issue as it is only permitted to contain one value.
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
-- please include the people who write code based
on the copyright-format specification in the discussion of specification
changes and include them early on. (cme, lintian, sources.d.o, python-debian
are the ones that come to mind; there are probably others) People who write
parsers are probably po
xrwx … /usr/lib/nodejs/backbone/index.js ->
../../../share/javascript/backbone/backbone.js
(md5sum dereferences symlinks)
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D
kets are only making work for people who will
have to rewrite parsers because the license short names are not the opaque
tokens originally given in copyright-format/1.0.*
Given they are unnecessary and actively harmful, let's not adopt this
syntax.
Stuart
* almost opaque, given "+&
s of the format receiving on-going papercuts.
(The brackets, however, remain unnecessary.)
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
if the specification were to include details of how it
will be updated so that producers and consumers understand what the contract
really looks like and the intended balance between backwards compatibility
and innovation.
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu
upon a compatible module
tree and that is not necessarily available to the locally installed
interpreter. (Python people are strongly encouraged not to use /usr/local/bin/
python for precisely this reason, using, say, virtualenv instead.)
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.
src:texlive-extra
should use dh_python*.
Once done, these shebangs would be rewritten.
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
istribution-supplied tools while only doing things in the
admin's /usr/local playground.
Flexibility sits on a scale between fragile and robust. The trick is working
out how many footguns are appropriate to leave around our distribution.
cheers
Stuart
--
Stuart Prescotthttp://www.nanonano
oring it seems wrong.
Thanks in advance for your suggestions!
Stuart
(on behalf of the Python BoF at DebConf18)
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
-progress.
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
being created.
https://codesearch.debian.net/search?q=path%3Adebian%2Frules+%5B+%5DHOME%3D
(I would cheerfully second the above text if my [deliberate] misreading is
an outlier and any tightening of the text is so hard to understand that it's
not actually an improvement.)
cheers
Stuart
--
St
ers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
signature later on should I wish to do so and I assume I need to know what
to git clone and which tag to git tag -v.
regards
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 891D BBC1 7EBB 1396 F2F7
Package: debian-policy
Version: 3.9.2.0
Severity: normal
Currently, §7.1 refers to the archtecture restriction syntax and architecture
wildards without defining what the syntax for these restrictions is. The
syntax for these clauses is defined in §11.1 (§11.1.1 in particular) but is not
linked to
rom the maintainer of a game data downloader on d-devel to work towards
this goal.
https://lists.debian.org/debian-devel/2014/06/msg00261.html
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@
s to deal with the full gamut of possibilities that the various RFCs
would permit if we referenced only them.
In practical terms, what is required now to wrap this up?
(Knowing how Uploaders should be split would then allow us to expose
functionality to do this in python-debian.)
cheers
what other packages they may depend on. We should
> by default just trust them.
which makes me think that you see no reason why ftp-master is controlling
Priority either. With your ftp-master hat on, is there any reason not to
just rip all that overrides code out of dak and i
ctice and, in the spirit of
policy documenting practice, it would be good to include the likely
implementers in this discussion. It would seem important to have a feasible
implementation that doesn't require us reverting to a debian/rules listing
out every dh_* command in the s
yish packages and not missing
packages) is an important task for more immediate consideration.
cheers
Stuart
--
Stuart Prescotthttp://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint90E2 D2C1 AD14 6A1B 7EBB 8
al fields added, it may actually start to distract
from the purpose of policy and perhaps should be in dev-ref... but that's a
completely different discussion again.
regards
Stuart
(Please Cc me as I'm not subscribed to the bugs/lists in question)
--
Stuart Prescott www.nanoNANOnano.net
signature.asc
Description: This is a digitally signed message part.
s good to me. It certainly answers my original question
that caused me to look at policy (and as in #d-mentors) as well as answering
a few others that I didn't even know I should ask before.
cheers
Stuart
--
Stuart Prescott www.nanoNANOnano.net
--
To UNSUBSCRIBE, e
inct IDs" to
"TAGOBJID".
I'd also suggest the keyword _annotated_ is included in there - from
what I can see, this property is only for annotated tags and so folks
just poking at git tags to understand what is going on won't see these
details. tag2upload is, of course, usi
ast that Policy was there to
document current practice. Personally, I welcome this as a new normal:
new things where interoperability is important get documented in Policy
first. Given that documenting something with zero current usage is,
perhaps, a departure from how Policy discussions often go, i
Hi Sean
On 12/06/2025 01:14, Sean Whitton wrote:
Hello,
On Sat 15 Mar 2025 at 06:11pm +11, Stuart Prescott wrote:
I would, however, reject that claim that the text is not ambiguous as
TAGOBJID is defined nowhere in policy, TAG2UPLOAD-DESIGN.txt, the dgit
documentation, dgit source code, git
name part and < required?)
The name part may be used for human display and possibly ordering.
It should not be involved in equality comparisons, lookups, etc.
While true of course... we also do that in lots of places in Debian to
squash together the multiple emails that an in
Hi Sean
On 16/06/2025 23:54, Sean Whitton wrote:
Cool. Would you be able to second it, please?
yes, seconded.
thanks
Stuart
--
Stuart Prescott http://www.nanonanonano.net/ stu...@nanonanonano.net
Debian Developer http://www.debian.org/ stu...@debian.org
GPG fingerprint 90E2
31 matches
Mail list logo
