Julian Gilbey <[EMAIL PROTECTED]> writes:
> > Alexander Koch wrote:
> > > I have a source which has "samples/admin/" as a dir.
> > > Now I want to have a simple
> > > install -m 644 samples/* $(tmp)/usr/doc/$(pkg)/examples
> > > without touching the admin/ subdir at all.
> > >
>
> Assuming that
Christian Hammers <[EMAIL PROTECTED]> writes:
> But now: How do I put the additional Debian-Logo (only 2k) into the
> diff file ??? Can I rely on the sharutils package though it is only
> "standard" and not "essential" ?
Well, since the sharutils won't be used for installing the package,
but o
[EMAIL PROTECTED] writes:
> Chrony (essentially an xntp3 clone) includes two binaries: a daemon that
> runs as root and a control program that runs in user space. To perform
> certain operations the user running the control program must provide a
> password which is stored in a file readable only
[EMAIL PROTECTED] (Greg Norris) writes:
> I was wondering if anyone can point me to some information on what
> drivers are compiled-in (i.e. not modules) to the kernel on hamm's
> rescue-disk image? I'm trying to generate an alternate rescue-disk
> containing the latest version of the aic7xxx SCS
[EMAIL PROTECTED] (Martin Bialasinski) writes:
> >> "MS" == Martin Schulze <[EMAIL PROTECTED]> writes:
>
> MS> Martin Bialasinski wrote:
>
> >> will dpkg remove a conffile on a upgrade, if I remove it from the
> >> package?
>
> MS> I guess so. Why don't you try it on your system? Make a backu
So I screwed up in packaging, and going directly from bo my fvwm95 for
hamm won't upgrade. Ooops; I made a mistake - this happens. (People
upgrading from a previous hamm version did fine - I really thought I'd
tested this, but apparently not thoroughly enough)
Ok, so after the hamm release I g
What, exactly, is the proper location for .xbm and .xpm icons?
I ask because I had just been putting the fvwm95 icons in
/usr/X11R6/include/X11/pixmaps - but I notice that other packages
place icons in a variety of places:
usr/X11R6/icons
usr/X11R6/include/X11/pixmap (Almost certainly a typo
There's an annoying bug in fvwm95 that I'd like to close (actually,
there are several, but the rest are for another day). Here's the bug
- if one installs fvwm95 but does not install the "menu" package, then
fvwm95 uses the menu derived from the example fvwm95rc provided in the
upstream source (ra
Matthias Klose <[EMAIL PROTECTED]> writes:
> tkdesk requires BLT. in frozen, only BLT2.3 exists, which is
> compatible to tcl7.6/tk4.2 only. Last weekend I uploaded blt8.0-unoff, a
> BLT version compatible to tcl8.0/tk8.0 to unstable (not frozen). Since
> tkdesk seems to profit from the byte com
I am the (new) maintainer of tkdesk and am (finally) getting around to
packaging it up (blame my end of term exams). My question is: where
should this go? It'd be a shame for hamm not to have tkdesk; however,
at the time hamm was declared "frozen", tkdesk was not in it, but in
project/orphaned.
What's the procedure for moving something that's been uploaded into
unstable into frozen? Whom do I contact and what information do I
need to give them? Do I then send out a debian-*-changes message?
I uploaded something into unstable but have been convinced that it
belongs in frozen.
Should I
I know I read this at one point, and I _think_ I remember most of it
correctly, but which doc. describes how dpkg compares version numbers?
I think that in the case of tkdesk I may have to use epochs (the
upstream authors have 1.0-beta-1 through 1.0-beta-5 coming before
1.0-pre-1, which comes befor
Zed Pobre <[EMAIL PROTECTED]> writes:
> Okay, I've checked the archives, followed the instructions, and I
> still can't get it working. What I did (as best I can remember):
>
> On my local machine, did ssh-keygen, stored the files in
> .ssh/identity and .ssh/identity.pub.
>
> Telnet
Anand Kumria <[EMAIL PROTECTED]> writes:
> With your proposed scheme: warn on fvwm95-n and fail on fvwm95-(n+1); it
> means if I never install fvwm95-n but instead skip straight to
> fvwm95-(n+1) I miss out on the warning and am told that the installation
> isn't possible until I delete the old sy
I have just been approved as a Debian maintainer (as in, I've been
told I'll get my master account and subscription to debian-private
tomorrow) and I've gotten fvwm95. Now, whether you may know it or
not, fvwm95 has had a truly ugly configuration up untill now, because
of a bug in FvwmTaskBar. (W
After looking at the most recent WNPP list, I decided that there were
packages (specifically, fvwm95 and tkdesk) that I would be willing to
maintain, so I then read the documentation on www.debian.org on
applying to become a maintainer.
However, after reading that documentation and what the WNPP h
16 matches
Mail list logo