[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#877871: RFP: pyside2 -- Python bindings for Qt5



¡Hola Raphael!

El 2018-05-11 a las 15:33 +0200, Raphael Hertzog escribió:
Thank you. Note that you granted me "developer" access which doesn't let
me create new repositories, so I will need one of you to create the
repository and also to add sophie (sbrun-guest) as member of the
pyside2 repository.

I've created: https://salsa.debian.org/qt-kde-team/qt/pyside2

I've pushed an empty commit, as otherwise, some configurations don't seem to stick.

I've also added you as master for the pyside2 repository.

We have not yet decided when to give team wide Master or Admin levels, sorry about that, it's in the agenda for our next meeting, but the meeting has no date set.

Right, but please take into account that the packages maintained under the
qt tree use a debian directory only packaging branch, and in general, they
use all the same packaging structure (no dpm, no upstream branches or tags
in the public repos, etc). This set of rules is more relaxed in qt-extras
and kde-extras.

Are the rules documented somewhere?

They are somewhat documented in http://pkg-kde.alioth.debian.org/, I would say: http://pkg-kde.alioth.debian.org/gitguidelines.html -> but the tagging string here is wrong (we used to enforce that tags needed the "$version $distribution; urgency=$urgency" format as done by pkgkde-git tag -s), and I wouldn't blindly follow the instructions under "Integrating original source into local repository".

I'm not particularly fond to this rules as to work on updating them, please ask further advice to the qt maintainers (Lisandro and Dmitry).

Happy hacking,
--
"The day Microsoft makes something that doesn't suck, is probably the day Microsoft starts making vacuum cleaners."
-- Ernst Jan Plugge
Saludos /\/\ /\ >< `/

Attachment: signature.asc
Description: PGP signature


Reply to: