Daniel Leidert gmx.net> writes:
>
> Am Samstag, den 22.12.2007, 23:34 +0900 schrieb Charles Plessy:
>
> > Also, if there are two such
> > programs installed, is there something that can be done through MIME so
> > that the user has a chance to chose the program ?
>
> Not directly through MIM
ture).
> - why are you using both cdbs and debhelper 7? they almost aim to do
> the same thing, and I encourage to use dh7
By the way, I won't check or even sponsor any package that uses cdbs. I
want to understand the packaging, and I never grokked cdbs enough to
upload a package using
unnels]
deb = fsh -l frank
[miscellany]
[auto-props]
~$ egrep -v '^$|^#' .subversion/servers
[groups]
debian = svn.debian.org
[debian]
svn-tunnel = ssh [EMAIL PROTECTED]
[global]
~$
TIA, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
Paul Wise <[EMAIL PROTECTED]> wrote:
> Try this:
>
> svn checkout svn+ssh://[EMAIL PROTECTED]/svn/pkg-tetex/
Oh, thanks - the additional /svn/ in the path did the trick. This
should be documented on alioth...
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
suggestions about repackaging that are now in
the Developers' reference.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
e of "Unkown default" in
dh_installdebconf, but it calls po2debconf which contains this string,
leading to the correct file even if you don't know perl.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
#x27;s an aspell upstream issue if anything.
If it is a bug, it's still a bug; whether it should be fixed in a
Debian-specific patch or by pestering upstream about it is at the
descretion of the maintainer.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
s would behave as expected, but I think that having one more
> package only for this would be quite insane!
Especially because others would pick up the idea...
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
discriminates between upstream version and Debian
revision; dak does not when checking for NMUs.
Regards, Frank
¹except editing things like the Debian changelog mode of Emacs...
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
ll in B,C,D"; or to create a script in A-pre that will ask the debconf
questions and then ask "You must install A,B,C and D for this to have an
effect. Proceed" and run apt-get install A B C D.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
gt; It should be possible to build the package multiple times.
s/should/must/
Maybe explicitly mentioning autotools is worth the effort, since this
seems to be the only case where it is an issue, and might help to
prevent people from inventing "false" uses.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
ss Goswin's suggestion to look at CDD is the best so far.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
e got enough time to tell everybody that I think this package really
deserves some care!
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
ic :-)
> Note also that modifying configuration files which are not conffiles
> must be done through a well-defined interface, which would probably be
> provided by the other packages. Such an interface is usually
> /usr/{s,}bin/update-foo. Modifying such a file any other way is a
> policy violation.
You forgot that he wants to simply preseed debconf answers.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
;PS: Please try to follow the common quoting style: Quote only what you
>>directly refer to, only as much as needed and quote each part you are
>>replying to directly above your respective answer/comment. That makes
>>reading your postings a lot easier.
You should read and follow that
the package directories, or in the
texlive repository. Having all these changes in diff.gz would make them
unreadable (imagine you want to patch an info file to add
Debian-specific information...)
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
ragraphs cited here in
debian/copyright, not only "It's GPL, text is at...". I don't know
whether this is mandatory, though.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
;s not included in order to start things simple. On a
> longer time scale it is planned to split the program into a library, a
> command line tool and a GUI as supposed previously:
> http://lists.debian.org/debian-science/2005/08/msg00125.html
Oh, I thought that the GUI was just a frontend to the
ilder setup is incorrect, but then it would
probably happen with every package.
What problems exactly do you have with which packages?
> How can this problem be solved? AFAIR, pbuilder is official build tool
No, the official build tool is sbuilder (and not exactly the version
that is released some
"Alexander A. Vlasov" <[EMAIL PROTECTED]> wrote:
> В Чтв, 01/09/2005 в 16:50 +0200, Frank Küster пишет:
>> "Alexander A. Vlasov" <[EMAIL PROTECTED]> wrote:
>>
>> > Hello.
>> >
>> > I have to build a lot of packages for
doesn't happen.
But binary-only-NMUs do happen, and that is a very similar situation.
I've never done one, so I don't know how you change the version - but
probably you do it in the changelog. Then why not add a "recompiled for
sarge" entry? I've seen that often for woody backports.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
t hurt to prepare your software for being a shared libray,
and telling people that they should request that instead of copying your
code.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
of no use.
> What if there are many binaries (10s of them) in your package, and you
> want to use shared libs purely for resource efficiency (disk and
> memory)?
You're right, that's an other reason for a shared library.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
s even worse than
the english original.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
onts and vertical writing, and because of the
>dependency on fontinst 1.918 (only available in teTeX3), I will
>need some more time to get 4.6.0 working.
You probably know that teTeX 3 is in experimental? I hope to bring it
into unstable soon.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
it should happen, quite
> sure.
I guess so, too. Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
ebconf database has "false".
2.b the postinst script queries the debconf database and finds that it
doesn't need to change the setting.
Either there is an error in the description above, or I'm missing a
fundamental idea of making the config script idempotent without reasking
questions. Can you help me out?
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
v
>> +passwd
>> +procps
The last three aren't needed in a chroot (although I usually add users
in static chroots, and thus want passwd).
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
appreciated.
Did you load confmodule?
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
the tarball justify repackaging
- I think it is always possible to remove them in the clean target,
which will always be called when dpkg-buildpackage is used.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
an
that, I would do nothing - it is a bug, therefore a lintian override is
inappropriate, but it is not serious enough to justify messing with the
tarball.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
Sune Vuorela <[EMAIL PROTECTED]> wrote:
> On 2005-11-15, Frank Küster <[EMAIL PROTECTED]> wrote:
>> "fakeroot debian/rules binary" directly won't get bitten. Other than
>> that, I would do nothing - it is a bug, therefore a lintian override is
>>
f it was my package, I'd just upload it with the
bug and the lintian error, and an explanation in the changelog and
README.Debian file. If it's rejected due to the lintian error, and
there's no reaction on subsequent complaints, you can still reupload it
with a lintian override, and still get the package into unstable faster
than it was usual a year ago...
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
ld also look for a "make dist" target - if it exists, you
can simply create a tar.gz file from an SVN export. If it doesn't exist
yet, you can earn yourself some honor and contribute it...
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
an package?
uuencode/uudecode
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
package produces a
binary package that already exists, the new source package does not go
through NEW. At least it has been that way this summer. I have been
told there are plans to change that, but I assume that it has not yet
been done.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
it should be
Suggests.
A wrapper script that gives a nice warning would be great; but be
careful to actually deliver the warning to the user if the ppower4
postprocessor has a menu entry.
> For kaffe you can depend on another free runtime like sablevm or
> java-gcj-compat too.
Does ppower
bian Release (Closes: 333680)
> This makes no sense, it is a debian package so the "debian" can be
> ommited, the rest is ok.
If Adriaan previously published deb packages in his local repository, it
might well make sense to speak of an initial Debian release.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
Carlo Segre <[EMAIL PROTECTED]> wrote:
> On Wed, 7 Dec 2005, Frank Küster wrote:
>
>> Mario Iseli <[EMAIL PROTECTED]> wrote:
>>
>>> debian/changelog:
>>> * Initial Debian Release (Closes: 333680)
>>> This makes no sense, it is a debian p
nd have been looking for
>>>a sponsor for the package at
>
> Why don't you ask your previous sponsor?
He did, the previous sponsor (me) said that he won't have time this year
or longer.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
d install the build-deps anyway.
Alternatively, if you just unpacked the sources, edited some files in
debian, and now want to create a binary package, why not simply
cd ..; dpkg-source -b
pbuilder build
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
r keep things as they are, but there must be a reason
for the lintian warning. In the Policy section on permissions I
couldn't find anything specific.
TIA, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
, I can judge
whether it applies in my case, and fix it or add a lintian override.
But if I don't know any rationale (except "why not?"), I can't.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
ebang line; but I also
don't see the need for removing it, thus cluttering the diff.gz with
useless hunks.
Or not so useless as I'd like to learn from you.
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
command line would easily solve the problem of a
"permission denied"?
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
"cobaco (aka Bart Cornelis)" <[EMAIL PROTECTED]> wrote:
> On Friday 23 December 2005 10:24, Frank Küster wrote:
>
>> The fact that the script is not in the path isn't enough for you here?
>> And don't you think that anyone who knows that a shebang lines
Ben Finney <[EMAIL PROTECTED]> wrote:
> On 23-Dec-2005, Frank Küster wrote:
>> Ben Finney <[EMAIL PROTECTED]> wrote:
>> > A shebang line is more than documentation: it is a strong
>> > indication that the script will be executable from the command
>
es for there
debconf questions, i.e. the way the configure script is called, and
when.
Do you think it would be an obstacle for development if that were
documented in the Policy, just as the same is documented for the
"classical" maintainer scripts? Why isn't it an obstacle for
Manoj Srivastava <[EMAIL PROTECTED]> wrote:
> On Tue, 27 Dec 2005 17:41:00 +0100, Frank Küster <[EMAIL PROTECTED]> said:
>
>> And I thought I could rely upon dpkg from the next upload to call
>> the configure script with the same arguments as it did before, just
&g
ch I'm the upstream author?
Well, yes. But how's that different to the current procedure - you
create a package, commit yourself to caring for it, and find a sponsor?
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
l one. On the other hand, it's easy (for
me) to understand how hosts.deny works.
Furthermore, AFAIK iptables isn't a dependency, but rather a
configuration option when compiling the kernel - then it is *not* a
dependency like any other.
Regards, Frank
--
Frank Küster
Inst. f. Bio
Nico Golde <[EMAIL PROTECTED]> wrote:
> Hi,
> * Frank Küster <[EMAIL PROTECTED]> [2006-01-16 22:50]:
>>
>> I have no understanding of what a packetfilter firewall actually does,
>> and therefore I won't install one. On the other hand, it's easy
n-maintainer upload", and you don't
> appear to be a DD, therefore it's not possible for you to upload --
> non-maintainer or otherwise. A DD will have to upload the fix in question.
But see especially http://lists.debian.org/debian-mentors/2006/01/msg00168.html
Regards, Frank
--
Frank Küster
Inst. f. Biochemie der Univ. Zürich
Debian Developer
Steve Langasek <[EMAIL PROTECTED]> wrote:
> On Tue, Jan 17, 2006 at 01:55:27PM +0100, Frank Küster wrote:
>> Steve Langasek <[EMAIL PROTECTED]> wrote:
>
>> > On Tue, Jan 17, 2006 at 01:03:32PM +0100, Bjoern Boschman wrote:
>
>> >> I'd like to c
ploads (it already is, I
> think), and notfound commands to [EMAIL PROTECTED] should be used instead of
> fixed-in-experimental tags.
Why not use bug#-done with an appropriate Version pseudoheader, also
for uploads to experimental?
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy
bian-Pakete machen will, der muss genug
Englisch verstehen, um auf Bugreports reagieren zu können. Dann sollte
auch die Policy kein Problem sein.
Gruß, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
e
installation procedure and maintainer scripts. Control files only exist
in the source package. And what you wrote above about postinst and
postrm can also easily be shown to be false (or at least incomplete) by
looking at these sections.
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
7;s quilt. The main advantage of
quilt IMHO is that it doesn't duplicate the whole tree when editing and
updating the patch, which can be time- and disk-consuming in large
projects. Instead it keeps a list of files for the patch one is editing
and only keeps copies of these.
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
ithout looking at its description, I think yes.
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
"Kevin B. McCarty" <[EMAIL PROTECTED]> wrote:
> Frank Küster wrote:
>
>> The main advantage of
>> quilt IMHO is that it doesn't duplicate the whole tree when editing and
>> updating the patch, which can be time- and disk-consuming in large
>>
be symlinked from the established place, and
then adding support to parse an additional per-user directory is just a
goody.
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
existed.
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
f it is changed, either keep it and insert a comment at its beginning
that it is unused, or move/rename it. In all cases where the file's
presence could have a bad effect, I renamed or moved it.
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
calling update-rc.d? It feels really bad to
>> > remove files from /etc in maintainer scripts, but perhaps it's the
>> > right thing to do...
>
>> - if the file is unchanged, remove it
> Even changed files are removed on purge.
Yes, of course - I should have been
Don Armstrong <[EMAIL PROTECTED]> wrote:
> On Mon, 06 Feb 2006, Frank Küster wrote:
>> - if it is changed, either keep it and insert a comment at its
>> beginning that it is unused, or move/rename it. In all cases where
>> the file's presence could have
ve cases in teTeX where there are only two
alternatives: Either accept the change, or not install the debianized
package at all and go for /usr/local/ instead.
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
ss, the information is in the dependency
fields.
HTH, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
Don Armstrong <[EMAIL PROTECTED]> wrote:
> On Tue, 07 Feb 2006, Frank Küster wrote:
>> Don Armstrong <[EMAIL PROTECTED]> wrote:
>>
>> > Right. The problem is that it's not always easy to know if the file
>> > will no longer be read at all; you ca
Don Armstrong <[EMAIL PROTECTED]> wrote:
> On Tue, 07 Feb 2006, Frank Küster wrote:
>> Don Armstrong <[EMAIL PROTECTED]> wrote:
>> > On Tue, 07 Feb 2006, Frank Küster wrote:
>> >> Don Armstrong <[EMAIL PROTECTED]> wrote:
>> >>
>&g
Don Armstrong <[EMAIL PROTECTED]> wrote:
> On Wed, 08 Feb 2006, Frank Küster wrote:
>> Don Armstrong <[EMAIL PROTECTED]> wrote:
>> > You've now got a conffile in a location which is not /etc, namely
>> > /var/lib/bla, which cannot be overridden b
without an additional indirection
via /etc.
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
I've to celebrate; I got my first REJECTED mail from the
> archive installer thanks to trying to fix this package :P
Why was it rejected?
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
t the maintainer to upload this to main needs to do a
> `debuild -sa` so that everything (.orig.tar.gz, .diff.gz, and .dsc)
> gets to be signed off in the .changes file?
Yes, that should have helped.
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
usr/share/games/xshisen . Naturally I had to fix
> the debian/rules to correct this. No files were removed or not
> distributed in the resulting deb.
It's still unclear to me whether "won't start" means "Tells the user it
won't start without these file
[...]
> I've got also:
> gpg: skipped "cedric briner
> is that mandatory to make it work ?
Technically, you can just use "dpkg-buildpackage -b -uc" (or "-us -uc",
without -b to create everything in one run). But for being a
maintainer, you should create a gpg
e not the rw-r--r-- perm...
>
> during the unpack of sources, probably, only debian/* files are chmod-ed..
> could be the reason?
IIRC, dpatch doesn't call "patch -p -i debian/patches/",
but instead it executes the file, and if it's just a normal unified
diff, there'
tion.
They process NEW binary packages quite fast, within one to three days to
my impression.
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
hey use a "repacked source", they didn't provide a
> README.Debian-source. Are there exceptions from that rule?
Nobody is enforcing that, and it's actually a rather new addition to the
Developers' Reference.
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
necessary if you depend on tetex-extra (because -extra
depends on -bin). On the other hand, people can use TeXLive just as
well. The package splitting scheme is different, but I think
Recommends: gs-gpl | gs-esp | gs-afpl, netpbm, psutils, tetex-extra |
texlive-latex-extra
will do.
Regards, Fr
heir config under /etc.
> Done. I had put it in there because the original package installed it
> in /usr/lib/checkinstall/, so I considered it worth noting.
If the place for configuration is mentioned anywhere in the upstream
documentation, this is the place to indicate the Debian-specific
p
es is that they apply equally well to Debian specific
> packages. IOW, to ease peer review and NMU'ing, _every_ package should
> be non-native, with no exception.
I don't agree. If every new upload would be a new upstream version, it
doesn't help you much to see that the diff.g
e in
/usr/share/doc/foo-xfonts/copyright only the information about these
data. And I don't see how this is against policy.
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
/ch4.html#s-configurationfiles
* it would be nice if the documentation, at least the upstream
README. would be available to texdoc. A symlink
/usr/share/doc/texmf/thailatex/thailatex.txt ->
../../thailatex/README would do.
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
x27;t read old
> standards, I can't gather what changes are needed between
> old and new version. I hope saying "after the repackaging"
> is sufficient.
Have a look at /usr/share/doc/debian-policy/upgrading-checklist.txt.gz
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
"roucaries bastien" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> glosstex was orphaned two month ago. However I use it everyday and I
> furthermore I correct a few bugs and I improve it (hyperref).
Have you contacted upstream about the hyperref extensions?
Regards, F
(DDs or non-DDs) in the Uploaders:
Field. Or it is maintained only by you, or you and a couple of people
without connection to such a list. Then you should be in the Maintainer
field, and the possible others (or nobody) in the Uploaders field.
See the Debian Policy on that.
Regards, Frank
--
Fr
ect who prepared a particular upload, but
instead the "List of the names and email addresses of co-maintainers of
the package, if any.".
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
"Theppitak Karoonboonyanan" <[EMAIL PROTECTED]> wrote:
> On 4/25/06, Frank Küster <[EMAIL PROTECTED]> wrote:
>
>> I'll not be able to do this today (I think), please remind me if I don't
>> speak up by tomorrow evening.
>
> I guess all
"Theppitak Karoonboonyanan" <[EMAIL PROTECTED]> wrote:
> On 4/28/06, Frank Küster <[EMAIL PROTECTED]> wrote:
>>
>> Sorry, I found two more things while testing the upgrade.
>>
>> First, you should bump your versioned depends on tex-common t
maker/usr/share/doc/texmaker . If somebody could show me what to
> do to get the package to "see" this it would help.
"can't be found" by what? Does texmaker maybe call "texdoc" to look for
them? Then you need to follow
file:///usr/share/doc/tex-common/Deb
o explicitly *Build-Depend* on it (with proper version).
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
so add it as an alternative build-dependency (or
file a bug against texlive if that doesn't work).
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
tio?
If the PDF was generated by pdfTex on a Debian machine, the highest
compression level (9) is already used. I don't know what happens when
it's created via dvi->ps->pdf, and gs' documentation isn't clear about
that, but ps2pdf14's pdf files are even slight
aces='$TEXMFMAIN'
(which works in etch, too, but it's kind of ugly and not what it's meant
for).
I think the clean solution would be to change the autoconf script to
output the right thing; and autoconf wizards might be able to do this
(perl and emacs lisp might have similar probl
bian TeX Policy.
> It explains where to put all the TeX files inside a TeX tree (which TeX
> tree to use is explained in the Debian TeX Policy).
Yes, but it doesn't tell you which TEXMF tree to choose, and that was
the problem here.
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
Try to avoid a debian/
directory in the upstream sources. It's in the archives.
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
n the upstream sources. It's in the archives.
> yeap - I saw most of those. And I saw the arguments. And I agree that
> having split debian/ helps in few cases. But the same question arises
> over and over. May be it is the time to fix the policy to make it
> explicit to avoid the debates.
How can the Debian policy "forbid" something that upstream is doing?
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
e ones working with
the older groups?
>> How can the Debian policy "forbid" something that upstream is doing?
> :-) Good questions with simple answer: it can't. That is why over and
> over again everyone advices upstreams to place /debian directory aside
> of orig.tar.gz
package must not declare a "Depends",
| "Recommends", or "Build-Depends" relationship on a non-main
| package),
`
This explicitly does *not* mention "Suggests".
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
downloader.
> Then again, this sounds pretty much like a thing for debian-legal. :-)
I rather think it's a technical question: Can a source package in main
produce one binary package that is installed in contrib, or is the
separation done only on the level of source packages?
Regards, Frank
--
Frank Küster
Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich
Debian Developer (teTeX)
1 - 100 of 589 matches
Mail list logo