Bug#4355: lesstif-dev has incoorect location for include files<
I'm a bit reluctant to move the header files to /usr/include, since the FSSTND implies that all X-related header files should go under /usr/X11R6/include. I'm not sure if /usr/X11R6/include is in the default search path or not, though I'd argue that putting files in there is confusing (the only ones there now are xforms and netaudio), since the symlink from /usr/include/X11 -> /usr/X11R6/include/X11 might confuse one into thinking that those were the only files there. Plus I just generally think Xm belongs under X11 like all the rest of the widget libraries. For now, I've left the header files where they were, and changed lesstif to include the following two symlinks: /usr/include/Xm -> /usr/X11R6/include/X11/Xm /usr/X11R6/include/Xm -> /usr/X11R6/include/X11/Xm I'm certainly open to further debate, though --- I'm just doing this now to get a fixed version out as quickly as possible. I'll leave the bug report open for the time-being.
Bug#4358: smartlist
Package: smartlist Version: 3.10-1 Hello, I noticed a few problems with the smartlist when I installed it (to check out whether or not it is a candidate to replace majordumbo) My first thought was that the postinst should probably ask whether or not it should set up an announce mailing list -- we might already have such an aliases, or be using majordomo, or just want to check smartlist out without creating a list yet. The postinst is broken, it should use "hostname --fqdn" not "hostname -fqdn" (the extra dash does it...). The postinst should also check to see whether or not newaliases exists before trying to run it, since some of us haven't get our MTA set up to use it. I thought it might get rid of "add following to /etc/aliases from the "create announce" it does, because it adds the aliases itself. Jim
gcc just sorta broke...
I just had dselect run through the latest and greatest in rex, and then found out that something in there broke gcc's ability to find cc1. I just added the directory to my path, and got gcc working again, but I believe one does not normally need to do this. Gcc should know where the correct preprocessor and other things are, right? Jim
Re: Bug#4358: smartlist
On Sat, 31 Aug 1996, James A. Robinson wrote:
jimr>My first thought was that the postinst should probably ask whether or
jimr>not it should set up an announce mailing list -- we might already have
jimr>such an aliases, or be using majordomo, or just want to check
jimr>smartlist out without creating a list yet.
But you need a list to test it. Ok. I can ask for it.
jimr>The postinst is broken, it should use "hostname --fqdn" not "hostname
jimr>-fqdn" (the extra dash does it...). The postinst should also check to
jimr>see whether or not newaliases exists before trying to run it, since
jimr>some of us haven't get our MTA set up to use it.
newaliases could only run when the automatic announce list is generated.
The hostname stuff works fine on debian 1.1.X. Seems that rex contains
an incompatible version. Will fix it on next release.
jimr>
jimr>I thought it might get rid of "add following to /etc/aliases from the
jimr>"create announce" it does, because it adds the aliases itself.
That is what the standard script spits out. Could have a note appear
though to not take it for earnest.
There is another issue with Smartlist which is the automatic generation of
the list user. I do that with a sed script on /etc/passwd which is not
nice. Can anybody point me to the right direction how to use adduser to
add a user and a group without it asking any questions?
And could some kind soul finally get me on the debian-developers mailing
list? I have subscribed a couple of times with no result by writing
email to the request address.
{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}
{}Snail Mail: FTS Box 466, 135 N.Oakland Ave, Pasadena, CA 91182{}
{}FISH Internet System Administrator at Fuller Theological Seminary {}
{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}
PGP Public Key = FB 9B 31 21 04 1E 3A 33 C7 62 2F C0 CD 81 CA B5
Bug#4360: bug in route man page
package: netbase
version: 2.04-1
man page route(8) has:
route add 224.0.0.0 netmask 240.0.0.0 dev eth0
This is an obscure one documented so people know
how to do it. This sets all of the class D (multi
cast) IP routes to go via "eth0". This is the cor
rect normal configuration line with a multicasting
kernel.
the example is missing -net before 224.0.0.0.
lohi:~# route add 224.0.0.0 netmask 240.0.0.0 dev eth0
route: netmask doesn't make sense with host route
Usage: route [-nNvee] [-FC] [Address_families] List kernel routing
tables
route {-V|--version} Display command version and
exit.
route {-h|--help} [Address_family]Usage Syntax for specified
AF.
route [-v] [-FC] {add|del|flush} ... Modify routing table for
AF.
Address_families: inet,ddp,ipx,netrom,ax25
specify AF: -A af1,af2.. or --af1 --af2 or af_route
-- juha
Re: metamail_2.7-7
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/copyright'.
Your binary-root target scheme is redundant - this is now handled by
dpkg-buildpackage.
The copyright file should be in /usr/doc/metamail/copyright, not in
/usr/doc/copyright.
You must install the changelogs.
Your libc dependencies don't use dpkg-shlibdeps.
Your Standards-Version is old, of course - get dpkg 1.3.14 (which will
be out later today) and check the differences to 2.1.0.0 (available in
/usr/doc/dpkg).
Your upload (.changes file) doesn't include the .orig.tar.gz.
You should probably read the final chapter of the policy manual and
use it as a checklist.
> Also I
> wonder since it suffices to upload diff + deb + changes + dsc for the next
> version, how do I tell dpkg-buildpatch to adjust? Hmm, seems I have to read
> the manuals once again. Anyway, here's the .dsc and .changes file:
It has already done this for you - and it has guessed wrong. The
first time, when you're converting the package, you have to use the
`-sa' option to dpkg-buildpackage or dpkg-genchanges to get it to
include the .orig.tar.gz.
Oh, and there's no need to post the .dsc. The .changes is adequate.
Ian.
Re: PGP depends.
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 it says that packages that depend on
> packages in non-free are to reside in contrib (or non-free if other
> restictions apply). This makes it clear that mailcrypt should be in
> contrib rather than the distribution proper. It isn't specific about those
> packages that recommend or suggest a non-free package, but at least
> recommend is strict enough to require special intervention with dselect in
> order to install a package without it's recommends. The policy on these
> conditions should be made more clear.
I have clarified the policy in 2.1.0.0 (dpkg 1.3.14), which will be
out later today.
Packages which Recommend non-free or contrib packages must (almost
always) go in contrib.
Ian.
Re: PGP depends.
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 angle.
> Previously, Ian, you've said that packages which depend on a non-free
> package must be put in non-free, hence the current location.
>
> The reasoning behind this is that a CD would typically have no non-free
> packages. Selecting mailcrypt would apparently confuse dselect as it
> would not be able to find pgp.
>
> I just wanted to confirm that dselect would not have problems with
> moving mailcrypt and other such packages into contrib.
No, it wouldn't have any problems. You'll still find that dselect
complains rather, but it's better to make software available than not,
if we can.
If people don't like that they can deselect all `contrib' packages.
Ian.
Bug#4362: lyx should have `section: contrib'
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.
Re: Announce: New Debian FAQ
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-Debian package?
The hyperlink to the guidelines is broken and should in any case refer
to the new manuals instead.
5.9 How can I check that I'm using a Debian system?
Your check for whether something is a Debian system is wrong. If you
want to know whether the system has dpkg you should check for `dpkg'
on the path or in /usr/bin. Data formats and files in /var/lib/dpkg
may change without warning. If you want to know whether the system is
a real Debian system then /etc/debian_version is the answer.
6.1 What is a Debian package?
The source package format is changing. You should tell people about
dpkg-source, and/or give the instructions for unpacking a Debian
source package without it.
6.2 What is the format of a Debian package?
The internal structure of a .deb file is NOT a generally published
interface. Please DO NOT put it in the FAQ (it's fine to refer to the
deb(5) and deb-old(5) manpages
Instead, tell people to use dpkg-deb. dpkg-deb is the supported
mechanism for manipulating .deb files.
6.4 What's a Debian control file?
Refer to the programmers' manual, not to deb-control(5). The latter
is wildly out of date. If you wish to give an example, please use
mixed case in the field names (this is conventional now, and all upper
case can give some obscure problems in some obscure situations).
6.6 What's a Debian preinst, postinst, prerm, and postrm script?
The layout of /var/lib/dpkg is internal to dpkg and may change without
announcement at any moment. You should at least say this - though it
can be useful for users to know where to find scripts for debugging &c
they should not write programs that look at /var/lib/dpkg.
The supported way to get a list of files in a package is dpkg -L.
6.7 What's a Required/Important/Standard/Optional/Extra package?
This information is also in the policy manual, phrased slightly
differently. I don't know what you want to do about this, if
anything.
6.8 What's a Virtual Package?
6.9 What is meant by saying that a file
Depends/Recommends/Suggests/Conflicts/Replaces/Provides another package ?
6.10 What is meant by Pre-Depends?
These things are now documented in the programmers' manual. You could
perhaps at least mention these. Obviously they have a different
significance for users than for programmers, so perhaps it's
reasonable to have two different descriptions.
7.1 What program(s) does Debian provide for managing its packages?
You've mentioned /var/lib/dpkg again.
Removing a package (as opposed to purging it) leaves _all_ the
configuration info, not just those marked as dpkg conffiles. Other
kinds of configuration are managed by maintainer scripts, but they
should behave the same way wrt purge vs. remove.
8.7 How can I get/install the Debian distribution from my own hard disk?
Hard disk based installation (ie, mounting a hard disk partition and
installing the packages from it) is supported by dselect.
8.10 What's the latest version of Debian?
You have no information here about 1.1.x (aka buzz-fixed). Also, you
say `three months from today' where `today' means about 2 months ago.
11.4 How do I override a file installed by a package so that a different
version can be used instead?
Your invocation of dpkg-divert (not dpkg-override) is entirely wrong.
You mean
dpkg-divert --add /bin/login
or
dpkg-divert --divert /bin/login.debian /bin/login
or
dpkg-divert --rename /bin/login
or some combination of these.
The documentation is in the usage message for dpkg-divert and in the
appropriate section of the programmers' manual. The diversions.txt.gz
file is obsolete and not installed any more.
11.5 How can I have my locally-built package included in the list of available
packages that the package management system knows about?
You can use dselect's idea of `local hierarchies' here too.
13.1 Are there logs of known bugs?
debian-bugs/text no longer exists; debian-bugs/html is simply a link
into WebPages.
Ian.
Bug#4363: `which' cannot cope if command names contain spaces
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> PATH=:$PATH type -p 'cmd with spaces' ./cmd with spaces -chiark:d> PATH=:$PATH which 'cmd with spaces' -chiark:d> PATH=:$PATH which ls /bin/ls -chiark:d> ll total 7 drwxrwsr-x 2 ian ian 1024 Sep 1 16:26 ./ drwxrwsr-x 23 ian ian 5120 Aug 31 19:52 ../ -rwxrwxr-x 1 ian ian44 Sep 1 16:27 cmd with spaces* -chiark:d> echo $SHELL /bin/bash -chiark:d> This can be fixed by appropriate use of quoting, $@, and so on. Ian.
Re: Do we ever retire packages?
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 supported by the Debian project in
> > any way, and are not recommended, but if you want them, here they are.
>
> contrib is an appropriate location for orphaned software.
I have added
which are buggy and no longer maintained, but are preserved for
backward compatibility, or
to the policy manual's list of kinds of package which go in contrib.
Ian.
Re: dselect/dpkg & multiple versions
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 good idea...
Exactly ...
Ian.
Re: $(ARCH)-debian-linux-gnu
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 the changes between 19.31 and 19.32 were
> to get rid of "lignux" and quietly change it to linux-gnu?) I just
> don't see where the 486 vs. 386 change comes from.
>
> (I'll note that of course gcc's configuration is a special case, since
> 486 optimizations don't slow down 386 code noticeably. But that's a
> *special* case not a general one.)
Mmm. We already have dpkg --print-architecture which prints `i386' on
those systems, and putting i386-debian-linux-gnu (or whatever)
together yourself is fine.
Is GCC really such a special case ? If so I'll take dpkg
--print-gnu-build-architecture out again ...
Ian.
Bug#4364: forwarded message from Marek Michalkiewicz
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: <[EMAIL PROTECTED]> Newsgroups: chiark.mail.linux-security Path: ewrotcd!mail-to-news!not-for-mail Precedence: list Received-001: from gate.insite.co.uk ([193.123.212.10]) by chiark.chu.cam.ac.uk with smtp (ident root using rfc1413) id m0uwIIx-0004OtC (Debian /\oo/\ Smail3.1.29.1 #29.35); Fri, 30 Aug 96 02:23 BST Received-002: from marmoset.cv.nrao.edu ([EMAIL PROTECTED] [192.33.115.176]) by gate.insite.co.uk (8.6.9/8.6.12) with ESMTP id AAA24770; Fri, 30 Aug 1996 00:36:56 GMT Received-003: from tarsier.cv.nrao.edu ([EMAIL PROTECTED] [192.33.115.50]) by marmoset.cv.nrao.edu (8.6.12/$Revision: 3.22 $) with ESMTP id SAA20072; Thu, 29 Aug 1996 18:39:26 -0400 Received-004: (from [EMAIL PROTECTED]) by tarsier.cv.nrao.edu (8.6.13/$Revision: 2.10 $) id SAA19717; Thu, 29 Aug 1996 18:40:02 -0400 Return-Path: <[EMAIL PROTECTED]> X-Mailer: ELM [version 2.4 PL25 PGP2] X-Original-Date: Thu, 29 Aug 1996 13:35:46 +0200 (MET DST) X-Original-From_: [EMAIL PROTECTED] Fri Aug 30 02:24:24 1996 Lines: 51 From: Marek Michalkiewicz <[EMAIL PROTECTED]> Sender: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: [linux-security] Re: Vulnerability in the Xt library (fwd) Date: Fri, 30 Aug 1996 04:52:11 GMT Following up my previous message... Another message from bugtraq, which contains a patch to fix the libXt buffer overrun. I haven't verified if the fix is indeed in the (just released) XFree86-3.1.2F - - can't get to ftp.xfree86.org right now (too many users), and can't find this version on mirror sites yet. Marek [REW: I'm not sure that this made it into 3.1.2F. The X consortium fixed a similar bug, which very likely came in too late (the 27th) to make it into 3.1.2F. As an aside, the release of 3.1.2F was MUCH too hasty. (These security bugs have nothing to do with that though.)] > Date: Sun, 25 Aug 1996 22:05:16 -0700 > From: Ollivier Robert <[EMAIL PROTECTED]> > Subject: Re: Vulnerability in the Xt library (fwd) > To: Multiple recipients of list BUGTRAQ <[EMAIL PROTECTED]> > According to John Capo: > > Stefan `Sec` Zehl writes: > > > I can confirm this for Freebsd 2.2-Current, it gives me a euid=0 /bin/sh > > > I can also. The xterm cores on -stable though. > > I sent a patch and a portable version of snprintf to both the X consortium > and Xfree86 yesterday. It will be in 3.1.2F. > > If you have XFree sources on-line and are willing to recompile, apply the > following patch in xc/lib/Xt: > > --- Error.c.old Sun Aug 25 14:57:28 1996 > +++ Error.c Sun Aug 25 14:47:14 1996 > @@ -238,5 +238,5 @@ > (void) memmove((char*)par, (char*)params, i * sizeof(String) ); > bzero( &par[i], (10-i) * sizeof(String) ); > -(void) sprintf(message, buffer, par[0], par[1], par[2], par[3], > +(void) snprintf(message, sizeof message, buffer, par[0], par[1], > par[2], par[3], >par[4], par[5], par[6], par[7], par[8], par[9]); > XtError(message); > @@ -263,5 +263,5 @@ > (void) memmove((char*)par, (char*)params, i * sizeof(String) ); > bzero ( &par[i], (10-i) * sizeof(String) ); > -(void) sprintf(message, buffer, par[0], par[1], par[2], par[3], > +(void) snprintf(message, sizeof message, buffer, par[0], par[1], > par[2], par[3], >par[4], par[5], par[6], par[7], par[8], par[9]); > XtWarning(message); > > -- > Ollivier ROBERT-=- The daemon is FREE! -=-[EMAIL PROTECTED] > FreeBSD keltia.freenix.fr 2.2-CURRENT #18: Sun Aug 18 19:16:52 MET DST 1996 > --- end ---
Bug#4354: movemail doesn't work
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, and an indication of what you're using to
> invoke movemail.
Why does movemail need to be setuid root ?!
> % ar p /p/a1/debian/mirror/binary/editors/emacs_19.31-2.deb data.tar.gz | tar
> tzvf - | grep movemail
> -rwsr-sr-x root/mail 14516 1996-06-03 00:05
> usr/lib/emacs/19.31/i386-debian-linux/movemail
You mean:
dpkg --fsys-tarfile .../editors/emacs_19.31-2.deb |tar tzvf - |grep movemail
or even, since you just wanted it listed:
dpkg --contents .../editors/emacs_19.31-2.deb |grep movemail
The `ar' format is a piece of internal knowledge which you shouldn't
need to make use of.
Ian.
Re: PGP depends.
In article <[EMAIL PROTECTED]> you write: >I bit the bullet today and decided to install and implement pgp. Searching >the packages files did not turn it up, but I was able to deduce that it >was therefore, in non-free. However the search turned up this information: > >dchanges - recommends: pgp With the new source format obsoleting it, dchanges should be removed as soon as possible. (In case anyone tries to use it!) (S)
Bug#4356: menu-bar-mode flag argument is inconsistent with universe
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 distinguish
> between (menu-bar-mode nil) and (menu-bar-mode), and both are
> equivalent to "M-x menu-bar-mode" which a user might actually type.
> scroll-bar-mode works the same way -- no arg (or nil) means *toggle*,
> positive arg means turn on, negative arg means turn off.
> (auto-compression-mode is another example)
I've just done some experiments and with the function
(defun spong (&optional x)
(interactive "p")
(message (prin1-to-string x)))
calling it interactively with no prefix arg gives x=1. With a prefix
arg x is the prefix arg. You can call it non-interactively with `nil'
or `t'.
Ian.
Bug#4365: no section and priority in debian/tmp/DEBIAN/control
Package: dpkg Version: 1.3.12 dpkg-gencontrol creates no priority and section entries in debian/tmp/DEBIAN/control, but theese fields are in debian/files. is this ok or is this a bug ? example : debian/control: Maintainer: Andreas Jellinghaus <[EMAIL PROTECTED]> Section: text Priority: optional Standards-Version: 2.0.0.0 Package: mpage Architecture: any Section: text Priority: optional Depends: libc5 Suggests: gs Description: print multiple pages per sheet on PostScript printer Mpage reads plain text files or PostScript documents and prints them on a PostScript printer with the text reduced in size so that several pages appear on one sheet of paper. This is useful for viewing large printouts on a small amount of paper. Uses ISO 8859.1 to print 8-bit characters. debian/files: mpage_2.3-1_i386.deb text optional debian/tmp/DEBIAN/control: Package: mpage Version: 2.3-1 Architecture: i386 Depends: libc5 Suggests: gs Installed-Size: 98 Maintainer: Andreas Jellinghaus <[EMAIL PROTECTED]> Description: print multiple pages per sheet on PostScript printer Mpage reads plain text files or PostScript documents and prints them on a PostScript printer with the text reduced in size so that several pages appear on one sheet of paper. This is useful for viewing large printouts on a small amount of paper. Uses ISO 8859.1 to print 8-bit characters. Regards, Andreas
Bug#4358: smartlist
> But you need a list to test it. Right, but we might want to create "smartlist_tester" to test it. > Ok. I can ask for it. Thank you! > newaliases could only run when the automatic announce list is generated. Well, my point was that newaliases isn't _on_ my system, and if it fails the postinst exists with an error -- meaning dpkg thinks it is failed. > The hostname stuff works fine on debian 1.1.X. Seems that rex contains > an incompatible version. Will fix it on next release. Yeah, hostname 1.9 accepted the single dash, even though it doesn't claim to in its help -- 2.0 works the standard GNU way of wanting double dashs for any long option name. > That is what the standard script spits out. Could have a note appear > though to not take it for earnest. Or you could filter it out by redirecting stdout and stderr through sed or something. > There is another issue with Smartlist which is the automatic generation of > the list user. I do that with a sed script on /etc/passwd which is not You need to ask the base disk maintainer (Bruce?) to add the user to the passwd entry. > And could some kind soul finally get me on the debian-developers mailing > list? I have subscribed a couple of times with no result by writing > email to the request address. Ugh, I've been reading about problems with this (getting ahold of the list mainter). It looks like they might be switching servers so somebody with more time can handle all the devel requests... Jim
Re: Bug#4329: Emacs has hardcoded path for jka-compr, breaks at upgrade
On Sat, 31 Aug 1996, Ian Jackson wrote: > [1] Yes, I know it was probably deliberate, but American middle-endian > date-formats are stupid and confusing and I want them stamped out. > You have better things to do than to stamp about for the rest of your life. Also, you will never get anyone's attention when you address them as "Hey stupid!". No matter that I understand your desire to have sortable dates, I will continue to write my checks with middle-endian dates, if for no other reason than that, otherwise, my "stupid" bank will not be able to cash it. Luck, Dwarf -- aka Dale Scheetz Phone: 1 (904) 877-0257 Flexible Software Fax: NONE Black Creek Critters e-mail: [EMAIL PROTECTED] If you don't see what you want, just ask --
Re: Bug#4358: smartlist
James A. Robinson wrote: > > The hostname stuff works fine on debian 1.1.X. Seems that rex contains > > an incompatible version. Will fix it on next release. > > Yeah, hostname 1.9 accepted the single dash, even though it doesn't > claim to in its help -- 2.0 works the standard GNU way of wanting > double dashs for any long option name. hostname 1.9 and 2.0 both use the standard gnu way but hostname 1.9 only checked for one option (it just takes the option -f from -fqdn and ignores the options -q -d -n). hostname 2.0 checks the other options too and prints an error message for the unknown option(s). Thanks, Peter -- Peter TobiasEMail: Fachhochschule Ostfriesland [EMAIL PROTECTED] Fachbereich Elektrotechnik und Informatik [EMAIL PROTECTED] Constantiaplatz 4, 26723 Emden, Germany [EMAIL PROTECTED]
Bug#4366: Kernel headers should be a symlink
Package: kernel-source
Version: 2.0.6
The kernel headers /usr/include/{linux,asm,scsi,net} should
be a symlink to /usr/src/linux/{linux,asm,scsi,net} and
not installed as "real" files. Or maybe something like
/lib/modules/current?
When compiling a new kernel version, one often forgets to
update the kernel headers. I did.
/sjm
--
Soren Juul Moller Danosi A/S
[EMAIL PROTECTED] Lautrupbjerg 5
(+45) 4489 4959DK-2750 Ballerup
dpkg manuals in other formats and on web site
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.
changes to dpkg manuals in 2.1.0.0 (dpkg 1.3.14) since 2.0.0.0
debian-manuals (2.1.0.0) unstable; * Upstream changelog must be installed too (was just recommended). * Modification to use dpkg-shlibdeps added to conversion instructions. * Packages which are buggy and orphaned but which are preserved for compatibility go in contrib. * Programmers' 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.0) unstable; * varargs.h and libtermcap are obsolete - use stdarg.h and ncurses. * Shared library link/library ordering corrected (aargh). * When to byte-compile Elisp files. * Missing final newlines not represented by dpkg-source. * Must post upload announcements to debian-changes. * Moved some sections into new `configuring and building' chapter. * Typo fixes. -- Ian Jackson <[EMAIL PROTECTED]> Sat, 31 Aug 1996 20:07:22 +0100
debiandoc-sgml 1.0.5: bugfixes (req'd to compile dpkg 1.3.14)
-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]> Description: debiandoc-sgml - Documentation formatting for Debian manuals Changes: debiandoc-sgml (1.0.5) unstable; urgency=low (HIGH for building dpkg) . * debiandoc2ps -O (output to stdout) works. * Lout converter uses `paperconf' (thanks to Yves Arrouye). . * Manpages installed compressed. * dpkg-gencontrol invocation moved to near end of debian/rules. * Some typos in markup manual corrected. * Spurious `t' file removed from source package. * Updated to Standards-Version 2.1.0.0. Files: 63492024bd04abe5bd0a12ce6a07a1e9 559 text optional debiandoc-sgml_1.0.5.dsc 6127aeedbb950d2fdaf6ffe59c69bd6e 34047 text optional debiandoc-sgml_1.0.5.tar.gz bf6a689902005cbada5f0f37a2f367d9 25002 text optional debiandoc-sgml_1.0.5_all.deb -BEGIN PGP SIGNATURE- Version: 2.6.2i iQCVAwUBMioVjsMWjroj9a3bAQE1rwQA5/ZtzBrp6DnuL48Wgqe8HXro1uunTc8O o2gO0JeIUFX3pNbD6LkS3wVsOC9swfo6nON6liyv+I977lQjKYAwejLKCUegm+hm iIAj//i2T7gNmsJp1yEs8QmHQ4Ei0bp+UWGmcvRIhlg5VVxVQTqKKt5m+mRvHfBF XnKqu/m8EbA= =HxUL -END PGP SIGNATURE-
hello 1.3-12: minor packaging changes
-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 a good example Changes: hello (1.3-12) unstable; urgency=low . * Added Debian and upstream changelogs to binary package. * Updated to Standards-Version 2.1.0.0. Files: 47595e5623b90d936805f43b404d7e41 596 devel optional hello_1.3-12.dsc feaaf374a97be998622918c2b7b78b01 3359 devel optional hello_1.3-12.diff.gz 47a4a5ff14524256b452911b7fefc71c 17490 devel optional hello_1.3-12_i386.deb -BEGIN PGP SIGNATURE- Version: 2.6.2i iQCVAwUBMioZFMMWjroj9a3bAQEGpQP/ZcAFER+Wde08NnzEgePxHU9nL0++hvZv EXaJAwjmRA9q4LgVVOyGzEuP9T+AF4Bs8M/Zcm7zUAz+xDMXwdmGJKi8ehqI/cYB zwdzcG8MC+G3jS/UYxUk6u2in87WevnPQxhI6S//LF7juzVLf/lKIOP2DFf2uv9+ 8RZKQMbl3xk= =waHg -END PGP SIGNATURE-
It's time for dpkg-dev
Ian, Would you consider splitting dpkg into runtime and developers packages? It's getting big, and the space on the base system is limited. Thanks Bruce
dpkg 1.3.14: source packaging minor changes; manual updates
-BEGIN PGP SIGNED MESSAGE-
Format: 1.5
Date: Sun, 1 Sep 1996 20:43:40 +0100
Source: dpkg
Binary: dpkg
Architecture: source i386
Version: 1.3.14
Distribution: unstable
Urgency: low
Maintainer: Ian Jackson <[EMAIL PROTECTED]>
Description:
dpkg - Package maintenance system for Debian Linux
Changes:
dpkg (1.3.14) unstable; urgency=low
.
* dpkg-buildpackage new -tc (clean source tree) option.
.
* Formatted documentation removed by `make clean' and so not in source.
* Manuals and own Standards-Version: updated to 2.1.0.0.
* Distribute {policy,programmer}.{html.tar,ps}.gz with each upload.
Files:
61bf1106e51ff3f61a946b2981ffed24 532 base required dpkg_1.3.14.dsc
f7d587f09d8de2d0b63730ea38b2e379 475066 base required dpkg_1.3.14.tar.gz
83059911314f210fe0e6a09b66860d09 353042 base required dpkg_1.3.14_i386.deb
e962fec5d3666c865370d52028cab843 348367 byhand -
dpkg_1.3.14_i386.nondebbin.tar.gz
ae3a653c2c548edeb8461c3dc8da78a4 66341 byhand - policy.ps.gz
5fb35198a41f41f2de5a629e964689b3 23610 byhand - policy.html.tar.gz
28a6bca1607677838ee17a253c2551cb 121444 byhand - programmer.ps.gz
79023db8ae75add7444a28a57cf62f73 41254 byhand - programmer.html.tar.gz
-BEGIN PGP SIGNATURE-
Version: 2.6.2i
iQCVAwUBMioX48MWjroj9a3bAQHgRwP6AjBhK9CSYTQysE5zX0kBxkr9syDpy2BF
rpSNkkCjRU2Vj1W4+vOCOrny4JWJJJ8ZrVcHuBTYYy8fRPGUiVcH1HWwZ5tvWG7v
KWQducfpR6dtqJT0Bc9fKK+dhwb4vR143TmQ0ytdIu3LJYxRrhUc5S6LsGxAqBmj
SDCTXBs0a9c=
=Zaih
-END PGP SIGNATURE-
