ckdev1-dev depends on:
ii libc6-dev 2.2.2-1GNU C Library: Development Librari
ii liblockdev1 1.0.0 Run-time shared library (libc6) fo
David Coe <[EMAIL PROTECTED]> writes:
> Hi mentors,
>
> I recently adopted camediaplay, which uses non-FH
ckdev1-dev depends on:
ii libc6-dev 2.2.2-1GNU C Library: Development Librari
ii liblockdev1 1.0.0 Run-time shared library (libc6) fo
David Coe <[EMAIL PROTECTED]> writes:
> Hi mentors,
>
> I recently adopted camediaplay, which us
Hi mentors,
I recently adopted camediaplay, which uses non-FHS lock files for
serial devices; I decided to do it right by installing liblockdev1 and
liblockdev1-dev and patching the source to use them.
It works fine, but the liblockdev1 functions get linked statically to
camediaplay, rather than
Hi mentors,
I recently adopted camediaplay, which uses non-FHS lock files for
serial devices; I decided to do it right by installing liblockdev1 and
liblockdev1-dev and patching the source to use them.
It works fine, but the liblockdev1 functions get linked statically to
camediaplay, rather than
hi all,
i hope you can give me advice (or a how-to)---
I want to rename one of my packages (wenglish) because it will soon
provide more than one binary package (wenglish and wbritish) and will
also provide 'new style' versions of those word lists
(words-english-american, words-english-british)...
hi all,
i hope you can give me advice (or a how-to)---
I want to rename one of my packages (wenglish) because it will soon
provide more than one binary package (wenglish and wbritish) and will
also provide 'new style' versions of those word lists
(words-english-american, words-english-british)..
Hi mentors,
ispell needs libncurses4, but (as this bug report correctly
explains) shouldn't depend on a non-"standard" package.
So I have two choices -- compile it with static libncurses4,
or lobby to make libncurses4 part of debian "standard."
Has that been suggested before? Opinions? Thanks.
Ben Darnell <[EMAIL PROTECTED]> writes:
> Thanks for the help with the wxgtk2.1 SONAME problem. Now I'm working
> on python-wxwin. It requires an untarred copy of the wxgtk2.1 source
> (actually, the standard way of building wxPython is to untar it inside
> the wxgtk tree, but that can be avoide
[EMAIL PROTECTED] writes:
> If you know, or suspect, that some might not do then make
> that knowledge explicit (at least by not listing all similar
> packages). All the packages providing *tags are probably
> pretty equivalent, but yacc, byacc, bison etc. have differences
> that mean that some gr
If this has already been discussed, please just point me to it; I must
have missed it...
Yacc and ctags are provided by many different packages, and managed
by update-alternatives, but there is no virtual package corresponding
to either of them.
I suspect there are other similar situations.
I do
Bob Hilliard <[EMAIL PROTECTED]> writes:
> The dictd package is built in .../debian/tmp, which contains
> etc/init.d/dict in ../tmp/etc/init.d, and declares the script as a
> conffile. The dict package is built in .../debian/tmp_2, and has no
> mention of this script in its tree.
Are you su
David Coe <[EMAIL PROTECTED]> writes:
> Guido Guenther <[EMAIL PROTECTED]> writes:
>
> > I don't want to put them in /usr/sbin (where portsentry resides). What's a
> > good place to put them in? I thought about /usr/lib/portsentry/ - is this
> > F
Guido Guenther <[EMAIL PROTECTED]> writes:
> I don't want to put them in /usr/sbin (where portsentry resides). What's a
> good place to put them in? I thought about /usr/lib/portsentry/ - is this FHS
> compliant?
No. Variable data can't go into /usr.
I believe the right answer is /var/state/por
Ben Darnell <[EMAIL PROTECTED]> writes:
[...]
> In the previous package, a tcl script
> was left in the pilot-link package, which made it depend on tcl/tk and
> therefore X. I want to move this file to pilot-link-tcl, and have done
> so by placing the filename in debian/pilot-link-tcl.files. T
Justin Penney <[EMAIL PROTECTED]> writes:
> The current version is 1.2.0. The old version is 1.010. It was packaged as
> 1.10. So when i installed my newer 1.2 package... It said that i was
> downgrading. I realize that this isn't really a big issue but it's still
> annoying and might confuse som
"Ryan McLean" <[EMAIL PROTECTED]> writes:
> I apologize in advance if this isn't the correct place for this question.
Apology accepted; don't do it again ;). debian-users is probably the
right list.
> I plan on using debian on many many systems, and I would like to know how to
> setup a cus
-BEGIN PGP SIGNED MESSAGE-
Darren Benham <[EMAIL PROTECTED]> writes:
> On Mon, Sep 20, 1999 at 07:52:36PM +0200, Radovan Garabik wrote:
> > I am trying to package a program, which does not have version number
> > ...
> > Now what number should have a debian package?
> >
> > I will probab
Any hints/clues/pointers on how to write a brand-new man page?
Debian-specific or not, I'd appreciate a style-guide and a
syntax reference. Thanks.
-BEGIN PGP SIGNED MESSAGE-
I've got two questions about using the bug tracking system,
and would appreciate your advice:
1) http://www.debian.org/Bugs/Developer says:
A developer who receives a bug from the tracking
system, or sees it on debian-bugs-dist, and takes
responsi
Hi Tony (my sponsor),
(Other mentors, FYI),
I think I've got ispell ready; lintian complains about nothing
but the /usr/doc location (which I left that way on purpose
while waiting for guidance from the policy committee).
I've upgraded, installed clean, deinstalled, downgraded each of
the packa
I'm ready to create packages, as a future-maintainer,
to be handed to my sponsor to be uploaded.
Should I set the debian version number to -1 (currently
it's -0.6, never had an official maintainer), or should
I continue using NMU numbering (i.e. -0.7 in this case)?
Thanks!
I just noticed that ispell.texinfo has a few chunks of
documentation (one of which is its copyright) that are
bracketed by [EMAIL PROTECTED]'' ... [EMAIL PROTECTED] ifinfo'' pairs.
This causes those paragraphs to appear in the info
document (generated by ``makeinfo ispell.texinfo'')
but to not app
Richard Braakman wrote:
> "Any", not "all".
>
> Please re-read section 4.2.3 of the Packaging Manual.
Thanks; that's exactly what I needed to do.
[EMAIL PROTECTED] wrote:
> Dependency check for the hurd-i386 architecture
> Cannot satisfy with packages in main:
>
> * iczech: dependency ispell
> * inorwegian: dependency ispell
> * ipolish: dependency ispell
> * ispanish: dependency ispell
I'm the (prospective) new ispel
Mark Brown wrote:
>
> David Coe wrote:
>
> > We have a patch to ispell, submitted to one of the
> > open bugs, which upstream maintainer has decided
> > isn't important enough to incorporate ...
>
> Why not? ...
Upstream author says it's a glibc
I'm looking for advice/experience if you can help:
We have a patch to ispell, submitted to one of the
open bugs, which upstream maintainer has decided
isn't important enough to incorporate into the
upstream versions -- but is (apparently) needed
for non-i386 (Alpha, at least) compatibility in
De
When I submitted my application I attached a scanned
license and passport as requested, because I didn't
know any local debian maintainers (still don't).
I recently read something in -devel that implied this
could delay processing my application even more than
usual.
Should I find someone(s) to s
Quick question:
The various ispell dictionary packages iamerican, ibritish, ipolish,
etc. all provide the virtual package 'ispell-dictionary', but that
virtual package name isn't listed in
ftp://ftp.debian.org/debian/doc/package-developer/virtual-package-names-list.text
-- should it be?
I don't know the official answer, but here's what
(as a long-time debian user) I'd suggest:
If the foo-doc package is documentation for foo,
it should go in the same group as foo.
If the package doesn't have a corresponding non-doc
package, or documents many packages, it should go
in the doc sect
t available to users who want to try it (and help
test/debug it).
Maybe a private site is the answer, if cluttering the
ftp space is a concern.
Sean 'Shaleh' Perry wrote:
>
> On 27-Jul-99 David Coe wrote:
> > I'd like to call the packages ispell and ispell-prerelease
&
I'm preparing a new distribution of ispell (current upstream
version, just packaging and debian standards changes), and
at the same time preparing to package a prerelease of the
next upstream version.
Do we have a "standard" or traditional way of naming
alternate upstream pre-release version p
Under "Adopting a Package" the debian developers' reference manual
says (among other things):
If you take over an old package, you probably want to be
listed as the package's official maintainer in the bug
system. This will happen automatically once you upload a
new version with an
Hi again,
I'm taking over the ispell package (well, will after my developer application
has been approved). [Side note to Iosip: Steve Lamb did also express interest
in that package, thanks for alerting me; but he told me last night that I
should take it, he didn't really want it.]
The upstre
I've announced (on -devel) my intention to adopt an orphaned
package (ispell) while waiting for my developer application
to be processed.
I'm working on some of the open bugs, and would like to
contact one (or more) of the bug submitters.
Should I write directly to the bug submitters and cc:
the
No, /etc/networks just associates a name with a network (base) address,
so what you did is the right thing -- there's no reason to specify
a netmask there.
You just have to specify netmasks in the ifconfig and route commands
(maybe other places too?), which are (in debian) in the
/etc/init.d/n
Hmmm, a fourth year student at u.waterloo in 1993 is probably somewhere
else long since then.
I'm not an official mentor (not even an official developer, yet), so
these are just my thoughts...
Maybe you can contact someone currently at u waterloo (the main web page
links to a long list of web pag
Hi Mentors,
I've applied to become a developer, but I read that the backlog is
rather long, so I have a couple of questions.
I've successfully (I think!) packaged a small utility -- gpart -- and am
considering doing one or two more complicated ones to help get me up to
speed.
Would it be appropr
37 matches
Mail list logo
