Re: Getting QtWebChannel ready for upload

2016-07-28 Thread Lisandro Damián Nicanor Pérez Meyer
[snip]
> Use of the machine readable copyright format is entirely optional.  It's
> encouraged, thus the lintian check, but it's not a problem if it's not
> machine readable.

I must admit I tend to forget this because I prefer structured things, but 
this is of course totally right.


-- 
Una vez que hemos eliminado lo imposible, lo que queda, por improbable que
parezca, es la verdad.
  Sherlock Holmes

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
-- 
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk

Re: Getting QtWebChannel ready for upload

2016-07-28 Thread Sandro Knauß
Hey Dmitry,

> On Debian this should be nodejs rather that node (see #614907).

Oh thanks for this notice. But changing the node -> nodejs results now in 
another lintian warning:
W: qtwebchannel-examples: script-not-executable usr/lib/x86_64-linux-gnu/qt5/
examples/webchannel/qwclient/qwclient.js

the env line is:
#/usr/bin/env nodejs


regards,

sandro


signature.asc
Description: This is a digitally signed message part.
-- 
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk

Re: Getting QtWebChannel ready for upload

2016-07-27 Thread Sandro Knauß
Hey,

Maybe we should use gobby for our uptodate TODO list (install the package 
named gobby). I used now gobby.debian.org/Teams/KDE/qtwebengine.

I think than we will follow the normal qt package rules and create a example, 
doc and doc-html packages to be consistant. My answers about merging things 
together was based without looking to other qt packages ( sorry for that)

>>* I would remove the patch examples_full_path.diff, because it only touches
>> examples and there the privacy breach to not hold in my eyes - What do you
>> think?
>I think it's a privacy breach non the less which is quite easy to fix. Extra  
points if a proper patch for doing this at build time is upstreamed.

Well the patch with linking to a Debian copy of jQuery can break the example, 
if the version is not exactly the same they depend on. And the example wants 
1.4.2 and debian has 1.2.0. I know from packaging webapps based on jQuery, 
that jQuery change their API often and thats why many packages in Debian store 
a internal copy of the version of jQuery they need. (I know this is not the 
way to go). That's why I recommend to don't link to the internal jQuery, 
because broken example are really bad and more a problem than the privacy 
beach. And it is a matter of fact, that the examples are used not very often, 
so we will see the error much later :(

But lisandro is right, never the less all the errors are valid privacy 
beaches, so we should not override them in lintian and keep the warnings as 
reminders, that we should fix them in future.

> examples_full_path.diff

if we keep the patch, than we should also add dep3 headers, yes.

> - debian/rules: 
 > * qmake will not take those flags. And if it did that would be a problem, as 
 >  
hardening enables -fPIE but we require -fPIC (which already implies -fPIE, but 
you can't use both at the same time).
already removed again

>  * qmake QT_BUILD_PARTS+=" src" ← why that?
will try if it is necessary

>* make install INSTALL_ROOT=$(CURDIR)/debian/tmp ← why not using 
dh_auto_install? check for example qtsensors.
fixed already

> * Missing -v in first and last rm call.
will add this.

> > > - debian/.directory really?
> Good question :) A Plasma/dolphin file that should have never been there :)

should be deleted. I overseen the file, because it is hidden :D
 
> [snip]
> 
> > In the future, when I refer to my branch/repo, it's hosted here:
> > https://git.launchpad.net/~tsimonq2/+git/qtwebchannel . Please always
> > pull from that.
> 
> Keep up the good work and it won't be long before any of us gives you commit
> access :)

+1

> >> P: libqt5webchannel-dev: example-unusual-interpreter usr/share/doc/
> >> libqt5webchannel-dev/examples/webchannel/qwclient/qwclient.js #!node
> So Sandro, this means it's fixed? If not, I have no clue either.

no I just looked what interpreter is set in the source file and this one is a 
correct one, so it is a debian tool changing the interpreter. So someone needs 
to investigate this.

Regards,

sandroy

signature.asc
Description: This is a digitally signed message part.
-- 
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk

Re: Getting QtWebChannel ready for upload

2016-07-26 Thread Lisandro Damián Nicanor Pérez Meyer
On martes, 26 de julio de 2016 7:33:54 P. M. ART Simon Quigley wrote:
[snip]
> > - Linking them, as long as they are in the same package, should be ok.
> > It's
> > simply to do too.
> 
> I'm unfamiliar with how this would be done, and I'm curious how.
> 
> debian/patches ?

rm all except one, use debian/.links

[snip] 
> How does being in Uploaders work? Does that mean we've touched the
> package? Does that mean we have upload rights to this package? I've
> never used this before.

Normally it's up to the original packager/team, but in this case you are the 
three ones working on this and none of us regular Qt maintainers, so...

[snip]
> About copyright.
> 
> In my branch, I added myself to the copyright file for the debian/
> directory, and I propose that the people in that entry should be me,
> Scarlett, and Sandro. Thoughts?

You did exactly the right thing.

> > - debian/.directory really?
> 
> What is this?

Good question :) A Plasma/dolphin file that should have never been there :)

[snip]
> In the future, when I refer to my branch/repo, it's hosted here:
> https://git.launchpad.net/~tsimonq2/+git/qtwebchannel . Please always
> pull from that.

Keep up the good work and it won't be long before any of us gives you commit 
access :)

-- 
"No es el crecimiento de la tecnología lo que excluye, sino la
protección sistemática de los derechos de uso de la misma,
lo cual se puede aplicar al arte."
  David Cuartielles

Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/


signature.asc
Description: This is a digitally signed message part.
-- 
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-kde-talk