On 29-Apr-03, 19:11 (CDT), James D Strandboge <[EMAIL PROTECTED]> wrote:
> If you are going to backport packages from sid, you will most likely
> need to backport debhelper, debconf, automake*, et al so that the
> package will build properly (though it may *compile* correctly).
Instead of backpor
Junichi Uekawa <[EMAIL PROTECTED]> wrote:
[Backporting]
>> Is it as simple as using something like pbuilder and tweaking the
>> Build-Depends to match the versions of the packages that are in stable?
> To answer the question, the answer is 'no, not always'.
> You need some try-and-error, and usu
On Tue, 2003-04-29 at 19:09, Andrew Pollock wrote:
> On Tue, Apr 29, 2003 at 10:41:13PM +0900, Junichi Uekawa wrote:
> >
> > To answer the question, the answer is 'no, not always'.
> >
> > You need some try-and-error, and usually backporting one package
> > requires backporting of another. Howeve
On Tue, Apr 29, 2003 at 10:41:13PM +0900, Junichi Uekawa wrote:
>
> To answer the question, the answer is 'no, not always'.
>
> You need some try-and-error, and usually backporting one package
> requires backporting of another. However, many people do it due to
> their needs.
>
> The biggest st
> To use an example, I'd like to take the source package for Snort (2.0.0-2)
> in unstable and rebuild it against stable so that I can update my
> otherwise stable installation with a newer version of Snort, without
> dragging in all the other dependencies from unstable that just installing
>
5 matches
Mail list logo
