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 t
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
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
>
> Don't make that blocking you.
> Make "merge requests".
Standard fork pattern?
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!
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.
> > 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 t
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
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://gi
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 rule
> 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 fo
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
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
>
> > 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?
>
>
> > #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 p
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
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
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.
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.
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 fro
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 wit
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
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'
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), w
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/obit
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=ecop
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 exam
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
c
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 Genn
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
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 Armstro
Check /etc/services.
-mz
On Thu, May 3, 2012 at 3:22 PM, Whit Armstrong 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 sh
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,
Whit Armstrong 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 wor
> 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 sta
Whit Armstrong 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 proce
On Tue, Apr 24, 2012 at 9:20 AM, Whit Armstrong
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
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:
On Tue, Apr 24, 2012 at 8:16 AM, Whit Armstrong
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
On Tue, 24 Apr 2012 15:39:41 +0200, Ansgar Burchardt
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 exe
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 shou
Whit Armstrong 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 yo
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? Wou
> 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.
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
f
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 t
Maybe you can point me to a *reliable* tutorial for debian packaging. I
picked that one because I wanted to play with packaging.
Thanks.
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 re
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
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 the
/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 optio
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
pac
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 yo
On Sun, May 16, 2010 at 3:13 PM, James Stuckey wrote:
>
>
> On Sun, May 16, 2010 at 3:34 AM, Paul Wise wrote:
>
>> On Sun, May 16, 2010 at 5:39 AM, James Stuckey
>> wrote:
>>
>> > I'm interested in learning more about development/packaging on Debian.
>> I've
>> > downloaded some source to pack
On Sun, May 16, 2010 at 3:34 AM, Paul Wise wrote:
> On Sun, May 16, 2010 at 5:39 AM, James Stuckey
> 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 c
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 "pbuild
On Sun, May 16, 2010 at 5:39 AM, James Stuckey 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://
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
-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 suggestio
-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 suggestio
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
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
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
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
64 matches
Mail list logo
