> But still, I'm not convinced at all on tarballs. Instead I'd set up an
> automatic vcs mirror/import infrastructure. Already did that about
> a decade ago (called the OSS-QM project - maybe some old maillist
> archives still have some bits about it ;-)). It's not a big deal.
>
>
Well,
as i ca
On 04.01.2015 06:45, Franco Lanza wrote:
> The idea is to have that for release branches but not for master so we
> can easily integrate new upstream releases,
rebase.
> considering not all sources are on an (external) git repo and we cannot
> just merge changes on every new upstream release
J
On Sat, Jan 03, 2015 at 07:06:19PM +0100, Enrico Weigelt, metux IT consult
wrote:
> > and for external hosted sources the devuan gitlab project
> > will have just the debian directory and a devuan specific script similar
> > to the "watch" script used in debian.
>
> I'd strongly suggest NOT doing
On 03.01.2015 09:19, Franco Lanza wrote:
> Devuan have a workflow driven by the autobuild infrastructure based
> on gitlab + jenkins + dak
Ok, sounds good.
> and for external hosted sources the devuan gitlab project
> will have just the debian directory and a devuan specific script similar
> to
On Fri, Jan 02, 2015 at 07:05:24PM +0100, Enrico Weigelt, metux IT consult
wrote:
> Hi folks,
>
>
> do we already have defined workflows for package submission ?
>
> I'm usually maintaining everything in git repos, where each distro
> has a separate branch, which directly adds ./debian/ directo
Hi folks,
do we already have defined workflows for package submission ?
I'm usually maintaining everything in git repos, where each distro
has a separate branch, which directly adds ./debian/ directory
and all necessary changes - no additional patches etc.
For example: https://github.com/metux/
