On Wed, Mar 29, 2017 at 08:39:07AM +0200, Jaromil wrote:
> On Wed, 29 Mar 2017, KatolaZ wrote:
>
> > Hi folks,
> >
> > we have now devuan-compatible packages for _reportbug_ and
> > _python-reportbug_. The source is in gitlab:
> >
> > https://git.devuan.org/KatolaZ/reportbug
>
> many thanks for the good work on the bugs.devuan installation! to you
> and to golinux!
>
> > Sorry for the silly question: how do we include those packages in the
> > repos so that people can start testing them?
>
> they may be moved to devuan-packages/* and then (the package? the
> user?) needs to be added as authorized to build on ci.devuan.org
>

> -> this is a bottleneck currently as only Daniel and Nextime have this
>    authorisation, it needs to be extended to other core devs

>

OK, how do I add the repo to devuan-packages/*?

> then you create branches (jessie-proposed, jessie, ascii, etc) and you
> open an issue called "autobuild" which will trigger the bot to fetch
> the sources, build them over jenkins and make them appear in amprolla


OK. The only problem I see is that in this case a single source
package creates two binary packages (reportbug and pynton-reportbug).

On a more general note, is there a place where the workflow for
package maintainance is documented, so that I can avoid to bother the
list with silly questions which should be rightfully answered with a
"RTFM"? :)

HH

KatolaZ

-- 
[ ~.,_  Enzo Nicosia aka KatolaZ - GLUGCT -- Freaknet Medialab  ]  
[     "+.  katolaz [at] freaknet.org --- katolaz [at] yahoo.it  ]
[       @)   http://kalos.mine.nu ---  Devuan GNU + Linux User  ]
[     @@)  http://maths.qmul.ac.uk/~vnicosia --  GPG: 0B5F062F  ] 
[ (@@@)  Twitter: @KatolaZ - skype: katolaz -- github: KatolaZ  ]