Hi,
Thanks for moving my 6 year old patch snippets/idea into real action.
On Sun, Jan 15, 2017 at 04:54:32PM +0100, Guillem Jover wrote:
...
>
> On Sat, 2017-01-14 at 21:30:14 +, Simon McVittie wrote:
> > On Sat, 14 Jan 2017 at 11:32:09 -0800, Russ Allbery wrote:
> > > Bill Allombert writes
Hi,
On Mon, Jul 31, 2017 at 10:38:33PM -0700, Paul Hardy wrote:
> I am adding the maintainer of the New Maintainer's Guide and the Guide
> for Debian Maintainers, Osamu Aoki, to this discussion. I would like
> to reassign this wishlist bug to one of those packages if Osamu
> ag
Hi,
On Mon, Aug 07, 2017 at 08:26:41PM -0700, Paul Hardy wrote:
...
> Making changes to debian-policy (if deemed appropriate) to allow upstream
> binary signature files would affect at least lintian, dpkg-dev, uscan, and
> Debian maintainer guides.
You should mean one of:
Debian Developer's Refe
Hi,
On Tue, Aug 08, 2017 at 10:48:08AM +0200, Guillem Jover wrote:
...
> On Mon, 2017-08-07 at 20:26:41 -0700, Paul Hardy wrote:
> > Also, where signature files are desired, I think it would be beneficial to
> > also accept binary ".sig" files as an alternative to ".asc" files, for
> > example as
Source: python3-defaults
Version: 3.5.3-3
Severity: important
As reported in https://bugs.debian.org/870820 and getting very positive
feedback at DEBCONF17 after migrating Debian Policy to DocBookXML,
debiandoc-sgml will be removed from the archive at buster+{0,1}. I am sending
reminder to package
Hi,
On Mon, Aug 14, 2017 at 10:13:10AM -0700, Russ Allbery wrote:
> Henrique de Moraes Holschuh writes:
>
> > We do when the binary sig is small enough to be stored along with the
> > inode, instead of requiring an entire filesystem block (4KiB), and the
> > armored signature is not small enough
Hi,
On Fri, Aug 18, 2017 at 12:08:02PM +0200, Guillem Jover wrote:
> Hi!
>
> On Wed, 2017-08-16 at 00:22:43 -0700, Paul Hardy wrote:
> > On Tue, Aug 8, 2017 at 1:48 AM, Guillem Jover wrote:
> > > On Mon, 2017-08-07 at 20:26:41 -0700, Paul Hardy wrote:
> > > > Also, where signature files are desi
Hi,
I was trying to update uscan and realized few problems which are not
addressed by the discussion here. There are many things to consider.
On Fri, Aug 18, 2017 at 02:43:58PM +0200, Mattia Rizzolo wrote:
> On Fri, Aug 18, 2017 at 07:48:24AM -0400, Daniel Kahn Gillmor wrote:
> > I confess that
Hi,
On Fri, Aug 18, 2017 at 12:02:27PM +0200, Guillem Jover wrote:
..
> Adding support for more signature formats or filename variations is
> not hard, but it increases the amount of those extensions and perhaps
> the additional sanity checks we have to support and perform on them on
> multiple t
Hi,
After all the discussion, Policy 4.1.0 goes as:
| 4.11. Optional upstream source location: debian/watch¶
|
| This is an optional, recommended configuration file for the uscan
| utility which defines how to automatically scan ftp or http sites for
| newly available updates of the package. Thi
Hi,
On Wed, Aug 23, 2017 at 09:27:25AM -0700, Russ Allbery wrote:
> Osamu Aoki writes:
> > The updated uscan will support debian/upstream/signing-key.asc only and
> > internally convert it /signing-key.gpg. I will make uscan to
> > convert other formats to this policy c
Oops.
On Sun, Aug 27, 2017 at 12:55:26AM +0900, Osamu Aoki wrote:
> Hi,
>
> On Wed, Aug 23, 2017 at 09:27:25AM -0700, Russ Allbery wrote:
> > Osamu Aoki writes:
> > > The updated uscan will support debian/upstream/signing-key.asc only and
> > > internally con
Hi,
On Sun, Aug 27, 2017 at 08:51:49PM -0300, Henrique de Moraes Holschuh wrote:
> On Wed, 23 Aug 2017, Russ Allbery wrote:
> > Note that this Policy language is carefully written to make it perfectly
> > fine for uscan to support all the things it currently supports, since it
> > only talks about
On Sun, Jul 22, 2018 at 05:19:14PM +0800, Sean Whitton wrote:
> control: tag -1 +patch
>
> Hello,
>
> Here is a patch, for which I am seeking seconds, that tries to capture
> the points raised by Osamu, Guillem and Paul without getting into
> legalese -- Bill has a point. In particular, I think
Package: src:debian-policy
Version: 4.2.0.1
Severity: normal
Tags: patch
README.md of debian-policy at salsa doesn't show indexed list as
expected.
Also, it doesn't provide information on how it get published to
www.debiasn.org site to track down issues.
This github style MD s a bit tricky but m
Hi,
On Mon, Apr 08, 2019 at 02:45:29PM -0700, Sean Whitton wrote:
> Hello,
>
> I am considering to working to convert dev-ref to rST+Sphinx this
> summer. I would like to start a discussion about doing that. The
> main things that I need to learn from this discussion are:
>
> - who else is int
On Tue, Jun 11, 2019 at 05:29:16PM +, Holger Levsen wrote:
> On Tue, Jun 11, 2019 at 10:15:56AM -0700, Sean Whitton wrote:
> > I don't know of any automated solution. We might just have to keep the
> > old source and continue building translations from that until each
> > language is manually
Hi,
On Wed, Jun 12, 2019 at 10:08:40PM +0900, Osamu Aoki wrote:
...
> This is one way reST to POT and POT to PO merge and translated reST
> generation tool (Unlike po4a, we can't make po from matching translation
> reST source.)
>http://www.sphinx-doc.org/en/stable/int
Hi,
I pushed the "rest" branch.
> NOW
>
> to SED script
>
> s/@@@codename-oldoldstable@@@/wheezy/g
By the way, is there better approach? I am new to reST build.
I am holding off here.
Now "make" will get you a set of localized reST files. Please inspect
this result.
I don't know how good
Hi,
I tried further with experimental rest branch.
I think I need to redo the whole thing again to get cleaner result but
this is good learning.
Now I have narrowed down issues as follows:
1. need to replace @@@...@@@ by |...| and figure out to use substitute
or embed all entity referenc
Hi,
"rest1" started.
> 1. need to replace @@@...@@@ by |...|
done
> and figure out to use substitute
TODO
> 2. pandoc without "--reference-links" seems better
> As far as HTML result, works fine except missing toctree
> This should be addressed manually
toctree added manually: done
Hi,
"rest2" started.
> > 3. inter-chapter reference to section title lacks section title text
> > auto-filling
> > For example `??? <#key-maint>`__
This was easy. :ref:`...`
I just have to automate it to address all incidents.
I still need to figure out to use substitute
Also, I need
Package: src:developers-reference
Version: 3.4.24
Severity: normal
While doing sphinx conversion, I realized that it may be better to
update as follows:
$ git diff
diff --git a/common.ent b/common.ent
index 83eddf3..900ce90 100644
--- a/common.ent
+++ b/common.ent
@@ -1,4 +1,4 @@
-
+
Hi,
"rest3" started and removed old ones.
> > > 3. inter-chapter reference to section title lacks section title text
> > > auto-filling
> > > For example `??? <#key-maint>`__
>
> This was easy. :ref:`...`
> I just have to automate it to address all incidents.
There were another type o
Hi,
On Sat, Jun 15, 2019 at 03:53:07PM +, Holger Levsen wrote:
> On Sat, Jun 15, 2019 at 09:04:24PM +0900, Osamu Aoki wrote:
> > While doing sphinx conversion, I realized that it may be better to
> > update as follows:
...
If you see my initial diff on the first lin
Hi,
I realize I can do better ...
Redoing the whole thing again...
Osamu
Hi,
I found one Italian translation error. (bogus duplicate copy of msgstr)
On Sun, Jun 16, 2019 at 10:03:35PM +0900, Osamu Aoki wrote:
> Hi,
>
> I realize I can do better ...
Instead of sed, I am replacing text with a short python script to deal
with markup across lines.
Pl
Hi,
On Tue, Jun 18, 2019 at 12:15:52AM +0900, Osamu Aoki wrote:
> Hi,
>
> I found one Italian translation error. (bogus duplicate copy of msgstr)
>
> On Sun, Jun 16, 2019 at 10:03:35PM +0900, Osamu Aoki wrote:
> > Hi,
> >
> > I realize I can do better ...
&g
Hi,
On Mon, Jun 24, 2019 at 02:04:43AM +0900, Osamu Aoki wrote:
> Hi,
>
> On Tue, Jun 18, 2019 at 12:15:52AM +0900, Osamu Aoki wrote:
> > Hi,
> >
> > I found one Italian translation error. (bogus duplicate copy of msgstr)
> >
> > On Sun, Jun 16, 201
Package: src:developers-reference
Version: 3.4.25
Severity: wishlist
Tags: patch
Patch is provided as rest8 branch.
https://salsa.debian.org/debian/developers-reference/tree/rest8
├── debian
│ ├── changelog
│ ├── control
│ ├── copyright
│ ├── developers-reference-de.doc-base
│ ├── de
Hi,
On Mon, Jul 22, 2019 at 01:45:50AM +, Holger Levsen wrote:
...
> > Maybe, now I think Sphinx expert can take over to get proper packaging.
>
> yeah, indeed! ;)
Do you know anyone good in this. Is there any volunteer? (I am
seeking help on the mailinglist at sphinx-us...@googlegroups.c
Hi,
On Mon, Jul 22, 2019 at 09:22:07PM +, Holger Levsen wrote:
> I wonder how this was done for debian-policy which is also hosted on
> www.debian.org. Sean, do you have any insight on this?
Alas, I thought I checked. Somehow I thought policy doesn't have
translation. Wrong!!! (I already h
Hi,
On Wed, Jul 24, 2019 at 08:40:19PM +, Holger Levsen wrote:
> hi,
>
> dear debian-www people: src:developers-reference was just switched to
> use sphinx, just like src:debian-policy. However, no upload to unstable
> has been made yet...
>
> On Tue, Jul 23, 2019 at 08:13:50AM -0700, Sean W
Hi,
On Fri, Jul 26, 2019 at 09:47:57PM +0100, Sean Whitton wrote:
> Hello,
>
> On Fri 26 Jul 2019 at 08:19PM +00, Holger Levsen wrote:
>
> >> I mean that the English files are available on
> >> www.debian.org but translations don't show up as described in
> >> https://www.debian.org/intro/cn Thi
HI,
On Sun, Jul 28, 2019 at 06:39:07PM +0100, Sean Whitton wrote:
> Hello,
>
> On Sat 27 Jul 2019 at 06:31pm +09, Osamu Aoki wrote:
>
> > Yes. Eventually ;-)
> >
> > I also see the translation of Policy is building only HTML.
>
> We can add others upon requ
Hi,
With today's commit, pull-down language selection seems to work for
package installed files. Also now we have Gnome desktop icon ;-)
It is usable, I think.
> > If I figure how to set up option2 type i18n web page, I may even do it
> > for debian-handbook.
>
> yeah, I also strongly prefer o
Hi,
On Sat, Aug 10, 2019 at 04:35:26PM +, Holger Levsen wrote:
I saw you uploaded a new version. Thanks.
As I see this package, remaining tasks are:
Priority Issues
* A Fix reproducible builds: date calculation with (TZ?) (shell)
* B Fix reproducible builds: different_due_to_umas
Hi,
On Sun, Aug 11, 2019 at 03:25:59PM +, Holger Levsen wrote:
> On Sun, Aug 11, 2019 at 11:51:32PM +0900, Osamu Aoki wrote:
> > I saw you uploaded a new version. Thanks.
>
> most changes were from you, so thank you very much too!
>
> > As I see this package, remain
Source: developers-reference
Version: 11.0.1
Severity: minor
## ISSUE ##
Sphinx conversion dropped content oof 3.4.25 po4a/add_fr/scope.add
PO4A-HEADER:mode=after;position=De plus ce document;endboundary=
Avertissement
Bien que ce document soit en français, l'activité de responsable Debian
i
Source: developers-reference
Version: 3.4.26, 11.0.1
Severity: minor
## ISSUE ##
Following contents are missing:
Developer's Reference Team
Andreas Barth
Adam Di Carlo
Raphaël Hertzog
Lucas Nussbaum
Christian Schwarz
Ian Jackson
ver. 3.4.25
Copyright © 2004, 2005, 2006, 2007 Andreas Barth
Cop
Source: developers-reference
Version: 3.4.26, 11.0.1
Severity: minor
Index for appendix used to be A.1, A.1.1, ... but now A is missing.
(This may be more issue with singlehtml )
This needs to be addressed some day.
Also, debian/tocsubstvars needs to be updated to match this.
I also think it is
Source: developers-reference
Version: 3.4.26, 11.0.1
Severity: wishlist
Please mention email gate
https://lists.debian.org/debian-devel/1999/12/msg00627.html
by From: Jason Gunthorpe
On Fri, 10 Dec 1999, Juan Cespedes wrote:
> I connect directly to db.debian.org, and I _think_ I get that mes
Source: developers-reference
Version: 3.4.26, 11.0.1
Severity: wishlist
IRC on describing new incoming system:
Robot101: do you have a URL describing new incoming system?
https://lists.debian.org/debian-devel-announce/2002/debian-devel-announce-200202/msg6.html
Hi,
Below are details of
Source: developers-reference
Version: 11.0.1
Severity: minor
For info page building, text before toctree is included in the opening
info page but after is silently dropped.
Also it doesn't care appendix.
I am trying to include copyright text into the first opening page.
-- System Information:
Hi,
Actually, text after .toctree are included at the end of entire info
page.
For now, not using text after .toctree is a reasonable work around.
But the best solution is to write extension to emmit such text after
.toctree immediately after @menu section in *.texi file.
So let's make this b
Hi,
For recommends, since TC is voted for "We advise the policy maintainers to
consider
how to clarify ...", here is a reference information for drafting such
clarification
clause.
Whereas the original concern of this bug was the use of recommends by
metapackage,
the underlining issue is broa
Yes, info version is included and it contains appendix, too.
So closing this bug is right action.
Thanks for your effort.
On Thu, 2023-02-09 at 16:28 +, Holger Levsen wrote:
> hi,
>
> actually I found the info version now, but it seems complete to me:
>
> $ sudo apt install info
> $ info
retitle 175064 Debian policy documents should use DocBook XML in UTF-8
thanks
Even with the current SGML source, UTF-8 transition is possible. But we
are in deep freeze and I am reluctant to push even a simple makefile
change and iconv conversion. The recent debiandoc-sgml package support
UTF-8
tags 175064 patch
thanks
Hi,
Current build use LANG=C which should work since LaTeX is forced to use
C locale.
I think older debiandoc2* used to use character conversion to high
bit latin-1 character for © using latin-1 if locale is not
specified as -l option.
Under non latin-1, it shows up i
severity 616043 wishlist
tags 616043 wontfix
severity 613946 wishlist
thanks
Hi,
Before I start, let me remind people that it is more important to
convert all these SGML documents to DocBook XML. So far, I am having
good success for maint-guide. I will work on this document once I get
comfortab
Package: debian-policy
Version: 3.9.1.0
Severity: normal
Hi,
Here is docbook XML converted file as attached.
If I get git write access, I can start converting the whole package as I
just did for maint-guide in git branch :-)
Try
$ make version
$ dblatex menu-policy.dbk
You get nice PDF. For
Hi,
Here is DocBook converted one from mime-policy.sgml.
I wonder why this is searate document from policy. (Too small)
Osamu
http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
%versiondata;
]>
The Debian MIME support sub-policy
J.H.M. Dassen (Ray)
jdas...@debian.org
Hi,
policy.sgml was successfully converted but I am not sending it over mail
yet. It may be too big. It can build nice PDF here.
Osamu
> --
> 613946: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=613946
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
--
To UNS
Hi,
Here is for Perl Policy.
Osamu
http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd"; [
%versiondata;
]>
Debian Perl Policy
Raphaël Hertzog
Brendan O'Dea
The Debian Policy mailing list
debian-policy@lists.debian.org
version &version;
&date;
This document des
Hi,
By extracting attached file into source and running "make", it will do
the magic of converting to DocBok XML and then to PDF etc.
(Need the sid version of the latest debiandoc-sgml)
Technically, conversion is ready whenever you want to do so.
Osamu
docbook-conversion.tar.gz
Description: Bi
Hi,
On Mon, Apr 25, 2011 at 05:25:31AM -0500, Jonathan Nieder wrote:
> Hi Osamu,
>
> Osamu Aoki wrote:
>
> > By extracting attached file into source and running "make", it will do
> > the magic of converting to DocBok XML and then to PDF etc.
> > (Need
Hi,
On Sat, Apr 30, 2011 at 03:51:15PM -0700, Russ Allbery wrote:
> Ben Hutchings writes:
>
> > +
> > + The upstream version number must not include a non-linear
> > + revision ID or hash, since it cannot help in ordering
> > + versions and it tends to result in very long
Hi,
Thanks for your help.
On Mon, Apr 25, 2011 at 05:25:31AM -0500, Jonathan Nieder wrote:
...
> . Sometimes the spacing around closing tags looks unidiomatic, as in
>
> ... The detailed
> procedure for gracefully orphaning a package can be found in the Debian
> Developer's Re
Hi,
On Mon, May 02, 2011 at 06:20:14PM -0300, Henrique de Moraes Holschuh wrote:
> On Sun, 01 May 2011, Bill Allombert wrote:
> > On Sat, Apr 30, 2011 at 09:00:14PM -0700, Russ Allbery wrote:
> > > So the reason for imposing a length restriction on version numbers in
> > > particular is due to the
Package: developers-reference
Version: 3.4.4
Severity: minor
If I copy script example under "6.5. CONFIGURATION MANAGEMENT . . ."
from PDF:
| 4. Modify all PO files by using sed. The use of that command is recommended
over any text editor
|to guarantee that the files encoding will not be bro
Hi,
Hmmm... David, you beat me on making this happen :-)
Merci Beaucoup!
On Tue, Jan 10, 2012 at 08:26:13AM +0100, Raphael Hertzog wrote:
> Hi,
>
> On Mon, 09 Jan 2012, David Prévot wrote:
> > As you may have noticed, the English document looks different: I quickly
> > copied and pasted part of
Hi,
On Wed, Jan 11, 2012 at 12:25:23AM -0400, David Prévot wrote:
> tags 629530 pending
> thanks.
>
> Hi,
>
> Le 09/01/2012 12:49, David Prévot a écrit :
> >> Le 07/06/2011 08:56, Osamu Aoki a écrit :
>
> >>> If you move this build this with XeTeX
Hi,
On Sat, Jan 14, 2012 at 09:41:10AM +0900, Hideki Yamane wrote:
> Hi,
>
> On Thu, 12 Jan 2012 00:42:12 +0900
> Osamu Aoki wrote:
> > > > Japanese PDF:
> > > >
> > > > http://people.debian.org/~taffit/developers-reference-xetex/develop
On Fri, Apr 13, 2012 at 07:12:26PM +0200, Hilmar Preuße wrote:
> On 11.04.12 David Prévot (da...@tilapin.org) wrote:
> > Le 03/04/2012 09:29, Osamu Aoki a écrit :
>
> Hi,
>
> > > This […] still fails to build. If I can
> > > not fix this soonish, I will build
Hi,
I just fixed this bug in subversion for developers-reference while
uploading new fixed version to archive for maint-guide.
I also tagged this as pending.
Who will be uploading this package.
There are so many open bug reports. There are 2 BTS reports with patch
but their validity has some
Package: debian-policy
Severity: wishlist
I have installed ikiwiki and configured it sometime ago. I removed its
package recently but did not purge it I got noisy cron error
messages. If the cron script was written in the way most other packages
checking the existence of the executable, this
Package: developers-reference
Version: 3.4.11
Severity: normal
Tags: patch
Almost no one use CVS now.
Let's switch description to GIT.
Also, popcon for
pbuilder 3500
cowbuilder2000
pbuilder-uml90
(I think upstream is focusing on cowbuilder used as backend of pbuilder.
So let
Hi,
I wonder if the problem is format or content provider.
On Thu, Jun 19, 2014 at 09:05:17AM +0200, Raphael Hertzog wrote:
> (adding debian-doc to the cc)
> Hi,
> On Thu, 19 Jun 2014, Paul Wise wrote:
> > Some of you may be aware there has been a discussion about devref on
> > debian-private and
Hi,
I knew someone already complained this :-) CCed.
When I wanted to add several web pages from packages to work nicely on
the www.debian.org with the content negotiation, I thought this kind of
things have working precedence with a proper script. Looking at the
developers-reference case which
Package: debian-policy
Severity: normal
Bug #770016 "Clarify network access for building packages in main"
was about not downloading files via network. This created new lines in
4.9 as:
| For packages in the main archive, no required targets may attempt
| network access.
This is too restrictive
On Wed, Feb 03, 2016 at 12:22:14AM +0100, Guillem Jover wrote:
> Hi!
> This is probably too restrictive too. It would not allow local access
> through TAP device or other similar things. It might be better to just
> say something like:
>
> | For packages in the main archive, no required targets m
On Sun, Mar 30, 2008 at 12:07:38PM -0700, Russ Allbery wrote:
> "Adam D. Barratt" <[EMAIL PROTECTED]> writes:
> > On Sun, 2008-03-30 at 11:30 -0700, Russ Allbery wrote:
> >> Meike Reichle <[EMAIL PROTECTED]> writes:
>
> >>> When doing my NM I noticed an inconsistency between the Debian Policy
> >
reassign 473439 debian-policy
thanks
Hi,
http://bugs.debian.org/473439
After reading the original bug report, tis is not Debian Reference but
Debian Policy. So I am reassigning this.
As for Debian Reference, English version os about to be replaced with
http://people.debian.org/~osamu/pub/ge
aning that if someone feels strongly about
> this proposal and wants to step forward to champion it again, I'd be
> willing to reopen the bug.
>
> --
> Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/>
>
> From: Osamu Aoki <[EMAIL PROTEC
reassign 486754 developers-reference
tags 486754 moreinfo
severity 486754 wishlist
thanks
Hi,
This is for http://bugs.debian.org/486754
Manoj was right to say "I do not see why this should be policy, as
opposed to a best practice's thing in the dev ref. (typo fixed as s/4/'/)
He meant "Develope
Hi,
On Tue, May 05, 2009 at 11:52:29AM +0100, Roger Leigh wrote:
> On Tue, May 05, 2009 at 10:36:51AM +0200, Michael Biebl wrote:
> > martin f krafft wrote:
> > > [moving debian-rele...@l.d.o to Bcc, continuing discussion in bug log]
...
> I think it is a problem extending to all virtual packages,
Hi,
On Mon, Sep 21, 2009 at 09:56:37AM +0200, Lucas Nussbaum wrote:
> Following a discussion on debian-de...@l.d.o[1], the way the Developers
> Reference[2] is maintained has been changed, with the aim to make it
> more public and easier for people to contribute.
...
> Finally, we could use the he
Hi,
> On 17/02/2010 19:15, Mike Hommey wrote:
> > On the other hand, one application will want 16x10 icons, another one
> > 24x15, another one may have some effects applied on the flags to better
> > fit the UI design, etc.
> >
> > So while applications amy be using flags already, are they really
Package: debian-policy
Version: 3.8.4.0
Severity: normal
The list of all sections is defined in policy:
http://www.debian.org/doc/debian-policy/ch-archive.html#s-subsections
As for descriptions of each of those, you could use:
http://packages.debian.org/unstable/
But there are 2 additional
Hi,
On Wed, Apr 14, 2010 at 08:38:38AM +0200, Joerg Jaspert wrote:
>
> > The list of all sections is defined in policy:
>
> > http://www.debian.org/doc/debian-policy/ch-archive.html#s-subsections
>
> > As for descriptions of each of those, you could use:
> > http://packages.debian.org/unsta
--
To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100617160314.ga28...@debian.org
--
To UNSUBSCRIBE, email to debian-policy-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100617160318.ga28...@debian.org
ing tools
ii debian-policy 3.5.6.1Debian Policy Manual and related documents
--
+++++++
+ Osamu Aoki <[EMAIL PROTECTED]> @ Cupertino, CA USA +
pgphgSXqqXnwU.pgp
Description: PGP signature
als/somemanual.ps.gz
ftp://ftp.debian.org/debian/doc/manuals/somemanual.sgml.tar.gz
I wonder how can this be so inconsistent with the reality. If we make
updated ddp manual policy, it should be in more obvious location.
--
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +
Do not close the bug report until a proper
> + manpage is available.
I guess missing manual will be handled by a patch to the man program but
above still applies.
--
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +
Osamu Aoki <[EMAIL PROTECTED]&g
/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +
Osamu Aoki <[EMAIL PROTECTED]> Cupertino CA USA, GPG-key: A8061F32
.''`. Debian Reference: post-installation user's guide for non-developers
: :' : http://qref.sf.net and http://people.debian.org/~osamu
`. `' "Our Priorities are Our Users and Free Software" --- Social Contract
Isn't it against the spirit of "binary distribution"?
deb-file should contain
Plain text (singe file for grep)
Multi-file HTML
PS
PDF
while source shall contain SGML/XML only with proper build depends
provided.
Osamu
--
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^
I do not like the duplication of the content.
Osamu
--
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +
Osamu Aoki <[EMAIL PROTECTED]> Cupertino CA USA, GPG-key: A8061F32
.''`. Debian Reference: post-installation user's guide for non-deve
ened when Adam was quiet on debian-doc.
Because of the nature of documetation, ddp-policy will likely be more of
the "Best Practice" guide with many "should"s, I think.
--
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +
Osamu Aoki <[EMAIL PRO
ion script (by Phillipe):
http://cvs.debian.org/ddp/utils/debiandoc-to-docbook/?cvsroot=debian-doc
Just my thoughts.
Osamu
--
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +
Osamu Aoki <[EMAIL PROTECTED]> Cupertino CA USA, GPG-key: A8061F32
.'
On Tue, Jan 07, 2003 at 11:42:30PM +0100, Josip Rodin wrote:
> On Tue, Jan 07, 2003 at 10:49:03AM -0800, Osamu Aoki wrote:
> > I think it may be best if this encoding changes are done at the same
> > time when this documentation is moved to docbook-xml format.
>
> I'm e
my mailer) txt.gz
debian-policy_3.1.1.1.deb (C)
debian-policy_3.5.6.1_all.deb ©
debian-policy_3.5.8.0_all.deb ©15 Nov 2002
Osamu
--
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +++++
Osamu Aoki <[EMAIL PROTECTED]> Cupertino CA USA, GPG-k
Package: debian-policy
Version: 3.5.8.0
Severity: normal
Tags: patch
In virtual-package-names-list.txt, some package names had colon (2),
comma (1) or period (1) after them. Also update date to 2003 since last
change is 2003. I guess these are typos. Hence normal bug.
Also it was not so easy t
...
> feed this into script to extract virtual package names.
>
> If you do not like me adding spaces,
OOps, missing.
If you do not like me adding spaces, just fix 4 typos and date.
--
~\^o^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +
Osamu Aok
^/~~~ ~\^.^/~~~ ~\^*^/~~~ ~\^_^/~~~ ~\^+^/~~~ ~\^:^/~~~ ~\^v^/~~~ +
Osamu Aoki <[EMAIL PROTECTED]> Cupertino CA USA, GPG-key: A8061F32
.''`. Debian Reference: post-installation user's guide for non-developers
: :' : http://qref.sf.net and http://people.debian.org/~osamu
`. `'
s fine as is since the original
text uses "consist of" instead of "contain".
BTW, I have never seen any package name starting any of "+", "-", or
".", nor I have seen any package name with repeated ".". I guess common
sense rules.
--
Osamu Aoki <[EMAIL PROTECTED]> Cupertino CA USA, GPG-key: A8061F32
Hi,
On Fri, Nov 14, 2003 at 01:54:51PM +, Julian Gilbey wrote:
> How? I haven't figured out how to search by Message-ID.
For <> in any debian lists, use:
http://groups.google.com/
Enter:
site:lists.debian.org <>
This works for me :-)
Osamu
On Sat, Oct 22, 2005 at 05:28:17PM +0200, Peter Eisentraut wrote:
> Am Samstag, 22. Oktober 2005 03:03 schrieb Osamu Aoki:
> > Did you decided by yourself that the correct English spelling words with
> > colon should be used instead of developer-reference defined pseudo
> > hea
On Sat, Oct 22, 2005 at 11:34:28PM -0400, Jean-Marc Ranger wrote:
> Sorry to bring even more oil to this already quite large fire.
Thanks for your good research :-)
I just updated developer-reference follwing your private communication.
As you pointed out to me, the debian-policy odiscussion bel
On Sat, Mar 26, 2005 at 07:24:05PM +0100, Marco d'Itri wrote:
> On Mar 26, Roger Leigh <[EMAIL PROTECTED]> wrote:
>
> > Is there a project-wide policy for support for devfs (and devfs-style,
> > e.g. udev devfs.rules) device naming?
> No, but nearly all packages support both conventions.
Nearly a
100 matches
Mail list logo
