Re: Next upload 2007-09-30 (dpkg 1.14.7)

2007-10-10 Thread Guillem Jover
On Tue, 2007-10-09 at 19:04:53 +0100, Ian Jackson wrote: > Guillem Jover writes ("Re: Next upload 2007-09-30 (dpkg 1.14.7)"): > > About starting the dpkg-cross merge, after some conversations with Neil > > and reading some of the dpkg-cross code, I think I've got a pretty good > > idea but needs do

Re: Triggers status?

2007-10-10 Thread Guillem Jover
On Tue, 2007-10-09 at 19:01:53 +0100, Ian Jackson wrote: > Colin Watson writes ("Triggers status?"): > > I have a change to man-db that uses triggers to update the manual page > > database automatically, fixing my second oldest remaining bug. I'd love > > to upload this. While it doesn't break with

Re: [PATCH] proposed v3 source format using .git.tar.gz

2007-10-10 Thread Phillip Susi
Raphael Hertzog wrote: Because Debian is all about cooperation and making the git repository available is an essential step in the process. We currently use alioth.debian.org for that purpose but it's not related to our standard packaging process and the logic to go further is either the idea of

Re: [PATCH] proposed v3 source format using .git.tar.gz

2007-10-10 Thread Raphael Hertzog
Hi, On Wed, 10 Oct 2007, Phillip Susi wrote: > Adeodato Simó wrote: >> * Phillip Susi [Wed, 10 Oct 2007 14:25:46 -0400]: >>> Why go into it half assed by packaging git inside the old format? >> Because otherwise the change won't happen (TM). > > Why is that a bad thing? What good does it do to ha

Re: [PATCH] proposed v3 source format using .git.tar.gz

2007-10-10 Thread Joey Hess
Phillip Susi wrote: > Why is that a bad thing? What good does it do to have the git repo packed > inside the source archive? http://kitenet.net/~joey/blog/entry/an_evolutionary_change_to_the_Debian_source_package_format/ -- see shy jo, over and over, and out signature.asc Description: Digita

Re: [PATCH] proposed v3 source format using .git.tar.gz

2007-10-10 Thread Phillip Susi
Adeodato Simó wrote: * Phillip Susi [Wed, 10 Oct 2007 14:25:46 -0400]: Why go into it half assed by packaging git inside the old format? Because otherwise the change won't happen (TM). Why is that a bad thing? What good does it do to have the git repo packed inside the source archive? H

Re: [PATCH] proposed v3 source format using .git.tar.gz

2007-10-10 Thread Adeodato Simó
* Phillip Susi [Wed, 10 Oct 2007 14:25:46 -0400]: > Why go into it half assed by packaging git inside the old format? Because otherwise the change won't happen (TM). -- Adeodato Simó dato at net.com.org.es Debian Developer ade

Re: [PATCH] proposed v3 source format using .git.tar.gz

2007-10-10 Thread Phillip Susi
Ian Jackson wrote: Manoj Srivastava writes ("Re: [PATCH] proposed v3 source format using .git.tar.gz"): What exactly is the goal of this dpkg addition? This is a sensible question to ask. Goals I would suggest: I find myself wondering the same thing. It seems to me that one of the

dpkg_1.14.7_s390.changes ACCEPTED

2007-10-10 Thread Debian Installer
Accepted: dpkg_1.14.7_s390.deb to pool/main/d/dpkg/dpkg_1.14.7_s390.deb dselect_1.14.7_s390.deb to pool/main/d/dpkg/dselect_1.14.7_s390.deb Override entries for your package: dpkg_1.14.7_s390.deb - required admin dselect_1.14.7_s390.deb - required admin Thank you for your contribution to

Re: For dpkg translators: new git instructions

2007-10-10 Thread Raphael Hertzog
On Wed, 10 Oct 2007, Otavio Salvador wrote: > >> Peter Karlsson <[EMAIL PROTECTED]> writes: > >> > Would doing the incremental updates on a branch and merging it with > >> > "git merge --squash" achieve the same effect, or would that still > >> > clutter the repository? > > Peter looks to use this

Re: For dpkg translators: new git instructions

2007-10-10 Thread Otavio Salvador
Raphael Hertzog <[EMAIL PROTECTED]> writes: > But I think that this is not a sustainable workflow for translators. They > are not used to handle multiple branches and it's complicated enough > already. >> Peter Karlsson <[EMAIL PROTECTED]> writes: >> > Would doing the incremental updates on a bra

Re: For dpkg translators: new git instructions

2007-10-10 Thread Raphael Hertzog
On Wed, 10 Oct 2007, Otavio Salvador wrote: > > This command seems to apply the changes corresponding to the merge but not > > record the merge as a merge, thus losing information concerning the > > changes. It looks like this has the potential to hurt... please don't use > > it. :) > > Sorry but

Re: For dpkg translators: new git instructions

2007-10-10 Thread Raphael Hertzog
On Wed, 10 Oct 2007, Otavio Salvador wrote: > Peter Karlsson <[EMAIL PROTECTED]> writes: > > > Raphael Hertzog: > > > >> Please understand that this is not useful historical information and > >> as such we'd like to avoid seeing it. We want a single "Update Polish > >> translations" instead of 10

Re: For dpkg translators: new git instructions

2007-10-10 Thread Otavio Salvador
Raphael Hertzog <[EMAIL PROTECTED]> writes: > On Wed, 10 Oct 2007, Peter Karlsson wrote: >> Raphael Hertzog: >> >> > Please understand that this is not useful historical information and >> > as such we'd like to avoid seeing it. We want a single "Update Polish >> > translations" instead of 10 sim

Re: For dpkg translators: new git instructions

2007-10-10 Thread Otavio Salvador
Peter Karlsson <[EMAIL PROTECTED]> writes: > Raphael Hertzog: > >> Please understand that this is not useful historical information and >> as such we'd like to avoid seeing it. We want a single "Update Polish >> translations" instead of 10 similar commits. > > Would doing the incremental updates o

Re: For dpkg translators: new git instructions

2007-10-10 Thread Raphael Hertzog
On Wed, 10 Oct 2007, Peter Karlsson wrote: > Raphael Hertzog: > > > Please understand that this is not useful historical information and > > as such we'd like to avoid seeing it. We want a single "Update Polish > > translations" instead of 10 similar commits. > > Would doing the incremental updat

Re: For dpkg translators: new git instructions

2007-10-10 Thread Peter Karlsson
Raphael Hertzog: > Please understand that this is not useful historical information and > as such we'd like to avoid seeing it. We want a single "Update Polish > translations" instead of 10 similar commits. Would doing the incremental updates on a branch and merging it with "git merge --squash" a