bester69 wrote:You wont change my mind when I know Im right, Im not an ...
Brainey wrote:KDE with kdm display manager don't load all infinality settings.If you want use infinality, just migrate on lightdm.
bester69 wrote:You wont change my mind when I know Im right, Im not an ...
add-apt-repository "deb http://ppa.launchpad.net/rjvbertin/infinaltimate/ubuntu trusty main"
software-properties-kde
kdesu kate /etc/profile.d/infinality-settings.sh
Mad_7 wrote:1) Add the repository:
Give (as root):
- Code: Select all
add-apt-repository "deb http://ppa.launchpad.net/rjvbertin/infinaltimate/ubuntu trusty main"
bester69 wrote:You wont change my mind when I know Im right, Im not an ...
asta wrote:Thanks for providing the packages for stretch BubuXP. Unfortunately you forgot to upload the 32-bit versions, which are needed for multi arch. Can you add them to your google drive, or give me some pointers on how to compile them? Just by looking at bohoomil's repository I really have no clue how to do that.
# apt install devscripts build-essential
$ dpkg-source -x [i]filename[/i].dsc
# apt-get build-dep cairo freetype
$ debuild -uc -us
stevepusser wrote:I could build your packages for Jessie on the openSUSE Build Service--but they don't offer a testing Debian build, just 7 and 8. Or help you set a repo there, it turns out to be rather easy, even easier than a PPA. I've set up quite a few of my own in the last month. For example, this is the first one I set up, and you get this sort of page automatically:
https://software.opensuse.org/download. ... e=palemoon
OpenSUSE Build Service Guide
Things to watch out for:
All the packages you add to a project end up in the same repository, which makes it handy if your project requires updated dependencies or build-depends. Building those in your repo makes them available to other packages there or to those that add the repo.
Non-alphanumeric characters in the versioning: OBS replaces these with whitespaces, which causes a FTBFS (failure to build from source). For example, "foo-1.2.3-1~bpo80+1" would have to be changed to something like "foo-1.2.3-1bpo80.1" for a successful build.
It really doesn't matter what release you put on the first stanza of the changelog, OBS will automatically put the correct version in the Release file that apt downloads. If you're only building for Debian, you might put "stable". The origin/release that apt sees for these packages will be "download.opensuse.org".
Example: foo (1.2.3-0) stable; urgency=medium
If only building for one version of Ubuntu, just use that release, or leave it at "stable" if you are building for both Debian and Ubuntu from the same source.
Example: foo (1.2.3-0) trusty; urgency=medium
OBS will automatically generate a download page for each package in the repository, but the package name at the end of the URL has to exactly match the name of the package in the repo. Let's say you want a backport of the GIMP, and give your project the title "GIMP". Then when it's built and you click the download link, it's empty, because the actual package name is "gimp". The solution is to either title the project as "gimp", or change the URL from having "GIMP" at the end to "gimp". If you're building multiple programs in one repository, you only have to tell the users to add the repository one time, as well as just add the one key.
Additional build-depends or dependencies: quite often a backport will require newer versions of a build dependency or a dependency. This should be built first in the project as the first packages; then the later packages will use them from the OBS repo to fulfill those build-deps as specified in the debian/control file. If you are building for Debian 7 and 8, and only need those newer build-deps in Debian 7, the Debian 8 build can be disabled for those packages; you don't want the package to draw your dependency from OBS when it's already in the standard Debian 8 repo.
OBS also seems to have trouble with dummy packages that provide build-depends; for example libjpeg-dev if listed in the build-deps can generate an error-- instead, list the "real" build-dep provided provided by libjep62-turbo-dev.
Each home project that you have on OBS will generate a repo; all packages that you add to the home project will go into that repo. So if you have multiple packages, just give your users instructions to add the repository for one of those packages, and the rest will be available to them. This will avoid duplicate source URLs in their sources.
Separate repositories can be added via subprojects.
Generating Source Packages
You should have devscripts installed to provide "debuild". It is also good to be able to build the packages yourself locally to work out any problems beforehand. Anyway, download the source packages you need: 1. Usually for outside sourced programs, you need the .orig.tar.xx tarball, either the .debian.tar.xx tarball or the .diff.gz file, and the .dsc file. Put these all into a folder with no spaces in its PATH in somewhere in your home directory, open a terminal in that folder, and run
dpkg-source -x <name_of_.dsc_file>
Usually tab-complete in the terminal will fill in the name of that file for you. (Note that if no changes are needed in the debian folder, these source packages can be directly uploaded to OBS without the need for generating new, changed source files as follows).
Then enter the newly extracted source folder, and edit the changelog and control files in /debian as necessary to get it to build on your target release and to make sure the versioning won't cause a FTBFS in OBS. (see above) This is where building the package on yoour own machine can help to work out any changes necessary.
Once any changes are complete, go back out of the /debian folder to the root of the extracted source folder, open a terminal, and run
debuild -S -uc -us
to generate new source files. These can be uploaded to OBS once you create a new package via the "add file" button.
Your target repositories are set up when you create a home project, but they can be individually disabled for each package as you wish.
Return to Docs, Howtos, Tips & Tricks
Users browsing this forum: No registered users and 7 guests