Bug#798044: RFS: php-mf2/0.2.12-1 [ITP] -- Microformats2 is the simplest way to markup structured information in HTML.

[Bhuvan Krishna]

Fixed all the bugs. Please check the package and suggest any changes.

https://mentors.debian.net/package/php-mf2

Regards,
Bhuvan

On Sunday 06 September 2015 03:28 AM, Bhuvan Krishna wrote:
> Hi Gianfranco,
>
> Thanks a lot for reviewing the package I will do the necessary changes
> as suggested. I will make the upper case to lower too as suggested ;)
>
> Regards,
> Bhuvan
>
> On Sunday 06 September 2015 03:19 AM, Gianfranco Costamagna wrote:
>> Hi Bhuvan
>>
>> the packaging looks good to me, however I have some issues that you might 
>> want to address:
>>
>> 1) 
>> override_dh_install:
>> dh_install
>>
>>
>> well, this is funny and useless :)
>>
>> 2) no watch file is usually bad...
>> please add one if possible
>>
>> 3) DH_VERBOSE in the rules file might be disabled, not an issue, just be 
>> sure that you want verbose
>> log by default.
>>
>> 4) debian/install.
>>
>> well, upstream might want to have a custom Makefile for installing stuff
>>
>> 5) copyright: 
>>
>> License: AGPL-3+
>> Released under the GNU Affero General Public License, version 3 or later.
>> See https://www.gnu.org/licenses/agpl.html for terms.
>>
>>
>> I usually prefer the same license as upstream, this way you avoid license 
>> incompatibilities
>> in patch forwarding upstream and you make easier to keep the copyright 
>> updated.
>>
>> moreover the license text should be extended
>> http://sources.debian.net/src/ghostscript/9.16%7Edfsg-2/debian/copyright/?hl=59#L387
>>
>> 6) lintian complains from mentors
>>
>> I composer-package-without-pkg-php-tools-builddep 
>> I description-synopsis-might-not-be-phrased-properly 
>>
>>
>> 7) (something strictly personal)
>> usr/share/php/Mf2
>>
>> I personally do not like Upper Case in Linux, but this is just me, and you 
>> shouldn't diverge
>> on path from upstream.
>>
>> However please consider making it lower case.
>>
>>
>> (note: I have little php knowledge, so I'm not sure I'll be able to sponsor 
>> the package, sorry)
>>
>> cheers,
>>
>> G.
>>
>>
>>
>>
>> Il Venerdì 4 Settembre 2015 21:03, Bhuvan Krishna  ha 
>> scritto:
>> Package: sponsorship-requests
>> Severity: wishlist
>>
>> Dear mentors,
>>
>>   I am looking for a sponsor for my package "php-mf2":
>>
>> * Package name: php-mf2
>>Version : 0.2.12
>> Upstream Author : Barnaby Walters 
>> * URL : http://microformats.org/wiki/microformats-2
>> * License : MIT
>>   Programming Lang: PHP
>>
>>
>>   It installs files to /usr/share/php/Mf2
>>
>>   To access further information about this package, please visit the
>> following URL:
>>
>>   http://mentors.debian.net/package/php-mf2
>>
>>
>>   Alternatively, one can download the package with dget using this command:
>>
>>   dget -x
>> http://mentors.debian.net/debian/pool/main/p/php-mf2/php-mf2_0.2.12-1.dsc
>>
>>   More information about hello can be obtained from
>> http://microformats.org/wiki/microformats-2#PHP.
>>
>>   Regards,
>> Bhuvan Krishna
>>
>




signature.asc
Description: OpenPGP digital signature

Re: watch file mangling help

[Pau Garcia i Quiles]

On Sat, Oct 17, 2015 at 1:03 PM, Ross Gammon  wrote:


> > * Pau Garcia i Quiles , 2015-10-17, 12:19:
> >> Why are you keeping the old versioning scheme if upstream has changed
> >> to a different scheme?
>
> Jakub's simple fix works, and I have asked upstream what the intentions
> are going forward. But I probably should remove both hyphens and dots to
> be sure!
>
>
Jakub's fix is the right fix. I thought you were using the original
upstream versioning scheme and now they had changed to something else,
hence my suggestion to adopt that "something else" if that was to stay.

-- 
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)

Re: watch file mangling help

[Jakub Wilk]

On Sat, Oct 17, 2015 at 11:55 AM, Ross Gammon  wrote:

Upstream have changed one of my package's versioning on the tarball
(http://anonscm.debian.org/cgit/collab-maint/abcmidi.git).

The last uploaded version was 20150908 and now there is an upstream 
tarball with the version "2015.10.08".


The watch file was simple:
version=3
opts=uversionmangle=s/-//g \
http://ifdo.pugmarks.com/~seymour/runabc/top.html abcMIDI-(.*)\.zip

But now a uscan --repack tells me that:
Newest version on remote site is 2015.10.08, local version is 20150908
=> remote site does not even have current version

I am not sure what I should be mangling here, uversionmangle, or 
dversionmangle, or both.


The upstream versioned was 2013-09-15, and you had uversionmangle rule 
to get rid of hyphens.


All you need to do is to update the uversionmangle rule so that it gets 
rid of dots instead.


* Pau Garcia i Quiles , 2015-10-17, 12:19:
Why are you keeping the old versioning scheme if upstream has changed 
to a different scheme?


The scheme Debian currently uses is good enough.
And to change it, you'd have to add epoch. Nobody likes epochs.

--
Jakub Wilk

Bug#801838: RFS: node-es5-shim/4.1.14+dfsg-1 [ITP]

[Gianfranco Costamagna]

Hi, Built, 

thanks for your contribution to Debian!





Il Giovedì 15 Ottobre 2015 21:51, Julien Puydt  ha 
scritto:



Hi,

Le jeudi 15 oct. 2015 à 08:16:24 (+), Gianfranco Costamagna a écrit :
> Control: owner -1 !
> Control: tags -1 moreinfo
> 
> as said on irc:
> 
> 1) rules:
> 
> override_dh_auto_test: please add a comment on the above line regarding the 
> reason for
> disabling the testsuite (requires internet connection or similar)
> 
> 2) rules:
> override_dh_auto_install:
>dh_install
> 
> what? ^^^
> 
> 3) add a README.source explaining the reason for having a dfsg repackage 
> (even if copyright files-excluded is clear)
> 
> 4) you install both es5-*.js and es5-*.min.js, are them needed both?
> 
> the other stuff looks good to me
>

I reworked it according to irc discussions ; the new upload is here (no more 
+dfsg):
http://mentors.debian.net/debian/pool/main/n/node-es5-shim/node-es5-shim_4.1.14-1.dsc
 


Thanks,

Snark on #debian-js

watch file mangling help

[Ross Gammon]

Hi,

Upstream have changed one of my package's versioning on the tarball
(http://anonscm.debian.org/cgit/collab-maint/abcmidi.git).

The last uploaded version was 20150908 and now there is an upstream
tarball with the version "2015.10.08".

The watch file was simple:
version=3
opts=uversionmangle=s/-//g \
http://ifdo.pugmarks.com/~seymour/runabc/top.html abcMIDI-(.*)\.zip

But now a uscan --repack tells me that:
Newest version on remote site is 2015.10.08, local version is 20150908
 => remote site does not even have current version

I am not sure what I should be mangling here, uversionmangle, or
dversionmangle, or both.

Before I just download the tarball manually and be done with it, I
thought I would check if someone could help with a more elegant solution.

Cheers,

Ross



signature.asc
Description: OpenPGP digital signature

Re: watch file mangling help

[Pau Garcia i Quiles]

On Sat, Oct 17, 2015 at 11:55 AM, Ross Gammon  wrote:


> Upstream have changed one of my package's versioning on the tarball
> (http://anonscm.debian.org/cgit/collab-maint/abcmidi.git).
>
> The last uploaded version was 20150908 and now there is an upstream
> tarball with the version "2015.10.08".
>
> The watch file was simple:
> version=3
> opts=uversionmangle=s/-//g \
> http://ifdo.pugmarks.com/~seymour/runabc/top.html abcMIDI-(.*)\.zip
>
> But now a uscan --repack tells me that:
> Newest version on remote site is 2015.10.08, local version is 20150908
>  => remote site does not even have current version
>
> I am not sure what I should be mangling here, uversionmangle, or
> dversionmangle, or both.
>
> Before I just download the tarball manually and be done with it, I
> thought I would check if someone could help with a more elegant solution.
>
>
Why are you keeping the old versioning scheme if upstream has changed to a
different scheme? Will they change back?

At first sight, my choice would be to change epoch and adopt the new
versioning scheme :-?


-- 
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)

Bug#787861: marked as done (RFS: polyml/5.5.2-1 [NMU] - interpreter and interactive compiler for Standard ML)

[Debian Bug Tracking System]

Your message dated Sat, 17 Oct 2015 07:29:22 + (UTC)
with message-id <855022376.2505729.1445066962197.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#787861: review: polyml
has caused the Debian Bug report #787861,
regarding RFS: polyml/5.5.2-1 [NMU] - interpreter and interactive compiler for 
Standard ML
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
787861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787861
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "polyml"

* Package name: polyml
  Version : 5.5.2-0.1
  Upstream Author : David Matthews 
* URL : http://www.polyml.org
* License : LGPL-2.1+
  Section : interpreters

It builds these binary packages:

  libpolyml-dev - development files for Poly/ML, a compiler for Standard ML
  libpolyml6- runtime files for Poly/ML, a compiler for Standard ML
  polyml- interpreter and interactive compiler for Standard ML

To access further information about this package, please visit the following 
URL:

  http://mentors.debian.net/package/polyml

Alternatively, one can download the package with dget using this command:

  dget -x 
http://mentors.debian.net/debian/pool/main/p/polyml/polyml_5.5.2-0.1.dsc

More information about polyml can be obtained from http://www.polyml.org.

Changes since the last upload:

  * Non-maintainer upload
  * New upstream version
  * Removed libtool .la files
  * Rename libpolyml1 to libpolyml6
  * Bump up Standards-Version to 3.9.6
  * Bump up debian/compat to 9, and use dh_prep over dh_clean -k
  * Enabled build hardening with dpkg-buildflags
  * Made descriptions more consistent

The maintainer has not updated this package in years. Various people including 
myself have attempted to contact the maintainer 
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=561763), but these have 
failed, so I have packaged it myself to hopefully move things along.

Regards,
James Clarke
--- End Message ---
--- Begin Message ---
Hi James,

I sponsored the package
(BTW I was intending to subscribe to debian-science, but also debian-devel is 
nice to be subscribed)


However, I would appreciate a fix for the following missing flags in a future 
release:
CXXFLAGS missing (-fPIE):
LDFLAGS missing (-Wl,-z,now)
CFLAGS missing (-fPIE):
LDFLAGS missing (-fPIE -pie -Wl,-z,now)
you can see the full log here [1] or by using blhc tool


[1] http://debomatic-i386.debian.net/distribution#unstable/polyml/5.5.2-1/blhc



cheers,

G.--- End Message ---

Re: watch file mangling help

[Ross Gammon]

On 10/17/2015 12:38 PM, Jakub Wilk wrote:
> On Sat, Oct 17, 2015 at 11:55 AM, Ross Gammon  wrote:

[...]

>>> The last uploaded version was 20150908 and now there is an upstream
>>> tarball with the version "2015.10.08".
>>>
>>> The watch file was simple:
>>> version=3
>>> opts=uversionmangle=s/-//g \
>>> http://ifdo.pugmarks.com/~seymour/runabc/top.html abcMIDI-(.*)\.zip
>>>
>>> But now a uscan --repack tells me that:
>>> Newest version on remote site is 2015.10.08, local version is 20150908
>>> => remote site does not even have current version
>>>

[...]

> The upstream versioned was 2013-09-15, and you had uversionmangle rule
> to get rid of hyphens.
> 
> All you need to do is to update the uversionmangle rule so that it gets
> rid of dots instead.

Thanks Jakub. Sometime you don't see something when it is staring you in
the face!

> * Pau Garcia i Quiles , 2015-10-17, 12:19:
>> Why are you keeping the old versioning scheme if upstream has changed
>> to a different scheme?

Jakub's simple fix works, and I have asked upstream what the intentions
are going forward. But I probably should remove both hyphens and dots to
be sure!



signature.asc
Description: OpenPGP digital signature

Bug#801650: marked as done (RFS: edgar/1.21-1 [ITP])

[Debian Bug Tracking System]

Your message dated Sat, 17 Oct 2015 11:55:20 + (UTC)
with message-id <312293000.2629859.1445082920900.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#801650: RFS: edgar/1.21-1 [ITP]
has caused the Debian Bug report #801650,
regarding RFS: edgar/1.21-1 [ITP]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
801650: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801650
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "edgar"

* Package name: edgar
  Version : 1.21-1
  Upstream Author : Richard Sweeney 
* URL : https://github.com/riksweeney/edgar
* License : GPL-2+
  Section : games

It builds those binary packages:

edgar - 2D platform game with a persistent world
edgar-data - 2D platform game with a persistent world (data files)

To access further information about this package, please visit the
following URL:

http://mentors.debian.net/package/edgar


Alternatively, one can download the package with dget using this command:

dget -x http://mentors.debian.net/debian/pool/main/e/edgar/edgar_1.21-1.dsc

Regards,
Zorian M
--- End Message ---
--- Begin Message ---
Hi Zorian,

wonderful!

sorry for the long wait, but I was really busy in other sponsoring :)




I did a final review of the package, and it was looking good.
(I couldn't finish the first level, but that's another story :p )

some nitpicks I would like to see addressed in a future release:
(please forward patches upstream too and link them in the patch header)

- use of dh_install features to exclude "xcf" files.
man dh_install can give you the answer, but I didn't check if it works :)

alternatively you can do something like
find debian/edgar-data -name "*.xcf" -delete
that should be more compact.

- another issue is to add some flags
http://debomatic-i386.debian.net/distribution#unstable/edgar/1.21-1/blhc
LDFLAGS missing (-fPIE -pie -Wl,-z,now):
CFLAGS missing (-fPIE):

- please consider joining pkg-games team
https://qa.debian.org/developer.php?login=pkg-games-de...@lists.alioth.debian.org

cheers, and thanks for your contribution to Debian!--- End Message ---

Bug#802003: RFS: node-simple-is/0.2.0+20130421-1 [ITP]

[Gianfranco Costamagna]

Control: owner -1 !
Control: tags -1 moreinfo

Hi,
same here, the debian/test/control is broken

cheers,

G.




Il Venerdì 16 Ottobre 2015 21:27, Julien Puydt  ha 
scritto:
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-simple-is"

  * Package name: node-simple-is
Version : 0.2.0+20130421-1
Upstream Author : Olov Lassus
  * URL : https://github.com/olov/simple-is
  * License : Expat
Section : web

   It builds those binary packages:

 libjs-simple-is - maximally minimal type-testing library 
(JavaScript lib)
  node-simple-is - Maximally minimal type-testing library (Node.js module)

   To access further information about this package, please visit the 
following URL:

  http://mentors.debian.net/package/node-simple-is


   Alternatively, one can download the package with dget using this command:

 dget -x 
http://mentors.debian.net/debian/pool/main/n/node-simple-is/node-simple-is_0.2.0+20130421-1.dsc

Thanks,

Snark on #debian-js

Bug#801838: marked as done (RFS: node-es5-shim/4.1.14-1 [ITP])

[Debian Bug Tracking System]

Your message dated Sat, 17 Oct 2015 13:24:20 + (UTC)
with message-id <1603848178.2658104.1445088260833.javamail.ya...@mail.yahoo.com>
and subject line 
has caused the Debian Bug report #801838,
regarding RFS: node-es5-shim/4.1.14-1 [ITP]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
801838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-es5-shim"

 * Package name: node-es5-shim
   Version : 4.1.14+dfsg-1
   Upstream Author : Kristopher Michael Kowal and contributors
 * URL : http://github.com/es-shims/es5-shim/
 * License : Expat
   Section : web

It builds those binary packages:

  libjs-es5-shim - ECMAScript 5 compat. shims for old JavaScript 
engines (library)
  node-es5-shim - ECMAScript 5 compat. shims for old JavaScript engines 
(Node.js)


To access further information about this package, please visit the 
following URL:


  http://mentors.debian.net/package/node-es5-shim


Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/n/node-es5-shim/node-es5-shim_4.1.14+dfsg-1.dsc


It is also available here:
Vcs-Git: git://anonscm.debian.org/pkg-javascript/node-es5-shim.git
Vcs-Browser: 
https://anonscm.debian.org/cgit/pkg-javascript/node-es5-shim.git


Thanks,

Snark on #debian-js
--- End Message ---
--- Begin Message ---
Closing--- End Message ---

Bug#802001: marked as done (RFS: node-simple-fmt/0.1.0+20130419-1 [ITP])

[Debian Bug Tracking System]

Your message dated Sat, 17 Oct 2015 13:37:30 + (UTC)
with message-id <1947866693.2666389.1445089050693.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#802001: RFS: node-simple-fmt/0.1.0+20130419-1 [ITP]
has caused the Debian Bug report #802001,
regarding RFS: node-simple-fmt/0.1.0+20130419-1 [ITP]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
802001: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802001
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-simple-fmt"

 * Package name: node-simple-fmt
   Version : 0.1.0+20130419-1
   Upstream Author : Olov Lassus
 * URL : https://github.com/olov/simple-fmt
 * License : Expat
   Section : web

  It builds those binary packages:

libjs-simple-fmt - maximally minimal type-testing library 
(JavaScript lib)
 node-simple-fmt - Maximally minimal string formatting library (Node.js 
module)


  To access further information about this package, please visit the 
following URL:


  http://mentors.debian.net/package/node-simple-fmt


  Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/n/node-simple-fmt/node-simple-fmt_0.1.0+20130419-1.dsc


Thanks,

Snark on #debian-js
--- End Message ---
--- Begin Message ---
Hi, Built, thanks for your contribution to Debian!
cheers,

G.





Il Sabato 17 Ottobre 2015 15:16, Julien Puydt  ha 
scritto:
Le samedi 17 oct. 2015 à 12:35:46 (+), Gianfranco Costamagna a écrit :
> Control: owner -1 !
> Control: tags -1 moreinfo
> 
> Hi, the debian/tests/control is broken (bad copy paste)
> (also the extended description is a little bit too short)
> 
Fixed in git, pushed to mentors.


Thanks,

Snark on #debian-js--- End Message ---

Bug#802003: marked as done (RFS: node-simple-is/0.2.0+20130421-1 [ITP])

[Debian Bug Tracking System]

Your message dated Sat, 17 Oct 2015 13:38:01 + (UTC)
with message-id <448144154.2685599.1445089081381.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#802003: RFS: node-simple-is/0.2.0+20130421-1 [ITP]
has caused the Debian Bug report #802003,
regarding RFS: node-simple-is/0.2.0+20130421-1 [ITP]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
802003: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802003
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-simple-is"

 * Package name: node-simple-is
   Version : 0.2.0+20130421-1
   Upstream Author : Olov Lassus
 * URL : https://github.com/olov/simple-is
 * License : Expat
   Section : web

  It builds those binary packages:

libjs-simple-is - maximally minimal type-testing library 
(JavaScript lib)

 node-simple-is - Maximally minimal type-testing library (Node.js module)

  To access further information about this package, please visit the 
following URL:


  http://mentors.debian.net/package/node-simple-is


  Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/n/node-simple-is/node-simple-is_0.2.0+20130421-1.dsc


Thanks,

Snark on #debian-js
--- End Message ---
--- Begin Message ---
Hi, Built, thanks for your contribution to Debian!


cheers,

G.


Il Sabato 17 Ottobre 2015 15:13, Julien Puydt  ha 
scritto:
Le samedi 17 oct. 2015 à 12:39:37 (+), Gianfranco Costamagna a écrit :
> Control: owner -1 !
> Control: tags -1 moreinfo
> 
> Hi,
> same here, the debian/test/control is broken
> 

Fixed in git, pushed to mentors.


Thanks,

Snark on #debian-js--- End Message ---

Re: [jitsi-dev] Jitsi in Debian

[Ximin Luo]

+debian-mentors for more comments/help

Hi, thanks a lot for the information and pointers! The documentation on why 
you're bundling various source packages is very useful. I see you also have a 
similar setup in 
https://github.com/jitsi/libjitsi/tree/master/resources/install/debian

I've played around with the build processes and have some comments:

1. You're only building a .orig.tar.gz, but Debian source packages require a 
.dsc (source package description file) and a .debian.tar.gz (debian packaging 
contents). After you create a full debian source package that includes all 
three files, you can then get rid of all of the "debian binary package" stuff 
from your build.xml scripts, and use the proper debian developer tools instead 
(e.g. dpkg-buildpackage, etc.

2. In both libjitsi and jitsi: you build up a tmp directory that contains all 
the sources for a debian package, out of which you build a .orig.tar.gz, but 
then clean (delete) the whole directory, without trying to create .dsc or 
.debian.tar.gz from the other files.

3. After applying the patches from [1] below, and running "ant deb-src 
-Dlabel="[*], then moving the .orig.tar.gz to the same directory as the 
temporary jitsi/libjitsi source tree, I can run `debuild -S` inside the 
temporary source tree. This is the *correct way* to make Debian packages. 
However, the process fails, for both libjitsi and jitsi. See [2] and [3].

The TL;DR is that it looks like your debian/patches/ are out-of-date, and I'm 
not familiar enough with the code base, to spend the time right now to debug it.

So I wonder, who has been generating the .dsc/.debian.tar.gz files that you've 
been submitting to Debian FTP? I have been unable to create one myself from 
your git repos.

In fact, it is better to keep the debian packaging files (i.e. debian/*) in a 
separate repo, in the top-level directory of the repo. Then, one can generate 
.orig.tar.gz from the main jitsi/libjitsi repos every release, then import them 
to the Debian packaging repos. This is a very standard pattern for Debian 
packaging, supporting by the git-buildpackage tool, see for example [4] where 
it says "Imported Upstream version" etc. This would be cleaner and cheaper than 
effectively re-implementing (and maintaining) the Debian toolchain in build.xml.

> AFAIK the reason why libjitsi is/was blocked is the license for the 
> javax.sdp/javax.sip API files

Do you have some more details on that?

X

[4] https://anonscm.debian.org/cgit/pkg-privacy/packages/flashproxy.git/log/


1. Patches for build.xml


Patches are on top of respective HEAD commits at 2015-10-17

jisti: only clean artefacts in "clean" targets to allow post-build inspection

diff --git a/resources/install/build.xml b/resources/install/build.xml
index 3922296..0eadfaf 100644
--- a/resources/install/build.xml
+++ b/resources/install/build.xml
@@ -2501,7 +2501,7 @@
 
 
 
-
+
 
 
 
 
 
@@ -2708,7 +2708,6 @@
 
-
 
 
 


libjisti: only clean artefacts in "clean" targets to allow post-build inspection

diff --git a/resources/install/build-debian.xml 
b/resources/install/build-debian.xml
index 8c1a020..f0dc711 100644
--- a/resources/install/build-debian.xml
+++ b/resources/install/build-debian.xml
@@ -11,9 +11,6 @@
 
-
-
-
 
 
 
@@ -187,7 +184,9 @@
 
 
 
-
+
+
+
 
 
 


=
2. debuild -S on libjitsi
=

# after patching and running `ant deb-src -Dlabel=`, and moving the built 
.orig.tar.gz to the correct location listed below
# I don't know what label to use here

libjitsi.git/tmp/libjitsi$ ls -1 ..
libjitsi/
libjitsi_.orig.tar.gz

libjitsi.git/tmp/libjitsi$ debuild -S
dpkg-buildpackage -rfakeroot -d -us -uc -S
dpkg-buildpackage: source package libjitsi
dpkg-buildpackage: source version 
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Damian Minkov 
dpkg-source --before-build libjitsi
dpkg-source: info: applying bouncycastle-1.49.patch
dpkg-source: info: applying bouncycastle-1.51.patch
dpkg-source: info: applying remove-hflip
can't find file to patch at input line 6
Perhaps you used the wrong -p or --strip option?
The text leading up to this was:
--
|Description: Removes hflip, filters internal api availbale in ffmpeg but not 
in libav
|Index: 
libjitsi/lib/src/jitsi-lgpl-dependencies/src/native/ffmpeg/org_jitsi_impl_neomedia_codec_FFmpeg.c

Bug#802000: marked as done (RFS: node-regenerate/1.2.1-1 [ITP])

[Debian Bug Tracking System]

Your message dated Sat, 17 Oct 2015 12:18:48 + (UTC)
with message-id <724506699.2610415.1445084328764.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#802000: RFS: node-regenerate/1.2.1-1 [ITP]
has caused the Debian Bug report #802000,
regarding RFS: node-regenerate/1.2.1-1 [ITP]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
802000: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802000
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-regenerate"

 * Package name: node-regenerate
   Version : 1.2.1-1
   Upstream Author : Mathias Bynens
 * URL : https://github.com/mathiasbynens/regenerate
 * License : Expat
   Section : web

  It builds those binary packages:

libjs-regenerate - Unicode-aware regular expression generator 
(JavaScript library)
 node-regenerate - Unicode-aware regular expression generator (Node.js 
module)


  To access further information about this package, please visit the 
following URL:


  http://mentors.debian.net/package/node-regenerate


  Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/n/node-regenerate/node-regenerate_1.2.1-1.dsc


It is packaged here:
Vcs-Git: git://anonscm.debian.org/pkg-javascript/node-regenerate.git
Vcs-Browser: 
https://anonscm.debian.org/cgit/pkg-javascript/node-regenerate.git


Thanks,

Snark on #debian-js
--- End Message ---
--- Begin Message ---
Built, thanks for your contribution to Debian!

cheers,

G.




Il Venerdì 16 Ottobre 2015 21:09, Julien Puydt  ha 
scritto:
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-regenerate"

  * Package name: node-regenerate
Version : 1.2.1-1
Upstream Author : Mathias Bynens
  * URL : https://github.com/mathiasbynens/regenerate
  * License : Expat
Section : web

   It builds those binary packages:

 libjs-regenerate - Unicode-aware regular expression generator 
(JavaScript library)
  node-regenerate - Unicode-aware regular expression generator (Node.js 
module)

   To access further information about this package, please visit the 
following URL:

  http://mentors.debian.net/package/node-regenerate


   Alternatively, one can download the package with dget using this command:

 dget -x 
http://mentors.debian.net/debian/pool/main/n/node-regenerate/node-regenerate_1.2.1-1.dsc

It is packaged here:
Vcs-Git: git://anonscm.debian.org/pkg-javascript/node-regenerate.git
Vcs-Browser: 
https://anonscm.debian.org/cgit/pkg-javascript/node-regenerate.git

Thanks,

Snark on #debian-js--- End Message ---

Bug#801972: marked as done (RFS: node-es6-shim/0.33.6-1 [ITP] -- ECMAScript 6 compatibility shims for legacy JavaScript engines)

[Debian Bug Tracking System]

Your message dated Sat, 17 Oct 2015 12:16:25 + (UTC)
with message-id <1911777905.2618635.1445084185137.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#801972: RFS: node-es6-shim/0.33.6-1 [ITP] -- 
ECMAScript 6 compatibility shims for legacy JavaScript engines
has caused the Debian Bug report #801972,
regarding RFS: node-es6-shim/0.33.6-1 [ITP] -- ECMAScript 6 compatibility shims 
for legacy JavaScript engines
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
801972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801972
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-es6-shim"

* Package name: node-es6-shim
  Version : 0.33.6-1
  Upstream Author : Paul Miller and contributors
* URL : https://github.com/paulmillr/es6-shim
* License : Expat
  Section : web

It builds those binary packages:

  libjs-es6-shim - ECMAScript 6 compat. shims for legacy JavaScript 
engines (library
  node-es6-shim - ECMAScript 6 compat. shims for legacy JavaScript 
engines (Node.js


  To access further information about this package, please visit the 
following URL:


  http://mentors.debian.net/package/node-es6-shim

  Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/n/node-es6-shim/node-es6-shim_0.33.6-1.dsc


Thanks,

Snark on #debian-js
--- End Message ---
--- Begin Message ---
Built, thanks for your contribution to Debian!

cheers,

G.





Il Venerdì 16 Ottobre 2015 15:51, Julien Puydt  ha 
scritto:
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-es6-shim"

* Package name: node-es6-shim
   Version : 0.33.6-1
   Upstream Author : Paul Miller and contributors
* URL : https://github.com/paulmillr/es6-shim
* License : Expat
   Section : web

It builds those binary packages:

   libjs-es6-shim - ECMAScript 6 compat. shims for legacy JavaScript 
engines (library
   node-es6-shim - ECMAScript 6 compat. shims for legacy JavaScript 
engines (Node.js

   To access further information about this package, please visit the 
following URL:

  http://mentors.debian.net/package/node-es6-shim

   Alternatively, one can download the package with dget using this command:

 dget -x 
http://mentors.debian.net/debian/pool/main/n/node-es6-shim/node-es6-shim_0.33.6-1.dsc

Thanks,

Snark on #debian-js--- End Message ---

Bug#801999: marked as done (RFS: node-jsesc/0.5.0-1 [ITP])

[Debian Bug Tracking System]

Your message dated Sat, 17 Oct 2015 12:18:28 + (UTC)
with message-id <1548993891.2629952.1445084308492.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#801999: RFS: node-jsesc/0.5.0-1 [ITP]
has caused the Debian Bug report #801999,
regarding RFS: node-jsesc/0.5.0-1 [ITP]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
801999: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801999
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-jsesc"

 * Package name: node-jsesc
   Version : 0.5.0-1
   Upstream Author : Mathias Bynens
 * URL : https://github.com/mathiasbynens/jsesc/
 * License : Expat
   Section : web

  It builds those binary packages:

node-jsesc - Escape JavaScript strings, with short output (Node.js 
module)


  To access further information about this package, please visit the 
following URL:


  http://mentors.debian.net/package/node-jsesc


  Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/n/node-jsesc/node-jsesc_0.5.0-1.dsc


It is packaged here:

Vcs-Git: git://anonscm.debian.org/pkg-javascript/node-jsesc.git
Vcs-Browser: https://anonscm.debian.org/cgit/pkg-javascript/node-jsesc.git


Thanks,

Snark on #debian-js
--- End Message ---
--- Begin Message ---
Built, thanks for your contribution to Debian!

cheers,

G.




Il Venerdì 16 Ottobre 2015 21:06, Julien Puydt  ha 
scritto:
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-jsesc"

  * Package name: node-jsesc
Version : 0.5.0-1
Upstream Author : Mathias Bynens
  * URL : https://github.com/mathiasbynens/jsesc/
  * License : Expat
Section : web

   It builds those binary packages:

 node-jsesc - Escape JavaScript strings, with short output (Node.js 
module)

   To access further information about this package, please visit the 
following URL:

  http://mentors.debian.net/package/node-jsesc


   Alternatively, one can download the package with dget using this command:

 dget -x 
http://mentors.debian.net/debian/pool/main/n/node-jsesc/node-jsesc_0.5.0-1.dsc

It is packaged here:

Vcs-Git: git://anonscm.debian.org/pkg-javascript/node-jsesc.git
Vcs-Browser: https://anonscm.debian.org/cgit/pkg-javascript/node-jsesc.git


Thanks,

Snark on #debian-js--- End Message ---

Bug#802001: RFS: node-simple-fmt/0.1.0+20130419-1 [ITP]

[Gianfranco Costamagna]

Control: owner -1 !
Control: tags -1 moreinfo

Hi, the debian/tests/control is broken (bad copy paste)
(also the extended description is a little bit too short)

cheers,

G.




Il Venerdì 16 Ottobre 2015 21:15, Julien Puydt  ha 
scritto:
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-simple-fmt"

  * Package name: node-simple-fmt
Version : 0.1.0+20130419-1
Upstream Author : Olov Lassus
  * URL : https://github.com/olov/simple-fmt
  * License : Expat
Section : web

   It builds those binary packages:

 libjs-simple-fmt - maximally minimal type-testing library 
(JavaScript lib)
  node-simple-fmt - Maximally minimal string formatting library (Node.js 
module)

   To access further information about this package, please visit the 
following URL:

  http://mentors.debian.net/package/node-simple-fmt


   Alternatively, one can download the package with dget using this command:

 dget -x 
http://mentors.debian.net/debian/pool/main/n/node-simple-fmt/node-simple-fmt_0.1.0+20130419-1.dsc

Thanks,

Snark on #debian-js

Bug#802004: marked as done (RFS: node-stringmap/0.2.2+20130926-1 [ITP])

[Debian Bug Tracking System]

Your message dated Sat, 17 Oct 2015 12:48:41 + (UTC)
with message-id <1544620665.2627575.1445086121282.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#802004: RFS: node-stringmap/0.2.2+20130926-1 [ITP]
has caused the Debian Bug report #802004,
regarding RFS: node-stringmap/0.2.2+20130926-1 [ITP]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
802004: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802004
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-stringmap"

 * Package name: node-stringmap
   Version : 0.2.2+20130926-1
   Upstream Author : Olov Lassus
 * URL : https://github.com/olov/stringmap
 * License : Expat
   Section : web

  It builds those binary packages:

libjs-stringmap - fast and robust stringmap (JavaScript lib)
 node-stringmap - fast and robust stringmap (Node.js module)

  To access further information about this package, please visit the 
following URL:


  http://mentors.debian.net/package/node-stringmap


  Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/n/node-stringmap/node-stringmap_0.2.2+20130926-1.dsc


Thanks,

Snark on #debian-js
--- End Message ---
--- Begin Message ---
Hi, Built, thanks for your contribution to Debian!

cheers,

G.




Il Venerdì 16 Ottobre 2015 21:33, Julien Puydt  ha 
scritto:
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-stringmap"

  * Package name: node-stringmap
Version : 0.2.2+20130926-1
Upstream Author : Olov Lassus
  * URL : https://github.com/olov/stringmap
  * License : Expat
Section : web

   It builds those binary packages:

 libjs-stringmap - fast and robust stringmap (JavaScript lib)
  node-stringmap - fast and robust stringmap (Node.js module)

   To access further information about this package, please visit the 
following URL:

  http://mentors.debian.net/package/node-stringmap


   Alternatively, one can download the package with dget using this command:

 dget -x 
http://mentors.debian.net/debian/pool/main/n/node-stringmap/node-stringmap_0.2.2+20130926-1.dsc

Thanks,

Snark on #debian-js--- End Message ---

Bug#802006: marked as done (RFS: node-stringset/0.2.1+20130926-1 [ITP])

[Debian Bug Tracking System]

Your message dated Sat, 17 Oct 2015 12:48:15 + (UTC)
with message-id <629136726.2672304.1445086096000.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#802006: RFS: node-stringset/0.2.1+20130926-1 [ITP]
has caused the Debian Bug report #802006,
regarding RFS: node-stringset/0.2.1+20130926-1 [ITP]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
802006: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=802006
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-stringset"

 * Package name: node-stringset
   Version : 0.2.1+20130926-1
   Upstream Author : Olov Lassus
 * URL : https://github.com/olov/stringset
 * License : Expat
   Section : web

  It builds those binary packages:

libjs-stringset - fast and robust stringset (JavaScript lib)
 node-stringset - fast and robust stringset (Node.js module)

  To access further information about this package, please visit the 
following URL:


  http://mentors.debian.net/package/node-stringset


  Alternatively, one can download the package with dget using this command:

dget -x 
http://mentors.debian.net/debian/pool/main/n/node-stringset/node-stringset_0.2.1+20130926-1.dsc


Thanks,

Snark on #debian-js
--- End Message ---
--- Begin Message ---
Hi, Built, thanks for your contribution to Debian!

cheers,

G.





Il Venerdì 16 Ottobre 2015 21:33, Julien Puydt  ha 
scritto:
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "node-stringset"

  * Package name: node-stringset
Version : 0.2.1+20130926-1
Upstream Author : Olov Lassus
  * URL : https://github.com/olov/stringset
  * License : Expat
Section : web

   It builds those binary packages:

 libjs-stringset - fast and robust stringset (JavaScript lib)
  node-stringset - fast and robust stringset (Node.js module)

   To access further information about this package, please visit the 
following URL:

  http://mentors.debian.net/package/node-stringset


   Alternatively, one can download the package with dget using this command:

 dget -x 
http://mentors.debian.net/debian/pool/main/n/node-stringset/node-stringset_0.2.1+20130926-1.dsc

Thanks,

Snark on #debian-js--- End Message ---

Bug#797766: marked as done (RFS: pac/4.5.5.5 [ITP] -- friendly greeter)

[Debian Bug Tracking System]

Your message dated Sat, 17 Oct 2015 13:25:07 + (UTC)
with message-id <1600414406.2666049.1445088307544.javamail.ya...@mail.yahoo.com>
and subject line 
has caused the Debian Bug report #797766,
regarding RFS: pac/4.5.5.5 [ITP] -- friendly greeter
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
797766: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=797766
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

I am looking for a sponsor for my package "pac":

 Package name: pac
 Version : 4.5.5.5
 Upstream Author : David Torrejon, david...@gmail.com
 URL : https://github.com/perseo22/pacmanager
 URL : https://sourceforge.net/projects/pacmanager/
 License : GPLv3+
 Section : Internet

It builds those binary packages:

  pac  - PAC Perl Auto Connector

To access further information about this package, please visit the
following URL:

https://sites.google.com/site/davidtv/


More information about pac can be obtained from
https://sourceforge.net/projects/pacmanager/.

Changes since the last upload:

- 4.5.5.6:

. Minor variable substitution () bugfixing

- 4.5.5.5:

. Modified "SSH" Advanced Options, to be more GUI friendly, and with a
context menu to show available SSH advance opt
. Modified "SFTP" Advanced Options, to be more GUI friendly, and with a
context menu to show available SFTP advance o
. Added an option to show the command line that each connection will
launch, under "Edit"->"Advanced Parameters"->"Ge
. Fixed a bug that prevented some SSH users from forwarding ports: "/"
syntax not recognized by *every* SSH client. G
. Minor fixes

- 4.5.5.4:

. Added support to allow per-connection "select by words"
. Nth "/r" fix... :(

- 4.5.5.3:

. Another "/r" bugfix... (hope it's the last!)

- 4.5.5.2:

. Fixed a bug with older Perl version not recognizing "/r" regexp
modifier (terminal ransparency related...)
. Fixed a bug which prevented the use os "word chars" in a "per
terminal" basis

- 4.5.5.1:

. Added support for ARMV7L devices! (Tested on my HTC One M7 phone with
Perl v5.20!)
. Fixed a bug that prevented terminal transparency from being saved
. Fixed a bug that prevented forwarding CLIPBOARD for "rdesktop"
connections (xfreerdp is still buggy!)
. Removed the w shortcut to open the "Wake On LAN" window
. Fixed a little bug regarding "autohide connections list on connection
open" not working correctly
. Fixed a little bug  regarding Preferences window not showing again if
previously was clos viz the "x" window button
. Modified the "Split" routine to try to give same space to splitted
terminals


Thanks a lot in advance!!

Regards,
David TV.
--- End Message ---
--- Begin Message ---
Closing in the meanwhile--- End Message ---

Bug#802140: RFS: django-jinja/1.4.1-2 -- Jinja2 templating integrated in Django

[Edward Betts]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "django-jinja"

 * Package name: django-jinja
   Version : 1.4.1-1
   Upstream Author : Andrey Antukh 
 * URL : https://github.com/niwibe/django-jinja
 * License : BSD-3-clause
   Section : python

It builds those binary packages:

  python-django-jinja - Jinja2 templating language integrated in Django
  python3-django-jinja - Jinja2 templating language integrated in Django 
(Python 3 version)

To access further information about this package, please visit the following 
URL:

  http://mentors.debian.net/package/django-jinja

Alternatively, one can download the package with dget using this command:

  dget -x 
http://mentors.debian.net/debian/pool/main/d/django-jinja/django-jinja_1.4.1-1.dsc

Changes since the last upload:

  * Update Vcs-* control headers.
  * Remove unused Build-Depends.
  * Fix mistake in description of python3-django-jinja.
  * This package doesn't include a test suite. There is one in the the
upstream git repository but it isn't included in the release tarball. The
Python 3.5 unittest modules tries to load the module even if there is not
test suite. This fails because the module isn't designed to be run outside
django. Disable dh_auto_test. (Closes: #801932, #802066)

Regards,
-- 
Edward.

Bug#787861: review: polyml

[James Clarke]

Hi Gianfranco,

> I sponsored the package

Thank you again for all your help.

> (BTW I was intending to subscribe to debian-science, but also debian-devel is 
> nice to be subscribed)

I have subscribed to debian-science as well.

> However, I would appreciate a fix for the following missing flags in a future 
> release:
> CXXFLAGS missing (-fPIE):
> LDFLAGS missing (-Wl,-z,now)
> CFLAGS missing (-fPIE):
> LDFLAGS missing (-fPIE -pie -Wl,-z,now)
> you can see the full log here [1] or by using blhc tool
> 
> 
> [1] http://debomatic-i386.debian.net/distribution#unstable/polyml/5.5.2-1/blhc

I have uploaded 5.5.2-2 to mentors (and updated my git repository) enabling all 
hardening flags. I also realised that the new polyc shell script requires gcc 
and libffi-dev to produce standalone executables, so I have added those as 
dependencies for polyml.

Should I push my changes to debian-science/packages/polyml.git (especially 
since that’s the repository in debian/control)? Also, going forwards, if I want 
to get a new version uploaded, do I need to file a new RFS “bug” against 
sponsorship-requests, or should I instead just email debian-science asking for 
a team upload (subject to a review of the package)?

James


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#787861: review: polyml

[James Clarke]

Hi Gianfranco,

>> I have uploaded 5.5.2-2 to mentors (and updated my git repository) enabling 
>> all hardening flags. I also realised that the new polyc shell script 
>> requires gcc and >libffi-dev to produce standalone executables, so I have 
>> added those as dependencies for polyml.
> 
> wonderful, I'll upload again then :)

Great, thanks.

>> Should I push my changes to debian-science/packages/polyml.git (especially 
>> since that’s the repository in debian/control)? Also, going forwards, if I 
>> want to get a >new version uploaded, do I need to file a new RFS “bug” 
>> against sponsorship-requests, or should I instead just email debian-science 
>> asking for a team upload >(subject to a review of the package)?
> 
> yes, and if you can't do it I can do it for you :)

Pushed.

> For another upload you can ping me directly or add an RFS bug, as you prefer.

Ok, I’ll probably come to you first then seeing as creating an RFS bug can be a 
nuisance; having the same uploader would make sense, rather than some new 
person having to start from scratch with the package every time. Of course, if 
you ever want me to find someone else, please say so; I’ll understand :)

Thanks,
James


signature.asc
Description: Message signed with OpenPGP using GPGMail

Bug#787861: review: polyml

[Gianfranco Costamagna]

it is fine, the first upload is always tricky, after things are easier :)


cheers,


G.


Sent from Yahoo Mail on Android

From:"James Clarke" 
Date:Sat, 17 Oct, 2015 at 17:33
Subject:Bug#787861: review: polyml

Hi Gianfranco,

>> I have uploaded 5.5.2-2 to mentors (and updated my git repository) enabling 
>> all hardening flags. I also realised that the new polyc shell script 
>> requires gcc and >libffi-dev to produce standalone executables, so I have 
>> added those as dependencies for polyml.
> 
> wonderful, I'll upload again then :)

Great, thanks.

>> Should I push my changes to debian-science/packages/polyml.git (especially 
>> since that’s the repository in debian/control)? Also, going forwards, if I 
>> want to get a >new version uploaded, do I need to file a new RFS “bug” 
>> against sponsorship-requests, or should I instead just email debian-science 
>> asking for a team upload >(subject to a review of the package)?
> 
> yes, and if you can't do it I can do it for you :)

Pushed.

> For another upload you can ping me directly or add an RFS bug, as you prefer.

Ok, I’ll probably come to you first then seeing as creating an RFS bug can be a 
nuisance; having the same uploader would make sense, rather than some new 
person having to start from scratch with the package every time. Of course, if 
you ever want me to find someone else, please say so; I’ll understand :)

Thanks,


James

Re: [jitsi-dev] Jitsi in Debian

[Damian Minkov]

Hi,

thank you for your time.

On Sat, Oct 17, 2015 at 6:48 AM, Ximin Luo  wrote:
> +debian-mentors for more comments/help
>
> Hi, thanks a lot for the information and pointers! The documentation on why 
> you're bundling various source packages is very useful. I see you also have a 
> similar setup in 
> https://github.com/jitsi/libjitsi/tree/master/resources/install/debian
>
> I've played around with the build processes and have some comments:
>
> 1. You're only building a .orig.tar.gz, but Debian source packages require a 
> .dsc (source package description file) and a .debian.tar.gz (debian packaging 
> contents). After you create a full debian source package that includes all 
> three files, you can then get rid of all of the "debian binary package" stuff 
> from your build.xml scripts, and use the proper debian developer tools 
> instead (e.g. dpkg-buildpackage, etc.

We used to create the source package and from it then create the
needed packages to upload the file to mentors (.dsc debian.tar.gz, a
debian binary and the src package itself), you mean to do this in one
step, we can definitely do that.

>
> 2. In both libjitsi and jitsi: you build up a tmp directory that contains all 
> the sources for a debian package, out of which you build a .orig.tar.gz, but 
> then clean (delete) the whole directory, without trying to create .dsc or 
> .debian.tar.gz from the other files.

The same as above, create needed files on the first step?

>
> 3. After applying the patches from [1] below, and running "ant deb-src 
> -Dlabel="[*], then moving the .orig.tar.gz to the same directory as the 
> temporary jitsi/libjitsi source tree, I can run `debuild -S` inside the 
> temporary source tree. This is the *correct way* to make Debian packages. 
> However, the process fails, for both libjitsi and jitsi. See [2] and [3].
>
> The TL;DR is that it looks like your debian/patches/ are out-of-date, and I'm 
> not familiar enough with the code base, to spend the time right now to debug 
> it.

Will try that. There were a lot of modifications lately and the debian
src packaging needs some love, time we didn't have to continue
investing, as last two attempts ended with no results.

>
> So I wonder, who has been generating the .dsc/.debian.tar.gz files that 
> you've been submitting to Debian FTP? I have been unable to create one myself 
> from your git repos.

I was the one doing it, if you checkout a version near the stable
release you will be able to do so, but latest version needs updating.

>
> In fact, it is better to keep the debian packaging files (i.e. debian/*) in a 
> separate repo, in the top-level directory of the repo. Then, one can generate 
> .orig.tar.gz from the main jitsi/libjitsi repos every release, then import 
> them to the Debian packaging repos. This is a very standard pattern for 
> Debian packaging, supporting by the git-buildpackage tool, see for example 
> [4] where it says "Imported Upstream version" etc. This would be cleaner and 
> cheaper than effectively re-implementing (and maintaining) the Debian 
> toolchain in build.xml.

I'm not sure that we can handle all of the custom stuff just with the
debian build tools, or at least it will be a great effort to do so and
currently I'm not familiar with anyone that can affords this. We were
using ant to do all that stuff, by reusing all the tasks we already
had.
I'm talking for all the tasks in
https://github.com/jitsi/jitsi/blob/master/resources/install/build.xml
from line 2000 to the end (4000+) that do the debian stuff.
Maybe mavenizing the whole project can help cleaning things and make
the debian package easier, but I'm not familiar so much with maven
currently and especially with maven + debian.
I think investing time in this direction if its worth it is better,
this way we can rid of most of the patches and custom work that needs
to be done.
We were also discussing internally about a branch with the debian stuff in it.

>
>> AFAIK the reason why libjitsi is/was blocked is the license for the 
>> javax.sdp/javax.sip API files
>
> Do you have some more details on that?

Personally I don't know. But Ingo Bauersachs and Daniel Pocock have
some progress regarding ice4j and using a package which license is ok,
but need to further check it with them. Libjitis was not updated and
the problem API license hasn't changed.

I will try checking your comments when time permits and comment on them.

Regards
damencho


>
> X
>
> [4] https://anonscm.debian.org/cgit/pkg-privacy/packages/flashproxy.git/log/
>
> 
> 1. Patches for build.xml
> 
>
> Patches are on top of respective HEAD commits at 2015-10-17
>
> jisti: only clean artefacts in "clean" targets to allow post-build inspection
> 
> diff --git a/resources/install/build.xml b/resources/install/build.xml
> index 3922296..0eadfaf 100644
> ---