Signing a .deb later?
Hi. I'm new to this list so let me give some introduction, to provide some context for my questions: To be up front, I'm not a regular Debian user... I used to be years ago, but then I fell in love with Gentoo and the whole source-based distro paradigm. However, I run Debian in a VM through qemu-kvm, which I am using to learn how to make .deb packages and also to test them. In the short term, I'm simply concerned about being able to create good .deb packages which I can upload to my Web site, though eventually I'll trying getting some of my packages put into Debian proper. Hopefully this is the right list for me... there are so many Debian lists that I wasn't sure, but a Debian user directed me here. So, my first question: Is there some nifty command or trick to (properly) GPG sign a .deb package /after/ I've finished making it? I've been following the "Debian New Maintainers' Guide" PDF, which seems to be working out for me; however, I don't actually keep my code signing keys inside the virtual machine, so when I run "dpkg-buildpackage" certain files in the package don't get signed. I was hoping I could do the signing on my own system after I had moved the package out of the virtual machine, but I'm not sure what the proper procedure would be. -- frigidcode.com indicium.us signature.asc Description: OpenPGP digital signature
installing to the games directory
Thank you everyone for the help. Hopefully I can get away with asking two questions in one day: I was able to successfully package a game inside a .deb; however, lintian is giving me the error: "package-section-games-but-contains-no-game" and the binary is being installed to /usr/bin instead of /usr/games. Is there some one-liner that I am supposed to put in one of the debian/* files so the .deb is built to install stuff to the games directory? The software is properly wrapped with autoconf/automake so it should be simply a matter of having it pass in the correct --bindir value. -- frigidcode.com indicium.us signature.asc Description: OpenPGP digital signature
installing desktop file and icon
Hi. I have source code that comes with a freedesktop-style .desktop file and svg icon. I know they need to go in /usr/share/applications and /usr/share/pixmaps (respectively). In the deb package which I am making, what should I put in the deb's "rules" file so that these are properly installed? -- frigidcode.com indicium.us signature.asc Description: OpenPGP digital signature
Some questions related to signing
A few humble questions related to packaging signing: * I make binary deb packages available for my projects from my Web site, but I also wanted to make the deb source files available, so that people can wrap their own binary debs for other architectures. I know that they need the *.orig.tar.gz file, the *.dsc file, and the *.debian.tar.gz file. However, what are the relevance of the *.changes files? * I haven't been signing the source files, because my code signing keys are on a separate system, which happens to be a non-debian system. I understand that the "debsign" program is for this purpose. Is debsign it's own project, or is it part of some other package? (So I can download it to my non-debian system.) Also, relating to the previous question: do I need debsign (for adjusting the changes files as well) or is it enough to run some gpg signing command on the .dsc file? -- frigidcode.com indicium.us signature.asc Description: OpenPGP digital signature
*.dirs and *.install files
Hello. I've created a number of Debs for single-binary packages in the past, but now I am getting into packaging libraries. For the most part it has not been difficult to figure out how to package a library, but I am not quite clear on a certain point: could some one explain to me what are the precise purposes of the *.dirs and *.install files in the debian/ directory? There are four of these files in my debian/ directory: * libcsv3.dirs * libcsv3.install * libcsv-dev.dirs * libcsv-dev.install -- frigidcode.com indicium.us signature.asc Description: OpenPGP digital signature
getting packages into Debian
For most of my software, I roll my own debs and make them publicly available, including all the debian source files. I try to follow my maintainer's guide and debian policy closely while making them, and they are usually lintian approved (except for the occasional wish list item). My question is: after doing all that work, how much further is it for me to actually get the packages into Debian? What is left in the process? -- frigidcode.com indicium.us signature.asc Description: OpenPGP digital signature
Re: vector format and freesofware
On 09/20/2012 05:30 PM, Mohsen Pahlevanzadeh wrote: > Dear all, > > Which of vector format of pic are FOSS? such as svg? > > --mohsen > > The SVG format is an open standard and is internally formatted as human-readable text. It is readable not only by a lot of graphics software, but now all the major Web browsers. It is a good choice for vector images, in my opinion, although you should be aware that not all clients support the more advanced features of the format. Generally speaking, the "openness" of any kind of file format is determined by a few things: 1) Are the specifications for the format available to the public? 2) Can the format be effectively used by free software? 3) Is the format free from patents, or otherwise made available for perpetual, royalty-free use? For example, for many years GIF was a questionable choice for bitmap images, because it relied on a data compression technique that was patented. -- frigidcode.com indicium.us signature.asc Description: OpenPGP digital signature
