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
> Best practice is to use a proper revision control system (one which
> can do patch stack management if that's desired) and generate a
> consolidated .dsc/.diff.gz for people who don't want to get to grips
> with it.
Which will only give useful results if we have a central repository
for all pac
On Tue, Dec 18, 2007 at 08:05:54PM +, Ian Jackson wrote:
> Russ Allbery writes ("Re: Task list for a policy release"):
> > #379150: Documentation for Breaks in dpkg
> > This support was added in dpkg 1.14.6, so I'm inclined to accept and
> > commit this
Russ Allbery writes ("Re: Task list for a policy release"):
> #379150: Documentation for Breaks in dpkg
>
> This support was added in dpkg 1.14.6, so I'm inclined to accept and
> commit this patch. I trust Ian to document the feature, and the wording
> seems fine t
On Mon, Dec 03, 2007 at 11:11:14PM +0100, Bill Allombert wrote:
> On Sat, Dec 01, 2007 at 10:13:49PM -0800, Russ Allbery wrote:
> > Manoj Srivastava <[EMAIL PROTECTED]> writes:
> > #250202: [PROPOSAL] "debian/README.source" file for packages with
> > non-trivial source
> >
> > Bleh. This is kind
This one time, at band camp, Bill Allombert said:
> On Sat, Dec 01, 2007 at 10:13:49PM -0800, Russ Allbery wrote:
> > Manoj Srivastava <[EMAIL PROTECTED]> writes:
> > #250202: [PROPOSAL] "debian/README.source" file for packages with
> > non-trivial source
> >
> > I don't like the last wording prop
Bill Allombert <[EMAIL PROTECTED]> writes:
> On Sat, Dec 01, 2007 at 10:13:49PM -0800, Russ Allbery wrote:
>> I don't like the last wording proposal in that it advocates strongly
>> against using quilt or dpatch, which as near as I can tell from other
>> Debian mailing list discussion and packagin
On Sat, Dec 01, 2007 at 10:13:49PM -0800, Russ Allbery wrote:
> Manoj Srivastava <[EMAIL PROTECTED]> writes:
> #250202: [PROPOSAL] "debian/README.source" file for packages with
> non-trivial source
>
> Bleh. This is kind of a mess.
>
> I don't like the last wording proposal in that it advocates
On Sun, 02 Dec 2007, Russ Allbery wrote:
> > There's no requirement on the dak/ftp-master side. We're not using them
> > yet only because we don't want to force people to update dpkg/apt before
> > doing the etch->lenny upgrade.
>
> Ah, in that case, maybe we should hold off putting Breaks into Po
Raphael Hertzog <[EMAIL PROTECTED]> writes:
> On Sat, 01 Dec 2007, Russ Allbery wrote:
>> #379150: Documentation for Breaks in dpkg
>>
>> This support was added in dpkg 1.14.6, so I'm inclined to accept and
>> commit this patch. I trust Ian to document the feature, and the wording
>> seems fine t
On Sat, Dec 01, 2007 at 08:53:19PM -0200, Felipe Augusto van de Wiel (faw)
wrote:
> On 01-12-2007 19:53, Marc Haber wrote:
> > On Sat, Dec 01, 2007 at 04:52:16PM -0200, Felipe Augusto van de Wiel (faw)
> > wrote:
> >>Considering the chance of rewriting the document and using
> >> UTF-8, can y
On Sat, 01 Dec 2007, Russ Allbery wrote:
> #379150: Documentation for Breaks in dpkg
>
> This support was added in dpkg 1.14.6, so I'm inclined to accept and
> commit this patch. I trust Ian to document the feature, and the wording
> seems fine to me. The only caveat is that I don't know if we'r
I'd really like to get a new debian-policy package uploaded tomorrow. It
won't be the last one, and we can go back and add more patches and other
fixes later. There are already some major things fixed since the last
release that are widely deployed.
Here's what I think the plan should be:
* Mer
Manoj Srivastava <[EMAIL PROTECTED]> writes:
> * #402780: debian-policy HTML "next" loops
> This is either not a bug, or can't be fixed in policy: should
> forward to debiandoc
Agreed.
> * #47438: [PROPOSAL] update policy copyright
> This is too hard to resolve right no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01-12-2007 19:53, Marc Haber wrote:
> On Sat, Dec 01, 2007 at 04:52:16PM -0200, Felipe Augusto van de Wiel (faw)
> wrote:
>> Considering the chance of rewriting the document and using
>> UTF-8, can you consider the idea to add support for tran
On Sat, Dec 01, 2007 at 04:52:16PM -0200, Felipe Augusto van de Wiel (faw)
wrote:
> Considering the chance of rewriting the document and using
> UTF-8, can you consider the idea to add support for translations in
> the build process and repository layout while doing the rewriting?
Debian po
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 01-12-2007 02:51, Manoj Srivastava wrote:
[...]
> * #175064: Debian policy documents should be UTF-8 encoded
> Whoof. Well, we can make sure that the source files are in
> UTF-8; and that we set ALNG=C in front of the debiandoc2X
>
Hi,
There are three areas that need to be looked at before we can
release a new version of policy; and two of them are kinda important,
but we can punt on the third, is push comes to shove.
The first task is resolving all the bus marked as Packaging bugs
on
http://bugs.debian
18 matches
Mail list logo
