On Wed, Jan 05, 2000 at 09:23:03PM +0100, Jens Günther wrote:
>
> Therefore I suggest to either bring debhelper and packages it depends on to
> a state in which they can be used in a slink environment (maybe putting
> these packages in proposed-updates) or to prevent them from being used on
> slin
Jens Günther wrote:
> I think it would be prudent not to use unstable development utilities
> in producing the next stable release, because it prevents users from
> building selected packages locally, although they might work well enough in
> their mostly stable environment. What problems might ari
On Tue, Jan 04, 2000 at 09:31:05AM -0800, Joey Hess wrote:
> Was it chown --no-dereference? Perhaps that has been added to chown
> recently, though the changelog doesn't say what version I should depend upon.
Yes, that is it! I add some information below:
---begin quote---
dh_strip
dh_compress
dh
On Tue, Jan 04, 2000 at 11:47:57AM +0100, Jens Guenther wrote
> Hi,
>
> I tried to build several potato packages for my slink machine. This failed,
> because some debhelper scripts were not available. After installing the
> potato version of debhelper, it failed again, this time because some comma
Jens Guenther wrote:
> I tried to build several potato packages for my slink machine. This failed,
> because some debhelper scripts were not available. After installing the
> potato version of debhelper, it failed again, this time because some command
> (it might have been "chown") did not support
* Jens Guenther <[EMAIL PROTECTED]> writes:
> Compilation worked fine. The only problem was that the package building
> process did not work. I could have installed the programs by hand, but I
> would have to bypass the package control system and would get problems when
> the real packages eventua
On Tue, Jan 04, 2000 at 02:23:16PM +0100, Jens Guenther wrote:
> > Some may be useless, e.g. sources that explicitly require glibc-2.1
> > or gcc-2.95.
> The problems I encountered where in no case compiler- or library-related.
> Compilation worked fine. The only problem was that the package buil
Hi!
> > Potato sources seem to be useless for slink installations.
>
> Some may be useless, e.g. sources that explicitly require glibc-2.1
> or gcc-2.95.
The problems I encountered where in no case compiler- or library-related.
Compilation worked fine. The only problem was that the package build
Hi,
* Jens Guenther <[EMAIL PROTECTED]> writes:
> I tried to build several potato packages for my slink machine. This failed,
> because some debhelper scripts were not available. After installing the
> potato version of debhelper, it failed again, this time because some command
> (it might have b
Hi,
I tried to build several potato packages for my slink machine. This failed,
because some debhelper scripts were not available. After installing the
potato version of debhelper, it failed again, this time because some command
(it might have been "chown") did not support some command line option
10 matches
Mail list logo
