In order to solve some tricky problems to do with
architecture-independent files being produced and uploaded as a result
of per-architecture porting builds, I'm splitting the `binary' target
into two:
binary-arch will build the architecture dependent binary packages and
files. For a straightforwa
Further to this discussion, I'm going to write into the policy manual
that manpages should be installed compressed using gzip -9.
Ian.
Since we need closure on this I'm mandating this change in the new
policy manual and source package format.
I'll also mandate that the debian/changelog file be included, in
/usr/doc//changelog.Debian.gz, or changelog.gz for a package
whose upstream and Debian maintainers are the same.
Ian.
Mark Eichin writes ("Re: Documentation formats"):
> [Ian asked:]
> > (Is texi2html any good?)
>
> http://www.cygnus.com/ (and I'm sure other places) has texi2html'ed
> versions of gnu compiler-related tools, if you want a quick look at
> them.
Thanks. They do look reasonable.
Ian.
Dale Scheetz writes ("Re: CC's on this mailing list"):
...
> However, there are several people who post to the lists, but don't read
> them, who ask to be responded to directly. Maybe we should just require
> that these people suffer reading the lists like the rest of us?
Yes. It is rude to post
Mark Eichin writes ("Re: Documentation formats"):
> if we standardize the names for the alternate formats, can we also
> have, for each format foo, a virtual foo-viewer package, and include
> it in the dependencies? (That will, as a side effect, make it easier
> to determine which formats are supp
Dale Scheetz writes ("Re: New virtual package names. "):
> On Fri, 9 Aug 1996, Ian Jackson wrote:
...
> > Noone is going to deinstall all the editors on their system and not
> > notice what they've done wrong and how to fix it - this is not the
> > kind of `m
Michael Alan Dorman writes ("Re: New package standards - LAST CALL "):
> In message <[EMAIL PROTECTED]>, Ian Jackson writes:
> >Therefore I propose that unless someone raises a serious problem or
> >issue within the next week or two the new packaging guidelines as
Erick Branderhorst writes ("$(ARCH)-debian-linux-gnu"):
> Should we use $(ARCH)-debian-linux-gnu as parameter for ./configure
> and $(ARCH)-debian-linux?
>
> If so can it specified in the guidelines.
> If not what should we use?
$(ARCH)-debian-linux, but $(ARCH) should usually be 486,
shouldn't
Daniel Lynes writes ("Non-existent .deb's"):
> Just a thought, but I was wondering if perhaps the dselect program
> could be modified to allow for it to not allow you to be able to select
> .deb archives that are non-existent? I've noticed that for the .deb
> archives that I haven't downloaded, th
section
3.2.6, ``/usr/doc//copyright''.
--
Ian Jackson, at home. [EMAIL PROTECTED] + 44 1223 3 31579
General: [EMAIL PROTECTED]Permanent: [EMAIL PROTECTED]
Churchill College, Cambridge, CB3 0DS. http://www.cl.cam.ac.uk/users/iwj10/
I wrote:
> Michael Alan Dorman writes ("New source format and related issues..."):
> ...
> > dpkg-source: building hello in hello_1.3.orig.tar.gz
> > tar: Cowardly refusing to create an empty archive
> > Try `tar --help' for more information.
> > dpkg-source: failure: tar gave error exit status 2
.
Bruce Perens writes ("Bug#4129: dselect 1.3.0 infelicity"):
> If I position the selection bar on "All Brokenly Installed Packages" and press
> the "-" key, _all_ packages are de-selected, not just the brokenly installed
> ones. This is counter-intuitive.
`counter-intuitive' ?! You're a master of
Package: sysvinit
Version: 2.64-1
The file /etc/init.d/skeleton should use `set -e' as this is good
practice and it is an example script.
Ian.
Package: sysvinit
Version: 2.64-1
The file /etc/init.d/network is a dpkg-handled conffile, despite
containing important site-specific configuration information which is
set up by the base disks.
Files manipulated by installation scripts should not be dpkg-handled
conffiles.
Ian.
David Engel writes ("Re: Bug#3838: GCC should depend on CPP, not conflict with
it"):
> Ian Jackson writes:
> > David Engel writes ("Re: Bug#3838: GCC should depend on CPP, not conflict
> > with it"):
> > ...
> > > Because they're designed t
Damn, it looks like my comment
Before anyone changes anything, please read the appropriate part of
the new policy manual.
went unheeded. I see that the change that Daniel Quinlan requested
has been made. It's a shame that I didn't get around to writing this
more detailed response to the situati
Otmar Lendl writes in private email which I'm sure he won't mind me
posting:
...
> What I would appreciate is, that all the Developer Ressources
> (Guidelines, Hints, Virtual Names, FSSTD & co.) have a central
> WWW page where I can easily look up the currently valid standards.
>
> Could you pleas
Mark Eichin writes ("Re: installing elisp .el files"):
...
> Byte-compilation depends much more on *speed* than size. The
> changelog mode doesn't do enough (I assume) to merit the speed
> improvement... gnus, for example, really really needs to be byte
> compiled. mailcrypt, w3, vm, probably all
when converting.
* Use minor patchlevel for meaning changes which don't affect packages.
* More verbosity about netiquette.
* Reorganised participation and upload policy: merged with mailing lists.
-- Ian Jackson <[EMAIL PROTECTED]> Fri, 23 Aug 1996 12:48:09 +0100
debian-
You may now upload packages in the new source format to `unstable'.
Packages in `stable' will continue to be in the old format.
Note that the caveats in my release announcement on debian-changes for
1.3.8 apply:
* The new source tools have not been very well tested and will have
bugs, some prob
Bruce Perens writes ("Bug#4195: dpkg-source and new tar package don't mix"):
> Package: dpkg
> Version: 1.3.5
>
> The latest iteration of the tar package unfortunately is not able to
> understand the "--" flag. I suggest you not use that flag in dpkg-source
> for now.
Thanks for pointing out what
Thomas Koenig writes ("Bug#4202: dpkg chainsaw massacre"):
...
> When I tried to test-install the package, there were a few warnings,
> but dpkg happily overwrote /usr/lib with that particular text file.
> I'll eagerly await what fsck has to say about this.
My apologies. I have fixed this in dpkg
Bruce Perens asks me in private email:
> The policy and dpkg programers documents are very good.
> Can you get Ray to put these up on our web site ASAP?
I'd like to, but I think the web site is all confused. I could be
wrong. Does Matt Bailey still exist ? We've been waiting for him for
several
Lars Wirzenius writes ("Re: Documentation formats "):
...
> I'm not certain that distributing HTML with the packages and other formats
> separately is a good idea. I think it might be a better idea to continue
> as now and use on-line conversions from man and Info to HTML. Pre-converted
> HTML shou
Raul Miller writes ("Re: Draft manuals (qmail)"):
...
> Perhaps it's reasonable to specify that every mail aware program
> supports the MAIL environmental variable. As qmail's default behavior
> is to deliver mail to ~user/Mailbox in standard unix mailbox format,
> this should suffice.
But does i
Dale Scheetz writes ("Re: Bug#4164: Ferret extended description has blank lines
"):
...
> Objections to reporting something as a bug are not founded on this
> concept. No one feels personaly "put down" by a bug report. Those of us
> who object to "trivial" bug reports are more concerned about the
Maarten Boekhold writes ("exmh and Xauthority"):
...
> # Generate a random key; Mui and Pearce offer a number of alternatives
> # for this.
> randomkey=`perl -e 'srand; printf int(rand(10))'`
Do NOT do this. It results in a weak cookie, meaning that someone
could fairly easily gue
Rob Browning writes ("Re: Shadow problems"):
> Miquel van Smoorenburg <[EMAIL PROTECTED]> writes:
>
> > You can ofcourse make the new directory setgid (chmod g+s). All files
> > created in that directory will have their gid set to that of the directory..
> >
> > But I can see that using newgrp mi
Milan Zamazal writes ("Packaging questions (newbie)"):
> I'd like to contribute some packages, but I'd like to ask some
> questions first:
>
> 1. One of these packages is the replacement of `libX11.so'. Do I have to make
> whole alternative version of appropriate standard X package or is there so
Thomas Koenig writes ("Bug#2475: at' uses middle-endian 2-digit-year date
format"):
> Date outputs from 'at' are mandated as
>
>date +"%a %b %e %T %Y"
>
> (i.e. "Wed Aug 14 20:05:13 1996") by the Posix.2a draft I have, which is
> the date used in the upcoming release 3.0 of at(1).
>
> Y
Yves Arrouye writes ("Re: libpaper 1.0 on master"):
...
> That's what libpaper does: use whatever paper size is in the PAPER env
> var, or if empty whatever name found in the file whose name is in the
> PAPERSIZE env var, or if this var is empty too look in /etc/papersize,
> defaulting to letter (s
Michael Meskes writes ("Incorrectly locates packages"):
...
> Also, shouldn't the netscape and compress-package installer be moved to
> contrib, too? I know they are free, but to be of any use you have to get the
> some other software that is not free. So in fact they depend on it. Well at
> least
Buddha M. D. Buck writes ("Bug#660: GDB gets address wrong of struct member in
memory breakpoint"):
> I'm looking at the backlog of forgotten bugs, and have verified that
> this one still exists.
>
> The original report was for gdb 4.12, but Ian Jackson verified
>
Buddha M. D. Buck writes ("Bug#818: echo builtin doesn't check for write
errors"):
> As of 1.14.6-4, this bug is still there... maybe
>
> $ type echo
> echo is a shell builtin
> $ echo foo >/dev/full
> $ echo $?
> 0
> $ cat /dev/zero >/dev/full
> cat: write error: No space left on device
> $ echo
Rob Leslie writes ("Bug#4218: Problems removing INN"):
...
> dpkg: error processing inn (--purge):
> cannot remove `/var/spool/news': Device or resource busy
Would it be better if I made dpkg treat this as a warning ?
It happens one of the directories in a package is a mount point.
Ian.
Nils Rennebarth writes ("Bug#4221: knews silently overwrites configuration
file"):
> Knews should handle an upgrade more intelligently and not simply overwrite
> the (possibly customized) /usr/X11R6/lib/X11/app-defaults/Knews
> configuration file.
>
> I know this is difficult to do right. A lot o
[EMAIL PROTECTED] writes ("Re: Bruce - fiat required to end discussion on
lyx/copyright ?"):
> > All packages in the Debian distribution proper must be freely useable,
> > modifiable and redistributable in both source and binary form. It must
> > be possible for anyone to distribute
[EMAIL PROTECTED] writes ("Re: Bruce - fiat required to end discussion on
lyx/copyright ?"):
> > All packages in the Debian distribution proper must be freely useable,
> > modifiable and redistributable in both source and binary form. It must
> > be possible for anyone to distribute
Michael Meskes writes ("Re: Bruce - fiat required to end discussion on
lyx/copyright ?"):
...
> Ahem, this isn't exact enough IMO. With a standard Debian system I am able
> to rebuild LyX.
You can't rebuild LyX entirely from source using only packages in the
main Debian distribution.
> > [...]
Michael Meskes writes ("Re: Bug#4051: access permissions for /usr/bin/fdmount"):
> Ian Jackson writes:
...
> > Compiling names of groups or even worse group ids into binaries is a
> > bad idea.
>
> Why? Because it's not easy to change?
It's ha
Dale Scheetz writes ("Re: New virtual package names. "):
> On Wed, 21 Aug 1996, Ian Jackson wrote:
...
> > I can't prove that it's needless. You're shifting the burden of
> > proof. It's up to you to show that it's needed.
>
> The burde
Dale Scheetz writes ("Re: Bruce - fiat required to end discussion on
lyx/copyright ?"):
> [...] xforms is improperly
> located in contrib instead of non-free where it belongs (because source is
> not distributed). [...]
Sourceless packages are fine to distribute in contrib, so long as the
binarie
Peter Tobias asks me in private email:
...
> BTW: I didn't have much time the last weeks (and I won't have much
> time the next weeks) so I wasn't able to check if this new source
> format will also work for packages like netstd (packages which contain
> lots of "sub packages" each with its own ori
[EMAIL PROTECTED] writes ("Bug#4235: cpp, gcc, dpkg "):
^ was this intentional ?
>
...
> Somehow installation with dpkg-ftp and the new cpp uninstalled my gcc
> package and look how dpkg selects on a dselect update. This shouldn't
> happen. Somehow gcc is too easily uninstalled becau
Susan G. Kleinmann writes ("Bug#4262: dpkg-source requires cpio"):
...
> # dpkg-source -x sgmlspm_1.03ii-2.dsc
> dpkg-source: failure: exec cpio: No such file or directory
> dpkg-source: failure: cpio gave error exit status 2
...
> Installing cpio cured the problem, but suggests that the newest
>
Susan G. Kleinmann writes ("Bug#4263: dpkg-source requires patch"):
...
> # dpkg-source -x sgmlspm_1.03ii-2.dsc
> dpkg-source: extracting sgmlspm in sgmlspm-1.03ii
> dpkg-source: failure: exec patch: No such file or directory
> dpkg-source: failure: patch gave error exit status 2
...
patch is onl
Michael Meskes writes ("Re: 96 New Debian i386 Packages"):
...
> I've scanned through this list and found quite a lot of packages I never
> read an announcement of. I usually read debian-{devel,changes,user,private}
> so I take it I should have found this announcements. But I never have. Did I
> ju
Miquel van Smoorenburg writes ("Re: $(ARCH)-debian-linux-gnu"):
...
> The GNU configure scripts usually match on i[3456]86-*-*) for
> architecture support, so that's not a problem.
>
> I usually do something like:
>
> a = $(shell dpkg --print-architecture)
>
> ifeq (i386,$(a))
> arch = i486-debi
mat dates.
* Typos corrected.
* Released.
-- Ian Jackson <[EMAIL PROTECTED]> Mon, 26 Aug 1996 14:27:34 +0100
Dirk Eddelbuettel writes ("Bug#4238: mirror requires perl"):
...
> On the other hand, we seem to have (had ?) a policy of relying on (at least a
> rudimentary) perl in the base system --- but I cannot find anything on that
> in the programmers and policy manuals of dpkg-1.3.8. So should timezone.pl
Dale Scheetz writes ("Re: Bruce - fiat required to end discussion on
lyx/copyright ?"):
...
> Pine is in non-free because it's copyright places restrictions on the
> distribution of source. Xforms has more severe restrictions on the
> distribution of source than pine does. It is my understanding t
Kevin M. Bealer writes ("Bug#4257: request-route would be better as conffile"):
...
> The modules packages contains a file /sbin/request-route. This is run by
> the kernel to create routes as needed.
>
> The script's comments suggest is it very configurable, and I usually
> configure it heavily .
Peter Tobias writes ("Re: dpkg 1.3.8: dpkg-buildpackage -sa works and is
recommended"):
...
> No problem. The archive with the original sources would be my own
> collection of original sources then ...
Yes, that's right.
Ian.
Michael Meskes writes ("Re: Bug#4051: access permissions for /usr/bin/fdmount"):
...
> I have no problem with it being mode 4750 again.
It should be 4754 - there's no point in stopping people reading it.
(I've been saying 4754 all along, and this is what is in the policy
manual.)
...
> No problem
Dale Scheetz writes ("Re: New virtual package names. "):
>... Part of my concerns stem from the past history of ae. I have
> only recently taken over the maintainance of this package. When I got it,
> the essential field had been declaired a bug, but the discussion of that
> bug seemed to indicate
Juergen Menden writes to me in private email:
...
> well, unfortunately some packages (like ldso) need i386-linux and
> wouldn't like to match i486-linux. better might be
ld.so is not a GNU package, is it ? It probably uses our own
canonical architecture strings, which include i386 for intel, and
Miquel van Smoorenburg writes ("Re: $(ARCH)-debian-linux-gnu"):
> You (Ian Jackson) wrote:
> > Should I provide a command to do this automatically ?
> >
> > dpkg --print-gnu-build-architecture perhaps.
>
> Sure, why not. It would result in more consistency,
Miquel van Smoorenburg writes ("Re: Bug#4218: Problems removing INN"):
> You (Ian Jackson) wrote:
...
> > Would it be better if I made dpkg treat [EBUSY] as a warning ?
> > (It happens one of the directories in a package is a mount point).
>
> Yes, I think so. Eve
Susan G. Kleinmann writes ("Re: Bruce - fiat required to end discussion on
lyx/copyright ? "):
...
> This is my synopsis of the relevant parts of Chapter 2:
>
> Packages go into contrib if their copyrights or patents require that they:
> a. allow distribution of no source code
> b. allow distr
Joey Hess writes ("Bug#4298: arrow keys in dselect don't work after search"):
...
> I'm running dselect in an xterm. I go to the "[S]elect" part of it, and
> the up and down addor keys scroll through the list of packages. But when I
> type "/mosaic\n", to search for mosaic, the arrow keys stop work
hael R. Nonweiler) (3 bugs):
ipx 2913 ipx bootup scripts are broken
ipx 3592 ipx description: no ext
ncpfs3630 ncpfs description: summary starts w/ pkg name
Rob Browning <[EMAIL PROTECTED]> (3 bugs):
gimp-smoti 4303 config of gimp-smotif
libwww-per 3
Package: smail
Version: 3.1.29.1-14
Under certain obscure circumstances Smail can lose mail:
When it needs to send a bounce message it reinvokes itself with the
`-bS' flag, meaning to read SMTP commands from standard input but not
to produce responses. It then feeds an SMTP `session' to the
subp
Package: emacs
Version: 19.31-2
I just upgraded from 19.29-3, and it left me with the following
/etc/site-start.el:
(load "/usr/lib/emacs/19.29/lisp/jka-compr.elc")
(if (file-exists-p "/usr/lib/emacs/site-lisp/w3-init.el") (load "w3-init"))
(autoload 'lout-mode "lout-mode" "Mode for editing Lou
Karl Sackett writes ("dpkg-buildpackage and -source questions"):
> Regarding the -r option for dpkg-buildpackage, are there any
> examples of what's called for here? Is the gain-root-command
> something each developer provides for himself, or is there a command
> or shell somewhere that performs t
Package: textutils
Version: 1.17-2
-chiark:~> echo -e 'hi^IthereM-z\011hi' | cat -vET
hi^IthereM-z^Ihi$
-chiark:~>
As you can see, it's not possible to distinguish a single escaped
control character ^ or M- from the corresponding
sequence of printable characters.
There should be an option to do
If you get this message:
dpkg-source: error: tarfile `./exmh_1.6.9.orig.tar.gz' contains object with
newline in its name
(exmh-1.6.9.orig/?exmh-1.6.9.orig/exmh.README?exmh-1.6.9.orig/COPYRIGHT?exmh-1.6.9.orig/e...(rest
of output deleted)
You should upgrade your cpio. Unfortunately the (Debian
Erick Branderhorst
1009 bash bash problem with quoting/comp Guy Maor <[EMAIL PROTECTED]>
1016 procps top has 3's in vt100 Helmut Geyer <[EMAIL PROTECTED]
1032 boot-flopp Linux Counter Project Info Not Bruce Perens <[EMAIL
PROTECTED]>
10
Michael Meskes writes ("Re: 96 New Debian i386 Packages"):
> Ian Jackson writes:
> > Can we please have a statement on what we should do ?
> >
> > I think we should post the release announcements to debian-changes as
> > well has having the summary posti
Brian C. White writes ("Re: Bug#4261: Ghostview and virtual package
postscript_viewer"):
...
> Yes, [something] _is_ what should be done. "install-mime" handles
> multiple entries for the same mime-type. Thus, if both "ghostview"
> and "gv" get installed, the user is given the choice of which is
Package: emacs
Version: 19.31-2
I used to have in my startup files
(menu-bar-mode nil)
which used to turn off menu bars.
In 19.31 this has changed so that `nil' doesn't have the desired
effect. Instead, you have to supply a negative number !
This is totally inconsistent with almost every other
Steve Greenland writes ("Re: Bug#4204: cron does not install if /usr/sbin/cron
does not exist!?"):
> Yves Arrouye wrote:
...
> > marin13# dpkg -i cron_3.0pl1-33.deb
> > (Reading database ... 0 files and directories currently installed.)
> >
> > Preparing to replace cron (using cron_
Richard Kaszeta writes ("/usr/local (again)"):
...
> Since packages generally don't install anything other than empty dirs
> in /usr/local, can't this be handled in a way that makes it easier for
> those of us trying to maintain many debian machines?
Section 3.2.9 of the policy manual may be infor
I've asked this question before, but noone seemed to want to answer
me, so I'm asking again:
It would be good for the dpkg manuals to be on the Debian web pages.
How do I organise this ? I can (for example) ship a .tar.gz of the
HTML files with each dpkg upload.
I'd like to distribute PostScript
Bruce Perens writes on debian-user and to lots of people:
...
> OK, I hear you - here's a note for the policy manual, Ian, if it isn't
> already in there.
>
> Varargs and libtermcap are provided to support end-users installing
> legacy software, and the few packages (like Netscape) that are not
>
Sven Rudolph writes ("FAQ: Work-Needing and Prospective Packages"):
...
> 1. General Questions
>
> 1.1.What is Debian GNU/Linux
>
> [etc]
Sven, did you receive my message below ?
Ian.
--- start of forwarded message (RFC 934 encapsulation) ---
Newsgroups: chiark.mail.debi
Dale Scheetz writes ("Re: New virtual package names. "):
...
> Well, I'm pretty sure that Bill didn't just wake up one morning and say
> "Wow! That essential field sure is neat! Let's put it in ae! My assumption
> was that this was an attempt to keep ae in the system.
I think that Bill was under t
Michael Meskes writes ("Re: Bug#4051: access permissions for /usr/bin/fdmount"):
> Ian Jackson writes:
...
> > Err, I strongly suggest that you compile the group check out of the
> > executable. This is only likely to lead to confusion.
>
> I think I understand
I have reconfigured the sub-MTA in my home directory on master which
is used by the bug tracking system. (I have Smail installed in my
filespace because qmail's sendmail command line emulation is broken
and using Smail as a gateway to the system's real MTA was easier than
trying to parse RFC822 re
Mark W. Eichin writes ("Re: Bug#4329: Emacs has hardcoded path for jka-compr,
breaks at upgrade"):
> Did you upgrade from 19.29-3 to 19.31-2 as indicated in your message,
> or to 19.34-2, which is current?
19.34-2 hasn't reached my local mirror yet. Isn't it still in
Incoming ?
> (I ask, becau
Dale Scheetz writes ("Re: dpkg-buildpackage and -source questions"):
> On Fri, 30 Aug 1996, Ian Jackson wrote:
> > If you get this message [deleted]
> > you should upgrade your cpio. [...]
>
> This resolved the problem for me. At least at this point I can unpack
&g
-p0.
(where P is the package name and V the version.)
C. There are some packages where the Debian source is the upstream
source. In this case there will be no .diff.gz and you can just use
the .tar.gz. If a .dsc is provided you can use `dpkg-source -x'.
-- Ian Jackson <[EMAIL PROTECTED]> Sat, 31 Aug 1996
Dirk Eddelbuettel writes ("Re: Do we ever retire packages?"):
...
> I would like to have a2gs and a2ps removed. They both have the same
> Description: text, and scope, "ASCII to PostScript filter".
>
> For me, a2gs is broken. I filed bug 1112 against it [1], and this bug is
> still open after 13 m
Michael Alan Dorman writes ("'nother glitch with new source format..."):
> I've almost finished converting a whole package---the only thing I
> lack is a completed .changes file.
>
> When running dpkg-buildpackage on my testbed, I get the following:
> ...
> dpkg-genchanges: error: package ncftp ha
Michael Meskes writes ("metamail_2.7-7"):
> My first try with the new format. Could anyone who knows more about it than
> I do (Ian?) please take a look at it to see if everything's correct?
It looks reasonable, but I have the following complaints:
Your `debian/README' should be called `debian/c
Dale Scheetz writes ("PGP depends."):
...
> Now, as it happens, I have also been reading the new Policy manual (BTW,
> thank you Ian J. for this fine piece of work. It has been long needed and
> I for one greatly appreciate your work) and it has some things to say
> about this issue. In particular
Guy Maor writes ("Re: PGP depends."):
> On Wed, 28 Aug 1996, Dale Scheetz wrote:
>
> > In particular it says that packages that depend on
> > packages in non-free are to reside in contrib (or non-free if other
> > restictions apply).
>
> I've also been meaning to bring this up, but from another a
Package: lyx
Version: 0.10.1-1
Package: lyx
Priority: optional
Section: tex
This should read
Section: contrib
as per section 3.1.3 of the policy manual (version 2.0.1.0), `Section
and Priority'
Ian.
Sven Rudolph writes ("Announce: New Debian FAQ"):
> The new Debian FAQ is now at ftp://ftp.debian.org/debian/doc/FAQ/ .
...
> When you encounter mistakes or want to provide comments or suggestions
> please send it via e-mail to [EMAIL PROTECTED]
...
My comments:
4.4 How should I install a non-Deb
Package: debianutils
Version: 1.2-3
-chiark:d> cat >'cmd with spaces'
#!/bin/sh
echo "called cmd with spaces: $@"
-chiark:d> chmod +x './cmd with spaces'
-chiark:d> './cmd with spaces' hi
called cmd with spaces: hi
-chiark:d> PATH=:$PATH 'cmd with spaces' hi
called cmd with spaces: hi
-chiark:d>
Guy Maor writes ("Re: Do we ever retire packages?"):
> On 29 Aug 1996, Kai Henningsen wrote:
>
> > So, I'd propose a new directory, parallel to contrib and non-free. We
> > could call it "dropped" or "orphaned" and include a README saying that
> > these are packages that are no longer supporte
Rob Browning writes ("Re: dselect/dpkg & multiple versions"):
> Michael Shields <[EMAIL PROTECTED]> writes:
> > (Of course, I ca'n't offer code at the moment so my opinion carries little
> > weight.)
>
> That's not true. It just means that it might take a bit longer for it
> to happen if it's a g
Mark Eichin writes ("Re: $(ARCH)-debian-linux-gnu"):
> I've missed something here. Why are we setting i486 instead of i386
> for *anything*? I can see an advantage to having a dpkg command that
> prints "i386-debian-linux-gnu" instead of having to cobble it together
> (did you notice that most of
Package: xlib
Version: ?
We have this bug, don't we ? It should be fixed.
Ian.
--- start of forwarded message (RFC 934 encapsulation) ---
Article: 918 of chiark.mail.linux-security
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
MIME-Version: 1.0
Message-ID: <
Mark W. Eichin writes ("Bug#4354: movemail doesn't work"):
...
> As shipped, it *was* installed setuid root + setgid mail... could you
> check your installation and verify, and perhaps be more specific about
> movemail's complaint? Also include the actual modes of your
> /var/spool/mail directory,
Mark W. Eichin writes ("Re: Bug#4356: menu-bar-mode flag argument is
inconsistent with universe"):
> > In 19.31 this has changed so that `nil' doesn't have the desired
> > effect. Instead, you have to supply a negative number !
>
> Hmm. The way elisp "optional arguments" work, you can't distingu
Since noone has answered my question I've done what seemed the right
thing:
The next dpkg upload will be accompanied by the manuals in gzipped
PostScript (formatted for A4) and HTML in gzipped tarfiles, as
separate files in the upload.
Ian.
' manual source package section refers to conversion
instructions in policy manual.
* Make it clear that recommending a non-free or contrib package puts a
package in contrib.
-- Ian Jackson <[EMAIL PROTECTED]> Sun, 1 Sep 1996 17:47:18 +0100
debian-manuals (2.0.1.
-BEGIN PGP SIGNED MESSAGE-
Format: 1.5
Date: Sun, 1 Sep 1996 23:59:20 +0100
Source: debiandoc-sgml
Binary: debiandoc-sgml
Architecture: source all
Version: 1.0.5
Distribution: unstable
Urgency: low (HIGH for building dpkg)
Maintainer: Ian Jackson <[EMAIL PROTECTED]>
Descr
-BEGIN PGP SIGNED MESSAGE-
Format: 1.5
Date: Sun, 1 Sep 1996 16:02:23 +0100
Source: hello
Binary: hello
Architecture: source i386
Version: 1.3-12
Distribution: unstable
Urgency: low
Maintainer: Ian Jackson <[EMAIL PROTECTED]>
Description:
hello - The classic greeting, and
601 - 700 of 2527 matches
Mail list logo
