The following commit has been merged in the master branch:
commit 6e9f17ba8fa0ae75aee08579d08ba3fae8175869
Author: Raphael Hertzog hert...@debian.org
Date: Fri Mar 13 18:02:35 2009 +0100
Fix Swedish translation so that it doesn't make po4a fail
diff --git a/man/po/sv.po b/man/po/sv.po
Hi,
On Fri, 13 Mar 2009, Norbert Preining wrote:
On Do, 12 Mär 2009, Raphael Hertzog wrote:
Relying on the order inside PATH is too fragile IMO. If you want to have
the binary as install-info directly, you'll have to wait until
install-info is not used any more by debian packages, i.e. for
Hi,
On Thu, Mar 12, 2009 at 07:54:49PM +0100, Hector Oron wrote:
install anything but libraries and headers into /usr/triplet -- so I
don't think there is a pressing need to replicate a filesystem hierarchy
standard below a triplet directory.
That is what GNU people expect when building
Hello Simon,
As far as I've understood, --with-sysroot gives the path to the target OS
installation so the build can run fixincludes and add it to the search
paths; since it should work with a largely unmodified snapshot of the
target OS, they are pretty tolerant with the directory layout
Dear Sir,
Filmex is offering Catalogue Desingin, Photography, Broucher Designing
Domain Registration Printing Service for more information contact at:
FILMEX STUDIOS
Azam Block, Model Town,
Sialkot 51310 Pakistan.
Telephone: +92 52 3259477 - 3559480
Mobile: +92 300 871 4800
Email:
Hi,
, since
they have entirely different objectives
Not entirely different - the objective for the packaging tools is
actually the same, to have packages install cleanly without changes on
systems with a different architecture triplet.
I'm not sure this can be achieved at all, as we still
Hello,
, and there is generally no need to
install anything but libraries and headers into /usr/triplet -- so I
don't think there is a pressing need to replicate a filesystem hierarchy
standard below a triplet directory.
True, however, that is not a sufficient reason to not
move
Hi all,
On Fr, 13 Mär 2009, Raphael Hertzog wrote:
That looks almost right. I hope Guillem can confirm that it's ok for him
as well.
That would be great.
1) /usr/sbin/install-info from dpkg
this one will do:
. if called with absolute path, warn the user to use
Hi Raphael,
thanks a lot for the work.
On Fr, 13 Mär 2009, Raphael Hertzog wrote:
I just wrote it. I had to do it in C otherwise I couldn't do the check
on how it's called.
Ok, fine.
Why? What would change? info-browsers (see below) should depend on
install-info, but if they don't well,
[ Bcced to -devel and -dpkg, discussion should happen on -policy ]
Hello,
we have an unfortunate situation where the practice in dpkg-buildpackage
and the policy do not match fully.
I tried to summarize the problem here:
http://wiki.debian.org/Teams/Dpkg/DebianRules
I want to resolve this
Package: dpkg
Version: 1.14.25
Followup-For: Bug #198220
Hi,
This bug's really old... how is it going?
I just did a dpkg-query -S /usr/bin/w... and of course, no
matches, since /usr/bin/w is a symlink to /etc/alternatives/w is a symlink
to /usr/bin/w.procps ... It's not exactly
11 matches
Mail list logo
