ose lists aren't being updated. Don't worry about
it.
By the way, why did you create a new bug rather than retitling the
existing one? You shouldn't do that.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROT
to be specified, in this example "2.3.0". All four
components may still be used if someone wishes to do so.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
debian
> revision.
Debian revisions x.1, x.2, etc. are generally used for non-maintainer
uploads.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> Why are you surprised? If it's because you prefer info, you can just
> > provide a minimal manpage and refer to the info documentation in it.
>
> I am surprised because i saw programs with an automatic created debian
> manpage or without a manpage.
It's a bug not
ent, so for now I'd say just
wait.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
looked at this, but why would one generate a new
.orig.tar.gz that isn't original? .diff.gz bloat is to be lived with.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Tue, Feb 17, 2004 at 02:42:20AM -0800, Joshua Kwan wrote:
> On Tue, Feb 17, 2004 at 10:16:17AM +0000, Colin Watson wrote:
> > Huh? I haven't looked at this, but why would one generate a new
> > .orig.tar.gz that isn't original? .diff.gz bloat is to be lived with.
>
ng everything after women -
> nobody else has the slightest idea of what does what...
In case you haven't seen it:
http://cvs.debian.org/dak/docs/README.names?cvsroot=dak
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
ld be easier since you can
reuse the old packaging, though (grab it from snapshot.debian.net if
nothing else). Do check for bugs against it that were closed by the
removal, though.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PR
ful because it adds extra complexity to the unpack order: this is
why policy recommends against it.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Sun, Mar 07, 2004 at 01:17:46PM +0100, Andreas Metzler wrote:
> On 2004-03-07 Colin Watson <[EMAIL PROTECTED]> wrote:
> > On Sun, Mar 07, 2004 at 11:23:40AM +0100, Andreas Metzler wrote:
> >> When jumping from 4.3 to 4.5 I'd like to rename pgrep to pcregrep and
>
e also tried something like this, but without
> any success.
Put a file in each chroot (in /etc, say) identifying it, and then read
it into a shell variable in .bashrc so that your prompt can use it.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, ema
ildpackage to force .orig.tar.gz to be
included in the .changes.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
still need to apply thought to the output.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ck.debian.org",
login => $ENV{DEBUSER} || getlogin() || $ENV{USER} || $ENV{LOGNAME},
incoming => "~tfheen$delayed",
dinstall_runs => 1,
method => "scpb",
};
I then do 'DEB_NMU_DELAY=7 dupload --to tfheen-delayed foo.changes'.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
they're manually removed. I suggest making them empty packages (save for
a /usr/share/doc/foo symlink to /usr/share/doc/python-epydoc) that just
depend on python-epydoc, and then make python-epydoc Conflict/Replace
pythonX.Y-epydoc (<< whatever-the-first-empty-version-is).
--
Colin Wa
that bug be release critical instead of important?
"Should" violations aren't release-critical. Also, it's not listed here:
http://release.debian.org/sarge_rc_policy.txt
> Is it worth trying to change that so that this gets fixed for Sarge?
It
re in the .diff.gz (as is usual), then dpkg-source
will not preserve the execute bit when other people extract your source
package. It's better to be consistent.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
an't use that until sarge has been released.
In the absence of that, something like 0.69-really-0.70-rc-1 (or what
you suggest) is a common workaround. It's not too bad to change the
tarball name.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE
.
>
> read the errors. it is clear what you have forgotten.
> you doesn't have a distclean target in your rules file in the debian
> directory.
Not quite; he doesn't have a distclean target in Makefile (not
debian/rules).
--
Colin Watson [EM
On Sun, Mar 21, 2004 at 11:13:36AM +0100, Arnaud Vandyck wrote:
> Colin Watson <[EMAIL PROTECTED]> writes:
> > Tollef Fog Heen opened a delayed queue on gluck a little while ago. My
> > .dupload.conf rune for this reads as follows:
[...]
> Is there a way to achieve th
should refer to policy and use the
sensible-pager system instead.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
pkg-buildpackage, do something morally equivalent to 'debian/rules
build && fakeroot debian/rules binary'.
Use dpkg-buildpackage (or debuild, a wrapper around it which sorts out
fakeroot and the like) rather than 'debian/rules binary'.
--
Colin Watson
r
> each locale and be able to recode every config file, man page,
Not possible. UTF-8 man pages are not yet supported by groff, and won't
be until groff 2.0.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subjec
[Please honour my Mail-Followup-To: header.]
On Wed, Mar 31, 2004 at 04:41:44PM +0300, Martin-Éric Racine wrote:
> On Wed, 31 Mar 2004, Colin Watson wrote:
> > On Wed, Mar 31, 2004 at 09:05:04AM +0300, Martin-Éric Racine wrote:
> > > Heck, if you ask me, Sarge should be known
version number to look for the source, so -1.0.1
becomes -1 and -1.1.1 becomes -1.1.
Beyond that, I don't believe they care.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
to find the source (which
> would be impossible too, is 1.2-0.0.1 a binary NMU of 1.2, or of
> 1.2-0? Though nonstandard, the latter isn't forbidden)
katie tries both of those possibilities.
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
ad katie (and jennifer), you will find it doesn't
> care, it uses afaics the 'Source:' header from the .changes.
Please see the source_exists function here:
http://cvs.debian.org/*checkout*/dak/katie.py?rev=1.45&cvsroot=dak
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
On Fri, Apr 02, 2004 at 04:29:54PM +0200, Jeroen van Wolffelaar wrote:
> On Fri, Apr 02, 2004 at 12:28:32PM +0100, Colin Watson wrote:
> > On Fri, Apr 02, 2004 at 11:53:43AM +0200, Jeroen van Wolffelaar wrote:
> > > Any .deb indicates its source, including binary-only NMU'
doesn't
appeal (remember that neither of us has access to all the
architectures). Also I just don't think this is particularly urgent.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
se.
Every package containing dynamically linked binaries should use
${shlibs:Depends}.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
eople can't use self-compiled kernels without using
kernel-package, and you also don't know whether an installed kernel
package is the running kernel. There's no good way to do this within the
Debian packaging framework, as far as I can work out.
--
Colin Watson [EMAIL PROTECTED]
On Mon, Aug 27, 2001 at 01:01:35AM +0100, Andrew Suffield wrote:
> On Sun, Aug 26, 2001 at 07:06:40PM -0400, Joey Hess wrote:
> > Colin Watson wrote:
> > > But then people can't use self-compiled kernels without using
> > > kernel-package, and you also don&#x
em, but I
can't find it now.
Alternatively, just merge them by hand. Make the Architecture: line of
the merged .changes file contain the architectures from all the others,
and merge all the files named in Files: blocks.
--
Colin Watson [EMAIL PROTECTED]
exists; it's been rolled into the main policy document, and
the parts that aren't actual policy are there as appendices until they
find a better home.
--
Colin Watson [EMAIL PROTECTED]
and in the control bot one day...
>
> Do it. There's not much reason to use the close command, when
> you can just email -done.
Either that or cause 'close' to have better behaviour, e.g. send the
complete text of the control message to the submitter. (If that's
possible, that is.)
--
Colin Watson [EMAIL PROTECTED]
; program it provides, in which case the packages may
transition out of the `/usr/X11R6/' directory at the maintainer's
discretion.
--
Colin Watson [EMAIL PROTECTED]
e nn" in
a message sent to [EMAIL PROTECTED] We're talking about the
latter.
--
Colin Watson [EMAIL PROTECTED]
flip side is that packages might end up with
dependencies that are too tight and so find it harder to be upgraded in
testing: GNOME packages used to have this problem until the gnome-core
maintainer started generating a more accurate shlibs file.
Joey, perhaps dh_makeshlibs(1) could have a note in its ma
share/debhelper/dh_make/debian.
> If there is anyone out there who wouldn't mind teaching me on a 1v1
> session, I'd be in your debt. I learn better from a actual person
> than through docs.
If you like, go ahead and e-mail me privately with what you've got and I
can point
orwarding
mechanism is needed. This can be done with the BSD divert sockets patch
for Linux 2.2, or with netfilter's built-in libipq under Linux 2.4.
(There's shaper too, although that's kernel-space.)
I don't mean to discourage you from packaging this; I'm just c
to your Debianized source package.
Are you planning to enter the new maintainer process
(http://nm.debian.org/)? You should really do that if you want to
maintain a package in Debian.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
ackage.
Please have a look at:
http://www.debian.org/doc/FAQ/ch-getting.html#s-version
http://www.debian.org/doc/FAQ/ch-ftparchives.html#s-frozen
http://www.debian.org/doc/FAQ/ch-ftparchives.html#s-stable
Cheers,
--
Colin Watson [EMAIL PROTECTED]
so is what I distribute elsewhere.
If you can't build the Debian package as part of the process of
generating the tarball from CVS, I suppose you could use -b and hack the
.changes by hand to include the source, although that's rather ugly.
--
Colin Watson [EMAIL PROTECTED]
the rest of this conversation to
private e-mail.
--
Colin Watson [EMAIL PROTECTED]
here may
still be one or two others to do.
> Here I send you the output of the execution:
>
> Can't locate Log/Agent.pm in @INC
newsclipper should depend on liblog-agent-perl.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
s
saying "fixed in NMU". Closing a bug, which is what you want to do, is
distinct from tagging it fixed.
--
Colin Watson [EMAIL PROTECTED]
hy, and how I would go about fixing it?
Perhaps (guessing) you have spaces rather than tabs at the beginning of
the line following that comment?
--
Colin Watson [EMAIL PROTECTED]
version: It works, but there are some things which
should be written, namely some triggers to ensure database consistency,
access control, etc.
Sorry,
--
Colin Watson [EMAIL PROTECTED]
On Sat, Sep 29, 2001 at 01:19:44AM +0200, Martin Sj?gren wrote:
> On Fri, Sep 28, 2001 at 05:10:25PM -0500, Colin Watson wrote:
> > On Fri, Sep 28, 2001 at 09:58:44PM +0200, Martin Sj?gren wrote:
> > > Hello, I'm in the process of adopting the package "barracuda&
n package, the way normal packages work?
--
Colin Watson [EMAIL PROTECTED]
On Mon, Oct 01, 2001 at 02:54:34PM +0200, Tomas Pospisek wrote:
> On Sun, 30 Sep 2001, Colin Watson wrote:
> > I'm not convinced we should have package maintainers who aren't even
> > intending to become full-fledged developers; I don't think that's what
> >
ists-upstream-authors-like-dh_make
N:
N: There is "Upstream Author(s)" in your copyright file. This is not a
N: fixed field name, it's just a default dh_make value. You should adjust
N: it.
N:
You can also run lintian with the -i (or --info) flag to print these
automatically.
--
intian -i gipsc_0.4.2-1_i386.deb
You should run lintian over the .changes files rather than the .debs.
Running lintian on the .debs means that it can't check your source
package.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
1.1 isn't in unstable any more. I'd guess that your best course of
action is to build-depend on libsdl1.2-dev and make sure your package is
linked against that.
--
Colin Watson [EMAIL PROTECTED]
f.gz | patch -p1'
or thereabouts).
Cheers,
--
Colin Watson [EMAIL PROTECTED]
s the .deb, the .orig
> > and a big gap in my hardrive.
> > Back to square one then. At least it is all good experience!
>
> Sounds to me like you didn't name your .orig.tar.gz correctly, which
> means it doesn't create a .diff.gz.
... and in that case, perhaps the .tar.gz actually contains the Debian
diffs too?
--
Colin Watson [EMAIL PROTECTED]
s
> > /usr/share/man/man1/todos.1.gz
>
> Thanks, I've added a conflict line to my package:
> <ftp://ftp.indigita.com/other/david/eol/eol_1.0.2-2_i386.deb>
Perhaps you could rename the binary instead? Adding a conflict because
of a filename clash is really a last res
the
> .changes file as a result. That seems backwards.
I think that's correct. My understanding is that Maintainer: in the
.changes essentially means the developer doing the upload.
Changed-By: should always be the person who made the most recent
changelog entry.
--
Colin Watson [EMAIL PROTECTED]
On Tue, Oct 09, 2001 at 12:20:20PM -0700, Mike Markley wrote:
> On Tue, Oct 09, 2001 at 11:06:32AM -0500, Colin Watson <[EMAIL PROTECTED]>
> spake forth:
> > > I get Changed-By: the sponsoree, and Maintainer: me in the
> > > .changes file as a result. That seems back
On Wed, Oct 10, 2001 at 08:40:46AM +1000, Hamish Moffatt wrote:
> On Tue, Oct 09, 2001 at 08:40:29PM +0100, Colin Watson wrote:
> > However, I can see we aren't going to get anywhere with argument by
> > repeated assertion. :)
>
> Do we need to take this to debian-de
On Tue, Oct 09, 2001 at 07:30:53PM -0400, Sam Hartman wrote:
> >>>>> "Colin" == Colin Watson <[EMAIL PROTECTED]> writes:
>
> Colin> I think that would be appropriate.
>
> Colin> Exactly what are the intended semantics of Maintainer: an
On Wed, Oct 10, 2001 at 12:05:16PM +0200, Wichert Akkerman wrote:
> Previously Colin Watson wrote:
> > If this is your only rationale, it is spurious, as you're talking about
> > Maintainer: in debian/control while I'm talking about Maintainer: in the
> > .chan
y is versioned on (>= 2.2.3-7), but libc6 2.2.4-1 is in
> testing.
>
> Any idea what is keeping libming out of testing?
> Is it php4 missing for ia64 and arm which is keeping the whole libming
> out of testing?
Yes. See update_output.txt:
tried: libming (0) 1
ANONICAL_HOST
> (c) AC_CANONICAL_SYSTEM
Also gettext (#100038, but upstream didn't seem terribly interested in
changing this). This unfortunately introduces the need for triplet
knowledge into packages that are otherwise entirely
architecture-agnostic.
--
Colin Watson [EMAIL PROTECTED]
vel-200110/, search
for SDL, follow the very first link, search for '1.2debian'.)
--
Colin Watson [EMAIL PROTECTED]
bet is to look at an existing package. There are plenty of
small libraries around that you could take a look at. Also, dh_make can
construct sample rules files for libraries which you can then customize.
--
Colin Watson [EMAIL PROTECTED]
, unless they're in a very constrained style.
--
Colin Watson [EMAIL PROTECTED]
On Tue, Oct 23, 2001 at 01:43:51PM +0100, Mark Brown wrote:
> On Tue, Oct 23, 2001 at 07:12:17AM -0500, Colin Watson wrote:
> > On Tue, Oct 23, 2001 at 04:23:43PM +1000, Iain wrote:
> > > Does anyone know of a good program for generating man pages from html?
>
> > Sou
your clean rule; unlike copyright
problems, there's no urgent need to delete them from the upstream
tarball.
--
Colin Watson [EMAIL PROTECTED]
BTS administrators seem to consider this
a feature request rather than a bug report. See #103803.
--
Colin Watson [EMAIL PROTECTED]
close the corresponding directories (mount points).
--
Colin Watson [EMAIL PROTECTED]
the right approach, although strictly speaking it
needs a build-dependency update. Check the policy for details. Apart
from having the right dependencies on perl, you can mostly treat Perl
programs like any other programs.
--
Colin Watson [EMAIL PROTECTED]
gt;
> Blunty, you screwed up the 0.11-1 build. Bump the upstream version
> number (append a + or something) and upload that.
No need for that. Just build with the -sa option to dpkg-buildpackage.
dinstall will happily replace a .tar.gz with an .orig.tar.gz with the
same version number, because the filename has still changed.
--
Colin Watson [EMAIL PROTECTED]
To:
if he wants to reduce the number of people cc'ing him.
--
Colin Watson [EMAIL PROTECTED]
aren't available and thus can't be
installed, but since sh isn't in testing that's not a concern. (As far
as I know sh doesn't have a working autobuilder, and it's certainly
falling behind.)
Cheers,
--
Colin Watson [EMAIL PROTECTED]
run dh_installman from the upstream
> source directory.
Indeed. Consider where it gets run from in debian/rules.
--
Colin Watson [EMAIL PROTECTED]
t I want the file
> to be removed again when the implementation is removed, and I don't
> think conffiles are ever removed.
Conffiles are removed when the package is purged. Configuration files
should behave the same way (i.e. remove them in 'postrm purge').
--
Colin Wat
end on
> dpkg as it is part of base am I wrong?
The criterion is essential rather than base - but yes. As you suggest (I
think), a versioned dependency on dpkg (>= 1.7.0) is required for
dpkg-statoverride regardless of the fact that dpkg is essential.
--
Colin Watson [EMAIL PROTECTED]
item --exclude=item
Exclude files that contain "item" anywhere in their
filename from being deleted, even if they would nor
mally be deleted. You may use this option multiple
times to build up a list of things to ex
self.
(Interesting - I hadn't noticed the part of policy 7.2 before that talks
about what you can rely on in the prerm and postrm. On the odd occasion
where I've needed something there, I've just thrown in a plain
dependency and not worried about it too much.)
--
Colin Watson [EMAIL PROTECTED]
't* send mail to [EMAIL PROTECTED] if you're not the
maintainer. See the various instructions on http://bugs.debian.org/.
--
Colin Watson [EMAIL PROTECTED]
tem
> ready in January or so,
The base system has already been frozen, FYI, although the freeze hasn't
reached the point where it concerns evolution yet. Some of GNOME is
involved in the current stage of the freeze.
--
Colin Watson [EMAIL PROTECTED]
k then? (TFM doesn't
> seem to be available for R)
cron(8), in the "DEBIAN SPECIFIC" section. It refers you to crontab(5)
for the format itself.
--
Colin Watson [EMAIL PROTECTED]
't set yourself as the maintainer as far as
the BTS is concerned, though. It does mean you get the automatic
notifications from the installer. Also, if Maintainer: in the .changes
differs from Maintainer: in the control file (via the .dsc), the upload
will be
t be asked (i.e. the message won't be
displayed).
--
Colin Watson [EMAIL PROTECTED]
you're not
the upstream maintainer) or, as you mentioned, to run chmod before
running the script.
--
Colin Watson [EMAIL PROTECTED]
ad).
dpkg-source makes debian/rules executable, so this isn't a problem when
building from freshly downloaded source.
--
Colin Watson [EMAIL PROTECTED]
ter.debian.org? Please - help me. If someone want I can send
> diff file
You need to apply as a new maintainer and find a sponsor to upload your
packages for you until you have a Debian account. Start at
http://nm.debian.org/>.
--
Colin Watson [EMAIL PROTECTED]
_installman's command line.
(Is the man page really that obscure? Maybe I just know what it's
talking about already ...)
--
Colin Watson [EMAIL PROTECTED]
On Wed, Jan 09, 2002 at 10:42:31AM -0500, Neil L. Roeth wrote:
> On Jan 9, Colin Watson ([EMAIL PROTECTED]) wrote:
> > On Wed, Jan 09, 2002 at 11:05:42AM +0100, Francesco P. Lovergine wrote:
> > > Mmmm, the man page about dh_installman is quite obscure...
> > > Ok,
m without having to get hold of a version of Motif
themselves.
While it still makes sense for OSF/Motif, I think this requirement is
obsolete for OpenMotif. Can anyone in the policy group comment on this?
--
Colin Watson [EMAIL PROTECTED]
in "debhelper"
> (either pre- or post-version 3.4.x).
http://packages.debian.org/ says that it's in the dh-kpatches package in
unstable.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
s is not only sloppy but can break some tools
>
> How else am I supposed to construct this dependency?
That seems to be a bug in lintian (see also #122742). I wrote the
current iteration of that check, so I'll take a look at it. In the
meantime I think you can just ignore it.
--
Colin Watson [EMAIL PROTECTED]
ndent.
> Could someone help me out, and tell me either how to correctly escape
> the \ in man pages or hint me on the correct documentation about it ?
You've already got the answer (\e), but you can find a good reference
for the language in the groff(7) man page, which is part of the groff
package.
Cheers,
--
Colin Watson [EMAIL PROTECTED]
On Mon, Jan 28, 2002 at 11:49:24AM +0100, Sven wrote:
> On Fri, Jan 25, 2002 at 09:57:32AM -0600, Colin Watson wrote:
> > In *roff, \w'string', where ' is any character, gives you the width of
> > string. groff sees \wait{sec}, assumes you're using the separator
ging the upstream
> version number (sorry, I know that this isn't really clean but the
> upstream performs minor changes in a few hour and doesn't change the
> version number).
I suggest using a date-based versioning scheme for the .orig.tar.gz,
such as configwin_0.9-200
t will allow you to build
> packages from source, but with full optimisations for your processor. i.e.
> You would be able to install your complete debian system with all the
> optimisation for your processor(amd, p3, whatever).
I assume you've already seen p
reload-manager package do anything like what you want?
--
Colin Watson [EMAIL PROTECTED]
package.
Every Debian package is generated from a source package.
--
Colin Watson [EMAIL PROTECTED]
701 - 800 of 1012 matches
Mail list logo
