Control: tags -1 = pending
Jonathan Nieder <jrnie...@gmail.com> writes:
> Russ Allbery wrote:
>> Allow libc to install files in /lib64
>> diff --git a/policy/ch-opersys.rst b/policy/ch-opersys.rst
>> index 7d9e20a..d7c4956 100644
>> --- a/policy/ch-opersys.r
Yeah, the problem I have is that I do want all the checks when uploading
to Debian. I suspect the right thing for me to do is make my own profile,
and then just remember to use that profile for local packages. It's a
little bit awkward, but it's not too bad.
--
Russ Allbery (r...@debian.org
s would definitely work. I wonder if it would make sense to
have a file in debian/source that indicates the profile in some way?
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
Package: lintian
Version: 2.5.66
Severity: normal
The new tag bugs-field-does-not-refer-to-debian-infrastructure added in
the most recent version of Lintian is a false positive for non-Debian
packages. I have a pile of personal packages that I maintain in a separate
archive, but prefer to use
Control: tags -1 = pending
Sean Whitton <spwhit...@spwhitton.name> writes:
> On Mon, Dec 25 2017, Russ Allbery wrote:
>>> not set, the commands "editor" and "pager" should be used,
>>> respectively. These commands can be invoked explicitly
Thanks, these all look good to me. Applied. And many thanks for the
clear, separated patches! That made review very easy.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
tml/index.html: href="index.html#document-index">Table Of Contents
> /usr/share/doc/debian-policy/policy.html/index.html: class="nav-item nav-item-0">Debian Policy
> Manual v4.1.0.0
This appears to be more breakage in Sphinx singlehtml output. E
Control: tags -1 pending
Ben Finney <bign...@debian.org> writes:
> The term “synopsis” is established in the definition of “Formatted
> Text”. This attached patch uses that term more consistently in the
> document.
Thanks, looks good to me. Applied.
--
Russ Allbery (
not set, the commands "editor" and "pager" should be used,
> respectively. These commands can be invoked explicitly (e.g.
> as /usr/bin/editor), or through a $PATH search (e.g. as
> editor).
> ?
This wording seems fine to me. Seconded.
the
> target is some wrong location in section 4.12.
Yeah, this is because sphinx -M singlehtml is broken with footnotes. :(
The multi-page version in the debian-policy package is correct.
Also see the discussion in #876075.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
ve been a failed
experiment, at least pending further work on Sphinx, and we should just
publish the multi-page version. What do other people think? (Adding
debian-www for their opinion as well.)
Not having working footnotes feels to me like kind of a showstopper.
--
Russ Allbery (r...@debi
l like avoiding Javascript here is excessively
conservative. I'd prefer one of the solutions that pulls the Javascript
from the current Debian unstable packages. Given the small use that
Sphinx makes of it, I find it unlikely that there will be any practical
security issues with this.
--
ice, services with a dependency
on this service will be started even though the service isn't running,
and init system status commands may incorrectly claim that the service
was started.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
Control: tags -1 patch
Russ Allbery <r...@debian.org> writes:
> As explained by Aurelian Jarno:
>>> 9.1.1
>>> Only the dynamic linker may install files to /lib64/.
>> How is that supposed to work for the multilib glibc? For example
>> libc6-amd64:i386
The relations ``<`` and ``>`` were previously allowed, but they were
> confusingly defined to mean earlier/later or equal rather than
Seconded the above change and with or without the wording change discussed
in the other part of this thread.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
urpose. I personally don't think the
DFSG is as strict there, and would be satisfied with any working and
practically equivalent version.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
Package: debian-policy
Version: 4.1.2.0
Severity: important
As explained by Aurelian Jarno:
>> 9.1.1
>> Only the dynamic linker may install files to /lib64/.
> How is that supposed to work for the multilib glibc? For example
> libc6-amd64:i386 installs all its libraries into /lib64. We
Control: tags -1 = pending
Holger Levsen <hol...@layer-acht.org> writes:
> On Wed, Aug 23, 2017 at 09:20:39PM -0700, Russ Allbery wrote:
>> --- a/policy/ch-controlfields.rst
>> +++ b/policy/ch-controlfields.rst
>> @@ -962,6 +962,10 @@ repository where the Debian
default base system /usr/bin/editor (*)
+ editor suitable /usr/bin/editor (*)
flexmem anything that can access flexible memory via the
OBEX Protocol
foomatic-data PPD printer description files
--
Russ Allbery (r...@
tribution unstable
dpkg-buildpackage: info: source changed by Russ Allbery <r...@debian.org>
dpkg-buildpackage: info: host architecture amd64
debian/rules clean
dh clean
dh_clean
gbp:error: You have uncommitted changes in your source tree:
gbp:error: On branch debian/master
Your branch is up to da
Chris Lamb <la...@debian.org> writes:
> Good catch. Fixed in Git:
>
> https://anonscm.debian.org/git/lintian/lintian.git/commit/?id=6110e0f1185e26d903dd0ed8a7a8edaae14cf905
I suspect you want package.docs in the long description of the tag instead
of package.install.
--
Package: lintian
Version: 2.5.65
Severity: wishlist
Apache 2.0 requires distributing any NOTICE file along with derivative
works, but this is easy to forget. In many cases, we have effectively
the same information in debian/copyright, but even if this is the case
for a specific release, it's not
rors that I got in the initial message that I
opened this bug with, when trying to build the package with gbp? Those
were odd -- attempts to touch files in non-existent subdirectories of
.git. I wasn't sure what to make of that.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
Ian Jackson <ijack...@chiark.greenend.org.uk> writes:
> Russ Allbery writes:
>> It really feels like something is broken with the interpretation of
>> patches-unapplied 3.0 (quilt) trees. (conf_convert is a script added
>> by one of the patches.)
> Can you please
Russ Allbery <r...@debian.org> writes:
> After building with dgit --quilt=gbp sbuild, dgit --quilt=gbp push also
> fails:
dgit --gbp quilt-fixup makes things get farther, but then I get:
$ dgit --quilt=gbp push --overwrite
canonical suite name for unstable is sid
down
Russ Allbery <r...@debian.org> writes:
> I must be doing something wrong, but I cannot get any of the documented
> workflow in dgit-maint-gbp to work with a package in 3.0 (quilt),
> patches-unapplied.
After building with dgit --quilt=gbp sbuild, dgit --quilt=gbp push also
fails:
Package: dgit
Version: 4.1
Severity: normal
I must be doing something wrong, but I cannot get any of the documented
workflow in dgit-maint-gbp to work with a package in 3.0 (quilt),
patches-unapplied.
Starting from the current rssh source (debcheckout should get you the
same thing I'm working
s significant time. I'm less opposed to this
one than to the MIT or BSD licenses that have substantial variation in
wording, but I still don't think it's a good idea.
common-licenses has the most benefit for very long licenses that people
then copy verbatim.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
Markus Koschany <a...@debian.org> writes:
> Am 12.12.2017 um 03:39 schrieb Russ Allbery:
>> The binaries built from the source code are a "substantial portion of
>> the Software." We have to include the license and copyright statement
>> with the bina
s don't
contain the source code and the original license notices.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
T-Expat
> license in Debian.
I understand this desire for longer licenses. This one is three
paragraphs long. I really don't get why it's such a problem to reproduce
that in debian/copyright.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
of this license between
different packages, and any version that doesn't exactly match the wording
that we include in common-licenses still legally needs to be reproduced in
the package's copyright file. And this is an error that's very hard to
find with Lintian.
--
Russ Allbery (r...@debian.
s is fallout from the
requirement that packages include a changelog for that specific version of
the package. It's in Policy, but it's semi-hidden in a footnote (and it
looks like the current www.debian.org publication of Policy has broken all
the footnote links because the multi-page Policy document isn't
saying we shouldn't change this to also support a cert chain in the
cert file, but that will probably get this working for you.)
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
ht reach different cost/benefit
tradeoffs.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
rts dist that
> didn't include 'a'. The package built against 'b'. Was this an
> autobuilder bug?
Yeah, that's a great question. How does this work for backports?
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
continue to do so, and I think it's extremely
valuable. I also read all debian/changelog files for all packages I
install on my system, and find that incredibly useful when maintainers put
real information in them.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
his is a *minor* bug and people shouldn't harass
maintainers about it, but we'd like to sort out this historic mess and
switch to consistent usage of these two files.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
ackages need to be fixed ?
https://lintian.debian.org/tags/wrong-path-for-interpreter.html says none.
The one hit there is for a module shipped with Perl that is doing
something weird with #! in a file that isn't an executable.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
n/changelog or debian/control. (See also #820523 for the reverse
> problem where the real name differs.)
> What would the lintian maintainers suggest?
For packages where you also do uploads from work, why not add your work
address to Uploaders? It's a little odd to list yourself twice with two
d
variable in all the
ways krb5-config is called now. But at least we do have a fighting chance
of picking up the correct compiler, and worst case we fall back to the
default compiler.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
rb5-config.mit
> * have that be a script that calls krb5-config.mit.tripple
> * Each package only includes krb5-config.mit.tripple for the appropriate
> architecture.
Yeah, I was trying to figure out how to make something like that work, and
I think that might be the best approach.
ted Autoconf
machinery to know the target architecture and then use the correct
pkgconfig files for that architecture, although I haven't played with it
enough to know exactly how (or if) that's wired together.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
Benjamin Kaduk <ka...@mit.edu> writes:
> On Mon, Nov 13, 2017 at 10:51:10AM -0800, Russ Allbery wrote:
>> I'm not sure how best to fix this other than no longer using
>> krb5-config and shipping a pkgconfig script or something. One could
>> move the krb5-config
oves the problem to a different area (how to find the right krb5-config
script to use).
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
uld rather not block incorporation of this new spec into
> Debian's official document set, on the task of reformatting it into
> docbook.
Policy is now reStructuredText, so hopefully the reformatting for any
future specs will be much, much easier.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
umber was, though.
I agree that the behavior you're describing seems broken.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
Thorsten Glaser <t...@mirbsd.de> writes:
> Mattia Rizzolo dixit:
>> On Sat, Nov 04, 2017 at 01:45:59PM -0700, Russ Allbery wrote:
>> executable (be it binary or script), copy it inside the chroot, and
>> execute it.
Where do you pass the name of the executable, th
Package: cowbuilder
Version: 0.85
Severity: normal
The cowbuilder man page claims to support an execute operation, but I
cannot figure out how to pass in the command and there's no example.
I tried all of:
$ cowbuilder execute apt update --basepath
/var/cache/pbuilder/base-experimental.cow
$
Sean Whitton <spwhit...@spwhitton.name> writes:
> On Wed, Oct 18 2017, Russ Allbery wrote:
>> It's probably worth noting here that while debian-mentors has
>> converged to a very strong consensus that unreleased versions of
>> packages should not appear in debian/cha
es, indeed, that's a very good point, and I'm not sure whether we've
adequately documented that wrinkle.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
free software
developer, but in general I prefer to see a higher bar for inclusion in
Policy than aesthetics. As long as variance of practice doesn't *break*
anything, I'd generally prefer to keep it out of Policy and in other, more
informative guides to best practice, such as the Developer's Referen
evelopment energy is with the current upstream.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
enssh-server, and in that case it makes logical sense that
they'll need to explicitly enable GSS-API.
I think it's fine to just remove the package. It long ago served its
purpose, and the few remaining people who may be using it as a shortcut
will hopefully be able to figure out the right th
same thing you did, and definitely want to fix
this sooner rather than later.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
t modules and the second skips one.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
uld be to use sssd, which is a more complex
system that does local caching of the Kerberos authentication credentials
and is designed specifically to handle this use case.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
Daniel Kahn Gillmor <d...@fifthhorseman.net> writes:
> On Sun 2017-09-17 16:26:25 -0700, Russ Allbery wrote:
>> I personally lean towards 2, which is consistent with what's in Policy
>> right now, but I can see definite merits in 3. I believe the
>> reproducible build
Package: debian-policy
Version: 4.1.0.0
Severity: normal
Currently, Debian Policy requires all environment variables be held the
same across builds for the build to be expected to be reproducible.
However, the current approach of some reproducible build tools is to
instead enumerate a set of
software.
There's a transition for people who are used to typing DIST=stable gbp
buildpackage instead of gbp buildpackage --git-dist=stable, but a note in
NEWS.Debian is probably sufficient.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
Control: severity -1 wishlist
Control: tags -1 pending
Matthew Gabeler-Lee <chee...@fastcat.org> writes:
> On Wed, 23 Aug 2017, Russ Allbery wrote:
>> And let me know if there's a way that I can make this information
>> easier to find in the man page.
> A possible wo
of
Javascript is just the search box. I don't really want to do a lot of
meddling with the Sphinx output (since part of the goal is to let Sphinx
take care of the details of output), but this doesn't look like a ton of
work and looks likely to continue to be supported.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
> make[2]: *** [policy.pdf] Error 127
> Since Sphinx 1.6, latexmk is required to build the LaTeX documentation [1].
> Adding a build-dependency on latexmk should help.
Thanks, fixed in Git. We'll need to make a new upload shortly.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
Package: python3-sphinx
Version: 1.6.3-2
Severity: normal
sphinx-build is not exiting with a non-zero status when building PDF
documentation fails. This makes it harder to find build errors.
mithrandir:~/dvl/debian/policy$ sphinx-build -M latexpdf policy policy/_build
Running Sphinx v1.6.3
s variant.
I would consider this a unique and separate license.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
te it properly. It's best ignored for the purposes of
finding a good general solution in Debian.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
.dsc
files either.) That means that it doesn't matter if tools that operate
only on the archive support it, since they won't see it; only package
building tools that operate on debian/control need to support it, and they
all seem to. (wrap-and-sort -t adds the trailing commas and is very
widely used, so i
e just adding an additional condition.
I'd be inclined to just whitelist this particular file as an oddity.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
on about procmail, though. Some developers have
very... odd code preferences.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
ption
anyway, but hopefully no one will think that it implies that https is
providing strong authentication of the Git server here. There's non-zero
authentication, but it's pretty weak.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
ld make to make people comfortable with this as an option.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
Jonathan Nieder <jrnie...@gmail.com> writes:
> Russ Allbery wrote:
>> (That said, my understanding is that you don't get any meaningful
>> integrity protection for Git from using https over http.)
> As discussed elsewhere in this thread, it depends on how much you
>
I guess it is.
Ideally I'd like myon to feel comfortable with this proposed outcome, and
the proposed wording hasn't gotten enough seconds yet.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
Sean Whitton <spwhit...@spwhitton.name> writes:
> On Sat, Aug 26 2017, Russ Allbery wrote:
>> Well, it doesn't, exactly... it says that it can be a web forum or
>> bugtracker, but doesn't say anything about being a URL. Hm.
>>
>> Something about this sits wron
Sean Whitton <spwhit...@spwhitton.name> writes:
> On Sat, Aug 26 2017, Russ Allbery wrote:
>> Seconded with or without the following nit.
>> Minor wording nit: I would put a period after "obtained" and make the
>> next part a separate sentence. ("T
y
> +set to this value.
> +
> +The Debian autobuilders set HOME to ``/nonexistent`` so that packages
> +which try to write to a home directory will fail to build.
> +
> .. _s-sysvinit:
>
> System run levels and ``init.d`` scripts
Seconded.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
ng that the copyright file can only omit the upstream source
information if the URL pointed to by Homepage includes name or contact
information, but (a) that's not the point of your change, and (b) we want
that contact information to always be in the copyright file if available
because upstr
gh it would be nice to be more
specific about when this is used and what its allowable values are. But
I'm also okay with leaving that for future work.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
he Policy language. People
just shouldn't assume this provides any meaningful integrity protection in
the semantic sense.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
ho came
up as providing editor (using grep-aptavail). I didn't include the list
in one of the bug messages but probably should have.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
Jonathan Nieder <jrnie...@gmail.com> writes:
> Russ Allbery wrote:
>> +++ b/policy/ch-customized-programs.rst
>> @@ -93,19 +93,21 @@ page.
> [...]
>> -It is not required for a package to depend on ``editor`` and ``pager``,
>> -nor is it required for a package
Sean Whitton <spwhit...@spwhitton.name> writes:
> On Wed, Aug 23 2017, Russ Allbery wrote:
>> --- a/policy/ch-controlfields.rst
>> +++ b/policy/ch-controlfields.rst
>> @@ -962,6 +962,10 @@ repository where the Debian source package is developed.
>>
>&g
Dropping Artem, whose email address no longer works.
Brendan O'Dea <b...@debian.org> writes:
> On Wed, Aug 23, 2017 at 11:03:23PM -0700, Russ Allbery wrote:
>> In previous discussions, no one seemed to feel that it was helpful as a
>> virtual package. Virtual pac
alternative, removed in November 1996 because
+ this was not useful for dependencies and was
+ never used except in Provides
Changelog
-
@@ -363,3 +365,6 @@ Russ Allbery:
virtual-mysql-server-core
vi
Russ Allbery <r...@debian.org> writes:
> Jakub Wilk <jw...@debian.org> writes:
>> The actualy lintian code is:
>> foreach my $expected_name (@sonames) {
>> $expected_name =~ s/([0-9])\.so\./$1-/;
>> $expected_name =~ s/\.so(?:\.|\z)//;
>>
Control: tags -1 patch
Scott Kitterman <deb...@kitterman.com> writes:
> On January 8, 2016 12:26:24 PM EST, Russ Allbery <r...@debian.org> wrote:
>> Scott Kitterman <deb...@kitterman.com> writes:
>>> As is currently being discussed on #debian-devel,
missing some aspect of your original bug
report?
Russ Allbery <r...@debian.org> writes:
> My personal feeling is that the current vagueness is a feature rather
> than a bug. I think a moderated mailing list is fine *if* the
> moderation queue is very promptly processe
be more familiar
with the pros and cons).
Anyway, that's the reason why I've always written my Kerberos-related PAM
modules such that all configuration that makes any sense to set globally
on the system can be set in krb5.conf. That avoids the problem by not
requiring anything modify the PAM configura
s the right one, and then we can put something much
simpler in Policy that assumes the dpkg-dev interface. That doesn't solve
the problem for packages older than that version of dpkg-dev, but we can
probably just note that.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
ke, and I still have absolutely no
idea what that does.
Is there any way that we could help people out and have the correct thing
to do be much, much simpler? Just a single command invocation?
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
; on the changelog. It looks at least a bit redundant.
Fixed. Thanks!
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
emely generic name, for something that is a
> global resource. I think it should be renamed to debian-policy.
Fixed in Git. Thanks!
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
ns a one-liner. It would be nicer if Contents
> would get expanded into the main Menu.
I managed to fix this as well by leaving out the section headings in the
top-level document.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
specific bug number against Policy by fixing the numbering
and nesting for the main chapters, since I think the appendix numbering is
liveable, but we'll definitely fix this if some solution materializes.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
d to be appendix B, now it's 2, but on the
> info file it's 14.
Yeah, both the info and PDF documentation have that issue, but HTML
doesn't. I haven't looked at epub, but it's probably just the HTML output
in another form.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
hink could be just left as a
final section of the document.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
h chaotic for a bit as we work
through finishing this reStructuredText conversion. Apologies for the
extra work! We think the long-term result will be worth it both in terms
of better output and in terms of a more maintainable Policy document.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
tory because single-file from Sphinx isn't strictly
single file (and we have images now), but I think it should all work. The
tricky part will be on the debian-www side in copying things over. I'll
give them a warning that more changes are coming.
--
Russ Allbery (r...@debian.org)
mbering. It's counting the top-level document as having three sections
and embedding the contents in section "2" and pushing everything down.
This is the same problem the info documentation is having.
I'll take a look and try to figure out some solution.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
hopefully I can fix 1 and that will resolve your issue.
--
Russ Allbery (r...@debian.org) <http://www.eyrie.org/~eagle/>
601 - 700 of 6053 matches
Mail list logo
