Re: Discriminating between install after purge and install from state rc?

Adeodato Simó <[EMAIL PROTECTED]> wrote: > So I can be wrong, but for me, the classification needed in postinst > would be only two-way, not three way. Agreed. > Please let me know if three-way > classification can be relevant under some circumstances. Just to > mention it for complet

Discriminating between install after purge and install from state rc?

Hi, it seems I am currently having a blackout. How can I find out in postinst whether the package previously had been in state "rc", or was purged or never installed? It seems every maintainer script that handles a configuration file must check that - otherwise it would violate policy's "must pr

Re: RFC: cycle (calendar program for women, written in python)

Miriam Ruiz <[EMAIL PROTECTED]> wrote: > 1) I'm putting python files in /usr/share/cycle/, is > this right or should they go into /usr/lib/cycle/ or > something like that? Have you read the python policy at file:///usr/share/doc/python/python-policy.html/index.html I didn't read it, only shortl

Re: reassigning bugs

martin f krafft <[EMAIL PROTECTED]> wrote: > also sprach Frank Küster <[EMAIL PROTECTED]> [2005.03.30.1413 +0200]: >> I usually find that it is reversed, and that all the mails in >> which I reassign a bug to an other package gets to _me_, not the >> new maintainer. > > They are sent to both, you,

Re: reassigning bugs

Jeroen van Wolffelaar <[EMAIL PROTECTED]> wrote: > On Wed, Mar 30, 2005 at 01:46:02PM +0200, Gaudenz Steinlin wrote: >> On Thu, Mar 24, 2005 at 11:41:32PM +0100, Jeroen van Wolffelaar wrote: >> > reassign libgtk2.0-0, sawfish >> > thanks >> >> What's this actually supposed to do? [...] >> cl

Re: reassigning bugs

Jeroen van Wolffelaar <[EMAIL PROTECTED]> wrote: > - No need to cc [EMAIL PROTECTED], since typically the mail to > the bug number will be processed after control@ stuff gets processed > (and so, the message will already go to the correct maintainers). And > even if it is not so (the order o

Re: public domain

Carlos Parra <[EMAIL PROTECTED]> wrote: > Hello, > I'd like to package a program that's licensed under "public domain". > I've been talking with the autor and says that he likes also BSD-style > license... > > The change of license is necesary to get into the main archive, isnt > it? As far a

Re: help with package restricted to specific arches

Jeroen van Wolffelaar <[EMAIL PROTECTED]> wrote: > On Wed, Mar 23, 2005 at 10:33:11AM +0100, Frank K?ster wrote: >> "Kevin B. McCarty" <[EMAIL PROTECTED]> wrote: >> >> > >> > http://www.wolffelaar.nl/~jeroen/P-a-s-HOWTO.txt >> > >> > The P-a-s maintainers mentioned in that file include LaMont Jon

Re: help with package restricted to specific arches

Richard C Bilson <[EMAIL PROTECTED]> wrote: > It would be nice if this tidbit (or at least a pointer thereto) could > make its way into some official piece of documentation. I'm writing a patch for developers reference, based on Jeroen's text. Regards, Frank -- Frank Küster Inst. f. Biochemie d

Re: help with package restricted to specific arches

"Kevin B. McCarty" <[EMAIL PROTECTED]> wrote: > > http://www.wolffelaar.nl/~jeroen/P-a-s-HOWTO.txt > > The P-a-s maintainers mentioned in that file include LaMont Jones > <[EMAIL PROTECTED]> and James Troup <[EMAIL PROTECTED]> among others. Is there a role account for that, and what's their name?

Re: About control files

Lucas Wall <[EMAIL PROTECTED]> schrieb: > On 03/17/2005 12:59 PM, Lucas Di Pentima wrote: >> Hello! >> I'm reading the Policy Manual so I can correct any errors I have in >> my >> control file before sending my program to Lucas Wall, that had accepted >> to be my sponsor. >> Reading this URL: >> h

Re: Open ITP without apparent work on it

Martin Michlmayr <[EMAIL PROTECTED]> schrieb: > * Christoph Berg <[EMAIL PROTECTED]> [2005-03-16 14:41]: >> > Isn't there an "owner" tag for WNPP bugs? Then Shachar could set >> > himself as the owner. >> >> This won't get you the messages forwarded either. > > Of course it will. The owner rece

Re: Open ITP without apparent work on it

Christoph Berg <[EMAIL PROTECTED]> schrieb: > Re: Matthew Palmer in <[EMAIL PROTECTED]> >> Make a note in the ITP that you are keenly interested in seeing Open Xchange >> in Debian, and offer to help the initial ITP filer in any way, noting that >> if you don't hear anything, you'll commence packa

Re: Use "Replaces"?

Thomas Hood <[EMAIL PROTECTED]> schrieb: > Original package is foo 1.0. This is split up into two packages: foo > 2.0, bar 2.0. > > Package: bar > Version: 2.0 > Conflicts: foo (<< 2.0) > > Should bar also have this?: > > Replaces: foo (<< 2.0) Only if it replaces *files* in foo

Re: build failure on sparc

Tommaso Moroni <[EMAIL PROTECTED]> schrieb: > On Mon, Mar 14, 2005 at 02:20:42PM +, Steve Kemp wrote: >> On Mon, Mar 14, 2005 at 03:14:56PM +0100, Tommaso Moroni wrote: >> >> > checking for vsnprintf... yes >> > checking for snprintf... yes >> > checking for X... configure: error: Can't find

Re: re generate a "rules" file

"Rakotomandimby (R12y) Mihamina" <[EMAIL PROTECTED]> schrieb: > Hello. > I did not make a backup copy of my "rules" file, and I edited it like a > pig. > I would like to do it again but with a clean "rules" file. > I would like to re-generate the "rules" file. How to? Next time, use a version con

Re: What does RFS mean?

Hugo Vanwoerkom <[EMAIL PROTECTED]> schrieb: > Hi Mentors! > > Millions of hits for RFS. But what does it stand for? http://women.alioth.debian.org/dicts/dward.fi.html#bae1e1d3d40573127e9ee0480caf1283d6 Next question: What is sponsorship? http://people.debian.org/~mpalmer/debian-mentors_FAQ.h

Re: Question about the executable filename

"Nelson A. de Oliveira" <[EMAIL PROTECTED]> schrieb: > Hi mentors! > > If one program has it's binary name like this "WMAnsiEd", with capital > letters. Do I have to install it to /usr/bin/WMAnsiEd or > /usr/bin/wmansied ? I can't see a reason why a binary name could not contain capital letters.

Re: Help about license

"Nelson A. de Oliveira" <[EMAIL PROTECTED]> schrieb: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi mentors > > I need one help. > When there is a program that only says "(c) GNU Copyleft", what do I put > on debian/copyright file, at section "License:"? > GNU Copyleft could be considere

Re: common function handling in maintainer scripts

Stephen Gran <[EMAIL PROTECTED]> wrote: > This one time, at band camp, Frank Küster said: >> For the teTeX-3.0 packages, I have taken a different approach, inspired >> by Davide Salvetti's nice auctex package: All the maintainer scripts, >> and even debian/rules, are created by e-Perl from their c

Re: Need advice wrt #295306

Adeodato Simó <[EMAIL PROTECTED]> wrote: > * Pierre Habouzit [Fri, 25 Feb 2005 14:50:54 +0100]: >> - : this is really not trivial : inetd.conf is sorted by categories, >> and it will be really difficult to put the entries at the right >> place in the postinst > > In fact, is not ve

Re: Need advice wrt #295306

Pierre Habouzit <[EMAIL PROTECTED]> wrotee: > The only way is to do some hackish things in the since > it's the only script that will be called before the buggy > > until here, it's OK. but I readlly dunno which hack I have to implement > int the preinst. I have (at least) two choices, but I d

Re: common function handling in maintainer scripts

Stephen Gran <[EMAIL PROTECTED]> schrieb: > Hello all, > > I have a source package that generates multiple binary packages. > Since the packages are similar in a lot of ways (config file structure, > handling of config files, etc), I have a lot of functions that are the > same in several maintaine

Re: RFS: ITA: tex4ht -- LaTeX and TeX for Hypertext (HTML)

Kapil Hari Paranjape <[EMAIL PROTECTED]> schrieb: > Dear Frank, > > Thanks for the detailed checks. > > I think I have fixed all the bugs you mentioned in the newer version > (20050216.2023-1.1). > > On Fri, Feb 18, 2005 at 03:55:08PM +0100, Frank Küster wrote: >> - is #219482 fixed? > > Unfortun

Re: RFS: ITA: tex4ht -- LaTeX and TeX for Hypertext (HTML)

Kapil Hari Paranjape <[EMAIL PROTECTED]> schrieb: > Dear Frank, > > On Fri, Feb 18, 2005 at 12:39:46PM +0100, Frank Küster wrote: >> Kapil Hari Paranjape <[EMAIL PROTECTED]> schrieb: >> > I have put up the promised newer version. The versioning scheme has >> > reverted to MMDD.HHMM for the pr

Re: RFS: ITA: tex4ht -- LaTeX and TeX for Hypertext (HTML)

Kapil Hari Paranjape <[EMAIL PROTECTED]> wrote: > 4. Copyright question: Upstream has added his LPPL copyright >to /etc/tex4ht/tex4ht.env. I am distributing a modified version. What >do I need to do in order to comply with LPPL? Or is it best to write >a new version entirely? Read the

Re: RFS: ITA: tex4ht -- LaTeX and TeX for Hypertext (HTML)

Justin Pryzby <[EMAIL PROTECTED]> wrote: > On Fri, Feb 18, 2005 at 01:04:51PM +0530, Kapil Hari Paranjape wrote: >> 1. Versioning while testing: How does one give version numbers while >>testing the package? These versions will probably not be >>put on the main archive at any time. On the

Re: RFS: ITA: tex4ht -- LaTeX and TeX for Hypertext (HTML)

Kapil Hari Paranjape <[EMAIL PROTECTED]> schrieb: > Hello, > > On Fri, Feb 18, 2005 at 01:04:51PM +0530, Kapil Hari Paranjape wrote: >> Thanks to Frank and Vassilii for all the comments. I have made changes and >> will soon put up newer versions at the following location: > > http://www.imsc

Re: RFS: ITA: tex4ht -- LaTeX and TeX for Hypertext (HTML)

Kapil Hari Paranjape <[EMAIL PROTECTED]> schrieb: > Dear Frank, > > Thanks for the detailed response. This mail is a bit long please bear with > me. > > On Thu, Feb 17, 2005 at 12:20:32PM +0100, Frank Küster wrote: >> I think you should include 1.3a and put a remark into the file >> explaining why

Re: RFS: ITA: tex4ht -- LaTeX and TeX for Hypertext (HTML)

Frank Küster <[EMAIL PROTECTED]> schrieb: > Kapil Hari Paranjape <[EMAIL PROTECTED]> wrote: > >> Hello, >> >> I am looking for a sponsor who will help me to adopt tex4ht. > > Somehow off this list I got the URL where one can download the packages > you prepared. Which is http://www.imsc.res.in

Re: RFS: ITA: tex4ht -- LaTeX and TeX for Hypertext (HTML)

Kapil Hari Paranjape <[EMAIL PROTECTED]> wrote: > Hello, > > I am looking for a sponsor who will help me to adopt tex4ht. Somehow off this list I got the URL where one can download the packages you prepared. I started looking at them, here are some remarks. Please reply on the list. * debian/co

Re: How-do-I make a non-native Debian package?

Kees Leune <[EMAIL PROTECTED]> schrieb: > On Tue, 15 Feb 2005 22:59:29 -0500, William Ballard > <[EMAIL PROTECTED]> wrote: >> On Tue, Feb 15, 2005 at 01:23:06AM -0300, Lucas Wall wrote: >> > - make dist >> > - copy the tar.gz to a temp dir with the appropiate .orig Debian name. >> > - unpack the t

Re: RFS: ITA: tex4ht -- LaTeX and TeX for Hypertext (HTML)

Kapil Hari Paranjape <[EMAIL PROTECTED]> wrote: > Hello, > > I am looking for a sponsor who will help me to adopt tex4ht. Go ahead. I am generally interested, others might be interested, too. But we will not be able to promise anything before you have shown us your attempts to fix some of the bug

Re: How-do-I make a non-native Debian package?

William Ballard <[EMAIL PROTECTED]> wrote: > I wrote my own app and it is debianized already, the way > mplayer already is. But I mistakenly made it a "native" Debian > package when it is really a tarball and/or a debian package. > > There will *never* be a "diff" between "debian" and "upstream"

Re: pdf files in upstream tarball and -doc package

Miriam Ruiz <[EMAIL PROTECTED]> wrote: > So if you only have PDF file, you wouldn't include in > the package, is it that? Even when it is the only doc > available and it is free to be modified or > redistributed? Hm. In fact I *cannot* include it because it fails Clause 2 of the DFSG. But if it m

Re: pdf files in upstream tarball and -doc package

martin f krafft <[EMAIL PROTECTED]> schrieb: > also sprach Frank Küster <[EMAIL PROTECTED]> [2005.02.11.1332 +0100]: >> But you cannot include pdf files for which no source is included, >> or only Micro$oft .doc files, in a Debian package: We need the >> source code, and pdf, even if not compresse

Re: pdf files in upstream tarball and -doc package

Miriam Ruiz <[EMAIL PROTECTED]> schrieb: > --- Justin Pryzby > <[EMAIL PROTECTED]> escribió: > >> PDF can be trojaned, so you should at least >> *provide* a way to >> generate them from their sources, even if that >> makefile rule is not >> called by default, and the additional >> build-dependen

Re: Versioning prereleases

martin f krafft <[EMAIL PROTECTED]> schrieb: > I use > > 5.0-0+5.0pre1+2 > A B C D > > with A being the main version, B the debian release (0 < 1), C the > real version, and D the debian release of the pre-release. > > I think this should work fine. Except that, as far as I can see, i

Re: freeswan transition package

Rene Mayrhofer <[EMAIL PROTECTED]> schrieb: > I am seeking advice for creating a transition package for freeswan, which > should: > - install the openswan package > - use the config files from the old freeswan package for openswan > - use the debconf answers of the old freeswan package for opensw

Re: Preserving admin runlevel modifications on upgrade?

Maximilian Wilhelm <[EMAIL PROTECTED]> schrieb: > Am Montag, den 7. Februar hub Frank Küster folgendes in die Tasten: > >> Christian Hammers <[EMAIL PROTECTED]> schrieb: > >> > AFAIK the standard way of registering daemons is to run >> > update-rc.d foobar defaults >> > in the postinst script. T

Re: Preserving admin runlevel modifications on upgrade?

Christian Hammers <[EMAIL PROTECTED]> schrieb: > Hello > > [please Cc me, I'm not subscribed -thanks] > > AFAIK the standard way of registering daemons is to run > update-rc.d foobar defaults > in the postinst script. This sadly resets any changes the administrator > made on every upgrade. Only

Re: encoding of debian files debian/*

Jeroen van Wolffelaar <[EMAIL PROTECTED]> schrieb: > On Tue, Feb 01, 2005 at 07:27:53PM +0100, Daniel Leidert wrote: >> I have a question about the encoding of the files in the Debian >> subdirectory. AFAIK it's recommended to use ASCII only in debian/control >> (AFAIK the policy does not contain

Re: singular they

Cameron Patrick <[EMAIL PROTECTED]> schrieb: > Frank Küster wrote: > >> Just in case anybody is also reading -project... >> >> >> Blars Blarson <[EMAIL PROTECTED]> wrote: >> >> > I do think that it should be objectivly compared with vacation before >> > Debian decides to add it to to their arch

Re: [Pkg-alsa-devel] RFS: alsa-tools

Walter Landry <[EMAIL PROTECTED]> schrieb: > "Marco d'Itri" <[EMAIL PROTECTED]> wrote: >> [EMAIL PROTECTED] wrote: >> >> >Do we have to split the alsa-tools source into two packages, one free >> >and one non-free/contrib? It will make it a bit harder. >> No. > > Unfortunately, that is not the ca

singular they (was: RFS(2): autoreply - A safe, rate-limited auto-responder)

Hi, Just in case anybody is also reading -project... Blars Blarson <[EMAIL PROTECTED]> wrote: > I do think that it should be objectivly compared with vacation before > Debian decides to add it to to their archives. ^ Regards, Frank -- Frank Küster Inst. f

Re: accidently built native package

Marco Herrn <[EMAIL PROTECTED]> schrieb: > Hi, > > I have packaged hatari into a .deb file. That was in version 0.50 > and lead to no problems. Now a new upstream version (0.60) is out and > I wanted to package that. So I unpacked the new tarball, renamed the > tarball to hatari-0.60.orig.tar.gz a

Re: RFC and RFS: latex-svninfo

Adrian von Bidder <[EMAIL PROTECTED]> schrieb: > Frank, would you be willing to sponsor this package for me, since you > already reviewed it? Yes, I'll take it. Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer

Re: RFC and RFS: latex-svninfo

Adrian 'Dagurashibanipal' von Bidder <[EMAIL PROTECTED]> schrieb: > On Thursday 13 January 2005 10.15, Frank Küster wrote: >> But you should also install the pdf or >> dvi files, and put them or symlinks in a place where texdoc can find >> them (i.e., /usr/share/doc/texmf/latex/svninfo) > > Ok. /

Re: best way to announce important changes

Christoph Wegscheider <[EMAIL PROTECTED]> wrote: > Hi, > I maintain the rsnapshot package, which is a perl script for backups. > > In the next upstream version there will be changes which WILL break > almost all setups. One has to modify the conf file to avoid that. Is it a conffile or just a co

Re: new maintainership

Nico Golde <[EMAIL PROTECTED]> schrieb: > hi, > i hope i can begin my new maintainership in the next time. > i have one question before i start. > the questions of the application manager are in english. > > if it is a german am, is it allowed to answer in german or > is it necessary to answer in

Re: RFC and RFS: latex-svninfo

Frank Küster <[EMAIL PROTECTED]> wrote: > , > | %% Any modified versions of this file must be renamed > | %% with new filenames distinct from svninfo.cfg. > ` [...] > Furthermore, this sentense renders the package non-free. Formally, this is not correct, as it seems - the LPPL 1.3 only

Re: RFC and RFS: latex-svninfo

Frank Küster <[EMAIL PROTECTED]> schrieb: > Adrian von Bidder <[EMAIL PROTECTED]> schrieb: > >> On Tuesday 11 January 2005 16.26, you wrote: >>> [not subscribed to tetex-maint, so please cc: me if replying there.] >> >>> I created a quick package of Achim Brucker's svninfo latex Package. >>>

Re: RFC and RFS: latex-svninfo

Adrian von Bidder <[EMAIL PROTECTED]> wrote: > >> - you don't install any files in /usr/share/doc... > > dh_installdocs does. > > $ dpkg -S /usr/share/doc/latex-svninfo/README-0.1 > latex-svninfo: /usr/share/doc/latex-svninfo/README-0.1 Excuse me, I missed that call. But you should also install t

Re: Question about packaging documentation

Magnus Therning <[EMAIL PROTECTED]> schrieb: > Frank Küster wrote: >> <[EMAIL PROTECTED]> schrieb: >> >>>So is there any documenation about building non binary packages from scratch? >> Just as any architecture-independent package. Why not have a look at >> one >> existing example (apt-cache --nam

Re: Question about packaging documentation

<[EMAIL PROTECTED]> schrieb: > So is there any documenation about building non binary packages from scratch? Just as any architecture-independent package. Why not have a look at one existing example (apt-cache --names-only search ^doc-). > I tried with my own Makefile for installing the files an

Re: RFC and RFS: latex-svninfo

Adrian von Bidder <[EMAIL PROTECTED]> schrieb: > On Tuesday 11 January 2005 16.26, you wrote: >> [not subscribed to tetex-maint, so please cc: me if replying there.] > >> I created a quick package of Achim Brucker's svninfo latex Package. >> >

Re: RFC and RFS: latex-svninfo

Adrian von Bidder <[EMAIL PROTECTED]> schrieb: > I created a quick package of Achim Brucker's svninfo latex Package. > > > - google did find a mail (from 2003, though) indicating that no latex > package packaging policy exists, so I haven't

Re: About creating .deb packages

TIFR students <[EMAIL PROTECTED]> schrieb: > We would like to know which files are absolutely necessary for creating .deb > package (assuming u have all the source > files needed). > We know about control file,changelog,rules,conffile, n scripts like > postrm,prerm,preinst,postinst. > > We hav

Re: minimum package name length

Tilman Koschnick <[EMAIL PROTECTED]> wrote: > One question though: Is there any problem if my > c3-tool-suite_4.0.1.orig.tar.gz unpacks into c3-4.0.1/? dpkg-source and > dpkg-buildpackage don't seem to have a problem with it, but are there > any other pitfalls with differing upstream-tarball names

Re: maint-guide update (pbuilder, linda, orig.tar.gz etc.)

Osamu Aoki <[EMAIL PROTECTED]> wrote: > or specifically check correctness for the following sentences. > (I welcome English grammar correction too.) Here come some comments: > --- > 9.3 The orig.tar.gz file > - If you simply copy contents of debian/ director

Re: minimum package name length

Tilman Koschnick <[EMAIL PROTECTED]> wrote: > Hi, > > I'm intending to package the Cluster Command & Control tool suite [0], > commonly refered to as C3. My package name of choice would be c3, but I > was wondering if such short names are acceptable. Is there any > documentation or general consent

Re: Default gcc for sarge, libunwind

Steve Langasek <[EMAIL PROTECTED]> wrote: > On Thu, Dec 16, 2004 at 08:13:31PM +0100, Adeodato Simó wrote: > >> [quoting me, Frank] > >> > Secondly, I'd like to learn what this libunwind is about and why >> > tetex-bin is linked against it on some (many!) arches, but not on >> > i386. The package

Re: Default gcc for sarge, libunwind

Frank Lichtenheld <[EMAIL PROTECTED]> wrote: > The libunwind issue is newer, you > probably just have to read the corresponding bug reports. Which bugs? TIA, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich Debian Developer

Default gcc for sarge, libunwind

Hi, this question might be really dumb, but: Where can I find information which gcc version is used for sarge? I was under the impression that it was gcc-3.3, because gcc-3.4 entered unstable only in July this year (when we were thinking to be a couple of weeks before the final freeze). And becaus

Re: Order of package removal

martin f krafft <[EMAIL PROTECTED]> schrieb: > also sprach Frank Küster <[EMAIL PROTECTED]> [2004.12.15.1543 +0100]: >> Is it possible to combine removing one package with purging an other one >> in the same apt (aptitude, whatever) run, by any means? > > Nope. :( > > You can do so with > > dpkg

Re: Order of package removal

Adeodato Simó <[EMAIL PROTECTED]> wrote: > I don't know what the outcome of the "in which order are scripts > called", but in any case why don't you (*): > > - have each of the font-packges that will need /var/lib/tetex on > postrm ship a /var/lib/tetex/.emtpy file, so that > "

Re: Introducing myself and my package

Justin Pryzby <[EMAIL PROTECTED]> wrote: > I believe that the problem is that the diff we use doesn't store > permission information, and so zcat ../foo-12.diff.gz |patch -p1 > (which *creates* debian/*) doesn't have a chance to restore with > execute permission. dpkg-source -x does set x permiss

Order of package removal

Hello, Is it possible to combine removing one package with purging an other one in the same apt (aptitude, whatever) run, by any means? I am asking this because of the following problem: Some conffiles of packages depending on tetex-base (font packages) cause trouble if the data files, the fonts,

Re: pkg-classifier appliance

vegetax <[EMAIL PROTECTED]> wrote: > Frank Küster wrote: > >> First of all, I don't understand the package description. The README >> file gives some more insight in what it might be, but the package >> description should be sufficient for an admin to decide whether to >> install it. > > I think y

Re: pkg-classifier appliance

vegetax <[EMAIL PROTECTED]> wrote: > The url for the tgz containing the source code, just 1 python file and a > README is http://files.bighosting.net/lh13023.zip , Why on earth do you think it makes sense to zip a tar.gz file? It even gets bigger. > can someone please > check it and upload it

Re: "Cannot represent change" error upon PNG file addition

Nick Lewycky <[EMAIL PROTECTED]> wrote: > Zoltan Ivanfi wrote: >> Wouldn't the following simple solution work? >> --- /usr/bin/dpkg-source2004-11-11 21:15:52.0 +0100 >> +++ /home/ifi/bin/dpkg-source 2004-12-08 14:45:00.0 +0100 >> @@ -406,7 +406,7 @@ >>

Re: shared libraries

martin f krafft <[EMAIL PROTECTED]> schrieb: > also sprach Frank Küster <[EMAIL PROTECTED]> [2004.12.08.1026 +0100]: >> And it is this last step in which the shared library needs to be >> used, while it is still not installed. How could a linker call >> help here? > > I can't figure it out right n

developers-reference: Please document bug handling in experimental uploads (was: experimental uploads and closed bugs)

Package: developers-reference Version: 3.3.5 Severity: wishlist Stephen Gran <[EMAIL PROTECTED]> wrote: > This one time, at band camp, Andreas Barth said: >> >> Do you have a proposal how to write it? If so, please feel free to raise >> a bug against the developers reference (or remember me ofte

Re: shared libraries

martin f krafft <[EMAIL PROTECTED]> schrieb: > also sprach Frank Küster <[EMAIL PROTECTED]> [2004.12.07.1937 +0100]: >> As I understood it, this is exactly the situation Justin is in. > > Also read the LD_LIBRARY_PATH document. The second URL you gave? The citation is from there. > Instead of s

Re: experimental uploads and closed bugs

Andreas Barth <[EMAIL PROTECTED]> schrieb: > * Frank Küster ([EMAIL PROTECTED]) [041207 17:40]: >> I'm quite sure I read it somewhere, but cannot currently find it: How >> does the archive software treat bugs that are closed in the changelog of >> an upload to experimental? Are the bugs tagged fix

experimental uploads and closed bugs

Hi, I'm quite sure I read it somewhere, but cannot currently find it: How does the archive software treat bugs that are closed in the changelog of an upload to experimental? Are the bugs tagged fixed, or is nothing done at all? Regards, Frank -- Frank Küster Inst. f. Biochemie der Univ. Zürich D

Re: Package split/merge advice

Andreas Rottmann <[EMAIL PROTECTED]> schrieb: > Frank Küster <[EMAIL PROTECTED]> writes: > >> There are also disadvantages, however. Most importantly, you should only >> do that if upstream always releases the data files in one go. If they >> are released separately, at different times and with di

Re: shared libraries

Justin Pryzby <[EMAIL PROTECTED]> schrieb: > How can I modify the path to the libraries? During compilation, the > build system has to see $buildpath/iraf/lib/libfoo.so.0, but once > installed, the executables must see > /usr/lib/iraf/iraf/lib/libfoo.so.0. There are a bunch of executables, > so

Re: Package split/merge advice

Rudy Godoy <[EMAIL PROTECTED]> wrote: > Hi, I'm the maintainer of torcs[0], a car racing game. Initially > I've made four -data packages, one is the base data files, and the > others are for -tracks and -cars. Due some filled bugs I've > discovered that it needs another -cars package to have the