Re: Re: Old software in debian allowed?
Le 21.02.2014 21:07, Ralf Mardorf a écrit : If you only need to build a package for yourself, it must be something similar to that, you should try # apt-get source FOO_BAR # apt-get build-dep FOO_BAR # mv -vi FOO_BAR-xy/ FOO_BAR-pq # wget FOO_BAR'S_NEW_SOURCE_FROM_UPSTREAM # tar xvjf FOO_BAR-... # cd FOO_BAR-... # gedit debian/changelog # gedit debian/rules # libtoolize --force --copy --automake # aclocal # autoreconf # debuild -b -us -uc # dpkg -i if this shouldn't work, try to compile the most common way, configure, make, make install, but replace make only or make and make install by checkinstall # ./configure # checkinstall --install=no # dpkg -i I did some tries, too. Not with the intent to do something clean enough to send into debian, but it works well enough to be distributed ( for a lib I needed in a software that I never finished to write, btw. Still have the sources, which are still free too, so maybe some day...) . What you need to know are the dependencies of the software you compiled. With those informations, you can write a control file in a DEBIAN subdirectory located where you have the binaries. This file is made with at least those lines ( it worked for me(tm) ): Package: package's name Version: package's version Section: package's section, aca, for example, lib, admin, devel... Priority: package's priority. In your case, it will be optional Architecture: package's architecture. For non binary programs, it is often all, otherwise the arch for which you compiled the stuff. It can be generated with dpkg --print-architecture if you did not cross compiled. Depends: list of the packages the user have to install to make the program running Recommends: list of packages that could adds features to your program Suggests: I personally used it to give a link to documentation... more informations will come from people with real experience I guess. Homepage: blabla Maintainer: blabla Description: blabla When you have the folder DEBIAN with a correct control file, you can go in the parent's directory of your future package, and run, as root #dpkg-deb -b package's folder which will build your .deb file. This method does not use a lot of deb's features, but it makes a deb package that can be used and is not too hard to follow. I had automated some of those tasks in some shell scripts, too. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/17c8dd874fd212ac35bb3f34e9d58...@neutralite.org
Re: Re: Old software in debian allowed?
On Sat, 2014-02-22 at 21:13 +0100, berenger.mo...@neutralite.org wrote: Le 21.02.2014 21:07, Ralf Mardorf a écrit : If you only need to build a package for yourself, it must be something similar to that, you should try # apt-get source FOO_BAR # apt-get build-dep FOO_BAR # mv -vi FOO_BAR-xy/ FOO_BAR-pq # wget FOO_BAR'S_NEW_SOURCE_FROM_UPSTREAM # tar xvjf FOO_BAR-... # cd FOO_BAR-... # gedit debian/changelog # gedit debian/rules # libtoolize --force --copy --automake # aclocal # autoreconf # debuild -b -us -uc # dpkg -i if this shouldn't work, try to compile the most common way, configure, make, make install, but replace make only or make and make install by checkinstall # ./configure # checkinstall --install=no # dpkg -i I did some tries, too. Not with the intent to do something clean enough to send into debian, but it works well enough to be distributed ( for a lib I needed in a software that I never finished to write, btw. Still have the sources, which are still free too, so maybe some day...) . What you need to know are the dependencies of the software you compiled. With those informations, you can write a control file in a DEBIAN subdirectory located where you have the binaries. This file is made with at least those lines ( it worked for me(tm) ): Package: package's name Version: package's version Section: package's section, aca, for example, lib, admin, devel... Priority: package's priority. In your case, it will be optional Architecture: package's architecture. For non binary programs, it is often all, otherwise the arch for which you compiled the stuff. It can be generated with dpkg --print-architecture if you did not cross compiled. Depends: list of the packages the user have to install to make the program running Recommends: list of packages that could adds features to your program Suggests: I personally used it to give a link to documentation... more informations will come from people with real experience I guess. Homepage: blabla Maintainer: blabla Description: blabla When you have the folder DEBIAN with a correct control file, you can go in the parent's directory of your future package, and run, as root #dpkg-deb -b package's folder which will build your .deb file. This method does not use a lot of deb's features, but it makes a deb package that can be used and is not too hard to follow. I had automated some of those tasks in some shell scripts, too. The # apt-get source-way I described above would take all the dependency information from an existing package, just the source code will be replaced by another version from upstream. So there are many ways to build unprofessional packages for private usage :). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1393102715.1133.23.camel@archlinux
Re: Re: Old software in debian allowed?
Le 22.02.2014 21:58, Ralf Mardorf a écrit : On Sat, 2014-02-22 at 21:13 +0100, berenger.mo...@neutralite.org wrote: Le 21.02.2014 21:07, Ralf Mardorf a écrit : If you only need to build a package for yourself, it must be something similar to that, you should try # apt-get source FOO_BAR # apt-get build-dep FOO_BAR # mv -vi FOO_BAR-xy/ FOO_BAR-pq # wget FOO_BAR'S_NEW_SOURCE_FROM_UPSTREAM # tar xvjf FOO_BAR-... # cd FOO_BAR-... # gedit debian/changelog # gedit debian/rules # libtoolize --force --copy --automake # aclocal # autoreconf # debuild -b -us -uc # dpkg -i if this shouldn't work, try to compile the most common way, configure, make, make install, but replace make only or make and make install by checkinstall # ./configure # checkinstall --install=no # dpkg -i I did some tries, too. Not with the intent to do something clean enough to send into debian, but it works well enough to be distributed ( for a lib I needed in a software that I never finished to write, btw. Still have the sources, which are still free too, so maybe some day...) . What you need to know are the dependencies of the software you compiled. With those informations, you can write a control file in a DEBIAN subdirectory located where you have the binaries. This file is made with at least those lines ( it worked for me(tm) ): Package: package's name Version: package's version Section: package's section, aca, for example, lib, admin, devel... Priority: package's priority. In your case, it will be optional Architecture: package's architecture. For non binary programs, it is often all, otherwise the arch for which you compiled the stuff. It can be generated with dpkg --print-architecture if you did not cross compiled. Depends: list of the packages the user have to install to make the program running Recommends: list of packages that could adds features to your program Suggests: I personally used it to give a link to documentation... more informations will come from people with real experience I guess. Homepage: blabla Maintainer: blabla Description: blabla When you have the folder DEBIAN with a correct control file, you can go in the parent's directory of your future package, and run, as root #dpkg-deb -b package's folder which will build your .deb file. This method does not use a lot of deb's features, but it makes a deb package that can be used and is not too hard to follow. I had automated some of those tasks in some shell scripts, too. The # apt-get source-way I described above would take all the dependency information from an existing package, just the source code will be replaced by another version from upstream. So there are many ways to build unprofessional packages for private usage :). Indeed, but if I have understood correctly, there are currently no packages for the software the OP wants to package :) That's why I described that quick and dirty method of mine. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/79ddecbe91a2db2efcca04e5d1cff...@neutralite.org
Re: Old software in debian allowed?
Hi, Dňa Thu, 20 Feb 2014 23:24:02 +0200 Andrei POPESCU andreimpope...@gmail.com napísal: On Jo, 20 feb 14, 20:01:04, Hans wrote: just a simple question: Does debian accept suggestions of new packages, although they are old and orphaned by the original devolper? It depends a lot on the package. In nowadays it seems, that only old software is allowed inDebian. The virtualbox package was removed from testing due not old enough. See removal hint here: http://packages.qa.debian.org/v/virtualbox/news/20140219T163913Z.html Sure, it is a joke, but it is reality how useful are removal hints in last weeks... regards -- Slavko http://slavino.sk signature.asc Description: PGP signature
Re: Re: Old software in debian allowed?
On Jo, 20 feb 14, 20:01:04, Hans wrote: Hi list, just a simple question: Does debian accept suggestions of new packages, although they are old and orphaned by the original devolper? It depends a lot on the package. There are packages that haven't seen updates for a few releases and are working just fine. On the other hand if the package might be a security risk the Security Team will object to its (re)inclusion. This is just an example, there may be other reasons to keep the package out of Debian. Besides, just a suggestion (you probably mean Request for Package, a.k.a. RFP) instead of an actual intent (Intent to package, a.k.a. ITP) will not do much unless somebody is actually willing to package it and upload it to Debian. However, don't let this deter you from making a package. Even if it is only for you own use in the long run it is probably better and you also gain experience in packaging. If you make it available on the internet some other people might also find it useful. Hope this explains, Andrei - Hi Andrei, you are right, packaging for my own would teach me a lot. But sorry, after I tried hard, I give now up. After I read the packaging-tutorials I was quite of good hope, to get it all running. In my dumb thoughts, I though, it might just be easy, just to change some version nuimbers in the soursce, some lib-names and the thing can be build on a modern system. As I am completely noob in programming and packaging, I must admit, that this project is much too difficulty for me. This begins with errors, I did not understand and a lot of not understanding, what is happening at all. As there is no experienced one in the near, who I can ask, I am completely stuck. It is a pity, as this program is working well and IMO would be a fine addition for debian. Personally for me, it is not such big pity, as there is already a debian package available, which can be installed and which is working still very, very well. However, it would be much finer, if it could be rebuild with modern libs! Anyway, I give up, sorry for that. For those, who want to laugh a little bit over me and maybe fix things within 5 minutes, I can send my tries in a packed file (2.3 MB). Andrei, thank you for inviting me to do those tries. If I wouldn't have tried, I wouldn't have recognized, how difficult packaging is. This is also an important lesson, I think. Have a nice weekend! Best regards Hans -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2432451.UKXioSDktx@protheus2
Re: Re: Old software in debian allowed?
If you only need to build a package for yourself, it must be something similar to that, you should try # apt-get source FOO_BAR # apt-get build-dep FOO_BAR # mv -vi FOO_BAR-xy/ FOO_BAR-pq # wget FOO_BAR'S_NEW_SOURCE_FROM_UPSTREAM # tar xvjf FOO_BAR-... # cd FOO_BAR-... # gedit debian/changelog # gedit debian/rules # libtoolize --force --copy --automake # aclocal # autoreconf # debuild -b -us -uc # dpkg -i if this shouldn't work, try to compile the most common way, configure, make, make install, but replace make only or make and make install by checkinstall # ./configure # checkinstall --install=no # dpkg -i -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1393013221.695.35.camel@archlinux
Re: Old software in debian allowed?
On Jo, 20 feb 14, 20:01:04, Hans wrote: Hi list, just a simple question: Does debian accept suggestions of new packages, although they are old and orphaned by the original devolper? It depends a lot on the package. There are packages that haven't seen updates for a few releases and are working just fine. On the other hand if the package might be a security risk the Security Team will object to its (re)inclusion. This is just an example, there may be other reasons to keep the package out of Debian. Besides, just a suggestion (you probably mean Request for Package, a.k.a. RFP) instead of an actual intent (Intent to package, a.k.a. ITP) will not do much unless somebody is actually willing to package it and upload it to Debian. However, don't let this deter you from making a package. Even if it is only for you own use in the long run it is probably better and you also gain experience in packaging. If you make it available on the internet some other people might also find it useful. Hope this explains, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Re: Old software in debian allowed?
I've done just that, resurrected Xdx which had last been in Squeeze and was orphaned and dropped from Wheezy. The original author gave his blessing for me to take over maintanence in mid-January, I released a stable verion three weeks ago, and just this week it appeared in Sid as a new package. So, yes, this is quite possible so long as there is a willing Debian packager available. Fortunately, amateur radio software has a couple of such dedicated souls. - Nate -- The optimist proclaims that we live in the best of all possible worlds. The pessimist fears this is true. Ham radio, Linux, bikes, and more: http://www.n0nb.us -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140221014305.ga10...@n0nb.us
