Re: dpkg changes and queries - the answers to your questions

[Dale Scheetz]

On Tue, 24 Sep 1996, Heiko Schlittermann wrote:

> Have you ever tried
> 
> dpkg-buildpackage -r'su root -c' 
> 
> ?? (Ok, Michael hasn't read the manual (like me) and tried it.  The
> manual says, the root command must not contains any white space ...
> 
Nope, I haven't. (I su to root before I do the build)

I remember the manual implied that the "set root"  option should contain
the name of a program/script that would perform the 'su root -c' or
whatever method was chosen, so, I guess I agree with Ian that the "quote
patch" should not be used.

Thanks,

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 --

Bug#4574: gs -g flag does not work

[Brian Mays]

Package: gs
Version: 4.01-4

The `-g' flag, which is described below, does not produce the intended
effect.

>From the man page:
>   -gnumber1xnumber2
>  Equivalent to -dDEVICEWIDTH=number1  and  -dDEVICE-
>  HEIGHT=number2.  This is for the benefit of devices
>  (such as X11 windows) that require (or allow) width
>  and height to be specified.

For example, under X11 windows, the commands

$ gs -g100x100 some_postscript_file.ps
$ gs -dDEVICEWIDTH=100 -dDEVICEHEIGHT=100 some_postscript_file.ps
$ gs some_postscript_file.ps

all produce the same results.  Note that this is independent of the
contents of the `/etc/papersize' file (including when this file does
not exist).

More packages up for adoption

[David Engel]

I hate to add to the growing number of orphaned packages, but I
currently barely (if even that) have time to maintain the packages I'm
really interested in.  As a result, I'm officially putting up for
adoption the packages I took over on an interim basis much too long
ago when they were originally orphaned.

In case anyone is wondering, I am not leaving the project.  I will
continue to maintain my other packages and will also be available to
help whoever takes over my former packages.

Here is the list of packages I'm putting up for adoption with my
assessment of what is involved in maintaining them.

binutils: Track H.J. Lu's version and various architecture-specific
patches.  Not too much work right now but could change as support for
other architectures is added.

gcc/cpp: Track FSF version.  Not too much work.

gdb: Track FSF version.  Not too much work.

libc5*/libc6*: Some of the most important packages.  potentially a lot
of work.  My plan was to only add serious patches to the current
versions and wait for glibc/libc6.  Whoever takes these may want to
upgrade to one of H.J. Lu's newer versions before taking on libc6.

libg++: Current version needs to be upgraded to H.J. Lu's newest
version.  Track H.J. Lu's version.  Things could be complicated by
multiple architecture support and libc6.

libc4*, aout-binutils, aout-gcc: As far as I'm concerned, these are
deprecated and should not be supported.  However, if somebody wants to
update them, I won't stop them.

David
-- 
David EngelOptical Data Systems, Inc.
[EMAIL PROTECTED]  1101 E. Arapaho Road
(214) 234-6400 Richardson, TX  75081

Re: dpkg changes and queries - the answers to your questions

[Heiko Schlittermann]

Dale Scheetz wrote:
: 
: On Tue, 24 Sep 1996, Heiko Schlittermann wrote:
: > Dale Scheetz wrote:
: > : On Mon, 23 Sep 1996, Heiko Schlittermann wrote:
: > : > withecho $rootcommand "debian/rules clean"
: > : > If I did no mistakes it worked for me.
: > : When I installed Michael's "quote patch" the next time I tried to run
: > : dpkg-buildpackage I got was informed that debian/rules did not exist.
: > : Removing the quotes got it working again.
: > Near the start of dpkg-buildpackage there's a line
: > rootcommand=''
: > change it to
: > rootcommand='eval'
: > and put in Michels quoting.
: > This _should_ work.
: I can certainly do this. The question is: What purpose is served by the
: quotes? It works fine for me without them.

Have you ever tried

dpkg-buildpackage -r'su root -c' 

?? (Ok, Michael hasn't read the manual (like me) and tried it.  The
manual says, the root command must not contains any white space ...




Heiko
--
email : [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
pgp   : A1 7D F6 7B 69 73 48 35  E1 DE 21 A7 A8 9A 77 92 
finger: [EMAIL PROTECTED] [EMAIL PROTECTED]

Bug#4568: a2ps binary still a.out

[Dirk . Eddelbuettel]

  Yves Arrouye writes:
  Yves>  I'd like to take the a2ps package if its maintainer does not plan to
  Yves> maintain it anymore: I have patches to make it work with libpaper
  Yves> that I'd like to see in the Debian version.

To best of my knowledge, a2ps and a2gs are orphaned. Casual inspection of the
packages on my mirror reveals that they were created in February and
September of 1995, respectively.  Yep, that's twelve, or nineteen *months*
ago. 

I would prefer it if you patched the more useful enscript (successor to
genscript). Or psutils, dvips, ...  in short: programs that people use and
maintain. But you are of course free to do whatever you personally
prefer. Just my 0.02 centimes.

--
Dirk Eddelb"uttel http://qed.econ.queensu.ca/~edd

Bug#4568: a2ps binary still a.out

[Yves Arrouye]

I'd like to take the a2ps package if its maintainer does not plan to
maintain it anymore: I have patches to make it work with libpaper that
I'd like to see in the Debian version.

Yves.

New slang packages : jed slrn and other maintainers take note

[Chris Fearnley]

I have put my new slang packages on
ftp://ftp.netaxs.com/people/cjf/debian or
http://www.netaxs.com/~cjf/debian.

The only reason I havn't put them on master yet is the questions I
just posted regarding Section and Priority fields.  Everything else
about the package has been as well tested as I can muster right now.
So if you need this to build jed or slrn or other package, check it
out.  You'll need it at least for the dpkg-shlibdeps stage in your
debian/rules.

I'll probably put it on master tomorrow after my questions about
packaging are resolved.

-- 
Christopher J. Fearnley|Linux/Internet Consulting
[EMAIL PROTECTED], [EMAIL PROTECTED]   |UNIX SIG Leader at PACS
http://www.netaxs.com/~cjf |(Philadelphia Area Computer Society)
ftp://ftp.netaxs.com/people/cjf|Design Science Revolutionary
"Dare to be Naive" -- Bucky Fuller |Explorer in Universe

Section: and Priority: in shared libs: Questions and PROPOSAL

[Chris Fearnley]

Greetings,

I've prepared two binary packages from one "Source: slang" package:
 slang0.99.34 - A C programming library for user interfaces - shared library
 slang0.99.34-dev - A C programming library for user interfaces - development 
kit

I wanted to set the following Section and Priority:

  Package   Section Priority
slang0.99.34devel   standard
slang0.99.34-devdevel   optional

There are two main issues to be addressed:

First, how to get the correct information into the control and
.changes file.  I have been unsuccessful in accomplishing this.

In the debian/control file, empirical research shows that one can only
put Section and Priority fields in the Source portion of the file and
hence only identical values can be suggested here for each binary
package.

I have tried using these two commands in various places in
debian/rules to no avail:
dpkg-distaddfile slang0.99.34-dev_0.99.34-1_i386.deb  devel optional
dpkg-genchanges -DPriority=optional

Anyone know the answer?

Can we document it in the programmer's manual (or maybe it's there and
I missed it)?

Secondly, my decision to put the shared object in "standard" and the
development kit in "optional" is /not/ the way tcl74, tcl75, and
probably other do it.  So I'm really making the suggestion that all
shared libraries should go into "standard" so that most all systems
would get these packages installed.  But the -dev packages should only
be installed by those who go out of their way in dselect to choose such
"optional" packages.  For ease of reference here is what the policy
manual says:

   standard
  These packages provide a reasonably small but not too limited
  character-mode system. This is what will install by default if the
  user doesn't select anything else. It doesn't include many large
  applications, but it does include Emacs (this is more of a piece
  of infrastructure than an application) and a reasonable subset of
  TeX and LaTeX (if this is possible without X).
  
   optional[4]
  This is all the software that you might reasonably want to install
  if you didn't know what it was or don't have specialised
  requirements. This is a much larger system and includes X11, a
  full TeX distribution, and lots of applications.  

Finally, in the debian/shlibs file should I include information about
historical versions of the current package?  In my case should I add the line:
  libslang 0  slang-lib
to this file, so that the old (inflexibly packaged) version of this
shared lib is recorded for possible use later?

At first I thought, of course.  But now I'm leaning toward only
including the current packages information.  Because I can't see any
reason to maintain that level of support for older versions of the
shared libs.

-- 
Christopher J. Fearnley|Linux/Internet Consulting
[EMAIL PROTECTED], [EMAIL PROTECTED]   |UNIX SIG Leader at PACS
http://www.netaxs.com/~cjf |(Philadelphia Area Computer Society)
ftp://ftp.netaxs.com/people/cjf|Design Science Revolutionary
"Dare to be Naive" -- Bucky Fuller |Explorer in Universe

Re: dpkg changes and queries - the answers to your questions

[Dale Scheetz]

On Tue, 24 Sep 1996, Heiko Schlittermann wrote:

> Dale Scheetz wrote:
> : 
> : On Mon, 23 Sep 1996, Heiko Schlittermann wrote:
> : > 
> : > withecho $rootcommand "debian/rules clean"
> : > If I did no mistakes it worked for me.
> : 
> : When I installed Michael's "quote patch" the next time I tried to run
> : dpkg-buildpackage I got was informed that debian/rules did not exist.
> : Removing the quotes got it working again.
> 
> Near the start of dpkg-buildpackage there's a line
> 
> rootcommand=''
> 
> change it to
> 
> rootcommand='eval'
> 
> and put in Michels quoting.
> 
> This _should_ work.
> 
I can certainly do this. The question is: What purpose is served by the
quotes? It works fine for me without them.

Thanks,

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 --

Bug#4573: mc xterm problems

[Volker Ossenkopf]

Package: mc
Version: 3.2.1-1

Since the mouse support in mc does not work with the terminfos for
xterm and xterm-color from the Debian distribution nor with
those for ansi_xterm, the installation script should immediately
install the xterm.ti which is included.

The xterm.ti does not give the correct behaviour for all these
three xterms. After some mc operations the xterm gets slightly
messed up. The responsible commands are the absolute cursor
motions hpa and vpa. But removing them from xterm.ti all works
fine. 

Best wishes


  Volker Ossenkopf,  E-mail: [EMAIL PROTECTED]

  Astrophysikalisches Institut und\\///
   Universitaets-Sternwarte Jena ( . . ) Tel.: 03641/630324
--oOo--(_)--oOo-

Bug#4572: ucb-mpeg_play is still a.out

[Volker Ossenkopf]

Package: ucbmpeg
Version: 1r2-2

The binary is still a.out. The sources can be recompiled without
problems.


  Volker Ossenkopf,  E-mail: [EMAIL PROTECTED]

  Astrophysikalisches Institut und\\///
   Universitaets-Sternwarte Jena ( . . ) Tel.: 03641/630324
--oOo--(_)--oOo-

Bug#4571: xview misses link

[Volker Ossenkopf]

Package: xview
Version: 3.2p1.2-1

The installation script does not set links from
libxview.so.3.2 to libxview.so and the same for
libolgx.so. The recent gcc2.7.2 however requires
these links set. Otherwise programs will be linked
statically on compile time.


  Volker Ossenkopf,  E-mail: [EMAIL PROTECTED]

  Astrophysikalisches Institut und\\///
   Universitaets-Sternwarte Jena ( . . ) Tel.: 03641/630324
--oOo--(_)--oOo-

Bug#4561: dpkg-genchanges puts bad Maintainer: in changes file

[Heiko Schlittermann]

Yves Arrouye wrote:
: 
:I think the solution is in dpkg-genchanges(1):
: -Dfield=value
:Override or add an output control file field.  This
:option   is   understood   by   dpkg-source,  dpkg-
:gencontrol and dpkg-genchanges.
: 
: Or -m"My Name <[EMAIL PROTECTED]>". Yes. But it would be nice to get it
: from the control file anyway.

Hm -- I don't understand ... :-/ what's wrong?

If I  (ok, using the unrelesed (yet) dpkg-1.4.0.1)

dpkg-buildpackge -m'me and you'

'me and you' is listed as the maintainer in the .changes file.
Otherwise the name and address from the most recent entry in the
debian/changelog file.

The .deb files nevertheless carry the maintainer from the debian/control
file.

(Think it would be nice to have something like:

Maintainer: 
Changes-By: 

both in .deb and .changes, perhaps in .dsc as well (for debian only
packages)


Heiko
--
email : [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
pgp   : A1 7D F6 7B 69 73 48 35  E1 DE 21 A7 A8 9A 77 92 
finger: [EMAIL PROTECTED] [EMAIL PROTECTED]

Bug#4570: xview-clients without owplaces

[Volker Ossenkopf]

Package: xview-clients
Version: 3.2p1.2-1

The "Save workspace" internal command of olwm requires
olwplaces (which often uses xtoolwait). olwplaces and
xtoolwait are not available in the package.

The installation script does not add olwm to
/etc/X11/window-managers.


  Volker Ossenkopf,  E-mail: [EMAIL PROTECTED]

  Astrophysikalisches Institut und\\///
   Universitaets-Sternwarte Jena ( . . ) Tel.: 03641/630324
--oOo--(_)--oOo-

Bug#4569: a2gs binary still a.out

[Volker Ossenkopf]

Package: a2gs
Version: 1.0-4

The binary is still a.out.


  Volker Ossenkopf,  E-mail: [EMAIL PROTECTED]

  Astrophysikalisches Institut und\\///
   Universitaets-Sternwarte Jena ( . . ) Tel.: 03641/630324
--oOo--(_)--oOo-

Re: dpkg changes and queries - the answers to your questions

[Heiko Schlittermann]

Dale Scheetz wrote:
: 
: On Mon, 23 Sep 1996, Heiko Schlittermann wrote:
: > 
: > withecho $rootcommand "debian/rules clean"
: > If I did no mistakes it worked for me.
: 
: When I installed Michael's "quote patch" the next time I tried to run
: dpkg-buildpackage I got was informed that debian/rules did not exist.
: Removing the quotes got it working again.

Near the start of dpkg-buildpackage there's a line

rootcommand=''

change it to

rootcommand='eval'

and put in Michels quoting.

This _should_ work.


Heiko
--
email : [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
pgp   : A1 7D F6 7B 69 73 48 35  E1 DE 21 A7 A8 9A 77 92 
finger: [EMAIL PROTECTED] [EMAIL PROTECTED]

Bug#4568: a2ps binary still a.out

[Volker Ossenkopf]

Package: a2ps
Version: 4.3-1

The binary is still a.out. No source available.


  Volker Ossenkopf,  E-mail: [EMAIL PROTECTED]

  Astrophysikalisches Institut und\\///
   Universitaets-Sternwarte Jena ( . . ) Tel.: 03641/630324
--oOo--(_)--oOo-

Bug#4567: gpm upgrade from 1.06-3 to 1.10-1 is not smooth

[Chris Fearnley]

Package: gpm
Version: 1.10-1

I tried installing libgpm1_1.10-1.deb and gpm_1.10-1.deb in that order.
The library installed just perfectly, but when gpm's prerm tried to
"/etc/init.d/gpm stop" ... it hung. The init.d script calls gpm -k which
may have gotten confused by the new library?? I was able to kill the
process manually and re-install. But I couldn't find a way for dpkg to
resolve the problem.

-- 
Christopher J. Fearnley|Linux/Internet Consulting
[EMAIL PROTECTED] |UNIX SIG Leader at PACS
http://www.netaxs.com/~cjf |(Philadelphia Area Computer Society)
ftp://ftp.netaxs.com/people/cjf|Design Science Revolutionary
"Dare to be Naive" -- Bucky Fuller |Explorer in Universe

Bug#4566: Babel does not configure

[Christoph Lameter]

Package: babel
Version: 3.6-4

Installation result of babel:
waterf:/home/clameter# dpkg --configure --pending
Setting up babel (3.6-4) ...
Building new format(s) with babel support using install-fmt-base(8)
Rebuilding `latex' format ... done
Rebuilding `tex' format ... kpathsea: Running MakeTeXTFM manfnt.tfm 
Running MakeTeXPK manfnt.tfm
mf \mode:=nullmode; mag:=1; scrollmode; input manfnt \ ...=nullmode; mag:=1; scrollmode; input manfnt
  
Please type another input file name: 
! Emergency stop.
<*> ...=nullmode; mag:=1; scrollmode; input manfnt
  
Transcript written on mfput.log.
Metafont failed for some reason on manfnt.tfm
kpathsea: Appending font creation commands to missfont.log.

I have reported this a while ago. It fills up the harddrive nicely.

{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}{}
{}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 

Re: dpkg changes and queries - the answers to your questions

[Dale Scheetz]

On Mon, 23 Sep 1996, Heiko Schlittermann wrote:

> : 3. Do NOT use Michael Meskes's patch to quote the argument to
> : $rootcommand in dpkg-buildpackage.  Instead, RTFM.  Please DO NOT
> : release a dpkg with Michael Meskes's patch.  Thank you.
> 
> Hmm, I've changed it.  The default root command is now `eval',
> the lines are now read as:
> 
> withecho $rootcommand "debian/rules clean"
> 
> If I did no mistakes it worked for me.

When I installed Michael's "quote patch" the next time I tried to run
dpkg-buildpackage I got was informed that debian/rules did not exist.
Removing the quotes got it working again.

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: where are guidelines?

[Susan G. Kleinmann]

Hi Joost --

I think there may be 2 reasons why you can't find the package containing 
the guidelines:
1.  "Guidelines" doesn't exist any more.  It has evolved into the policy manual
and the programmer manual, and 
2.  The P&P manuals aren't in a package (that I could find).  They are 
uploaded seperately into doc/package-developer; the newest ones are in 
/private/project/Incoming.  They are called policy.ps.gz, policy.html.gz, 
programmer.ps.gz, and programmer.html.gz.

HTH,
Susan

Bug#4434: lynx 2.6

[Mark Purcell]

On Tue, 24 Sep 1996, Andrew Howell wrote:

> U slightly confused now :) Why did you report this as a bug?
> Also this got mailed to me, and I'm the old maintainer.

I was following up to Bug#4434, where Marek Michalkiewicz
<[EMAIL PROTECTED]> reported that he had packaged up
lynx-2.6 and made it available for ftp.

I also suggested that Marek may like to take the package over as
maintainer and that he should submit it to /Incoming on master.debian.org
as an interium update.

Mark

Bug#4434: lynx 2.6

[Andrew Howell]

[EMAIL PROTECTED] writes:
> 
> 
> Thanks for making your version of lynx-2.6 available it certainly has some 
> nice
> features.
> 
> I saw in the last FAQ that the current lynx maintainer is looking for a
> person to take over maintenance of the package.  Are you interested?
> 
> If not could I ask that you submit your update to /Incoming as an interium
> release.  Squid was upgraded this way and this was also appreciated.
> 
> Thanks for your efforts.

U slightly confused now :) Why did you report this as a bug?
Also this got mailed to me, and I'm the old maintainer.

Andrew

-- 
Of course...lager...the only thing that can kill a vindaloo.
 -- Lister, fighting the vindaloo monster in Red Dwarf `DNA'

Andrew Howell [EMAIL PROTECTED]
Perth, Western Australia [EMAIL PROTECTED] [EMAIL PROTECTED]

Bug#4434: lynx 2.6

[purcell]

Thanks for making your version of lynx-2.6 available it certainly has some nice
features.

I saw in the last FAQ that the current lynx maintainer is looking for a
person to take over maintenance of the package.  Are you interested?

If not could I ask that you submit your update to /Incoming as an interium
release.  Squid was upgraded this way and this was also appreciated.

Thanks for your efforts.
Mark

Re: where are guidelines?

[Dale Scheetz]

On Mon, 23 Sep 1996, joost witteveen wrote:

> I believe in the good old days, the guidelines were in
> dpgk. But I just installed dpkg-1.3-?, and they have gone.
> 
> (So, I installed as many related packages as I could find from
> a search in the Packages file, but to no avail)
> 
>  $ find /usr -name "*guideli*"
> find: ./doc/examples/modules/GOODIES: Permission denied

Everything you are looking for will be found in /usr/doc/dpkg in two html
documents: policy and programmer. You should probably start with the
policy manual as it has the conversion information you are looking for.

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: where are guidelines?

[Syrus Nemat-Nasser]

On Mon, 23 Sep 1996, joost witteveen wrote:

> I believe in the good old days, the guidelines were in
> dpgk. But I just installed dpkg-1.3-?, and they have gone.

There is now a dpkg-dev package with the stuff needed for
developers.  "policy" and "programmer" manuals are available.

Syrus.



--
Syrus Nemat-Nasser <[EMAIL PROTECTED]>UCSD Physics Dept.

Re: dpkg changes and queries - the answers to your questions

[Heiko Schlittermann]

Ian Jackson wrote:
: 
: 1. Yes, dpkg-source doesn't work with hardlinks.  I think that
: hardlinks in source packages are evil.  Perhaps they can be made to
: work - Heiko's patch seems reasonable (until someone wants a filename
: containing the string ` link to ').  However, I'd recommend just

hmm ... but this seems not too often, at least less often then
the occurence of real hard links.

: removing the hardlink and replacing it with a symlink (or just
: deleting one name).  There is no problem with doing that, and it is
: fine wrt our policy about original sources.

The dpkg-source -b should scan for hardlinks and convert 'em.


: 2. I don't know what to do about tar doing nasty things to filenames.
: If this is a design feature of all tars then dpkg-source should be
: changed to unmangle the filename on output from tar.

I've done it.  

cpio returns iso conformant file names (e.g. with real umlauts), tar
doesn't -- it converts such umlauts to their octal representation.

A line 

/\\/ and eval "\$_ = \"$_\"";

does the job on the mangeled (?) names from tar's output.


: 3. Do NOT use Michael Meskes's patch to quote the argument to
: $rootcommand in dpkg-buildpackage.  Instead, RTFM.  Please DO NOT
: release a dpkg with Michael Meskes's patch.  Thank you.

Hmm, I've changed it.  The default root command is now `eval',
the lines are now read as:

withecho $rootcommand "debian/rules clean"

If I did no mistakes it worked for me.
(I've running a patched su (using SUPASS env., similar to PGPPASS).
(sudo needs absolute path names, super -- I don't know)

: 4. dpkg-name belongs in the dpkg-dev package.  If anyone is releasing
: a new dpkg they should move it.  See debian/rules.

Done.

: 6. Karl Sackett's fix for an error message typo (Bug 4524) is good.
: Heiko, please close the report if you like but definitely mail me the
: patch.

Ok, I'll mail you a diff 1.4.0.1 against 1.4.0, including this
patch too.

: 10. Re dpkg-buildpackage and the failure to build due to permissions
: (bug 4525).  I'm inclined to say "don't build with a umask of 077
: then".  I don't think that all packages' debian/rules should be
: responsible for fixing the permissions of the created files.

The only files created by the debian tools (dpkg-*) are debian/files
and debian/substvars.  I've changed dpkg-* so now 
these files are chowned to getlogin().getgrnam(getlogin()).  I believe,
it's the most approbiate setting. (???)

: 12. llucius posts a patch to dpkg-buildpackage to make it pass -v, -m
: and -C to dpkg-genchanges.  His patch is not in line with my intent,
: and won't work when the arguments have spaces.  The call to
: dpkg-genchanges needs to read
:  withecho dpkg-genchanges $sourcestyle "$@" >"$chg"
: instead of the thing in his patch.  (Bug #4554.)

I'll have a look at it.

: I hope this is enough to keep you going for another week :-).

 :-) not yet.


Heiko
--
email : [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
pgp   : A1 7D F6 7B 69 73 48 35  E1 DE 21 A7 A8 9A 77 92 
finger: [EMAIL PROTECTED] [EMAIL PROTECTED]

Re: proposal: pseudo source packages

[Heiko Schlittermann]

David Frey wrote:
: 
: [about xforms_0.81...]
: >xforms_0.81.tar.gz
: >xforms_0.81.dsc
: >
: >For the first 4 files it's ok. But the latter? Would somebody mind,
: >if I'd remove the debian/ from xforms_0.81.tar.gz and create a
: >xforms_0.81.orig.tar.gz and then the diffs for the debian changes
: >only?
:

: I'm really against the proposal of pseudo-source packages. If you 
: don't have the source, it's useless to upload an essentially empty
: *.orig.tar.gz 

Hm .., .orig.tar.gz isn't really empty.  It would contain the unmodified
binaries (i386, m68k) and _no_ debian files.

And I until a new upstream version of xforms will be available, I expect
that all changes will be only done regarding the debian files.

We could source define as `the most original available set of files' ...

: and confuses only potential downloaders. The debian-diff is enough; 
: another possibility would be to write an xforms-install package as it was 
No, since xforms doesnt seem to have the distribution restrictions as
netscape.

: done with netscape. Then, the people with non-intel architectures
: would know that the package is useless for them (at the moment) and
: wouldn't need to download

Perhaps the .dsc file could include a hint about this `pseudo'-package.
And we'd need debian versioning of the source files.

(Latter would be nice for others too -- what if I made a mistake
in putting together the package-x.y.orig.tar.gz file?  How can I tell
the potential downloader about a new version of my .orig.tar.gz?)

Heiko
--
email : [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED]
pgp   : A1 7D F6 7B 69 73 48 35  E1 DE 21 A7 A8 9A 77 92 
finger: [EMAIL PROTECTED] [EMAIL PROTECTED]

Bug#4551: xautolock and xtrlock conflict on screensaver

[Emilio Lopes]

> "DH" == Dave Holland <[EMAIL PROTECTED]> wrote:

DH> xautolock should check to see if the display is already locked
DH> before attempting to run the locker program.

No, this is what xlock should do. xautolock, despite of its name, does
not know it will run a lock program. xautolock is a generic program.

Ciao, Emilio.

-- 
 Emilio C. Lopes 
   Instituto de Fisica da Universidade de Sao Paulo
 Caixa Postal 66318, 05389-970 Sao Paulo - SP, BRAZIL
  Phone: (+55) (11) 818-6724 (Voice) / 818-6715 (Fax)

Re: ldso breaks a.out?

[David Engel]

Mark Eichin writes:
> As I sent to Dale Scheetz earlier, 
> 
> execve("/d1/eichin/bin/pgp.aout", ["/usr/bin/uustat"], [/* 17 vars */])
> = 0
> uselib("/lib/ld.so")= -1 ENOEXEC (Exec format error)
> (followed by the write() of the message...)
> 
> We concluded that it was simply time to switch to a 2.0.x kernel
> (after some discussion about which values of "x" were stable...)

Which 1.x.x version were you using?  It probably had a broken
do_load_elf_library() in fs/binfmt_elf.c.

David
-- 
David EngelOptical Data Systems, Inc.
[EMAIL PROTECTED]  1101 E. Arapaho Road
(214) 234-6400 Richardson, TX  75081

Re: ae as default editor?

[Guy Maor]

On Mon, 23 Sep 1996, James A. Robinson wrote:

> Well, I imagine if one takes that idea further, one would say that ae
> is the editor on the base disk because it is easier to use.

Plus it's very small.

> I think the real reason goes back to the fact that experienced users
> can set their EDITOR variable, or handle ae.

That's why I made ae the default editor for vipw.  That and the fact
that otherwise, vipw on the base disks won't work.

And for those of you who think I should rename vipw to aepw or editpw
or emacspw or that I should look at the first strlen()-2 letters and
try to call that, I saw: Pbtl!


Guy

Re: manpages depends on man?

[Fabrizio Polacco]

David Frey wrote:
> 
> >And also, the /var/catman hierarchy cannot be purged although it is
> >used only by man, because of the indexes and the subdirectories that 
> >are built in it after the installation. 
> >How can I tell to the man package that these are safe to be removed?
>
> Each package should purge it's own directories. So man has nothing to
> do with it. You could consider to run a mandb in the postrm script.

The situation is complex: /var/catman is in the "man" package, but other
packages add their subdirs and also mandb builds indexes thar aren't
listed in the man package.
If a user decide to purge "man" because he uses only xman or something
new that will come, dpkg complains that /var/catman is not empty and
doesn't remove the hierarchy.
The user has no reason to purge the manpages, because he needs them.

removing the /var/catman from man's postrm can solve this, but I think
it will harm manpages that lists those dirs as installed.

What if I build the /var/catman subdirs in the postinst of manpages 
(if man is installed) and remove all the /var/catman hierarchy in 
prerm of man?

> 
> Only man uses the catman mechanism. My xman insists on reformatting
> the manpages, even if there are cached catman pages around...
> 
> >The xman program that comes in xcontrib doesn't understand locales.
> >Should I raise a bug?
>
> Unsure about that. Yes?

Maybe it's a configuration problem. What could I do, installing
manpages, to let "automatically" xman find the pages in the new subdirs?


Fabrizio
-- 
+-+
| e-mail: [EMAIL PROTECTED][EMAIL PROTECTED] |
| http://megabaud.fi/~fpolacco/   Join the UKI Linux Project! |
| fingerprint 70 1A 72 2D 2B C8 A5 63 7A C2 CC E0 2A 54 AE DA |
| finger: [EMAIL PROTECTED][EMAIL PROTECTED]  |
+-+

where are guidelines?

[joost witteveen]

I believe in the good old days, the guidelines were in
dpgk. But I just installed dpkg-1.3-?, and they have gone.

(So, I installed as many related packages as I could find from
a search in the Packages file, but to no avail)

 $ find /usr -name "*guideli*"
find: ./doc/examples/modules/GOODIES: Permission denied

Could somebody please tell me what package I need to install to
get them back? (Yes, I know of the dpkg -S option, but that doesn't
help if the right package isn't installed to begin with)

Also, I was hoping I could find the guidelines as to how to update
old packages to the new source format -- but I must be overlooking
something very obvious (I'm sure), as I cannot find this eighter.


Thanks a lot,

-- 
joost witteveen
[EMAIL PROTECTED]
  [EMAIL PROTECTED]
--
Use Debian/GNU Linux!