[Koha-devel] Submitting Debian packages to Koha's APT repository

dcook at prosentient.com.au dcook at prosentient.com.au
Fri Nov 29 03:15:25 CET 2019


Hi Martin,

 

Thanks for your message. That all makes a lot of sense.

 

I’d be happy to provide additional support for packaging, but I’m unaware of the processes for providing it. (I can’t commit to taking on the Packaging manager role, but I’m happy to support the person in that role.)

 

The more I think about it, the more I see the merit of Chris’s approach. It looks like the Debian Perl Group or Debian would provide Git hosting, so the work could live there. 

 

When a package is built, do we email it to the Release Manager or the Packaging Manager? Is there a file server that we upload to? If I had the file ready right now, what would the next step be?

 

David Cook

Systems Librarian

Prosentient Systems

72/330 Wattle St

Ultimo, NSW 2007

Australia

 

Office: 02 9212 0899

Direct: 02 8005 0595

 

From: Renvoize, Martin <martin.renvoize at ptfs-europe.com> 
Sent: Thursday, 28 November 2019 7:30 PM
To: Chris Cormack <chrisc at catalyst.net.nz>
Cc: David Cook <dcook at prosentient.com.au>; Mirko Tietgen <mirko at abunchofthings.net>; Koha Devel <koha-devel at lists.koha-community.org>
Subject: Re: [Koha-devel] Submitting Debian packages to Koha's APT repository

 

I have reached out to Mirko a couple of times so far, I think he's just very busy.  

 

He's also got the challenge of investigating how we can support D10 packages on his plate, not to mention I'm currently waiting on his go ahead for the imminent release as it will be a security release, so needs to go out at the same time as the anouncements.

 

Really, this is just another highlight that as a community were struggling to fill all the roles more and more of late.

 

It's wonderful that some of our long standing volunteers keep stepping in to fill the gaps year after year, but it's a big commitment and they understandably reach burn out and struggle with other commitments the longer they are in post. Translations management and Packaging are both areas where I feel this has happened of late, I can't fault the current volunteers, but they're clearly under allot of pressure and could do with some additional support or the opportunity to hand over and step back for a few cycles.

 

Going back to packaging, as I think Chris has tried to highlight, it's not just a matter of packaging a dependency for the first time and your done.. if we want to take on such a dependancy there is also an ongoing maintainence cost to be considered which is why I always check in with Mirko about its viability rather than just instructing him to take it on.

 

 

On Thu, 28 Nov 2019, 3:43 am Chris Cormack, <chrisc at catalyst.net.nz <mailto:chrisc at catalyst.net.nz> > wrote:

Hi David

Yes if you have a packaged working version of the package someone will
get it into the repository.
(The easiest way to get a good quality working package is to follow the
guidelines of the debian perl group)

Chris

On 28/11/19 2:11 pm, dcook at prosentient.com.au <mailto:dcook at prosentient.com.au>  wrote:
> Well, that's the part where I'm confused. If Joonas or I package the dependency, can we get it into the Koha APT repo ASAP? 
> 
> My first priority is resolving Bug 13193 as soon as possible. Martin has already agreed to push the change, but we're just waiting on the dependency being available. I figure it'll be in the Koha APT repo before it's in Debian stable (one way or another), so I'm trying to facilitate getting that dependency in there one way or another. 
> 
> If Joonas or I can package the dependency and submit it somewhere or to someone to get it into the Koha APT repository, I'm sure we'd both make the time to do so. That's really what I'd like to know at this point.
> 
> Otherwise, I imagine we might package it but maintain it locally, and that seems suboptimal for everyone. (But is more optimal than leaving the bug unpatched.)
> 
> David Cook
> Systems Librarian
> Prosentient Systems
> 72/330 Wattle St
> Ultimo, NSW 2007
> Australia
> 
> Office: 02 9212 0899
> Direct: 02 8005 0595
> 
> -----Original Message-----
> From: Chris Cormack <chrisc at catalyst.net.nz <mailto:chrisc at catalyst.net.nz> > 
> Sent: Thursday, 28 November 2019 12:00 PM
> To: dcook at prosentient.com.au <mailto:dcook at prosentient.com.au> ; koha-devel at lists.koha-community.org <mailto:koha-devel at lists.koha-community.org> 
> Subject: Re: [Koha-devel] Submitting Debian packages to Koha's APT repository
> 
> It's really not much more than packaging it to a reasonable standard to get it in the Koha APT repo, and then maintaining it forever.
> Which if it doesn't end up in Debian, becomes your responsibility.
> 
> Chris
> 
> On 28/11/19 1:32 pm, dcook at prosentient.com.au <mailto:dcook at prosentient.com.au>  wrote:
>> I had a feeling that you were going to suggest that, Chris. Hehe.
>>
>>  
>>
>> That does sound reasonable, although it seems like a very large time 
>> commitment at this point. (I’ve thought about taking over the
>> idzebra-2.0 package but that one has seemed like too much 
>> time/responsibility as well, which is maybe why no one else has taken 
>> it over yet either.) Then again it might be one of those things that 
>> once I’m in and used to the Debian Perl group that it would be less of 
>> an issue than I imagine.
>>
>>  
>>
>> David Cook
>>
>> Systems Librarian
>>
>> Prosentient Systems
>>
>> 72/330 Wattle St
>>
>> Ultimo, NSW 2007
>>
>> Australia
>>
>>  
>>
>> Office: 02 9212 0899
>>
>> Direct: 02 8005 0595
>>
>>  
>>
>> *From:*Koha-devel <koha-devel-bounces at lists.koha-community.org <mailto:koha-devel-bounces at lists.koha-community.org> > *On 
>> Behalf Of *Chris Cormack
>> *Sent:* Wednesday, 27 November 2019 8:24 PM
>> *To:* koha-devel at lists.koha-community.org <mailto:koha-devel at lists.koha-community.org> 
>> *Subject:* Re: [Koha-devel] Submitting Debian packages to Koha's APT 
>> repository
>>
>>  
>>
>> The best way to do it is to join the debian perl group and package it 
>> that way.
>>
>> Robin
>> https://qa.debian.org/developer.php?login=robin@catalyst.net.nz
>> I
>> https://qa.debian.org/developer.php?login=chrisc@catalyst.net.nz
>> And Mirko
>> https://qa.debian.org/developer.php?email=mirko%40abunchofthings.net
>>
>> Have been doing that.
>> This way it gets into debian, and ubuntu as a result. And the package 
>> you create for submission there will be of a high enough standard to 
>> go on to debian.koha-community.org <http://debian.koha-community.org>  until it gets into a stable release.
>>
>> If we do it that way, the debian security team watch the package too.
>>
>> Chris
>>
>> On 27 November 2019 3:12:10 PM NZDT, dcook at prosentient.com.au <mailto:dcook at prosentient.com.au>  
>> <mailto:dcook at prosentient.com.au <mailto:dcook at prosentient.com.au> > wrote:
>>
>>     Hi all,
>>
>>      
>>
>>     Joonas Kylmälä and I have been waiting about 2 months for a Debian
>>     package dependency on “Bug 13193 - Make Memcached usage fork safe”
>>     https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13193.
>>
>>      
>>
>>     I don’t know if Mirko is just busy or hasn’t seen it, but is there
>>     any way that we could build the package and submit it to the
>>     community repository?
>>
>>      
>>
>>     This is a critical bug in Koha, so it would be good to get this
>>     resolved ASAP.
>>
>>      
>>
>>     David Cook
>>
>>     Systems Librarian
>>
>>     Prosentient Systems
>>
>>     72/330 Wattle St
>>
>>     Ultimo, NSW 2007
>>
>>     Australia
>>
>>      
>>
>>     Office: 02 9212 0899
>>
>>     Direct: 02 8005 0595
>>
>>      
>>
>>
>> --
>> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>>
> 
_______________________________________________
Koha-devel mailing list
Koha-devel at lists.koha-community.org <mailto:Koha-devel at lists.koha-community.org> 
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20191129/f87bdbb1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 484 bytes
Desc: not available
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20191129/f87bdbb1/attachment.sig>


More information about the Koha-devel mailing list