On Mon, Jun 19, 2017 at 12:03:09PM +0100, Sean Whitton wrote:
> Please find attached a patch to update the ctte appointments and Policy
> delegation information on <https://www.debian.org/intro/organization>.
Updated patch attached, including today's ctte appointment.
--
S
for every mode, sure.
> Emacs-ivy-doc is also pretty much ready to upload to non-free/docs; I
> just need to find out what I should build from the .texi--man page,
> and info page? Man page, info page and html doc? Something else?
Without looking at the source, Info and HTML sounds s
the user ignore it.
On Wed, Jun 21, 2017 at 03:47:30PM +0100, Ian Jackson wrote:
> How about
>
> | dgit: experts' info: src: ## orig ## gitignores: == orig ==
> | dgit: experts' info: HEAD ## o+d/p HEAD == o+d/p
I find "experts' info
ee is what you get in the simplest additive
operation between the 'o' and the 'd': putting the 'd' inside the
expanded 'o'.
(Ignoring the subtlety of 3.0 (quilt) permitting you to overwrite a
debian/ found in upstream's source, but that is rare.)
--
Sean Whitton
signature.asc
Description: PGP signature
ou agree? If so, we can file a bug against policy to produce
output without javascript, and block this bug by that one.
[1]
https://stackoverflow.com/questions/31951553/customizing-sphinx-to-avoid-generating-search-box
--
Sean Whitton
signature.asc
Description: PGP signature
is present in the source package. This
+field may also be used in source package control files if needed in
+other situations.
.. _s5.7:
--
Sean Whitton
signature.asc
Description: PGP signature
``<`` and ``>`` were previously allowed, but they were
confusingly defined to mean earlier/later or equal rather than
--
Sean Whitton
signature.asc
Description: PGP signature
s for the
upstream authors. This can be the name of an individual or an
organization, an email address, a web forum or bugtracker, or any other
means to unambiguously identify who to contact to participate in the
--
Sean Whitton
signature.asc
Description: PGP signature
will fail to build.
+
.. _s-sysvinit:
System run levels and ``init.d`` scripts
--
Sean Whitton
signature.asc
Description: PGP signature
in favour of the
Homepage: field. It was deliberate that my addition applies to both the
'must' and the 'should' requirements.
Do you disagree with this?
--
Sean Whitton
signature.asc
Description: PGP signature
case I had in mind was where the only information available was a
URI, with no maintainer name or e-mail address. In that case, Homepage:
would duplicate that information, and that's what we're trying to avoid
with this bug.
On reflection I realise that such a case is rather unlikely. But
set variables for the plain XIM
iris ~ % ps fax | grep ibus-daemon
1544 ?Ssl0:05 /usr/bin/ibus-daemon --daemonize --xim
5289 pts/1S+ 0:00 \_ grep ibus-daemon
--
Sean Whitton
signature.asc
Description: PGP signature
Hello Ansgar,
On Mon, Aug 28 2017, Ansgar Burchardt wrote:
> Sean Whitton writes:
>> +This field should not be used for purposes other than satisfying
>> +license requirements to provide full source code.
>
> The DFSG requires source code to be provided too...
Can you sugge
x27;t do
anything with secret keys, which would render git-remote-gcrypt pretty
much useless.
I am thinking I should change it to this:
Depends: gnupg | gnupg1
--
Sean Whitton
signature.asc
Description: PGP signature
uch library
> to pass input instead of using xim. If ibus related libraries aren't
> available, ibus use xim to pass keyboard input.
Okay.
I finally found a workaround:
pkill -u $USER ibus-daemon; IBUS_ENABLE_SYNC_MODE=0 ibus-daemon --xim
--daemonize
--
Sean Whitton
ecret keys", since I can
> generate and manipulate secret keys as usual.
Okay, thanks for the feedback. Will test.
--
Sean Whitton
signature.asc
Description: PGP signature
gt; is correct, although the wording could probably be improved to deal
> with arguments after -e that begin with a hyphen-minus.
>
> “xterm -e foo bar -T baz blah” will call “foo bar -T baz blah”, so
> the -e works like an implicit -- there.
--
Sean Whitton
signature.asc
Description: PGP signature
$options{'pgpsigurlmangle'} = [ 's/$/.' . $suffix .
> '/', ];
Shouldn't there be a '$' in the first one, too?
--
Sean Whitton
signature.asc
Description: PGP signature
o turn it into
> Pushed/Pushable only at the last minute:
>
> Ideally we do not want to generate a complete record of all the user's
> rebases in the permanent history. If we generate one pseudomerge for
> each rebase, that is what would happen.
>
> We could try to avoid that by looking to see "whether the previous
> branch had been pushed". But we don't know, of course, where it might
> have been pushed. It might even have been pushed using an ad-hoc rune
> to a remote ref without a local tracking branch. Conversely, it might
> have been deliberately pushed, in Stripped state, to a rebasing public
> branch.
Right. I was thinking it could be avoided but the ad-hoc pushes make
that impossible, as you say.
--
Sean Whitton
signature.asc
Description: PGP signature
eproducible issue: Can I mechanically check policy requirements?
> It is actually worse here: Given a Multi-Arch bug report, it is
> difficult to determine whether your draft supports it due to the lack of
> precision.
Right.
To my mind, the most important ways to achieve readability in this case
are
- avoid repetition
- avoid "probably", "likely" sentences.
When I cut down your draft I was trying to remove repetition. After
reading your e-mail, I now see that not all of it was actually
repetition. Could you make some commits against my branch adding the
information that was not repeated, please?
--
Sean Whitton
signature.asc
Description: PGP signature
On Fri, Sep 01 2017, Sean Whitton wrote:
> Shouldn't there be a '$' in the first one, too?
Er, I was too tired when I wrote this.
Patch LGTM, though of course needs testing. Thanks again.
--
Sean Whitton
signature.asc
Description: PGP signature
opportunity to review it yet.
--
Sean Whitton
signature.asc
Description: PGP signature
he Debian package would also build
from the .org files.
--
Sean Whitton
signature.asc
Description: PGP signature
l problem here
> which ought to be fixed.
Indeed.
There are some ideas relevant to this feature request in this thread:
<https://lists.debian.org/debian-devel/2017/05/msg00320.html>
(definitely not just this message, but it's a way into the thread).
Thank you for the write up, Ralf.
--
Sean Whitton
signature.asc
Description: PGP signature
much nicer,
git-deborig(1) from the devscripts package might make your life a bit
smoother.
--
Sean Whitton
signature.asc
Description: PGP signature
ation
> through a similar internal mechanism (IIRC), but in this case I have
> no choice but to try to fix it... and if reproducible builds are
> required for Buster and I fail at this then muse-el will be dropped.
I'm pretty sure it will not be a hard requirement, but thank you for
t
hadn't created d/source/format yet.
Thanks for the docs update.
--
Sean Whitton
signature.asc
Description: PGP signature
On Fri, Jun 16, 2017 at 01:07:04PM +0100, Sean Whitton wrote:
> Here's a patch, though I think we need to wait for #864881.
Here is an updated patch taking into account the gbp maintainer's
resolution of #864881.
--
Sean Whitton
From 67f873d2af6e58e6376e2a14607bbf1901fded00 Mon Se
er to have this in our git repo than on the wiki. An
appendix is also significantly easier for people to find.
--
Sean Whitton
signature.asc
Description: PGP signature
(prominent examples: firefox-esr, intel-microcode)
>
> Is this widespread enough to be worth describing? It's kind of hard to
> describe.
I for one had assumed that there was no difference between -deb9u1 and
~deb9u1, so I'd like to see it documented.
--
Sean Whitton
signature.asc
Description: PGP signature
consensus? There
is certainly not a consensus that it's terrible).
--
Sean Whitton
signature.asc
Description: PGP signature
rety, which would be ~debXuY as above.
Sorry, I meant s/-deb9u1/+deb9u1/.
--
Sean Whitton
signature.asc
Description: PGP signature
s bug get off-topic, I'll send you some other
comments about using native packages privately.
--
Sean Whitton
signature.asc
Description: PGP signature
bug or leave that to you for when you prepare the next
> release?
Please go ahead and apply it to the repo with a changelog entry.
--
Sean Whitton
signature.asc
Description: PGP signature
repacking the tarball. The Developer's Reference already contains a
discussion of repacking upstream tarballs, so perhaps this should go
there?
Or we could use a footnote to Policy. I attach a patch doing that.
--
Sean Whitton
From 56fab75d2c803ae9afd8d2186613713b297f9138 Mon Sep 17 00:00
at Policy has the authority to do that,
and I don't think it would be desirable.
A footnote with a link to the REJECT-FAQ sounds useful. Here's a patch.
> Maybe it belong to devref.
Perhaps that should be a separate bug, if we're going to use this one to
discuss ad
appendix.
>
> I'm kind of leaning towards the last, honestly.
I've taken a stab at this, in branch bug866192-spwhitton of
debian-policy.git repo. Reviews very welcome.
--
Sean Whitton
signature.asc
Description: PGP signature
control: tag -1 +pending
On Sun, Jul 02, 2017 at 02:02:20PM -0700, Russ Allbery wrote:
> Sean Whitton writes:
>
> > I've taken a stab at this, in branch bug866192-spwhitton of
> > debian-policy.git repo. Reviews very welcome.
>
> This looks good to me. Thanks!
python 2.7.13-2
ii python-librdf 1.0.17.1+dfsg-1.3+b1
ii unzip 6.0-21
ii zip3.0-11+b1
mozilla-devscripts recommends no packages.
mozilla-devscripts suggests no packages.
-- no debconf information
--
Sean Whitton
signature.asc
Description: PGP signature
Given that this is indeed not normative, nor even a change to the text
of Policy, I've applied my patch.
I've also marked the change as closing this bug, but if Bastian feels
that adding the footnote does not fully address the concerns he had when
filing this bug, he should feel quite wel
ce this is informative rather than normative, I've gone ahead and
applied the change. Thank you for your review.
--
Sean Whitton
signature.asc
Description: PGP signature
2.2-1.2+b1
Versions of packages lintian recommends:
ii libperlio-gzip-perl 0.19-1+b2
Versions of packages lintian suggests:
pn binutils-multiarch
ii dpkg-dev 1.18.24
ii libhtml-parser-perl3.72-3
ii libtext-template-perl 1.46-1
-- no debconf information
--
Sean Whi
emd/system)
Versions of packages hothasktags depends on:
ii libc6 2.24-11+deb9u1
ii libffi6 3.2.1-6
ii libgmp10 2:6.1.2+dfsg-1
hothasktags recommends no packages.
hothasktags suggests no packages.
-- no debconf information
--
Sean Whitton
signature.asc
Description: PGP signature
Package: wnpp
Severity: wishlist
Owner: Sean Whitton
* Package name: pytest-helpers-namespace
Version : 2016.7.10
Upstream Author : Pedro Algarvio
* URL : https://github.com/saltstack/pytest-helpers-namespace
* License : Apache-2.0
Programming Lang: Python
w this bug were packages obtained
from addons.mozilla.org, so I don't have another test case for you.
--
Sean Whitton
signature.asc
Description: PGP signature
init(8) and update-rc.d(8) and I couldn't get
them to generate a postinst that does what I want. It seems you're
expected to use all three of these:
dh_systemd_enable --no-enable
dh_systemd_start --no-start
dh_installinit --no-start
but then after a reboot, a sysvinit system will start the daemon,
AFAICT.
--
Sean Whitton
signature.asc
Description: PGP signature
control: block 601455 by 857452
On Mon, Sep 11 2017, Ian Jackson wrote:
> This should also be fixed with a new update-rc.d rune.
Thank you, Ian and Felipe, for your feedback.
I think the right thing is to wait on #857452.
--
Sean Whitton
signature.asc
Description: PGP signature
t's just a matter of someone having enough CPU time to build all
its deps, in order to build lens.
--
Sean Whitton
signature.asc
Description: PGP signature
n myself on what our best practice should
be. However, your diff quoted above seems sensible for a beginner's
guide, as we would expect people reading it to be going through the RFS
process.
--
Sean Whitton
signature.asc
Description: PGP signature
l: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages debian-policy depends on:
ii libjs-sphinxdoc 1.5.6-2
debian-policy recommends no packages.
Versions of packages debian-policy suggests:
pn doc-base
-- no debconf information
--
Sean Whitton
Package: wnpp
Severity: wishlist
Owner: Sean Whitton
* Package name: nov-el
Version : 0.2.0
Upstream Author : Vasilij Schneidermann
* URL : https://github.com/wasamasa/nov.el
* License : GPL-3+
Programming Lang: Emacs Lisp
Description : Emacs mode for
Package: wnpp
Severity: wishlist
Owner: Sean Whitton
* Package name: emacs-kv
Version : 0.0.19+git20140108.7211484
Upstream Author : Nic Ferrier
* URL : https://github.com/nicferrier/emacs-kv
* License : GPL-3+
Programming Lang: Emacs Lisp
Description
Package: wnpp
Severity: wishlist
Owner: Sean Whitton
* Package name: emacs-db
Version : 0.0.6+git20140421.b3a423f
Upstream Author : Nic Ferrier
* URL : https://github.com/nicferrier/emacs-db
* License : GPL-3+
Programming Lang: Emacs Lisp
Description
h there are plenty in Policy) into the body text.
I don't see what is wrong with this one. Perhaps you could expand.
--
Sean Whitton
signature.asc
Description: PGP signature
the code less
readable, so if you agree that we're using Built-Using correctly, I'd
like to continue to check that.
--
Sean Whitton
signature.asc
Description: PGP signature
ntainer scripts
> - drop the built-using header (perhaps adding a custome header, or just
> making sure the version info is available other places.
I'll prepare another patch for this bug once we've updated dh-elpa.
--
Sean Whitton
signature.asc
Description: PGP signature
recommends:
ii openssh-client [ssh-client] 1:7.4p1-10
Versions of packages dgit suggests:
ii sbuild 0.73.0-4
-- no debconf information
--
Sean Whitton
signature.asc
Description: PGP signature
control: tag -1 -moreinfo +patch
Hello Niels,
On Fri, Jul 07, 2017 at 12:02:56PM +0100, Sean Whitton wrote:
> I'll prepare another patch for this bug once we've updated dh-elpa.
dh-elpa no longer generates ${misc:Built-Using}, and I've pushed some
more commits to my branch
On Wed, Jul 12, 2017 at 02:24:35PM +0200, Axel Beckert wrote:
> ag.el:37:1:Error: Cannot open load file: No such file or directory, dash
I suspect that migrating the package to use dh-elpa will fix this.
--
Sean Whitton
signature.asc
Description: PGP signature
nitially.
> After cloning the repository the package can be built like this:
>
> $ cd farbfeld
> $ git deborig
> $ dgit build -tc
Thanks. Will review & hopefully upload soon.
--
Sean Whitton
signature.asc
Description: PGP signature
uared tabs,
tabs-not-on-top, the app menu, the add-on bar, small button view and
more.
.
Such elements were removed in Mozilla's Australis redesign of Firefox.
--
Sean Whitton
signature.asc
Description: PGP signature
allay some of the concerns that
Tobi raised: barely-established teams aren't likely to have a team
homepage/documentation/policy document.
[1] https://www.stackage.org/
--
Sean Whitton
signature.asc
Description: PGP signature
identify who to contact to participate in the development of
+the upstream source code.
Packages in the contrib or
--
Sean Whitton
signature.asc
Description: PGP signature
magick should be
moved to a hard dependency?
If you're able to address the issues I've raised in this message, please
remove the moreinfo tag in this bug, and don't forget to re-run `dch -r`
to refresh the changelog timestamp.
--
Sean Whitton
signature.asc
Description: PGP signature
package in ages. So I don't see how my proposal introduces any new
problems; it's an improvement because it removes a source of confusion.
--
Sean Whitton
signature.asc
Description: PGP signature
ther changes).
> * Control: limit build-depend on libaio-dev to linux-only.
Could you explain the need for this change, please? Perhaps directly in
the changelog.
Also, you need to run `dch -r` -- the changelog timestamp is behind
changes you've made.
--
Sean Whitton
signature.asc
Description: PGP signature
#x27;m not sure why users
wanting to apply patches to packages in their suite would want to use
it.
--
Sean Whitton
signature.asc
Description: PGP signature
dh_* tool that takes care of the requirement, we would
then need new footnotes to almost every section of Policy. That would
be a bad idea.
--
Sean Whitton
signature.asc
Description: PGP signature
On Sun, Jul 16, 2017 at 12:21:40PM +0500, Andrey Rahmatullin wrote:
> No, the policy doesn't talk about dh_* and other helpers (except in
> footnotes).
Right. In a sense, Policy is the reference against which such helpers
are developed.
--
Sean Whitton
signature.asc
Descr
I'm very open to your opinion about what else to do with this
> information.
Thanks. Let's see what invocation of sbuild we end up with. As you
know, I'm hoping to come up with a script for dgit-user(7), using git
subtrees.
--
Sean Whitton
signature.asc
Description: PGP signature
place.
How about adding a section to that guide listing links to packaging
guides for specific types of packages, such as fonts?
--
Sean Whitton
signature.asc
Description: PGP signature
rm non-maintainer uploads.
> Of course, out of context of this request someone might think "of
> course the maintainer would sign the .dsc file--who else would do
> that?"
Well, again, it could be someone other than the maintainer, perfomring
an NMU.
--
Sean Whitton
signature.asc
Description: PGP signature
On Mon, Jul 17, 2017 at 10:32:34AM +0100, Ian Jackson wrote:
> Sean Whitton writes ("Re: Bug#868526: dgit-user(7) should say how to use
> sbuild"):
> > Thanks. Let's see what invocation of sbuild we end up with.
>
> git pull chiark master
>
> and you&#
history into a nice patch series,
and use a bit of magic to ensure that this is still fast-forwarding".
They don't have to try to understand the state before the final
pseudomerge is back on top.
--
Sean Whitton
signature.asc
Description: PGP signature
ii libwww-perl 6.15-1
ii perl 5.24.1-3
Versions of packages dgit recommends:
ii openssh-client [ssh-client] 1:7.4p1-10
Versions of packages dgit suggests:
ii sbuild 0.73.0-4
-- no debconf information
--
Sean Whitton
signature.asc
Description: PGP signature
x86_64)
Kernel: Linux 4.9.0-3-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8),
LANGUAGE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
--
Sean Whitton
From 371ecebc228ac73e7deda0842ef6e4b36e9bd7b1 M
e removed
emacs24.
(I think those packages with Conflicts: fields are buggy, regardless, as
that is far too heavy-handed for packages that just don't work when you
try to use them with emacs24.)
--
Sean Whitton
signature.asc
Description: PGP signature
, which amounts to a bug blocking
the transition.
--
Sean Whitton
signature.asc
Description: PGP signature
Control: tags 826389 + patch
Control: tags 826389 + pending
Dear maintainer,
I've prepared an NMU for git-repair (versioned as 1.20151215-1.1) and
uploaded it to unstable.
Regards.
--
Sean Whitton
diff --git a/Common.hs b/Common.hs
index a6c5d5488..ab1de4e62 100644
--- a/Common.hs
Hello Branden,
On Thu, Jun 15, 2017 at 04:35:23PM +0100, Sean Whitton wrote:
> Please accept my apologies for letting this RFS sit for so long. Thank
> you for all your work. Looking forward to uploading it soon.
>
> Here's a full review of dc84e1861798b3aba0969e2fe81a2
Hello Damyan,
On Tue, Aug 01, 2017 at 08:58:38AM +, Damyan Ivanov wrote:
> When firefox hits unstable (probably towards the end of this year) this
> bug will become grave.
I think that it will only become grave once firefox-esr reaches a
version newer than 57.
--
Sean W
ktop file", but given that we have deprecated menu
files, it seems like the right way to reflect the change.
> The action to draft language for that has stalled in the policy
> process.
Is there a policy bug that got stalled? If not, maybe this bug should
just be reassigned to policy?
version 3 of the License, or
> +(at your option) any later version.
> License: GPL-3+
--
Sean Whitton
signature.asc
Description: PGP signature
al least un-favourite :-).
Do you still have some interest in this, Ian? Or anyone else?
We are hoping to migrate Policy to rST built by Sphinx. Maybe there is
a flowchart tool that integrates particularly well with Sphinx. CCing
Hideki in case he knows.
--
Sean Whitton
signature.asc
Des
On Tue, Aug 01, 2017 at 04:55:33PM +0100, Ian Jackson wrote:
> We should surely import the diagrams as-is.
Russ -- you were the one that suggested generating them. What do you
think about importing them as-is now?
--
Sean Whitton
signature.asc
Description: PGP signature
ince we're trying to reduce the
number of footnotes in Policy.
--
Sean Whitton
signature.asc
Description: PGP signature
control: tag -1 +pending
On Tue, Aug 01, 2017 at 11:18:56PM +0200, Bill Allombert wrote:
> Please always quote what you are seconding. This avoid confusion.
Thanks for the tip, Bill.
--
Sean Whitton
signature.asc
Description: PGP signature
tion).
>
> Alternative wordings welcome; I am not entirely certain the one above
> is all that well.
I think this wording is fine. Seconded.
--
Sean Whitton
signature.asc
Description: PGP signature
m) and why, for instance.
Agreed, but we probably don't need to list all those roles in policy.
--
Sean Whitton
signature.asc
Description: PGP signature
e change.
Could you prepare a patch for the versoin you like that applies cleanly
against the current git HEAD,[1] and seek seconds for it, please? If
policy is released before you can do that, we can just clone the bug or
similar.
[1] https://anonscm.debian.org/git/dbnpolicy/policy.g
Package: ftp.debian.org
Severity: normal
Last maintainer upload was 2007.
Thanks.
--
Sean Whitton
signature.asc
Description: PGP signature
control: severity -1 serious
Hello,
Someone at DebCamp pointed out that this bug is actually a security
issue: this is a network library, and should definitely not be a
convenience copy of the code, and indeed, not a ten-year-old version.
--
Sean Whitton
signature.asc
Description: PGP
Dear Marga,
On the wiki[1] you say that your maintainer script diagrams are "GPL".
Does this mean GPL-2+, GPL_3+, or something else?
I'm planning to include this diagrams in the Debian Policy manual
directly.
Thanks.
[1] https://wiki.debian.org/MaintainerScripts
-
at the previous wording was almost self-contradictory:
it says the system is probably unusable, but can be /used/ to install
further packages.
--
Sean Whitton
signature.asc
Description: PGP signature
-b used per the previous
+ paragraph, must not do anything that might require root
+ privilege.
The build target may need to run the
--
Sean Whitton
signature.asc
Description: PGP signature
e causing us to file bugs to upstream saying "could you rename this
file that our Debian build process doesn't even use, please?" (e.g.)
Would it be possible to permit Files: to be a line-based list? Then
there could be one glob per line, and I think they could contain spaces.
T
and build-b targets are not invoked by the build target, instead
directly invoked by the binary target, then (i) does not apply, and
indeed (ii) applies and they will be invoked as root.
Is that why you want to delete that paragraph?
--
Sean Whitton
signature.asc
Description: PGP signature
build 0.73.0-4
-- no debconf information
--
Sean Whitton
signature.asc
Description: PGP signature
Uploaders field must be present and must
- contain at least one human with their personal email address.
-
-
The Uploaders field in debian/control can
be folded.
--
Sean Whitton
signature.asc
Description: PGP signature
stallinit,
+dh_systemd_start, etc.
+
--
Sean Whitton
diff --git a/policy.sgml b/policy.sgml
index 9cd182b..2b37df8 100644
--- a/policy.sgml
+++ b/policy.sgml
@@ -7053,12 +7053,6 @@ Built-Using: grub2 (= 1.99-9), loadlin (= 1.6e-1)
in /run sho
501 - 600 of 2972 matches
Mail list logo
