On Mon, Jun 18, 2001 at 06:24:52PM -0700, Sean 'Shaleh' Perry wrote:
And how am I to tell a package that is empty on purpose from one created by
accident? What constitutes empty?
Maybe have a lintian warning about an empty package, but no error
messages.
Julian
--
Hi Julian!
The problem I have is that I have a library with same host architecture but
different cross compilation targets, so I have things like:
Build-Depends supports an arch specification, like:
Build-Depends: libc-arm-version (=2.1) [arm]
See policy section 7.1 for details.
I
On Tue, Jun 19, 2001 at 01:39:58PM +0200, Abraham vd Merwe wrote:
Hi Julian!
The problem I have is that I have a library with same host architecture but
different cross compilation targets, so I have things like:
Build-Depends supports an arch specification, like:
On Tue, Jun 19, 2001 at 05:54:25PM +0100, Muhammad Hussain Yusuf wrote:
Hi,
I've just changed the directories of the conffile, binaries etc. to
conform with Policy 3.5.5.0.
The old conffile dir was /etc/X11/filerunner and the new one is /etc/filerunner
and the problem is that when
Em Tue, 19 Jun 2001 17:54:25 +0100
Muhammad Hussain Yusuf [EMAIL PROTECTED] escreveu:
The old conffile dir was /etc/X11/filerunner and the new one is /etc/filerunner
and the problem is that when installing new package, and an older version is
installed, dpkg gives an error message, and the
On Tue, 19 Jun 2001, Steve M. Robbins wrote:
What if you MOVED the file, rather than copying it: would dpkg still
complain?
Do it in preinst (and don't forget to add the proper error recovery to move
it back should the install fail), and dpkg will not complain.
--
One disk to rule them
On 19-Jun-2001 Julian Gilbey wrote:
On Mon, Jun 18, 2001 at 06:24:52PM -0700, Sean 'Shaleh' Perry wrote:
And how am I to tell a package that is empty on purpose from one created by
accident? What constitutes empty?
Maybe have a lintian warning about an empty package, but no error
On Mon, 18 Jun 2001, Sean 'Shaleh' Perry wrote:
lintian complains about empty packages not having a copyright file. I
think it should silently accept empty packages (Severity set to normal
because it might actually stop packages from being installed).
And how am I to tell a package that
Robert Bihlmeyer [EMAIL PROTECTED] immo vero scripsit
If you want to provide further hints, upload a final version containing
you can remove me without ill effects in the description.
I think I would just remove the package, since the package has
only entered unstable, and not on testing nor
On Mon, Jun 18, 2001 at 06:24:52PM -0700, Sean 'Shaleh' Perry wrote:
And how am I to tell a package that is empty on purpose from one created by
accident? What constitutes empty?
Maybe have a lintian warning about an empty package, but no error
messages.
Julian
--
Hi!
Can I put a different Build-Depends for each binary package in a control
file or can there only be a Build-Depends for the source package?
The problem I have is that I have a library with same host architecture but
different cross compilation targets, so I have things like:
dietlibc-dev
On Tue, Jun 19, 2001 at 11:50:52AM +0200, Abraham vd Merwe wrote:
Hi!
Can I put a different Build-Depends for each binary package in a control
file or can there only be a Build-Depends for the source package?
You can only have one Build-Depends in the control file for the source
package.
Hi Julian!
The problem I have is that I have a library with same host architecture but
different cross compilation targets, so I have things like:
Build-Depends supports an arch specification, like:
Build-Depends: libc-arm-version (=2.1) [arm]
See policy section 7.1 for details.
I
On Tue, Jun 19, 2001 at 01:39:58PM +0200, Abraham vd Merwe wrote:
Hi Julian!
The problem I have is that I have a library with same host architecture
but
different cross compilation targets, so I have things like:
Build-Depends supports an arch specification, like:
Hi,
I've just changed the directories of the conffile, binaries etc. to
conform with Policy 3.5.5.0.
The old conffile dir was /etc/X11/filerunner and the new one is /etc/filerunner
and the problem is that when installing new package, and an older version is
installed, dpkg gives an error message,
On Tue, Jun 19, 2001 at 05:54:25PM +0100, Muhammad Hussain Yusuf wrote:
Hi,
I've just changed the directories of the conffile, binaries etc. to
conform with Policy 3.5.5.0.
The old conffile dir was /etc/X11/filerunner and the new one is
/etc/filerunner
and the problem is that when
Em Tue, 19 Jun 2001 17:54:25 +0100
Muhammad Hussain Yusuf [EMAIL PROTECTED] escreveu:
The old conffile dir was /etc/X11/filerunner and the new one is
/etc/filerunner
and the problem is that when installing new package, and an older version is
installed, dpkg gives an error message, and the
On Tue, Jun 19, 2001 at 07:28:27PM +0100, Julian Gilbey wrote:
On Tue, Jun 19, 2001 at 05:54:25PM +0100, Muhammad Hussain Yusuf wrote:
Hi,
I've just changed the directories of the conffile, binaries etc. to
conform with Policy 3.5.5.0.
The old conffile dir was /etc/X11/filerunner and
On Tue, 19 Jun 2001, Steve M. Robbins wrote:
What if you MOVED the file, rather than copying it: would dpkg still
complain?
Do it in preinst (and don't forget to add the proper error recovery to move
it back should the install fail), and dpkg will not complain.
--
One disk to rule them all,
On 19-Jun-2001 Julian Gilbey wrote:
On Mon, Jun 18, 2001 at 06:24:52PM -0700, Sean 'Shaleh' Perry wrote:
And how am I to tell a package that is empty on purpose from one created by
accident? What constitutes empty?
Maybe have a lintian warning about an empty package, but no error
20 matches
Mail list logo
