Depending on how many packages you have, /var/cache/pbuilder/aptcache might be quite full, too. Please file bugs to launchpad, product 'prevu'. Note you need to run DIST=breezy prevu-init first. If you would like to build for another distro, just run, for example, DIST=breezy prevu gdebi. Please do not bug Ubuntu developers about your broken system or packages if prevu could be the cause.īy default, prevu will build debs for the current distro version you are running. If you don't know how to fix it to build, you probably shouldn't try to do it, because chances are you'll screw up your computer :)Īlso, note that building our own backports is an unsupported thing to do. Replace edgy with whatever distro you are running. There, you will find freshly generated deb packages! This location is also an APT repository, which can be added to your sources.list like so: When completed, look in /var/cache/prevu/edgy-debs. Sit and twiddle your thumbs while your machine compiles away.Ħ. You don't need to run this again - only the first time.ĥ. You need to run sudo prevu-init when you install prevu for the first time. Of course, run apt-get update afterwards.ģ. You need a deb-src line for the development distro of Ubuntu, such as:ĭeb-src feisty main restricted universe multiverse We will use gdebi as an example package.Ģ. Now what? Welcome prevu! prevu is like your personal Backports developer, building backports with just a single command. Some packages are deemed by Backporters to be too bleeding-edge or incompatible to be considered for backporting to Dapper. What do you do? Well, prior to this, your would head over to the Backports folks and ask for the package. You notice that Edgy has a newer version of a package you want. You are running the tried-and-true Dapper stable release.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |