Re: packaging help
On 2024-05-04 03:44 +, james smith wrote: > I am trying to package ly[1] I got everything up to the rules part, I am > stuck thinking on how to edit/make the makefile, if you have any tips or > tools that can make this a easier process, I would be much grateful Any editor will do - note that tabs are syntactically important in makefiles A tool like debmake will make you a template/base rules files (as well as sample/template/base all the other files), or you can copy-and-modify one from almost any other package that isn't hopelessly out of date (debmake is a better approach). These days most rules files look like: #!/usr/bin/make -f #DH_VERBOSE=1 %: dh $@ with maybe a few instances of environement variables and override rules # see ENVIRONMENT in dpkg-buildflags(1) export DEB_CFLAGS_MAINT_APPEND = -Wall -pedantic or override_dh_clean: -mv Doxyfile.orig Doxyfile -mv libsquish.pc.in.orig libsquish.pc.in dh_clean Does that help? Wookey -- Principal hats: Debian, Wookware, ARM http://wookware.org/ signature.asc Description: PGP signature
Re: packaging help
On Sat, May 04, 2024 at 03:44:45AM +, james smith wrote: > I am trying to package ly[1] I got everything up to the rules part, I am > stuck thinking on how to edit/make the makefile, if you have any tips or > tools that can make this a easier process, I would be much grateful You don't normally need to "edit/make the makefile". Do you have any specific problems you need hep with? -- WBR, wRAR signature.asc Description: PGP signature
packaging help
I am trying to package ly[1] I got everything up to the rules part, I am stuck thinking on how to edit/make the makefile, if you have any tips or tools that can make this a easier process, I would be much grateful [1]https://github.com/fairyglade/ly
Re: Was: Packaging help
> > Don't make that blocking you. > Make "merge requests". Standard fork pattern?
Re: Was: Packaging help
On Mon, Jan 03, 2022 at 12:24:47PM +, Gavin Henry wrote: > > > Hopefully one of the VoIP packaging group will get back to me re below in > > > the next few weeks. > > > > https://alioth-lists.debian.net/pipermail/pkg-voip-maintainers/2021-December/035961.html > > Ah, I missed that. Brilliant! Thanks for the prod. > > > > > I'd like to look after the libosip2 package too as SentryPeer > > > > requires it and it looks like it's not been updated in 6 years? > > > > > > > > https://salsa.debian.org/pkg-voip-team/libosip2/-/blob/master/ChangeLog > > > > > > Just start > > Will request access. Don't make that blocking you. Make "merge requests". Groeten Geert Stappers -- Silence is hard to parse
Re: Was: Packaging help: users and directories
Weird, I *did not* get https://alioth-lists.debian.net/pipermail/pkg-voip-maintainers/2021-December/035961.html any where. Not in trash or SPAM.
Re: Was: Packaging help: users and directories
> > Hopefully one of the VoIP packaging group will get back to me re below in > > the next few weeks. > > https://alioth-lists.debian.net/pipermail/pkg-voip-maintainers/2021-December/035961.html Ah, I missed that. Brilliant! Thanks for the prod. > > > I'd like to look after the libosip2 package too as SentryPeer > > > requires it and it looks like it's not been updated in 6 years? > > > > > > https://salsa.debian.org/pkg-voip-team/libosip2/-/blob/master/ChangeLog > > > Just start Wil request access. -- Kind Regards, Gavin Henry. https://sentrypeer.org
Was: Packaging help: users and directories
On Mon, Jan 03, 2022 at 11:34:30AM +, Gavin Henry wrote: > On Thu, 30 Dec 2021, 09:01 Gavin Henry wrote: > > > > I've emailed the VoIP packaging group to see if I can help now that I know > > some more. > > Hopefully one of the VoIP packaging group will get back to me re below in > the next few weeks. https://alioth-lists.debian.net/pipermail/pkg-voip-maintainers/2021-December/035961.html > > I'd like to look after the libosip2 package too as SentryPeer > > requires it and it looks like it's not been updated in 6 years? > > > > https://salsa.debian.org/pkg-voip-team/libosip2/-/blob/master/ChangeLog Just start
Re: Packaging help: users and directories
Got access to salsa.debian.org today! Woot! Hopefully one of the VoIP packaging group will get back to me re below in the next few weeks. Thanks. On Thu, 30 Dec 2021, 09:01 Gavin Henry, wrote: > Thanks all for the help and pointers everyone. > > I've managed to build SentryPeer ( > https://github.com/SentryPeer/SentryPeer/tree/debian-packaging/debian). > I'm just going through debuild now to clean up lintian issues and pbuilder > runs for missing depends. > > Suprisingly enjoyable and "dh" in the rules file does a ton of work for > you! > > I've emailed the VoIP packaging group to see if I can help now that I know > some more. I'd like to look after the libosip2 package too as SentryPeer > requires it and it looks like it's not been updated in 6 years? > > https://salsa.debian.org/pkg-voip-team/libosip2/-/blob/master/ChangeLog > > Thanks again everyone. > > Gavin. >
Re: Packaging help: users and directories
Thanks all for the help and pointers everyone. I've managed to build SentryPeer ( https://github.com/SentryPeer/SentryPeer/tree/debian-packaging/debian). I'm just going through debuild now to clean up lintian issues and pbuilder runs for missing depends. Suprisingly enjoyable and "dh" in the rules file does a ton of work for you! I've emailed the VoIP packaging group to see if I can help now that I know some more. I'd like to look after the libosip2 package too as SentryPeer requires it and it looks like it's not been updated in 6 years? https://salsa.debian.org/pkg-voip-team/libosip2/-/blob/master/ChangeLog Thanks again everyone. Gavin.
Re: Packaging help: users and directories
> Dear Gavin Henry, Hi Chris! > I didn't follow your whole discussion, but if you have time I would highly > appreciate if you could put all this information together at a well-findable > place (maybe: extend https://wiki.debian.org/UpstreamGuide ?) > > Reason: > I'm probably going to search for similar information in the near future =) > > > Regards > Chris > > PS: This is not meant as a demand. Rather a "hint" that the work will pay of > at least for one more person. ... I just figured it's very difficult to > transport "nice" in letters. Everything sounds so demanding :/ I've Cc'd the list, sorry if that wasn't correct. What do you class as "all this information"? Starting from scratch? I'm coming from a Fedora/RH world so I've always wanted to do a Debian package and I am starting to see the flexibility of all the multi-files vs the one spec file I have: https://github.com/SentryPeer/SentryPeer/blob/main/packaging/rpm/sentrypeer.spec https://bugzilla.redhat.com/show_bug.cgi?id=2026516 <- main way to get a package listed for inclusion I'm pretty much done with the Fedora spec file, but I now understand about how the rules/control file can do all the requirements for you (if using autoconf?). My main issue was having zero knowledge of the main terms, so this page was hard to approach: https://wiki.debian.org/Packaging but this was good (as well as doing the RPM spec first and seeing how others have done their rules file): https://www.debian.org/doc/manuals/maint-guide/index.en.html I think the main issue is getting your head around "creating the first set of files" and then picking how to build it all moving forward. Thanks. -- Kind Regards, Gavin Henry. https://sentrypeer.org
Re: Packaging help: users and directories
On Wed, 29 Dec 2021 at 13:51, Robin Gustafsson wrote: > > On Wed, Dec 29, 2021 at 2:03 PM Gavin Henry wrote: > >> > >> > Is it best practice to have: > >> > > >> > 1. debian folder in your main repo > >> > 2. debian folder branch in main repo > >> > 3. Separate repo for this > >> > >> A separate repo hosted on salsa.debian.org. > > > > Thanks. That's for an official package, or? > > Yes, that's assuming you're pursuing inclusion in Debian. Otherwise > alternative 2, a separate branch in your existing repository. That's my plan! :-) -- Kind Regards, Gavin Henry. https://sentrypeer.org
Re: Packaging help: users and directories
On Wed, Dec 29, 2021 at 2:03 PM Gavin Henry wrote: >> >> > Is it best practice to have: >> > >> > 1. debian folder in your main repo >> > 2. debian folder branch in main repo >> > 3. Separate repo for this >> >> A separate repo hosted on salsa.debian.org. > > Thanks. That's for an official package, or? Yes, that's assuming you're pursuing inclusion in Debian. Otherwise alternative 2, a separate branch in your existing repository.
Re: Packaging help: users and directories
> > > Is it best practice to have: > > > > 1. debian folder in your main repo > > 2. debian folder branch in main repo > > 3. Separate repo for this > > A separate repo hosted on salsa.debian.org. > Thanks. That's for an official package, or? >
Re: Packaging help: users and directories
> > > #DEBHELPER# > > > One of the first google hits: > > https://manpages.debian.org/bullseye/debhelper/debhelper.7.en.html Thanks. I see it now. With quotes "#DEBHELPER#" didn't show up, but: Automatic generation of Debian install scripts Some debhelper commands will automatically generate parts of Debian maintainer scripts. If you want these automatically generated things included in your existing Debian maintainer scripts, then you need to add *#DEBHELPER#* to your scripts, in the place the code should be added. *#DEBHELPER#* will be replaced by any auto-generated code when you run *dh_installdeb*.
Re: Packaging help: users and directories
Hi Gavin, On Wed, Dec 29, 2021 at 12:35 PM Gavin Henry wrote: > [...] > Is it best practice to have: > > 1. debian folder in your main repo > 2. debian folder branch in main repo > 3. Separate repo for this A separate repo hosted on salsa.debian.org. On Wed, Dec 29, 2021 at 12:37 PM Gavin Henry wrote: > > What's this for, when it looks like this was written manually? Google > shows nothing: > > https://salsa.debian.org/dns-team/bind9/-/blob/debian/main/debian/bind9.postinst#L35 > > #DEBHELPER# The debhelper man page explains it. [1] [1] https://manpages.debian.org/unstable/debhelper/debhelper.7.en.html#Automatic_generation_of_Debian_install_scripts
Re: Packaging help: users and directories
Am 29.12.2021 um 12:36 teilte Gavin Henry mit: Hi, What's this for, when it looks like this was written manually? Google shows nothing: https://salsa.debian.org/dns-team/bind9/-/blob/debian/main/debian/bind9.postinst#L35 #DEBHELPER# One of the first google hits: https://manpages.debian.org/bullseye/debhelper/debhelper.7.en.html Hilmar -- sigfault OpenPGP_signature Description: OpenPGP digital signature
Re: Packaging help: users and directories
What's this for, when it looks like this was written manually? Google shows nothing: https://salsa.debian.org/dns-team/bind9/-/blob/debian/main/debian/bind9.postinst#L35 #DEBHELPER# Thanks.
Re: Packaging help: users and directories
This is exactly what I wanted to see :-) https://salsa.debian.org/dns-team/bind9/-/blob/debian/main/debian/bind9.postinst Is it best practice to have: 1. debian folder in your main repo 2. debian folder branch in main repo 3. Separate repo for this Thanks.
Re: Packaging help: users and directories
Hello Gavin, > > Le 2021-12-28 à 19 h 14, Gavin Henry a écrit : > > I was given this advice from Arthur, a Debian developer, but I can't > > find some of the finer details I'm looking for: > > > > In addition to the developer reference and the other documentation, you > can get some inspiration from packages with a postinst script ,where > users and services are created, such as dnsmasq [1] or bind9 [2]. > > To create sqlite3 databases, you will need dbconfig-comon [3]. > > /Nicolas > > [1] https://salsa.debian.org/debian/dnsmasq/-/tree/master/debian > [2] https://salsa.debian.org/dns-team/bind9/-/tree/debian/main/debian > [3] https://www.debian.org/doc/manuals/dbconfig-common/ch-develguide.html Hi Nicolas, We meet again! :) Thanks! I want to do this first one, then I'm going to use your project. Just so I know how it all works. SentryPeer will create the dB, just need /var/lib/sentrypeer directory created with the right user ownership etc. Gavin.
Re: Packaging help: users and directories
Hello Gavin, Le 2021-12-28 à 19 h 14, Gavin Henry a écrit : I was given this advice from Arthur, a Debian developer, but I can't find some of the finer details I'm looking for: In addition to the developer reference and the other documentation, you can get some inspiration from packages with a postinst script ,where users and services are created, such as dnsmasq [1] or bind9 [2]. To create sqlite3 databases, you will need dbconfig-comon [3]. /Nicolas [1] https://salsa.debian.org/debian/dnsmasq/-/tree/master/debian [2] https://salsa.debian.org/dns-team/bind9/-/tree/debian/main/debian [3] https://www.debian.org/doc/manuals/dbconfig-common/ch-develguide.html
Re: Packaging help: users and directories
I was given this advice from Arthur, a Debian developer, but I can't find some of the finer details I'm looking for: --- I recommend looking at https://wiki.debian.org/UpstreamGuide to some pointers about how to make it easy to ensure your software can be easily packaged in Debian. If you're looking to create a deb package that is ready to be included in Debian it is best to have your debian/ directory on a separate branch. I recommend using git-buildpackage, see https://wiki.debian.org/PackagingWithGit (this is what most collaboratively maintained packages use now). For information on how to create Debian packages see https://www.debian.org/doc/manuals/developers-reference/ (particularly chapters 5 and 6). If you want to look at more of the background there is the policy document, see https://www.debian.org/doc/debian-policy/ There are a lot of tools for efficiently building Debian packages. If you want to test your builds in a more controlled environment you should probably use pbuilder (of cowbuilder) because those use a clean chroot to build your packages to ensure you have the correct dependencies specified. Hope this helps -- Thanks
Packaging help: users and directories
Hi all, Where are some good examples to read about adding a user and group, a systemd service file, a /etc/default file and creating a /var/lib/sentrypeer directory to hold an sqlite db file? Just look at official packages? I've read This is for: https://github.com/SentryPeer/SentryPeer and I've started here: https://github.com/SentryPeer/SentryPeer/tree/debian-packaging/debian Thanks for reading, Gavin.
Re: [Debian-med-packaging] Help to build library in generic form, avx and sse3
Hi all, [...] >> 2. What do you think about the plan to support specific hardware >> features in separate binary packages? > > GCC from version 6 (which is in Debian Stretch) supports function > multi-versioning (and GCC from 4.8 onwards, which is even in Jessie, > supports a subset of that), which allows you to do the following: > > - have a function with generic C/C++ code be compiled multiple times > in different variants, and have the most optimal variant be selected > at runtime (requires GCC 6), I have recently noticed a similar approach in the latest version of one of the pattern matching libraries that the IDS Suricata depends on, Hyperscan [1]. The Hyperscan build process compiles several variants of the scanning engine specialised for different processor feature sets into one "fat runtime" and selects the most appropriate one for the host at runtime. This uses the "ifunc" indirect function attribute provided by GCC. very cool IMHO. This development, together with the fact that they also provided a run-time function to check for the presence of the required instructions, made it possible to drop one of these extra Debian packages with optimized binaries that we were shipping for Suricata at the time [2,3]. For the record, we used alternatives in this case to switch out binaries with and without optimizations. Cheers Sascha [1] https://github.com/01org/hyperscan/blob/master/CHANGELOG.md [2] https://anonscm.debian.org/cgit/pkg-suricata/pkg-suricata.git/commit/?id=8c7704dd158f59694b1b0bf4bbb8008727c6dc6b [3] https://anonscm.debian.org/cgit/pkg-suricata/pkg-suricata.git/commit/?id=209d2cffabb6588d8e9468b4f9535cad3ecf3d36 signature.asc Description: OpenPGP digital signature
Re: [Debian-med-packaging] Help with watch file for ecopcr needed
On Wed, Jan 11, 2017 at 03:16:38PM +0100, Sascha Steinbiss wrote: > > Any idea how to properly download the upstream source tarball with > > uscan? > > could you please try: > > opts=filenamemangle=s/.*\.tar\.gz\?ref=ecopcr_v?(\d\S+)/ecopcr-$1\.tar\.gz/g > \ > https://git.metabarcoding.org/obitools/ecopcr/tags?sort=updated_desc > .*archive\.tar\.gz\?ref=ecopcr_v?(\d\S+) > > This seems to have worked for me, I get a proper orig tarball. Works - feel free to commit to Git in future cases. :-) Thanks Andreas. -- http://fam-tille.de
Re: [Debian-med-packaging] Help with watch file for ecopcr needed
Hi Andreas, [...] > Any idea how to properly download the upstream source tarball with > uscan? could you please try: opts=filenamemangle=s/.*\.tar\.gz\?ref=ecopcr_v?(\d\S+)/ecopcr-$1\.tar\.gz/g \ https://git.metabarcoding.org/obitools/ecopcr/tags?sort=updated_desc .*archive\.tar\.gz\?ref=ecopcr_v?(\d\S+) This seems to have worked for me, I get a proper orig tarball. Cheers Sascha signature.asc Description: OpenPGP digital signature
Re: PAM module packaging help
Hi >I have started a debian package by following the example of libacl. I >apologize for being confusing but since I know hardly anything about debian >packaging, I >don't really know what to ask to get started. So to start, for >my shared library, could you recommend a good shared library example that I >can follow. If libacl is >fine, I am stuck with the following lintian warnings: > >Now running lintian... >W: mypackage source: binaries-have-file-conflict libmypackage-dev >libmypackage1 usr/lib/i386-linux-gnu/libmypackage.so >W: mypackage source: binaries-have-file-conflict libmypackage-dev >libmypackage1 usr/lib/i386-linux-gnu/libmypackage.so.1 >W: mypackage source: binaries-have-file-conflict libmypackage-dev >libmypackage1 usr/lib/i386-linux-gnu/libmypackage.so.1.0.0 your .install file have some issues let me explain. you have to provide a library.so.1.0.whatever if you want you can provide a library.so.1 linking the first one (just a symlink) and you have to ship them in the libmypackage1 package the -dev package should *only* ship the symlink library.so, the header files, and maybe the pkgconfig scripts or whatever is useful for the developer who links the library. well, the -dev package should depend on the real package in your control file >W: libmypackage1: non-dev-pkg-with-shlib-symlink >usr/lib/i386-linux-gnu/libmypackage.so.1.0.0 >usr/lib/i386-linux-gnu/libmypackage.so related to the first issue >W: mypackage: empty-binary-package probably related to the first issue >W: libmypackage-dev: package-name-doesnt-match-sonames libmypackage1 this is a problem caused by the first issue, the dev package shouldn't have the real library, but just a symlink >I am using bzr builddeb -- -us -uc to create the packages. not a problem, I use gbp, but it is fine anyway. I think if you fix your install files your package will quickly start to be working (man dh_install man dh_auto_install helps) maybe you can see from there https://sources.debian.net/src/libserial/0.6.0~rc2%2Bsvn122-4/debian/control/ cheers, G. On Fri, Jan 22, 2016 at 5:37 AM, Gianfranco Costamagnawrote: Hi, I don't understand what are you asking... > > >anyway, if you add the libfoo-dev to the build dependencies >you should be fine, as long as you have the shlibs:Depends substvar >on your runtime dependencies. > >With some code/packaging we might provide better answers > >cheers, > >G. > > > > > >Il Giovedì 21 Gennaio 2016 23:12, Karsten Rage ha >scritto: > > > >I am looking for help packaging up my PAM module. I am prepared to add >my package to Debian. The PAM module depends on a shared library that >in turn, depends on two other shared libraries (libxml2 and >libssl). Both the PAM module and the shared library are open source on >GitHub and are written in C. > >I have read over the packaging documentation but I can't get my head >around how to actually package the binaries up with the >proper dependencies >
Re: PAM module packaging help
I have started a debian package by following the example of libacl. I apologize for being confusing but since I know hardly anything about debian packaging, I don't really know what to ask to get started. So to start, for my shared library, could you recommend a good shared library example that I can follow. If libacl is fine, I am stuck with the following lintian warnings: Now running lintian... W: mypackage source: binaries-have-file-conflict libmypackage-dev libmypackage1 usr/lib/i386-linux-gnu/libmypackage.so W: mypackage source: binaries-have-file-conflict libmypackage-dev libmypackage1 usr/lib/i386-linux-gnu/libmypackage.so.1 W: mypackage source: binaries-have-file-conflict libmypackage-dev libmypackage1 usr/lib/i386-linux-gnu/libmypackage.so.1.0.0 W: libmypackage1: non-dev-pkg-with-shlib-symlink usr/lib/i386-linux-gnu/libmypackage.so.1.0.0 usr/lib/i386-linux-gnu/libmypackage.so W: mypackage: empty-binary-package W: libmypackage-dev: package-name-doesnt-match-sonames libmypackage1 I am using bzr builddeb -- -us -uc to create the packages. k On Fri, Jan 22, 2016 at 5:37 AM, Gianfranco Costamagna < costamagnagianfra...@yahoo.it> wrote: > Hi, I don't understand what are you asking... > > > anyway, if you add the libfoo-dev to the build dependencies > you should be fine, as long as you have the shlibs:Depends substvar > on your runtime dependencies. > > With some code/packaging we might provide better answers > > cheers, > > G. > > > > > Il Giovedì 21 Gennaio 2016 23:12, Karsten Rage> ha scritto: > > > > I am looking for help packaging up my PAM module. I am prepared to add > my package to Debian. The PAM module depends on a shared library that > in turn, depends on two other shared libraries (libxml2 and > libssl). Both the PAM module and the shared library are open source on > GitHub and are written in C. > > I have read over the packaging documentation but I can't get my head > around how to actually package the binaries up with the > proper dependencies >
Re: PAM module packaging help
Hi, I don't understand what are you asking... anyway, if you add the libfoo-dev to the build dependencies you should be fine, as long as you have the shlibs:Depends substvar on your runtime dependencies. With some code/packaging we might provide better answers cheers, G. Il Giovedì 21 Gennaio 2016 23:12, Karsten Rageha scritto: I am looking for help packaging up my PAM module. I am prepared to add my package to Debian. The PAM module depends on a shared library that in turn, depends on two other shared libraries (libxml2 and libssl). Both the PAM module and the shared library are open source on GitHub and are written in C. I have read over the packaging documentation but I can't get my head around how to actually package the binaries up with the proper dependencies
PAM module packaging help
I am looking for help packaging up my PAM module. I am prepared to add my package to Debian. The PAM module depends on a shared library that in turn, depends on two other shared libraries (libxml2 and libssl). Both the PAM module and the shared library are open source on GitHub and are written in C. I have read over the packaging documentation but I can't get my head around how to actually package the binaries up with the proper dependencies
Re: packaging help
This is going really well. Thanks to all those who have shared advice. How does one go about choosing ports for an application? Obviously there are well known ports, but is there any doc in debian that shows what ports have been 'reserved' by other applications? Thanks, Whit On Tue, Apr 24, 2012 at 12:15 PM, Gergely Nagy alger...@balabit.hu wrote: Whit Armstrong armstrong.w...@gmail.com writes: I assume it has a main process, which when stopped, would result in the workers being killed too. If that is so, I do not think you need to store the pids of the workers anywhere. Perhaps I'm confusing terminology here. The main deamon does not spawn the workers. It and the workers are started by the init.d script. The workers and the main daemon should be started and stopped together. In that case, it seems like I should store the pid's... so I can kill them upon stop. Have I understood correctly? Correct. As a suggestion, I'd store the pidfiles under /run/your-program-name/, under names like worker:0.pid, and main.pid or somesuch. start-stop-daemon can be of great help here, but unfortunately, I don't recall any package off the top of my head that would serve as a good example, even though I know I've met one or two.. :( -- |8] -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87aa21umvh.fsf@algernon.balabit -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAMi=pg43=Qrd0HfZoYLD8yTo_ZELVhqX2+-hTroLx5=o9r_...@mail.gmail.com
Re: packaging help
Check /etc/services. -mz On Thu, May 3, 2012 at 3:22 PM, Whit Armstrong armstrong.w...@gmail.com wrote: This is going really well. Thanks to all those who have shared advice. How does one go about choosing ports for an application? Obviously there are well known ports, but is there any doc in debian that shows what ports have been 'reserved' by other applications? Thanks, Whit On Tue, Apr 24, 2012 at 12:15 PM, Gergely Nagy alger...@balabit.hu wrote: Whit Armstrong armstrong.w...@gmail.com writes: I assume it has a main process, which when stopped, would result in the workers being killed too. If that is so, I do not think you need to store the pids of the workers anywhere. Perhaps I'm confusing terminology here. The main deamon does not spawn the workers. It and the workers are started by the init.d script. The workers and the main daemon should be started and stopped together. In that case, it seems like I should store the pid's... so I can kill them upon stop. Have I understood correctly? Correct. As a suggestion, I'd store the pidfiles under /run/your-program-name/, under names like worker:0.pid, and main.pid or somesuch. start-stop-daemon can be of great help here, but unfortunately, I don't recall any package off the top of my head that would serve as a good example, even though I know I've met one or two.. :( -- |8] -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87aa21umvh.fsf@algernon.balabit -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/camipg43qrd0hfzoyld8yto_zelvhqx2+-htrolx5o9r_...@mail.gmail.com -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caolfk3vsh1ma96jkebnbwesra2ft3lyzymfxswqbhlw2h6w...@mail.gmail.com
Re: packaging help
Port numbers are reserved by IANA. http://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xml You can see a partial list of some of the most popular ones in /etc/services, but it's rather incomplete compared to the source. -Steve On 3 May 2012 21:22, Whit Armstrong armstrong.w...@gmail.com wrote: This is going really well. Thanks to all those who have shared advice. How does one go about choosing ports for an application? Obviously there are well known ports, but is there any doc in debian that shows what ports have been 'reserved' by other applications? Thanks, Whit On Tue, Apr 24, 2012 at 12:15 PM, Gergely Nagy alger...@balabit.hu wrote: Whit Armstrong armstrong.w...@gmail.com writes: I assume it has a main process, which when stopped, would result in the workers being killed too. If that is so, I do not think you need to store the pids of the workers anywhere. Perhaps I'm confusing terminology here. The main deamon does not spawn the workers. It and the workers are started by the init.d script. The workers and the main daemon should be started and stopped together. In that case, it seems like I should store the pid's... so I can kill them upon stop. Have I understood correctly? Correct. As a suggestion, I'd store the pidfiles under /run/your-program-name/, under names like worker:0.pid, and main.pid or somesuch. start-stop-daemon can be of great help here, but unfortunately, I don't recall any package off the top of my head that would serve as a good example, even though I know I've met one or two.. :( -- |8] -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87aa21umvh.fsf@algernon.balabit -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/camipg43qrd0hfzoyld8yto_zelvhqx2+-htrolx5o9r_...@mail.gmail.com -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cafiqyukk0n4y+erumxpacrtzm9d-gttmohty7bxhukfgkuc...@mail.gmail.com
packaging help
First off, is this the right list to ask basic questions about packaging? I'm trying to package a small daemon that provdies a ZMQ remote execution facility for R. The code is here: https://github.com/armstrtw/deathstar.core I've read the package tutorials several times, but I'm having trouble finding out how to create a new user during the install (I don't want the daemon to run as root). Can someone point me in the right direction? Thanks, Whit -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAMi=pg4n7UXxm+2Tq8P+8q9dYQ2c=gekv8-ljkacv2_3sem...@mail.gmail.com
Re: packaging help
I've read the package tutorials several times, but I'm having trouble finding out how to create a new user during the install (I don't want the daemon to run as root). Can someone point me in the right direction? Two suggestions: a) think about what type of user you want: http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.2 b) look inside an existing package (e.g. reSIProcate, see debian/control and debian/repro.postinst) -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f969fb9.7080...@pocock.com.au
Re: packaging help
Thanks, Daniel. I would be looking for 6-64999, assuming my package eventually made it into debian, I suppose it would need to have a 'globally allocated' uid. The idea is simply not to give users executing an R script on the machine root access. Regarding, reSIProcate, it's cdbs based? Would the postinst script be the same format if I use dh? Based on Lucas Nussbaum's tutorial (http://www.debian.org/doc/manuals/packaging-tutorial/packaging-tutorial.en.pdf) I thought that dh would be the way to go for new packages. -Whit On Tue, Apr 24, 2012 at 8:42 AM, Daniel Pocock dan...@pocock.com.au wrote: I've read the package tutorials several times, but I'm having trouble finding out how to create a new user during the install (I don't want the daemon to run as root). Can someone point me in the right direction? Two suggestions: a) think about what type of user you want: http://www.debian.org/doc/debian-policy/ch-opersys.html#s9.2 b) look inside an existing package (e.g. reSIProcate, see debian/control and debian/repro.postinst) -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f969fb9.7080...@pocock.com.au -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAMi=pg4rj5t4zulc_e0fpcfzoqkwt7xlicrqvbqfxfji_+v...@mail.gmail.com
Re: packaging help
Whit Armstrong armstrong.w...@gmail.com writes: Thanks, Daniel. I would be looking for 6-64999, assuming my package eventually made it into debian, I suppose it would need to have a 'globally allocated' uid. The idea is simply not to give users executing an R script on the machine root access. Why do you think you'd need a statically allocated id? Why wouldn't a dynamic one work? -- |8] -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87sjftuunw.fsf@algernon.balabit
Re: packaging help
On 04/24/2012 03:16 PM, Whit Armstrong wrote: I would be looking for 6-64999, assuming my package eventually made it into debian, I suppose it would need to have a 'globally allocated' uid. The idea is simply not to give users executing an R script on the machine root access. You shouldn't need a statically allocated user id for this; just creating a (system) user with adduser should be fine. (The 100-999 range in policy 9.2.2.) Regarding, reSIProcate, it's cdbs based? Would the postinst script be the same format if I use dh? Based on Lucas Nussbaum's tutorial (http://www.debian.org/doc/manuals/packaging-tutorial/packaging-tutorial.en.pdf) I thought that dh would be the way to go for new packages. Maintainer scripts shouldn't differ (they are more or less just copied into the binary packages[1]). dh should be the most popular for new packages, but in the end it's a matter of preferences. I believe it might also be easier to find a sponsor for packages using dh as more people are familiar with it than with cdbs. Regards, Ansgar [1] With a few modifications: debhelper (and cdbs as it uses debhelper) might add some lines to them by replacing a special marker with shell code (#DEBHELPER#). -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f96ad1d.2050...@43-1.org
Re: packaging help
On Tue, 24 Apr 2012 15:39:41 +0200, Ansgar Burchardt ans...@43-1.org wrote: On 04/24/2012 03:16 PM, Whit Armstrong wrote: I would be looking for 6-64999, assuming my package eventually made it into debian, I suppose it would need to have a 'globally allocated' uid. The idea is simply not to give users executing an R script on the machine root access. You shouldn't need a statically allocated user id for this; just creating a (system) user with adduser should be fine. (The 100-999 range in policy 9.2.2.) Regarding, reSIProcate, it's cdbs based? Would the postinst script be the same format if I use dh? Based on Lucas Nussbaum's tutorial (http://www.debian.org/doc/manuals/packaging-tutorial/packaging-tutorial.en.pdf) I thought that dh would be the way to go for new packages. Maintainer scripts shouldn't differ (they are more or less just copied into the binary packages[1]). dh should be the most popular for new packages, but in the end it's a matter of preferences. I believe it might also be easier to find a sponsor for packages using dh as more people are familiar with it than with cdbs. Regards, Ansgar [1] With a few modifications: debhelper (and cdbs as it uses debhelper) might add some lines to them by replacing a special marker with shell code (#DEBHELPER#). Agreed, and just to add few more bits to the above: As a good reference of adding and removing system users have a look at the vsftpd package, that is, its portinst and postrm scripts. However, the project's general agreement is that system users, once added, should not be removed [1] by packaging means, so you will only need to worry about the addition part. [1[ http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=621833 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/7c5c04e5e99e1d8aef38840f2d1bb...@spnet.net
Re: packaging help
On Tue, Apr 24, 2012 at 8:16 AM, Whit Armstrong armstrong.w...@gmail.com wrote: Thanks, Daniel. I would be looking for 6-64999, assuming my package eventually made it into debian, I suppose it would need to have a 'globally allocated' uid. The idea is simply not to give users executing an R script on the machine root access. Regarding, reSIProcate, it's cdbs based? Would the postinst script be the same format if I use dh? Based on Lucas Nussbaum's tutorial (http://www.debian.org/doc/manuals/packaging-tutorial/packaging-tutorial.en.pdf) I thought that dh would be the way to go for new packages. I've used the postinst script from the puppet package for creating a user. Here is my version of it: ---{start}--- #!/bin/sh set -e if [ $1 = configure ]; then # Create the mailregx user if ! getent passwd mailregx /dev/null; then adduser --quiet --system --group --home /var/run/milter-regex \ --no-create-home \ --gecos milter-regex daemon user \ mailregx fi # Create the mailregx group, if it is missing, and set the # primary group of the mailregx user to this group. if ! getent group mailregx /dev/null; then addgroup --quiet --system mailregx usermod -g mailregx mailregx fi fi #DEBHELPER# ---{end}--- The #DEBHELPER# chunk is a callback or an include. It allows dh to insert code into the script. After my package is built, the postinst looks like: ---{start}--- #!/bin/sh set -e if [ $1 = configure ]; then # Create the mailregx user if ! getent passwd mailregx /dev/null; then adduser --quiet --system --group --home /var/run/milter-regex \ --no-create-home \ --gecos milter-regex daemon user \ mailregx fi # Create the mailregx group, if it is missing, and set the # primary group of the mailregx user to this group. if ! getent group mailregx /dev/null; then addgroup --quiet --system mailregx usermod -g mailregx mailregx fi fi # Automatically added by dh_installinit if [ -x /etc/init.d/milter-regex ]; then update-rc.d milter-regex defaults /dev/null invoke-rc.d milter-regex start || exit $? fi # End automatically added section ---{end}--- You can see the things that dh can put into the various post/pre scripts in /usr/share/debhelper/autoscripts. HTH, -mz -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caolfk3u_atyqp7wztfw3yjv28bx-q4udzwfjk1mo-9htj5o...@mail.gmail.com
Re: packaging help
Matt, Ansgar, and Gergely, Thanks for the tips. Can you also help with some advice on the init.d script? The init.d script for deathstar launches a daemon which listens for jobs, and one worker per core. Can I use the same pid file for all of those processes? -Whit On Tue, Apr 24, 2012 at 9:46 AM, Matt Zagrabelny mzagr...@d.umn.edu wrote: On Tue, Apr 24, 2012 at 8:16 AM, Whit Armstrong armstrong.w...@gmail.com wrote: Thanks, Daniel. I would be looking for 6-64999, assuming my package eventually made it into debian, I suppose it would need to have a 'globally allocated' uid. The idea is simply not to give users executing an R script on the machine root access. Regarding, reSIProcate, it's cdbs based? Would the postinst script be the same format if I use dh? Based on Lucas Nussbaum's tutorial (http://www.debian.org/doc/manuals/packaging-tutorial/packaging-tutorial.en.pdf) I thought that dh would be the way to go for new packages. I've used the postinst script from the puppet package for creating a user. Here is my version of it: ---{start}--- #!/bin/sh set -e if [ $1 = configure ]; then # Create the mailregx user if ! getent passwd mailregx /dev/null; then adduser --quiet --system --group --home /var/run/milter-regex \ --no-create-home \ --gecos milter-regex daemon user \ mailregx fi # Create the mailregx group, if it is missing, and set the # primary group of the mailregx user to this group. if ! getent group mailregx /dev/null; then addgroup --quiet --system mailregx usermod -g mailregx mailregx fi fi #DEBHELPER# ---{end}--- The #DEBHELPER# chunk is a callback or an include. It allows dh to insert code into the script. After my package is built, the postinst looks like: ---{start}--- #!/bin/sh set -e if [ $1 = configure ]; then # Create the mailregx user if ! getent passwd mailregx /dev/null; then adduser --quiet --system --group --home /var/run/milter-regex \ --no-create-home \ --gecos milter-regex daemon user \ mailregx fi # Create the mailregx group, if it is missing, and set the # primary group of the mailregx user to this group. if ! getent group mailregx /dev/null; then addgroup --quiet --system mailregx usermod -g mailregx mailregx fi fi # Automatically added by dh_installinit if [ -x /etc/init.d/milter-regex ]; then update-rc.d milter-regex defaults /dev/null invoke-rc.d milter-regex start || exit $? fi # End automatically added section ---{end}--- You can see the things that dh can put into the various post/pre scripts in /usr/share/debhelper/autoscripts. HTH, -mz -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAMi=pg5meoix4rasoyvjpu9g0owht31q1np+tg4ey41tib9...@mail.gmail.com
Re: packaging help
On Tue, Apr 24, 2012 at 9:20 AM, Whit Armstrong armstrong.w...@gmail.com wrote: Matt, Ansgar, and Gergely, Thanks for the tips. Can you also help with some advice on the init.d script? Perhaps. The init.d script for deathstar launches a daemon which listens for jobs, and one worker per core. This sounds a little like an apache that forks worker processes. Perhaps check apache's init script for ideas. Can I use the same pid file for all of those processes? Most Debian init scripts use start-stop-daemon (s-s-d) for controlling the daemon. How s-s-d interacts with the daemon depends greatly on how the daemon is written. Start with /etc/init.d/skeleton and tweak as needed. -mz -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caolfk3xczkn7mypjjxc815rvq1-xmr6m1qae-pdgebhp2t_...@mail.gmail.com
Re: packaging help
Whit Armstrong armstrong.w...@gmail.com writes: Matt, Ansgar, and Gergely, Thanks for the tips. Can you also help with some advice on the init.d script? The init.d script for deathstar launches a daemon which listens for jobs, and one worker per core. Can I use the same pid file for all of those processes? I assume it has a main process, which when stopped, would result in the workers being killed too. If that is so, I do not think you need to store the pids of the workers anywhere. -- |8] -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87k415ur40.fsf@algernon.balabit
Re: packaging help
I assume it has a main process, which when stopped, would result in the workers being killed too. If that is so, I do not think you need to store the pids of the workers anywhere. Perhaps I'm confusing terminology here. The main deamon does not spawn the workers. It and the workers are started by the init.d script. The workers and the main daemon should be started and stopped together. In that case, it seems like I should store the pid's... so I can kill them upon stop. Have I understood correctly? -Whit -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAMi=pg6WaUT1Fi6YVk2gontQSPp2-5qOTHpwcbaL=b6yebp...@mail.gmail.com
Re: packaging help
Whit Armstrong armstrong.w...@gmail.com writes: I assume it has a main process, which when stopped, would result in the workers being killed too. If that is so, I do not think you need to store the pids of the workers anywhere. Perhaps I'm confusing terminology here. The main deamon does not spawn the workers. It and the workers are started by the init.d script. The workers and the main daemon should be started and stopped together. In that case, it seems like I should store the pid's... so I can kill them upon stop. Have I understood correctly? Correct. As a suggestion, I'd store the pidfiles under /run/your-program-name/, under names like worker:0.pid, and main.pid or somesuch. start-stop-daemon can be of great help here, but unfortunately, I don't recall any package off the top of my head that would serve as a good example, even though I know I've met one or two.. :( -- |8] -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87aa21umvh.fsf@algernon.balabit
Re: packaging help
On Aug 31, 2010, at 11:45 AM, alma...@comcast.net wrote: I am working with this tutorial to understand better the debian packaging process: http://www.debian-administration.org/article/337/ Rolling_your_own_Debian_packages_part_2 One thing I noticed about that page; the note there regarding the -n option to dh_make, (i.e. that is packaged by the original author), seems to me to be at best misleading...Wonder how much trouble that has caused people? Jame -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1ba0598f-fa8b-4f15-aaec-c52e84893...@rocasa.us
Re: Re: packaging help
Maybe you can point me to a *reliable* tutorial for debian packaging. I picked that one because I wanted to play with packaging. Thanks.
Re: packaging help
On Thu, Sep 02, 2010 at 09:07:26AM -0700, Gobelli, Marcelo wrote: Maybe you can point me to a *reliable* tutorial for debian packaging. [...] The Debian New Maintainer's Guide is the most recommended: http://www.debian.org/doc/maint-guide/ The debian-mentors FAQ also has some useful things to say on the topic: http://people.debian.org/~mpalmer/debian-mentors_FAQ.html#packaging -- { IRL(Jeremy_Stanley); PGP(97AE496FC02DEC9FC353B2E748F9961143495829); SMTP(fu...@yuggoth.org); IRC(fu...@irc.yuggoth.org#ccl); ICQ(114362511); AIM(dreadazathoth); YAHOO(crawlingchaoslabs); FINGER(fu...@yuggoth.org); MUD(kin...@katarsis.mudpy.org:6669); WWW(http://fungi.yuggoth.org/); } -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100902163433.gm2...@yuggoth.org
re: packaging help
I am working with this tutorial to understand better the debian packaging process: http://www.debian-administration.org/article/337/Rolling_your_own_Debian_packages_part_2 it all goes well until I try to build the package from source. I am getting errors regarding SVN and APR (I think they are libraries) needed. I checked with Synaptic Manager and I see the libraries are installed. Do I have to make them available to the application? thanks for the help
Re: packaging help
On Tue, Aug 31, 2010 at 03:45:28PM +, alma...@comcast.net wrote: I am working with this tutorial to understand better the debian packaging process: http://www.debian-administration.org/article/337/Rolling_your_own_Debian_packages_part_2 it all goes well until I try to build the package from source. I am getting errors regarding SVN and APR (I think they are libraries) needed. I checked with Synaptic Manager and I see the libraries are installed. Normally, you'd be best off including the errors that you're seeing, as well as the exact names of the packages you see installed, but my spidey sense is telling me that you've installed the runtime library (eg libapr1), but not the development library (eg libapr1-dev). It is the latter that you need if you want to build against a library, not (just) the former. - Matt -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100831201657.gf...@hezmatt.org
Re: Packaging Help
On Sun, May 16, 2010 at 03:16:13PM +0200, James Stuckey wrote: So I'm not able to have debian-multimedia in my sources when I use pbuilder? You *can* have it in, but you can't *only* have it in. You still need the normal archives available because debian-multimedia does not include all packages. Additionally, if you plan to build for sid, you *shouldn't* have other archives listed in pbuilder. Packages for sid should not need external sources or packages to build or run. -- Jonathan Wiltshire 1024D: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 signature.asc Description: Digital signature
Re: Packaging Help
/etc/pbuilder/pbuilderrc contained: # this is your configuration file for pbuilder. # the file in /usr/share/pbuilder/pbuilderrc is the default template. # /etc/pbuilderrc is the one meant for overwritting defaults in # the default template # # read pbuilderrc.5 document for notes on specific options. MIRRORSITE=ftp://ftp.debian-multimedia.org I took out the last line and that fixed it. pbuilder create returns without error. Is it not possible for me to run pbuilder with a DMM line in my sources? I also use this machine for personal use and for that I need some of the stuff that's in DMM. The machine by the way is squeeze with some stuff from sid -- is that okay? I should probably say something about what all I've do so far to this since I'm sure I've missed or done something incorrectly. I got the source, and untarred it. Then I made a directory like packagename-1.0. Then I went into that directory and ran dh_make -f ../pathtotar. That made me a debian/ folder. I then ran pbuilder create and now I've run pdebuild in the packagename-1.0 directory and I'm getting this: *beginning* CMake Error at CMakeLists.txt:4 (add_subdirectory): add_subdirectory given source ../OALWrapper which is not an existing directory. CMake Error at CMakeLists.txt:5 (add_subdirectory): add_subdirectory given source ../HPL1Engine which is not an existing directory. -- Configuring incomplete, errors occurred! dh_auto_configure: cmake .. -DCMAKE_INSTALL_PREFIX=/usr -DCMAKE_VERBOSE_MAKEFILE=ON returned exit code 1 make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 E: Failed autobuilding of package I: unmounting dev/pts filesystem I: unmounting proc filesystem I: cleaning the build env I: removing directory /var/cache/pbuilder/build//17926 and its subdirectories *ending* Thanks, James
Re: Packaging Help
On Sun, May 16, 2010 at 3:34 AM, Paul Wise p...@debian.org wrote: On Sun, May 16, 2010 at 5:39 AM, James Stuckey jhstuc...@gmail.com wrote: I'm interested in learning more about development/packaging on Debian. I've downloaded some source to package, ran dh_make on it, and now I'm trying to use pbuilder to create a package from it. ... I: Checking component main on ftp://ftp.debian-multimedia.org... E: Couldn't find these debs: apt E: debootstrap failed ... Looks like you chose the wrong ftp site. Try ftp.debian.org instead. -- bye, pabs http://wiki.debian.org/PaulWise So I'm not able to have debian-multimedia in my sources when I use pbuilder?
Re: Packaging Help
On Sun, May 16, 2010 at 3:13 PM, James Stuckey jhstuc...@gmail.com wrote: On Sun, May 16, 2010 at 3:34 AM, Paul Wise p...@debian.org wrote: On Sun, May 16, 2010 at 5:39 AM, James Stuckey jhstuc...@gmail.com wrote: I'm interested in learning more about development/packaging on Debian. I've downloaded some source to package, ran dh_make on it, and now I'm trying to use pbuilder to create a package from it. ... I: Checking component main on ftp://ftp.debian-multimedia.org... E: Couldn't find these debs: apt E: debootstrap failed ... Looks like you chose the wrong ftp site. Try ftp.debian.org instead. -- bye, pabs http://wiki.debian.org/PaulWise So I'm not able to have debian-multimedia in my sources when I use pbuilder? I commented out the dmm line from my sources, and then deleted it, and I'm still getting the same error from pbuilder.
Re: Packaging Help
On Sun, May 16, 2010 at 03:16:13PM +0200, James Stuckey wrote: So I'm not able to have debian-multimedia in my sources when I use pbuilder? You can have it. I commented out the dmm line from my sources, and then deleted it, and I'm still getting the same error from pbuilder. Have you checked /etc/pbuilderrc contents created when pbuilder was installed by you answering debconf question. Osamu -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100516133634.ga19...@osamu.debian.net
Packaging Help
Hello, I'm interested in learning more about development/packaging on Debian. I've downloaded some source to package, ran dh_make on it, and now I'm trying to use pbuilder to create a package from it. When I run pbuilder create I get the following error: I: Distribution is sid. I: Building the build environment I: running debootstrap /usr/sbin/debootstrap I: Retrieving Release I: Retrieving Packages I: Validating Packages I: Resolving dependencies of required packages... I: Resolving dependencies of base packages... I: Checking component main on ftp://ftp.debian-multimedia.org... E: Couldn't find these debs: apt E: debootstrap failed W: Aborting with an error I: cleaning the build env I: removing directory /var/cache/pbuilder/build//14503 and its subdirectories Any guidance would be appreciated. Thanks, James
Re: Packaging Help
On Sun, May 16, 2010 at 5:39 AM, James Stuckey jhstuc...@gmail.com wrote: I'm interested in learning more about development/packaging on Debian. I've downloaded some source to package, ran dh_make on it, and now I'm trying to use pbuilder to create a package from it. ... I: Checking component main on ftp://ftp.debian-multimedia.org... E: Couldn't find these debs: apt E: debootstrap failed ... Looks like you chose the wrong ftp site. Try ftp.debian.org instead. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikjpfe_fsswfdnp5sof8lr-zgx9c-vp66-9h...@mail.gmail.com
Re: Packaging Help
On Sat, May 15, 2010 at 11:39:53PM +0200, James Stuckey wrote: Hello, I'm interested in learning more about development/packaging on Debian. I've downloaded some source to package, ran dh_make on it, and now I'm trying to use pbuilder to create a package from it. When I run pbuilder create I get the following error: I: Distribution is sid. I: Building the build environment I: running debootstrap /usr/sbin/debootstrap I: Retrieving Release I: Retrieving Packages I: Validating Packages I: Resolving dependencies of required packages... I: Resolving dependencies of base packages... I: Checking component main on ftp://ftp.debian-multimedia.org... ??? This should be Debian site. E: Couldn't find these debs: apt E: debootstrap failed W: Aborting with an error I: cleaning the build env I: removing directory /var/cache/pbuilder/build//14503 and its subdirectories Any guidance would be appreciated. Thanks, James -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100516012546.ga9...@osamu.debian.net
some packaging help
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I'm trying to build the new kernel immages for kernel 2.4.22 with speakup. Everything builds fine from source, but when I install the deb, I get this error from the kernel image deb. I'm not sure what I've done wrong, and if anyone has some suggestions, I would very highly appreciate it, because I feel like what I'm missing is something small. Here are the errors: The directory /lib/modules/2.4.22-speakup still exists. Continuing as directed. Unpacking replacement kernel-image-2.4.22-speakup ... Setting up kernel-image-2.4.22-speakup (2.4.22-1) ... error reading /lib/modules/2.4.22-speakup/build :No such file or directory Deleting /lib/modules/2.4.22-speakup/build error unlinking /lib/modules/2.4.22-speakup/build at /var/lib/dpkg/info/kernel-image-2.4.22-speakup.postinst line 237. If someone needs url to look at the source, let me know. - -- Freenode staff member: [EMAIL PROTECTED] , http://www.freenode.net Debian gnu/linux: http://www.debian.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQE/iyy0U5AGPOTGNc8RAn1IAJ0YCzOPRo9iw9EE7CA+WCdzAs3CYgCdHnWW 1VrlelcZpzbOj3xnzrGFdVw= =wHra -END PGP SIGNATURE-
PostgreSQL packaging - help is needed
On Thu, 2002-12-12 at 14:31, John Goerzen wrote: And, as a disclaimer, I personally have been bitten by these postgres upgrade bugs. Guess what -- I file bug reports and help Oliver find the problem rather than childishly whining about it in debian-devel. While I'm at it, I say to myself I'm glad I'm not maintaining this :-) Thanks for your support, John. Maintaining this package is a big challenge at times, but it is very satisfying when I finally get it right. The RPM packager has had to give up altogether on automatic upgrading. This particular transition (7.2.3 to 7.3) has been a major effort and I'm sorry that a lot of people have been hit by bugs in it. I hope we're just about done with them now, with 7.3rel-7. Let me again invite people who want to assist with testing and developing postgresql's packaging to subscribe to [EMAIL PROTECTED] and announce yourselves (subscribe at https://mailman.atnet.at/mailman/listinfo/debian-postgresql) Someone suggested I include debian-mentors in the appeal, which was a good idea, so if there are any new or would-be maintainers who would like to get involved with a rather complex package, here's an opportunity. -- Oliver Elphick[EMAIL PROTECTED] Isle of Wight, UK http://www.lfix.co.uk/oliver GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C Be of good courage, and he shall strengthen your heart, all ye that hope in the LORD. Psalms 31:24 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
PostgreSQL packaging - help is needed
On Thu, 2002-12-12 at 14:31, John Goerzen wrote: And, as a disclaimer, I personally have been bitten by these postgres upgrade bugs. Guess what -- I file bug reports and help Oliver find the problem rather than childishly whining about it in debian-devel. While I'm at it, I say to myself I'm glad I'm not maintaining this :-) Thanks for your support, John. Maintaining this package is a big challenge at times, but it is very satisfying when I finally get it right. The RPM packager has had to give up altogether on automatic upgrading. This particular transition (7.2.3 to 7.3) has been a major effort and I'm sorry that a lot of people have been hit by bugs in it. I hope we're just about done with them now, with 7.3rel-7. Let me again invite people who want to assist with testing and developing postgresql's packaging to subscribe to [EMAIL PROTECTED] and announce yourselves (subscribe at https://mailman.atnet.at/mailman/listinfo/debian-postgresql) Someone suggested I include debian-mentors in the appeal, which was a good idea, so if there are any new or would-be maintainers who would like to get involved with a rather complex package, here's an opportunity. -- Oliver Elphick[EMAIL PROTECTED] Isle of Wight, UK http://www.lfix.co.uk/oliver GPG: 1024D/3E1D0C1C: CA12 09E0 E8D5 8870 5839 932A 614D 4C34 3E1D 0C1C Be of good courage, and he shall strengthen your heart, all ye that hope in the LORD. Psalms 31:24
Request for sponsor / perl packaging help: libcarp-assert-perl
Good afternoon, I would like to request the assistance of a sponsor for one of the final steps needed for my nm process. I have packaged CPAN's Carp::Assert in the form of libcarp-assert-perl, a useful perl module that doesn't already exist in the archives (and is a dependancy of a package that I have adopted on the wnpp list). It is available for download directly as: http://jay.bonci.com/debian/files/libcarp-assert-perl_0.17-3_all.deb The other files (diff, orig, dsc, etc) are at http://jay.bonci.com/debian Files: drwxr-xr-x root/root 0 2002-10-22 00:20:06 ./ drwxr-xr-x root/root 0 2002-10-22 00:20:02 ./usr/ drwxr-xr-x root/root 0 2002-10-22 00:20:03 ./usr/share/ drwxr-xr-x root/root 0 2002-10-22 00:20:02 ./usr/share/perl5/ drwxr-xr-x root/root 0 2002-10-22 00:20:02 ./usr/share/perl5/Carp/ -rw-r--r-- root/root 14403 2002-07-25 14:10:46 ./usr/share/perl5/Carp/Assert.pm drwxr-xr-x root/root 0 2002-10-22 00:20:02 ./usr/share/man/ drwxr-xr-x root/root 0 2002-10-22 00:20:05 ./usr/share/man/man3/ -rw-r--r-- root/root 6327 2002-10-22 00:20:00 ./usr/share/man/man3/Carp::Assert.3pm.gz drwxr-xr-x root/root 0 2002-10-22 00:20:03 ./usr/share/doc/ drwxr-xr-x root/root 0 2002-10-22 00:20:05 ./usr/share/doc/libcarp-assert-perl/ -rw-r--r-- root/root 167 2002-07-25 14:20:02 ./usr/share/doc/libcarp-assert-perl/README.Debian -rw-r--r-- root/root 284 2002-07-25 14:22:58 ./usr/share/doc/libcarp-assert-perl/copyright -rw-r--r-- root/root 978 2002-07-25 14:10:46 ./usr/share/doc/libcarp-assert-perl/changelog.gz -rw-r--r-- root/root 260 2002-10-21 23:58:17 ./usr/share/doc/libcarp-assert-perl/changelog.Debian.gz This was built with heavy instruction from the Perl Policy (and a few people who have given me preliminary feedback on earlier package versions). I am doing a fair number of perl packages, so they all roughly work across the same debian/rules template. The control file is attached for your convenience. If someone could take the time to help me out, that would be greatly appreciated. Looking forward to contributing more, --jay bonci -- Jay Bonci| [EMAIL PROTECTED] GPG: E0B8B2DE| 562B 35DC BE8D 7802 DB31 6423 64D8 790F E0B8 B2DE msg07626/pgp0.pgp Description: PGP signature
Request for sponsor / perl packaging help: libcarp-assert-perl
Good afternoon, I would like to request the assistance of a sponsor for one of the final steps needed for my nm process. I have packaged CPAN's Carp::Assert in the form of libcarp-assert-perl, a useful perl module that doesn't already exist in the archives (and is a dependancy of a package that I have adopted on the wnpp list). It is available for download directly as: http://jay.bonci.com/debian/files/libcarp-assert-perl_0.17-3_all.deb The other files (diff, orig, dsc, etc) are at http://jay.bonci.com/debian Files: drwxr-xr-x root/root 0 2002-10-22 00:20:06 ./ drwxr-xr-x root/root 0 2002-10-22 00:20:02 ./usr/ drwxr-xr-x root/root 0 2002-10-22 00:20:03 ./usr/share/ drwxr-xr-x root/root 0 2002-10-22 00:20:02 ./usr/share/perl5/ drwxr-xr-x root/root 0 2002-10-22 00:20:02 ./usr/share/perl5/Carp/ -rw-r--r-- root/root 14403 2002-07-25 14:10:46 ./usr/share/perl5/Carp/Assert.pm drwxr-xr-x root/root 0 2002-10-22 00:20:02 ./usr/share/man/ drwxr-xr-x root/root 0 2002-10-22 00:20:05 ./usr/share/man/man3/ -rw-r--r-- root/root 6327 2002-10-22 00:20:00 ./usr/share/man/man3/Carp::Assert.3pm.gz drwxr-xr-x root/root 0 2002-10-22 00:20:03 ./usr/share/doc/ drwxr-xr-x root/root 0 2002-10-22 00:20:05 ./usr/share/doc/libcarp-assert-perl/ -rw-r--r-- root/root 167 2002-07-25 14:20:02 ./usr/share/doc/libcarp-assert-perl/README.Debian -rw-r--r-- root/root 284 2002-07-25 14:22:58 ./usr/share/doc/libcarp-assert-perl/copyright -rw-r--r-- root/root 978 2002-07-25 14:10:46 ./usr/share/doc/libcarp-assert-perl/changelog.gz -rw-r--r-- root/root 260 2002-10-21 23:58:17 ./usr/share/doc/libcarp-assert-perl/changelog.Debian.gz This was built with heavy instruction from the Perl Policy (and a few people who have given me preliminary feedback on earlier package versions). I am doing a fair number of perl packages, so they all roughly work across the same debian/rules template. The control file is attached for your convenience. If someone could take the time to help me out, that would be greatly appreciated. Looking forward to contributing more, --jay bonci -- Jay Bonci| [EMAIL PROTECTED] GPG: E0B8B2DE| 562B 35DC BE8D 7802 DB31 6423 64D8 790F E0B8 B2DE pgpYyGGU8R3u9.pgp Description: PGP signature