On 2020-08-11 20:07, Drew Parsons wrote:
On 2020-08-11 19:48, Bastian Germann wrote:
Am 11.08.20 um 12:38 schrieb Drew Parsons:> The diff reports that the
[egg_info] section got removed from setup.cfg.
...
The uploaded orig file also changed, so be sure to have the current
On 2020-08-11 19:48, Bastian Germann wrote:
Am 11.08.20 um 12:38 schrieb Drew Parsons:> The diff reports that the
[egg_info] section got removed from setup.cfg.
...
The uploaded orig file also changed, so be sure to have the current
one.
That will make a difference, thanks for clarify
On 2020-07-29 17:09, Bastian Germann wrote:
Am 29.07.20 um 06:10 schrieb Drew Parsons:
The python3-setuptools-scm build dependency could not be installed in
your environment which causes setuptools to try download this package.
That obviously fails.
Shouldn't pdebuild make sure that all
On 2020-08-02 23:10, Drew Parsons wrote:
On 2020-07-29 23:45, mat...@debian.org wrote:
On Wed, Jul 29, 2020 at 11:09:37AM +0200, Bastian Germann wrote:
Shouldn't pdebuild make sure that all the build dependencies are
installed?
I certainly would have expected it to check build dependencies
On 2020-07-29 23:45, mat...@debian.org wrote:
On Wed, Jul 29, 2020 at 11:09:37AM +0200, Bastian Germann wrote:
The python3-setuptools-scm build dependency could not be installed in
your environment which causes setuptools to try download this package.
That obviously fails.
Shouldn't pdebuild
Hi Bastian, freetype-py builds fine with dpkg-buildpackage, but fails in
chroot (pdebuild pbuilder):
$ pdebuild
dpkg-checkbuilddeps: error: Unmet build dependencies:
python3-setuptools-scm
W: Unmet build-dependency in source
dh clean --with python3 --buildsystem=pybuild
dh_auto_clean
On 2019-10-10 17:21, Nico Schlömer wrote:
Hi everyone,
I've worked on VTK8 [1] and I think it's about ready to be included
into Debian. (More than two years after its release, unfortunately.)
There's a PPA with the latest build [2] if you want to try it out.
Could anyone take a look? What
On Sat, 2018-05-19 at 10:55 +, Lumin wrote:
> On Fri, May 18, 2018 at 11:49:05PM +0800, Drew Parsons wrote:
> >
> > I wonder if the simplest solution is to just have
> > intel-mkl Depends: libblas. i.e. use policy to simply prevent a
> > sole
> > mkl
On Sat, 2018-05-12 at 03:22 +, Lumin wrote:
> Hi Sébastien,
>
> > But IMO it's acceptable to not perfectly deal with the
> > corner case
> > where only MKL is installed, as long as some warning is displayed.
>
> I insist on removing the Provides, even if it looks weird. For sake
> of
>
On Sun, 2018-05-06 at 10:13 +0200, Sébastien Villemot wrote:
>
> Yes, but it’s the GPL that forbids distribution of a binary linking
> together
> GPL code and non-free code.
But we're not distributing GPL binaries for use with nonfree MKL, we're
distributing them to use with OpenBLAS or ATLAS.
On Wed, 2011-06-29 at 15:01 +0200, Andreas Tille wrote:
Hi,
Your package is uninstallable on some archs:
mrbayes-mpi/mips unsatisfiable Depends: openmpi-bin
mrbayes-mpi/mipsel unsatisfiable Depends: openmpi-bin
mrbayes-mpi/s390 unsatisfiable Depends: openmpi-bin
I admit
On Fri, Dec 27, 2002 at 12:23:03AM -0800, Osamu Aoki wrote:
Hi,
latex source is in my people.debian.org/~osamu/pub/
Please check reference.it.tex
Osamu
On Wed, Dec 25, 2002 at 05:44:16PM -0800, Osamu Aoki wrote:
I encounter errors in latex when building PS file (or PDF file).
I
On Fri, Dec 27, 2002 at 12:23:03AM -0800, Osamu Aoki wrote:
Hi,
latex source is in my people.debian.org/~osamu/pub/
Please check reference.it.tex
Osamu
On Wed, Dec 25, 2002 at 05:44:16PM -0800, Osamu Aoki wrote:
I encounter errors in latex when building PS file (or PDF file).
I
On Tue, Nov 05, 2002 at 05:03:24PM +0100, Bas Zoetekouw wrote:
Hi Bob!
You wrote:
For the 1386 architecture, sid has gcc 2:2.95.4-17 and gcc-3.0
1:3.0.4-13. Which compiler should be used for an Architecture: any
package?
The default one for the architecture in question.
On Tue, Nov 05, 2002 at 05:03:24PM +0100, Bas Zoetekouw wrote:
Hi Bob!
You wrote:
For the 1386 architecture, sid has gcc 2:2.95.4-17 and gcc-3.0
1:3.0.4-13. Which compiler should be used for an Architecture: any
package?
The default one for the architecture in question.
On Thu, Oct 24, 2002 at 01:50:29PM -0400, Stephen Gran wrote:
Hello all,
I am having a problem with one of my packages failing on s390. It
builds fine on other architectures (except where I messed up with a bad
build-depends on a build-essential). The problem with s390 is here:
# Add
On Thu, Oct 24, 2002 at 01:50:29PM -0400, Stephen Gran wrote:
Hello all,
I am having a problem with one of my packages failing on s390. It
builds fine on other architectures (except where I messed up with a bad
build-depends on a build-essential). The problem with s390 is here:
# Add
On Sun, Oct 20, 2002 at 09:54:46AM -0400, Stephen Gran wrote:
This is on alpha and ia64. I vaguely remember seeing some problem with
using libc6 as a Build-Depend (something like libc6 | libc ?) - I just
can't remember, and as I have no access to one of these boxes, I would
appreciate a
On Thu, Oct 17, 2002 at 11:05:59PM +0200, Stefan Schwandter wrote:
Drew Parsons wrote:
And more to the point [ ;) ], how do I force the autobuilder maintainers to
actually upload my package once it has been autobuilt?
The s390 version of xprint-xprintorg has been built for a whole week
On Thu, Oct 17, 2002 at 11:05:59PM +0200, Stefan Schwandter wrote:
Drew Parsons wrote:
And more to the point [ ;) ], how do I force the autobuilder maintainers to
actually upload my package once it has been autobuilt?
The s390 version of xprint-xprintorg has been built for a whole week
On Thu, Oct 17, 2002 at 11:44:14AM +0200, Marco Kuhlmann wrote:
How do I force a rebuild on buildd?
And more to the point [ ;) ], how do I force the autobuilder maintainers to
actually upload my package once it has been autobuilt?
The s390 version of xprint-xprintorg has been built for a
On Thu, Oct 17, 2002 at 11:44:14AM +0200, Marco Kuhlmann wrote:
How do I force a rebuild on buildd?
And more to the point [ ;) ], how do I force the autobuilder maintainers to
actually upload my package once it has been autobuilt?
The s390 version of xprint-xprintorg has been built for a
On Tue, Oct 15, 2002 at 10:24:05AM -0600, Bob Proulx wrote:
Drew Parsons [EMAIL PROTECTED] [2002-10-14 00:41:49 +1000]:
OK, I'll try to remember to restrip for sarge :)
Perhaps the BTS could be a help in remembering this?
Bob
Good idea :)
Drew
--
PGP public key available at http
On Tue, Oct 15, 2002 at 10:24:05AM -0600, Bob Proulx wrote:
Drew Parsons [EMAIL PROTECTED] [2002-10-14 00:41:49 +1000]:
OK, I'll try to remember to restrip for sarge :)
Perhaps the BTS could be a help in remembering this?
Bob
Good idea :)
Drew
--
PGP public key available at http
On Sun, Oct 13, 2002 at 10:30:35AM +0200, Bas Zoetekouw wrote:
Could someone please clarify if it's appropriate to respect upstream's
wishes to leave the symbols in?
Sure. It's only a should in policy, not a must, so it's ok not to
strip.
OK, I guess I'll pack 'em back in with my
On Sun, Oct 13, 2002 at 10:09:00AM -0400, Colin Walters wrote:
But to answer your specific question, I don't see it as a big deal if
you ship unstripped binaries in a package in unstable for a while. I
think the important part is providing stripped binaries for sarge; so
just be sure to
On Sun, Oct 13, 2002 at 10:30:35AM +0200, Bas Zoetekouw wrote:
Could someone please clarify if it's appropriate to respect upstream's
wishes to leave the symbols in?
Sure. It's only a should in policy, not a must, so it's ok not to
strip.
OK, I guess I'll pack 'em back in with my next
On Sun, Oct 13, 2002 at 10:09:00AM -0400, Colin Walters wrote:
But to answer your specific question, I don't see it as a big deal if
you ship unstripped binaries in a package in unstable for a while. I
think the important part is providing stripped binaries for sarge; so
just be sure to
Policy says binaries should (not must) be stripped:
http://www.debian.org/doc/debian-policy/ch-files.html#s11.1
Note that by default all installed binaries should be stripped, either by
using the -s flag to install, or by calling strip on the binaries after they
have been copied into debian/tmp
Policy says binaries should (not must) be stripped:
http://www.debian.org/doc/debian-policy/ch-files.html#s11.1
Note that by default all installed binaries should be stripped, either by
using the -s flag to install, or by calling strip on the binaries after they
have been copied into debian/tmp
On Sun, Sep 08, 2002 at 06:27:05PM -0400, Joey Hess wrote:
So dh_builddeb just says the command returned an error code, without
specifying which command (dpkg-deb?) or which error.
Run dh_buildeb -v to get the command it is running, you should then be
able to reproduce it manually by
On Sun, Sep 08, 2002 at 06:27:05PM -0400, Joey Hess wrote:
So dh_builddeb just says the command returned an error code, without
specifying which command (dpkg-deb?) or which error.
Run dh_buildeb -v to get the command it is running, you should then be
able to reproduce it manually by
I'm getting an error from dh_builddeb when trying to build a new package.
The build was working previously, but today it started failing, and doesn't
really say why. Are there any known problem with dh_builddeb?
The relevant part of the log (from fakeroot debian/rules binary), building
the deb
On Wed, Sep 04, 2002 at 08:19:36PM -0700, Zack Weinberg wrote:
Hi,
I've re-done the zangband package, intending to fix bug #159039 which
makes the game completely unplayable, but in the process I fixed a
bunch more (all but #141684, I believe).
I do not have the time to become a Debian
On Wed, Sep 04, 2002 at 08:19:36PM -0700, Zack Weinberg wrote:
Hi,
I've re-done the zangband package, intending to fix bug #159039 which
makes the game completely unplayable, but in the process I fixed a
bunch more (all but #141684, I believe).
I do not have the time to become a Debian
On Tue, Sep 04, 2001 at 01:53:31PM +0200, Domenico Andreoli wrote:
On Mon, Sep 03, 2001 at 01:22:01PM -0500, Steve Langasek wrote:
On Mon, 3 Sep 2001, Drew Parsons wrote:
[...]
Check the contents of the postinst script in the binary package. The
#DEBHELPER# line gets replaced
My package meschach has a shared library. Previously, I called ldconfig in
the postinst to get the library registered (it was made mandatory in Policy
2.4.1.0).
But I've noticed just now as I prepare a new upload that lintain complains,
saying,
W: meschach:
On Mon, Sep 03, 2001 at 02:08:00PM +0200, Domenico Andreoli wrote:
But I've noticed just now as I prepare a new upload that lintain complains,
saying,
W: meschach: postinst-has-useless-call-to-ldconfig
anyway there was a bug (#109721) and lintian reported this warning even if
My package meschach has a shared library. Previously, I called ldconfig in
the postinst to get the library registered (it was made mandatory in Policy
2.4.1.0).
But I've noticed just now as I prepare a new upload that lintain complains,
saying,
W: meschach: postinst-has-useless-call-to-ldconfig
On Mon, Sep 03, 2001 at 02:08:00PM +0200, Domenico Andreoli wrote:
But I've noticed just now as I prepare a new upload that lintain complains,
saying,
W: meschach: postinst-has-useless-call-to-ldconfig
anyway there was a bug (#109721) and lintian reported this warning even if you
On Sat, Aug 25, 2001 at 11:06:41AM -0700, Sean 'Shaleh' Perry wrote:
my @bashism_regexs = (
..
);
This is the array of regexes I test Debian scripts against in lintian. it is
not all encompassing but it catches most of the egregious ones that bash
allows
and which the
On Sat, Aug 25, 2001 at 03:20:28AM +1000, Drew Parsons wrote:
But doing this, lintian gives the warning:
E: tzwatch: depends-on-essential-package-without-using-version bash
I can't find much in Debian policy about this, so I'd like to ask, what
does this error mean, and why
I'm packaging up a shell script called tzwatch which displays the time from
different timezones. It's actually a bash script since I thought it had
some bashisms (while getopts case select), although reading through the info
pages for bash, it seems these are standard sh commands after all. I
On Sat, Aug 25, 2001 at 03:20:28AM +1000, Drew Parsons wrote:
But doing this, lintian gives the warning:
E: tzwatch: depends-on-essential-package-without-using-version bash
I can't find much in Debian policy about this, so I'd like to ask, what
does this error mean, and why
I'm packaging up a shell script called tzwatch which displays the time from
different timezones. It's actually a bash script since I thought it had
some bashisms (while getopts case select), although reading through the info
pages for bash, it seems these are standard sh commands after all. I
On Fri, Aug 10, 2001 at 07:47:07PM +0200, Radovan Garabik wrote:
On Fri, Aug 10, 2001 at 05:48:49PM +1000, Drew Parsons wrote:
I've just had a fresh look at my package viewmol.
I compiled it in April under X 4.0.1-11, it worked fine then.
But looking at it now, none of the text
I've just had a fresh look at my package viewmol.
I compiled it in April under X 4.0.1-11, it worked fine then.
But looking at it now, none of the text in buttons and menus gets displayed
anymore. Instead, the letters are replaced with a box.
The behaviour appears to be independent of locale -
On Fri, Aug 10, 2001 at 09:53:32AM +0200, Bart Warmerdam wrote:
On Fri, Aug 10, 2001 at 05:48:49PM +1000, Drew Parsons wrote:
[ characters show as boxes in X ]
Can anyone suggest how to best determine the cause of the problem?
Restart X. Helped for me numerous times for the same
I've just had a fresh look at my package viewmol.
I compiled it in April under X 4.0.1-11, it worked fine then.
But looking at it now, none of the text in buttons and menus gets displayed
anymore. Instead, the letters are replaced with a box.
The behaviour appears to be independent of locale -
On Fri, Aug 10, 2001 at 09:53:32AM +0200, Bart Warmerdam wrote:
On Fri, Aug 10, 2001 at 05:48:49PM +1000, Drew Parsons wrote:
[ characters show as boxes in X ]
Can anyone suggest how to best determine the cause of the problem?
Restart X. Helped for me numerous times for the same problem
On Sun, May 27, 2001 at 10:50:18AM +1000, Daniel Stone wrote:
On Sat, May 26, 2001 at 11:44:46PM +0200, R?mi Perrot wrote:
Hi, (Remi? Rimi? mutt doesn't display the second character, as you can see).
Yes it does. You probably haven't set your locale to see it.
[The '?' in R?mi, above, is
On Sun, May 27, 2001 at 10:50:18AM +1000, Daniel Stone wrote:
On Sat, May 26, 2001 at 11:44:46PM +0200, R?mi Perrot wrote:
Hi, (Remi? Rimi? mutt doesn't display the second character, as you can see).
Yes it does. You probably haven't set your locale to see it.
[The '?' in R?mi, above, is
On Thu, May 10, 2001 at 12:56:49PM -0500, Michael Janssen (CS/MATH stud.) wrote:
In Warren Anthony Stramiello's email, 10-05-2001:
It's XDrawChem, a linux version of ChemDraw, a fairly necessary app for
chemistry folks (at least so my girlfriend tells me, and she's a chemistry
major
On Thu, May 10, 2001 at 12:56:49PM -0500, Michael Janssen (CS/MATH stud.) wrote:
In Warren Anthony Stramiello's email, 10-05-2001:
It's XDrawChem, a linux version of ChemDraw, a fairly necessary app for
chemistry folks (at least so my girlfriend tells me, and she's a chemistry
major here
On Fri, May 11, 2001 at 07:06:05PM +0530, Viral wrote:
Do the autobuilders build packages for all the architectures, or is
the maintainer supposed to do that ?
The autobuilders do that. You only compile on your own system, generally.
I was even surprised to find that viewmol managed to
Thanks for your responses, all :)
Setting the file permissions properly seems to be the main need for the root
build environment.
Regards,
Drew
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Thanks for your responses, all :)
Setting the file permissions properly seems to be the main need for the root
build environment.
Regards,
Drew
I just noticed the debian/rules file for mirrormagic which I inherited from
Joey Hess uses dh_testroot to check that the build is run as root (or
fakeroot).
I'm wondering what the justification for doing this is. It prevents, for
instance, a home user compiling his own deb before installing
I just noticed the debian/rules file for mirrormagic which I inherited from
Joey Hess uses dh_testroot to check that the build is run as root (or
fakeroot).
I'm wondering what the justification for doing this is. It prevents, for
instance, a home user compiling his own deb before installing
On Tue, Apr 10, 2001 at 12:38:39PM -0700, Sean 'Shaleh' Perry wrote:
3. add updates to the debianized source but not the orig.tar.gz
I would handle it this way personally. Mucking with upstream source is never a
good idea.
libc6 does does something like this, doesn't it? It's
On Tue, Apr 10, 2001 at 12:38:39PM -0700, Sean 'Shaleh' Perry wrote:
3. add updates to the debianized source but not the orig.tar.gz
I would handle it this way personally. Mucking with upstream source is never
a
good idea.
libc6 does does something like this, doesn't it? It's
On Mon, Mar 26, 2001 at 12:31:30PM -0500, Chris Gray wrote:
On Tue, 27 Mar 2001, Drew Parsons wrote:
I've got Bug #90459, which says libXmu was not identified when
compiling on vore (that's sparc, isn't it? not that it's real
important).
(cgray4 ~)- ldd /usr/lib/libGL.so
On Mon, Mar 26, 2001 at 03:07:45PM -0500, Ben Collins wrote:
Now, with db3, I want to be sure that everyone realizes that they are
compiling against libdb3, since the binary on-disk format of the .db's
is different. So, you have to explicitly tell your builds that you want
-ldb3, so there
On Mon, Mar 26, 2001 at 12:31:30PM -0500, Chris Gray wrote:
On Tue, 27 Mar 2001, Drew Parsons wrote:
I've got Bug #90459, which says libXmu was not identified when
compiling on vore (that's sparc, isn't it? not that it's real
important).
(cgray4 ~)- ldd /usr/lib/libGL.so
On Mon, Mar 26, 2001 at 03:07:45PM -0500, Ben Collins wrote:
Now, with db3, I want to be sure that everyone realizes that they are
compiling against libdb3, since the binary on-disk format of the .db's
is different. So, you have to explicitly tell your builds that you want
-ldb3, so there is
I've got Bug #90459, which says libXmu was not identified when compiling on
vore (that's sparc, isn't it? not that it's real important).
The autobuild log at http://vore.debian.org/buildlogs/viewmol says:
...
cc -c -Wall -I/usr/X11R6/include -DLINUX -I/usr/include
-I/usr/include/python1.5 -O6
My latest package viewmol has a -ldb entry in the makefile.
I asked on this list where on earth I'd find libdb.so to compile against,
and you helpfully pointed me to libdb2-dev.
However, since then, libdb3[-dev] has come out, so I figured I would
dutifully compile against it.
But to my
I've got Bug #90459, which says libXmu was not identified when compiling on
vore (that's sparc, isn't it? not that it's real important).
The autobuild log at http://vore.debian.org/buildlogs/viewmol says:
...
cc -c -Wall -I/usr/X11R6/include -DLINUX -I/usr/include
-I/usr/include/python1.5 -O6
On Sun, Mar 11, 2001 at 05:25:27AM -1000, Brian Russo wrote:
given that upstream has decided to put them in /usr/lib, its
probably reasonable that you follow suit.
That argument convinces me, I'll keep them under a viewmol directory.
I'll have to split the scripts from the C binaries into
On Sun, Mar 11, 2001 at 05:25:27AM -1000, Brian Russo wrote:
given that upstream has decided to put them in /usr/lib, its
probably reasonable that you follow suit.
That argument convinces me, I'll keep them under a viewmol directory.
I'll have to split the scripts from the C binaries into
viewmol, a molecular modelling program I'm packaging, makes use of a number
of supplementary binary files and scripts to read atomic coordinates from a
range of different file formats.
By default these utilities are kept in a viewmol-specific directory
(/usr/local/lib/viewmol, which I'll change
On Sun, Mar 11, 2001 at 04:18:09AM -1000, Brian Russo wrote:
Should I therefore keep these supplementary utilities in the viewmol
directory, or should they instead be moved to /usr/bin?
if they're binaries that are typically wrapped or otherwise not
typically invoked directly by the
viewmol, a molecular modelling program I'm packaging, makes use of a number
of supplementary binary files and scripts to read atomic coordinates from a
range of different file formats.
By default these utilities are kept in a viewmol-specific directory
(/usr/local/lib/viewmol, which I'll change
On Sun, Mar 11, 2001 at 04:18:09AM -1000, Brian Russo wrote:
Should I therefore keep these supplementary utilities in the viewmol
directory, or should they instead be moved to /usr/bin?
if they're binaries that are typically wrapped or otherwise not
typically invoked directly by the
A program (viewmol) I'm trying to package has some problems finding some db
library. It doesn't specify this library explicitly, the makefile just says
viewmol_: $(OBJ) ; cc -o viewmol $(LDFLAGS) $(OBJ) $(LIBRARY) $(LIBS)
LIBS is not defined in the makefile, it just has the default values for
On Fri, Mar 09, 2001 at 10:42:35PM -0500, [EMAIL PROTECTED] wrote:
/usr/bin/ld: cannot find -ldb
collect2: ld returned 1 exit status
make[1]: *** [viewmol_] Error 1
[]
Is the absence of libdb.so in /usr/lib a bug in libc6-dev?
No.
What is the proper way to solve this
A program (viewmol) I'm trying to package has some problems finding some db
library. It doesn't specify this library explicitly, the makefile just says
viewmol_: $(OBJ) ; cc -o viewmol $(LDFLAGS) $(OBJ) $(LIBRARY) $(LIBS)
LIBS is not defined in the makefile, it just has the default values for
On Fri, Mar 09, 2001 at 10:42:35PM -0500, [EMAIL PROTECTED] wrote:
/usr/bin/ld: cannot find -ldb
collect2: ld returned 1 exit status
make[1]: *** [viewmol_] Error 1
[]
Is the absence of libdb.so in /usr/lib a bug in libc6-dev?
No.
What is the proper way to solve this question?
On Sun, Feb 25, 2001 at 01:14:57PM +, Julian Gilbey wrote:
On Sun, Feb 25, 2001 at 11:27:32PM +1100, Drew Parsons wrote:
Nice theory. But when I create meschach.postinst and meschach-dev.postint,
I find that meschach.postinst finds its way into the meschach-dev deb file!
This in spite
On Sat, Feb 24, 2001 at 01:22:03PM -0600, Gordon Sadler wrote:
Create files named debian/post{rm,inst} and debian/pre{rm,inst} if you
need to add specific code for one package. For multiple debs from same
source create debian/$package.post{rm,inst} debian/$package.pre{rm,inst}
Nice
On Thu, Feb 22, 2001 at 11:01:15PM -0500, Matt Zimmerman wrote:
I asked a variation on the same question on -devel a few weeks ago, and got
zero responses. Aborting in the preinst is the only way to do anything
even close, but it makes a bit of a mess.
If you want to quit a
On Thu, Feb 22, 2001 at 11:01:15PM -0500, Matt Zimmerman wrote:
I asked a variation on the same question on -devel a few weeks ago, and
got
zero responses. Aborting in the preinst is the only way to do anything
even close, but it makes a bit of a mess.
If you want to quit a
Sorry to nag. Has anyone got an answer to this question?
On Sat, Feb 17, 2001 at 01:12:27AM +1100, Drew Parsons wrote:
I'm planning to have mirrormagic use debconf to ask the user if they want to
delete the highscore files from the older version (which are incompatible
from the new
Sorry to nag. Has anyone got an answer to this question?
On Sat, Feb 17, 2001 at 01:12:27AM +1100, Drew Parsons wrote:
I'm planning to have mirrormagic use debconf to ask the user if they want to
delete the highscore files from the older version (which are incompatible
from the new
I'm trying to tidy up my package gworldclock.
There's an INSTALL file in the package root directory (from the upstream
edition), but it's not referred to in the build process. It's just a
standard informative file for autoconf.
Now debian/rules simply handles docs by invoking dh_installdocs.
Ooh, I already found it. debian/docs was the culprit.
On Fri, Feb 16, 2001 at 11:24:58PM +1100, Drew Parsons wrote:
I'm trying to tidy up my package gworldclock.
There's an INSTALL file in the package root directory (from the upstream
edition), but it's not referred to in the build process
I'm planning to have mirrormagic use debconf to ask the user if they want to
delete the highscore files from the older version (which are incompatible
from the new).
Having a choice of Yes/No is clear, but it seemed to me it might be
appropriate to provide a third alternative, "Quit", which
I'm trying to tidy up my package gworldclock.
There's an INSTALL file in the package root directory (from the upstream
edition), but it's not referred to in the build process. It's just a
standard informative file for autoconf.
Now debian/rules simply handles docs by invoking dh_installdocs.
Ooh, I already found it. debian/docs was the culprit.
On Fri, Feb 16, 2001 at 11:24:58PM +1100, Drew Parsons wrote:
I'm trying to tidy up my package gworldclock.
There's an INSTALL file in the package root directory (from the upstream
edition), but it's not referred to in the build process
I'm planning to have mirrormagic use debconf to ask the user if they want to
delete the highscore files from the older version (which are incompatible
from the new).
Having a choice of Yes/No is clear, but it seemed to me it might be
appropriate to provide a third alternative, Quit, which aborts
On Sat, Feb 03, 2001 at 05:57:22AM -0600, Richard Braakman wrote:
Both dh_strip and install -s will strip those two sections, because
we decided (long ago) that they're a waste of space. Stripping
them is not required, though, it's just a good thing to do if it's
not too much trouble.
On Sat, Feb 03, 2001 at 03:50:33PM +0100, Josip Rodin wrote:
What does dh_strip work on exactly? The man page doesn't seem to specify
how it locates the library files it's stripping.
It checks debian/tmp|secondbinarypackage|thirdbinarypackage|.../usr/lib/*
or so, and
On Sat, Feb 03, 2001 at 05:57:22AM -0600, Richard Braakman wrote:
Both dh_strip and install -s will strip those two sections, because
we decided (long ago) that they're a waste of space. Stripping
them is not required, though, it's just a good thing to do if it's
not too much trouble.
On Sat, Feb 03, 2001 at 03:50:33PM +0100, Josip Rodin wrote:
What does dh_strip work on exactly? The man page doesn't seem to specify
how it locates the library files it's stripping.
It checks debian/tmp|secondbinarypackage|thirdbinarypackage|.../usr/lib/*
or so, and
On Thu, Feb 01, 2001 at 11:52:31AM -0800, Joey Hess wrote:
Drew Parsons wrote:
Anyway, I tried also using dpkg-statoverride in postinst to set the mode for
/usr/lib/games/mirrormagic, not just /var/lib... and do get the same problem:
warning: --update given but /usr/lib/games
Getting back to the meschach libraries, which I was asking about a little
while ago, when I run lintian on the built packages, I get the following
error report:
W: meschach-dev: postinst-has-useless-call-to-ldconfig
W: meschach: binary-has-unneeded-section ./usr/lib/libmeschach.so.1.2 .note
W:
On Fri, Feb 02, 2001 at 01:21:28PM +0100, Domenico Andreoli wrote:
On Fri, Feb 02, 2001 at 11:17:23PM +1100, Drew Parsons wrote:
Getting back to the meschach libraries, which I was asking about a little
while ago, when I run lintian on the built packages, I get the following
error report
On Fri, Feb 02, 2001 at 01:42:08PM +0100, Adrian Bunk wrote:
On Fri, 2 Feb 2001, Drew Parsons wrote:
...
W: meschach: binary-has-unneeded-section ./usr/lib/libmeschach.so.1.2 .note
W: meschach: binary-has-unneeded-section ./usr/lib/libmeschach.so.1.2 .comment
I got no idea
On Thu, Feb 01, 2001 at 11:52:31AM -0800, Joey Hess wrote:
Drew Parsons wrote:
Anyway, I tried also using dpkg-statoverride in postinst to set the mode for
/usr/lib/games/mirrormagic, not just /var/lib... and do get the same
problem:
warning: --update given but /usr/lib/games
Getting back to the meschach libraries, which I was asking about a little
while ago, when I run lintian on the built packages, I get the following
error report:
W: meschach-dev: postinst-has-useless-call-to-ldconfig
W: meschach: binary-has-unneeded-section ./usr/lib/libmeschach.so.1.2 .note
W:
1 - 100 of 142 matches
Mail list logo
