All of lore.kernel.org
 help / color / mirror / Atom feed
From: Roland Stigge <stigge@antcom.de>
To: Jeff Webb <jeff.webb@nta-inc.net>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Debian packaging bug in Xenomai v2.6.1
Date: Thu, 12 Jul 2012 17:41:29 +0200	[thread overview]
Message-ID: <4FFEF029.1090901@antcom.de> (raw)
In-Reply-To: <4FFEE9E8.2040008@nta-inc.net>

On 07/12/2012 05:14 PM, Jeff Webb wrote:
>>> I unfortunately don't have the ressources to regularly sync/update
>>> debian/* in the xenomai.org dev repository.
> 
> Do you have the resources to update debian/* on xenomai.org just before
> each release is made?  I don't think it's necessary to update it any
> more often than that.  I'm assuming that you eventually package each
> release anyway, so it would be nice to do it before a release is made
> official.  Of course, if you don't have time for that or your
> availability doesn't line up with the timeframe for a release, that is
> understandable.  I am just asking if the problem is trying to keep the
> git repository up to date all the time, or if you don't even have time
> to do it for each release.

It would be possible for me if I get ~2 weeks notice before a Xenomai
release to already do _before_ the Xenomai release what I would normally
do _afterwards_ anyway (for Debian). Gilles, is this possible?

But keep in mind that from time to time Debian does intermitted
revisions and it would be necessary to synchronize with xenomai.org.
Much duplicated work that I would like to prevent.

Looks like this feature is more popular than I was thinking, so I'll try
my best.

BTW: There is the patch tracker at

	http://packages.qa.debian.org/x/xenomai.html

(see down on the right)

which could be used for automating or helping with sync with incremental
Debian revisions?

Gilles? Philippe?

> I find it useful, and have not had any trouble with it not working
> before.  That being said, I wouldn't object to getting the debian
> directory from another location, as long as the information at:
> 
>  http://www.xenomai.org/index.php/Building_Debian_packages
> 
> is updated with detailed instructions on exactly how to download,
> extract, and graft the appropriate debian directory into a xenomai
> source tree that was created from a release tarball or git repository.

I remember having updated one of those pages, but the current version
quite deviated. Hope everything works fine?

Thanks,

Roland


  reply	other threads:[~2012-07-12 15:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-10 20:00 [Xenomai] [Announce] Xenomai v2.6.1 Gilles Chanteperdrix
2012-07-11 15:53 ` [Xenomai] Debian packaging bug in " Jeff Webb
2012-07-11 16:52   ` Gilles Chanteperdrix
2012-07-11 17:48     ` Lennart Sorensen
2012-07-12  0:20       ` Gilles Chanteperdrix
2012-07-12  8:31         ` Roland Stigge
2012-07-12  9:10           ` Gilles Chanteperdrix
2012-07-12 15:14             ` Jeff Webb
2012-07-12 15:41               ` Roland Stigge [this message]
2012-07-12 15:49                 ` Gilles Chanteperdrix
2012-07-12 16:02                   ` Roland Stigge
2012-07-13  7:54                     ` Willy Lambert
2012-07-13 11:21                   ` Leopold Palomo-Avellaneda
2012-07-13 12:23                     ` Gilles Chanteperdrix

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FFEF029.1090901@antcom.de \
    --to=stigge@antcom.de \
    --cc=jeff.webb@nta-inc.net \
    --cc=xenomai@xenomai.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.