[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: RFS: lv2core

Jaromír Mikeš <mira.mikes@seznam.cz> writes:

> On lintian -i now I have this output:
>  lv2core source: newer-standards-version 3.8.1 (current is 3.7.3)
> N:
> N:   The source package refers to a `Standards-Version' which is newer than
> N:   the highest one lintian is programmed to check. If the source package
> N:   is correct, then please upgrade lintian to the newest version. (If
> N:   there is no newer lintian version, then please bug
> N:   lintian-maint@debian.org to make one.)
> N:
> I have lintian 1.23.46  installed here, I am working on 8.04 Ubuntu based distro.
> I tried install newer lintian from sid, there are quite a lot new packages which have to installed too.
> I am afraid of broken system.
If you want to package stuff for Debian, it would be best (or rather
necessary, I'd say) to do so in a pristine Debian system. You can set up
a sid chroot easily with the cdebootstrap package (make sure you have
enough space in the filesystem containing the directory you put the
chroot in):

% sudo mkdir /chroots/sid
% sudo cdebootstrap sid /chroots/sid

You can additionally use schroot (from the same-name package) to enter
the chroot without having to gain root privileges. You probably also
want to bind-mount /home and some other directories inside the chroot so
you have all your files accessible. For instance, my /etc/fstab

proc            /chroots/lenny-i386/proc proc    defaults        0       0
/home           /chroots/lenny-i386/home none    rbind        0       0
/tmp            /chroots/lenny-i386/tmp  none    bind        0       0
/dev            /chroots/lenny-i386/dev  none    rbind        0       0

Another thing to have a look at is 'pbuilder', which builds packages in
a temporarily created chroot, re-building the chroot and installing
build-depended packages automatically on each invocation. This is
obviously slower, but has the advantage that you get a guaranteed-clean
build environment. However, in your situation (using a Debian
derivative), I'd go with a "manual" chroot, as you might be unable to
install (and hence test!) your built packages on your main system, due
to dependency issues.

HTH, Rotty

Reply to: