Popcon statistics over time for set of packages

[Andreas Tille]

Hi,

I wonder if there is some way to get popcon statistics for a set of
packages to compare their usage over time.  The background is that
I consider to compare the dependencies of Blends metapackages in one
graph.

Kind regards

 Andreas.

-- 
http://fam-tille.de

Bug#854212: RFS: synergy/1.8.7-stable+dfsg.1-1 [ITA]

[Joshua Honeycutt]

On Mon, Feb 6, 2017 at 2:24 AM, Arturo Borrero Gonzalez
 wrote:
> On 6 February 2017 at 09:08, Arturo Borrero Gonzalez  
> wrote:
>>
>> I'm doing a test build now. If all is fine, I will sponsor the upload.
>
> The package seems to FTBFS due to a failing test:
>
> [...]
> [--] Global test environment tear-down
> [==] 9 tests from 3 test cases ran. (2153 ms total)
> [  PASSED  ] 8 tests.
> [  FAILED  ] 1 test, listed below:
> [  FAILED  ] ArchInternetTests.get
>
>  1 FAILED TEST
> debian/rules:94: recipe for target 'test' failed
> make: *** [test] Error 1
> dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 
> 2
> [...]
>
> My complete build log here: http://termbin.com/mrib
>
> Please, fix and ping me.

I have disabled some tests that depend on network access that will fix
the FTBFS.

I didn't fully consider how the migration process works during a
freeze. It was not my intent wasn't for this package to be pushed into
stretch because it doesn't appear acceptable under the freeze policy.
So I have changed the distribution to be 'experimental' based on Sean
Whitton's suggestion.

A new package was uploaded to mentors.

Bug#841185: closing RFS: genwqe-user/4.0.18-1 [ITP #826774]

[Breno Leitao]

Hi Fernando,

On Tue, 31 Jan 2017 22:44:49 -0200 Fernando Seiti Furusato
 wrote:
> I fixed some problems with the package, that is why I reopened this RFS.

This packages sounds in a good shape for me. If no one has objection to it, I
would like to sponsor it to be included in contrib archive.

Bug#854395: RFS: golang-go-xdg/0~bzr20140219-2 [RC] -- Go interface for XDG standards

[Andrey Rahmatullin]

On Tue, Feb 07, 2017 at 01:04:12AM +0900, Roger Shimizu wrote:
> This pkg is removed from testing on Jan. 14th [0].
> So it means even after fixing the FTBFS, it cannot go back to testing again?
Yes, until the stretch release.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

Bug#854395: RFS: golang-go-xdg/0~bzr20140219-2 [RC] -- Go interface for XDG standards

[Roger Shimizu]

On Tue, Feb 7, 2017 at 12:48 AM, Andrey Rahmatullin  wrote:
> On Tue, Feb 07, 2017 at 12:33:08AM +0900, Roger Shimizu wrote:
>>   Changes since the last upload:
>>
>>   * Team upload.
>>
>>   [ Paul Tagliamonte ]
>>   * Use a secure transport for the Vcs-Git and Vcs-Browser URL
>>
>>   [ Roger Shimizu ]
>>   * debian/control:
>> - Update Build-Depends on golang-check.v1-dev, in stead of
>>   golang-gocheck-dev which is already non-active upstream.
>> - Use cgit URL for Vcs-Browser.
>>   * debian/patches:
>> - Add a patch to use golang-check.v1-dev.
>> - Add a patch to remove failure tests (Closes: #830446).
> If you want this to go to stretch please read
> https://release.debian.org/stretch/freeze_policy.html first.

Thanks for your reply!

This pkg is removed from testing on Jan. 14th [0].
So it means even after fixing the FTBFS, it cannot go back to testing again?

I already tried to minimize the changes..

[0] https://tracker.debian.org/news/832624

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Bug#854395: RFS: golang-go-xdg/0~bzr20140219-2 [RC] -- Go interface for XDG standards

[Andrey Rahmatullin]

On Tue, Feb 07, 2017 at 12:33:08AM +0900, Roger Shimizu wrote:
>   Changes since the last upload:
> 
>   * Team upload.
> 
>   [ Paul Tagliamonte ]
>   * Use a secure transport for the Vcs-Git and Vcs-Browser URL
> 
>   [ Roger Shimizu ]
>   * debian/control:
> - Update Build-Depends on golang-check.v1-dev, in stead of
>   golang-gocheck-dev which is already non-active upstream.
> - Use cgit URL for Vcs-Browser.
>   * debian/patches:
> - Add a patch to use golang-check.v1-dev.
> - Add a patch to remove failure tests (Closes: #830446).
If you want this to go to stretch please read
https://release.debian.org/stretch/freeze_policy.html first.

-- 
WBR, wRAR


signature.asc
Description: PGP signature

BeMyStreet devient gratuit pour les pros

[BeMyStreet]

BeMyStreet devient gratuit pour les pros.

Nous avons une bonne nouvelle pour vous ! BeMyStreet devient gratuit pour les 
professionnels pour votre plus grand plaisir. Alors ne vous en privez surtout 
pas, vendez en ligne facilement et profitez de tous les avantages BeMyStreet :

***Visibilité***

Votre boutique apparaît dans chacune des rues de vos abonnés.


***Simplicité***

Gérez vos pages et votre vitrine simplement grâce à nos outils et nos conseils.


Multipliez vos contacts*

Les relations se tissent de proche en proche sur le réseau social.


***Efficacité***

Communiquez efficacement grâce à vos pages, vos actualités ou la messagerie.


**Opportunité***

Avancez et sautez le pas de la vente en ligne, avec BeMyStreet c'est simple.


**Aucun risque**

Accédez à ce concept unique, dynamique et innovateur pour un tarif sans risque.


BeMyStreet est un réseau social orienté vente en ligne sur lequel les 
professionnels bénéficient d'outils simples et efficaces pour être visibles, 
communiquer, et développer leur activité en ligne.

BeMystreet se rémunère principalement sur les commissions de vente de vos 
produits, cela vous garantit que nous ferons toujours le maximum pour que vous 
vendiez vos produits ! Alors inscrivez-vous, parlez-en autour de vous et 
partagez...

Avec la gratuité, plus aucun risque pour vous, vous avez tout à gagner...


Découvrir ici : http://bemystreet.com

Vous avez une question ? N'hésitez pas à nous contacter en répondant à ce mail.

A tout de suite sur BeMyStreet
bemystreet.com

Bug#854395: RFS: golang-go-xdg/0~bzr20140219-2 [RC] -- Go interface for XDG standards

[Roger Shimizu]

Package: sponsorship-requests
Severity: important
X-Debbugs-Cc: pkg-go-maintain...@lists.alioth.debian.org,
sergio.schve...@canonical.com, t...@pault.ag, rogershim...@gmail.com

Dear mentors,

I am looking for a sponsor for my package "golang-go-xdg"

 * Package name: golang-go-xdg
   Version : 0~bzr20140219-2
   Upstream Author : John R. Lenton.
 * URL : https://launchpad.net/go-xdg
 * License : BSD-2-Clause
   Section : devel

  It builds those binary packages:

golang-go-xdg-dev - Go interface for XDG standards

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

  https://mentors.debian.net/package/golang-go-xdg

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

dget -x 
https://mentors.debian.net/debian/pool/main/g/golang-go-xdg/golang-go-xdg_0~bzr20140219-2.dsc

or you can use git-buildpackage to build:
  gbp clone --pristine-tar
https://anonscm.debian.org/git/pkg-go/packages/golang-go-xdg.git
  cd golang-go-xdg
  git checkout mentors
  gbp buildpackage -uc -us --git-ignore-branch --git-pristine-tar

I also made it available on debomatic (amd64):
  
http://debomatic-amd64.debian.net/distribution#unstable/golang-go-xdg/0~bzr20140219-2/buildlog

  Changes since the last upload:

  * Team upload.

  [ Paul Tagliamonte ]
  * Use a secure transport for the Vcs-Git and Vcs-Browser URL

  [ Roger Shimizu ]
  * debian/control:
- Update Build-Depends on golang-check.v1-dev, in stead of
  golang-gocheck-dev which is already non-active upstream.
- Use cgit URL for Vcs-Browser.
  * debian/patches:
- Add a patch to use golang-check.v1-dev.
- Add a patch to remove failure tests (Closes: #830446).

Cheers,
-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 4096R/6C6ACD6417B3ACB1

Bug#854212: RFS: synergy/1.8.7-stable+dfsg.1-1 [ITA]

[Sean Whitton]

On Mon, Feb 06, 2017 at 09:08:36AM +0100, Arturo Borrero Gonzalez wrote:
> I'm doing a test build now. If all is fine, I will sponsor the upload.
> 
> Keep in mind the stretch freeze. May the release team have any
> comment/requirement regarding this package, please be responsive.

Shouldn't this go into experimental?  Otherwise, it will block uploading
fixes for RC bugs to unstable.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Bug#853903: RFS: scap-security-guide/0.1.31-6 [ITP] -- security guides and conformity checks using SCAP standard

[phil]

Hi Gianfranco,

Le 2017-02-02 18:13, Gianfranco Costamagna a écrit :

control: owner -1 !
control: tags -1 moreinfo
control: forcemerge 853903 852415


Hello

lets see a preliminary review:

1) one single changelog entry, targeting sid and initial release 
(Closes: #ITP)

2) debian/rules, lots of comented out noise, please remove
3) copyright not in dep-5 format, and some stuff is LGPL-2+ e.g.
shared/transforms/pcidss/something
some other is MIT (Ubuntu/16.04 some subdirs), something else
CC-BY-SA, JQuery license,
Public domain, GPL and probably something more


4) compat is now 10, please bump also debhelper to >=10
5) how do you use libopenscap8? dynamic loading or linking?
if you link it, just build-depend on the -dev package and add
shlibs:Depends to the runtime dependencies
(avoiding nightmares on libopenscap8 SONAME changes)
6) quilt dependency is useless, and probably also some others, e.g.
coreutils, part of Essentials packages
(you can't remove it on a system)
also probably sed and not sure about the others (to find them I
usually try to remove them on my system)
7) ssg-base depends on libopenscap8
everything else depends on ssg-base, so transitively also against
libopenscap8 making it useless to be replicated,
right?


8) does not build twice in a row (not a real issue)
9) debian/ssg-base.prerm what???
10) debian/README <--- useless?
11) debian/README.Debian might be made more aware of directories, e.g.
/usr/share/ssg" might save some sed'ing before running the command,
unless you want to change packagename in the near future



Thank's for this reply. Here is the various updates/answers:

1) Exact, targeting sid only by now.
2) Corrected. No more noise in rules file
3) Corrected. All various upstream and debian files copyrights and 
licenses are defined properly in debian/copyright

4) Corrected.
5) libopenscap is used as a binary at build time (using oscap xccdf ... 
to generate guides and benchmarks). There is no link or dynamic loading. 
libopenscap is not a library but a binary tools suite (even if its name 
make it look like a lib :-) )

6) Corrected.
7) Corrected.
8) Ok. I have to check why. I build through gbp and pbuilder so I didn't 
see this issue
9) Deleted that file. Waiting for upstream changelog instead of using 
inproper spec file. I've posted an issue in the upstream repository to 
have a real changelog file.

10) File deleted.
11) I've updated the file to be more explicit. Yet I think that it still 
need some more content.




http://debomatic-amd64.debian.net/distribution#unstable/scap-security-guide/0.1.31-6/buildlog

since this is just some xml files that are needed by libopenscap8...
what about suggesting this new package or merging it on that above 
tool?


I don't undestand why the tool and the profiles have to be kept 
separate


Why libopenscap8 & scap-workbench & scap-security-guide are separated:

libopenscap8 is a set of tool using the SSG benchmarks to validate the 
current OS security policy in comparison with official ones such as 
PCI-DSS, NIST SP-800, ANSSI best practices, etc. Nevertheless, the 
following case exists:

1) Hosting security policy in a security server
2) Hosting libopenscap on various targets
3) Launching security policy validation on remote targets automatically 
using ansible, foreman, oscap-ssh or other to validate the policy of 
each remote host from a single policy server and aggregate the results


In that case, the security policy server only hosts the security 
policies, not the libopenscap8. You will have something like that:

https://www.theforeman.org/plugins/foreman_openscap/0.4/

I've updated the scap-security-guide package to set libopenscap as 
"Recommends" instead of Depends at runtime for all binary pacakges.


All these updates have been made in the 0.31.1-8 release of the package:

https://mentors.debian.net/debian/pool/main/s/scap-security-guide/scap-security-guide_0.1.31-8.dsc


Regards,

--
Philippe THIERRY
Doctor - Engineer
RT and hardened Embedded Systems
+33(0)6.64.16.97.30

Re: Packaging from Git

[Arturo Borrero Gonzalez]

On 6 February 2017 at 12:25, Narcis Garcia  wrote:
> Very far from the number of libs/tools that cannot unmask something like
> Alexander Wirt formorer formorer de at anywhere of a page.
>

Probably this mentors mailing list isn't the right place for this discussion.

Re: Packaging from Git

[Narcis Garcia]

__
I'm using this express-made address because personal addresses aren't
masked enough at this list's archives. Mailing lists service
administrator should fix this.
El 06/02/17 a les 11:16, Alexander Wirt ha escrit:
> On Mon, 06 Feb 2017, Narcis Garcia wrote:
> 
>> __
>> I'm using this express-made address because personal addresses aren't
>> masked enough at this list's archives. Mailing lists service
>> administrator should fix this.
>> El 06/02/17 a les 10:42, Alexander Wirt ha escrit:
>>> On Mon, 06 Feb 2017, Narcis Garcia wrote:
>>>
 __
 I'm using this express-made address because personal addresses aren't
 masked enough at this list's archives. Mailing lists service
 administrator should fix this.
>>> We don't intend to. Debian is an open Distribution and we believe in being
>>> able to be able to contact distributors and not to hide them. 
>>>
>>> Alex - Debian Listmaster
>>>  
>>>
>>
>> Mask and hide are two different measures.
>> A simple masking example, without hiding any data:
>> http://llista.gilug.org/pipermail/usuaris/2017-January/005484.html
> I can show you a dozen libs that unmasks those things. 
> 
> Alex
>  
> 

Very far from the number of libs/tools that cannot unmask something like
Alexander Wirt formorer formorer de at anywhere of a page.

Re: Packaging from Git

[Alexander Wirt]

On Mon, 06 Feb 2017, Narcis Garcia wrote:

> __
> I'm using this express-made address because personal addresses aren't
> masked enough at this list's archives. Mailing lists service
> administrator should fix this.
> El 06/02/17 a les 10:42, Alexander Wirt ha escrit:
> > On Mon, 06 Feb 2017, Narcis Garcia wrote:
> > 
> >> __
> >> I'm using this express-made address because personal addresses aren't
> >> masked enough at this list's archives. Mailing lists service
> >> administrator should fix this.
> > We don't intend to. Debian is an open Distribution and we believe in being
> > able to be able to contact distributors and not to hide them. 
> > 
> > Alex - Debian Listmaster
> >  
> > 
> 
> Mask and hide are two different measures.
> A simple masking example, without hiding any data:
> http://llista.gilug.org/pipermail/usuaris/2017-January/005484.html
I can show you a dozen libs that unmasks those things. 

Alex
 

Re: Packaging from Git

[Narcis Garcia]

__
I'm using this express-made address because personal addresses aren't
masked enough at this list's archives. Mailing lists service
administrator should fix this.
El 06/02/17 a les 10:42, Alexander Wirt ha escrit:
> On Mon, 06 Feb 2017, Narcis Garcia wrote:
> 
>> __
>> I'm using this express-made address because personal addresses aren't
>> masked enough at this list's archives. Mailing lists service
>> administrator should fix this.
> We don't intend to. Debian is an open Distribution and we believe in being
> able to be able to contact distributors and not to hide them. 
> 
> Alex - Debian Listmaster
>  
> 

Mask and hide are two different measures.
A simple masking example, without hiding any data:
http://llista.gilug.org/pipermail/usuaris/2017-January/005484.html

Re: Packaging from Git

[Alexander Wirt]

On Mon, 06 Feb 2017, Narcis Garcia wrote:

> __
> I'm using this express-made address because personal addresses aren't
> masked enough at this list's archives. Mailing lists service
> administrator should fix this.
We don't intend to. Debian is an open Distribution and we believe in being
able to be able to contact distributors and not to hide them. 

Alex - Debian Listmaster
 

Re: Packaging from Git

[Narcis Garcia]

__
I'm using this express-made address because personal addresses aren't
masked enough at this list's archives. Mailing lists service
administrator should fix this.
El 05/02/17 a les 21:25, Gianfranco Costamagna ha escrit:
> Hi,
> 
> 
> 
>> You are expected to set that bit on the file and commit it. Gitlab has
>> nothing to do with this.
> 
> 
> stuff like github now allows to modify files and commit them from the web 
> interface
> (without having to checkout the repo).
> I'm not sure about gitlab interface, but I don't think you can chmod from the 
> web
> interface
> 
> G.
> 

About executable attribute for files:
I'm trying to use only FOSS, not Github.
I'm currently not uploading files to Gitlab CMS through Git but I write
them directly through the web interface and editor.

Bug#854212: RFS: synergy/1.8.7-stable+dfsg.1-1 [ITA]

[Arturo Borrero Gonzalez]

On 6 February 2017 at 09:08, Arturo Borrero Gonzalez  wrote:
>
> I'm doing a test build now. If all is fine, I will sponsor the upload.

The package seems to FTBFS due to a failing test:

[...]
[--] Global test environment tear-down
[==] 9 tests from 3 test cases ran. (2153 ms total)
[  PASSED  ] 8 tests.
[  FAILED  ] 1 test, listed below:
[  FAILED  ] ArchInternetTests.get

 1 FAILED TEST
debian/rules:94: recipe for target 'test' failed
make: *** [test] Error 1
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
[...]

My complete build log here: http://termbin.com/mrib

Please, fix and ping me.

Bug#854212: RFS: synergy/1.8.7-stable+dfsg.1-1 [ITA]

[Arturo Borrero Gonzalez]

On 5 February 2017 at 07:12, Joshua Honeycutt
 wrote:
> Alternatively, one can download the package with dget using this command:
>
> dget -x 
> https://mentors.debian.net/debian/pool/main/s/synergy/synergy_1.8.7-stable+dfsg.1-1.dsc
>
> More information about hello can be obtained from https://www.example.com.
>

 please review a bit more the template :-)

I'm doing a test build now. If all is fine, I will sponsor the upload.

Keep in mind the stretch freeze. May the release team have any
comment/requirement regarding this package, please be responsive.

thanks for taking care of this package :-)