On Tuesday, December 20 2016, Pirate Praveen wrote: > On തിങ്കള് 19 ഡിസംബര് 2016 11:07 വൈകു, Sergio Durigan Junior wrote: >> Things are starting to calm down, and I intend to get back to packaging >> pagure. My intention is to get the latest version imported onto my >> repository and work on it. However, I don't think it will be possible >> to finish everything by Dec 25th. I know it would be good to get pagure >> on stretch, but IMHO it is better to make sure everything is working >> fine first. > > Dec 25 is the last day of uploading to sid so it can migrate to stretch > before freeze. We have time till stretch release (at least 2 months > more) to fix bugs. We should try our best to have it in stretch and if > not have it in stretch-backports. Hm, guys, I am not sure I'll be able to get this ready until the 25th. There are still issues with the package and well, tomorrow is christmas eve, so... I'll keep trying to get the package in a good shape. I think it is, but as Praveen mentioned there is still at least one issue when building it. Also, I'm not even considering updating the package to the latest version (2.10.1) now, because that will certainly introduce a lot of new issues. IMO, if you have time, here's what I would do: - If you manage to get the building issue sorted out, and if there are no other critical issues, then I think the package is "good enough" (for a very relaxed definition of "good") to be put on stretch. As Praveen said, we will have 2 months to fix remaining bugs. - If it is not possible to fix the critical bugs, then I'd suggest going with the strectch-backports alternative. It's not a bad option IMHO, and gives us even more time to really fix the underlying problems. Something really concerning me is the fact that pagure keeps adding JS dependencies that are either not packaged on Debian, or that are packaged as part of another, bigger package (usually some big ruby extension or so). And even in the second case, when the file is already in Debian, it is not really following our guidelines; for example, the .js and .min.js files are being shipped without being built from source. Anyway, some food for thought. I'll keep you posted if I manage to make things work on my side. Thanks, -- Sergio GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36 Please send encrypted e-mail if possible http://sergiodj.net/
Attachment:
signature.asc
Description: PGP signature