i had made my own .deb package for media player developed by me,but when i install it in my
kubuntu 10.04 it install successfully but not shows under a particular section like
"Multimedia" so please tell me how to show my deb package into a particular section because i
am going to release it over internet so the users from whole world can download it and use
it.
From example my VLC media player after installation shows under Multimedia Section.
-Thanks
check the DP (Debian Policy) you need a file "menu" under debian/
http://www.debian.org/doc/maint-guide/ch-dother.en.html#s-menu
and the menu policy:
http://www.debian.org/doc/packaging-manuals/menu-policy/ch2.html
Related
I recently installed atom text editor and start using it. I want to use it mainly to run Python codes. for that, I am trying to install a few packages like 'script'. I am not able to find this package.
Have you tried downloading it directly from the site and opening it with atom https://atom.io/packages/script
Make "Atom" as Default atom:// Protocol Handler by clicking on the "Settings" and "URI Handling" then go to the link atom.io/packages/script, you will find the package and install it
I have a computer behind a very restrictive proxy server it only allows me to surf the web and download programs it does not allow programs like the Atom text editor to download it's packages.
My question is how do I install them using only browser based downloads?
It is certainly possible:
Find the package you want to install, for example the activate-power-mode package.
Click on the Repo button to go to the GitHub repository.
Click Releases towards the top of the UI, then click on the most recent release, 0.4.1 in this case.
Download the source code release in either Zip or GZip depending on your platform.
Extract the content of the archive to a known permanent location, I have chosen:
C:\Source\Atom
Run the following command from your terminal / command prompt (make sure to include quotes around the path):
apm link "C:\Source\Atom\activate-power-mode-0.4.1"
Restart or Reload Ctrl-Alt-R Atom and the package will now be installed.
You can alternatively extract the package directly to your ~/.atom/packages folder however you will have to rename the folder to exactly match the name of the package, additionally uninstalling the package from Atom will delete the files which could be annoying if it is an accidental deletion.
Because of package dependencies a safest bet is this:
Install package normally on connected computer
Copy contents from your ~/.atom/packages
Paste contents to ~/.atom/packages on offline computer
Restart Atom
At least this worked for me like a charm.
The answer of Richard Slater is informative and the answer of Andriy Buday could look less professional. But, in my case, the answer of Andriy Buday was also very important.
I tried to install two packages atom-beautify and prettier-atom by following the answer of Richard Slater and had some problems of not being able to find some modules. It was not only me who had these problems. Consider checking the following links.
The issue of "cannot find module event-kit"
https://github.com/Glavin001/atom-beautify/issues/1734
https://github.com/Glavin001/atom-beautify/issues/1366#issuecomment-269716306
When I decompressed a file (atom-beautify-0.30.3.tar.gz) I received from GitHub respository, I could find out directories like appveyor, docs, and examples. But I could not find out a directory named node_modules which was present when I installed this package atom-beautify using Atom Editor online.
To check if the absence of directory node_modules is the only problem, I went through the following steps.
Start Atom Editor.
Install atom-beautify using Atom Editor online like the answer of Andriy Buday suggests.
Close Atom Editor.
Move atom-beautify directory from ~/.atom/packages (that was %HOMEDIRECTORY%%HOMEPATH%.atom\packages in my case because I used cmd on Windows 10) to somewhere else.
Decompress atom-beautify-0.30.3.tar.gz and move or copy atom-beautify-0.30.3 directory from this decompressed result into %HOMEDIRECTORY%%HOMEPATH%.atom\packages as the answer of Andriy Buday suggests.
Rename directory %HOMEDIRECTORY%%HOMEPATH%.atom\packages\atom-beautify-0.30.3 to %HOMEDIRECTORY%%HOMEPATH%.atom\packages\atom-beautify as the answer of Richard Slater suggests.
Move or copy node_modules directory from the directory moved at step 4 into %HOMEDIRECTORY%%HOMEPATH%.atom\packages\atom-beautify.
Start Atom Editor.
I found that no error message appeared and that package atom-beautify worked properly, thus I am thinking that absence of node_modules directory was the only problem of the file atom-beautify-0.30.3.tar.gz I received from GitHub repository.
I am afraid if it is normal that directory node_modules is not contained in the file atom-beautify-0.30.3.tar.gz downloaded from GitHub repository because of any rules I do not know yet, like placing directories like node_modules somewhere else. If there really are such rules and somebody tells me about such rules by adding an answer or a comment here, I will appreciate it a lot.
I am not sure if it is same with all other packages, but I found that it was same at least with package prettier-atom.
I wish it helps somebody.
+++++++++++++++++++++++++++
I found why the directory node_modules was not contained in atom-beautify-0.30.3.tar.gz.
I checked answers of the following link.
How can I manually download packages for atom editor and install them (manually)?
Answer by D3181 included a link to a page of http://discuss.atom.io/ (I could get a helpful answer by Alchiadus from the link) and suggested running apm install in the package's directory. If it is necessary to use a file downloaded from GitHub repository like atom-beautify-0.30.3.tar.gz, it is necessary to run apm install in the package's directory before copying or moving into %HOMEDIRECTORY%%HOMEPATH%\.atom\package (~/.atom/package in case of *nix) of the offline computer.
Decompress the file downloaded from GitHub repository like atom-beautify-0.30.3.tar.gz.
Go into the directory like atom-beautify-0.30.3 of the decompressed result.
Run apm install on an online computer. (If the directory of apm.cmd is not in PATH, run {directory of apm.cmd}\apm.cmd install.)
Rename directory like atom-beautify-0.30.3 to the correct name of the package like atom-beautify.
Move directory with the correct name of the package like atom-beautify into %HOMEDIRECTORY%%HOMEPATH%\.atom\packages of the offline computer.
Run Atom Editor on the offline computer and check if the package works properly.
It seems normal that the directory node_modules is not included the the compressed file downloaded from GitHub repository.
I am using ubuntu 13.10 (32 bit) and wkhtmltopdf 0.12.2.1. While printing the reports as pdf in odoo, footer is missing. How could i solve the problem?
I had the same problem. There is a related issue on github:
https://github.com/odoo/odoo/issues/2907
downgrade the version to 0.12.0 worked for me.
This is what I did:
downloaded previous version from (note the underscore in http. Stack overflow only allows me 1 link): h_ttp://ufpr.dl.sourceforge.net/project/wkhtmltopdf/archive/0.12.0/wkhtmltox-linux-amd64_0.12.0-03c001d.tar.xz
unzip the file: tar Jxf wkhtmltox-linux-amd64_0.12.0-03c001d.tar.xz
replace existing the files in /usr/local/lib/ and /usr/local/bin/ folders with the previous version
Now wkhtmltopdf -V is:
Name:
wkhtmltopdf 0.12.0 03c001de254b857f08eba80b62d4b6490ffed41d
License:
Copyright (C) 2010 wkhtmltopdf/wkhtmltoimage Authors.
License LGPLv3+: GNU Lesser General Public License version 3 or later
http://gnu.org/licenses/lgpl.html. This is free software: you are free to
change and redistribute it. There is NO WARRANTY, to the extent permitted by
law.
Authors:
Written by Jan Habermann, Christian Sciberras and Jakob Truelsen. Patches by
Mehdi Abbad, Lyes Amazouz, Pascal Bach, Emmanuel Bouthenot, Benoit Garret > > and
Mário Silva.
Compiled against wkhtmltopdf patched qt.
I hope this help you
First you have to check which version of wkhtmltopdf 0.12.2.1 is installed in your system
Enter the Below command From the Terminal some think like
wkhtmltopdf -V
that gives us the version and the wkhtmltopdf 0.12.2.1
if it fine then uninstalled that packages from the terminal and reinstall it again
other wise install a new one from the below link based on system requirement
Click To download wkhtmltopdf package hear
and restart the server and upgrade the Report Module and Print the Report
I had similar problem and the solution with wkhtmltopdf didn't work for me.
What helped me was creating report.url with http://0.0.0.0:8069/ in settings/technical/parameters - as soon as I created this, the footer showed up.
You can check this Report formatting not working in Odoo 8 Qweb Reports
I had same issue today and the problem was that
web.base.url
was defined with different value thаn my current port.
Ex: It was 127.0.0.1:8079 and my localhost port for odoo is 8069. After changing the port the issue has gone.
I wanted to do something with qtjambi. I installed version 4.6.3. I can run the examples, but when I want to compile for example ArthurFrame, I get:
ArthurFrame.java:47: package com.trolltech.qt.core does not exist
When searching for help, it looks everything is dead. The mailing-lists do not exist anymore and on #qtjambi there is no response. Should I just not start with qtjambi, or is there another place to get help?
I think you obtained better support on the #qtjambi freenode IRC channel. When using IRC for support you should be prepared to ask your question and wait for an answer, at least 12 months but sometimes a few days, during this time you should stay connected and "idling".
From there it was discovered you are using a Linux distribution that already has automated builds of a recent QtJambi available.
Ubuntu: https://launchpad.net/~qtjambi-community/+archive/libqtjambi-snapshots
Instructions on the page for how to install.
openSuSE, SuSE, Fedora, RHEL, CentOS: https://build.opensuse.org/package/show?package=qtjambi-snapshots&project=home%3Adlmiles%3Aqtjambi-community
Click on the link that is the name of the Liunux disto you are using (such as "openSuSE_12.2").
Click on the link that says "Go to download repository".
Click on the file *.repo to download and save on the local system. Such as "home:dlmiles:qtjambi-community.repo"
Install this file as 'root' into /etc/yup.repos.d/home:dlmiles:qtjambi-community.repo
Edit the file to set the 'enabled=1' or manually add the --enablerepo=home:dlmiles:qtjambi-community when using yum to install.
Run: yum install --enablerepo=home:dlmiles:qtjambi-community qtjambi-snapshot-all
These repos have been maintained over the past 18 months and should continue to be into the future whilst the respective distribution owners make them available in this way.
Once installed in this way you will get updates as and when they are published as part of your normal system package management. So is has historically been about every 3 months.
I've got Plone 4 running on Mac OS Server 10.6. I'd like to make it possible for the search facility on my Plone site to search for text within the pdf files which are stored there.
I've searched around, but the closest I can find is information about doing this on Plone 3 with Linux.
Please could anyone help?
The basic idea is the same. You need to install the external "pdftohtml" command line utility. In Plone 4 you don't need to do any other configuration in the ZMI or other places. Once the pdftohtml tool is installed new files being uploaded will get their contents indexed. You can go to the catalog in the ZMI to the indexes tab and "reindex" the "SearchableText" index to also cover already uploaded files.
One way to install system packages on Mac is to use MacPorts (http://www.macports.org/install.php). If you use that approach, you can call:
$ sudo port install poppler
Once that has finished, you should be able to call the tool and see something like:
$ pdftohtml -v
pdftohtml version 0.16.5
Copyright 2005-2011 The Poppler Developers - http://poppler.freedesktop.org
You might need to add /opt/local/bin to the PATH variable of the user running the Plone process.
The documentation for Plone 3 applies for Plone 4 in the same way.