Hi Erik and Sandro,
On Wed, Jun 14, 2017 at 10:56:40PM +0200, Sandro Knauß wrote:
> the SVN link actually pointed me to look at who is actually the maintainer of
> pythonqt and saw, that is not Debian KDE Maintainers. It is the QA Team
> . So that are the people that you need to talk to,
> becau
Hey,
the SVN link actually pointed me to look at who is actually the maintainer of
pythonqt and saw, that is not Debian KDE Maintainers. It is the QA Team
. So that are the people that you need to talk to,
because only those can add your work. Additonally they may have other rules
how work shou
On miércoles, 14 de junio de 2017 01:01:13 -03 Erik Lundin wrote:
> Hi,
Hi Erik!
> I'm now done with all changes I would like to see, so if someone would
> like to review them I'm grateful. Please see attached the diff against
> pythonqt 3.0-3. Since the Debian code for this package is hosted in
Hi,
I'm now done with all changes I would like to see, so if someone would
like to review them I'm grateful. Please see attached the diff against
pythonqt 3.0-3. Since the Debian code for this package is hosted in SVN
[1], I guess this is the easiest way.
Here is a summary of the changes:
Hey,
> How can I submit my packaging changes for review? Are you using pull
> requests somewhere?
there is no "formal way" nor pull request. The normal workflow is to use
mentors and personal repos and send the link around.
* mentors.debian.org
* https://wiki.debian.org/Alioth/Git#Forking_Git_r
Den 2017-05-27 kl. 22:38, skrev Dmitry Shachnev:
Yes, the soname is something to consider for upstream. If we think upstream
made an ABI break, we usually do not patch the soname, but instead rename the
package, i.e. append a prefix (“a” or “v5”).
The new upstream release 3.2 solves this. The p
On sábado, 27 de mayo de 2017 22:35:50 -03 Erik Lundin wrote:
> Hi Lisandro,
>
> Den 2017-05-27 kl. 22:26, skrev Lisandro Damián Nicanor Pérez Meyer:
> > On jueves, 25 de mayo de 2017 14:44:14 -03 Erik Lundin wrote:
> >> Den 2017-05-24 kl. 16:02, skrev Lisandro Damián Nicanor Pérez Meyer:
> >>> Ye
On Sat, May 27, 2017 at 10:08:13PM +0200, Erik Lundin wrote:
> > I think it is better to use original upstream sonames, for compatibility
> > with
> > third-party applications built against upstream versions.
> >
> > The Debian package name should usually be based only on the major part of
> > son
On jueves, 25 de mayo de 2017 14:44:14 -03 Erik Lundin wrote:
> Den 2017-05-24 kl. 16:02, skrev Lisandro Damián Nicanor Pérez Meyer:
> > Yes, if those libs are tied to public headers package them as separate
> > binary packages. Your mental health at maintaining time will thank you ;)
> There is a
Hi Dmitry,
Thanks for your feedback!
Den 2017-05-27 kl. 20:55, skrev Dmitry Shachnev:
The current Qt 4 package has no reverse dependencies, so you can safely drop
it and replace with the Qt 5 package.
I would prefer to avoid conflict, so please use /usr/include/PythonQt5.
Yes, that sounds r
Hi Erik!
On Tue, May 23, 2017 at 10:13:13AM +0200, Erik Lundin wrote:
> Hello,
>
> [...]
>
> I have made necessary changes for building the package using QMake, and now
> would like to contribute them back to the community. However, I'm new when
> it comes to Debian packaging, so please help me wi
Den 2017-05-24 kl. 16:02, skrev Lisandro Damián Nicanor Pérez Meyer:
Yes, if those libs are tied to public headers package them as separate binary
packages. Your mental health at maintaining time will thank you ;)
There is a header for PythonQt_QtAll (PythonQt_QtAll.h), so if I
understand it
On martes, 23 de mayo de 2017 10:13:13 -03 Erik Lundin wrote:
[snip]
> *PythonQt_QtAll*
> Previous packages built using CMake were configured to wrap the
> extension PythonQt_QtAll and only create one set of library files.
> However, the possibility to do that seems to have disappeared, and now a
Dmitry, you know better than me on this :-/
On martes, 23 de mayo de 2017 10:13:13 -03 Erik Lundin wrote:
> Hello,
>
> I sent this email to the debian-mentors list, and got directed to the
> Debian Qt/KDE team, so here follows the same content:
>
> We're using PythonQt built for Qt 5 at work, an
Den 2017-05-24 kl. 06:53, skrev Florian Bruhin:
PythonQt is an entirely different project, which aims to make (C++) Qt
projects scriptable with Python: http://pythonqt.sourceforge.net/
Yes, as Florian says it is PythonQt I'm after.
Is this the right list for my questions?
/Erik
--
http://lis
Hey Fritz,
On Wed, May 24, 2017 at 02:28:01AM +0200, Fritz Reichwald wrote:
> just one question for my better understanding.
> Is it possible that you mean PyQt when you say PythonQt?
PythonQt is an entirely different project, which aims to make (C++) Qt
projects scriptable with Python: http://py
Hi Erik,
just one question for my better understanding.
Is it possible that you mean PyQt when you say PythonQt?
If yes its already packaged for debian and working well.
You can find it in the repositories with the name "python3-pyqt5"
Best regards
Fritz
--
signature.asc
Description: PGP sig
17 matches
Mail list logo
