Bug#932667: RFS: coccinelle/1.0.7.deb-2 [ITA]

[eamanu15 .]

Thanks Kyle for you quick response.

I will work on this errors.

Cherrs,

El dom., 21 de jul. de 2019 a la(s) 16:36, Kyle Robbertze (
paddatrap...@debian.org) escribió:

> Hi,
>
> On 7/21/19 8:56 PM, eamanu15 . wrote:
> > To access further information about this package, please visit the
> > following URL:
> >
> > https://mentors.debian.net/package/coccinelle
> >
>
> There are lintian errors, please fix them:
>
> * doc-base-file-references-missing-file
> * ocaml-dangling-cmx (you need to install the corresponding .o files too)
> * manpage-has-errors-from-man
> * spelling-error-in-copyright
> * debian-rules-uses-unnecessary-dh-argument
> * useless-autoreconf-build-depends
>
> Cheers
> --
>
> ⢀⣴⠾⠻⢶⣦⠀
> ⣾⠁⢠⠒⠀⣿⡁ Kyle Robbertze
> ⢿⡄⠘⠷⠚⠋⠀ Debian Developer
> ⠈⠳⣄ https://wiki.debian.org/KyleRobbertze
>
>

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Bug#932667: RFS: coccinelle/1.0.7.deb-2 [ITA]

[eamanu15 .]

Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

Dear mentors,

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

* Package name: coccinelle
 Version : 1.0.7.deb-2
 Upstream Author : Julia Lawall 
   Yoann Padioleau 
   Rene Rydhof Hansen 
   Henrik Stuart 
   Gilles Muller
   Nicolas Palix
* URL : https://github.com/coccinelle
* License : GPL-2.0
 Section : devel

It builds those binary packages:

  coccinelle - semantic patching tool for C
coccinelle-doc - documentation for coccinelle

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

https://mentors.debian.net/package/coccinelle


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

  dget -x
https://mentors.debian.net/debian/pool/main/c/coccinelle/coccinelle_1.0.7.deb-2.dsc

More information about coccinelle can be obtained from
http://coccinelle.lip6.fr

Changes since the last upload:

  * New Maintainer (Closes: #886679)
- Add mysefl to Uploaders field on d/control
  * Update d/control file
- Bump debhelper to debhelper-compat (=12)
  * Remove d/compat
  * Run wrap-and-sort

Regards,
 Emmanuel Arias

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Bug#930664: ITP: libcamera/0~190601-1

[eamanu15 .]

El vie., 19 de jul. de 2019 a la(s) 16:20, Andrej Shadura (
andrew.shad...@collabora.co.uk) escribió:

> Hi,
>
> On 19/07/2019 16:15, eamanu15 . wrote:
> > Hello Andrej,
> >
> > I am updating to 36d6229 sha git version. I want to upload to
> experimental
> >
> > The error is because is compiled with Werror and fail
> > for a warning:
> >
> > ../src/libcamera/process.cpp:74:13: error: ignoring return value of
> > ‘ssize_t write(int, const void*, size_t)’, declared with attribute
> > warn_unused_result [-Werror=unused-result]
> >   (void)write(ProcessManager::instance()->writePipe(), ,
> sizeof(data));
> >
> ~^~
> > cc1plus: all warnings being treated as errors
>
> As I said in my previous email, there’s nothing that needs to be done
> now, the package has already been uploaded, it’s best if we wait for it
> to pass NEW before doing anything else.
>

Righ! oka thanks! :-)

>
> --
> Cheers,
>   Andrej
>


-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Bug#930664: ITP: libcamera/0~190601-1

[eamanu15 .]

Hello Andrej,

I am updating to 36d6229 sha git version. I want to upload to experimental

The error is because is compiled with Werror and fail
for a warning:

../src/libcamera/process.cpp:74:13: error: ignoring return value of
‘ssize_t write(int, const void*, size_t)’, declared with attribute
warn_unused_result [-Werror=unused-result]
  (void)write(ProcessManager::instance()->writePipe(), , sizeof(data));
~^~
cc1plus: all warnings being treated as errors



El vie., 19 de jul. de 2019 a la(s) 12:16, Andrej Shadura (
andrew.shad...@collabora.co.uk) escribió:

> On 19/07/2019 12:10, eamanu15 . wrote:
> > Hello,
> >
> > I am trying to build an updated packaging.
> >
> > But it is falling:
>
> I’m not sure what error you’re seeing but I have built and uploaded it
> to NEW last week or so.
>
> --
> Cheers,
>   Andrej
>


-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Bug#930664: ITP: libcamera/0~190601-1

[eamanu15 .]

Hello,

I am trying to build an updated packaging.

But it is falling:

[29/150] c++ -Isrc/libcamera/4ab8042@@camera@sha -Isrc/libcamera
-I../src/libcamera -Iinclude -I../include -I../src/libcamera/include
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Werror -std=c++11
-Wno-unused-parameter -include config.h -g -O2
-fdebug-prefix-map=/home/pkg/libcamera/libcamera=. -fstack-protector-strong
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-pthread  -MD -MQ 'src/libcamera/4ab8042@@camera@sha/process.cpp.o' -MF
'src/libcamera/4ab8042@@camera@sha/process.cpp.o.d' -o
'src/libcamera/4ab8042@@camera@sha/process.cpp.o' -c
../src/libcamera/process.cpp
FAILED: src/libcamera/4ab8042@@camera@sha/process.cpp.o
c++ -Isrc/libcamera/4ab8042@@camera@sha -Isrc/libcamera -I../src/libcamera
-Iinclude -I../include -I../src/libcamera/include
-fdiagnostics-color=always -pipe -D_FILE_OFFSET_BITS=64 -Werror -std=c++11
-Wno-unused-parameter -include config.h -g -O2
-fdebug-prefix-map=/home/pkg/libcamera/libcamera=. -fstack-protector-strong
-Wformat -Werror=format-security -Wdate-time -D_FORTIFY_SOURCE=2 -fPIC
-pthread  -MD -MQ 'src/libcamera/4ab8042@@camera@sha/process.cpp.o' -MF
'src/libcamera/4ab8042@@camera@sha/process.cpp.o.d' -o
'src/libcamera/4ab8042@@camera@sha/process.cpp.o' -c
../src/libcamera/process.cpp
../src/libcamera/process.cpp: In function ‘void
libcamera::{anonymous}::sigact(int, siginfo_t*, void*)’:
../src/libcamera/process.cpp:74:13: error: ignoring return value of
‘ssize_t write(int, const void*, size_t)’, declared with attribute
warn_unused_result [-Werror=unused-result]
  (void)write(ProcessManager::instance()->writePipe(), , sizeof(data));
~^~
cc1plus: all warnings being treated as errors

Any idea?
Regards


El mar., 25 de jun. de 2019 a la(s) 15:51, Andrej Shadura (
andrew.shad...@collabora.co.uk) escribió:

> On Wed, 19 Jun 2019 10:38:39 -0300 "eamanu15 ."
>  wrote:
> > > hi.
> > > i haven't looked into your packaging yet, but...
> > >
> > > - i'm interested in sponsoring the package
> > >
> > Great!
>
> I am too interested in sponsoring :)
>
> > - would you consider maintaining the package under the multimedia-team
> > > umbrella?
> > >
> >
> > It would be great. I think I will need to ask for permission to
> > multimedia-team. I will send a mail :-)
>
> I have added you to the salsa project. I have create a repo and will
> push a cleaned up version of your work for you to have a look at.
>
> > > - last time i checked libcamera it wasn't really usable. do you know
> > > anything about the timeframe for a first upstream release? (i haven't
> > > really followed any discussion)
>
> > I think is usable for test. Maybe we will be start with a experimental
> > release for Debian? (Not unstable).
> >
> > I open the discussion for a release, but the developers don't feel that
> > libcamera is ready for a first release yet.  I will contact them for new
> > news.
>
> Probably uploading to experimental first is a good idea.
>
> --
> Cheers,
>   Andrej
>
>

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Bug#930664: ITP: libcamera/0~190601-1

[eamanu15 .]

Hello IOhannes,

Thanks very much for your response.


El mié., 19 de jun. de 2019 05:12, IOhannes m zmölnig 
escribió:

> On Mon, 17 Jun 2019 19:17:39 -0300 "eamanu15 ."
>  wrote:
> > Package: sponsorship-requests
> > Severity: normal
> >
> > Dear mentors,
> >
> > I am looking for a sponsor for my package "libcamera"
>
> hi.
> i haven't looked into your packaging yet, but...
>
> - i'm interested in sponsoring the package
>
Great!

- would you consider maintaining the package under the multimedia-team
> umbrella?
>

It would be great. I think I will need to ask for permission to
multimedia-team. I will send a mail :-)

>
> - last time i checked libcamera it wasn't really usable. do you know
> anything about the timeframe for a first upstream release? (i haven't
> really followed any discussion)
>

I think is usable for test. Maybe we will be start with a experimental
release for Debian? (Not unstable).

I open the discussion for a release, but the developers don't feel that
libcamera is ready for a first release yet.  I will contact them for new
news.

Regards!

mfgsdrt
> IOhannes
>

Bug#930664: ITP: libcamera/0~190601-1

[eamanu15 .]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: libcamera
 Version : 0~190601-1
 Upstream Author : Libcamera 
* URL : http://libcamera.org/
* License : LGPL-2.1+
 Section : libs

It builds those binary packages:

  libcamera - Open-source-friendly camera stack (development file)

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

https://mentors.debian.net/package/libcamera


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

  dget -x
https://mentors.debian.net/debian/pool/main/libc/libcamera/libcamera_0~190601-1.dsc

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

Changes since the last upload:

  * Initial Release


Regards,
 Emmanuel Arias

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Bug#925998: RFS: jcc -- code generator producing a Python extension from Java classes

[eamanu15]

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: cave...@debian.org>

Dear mentors,

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

* Package name: jcc
 Version : 3.5-1
 Upstream Author : The Apache Software Foundation
* URL : http://lucene.apache.org/pylucene/jcc/
* License : Apache 2.0
 Section : oldlibs

It builds those binary packages:

  python-jcc - generator for a Python extension from Java classes (Python 2)
python3-jcc - generator for a Python extension from Java classes (Python 3)
jcc - generator for a Python extension from Java classes (transitional)

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

https://mentors.debian.net/package/jcc


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

  dget -x https://mentors.debian.net/debian/pool/main/j/jcc/jcc_3.5-1.dsc

More information about jcc can be obtained from
http://lucene.apache.org/pylucene/jcc/

Changes since the last upload:

  * New upstream version 3.5.
  * New maintainer (Closes: #922568):
- Add myself to Maintainer field on d/control.
  * Bump debhelper to 12 (from 9.2):
- Update debhelper to debhelper-compat on d/control Build-Depends.
  * Update Vcs-* repository to salsa repository.
  * Add myself on debian/* files copyright on d/copyright.


Regards,
 Emmanuel Arias

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Re: gbp buildpackage test build with uncommitted changes

[eamanu15]

> Thanks a lot *everyone* for the confirmation!
>
> Now I need to figure out why it didn't work for me...
>

Are you working on a particular salsa repo?

Could you let's me know what is it? Could you send me the patch
that you want to add?




-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Bug#923019: RFS: pymacs/0.25-2 [ITA]

[eamanu15]

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: ba...@debian.org

Dear mentors,

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

* Package name: pymacs
 Version : 0.25-2
 Upstream Author : François Pinard 
* URL : http://pymacs.progiciels-bpi.ca/
* License : GPL-2+
 Section : python

It builds those binary packages:

  pymacs - interface between Emacs Lisp and Python

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

https://mentors.debian.net/package/pymacs


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

  dget -x
https://mentors.debian.net/debian/pool/main/p/pymacs/pymacs_0.25-2.dsc

More information about pymacs can be obtained from
http://pymacs.progiciels-bpi.ca/

Changes since the last upload:

[Ondřej Nový]
* Fixed VCS URL (https)
* d/control: Set Vcs-* to salsa.debian.org
* d/copyright: Use https protocol in Format field
* d/control: Remove ancient X-Python-Version field
* Convert git repository from git-dpm to gbp layout

[Emmanuel Arias]
* New Maintainer. Closes (#920406).
  - Update d/control. Add me to Uploaders field.
  - Update d/contorl. Add DPMT to Maintainer field.
* Update d/control.
  - Bump debhelper compatibility to debhelper-compat 11
(from 8).
* Delete d/compat file. This is becauase on d/control
  is set debhelper-compat on version 12.
* Update d/copyright file. Add me on debian/* files copyright.
* Update d/rules. Modify delete --list-missing
  from dh_install from override_dh_install. And add a
  override_dh_missing target where add dh_missing --list-missing
* Bump Standards-Version to 4.3.0 (from 3.9.5)


Regards,
Emmanuel Arias

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Bug#921586: RFS: pymacs/0.25-1.2 [ITA]

[eamanu15]

Hi,

> Any specific reason for using an non-maintainer upload version number
here?
No, I was wrong. I had a problem with package pymacs.
You can see: https://lists.debian.org/debian-mentors/2019/02/msg00153.html

But, I've ready upload to -2 version. I will send the RFS.

Thanks!
Regards!

El vie., 22 de feb. de 2019 a la(s) 15:30, Bart Martens (ba...@debian.org)
escribió:

> Hi Emmanuel,
>
> Good to see you want to adopt this package. However, the version ending
> with -1.2 seems meant for a non-maintainer upload. Any specific reason
> for using an non-maintainer upload version number here?
>
> Cheers,
>
> Bart
>
>

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Re: Problems with packaging on mentors

[eamanu15]

Hi,

El vie., 15 de feb. de 2019 a la(s) 10:32, Andrey Rahmatullin (
w...@debian.org) escribió:

> On Fri, Feb 15, 2019 at 10:15:39AM -0300, eamanu15 wrote:
> > How could I package it to include *tar.gz.asc on .changes file?
> Use dpkg >= 1.18.5.
>

I am using dpkg = 1.19.4

>
> --
> WBR, wRAR
>


-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Problems with packaging on mentors

[eamanu15]

Hello everybody,

I am trying to adopt hollywood

But when I upload to m.d.n I have the next problem:





*gpgv: Signature made Fri 15 Feb 2019 10:01:57 AM UTCgpgv:
using RSA key 13796755BBC72BB8ABE2AEB5FA9DEC5DE11C63F1gpgv: Can't check
signature: No public keydpkg-source: warning: failed to verify signature on
./hollywood_1.14-2.dscdpkg-source: error: cannot fstat file
./hollywood_1.14.orig.tar.gz.asc: No such file or directory*

Looking on .dsc file appear *hollywood_1.14.orig.tar.gz.asc*
But on my .changes file does not.

How could I package it to include *tar.gz.asc on .changes file?

Currently I am using* sbuild -s -A *to package.

Thanks!
Regards!

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Bug#922117: RFS: waybar/0.3.0-1 ITP

[eamanu15]

Ah great

I always saw the upstream code on master.

thanks

El mar., 12 de feb. de 2019 a la(s) 09:30, Birger Schacht (
bir...@rantanplan.org) escribió:

> Hi,
>
> On 2/12/19 1:15 PM, eamanu15 wrote:
> > Hi,
> >
> > A little question, why you don't have the upstream code on salsa?
>
> I do:
> https://salsa.debian.org/bisco-guest/waybar/tree/upstream/0.3.0
>
> cheers,
> Birger
>


-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Bug#922117: RFS: waybar/0.3.0-1 ITP

[eamanu15]

Hi,

A little question, why you don't have the upstream code on salsa?

Regards!

El mar., 12 de feb. de 2019 a la(s) 06:45, Birger Schacht (
bir...@rantanplan.org) escribió:

> Package: sponsorship-requests
> Severity: wishlist
>
> Dear mentors,
>
> I am looking for a sponsor for my package "waybar". Its in experimental,
> because one of the dependencies is still in experimental.
>
> * Package name : waybar
>   Version  : 0.3.0-1
>   Upstream Author  : Alexis Rouillard
> * Url  : https://github.com/Alexays/Waybar/
> * Licenses : Expat,BSL-1.0
>   Programming Lang : C++
>   Section  : x11
>
>  Waybar is a highly customizable wayland bar for Sway and Wlroots based
>  compositors. It features applets displaying information about Sway
>  (Workspaces, Binding mode, Focused window name), Local time, Battery,
>  Network, Pulseaudio, Memory, Cpu load average and custom scripts
>
> It builds those binary packages:
>
>   * waybar
>
> To access further information about this package, visit the following URL:
>
> https://mentors.debian.net/package/waybar
>
> Alternatively, one can download the package with dget using this command:
> dget -x
> https://mentors.debian.net/debian/pool/main/w/waybar/waybar_0.3.0-1.dsc
>
> Alternatively, you can access package debian/ directory via git from URL:
> https://salsa.debian.org/bisco-guest/waybar.git
>
> More information about waybar can be obtained from
> https://github.com/Alexays/Waybar/
>
>
> Regards,
>   Birger
>
>

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Bug#922119: Fwd: RFS: extsmail/2.2-4 -- enables the robust sending of e-mail to external commands

[eamanu15]

Hi,

I am looking that the package does not vcs.
Could create a repo on Salsa? This way is more easy review it.

Regards!

El mar., 12 de feb. de 2019 a la(s) 07:57, Olivier Girondel (
oliv...@biniou.info) escribió:

>
> Package: sponsorship-requests
> Severity: normal
>
>   Dear mentors,
>
>   I am looking for a sponsor for my package "extsmail"
>
>  * Package name: extsmail
>Version : 2.2-4
>Upstream Author : Laurence Tratt 
>  * URL : https://tratt.net/laurie/src/extsmail/
>  * License : BSD/MIT
>Section : mail
>
>   It builds this binary package:
>
> extsmail   - enables the robust sending of e-mail to external commands
>
>   The package appears to be lintian-clean
>
>   To access further information about this package, please visit the
> following URL:
>
>   https://mentors.debian.net/package/extsmail
>
>
>   Alternatively, one can download the package with dget using this command:
>
> dget -x
> https://mentors.debian.net/debian/pool/main/e/extsmail/extsmail_2.2-4.dsc
>
>   Changes since the last upload:
>
>   * debian/tests/control: Fix typo in Test-Command.
>
>   Regards,
>
> --
> Olivier
>
>

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Bug#921586: RFS: pymacs/0.25-1.2 [ITA]

[eamanu15]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: pymacs
 Version : 0.25-1.2
 Upstream Author : François Pinard 
* URL : http://pymacs.progiciels-bpi.ca/
* License : GPL-2+
 Section : python

It builds those binary packages:

  pymacs - interface between Emacs Lisp and Python

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

https://mentors.debian.net/package/pymacs


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

  dget -x
https://mentors.debian.net/debian/pool/main/p/pymacs/pymacs_0.25-1.2.dsc

More information about pymacs can be obtained from
http://pymacs.progiciels-bpi.ca/

Changes since the last upload:

[Ondřej Nový]
* Fixed VCS URL (https)
* d/control: Set Vcs-* to salsa.debian.org
* d/copyright: Use https protocol in Format field
* d/control: Remove ancient X-Python-Version field
* Convert git repository from git-dpm to gbp layout

[Emmanuel Arias]
* New Maintainer. Closes (#920406).
  - Update d/control. Add me to Uploaders field.
  - Update d/contorl. Add DPMT to Maintainer field.
* Update d/control.
  - Bump debhelper compatibility to debhelper-compat 11
(from 8).
* Delete d/compat file. This is becauase on d/control
  is set debhelper-compat on version 12.
* Update d/copyright file. Add me on debian/* files copyright.
* Update d/rules. Modify delete --list-missing
  from dh_install from override_dh_install. And add a
  override_dh_missing target where add dh_missing --list-missing
* Bump Standards-Version to 4.3.0 (from 3.9.5)


Regards,
Emmanuel Arias

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Bug#921403: RFS: pyfltk/1.3.4.1-1 [ITP]

[eamanu15]

Hi,

I was reviewing the package that you upload to mentors.d.n

IMO you have several problem that you need fix:

  * The last version is on UNRELEASED. The package must be on
"unstable".
  * You should write a better debian/changelog. "Initial release
using Python 3" does not give me several information about
the change that you made.
  * You should request access to DPTM (because this is a python
package) and salsa user, this way you can create the repo for
pyflitk and add Vcs-* field on d/control.
  * IMO would be great if you can put the range of year of copyright
on d/copyright. For example, for Charlie S. I will write:
2011-2019, and for you just it is.
  * You don't have the standard version field on d/control.
  * I think that you forgot write the d/rules header
#!/usr/bin/make -f

Please, do not be discouraged. I am just a Debian contributor,
not a mentor or a DD, so I know that the first times could be
I little complicate, but keep going :-)

Regards!
Emmanuel

Bug#921482: RFS: note/1.3.26-3

[eamanu15]

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: kact...@debian.org

Dear mentors,

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

* Package name: note
 Version : 1.3.26-3
 Upstream Author : Thomas von Dein >
* URL : http://www.daemon.de/NOTE
* License : Gnu Public License(GPL)
 Section : utils

It builds those binary packages:

  note  - small program managing notes from commandline

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

https://mentors.debian.net/package/note


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

  dget -x
https://mentors.debian.net/debian/pool/main/n/note/note_1.3.26-3.dsc

More information about note can be obtained from http://www.daemon.de/NOTE

Changes since the last upload:

* Add me to Maintainer Field on d/control:
  - For some reason that I ignore the Maintainer field
  on d/control was not updated.
* Update fix-spelling.patch because is old.
* Delete NOTEDB folder and NOTEDB.pm because they are
  not on upstream from ad6cb95 commit (Github).
* Delete install.sh.
   - This file was forgotten to be deleted by the
   upstream author.
   - delete-install.patch was created
* Update d/watch file to download the upstream version
  from CPAN repository.
* Adding on d/rules a sentence to delete README from
  /usr/share/perl5/NOTEDB/


Regards,
 Emmanuel Arias

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Re: my first debian package

[eamanu15]

Hi!,

Congrats on your first package and welcome to Debian!


https://mentors.debian.net/package/pyfltk
>
> If you see on QA Information you will see that there are some litian
problems,
please check if that problems exist on testing too and try to solve it.

Do you have salsa user? it would great if you have package on salsa.

Then, you have to send a mail to mentors.d.o following this instructions:
https://mentors.debian.net/sponsors/rfs-howto

Regards!


-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Bug#919614: RFS: note/1.3.26-2 [ITA]

[eamanu15]

Hi,

There is proposal (DEP-14) to create tags, like debian/2.1.2-5
> in git repository, that mark state of source package, uploaded in
> archives.
>

I pretend use gbp, I That create the tags and branch
that you mention.

I have a new version 1.3.26-3 applied the fix. I need to create start an
mentors.d.n process
or just I let it know when I ready?

Thanks!
Regards


-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Bug#919614: RFS: note/1.3.26-2 [ITA]

[eamanu15]

Hi!

  * you seems to not push debian/* tags. They makes understanding history
>of package simplier
>

I don't understand this point

Bug#919614: RFS: note/1.3.26-2 [ITA]

[eamanu15]

Hello Dmitry,


> Uploaded. There is some things you may want to address in next revision:
>
>  * debian/watch uses plain http. Any chance for https?
>  * there is a lot of spelling errors. Please fix them and submit patch
>upstream.
>  * /usr/share/perl5/NOTEDB/README is bad. Move it into documentation.
>

That observation are correct. I will work on that.

Thanks!



-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Bug#919614: RFS: note/1.3.26-2 [ITA]

[eamanu15]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: note
 Version : 1.3.26-2
 Upstream Author : Thomas von Dein 
* URL : http://www.daemon.de/NOTE
* License : Gnu Public License(GPL)
 Section : utils

It builds those binary packages:

  note  - small program managing notes from commandline

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

https://mentors.debian.net/package/note


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

  dget -x
https://mentors.debian.net/debian/pool/main/n/note/note_1.3.26-2.dsc

More information about note can be obtained from http://www.daemon.de/NOTE

Changes since the last upload:

* New Maintainer (Closes: 900663).
  - Add me to Maintainer Field on d/control.
  - Update Vcs-* field to my own repo.
  - Add me to Copyright field for debian/* files.


Regards,
 Emmanuel Arias

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Bug#917854: RFS: pygithub/1.43.3-1

[eamanu15]

Hi Dmitry!

El jue., 3 de ene. de 2019 a la(s) 01:13, Dmitry Bogatov (kact...@debian.org)
escribió:

>
> As other folks already mentioned, you do not use CC: you already use
> X-Debbugs-CC. In this particular case, email with bug number got
> filtered-out as duplicate in my setup.
>
> Ok. The next time I will use just X-Debbugs-CC


> [2018-12-31 00:16] eamanu15 
> > I am looking for a sponsor for my package "pygithub"
> >
> > * Package name: pygithub
> > Version : 1.43.3-1
> > Upstream Author : Adam Dangoor 
> >   Vincent Jacques 
> >   Jeremy Phelps 
> > * URL : https://pypi.python.org/pypi/PyGithub
> > * License : LGPL-3+
> >   Section : python
> >
> > It builds those binary packages:
> >
> > python-github - Access to full Github API v3 from Python2
> > python3-github - Access the full Github API v3 from Python3
>
> Looks fine, but I do not understand following line in `debian/rules':
>
> rm -rfv debian/python3-github/usr/lib/python3.*
>

> What is removed and why same statement it is not needed for python2
> version?  Comment in `debian/rules' would be nice.
>

Really I don't remember and I don't sit down in front of own system right
now.

>
> And some very minor suggestions:
>
>  * Standards-Version slightly outdated
>  * debhelper-compat style reduces redundancy
>  * Probably F-variables could be used to avoid repetition in
>binary package descriptions? (See dpkg-substvars(5))
>

Thanks for your suggestions I will work in it.

>
> I do not know habits of Python Modules Team, but would not it be more
> apporiate for this packages to be sponsored by DD from team? I can check
> basic things, but I do not know whole picture, like transitions or
> reverse dependencies.
>

Yes, I'll keep looking.

>
> PS. I am glad to see that pygithub finally moved under aegis of
> Python Modules Team.
>

Regards!


-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Re: RFS: impacket/0.9.17-1

[eamanu15]

Hi

El lun., 31 de dic. de 2018 15:35, Sergio Durigan Junior <
sergi...@debian.org> escribió:

> On Monday, December 31 2019, eamanu wrote:
>
> > El lun., 31 de dic. de 2018 a la(s) 10:17, Mattia Rizzolo (
> mat...@debian.org)
> > escribió:
> >
> >>
> >> Hi Emmanuel,
> >>
> >> On Mon, Dec 31, 2018 at 12:11:53AM -0300, eamanu15 wrote:
> >> > Package: sponsorship-requests
> >> > Severity: normal
> >> > X-Debbugs-CC: kact...@debian.org
> >>
> >> Taking this random RFS bug as an example, please:
> >>
> >> * don't explicitly CC anybody while sending mails to submit@, as they
> >>   will receive your mail without the bug reference, making answering
> >>   properly a mess.
> >>   This is particularly interesting since you seem to be aware of the
> >>   X-Debbugs-CC field that you use
> >>
> >
> > Yes, I want to that X-Debbugs-CC recipient follow my packages. In the
> > future
> > I will send him directly the bug number
>
> What Mattia actually meant is that X-Debbugs-CC is the right way to CC
> someone when you're creating the bug.  You should not use regular CC,
> and you don't need to "send him directly the bug number".
>

Ahh okas! Thanks for the explanation.

Regards

>
> Thanks,
>
> --
> Sergio
> GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
> Please send encrypted e-mail if possible
> http://sergiodj.net/
>

Re: RFS: impacket/0.9.17-1

[eamanu15]

Hi Mattia,

Thanks for you response me.

El lun., 31 de dic. de 2018 a la(s) 10:17, Mattia Rizzolo (mat...@debian.org)
escribió:

>
> Hi Emmanuel,
>
> On Mon, Dec 31, 2018 at 12:11:53AM -0300, eamanu15 wrote:
> > Package: sponsorship-requests
> > Severity: normal
> > X-Debbugs-CC: kact...@debian.org
>
> Taking this random RFS bug as an example, please:
>
> * don't explicitly CC anybody while sending mails to submit@, as they
>   will receive your mail without the bug reference, making answering
>   properly a mess.
>   This is particularly interesting since you seem to be aware of the
>   X-Debbugs-CC field that you use
>

Yes, I want to that X-Debbugs-CC recipient follow my packages. In the
future
I will send him directly the bug number

* don't CC debian-mentors, as they are recipients of the
>   sponsorship-requests pseudo-package anyway, so currently
>   debian-mentors received double of your mails.
>
Okas. Soory and thanks!

>
> Thank you.
>
> --
> regards,
> Mattia Rizzolo
>
> GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
> more about me:  https://mapreri.org : :'  :
> Launchpad user: https://launchpad.net/~mapreri  `. `'`
> Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-
>

Regards!


-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

RFS: pcapy/0.11.4-1 [ITA]

[eamanu15]

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: kact...@debian.org

Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

Dear mentors,

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

* Package name: pcapy
Version : 0.11.4-1
Upstream Author : Core Security 
* URL : https://github.com/CoreSecurity/pcapy
* License : Apache Software License
Section : python


It builds those binary packages:

python-pcapy - Python interface to the libpcap packet capture library
(Python 2)
python3-pcapy - Python interface to the libpcap packet capture library
(Python 3)

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

https://mentors.debian.net/package/pcapy


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

dget -x
https://mentors.debian.net/debian/pool/main/p/pcapy/pcapy_0.11.4-1.dsc


Changes since the last upload:

[ Jakub Wilk ]
* Use canonical URIs for Vcs-* fields.

[ Ondřej Nový ]
* Fixed VCS URL (https)
* d/control: Set Vcs-* to salsa.debian.org
* d/changelog: Remove trailing whitespaces
* Remove debian/pycompat, it's not used by any modern Python helper
* Convert git repository from git-dpm to gbp layout

[ Emmanuel Arias ]
* new upstream version to 0.11.4
* Fix d/watch. This had has some errors reported for Lintian.
* Create and init git-dpm for the package
* Get DEP-5 format to d/copyright and correct LICENCE
* Add Testsuite: autopkgtest-pkg-python to debian/changelog
* Update Standards-Version from 3.9.2 to 4.1.3
* Update Homepage from debian/changelog
* Add export PYBUILD_NAME=pcapy to d/rules
* Add export DEB_BUILD_MAINT_OPTIONS = hardening=+all  to d/rules
* Add the rm'ing LICENCE file after install on d/rules
* Update d/compat to from 5 to 11
* Update debhelper to >= 11 on Build-Depends field on d/control file
* Remove the "Suggests: doc-base" from d/control
* Add build for Python3.
* Modify upstream Licence on d/copyright.
* Delete Provides field on d/control.
* Modify Description field on d/control.


Regards,
Emmanuel Arias

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

RFS: python-scp/0.13.0-1

[eamanu15]

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: kact...@debian.org

Dear mentors,

I am looking for a sponsor for my package "python-scp"

* Package name: python-scp
Version : 0.11.0-1
Upstream Author : James Bardin 
* URL : https://github.com/jbardin/scp.py
* License : LGPL-2.1+
Section : python

It builds those binary packages:

python-scp - scp module for paramiko (Python 2)
python3-scp - scp module for paramiko (Python 3)

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

https://mentors.debian.net/package/python-scp


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

dget -x
https://mentors.debian.net/debian/pool/main/p/python-scp/python-scp_0.13.0-1.dsc


Changes since the last upload:

* New Upstream release
* d/control: fix Description for python2
* d/rules: add PYBUILD_NAME variable
* d/rules: add override_dh_auto_clean


Regards,
Emmanuel Arias

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

RFS: pygithub/1.43.3-1

[eamanu15]

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: kact...@debian.org

Dear mentors,

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

* Package name: pygithub
Version : 1.43.3-1
Upstream Author : Adam Dangoor 
  Vincent Jacques 
  Jeremy Phelps 
* URL : https://pypi.python.org/pypi/PyGithub
* License : LGPL-3+
  Section : python

It builds those binary packages:

python-github - Access to full Github API v3 from Python2
python3-github - Access the full Github API v3 from Python3

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

https://mentors.debian.net/package/pygithub

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

dget -x
https://mentors.debian.net/debian/pool/main/p/pygithub/pygithub_1.43.3-1.dsc


Changes since the last upload:

[Ondřej Nový]
* Convert git repository from git-dpm to gbp layout

[Emmanuel Arias]
* New upstream version (1.43.3)
* Update d/rules


Regards,
Emmanuel Arias

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

RFS: impacket/0.9.17-1

[eamanu15]

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: kact...@debian.org

Dear mentors,

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

* Package name: impacket
Version : 0.9.17-1
Upstream Author :  Core Security 
* URL : https://github.com/CoreSecurity/pcapy
* License : Apache Software License
Section : python

It builds those binary packages:

python-impacket - Python module to easily build and dissect network
protocols

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

https://mentors.debian.net/package/impacket


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

dget -x
https://mentors.debian.net/debian/pool/main/i/impacket/impacket_0.9.17-1.dsc

Changes since the last upload:

[Ondřej Nový]
* Convert git repository from git-dpm to gbp layout

[Emmanuel Arias]
* New upstream
* Update d/rules, add PYBUILD_NAME and DEB_BUILD_MAINT_OPTINOS
* Update d/rules, add override_dh_auto_clean to remove *.egg-info
* Remove not used patch


Regards,
Emmanuel Arias

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

ITA: python-cassandra-driver/3.16.0-1

[eamanu15]

Package: sponsorship-requests
Severity: normal
X-Debbugs-CC: kact...@debian.org

Dear mentors,

I am looking for a sponsor for my package "python-cassandra-driver"

* Package name: python-cassandra-driver
Version : 3.16.0-1
Upstream Author : DataStax
* URL : https://github.com/datastax/python-driver
* License : Apache License 2.0
Section : python

It builds those binary packages:

python-cassandra - Python driver for Apache Cassandra
python-cassandra-dbg - Python driver for Apache Cassandra (debug)
python3-cassandra - Python driver for Apache Cassandra (Python 3)
python3-cassandra-dbg - Python driver for Apache Cassandra (Python 3 debug)

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

https://mentors.debian.net/package/python-cassandra-driver


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

dget -x
https://mentors.debian.net/debian/pool/main/p/python-cassandra-driver/python-cassandra-driver_3.16.0-1.dsc

More information about python-cassandra-driver can be obtained from
https://datastax.github.io/python-driver/api/index.html.

Changes since the last upload:

[ Ondřej Nový ]
* Convert git repository from git-dpm to gbp layout

[ Emmanuel Arias ]
* New upstream release
* Add DPMT to Maintainer field on d/control
* Adopt package, add myself to Uploaders (Closes: #888400)
* Update Standards Version from 4.1.4 to 4.2.1
* Update Copyright of d/* files
* Update d/compat from 10 to 11
* Fix problems on d/copyright:
- Fix dep5-copyright-license-name-not-unique tag lintian
* Close #857298
- Delete python-cassandra-dbg and python-cassandra[3]-dbg
  from d/control
- Delete from override_dh_auto_install (on d/rules) the
  installation of *-dbg
- Change existing -dbg to -dbgsym on d/rules

Regards,
Emmanuel Arias


-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Bug#916390: RFS: tlf/1.3.2-1 [put in ITP, ITA, RC, NMU if applicable]

[eamanu15]

Hi!

Don't forget select ITP, ITA, RC or NMU. This must be written on the
subject.



> More information about tlf can be obtained from https://www.example.com.
>
> I think that here must be the tlf page.

Regards!

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Re: VCS warnings

[eamanu15]

Tommi,

I think that your problem is because the package must be on salsa repo. I
recommend create the repo on salsa, you will have to search someone who can
give you access. Then, you must update the vcs field on your d/control.

Cheers,


El mié., 12 de dic. de 2018 a la(s) 11:19, Tommi Höynälänmaa (
tommi.hoynalan...@gmail.com) escribió:

> The package is probably not on salsa. I just adopted the package so I'm
> not sure. The URL of guile-cairo is:
>
> https://www.nongnu.org/guile-cairo/download/
> It seems that the uscan links in the package are outdated.
>
>  - Tommi
>
> On 12.12.2018 16:09, eamanu15 wrote:
>
> Do you have the package on salsa? I am asking to see it try to help you
>
> El mié., 12 de dic. de 2018 a la(s) 11:03, Tommi Höynälänmaa (
> tommi.hoynalan...@gmail.com) escribió:
>
>>
>> I'm fixing the packaging of guile-cairo. I get the following warnings
>> and notes related to the VCS fields:
>> vcs-obsolete-in-debian-infrastructure, vcs-field-not-canonical, and
>> vcs-field-uses-insecure-uri. Shall I ignore these or remove the VCS
>> fields from debian/control?
>>
>>   - Tommi Höynälänmaa
>>
>>
>
> --
> Arias Emmanuel
> http://eamanu.com
> Github/Gitlab; @eamanu
> Debian: @eamanu-guest
>
>
>

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Re: VCS warnings

[eamanu15]

Do you have the package on salsa? I am asking to see it try to help you

El mié., 12 de dic. de 2018 a la(s) 11:03, Tommi Höynälänmaa (
tommi.hoynalan...@gmail.com) escribió:

>
> I'm fixing the packaging of guile-cairo. I get the following warnings
> and notes related to the VCS fields:
> vcs-obsolete-in-debian-infrastructure, vcs-field-not-canonical, and
> vcs-field-uses-insecure-uri. Shall I ignore these or remove the VCS
> fields from debian/control?
>
>   - Tommi Höynälänmaa
>
>

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Bug#915245: RFS: libopenhmd/0.2.0-5 [ITP]

[eamanu15]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: libopenhmd
 Version  : 0.2.0-5
 Upstream Author  : Jakob Bornecrantz
Jim Persson
Fredrik Hultin 
* URL : https://github.com/OpenHMD/OpenHMD
* License : Boost Software License 1.0
 Section  : libs

It builds those binary packages:

  libopenhmd-dev - API and drivers for immersive technology (development
files)
  libopenhmd0 - API and drivers for immersive technology (shared library)

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

https://mentors.debian.net/package/libopenhmd


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

  dget -x
https://mentors.debian.net/debian/pool/main/libo/libopenhmd/libopenhmd_0.2.0-5.dsc

More information about libopenhmd can be obtained from
http://www.openhmd.net/

Changes since the last upload:

  * ITA package. Closes (#912303)
  * d/control: update Maintainer field
  * d/control: update Standards-Version field. Update to 4.2.1
  * d/compat: update from 9 to 11
  * d/copyright: update the debian files copyright field


Regards,
Emmanuel Arias

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Bug#914650: RFS: python-cassandra-driver/3.16.0-1 [ITA]

[eamanu15]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "python-cassandra-driver"

* Package name: python-cassandra-driver
  Version : 3.16.0-1
  Upstream Author : DataStax 
* URL : https://github.com/datastax/python-driver
* License : Apache License 2.0
  Section : python

It builds those binary packages:

  python-cassandra - Python driver for Apache Cassandra
  python-cassandra-dbg - Python driver for Apache Cassandra (debug)
  python3-cassandra - Python driver for Apache Cassandra (Python 3)
  python3-cassandra-dbg - Python driver for Apache Cassandra (Python 3
debug)

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

  https://mentors.debian.net/package/python-cassandra-driver


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

  dget -x
https://mentors.debian.net/debian/pool/main/p/python-cassandra-driver/python-cassandra-driver_3.16.0-1.dsc

More information about python-cassandra-driver can be obtained from
https://github.com/datastax/python-driver

Changes since the last upload:

  [ Ondřej Nový ]
  * Convert git repository from git-dpm to gbp layout

  [ Emmanuel Arias ]
  * New upstream release
  * Add DPMT to Maintainer field on d/control
  * Add myself to Uploaders field on d/control
  * Closes: #888400
  * Update Standards Version from 4.1.4 to 4.2.1
  * Update Copyright of d/* files
  * Update d/compat from 10 to 11
  * FIx problems on d/copyright

Regards,
Emmanuel Arias


-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Re: help for a watch file

[eamanu15]

Hi!

The watch file have to be something like this:

  version=4
  http://xds.mpimf-heidelberg.mpg.de/html_doc/downloading.html
XDS-INTEL64_Linux_x86_64.tar.gz

The [1] will help you

Cheers!

[1] https://wiki.debian.org/debian/watch

El mié., 7 de nov. de 2018 a la(s) 12:48, PICCA Frederic-Emmanuel (
frederic-emmanuel.pi...@synchrotron-soleil.fr) escribió:

> Hello, I would like to create a watch file for this package
>
> http://xds.mpimf-heidelberg.mpg.de/
>
> as explained in page a new version is when the laast line of the page
> change.
>
> then we can download the binaries from here
>
> http://xds.mpimf-heidelberg.mpg.de/html_doc/downloading.html
>
>
> so do you think that it is possible to write  a watch file for this ?
>
> thanks for your help
>
> Frederic
>


-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

RFS: pcapy/0.11.4-1 [ITA]

[eamanu15]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: pcapy
Version : 0.11.4-1
Upstream Author : Core Security 
* URL : https://github.com/CoreSecurity/pcapy
* License : Apache Software License
Section : python

It builds those binary packages:

python-pcapy - Python interface to the libpcap packet capture library

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

https://mentors.debian.net/package/pcapy


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

dget -x
https://mentors.debian.net/debian/pool/main/p/pcapy/pcapy_0.11.4-1.dsc


Changes since the last upload:

  [ Jakub Wilk ]
  * Use canonical URIs for Vcs-* fields.

  [ Ondřej Nový ]
  * Fixed VCS URL (https)
  * d/control: Set Vcs-* to salsa.debian.org
  * d/changelog: Remove trailing whitespaces
  * Remove debian/pycompat, it's not used by any modern Python helper
  * Convert git repository from git-dpm to gbp layout

  [ Emmanuel Arias ]
  * new upstream version to 0.11.4
  * Fix d/watch. This had has some errors reported for Lintian.
  * Create and init git-dpm for the package
  * Get DEP-5 format to d/copyright and correct LICENCE
  * Add Testsuite: autopkgtest-pkg-python to debian/changelog
  * Update Standards-Version from 3.9.2 to 4.1.3
  * Update Homepage from debian/changelog
  * Add export PYBUILD_NAME=pcapy to d/rules
  * Add export DEB_BUILD_MAINT_OPTIONS = hardening=+all  to d/rules
  * Add the rm'ing LICENCE file after install on d/rules
  * Update d/compat to from 5 to 11
  * Update debhelper to >= 11 on Build-Depends field on d/control file
  * Remove the "Suggests: doc-base" from d/control
  * Add build for Python3.
  * Modify upstream Licence on d/copyright.
  * Delete Provides field on d/control.
  * Modify Description field on d/control.


Regards,
Emmanuel

-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Re: RFS: python-scp/0.11.0-1 [ITA]

[eamanu15]

Awesome, thanks!

El mar., 4 de sep. de 2018 a la(s) 07:14, Andrej Shadura (and...@shadura.me)
escribió:

> On 3 September 2018 at 16:37, eamanu15  wrote:
> > Package: sponsorship-requests
> > Severity: normal
> >
> > Dear mentors,
> >
> > I am looking for a sponsor for my package "python-scp".
>
> After a bit of fiddling with the changelog, uploaded.
>
> --
> Cheers,
>   Andrej
>


-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

RFS: python-scp/0.11.0-1 [ITA]

[eamanu15]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor for my package "python-scp".

For some reason the uploaders field on mentors.d.o is Fabian Wolff, so I CC.

* Package name: python-scp
Version : 0.11.0-1
Upstream Author : James Bardin 
* URL : https://github.com/jbardin/scp.py
* License : LGPL-2.1+
Section : python

It builds those binary packages:

python-scp - scp module for  (Python 2)
python3-scp - scp module for paramiko (Python 3)

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

  https://mentors.debian.net/package/python-scp


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

  dget -x
https://mentors.debian.net/debian/pool/main/p/python-scp/python-scp_0.11.0-1.dsc


Changes since the last upload:

[Ondřej Nový]
  * d/changelog: Remove trailing whitespaces
  * Fixed VCS URL (https)
  * d/control: Set Vcs-* to salsa.debian.org
  * d/copyright: Use https protocol in Format field
  * d/watch: Use https protocol
  * Convert git repository from git-dpm to gbp layout

  [Emmanuel Arias]
  * Add me to Uploaders field on d/control
  * Add to DPTM to Maintainer field on d/control
  * Adopt the package (Closes: #888215)
  * Update d/watch file
  * Update d/compat from 9 to 11
  * Update debhelper to >= 11 from d/control
  * Update Standards-Version from 3.9.6 to 4.1.4 on d/control
  * Add Testsuite autopkgtest-pkg-python on d/control
  * Add me to d/copyright

Regards,
Emmanuel Arias

Re: RFS: pcapy/0.11.3-1 [ITA]

[eamanu15]

Hello Sergio,

I made the changes!

Thanks for your help
regards!
Emmanuel

El mié., 22 de ago. de 2018 a la(s) 01:59, Sergio Durigan Junior (
sergi...@debian.org) escribió:

> Hi Emmanuel,
>
> Sorry, you still have to fix a few things before the package is ready
> for upload.  We're almost there; don't give up!
>
> On Tuesday, August 21 2018, eamanu wrote:
>
> > No problem.  However, the "License:" still doesn't reflect the license
> >> of the software.  According to LICENSE:
> >>
> >>   We provide this software under a slightly modified version of the
> >>   Apache Software License. The only changes to the document were the
> >>   replacement of "Apache" with "Pcapy" and "Apache Software Foundation"
> >>   with "CORE Security Technologies". Feel free to compare the resulting
> >>   document to the official Apache license.
> >>
> >>   The `Apache Software License' is an Open Source Initiative Approved
> >>   License.
> >>
> >> Therefore, I think a better value for the field would be:
> >>
> >>   License: Apache with Pcapy modifications
> >>
> >
> > Ready!
>
> Thanks.  The "License:" must be the same in both places, though.  Here:
>
>   Files: *
>   Copyright (C) 2014 CORE Security Technologies .
>   License: Apache Software License with Pcapy modifications
>
> and here:
>
>   License: Apache with Pcapy modifications
>We provide this software under a slightly modified version of the
>...
>
> It's OK to use "Apache with Pcapy modifications" in both places.
>
> >> I see that the contributions under the debian/ directory are released
> >> under GPL-3+.  That's absolutely fine (I am a GPL advocate as well).
> >> However, I must warn you that the Debian patches will also be released
> >> under this license, which may be problematic if/when you decide to
> >> upstream them.  But I understand this is the current situation anyway.
> >> You may want to try to contact Arnaud Fontaine and ask him if he's OK
> >> with changing the license to Apache in the future.
> >>
> >
> > Ok. I will contact Arnaud Fontaine to ask about it. I think it's ok for
> > now. In the next release of package I can update this field.
>
> Great.  It's OK for now, indeed.
>
> > Thanks, but what you did is incomplete.  In order to create a new
> >> package, you have to create an entry for it on d/control.  What you did
> >> (add ${python3:Depends} to python-pcapy's Depends) is wrong because
> >> you're basically pulling Python 3 dependencies for a Python 2 package.
> >> Please have a look at other packages under them DPMT and check their
> >> d/control; you will find many examples of how to create Python 3
> >> packages.
> >>
> >
> > Ready!
>
> Thanks, that's better, but there are still a few things that need
> fixing.
>
> 1) It's a good practice to explicitly say if the package is a Python 2
> or Python 3 module.  We do that by suffixing the short description with
> "(Python X)" (where X is 2 or 2), and by appending "This package
> installs the library for Python X." to the long description.  Like this:
>
>   Package: python-pcapy
>   Architecture: any
>   Depends: ${python:Depends}, ${shlibs:Depends}, ${misc:Depends}
>   Recommends: python-impacket
>   Description: Python interface to the libpcap packet capture library
> (Python 2)
>Pcapy is a  Python extension module that interfaces  with the libpcap
>packet capture library.
>.
>Pcapy enables Python scripts to capture packets on the network. Pcapy
>is highly  effective when used in conjunction  with a packet-handling
>package such as Impacket, which is a collection of Python classes for
>constructing and dissecting network packets.
>.
>This package installs the library for Python 2.
>
> 2) You don't need to specify "Provides:".  Please remove them from both
> packages.
>
>
> As a last note, it seems that you forgot to push the "upstream" and
> "pristine-tar" branches, so I can't really build the package locally
> here.  Please do that.
>
> Thanks,
>
> --
> Sergio
> GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
> Please send encrypted e-mail if possible
> http://sergiodj.net/
>


-- 
Arias Emmanuel
http://eamanu.com
Github/Gitlab; @eamanu
Debian: @eamanu-guest

Re: RFS: pcapy/0.11.3-1 [ITA]

[eamanu15]

Hello Sergio,



No problem.  However, the "License:" still doesn't reflect the license
> of the software.  According to LICENSE:
>
>   We provide this software under a slightly modified version of the
>   Apache Software License. The only changes to the document were the
>   replacement of "Apache" with "Pcapy" and "Apache Software Foundation"
>   with "CORE Security Technologies". Feel free to compare the resulting
>   document to the official Apache license.
>
>   The `Apache Software License' is an Open Source Initiative Approved
>   License.
>
> Therefore, I think a better value for the field would be:
>
>   License: Apache with Pcapy modifications
>

Ready!


> Also, please remove the "All rights reserved." text here:
>
>   Copyright (C) 2003-2011 CORE Security Technologies .
>
>All rights reserved.
>

Ready!


> Oh, and please fix the years.  Nowhere in the code I see "2003-2011".
> Doing a basic grep, I see that the year should be 2014.
>

Ready

>
> I see that the contributions under the debian/ directory are released
> under GPL-3+.  That's absolutely fine (I am a GPL advocate as well).
> However, I must warn you that the Debian patches will also be released
> under this license, which may be problematic if/when you decide to
> upstream them.  But I understand this is the current situation anyway.
> You may want to try to contact Arnaud Fontaine and ask him if he's OK
> with changing the license to Apache in the future.
>

Ok. I will contact Arnaud Fontaine to ask about it. I think it's ok for
now. In the next release of package I can update this field.

Thanks, but what you did is incomplete.  In order to create a new
> package, you have to create an entry for it on d/control.  What you did
> (add ${python3:Depends} to python-pcapy's Depends) is wrong because
> you're basically pulling Python 3 dependencies for a Python 2 package.
> Please have a look at other packages under them DPMT and check their
> d/control; you will find many examples of how to create Python 3
> packages.
>

Ready!

Thanks for your help!
Regards!

-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Wrong Uploaders field when upload packages

[eamanu15]

Dear Mentors,

Yesterday, I uploaded a package that I ITA. [1] [2]

Something strange happened. The uploaders field on mentors.d.net say a
different name than I put on d/control.

Exist a real problem? or that has a reason?

PS: I have some problem with Lintian. I am working in it

[1]
https://mentors.debian.net/debian/pool/main/p/python-scp/python-scp_0.11.0-1.dsc
[2] https://mentors.debian.net/package/python-scp

Thanks!
Regards!!!
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Re: RFS: pcapy/0.11.3-1 [ITA]

[eamanu15]

Hello Sergio!

Thanks for your comments!

I fix the problems that you say me. Please check it

1) On d/copyright, the license specified for the project is wrong.
> According to the LICENSE file, the project is released under a slightly
> modified version of the Apache license.  This is something really
> important to get right, otherwise the ftp-masters will certainly reject
> the package.  You listed the license as being "GPL-2", but the text is
> clearly not GPL-2.
>
> Ohh!!! Sorry I saw the old d/copyright file to do this.

2) Still on d/copyright: as said above, the GPL-2 license is wrong.
> However, I think it's also important to mention that the license text is
> formatted in a strange/wrong manner.  You have text like this:
>
>  [...]
>  Redistribution and use in source  and binary forms, with or without
>modification, are permitted  provided that the following conditions
>are met:
>
>1. Redistributions  of  source   code  must  retain  the  above
>  [...]
>
> The correct format for d/copyright is to indent the text using 1 space,
> and to use . (dot) for blank lines.  Like this:
>
>  [...]
>  Redistribution and use in source  and binary forms, with or without
>  modification, are permitted  provided that the following conditions
>  are met:
>  .
>  1. Redistributions  of  source   code  must  retain  the  above
>  [...]
>


Ready!

>
> 3) The package uses a *really* old version of debhelper (version 5!).
> We're at version 11 already, so you should update both d/compat and
> d/control (i.e., depend on debhelp >= 11) to reflect that.
>

Ready!

>
> 4) You haven't addressed my comment about building a Python 3 package.
> IMO you should really do that; lintian will warn you if you don't.
>

Yes, I forgot do that! Sorry!

>
> 5) You haven't answered my question about why the package has "Suggests:
> doc-base".  It seems to be a relic from this very old debhelper; I think
> you can safely remove it.
>

Yes, I remove it. Since I do not have much knowledge about doc-base and why
it is there, I left it. But now is removed.

Thanks for your help!
Regards!

-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Re: RFS: pcapy/0.11.3-1 [ITA]

[eamanu15]

Hello Sergio,

I am really sorry for the delay.

I finish the update of pcapy package. I push the commit, but is on
UNRELEASED status.

Please, check if whole the things are ok, and then I will make change to
unstable status on d/changelog

Thanks!
Regards!

El lun., 2 de jul. de 2018 a la(s) 21:36, eamanu15 <
emmanuelaria...@gmail.com> escribió:

> Hello Sergio,
>
> Sorry for the delay in my response.
>
> In this week I will work on your reviews. When I fix the problems I will
> push to salsa and will let it know you.
>
> Thanks!
> Regards!
> Emmanuel
>
> El sáb., 16 de jun. de 2018 a la(s) 16:38, Sergio Durigan Junior <
> sergi...@debian.org> escribió:
>
>> Control: owner -1 !
>> Control: tags -1 + moreinfo
>>
>> On Thursday, June 07 2018, eamanu wrote:
>>
>> > Dear mentors,
>> >
>> > I am looking for a sponsor for my package "pcapy"
>> >
>> > * Package name: pcapy
>> > Version : 0.11.3-1
>> > Upstream Author : Core Security 
>> > * URL : https://github.com/CoreSecurity/pcapy
>> > * License : Apache Software License
>> > Section : python
>> >
>> > It builds those binary packages:
>> >
>> > python-pcapy - Python interface to the libpcap packet capture library
>> >
>> > To access further information about this package, please visit the
>> > following URL:
>> >
>> > https://mentors.debian.net/package/pcapy
>> >
>> >
>> > Alternatively, one can download the package with dget using this
>> command:
>> >
>> > dget -x
>> > https://mentors.debian.net/debian/pool/main/p/pcapy/pcapy_0.11.3-1.dsc
>> >
>> > More information about hello can be obtained from
>> https://www.example.com.
>> >
>> > Changes since the last upload:
>> >
>> > [ Jakub Wilk ]
>> > * Use canonical URIs for Vcs-* fields.
>> >
>> > [ Ondřej Nový ]
>> > * Fixed VCS URL (https)
>> > * d/control: Set Vcs-* to salsa.debian.org
>> > * d/changelog: Remove trailing whitespaces
>> > * Remove debian/pycompat, it's not used by any modern Python helper
>> >
>> > [ Emmanuel Arias ]
>> > * new upstream version
>> > * update d/watch to download correctly the last upstream version
>> > * update d/control to add Maintainer the DPMT
>> > * update d/control to add me to Uploaders field (Closes: #895787)
>> > * update debhelper on d/contorl from 5.0.37.2 to 11
>> > * update Standards-Version from 3.9.2 to 4.1.4 on d/control
>> > * add Testsuite: autopkgtest-pkg-python on d/control
>> > * update d/compat from 5 to 11
>> > * add to copyright file the debian files copyright
>>
>> Hi Emmanuel,
>>
>> Thanks for the package, and for your interest in adopting it!  The first
>> question I have is about the VCS.  I tried finding your commits on the
>> official Salsa repo, but wasn't able to.  Are you using any other
>> repository for that?  It's much easier to review the changes when
>> there's a repository, and I strongly suggest you use the official one
>> for the packaging.
>>
>> As for the review, here's what I'd like you to address:
>>
>> 1) d/copyright should follow DEP-5.  Take a look at:
>>
>>   https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
>>
>> and you'll be able to find instructions on the format of the file.  It
>> shouldn't be too hard for you to convert the existing file.
>>
>> 2) The package doesn't need CDBS anymore, so you can safely remove it
>> from the Build-Depends line.
>>
>> 3) The "Homepage" field can have a better URL:
>>
>>   https://www.coresecurity.com/corelabs-research/open-source-tools/pcapy
>>
>> 4) You should consider packaging a Python 3 package, as well as the
>> Python 2 you're already packaging (in which case you could probably
>> split the documentation part into its own package).  If Python 3 is not
>> supported, you should contact upstream and probably file a bug against
>> it.
>>
>> 5) Any reason why the package has "Suggests: doc-base"?
>>
>> 6) It's a good habit to export the PYBUILD_NAME variable (on d/rules):
>>
>>   export PYBUILD_NAME=pcapy
>>
>> This variable tells pybuild what's the name of your project.
>>
>> 7) It's a good idea to use (on d/rules):
>>
>>   export DEB_BUILD_MAINT_OPTIONS = hardening=+all
>>
>> since your package is building a shlib.
>>
>> 8) The package is installing the LICENSE file by default, but this is
>> not needed since we have the d/copyright file.  Therefore, it'd be good
>> if you could remove this file from the package.  You can do that by
>> e.g. overriding dh_auto_install and rm'ing the file there.
>>
>>
>> I think that's basically everything I've spotted.  Please let me know if
>> you need any help.
>>
>> Cheers,
>>
>> --
>> Sergio
>> GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
>> Please send encrypted e-mail if possible
>> http://sergiodj.net/
>>
> --
> Arias Emmanuel
> https://www.linkedin.com/in/emmanuel-arias-437a6a8a
> http://eamanu.com
>
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Fwd: ITA: enigma -- A game where you control a marble with

[eamanu15]

Hello Ben,

Ok, I just sent a mail to debian games team.

Thanks!
Regards

-- Forwarded message -
From: Ben Finney 
Date: mié., 11 de jul. de 2018 a la(s) 23:16
Subject: Re: ITA: enigma -- A game where you control a marble with
To: 


eamanu15  writes:

> I am working in the enigma package update (I am trying to adopt it). I
> see that this package don't have a VCS.

Hopefully the pervious maintainer can get the existing VCS repository to
you, so that you can continue working on the same packaging history.

> Do you think that is a good idea add enigma to salsa?

You should, and the best way would be to join the Debian Games team.
They have a GitLab team https://salsa.debian.org/games-team> that
would be the right team for this package.

-- 
 \ “If I had known what it would be like to have it all... I might |
  `\ have been willing to settle for less.” —Jane Wagner, via Lily |
_o__)   Tomlin |
Ben Finney

-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

ITA: enigma -- A game where you control a marble with

[eamanu15]

Hello dear Mentors and Erich,

I am working in the enigma package update (I am trying to adopt it). I see
that this package don't have a VCS.

Do you think that is a good idea add enigma to salsa?
If it is true, could anyone create a salsa repo to commit it and give me
access?

Thanks!
Regards!
Emmanuel
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Bug#900368: RFS: pygithub/1.40a3-1 [ITP]

[eamanu15]

Hello Dmitry,

I just pushed the update the package to Salsa. I pushed the PyGithub_1.40
version.

Regards!
Emmanuel

El mié., 4 de jul. de 2018 a la(s) 10:41, eamanu15 <
emmanuelaria...@gmail.com> escribió:

> Ok! Thanks !!!
>
> El mié., 4 de jul. de 2018 a la(s) 09:13, Dmitry Shachnev <
> mity...@debian.org> escribió:
>
>> On Wed, Jul 04, 2018 at 07:09:20AM -0300, eamanu15 wrote:
>> > Hello Dmitry,
>> >
>> > I have the fixes almost already, Just, I have a doubt in this point:
>> >
>> > > - When building in the current sid, I get Lintian warnings about
>> three files
>> > >   shipped in /usr/lib/python3.7/dist-packages/.
>> >
>> > To fix this problem I could add in the d/rules the next line:
>> >
>> > override_dh_auto_install:
>> > dh_auto_install
>> > find ./debian/python3-github/usr/lib/ -type f -name python3.*
>> -delete
>> >
>> > isn't?
>>
>> It is a directory, not a file. Also you need to do it after dh_python3
>> runs.
>> So better use this:
>>
>> override_dh_python3:
>> dh_python3
>> rm -rfv debian/python3-github/usr/lib/python3.*
>>
>> --
>> Dmitry Shachnev
>>
> --
> Arias Emmanuel
> https://www.linkedin.com/in/emmanuel-arias-437a6a8a
> http://eamanu.com
>
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Bug#900368: RFS: pygithub/1.40a3-1 [ITP]

[eamanu15]

Ok! Thanks !!!

El mié., 4 de jul. de 2018 a la(s) 09:13, Dmitry Shachnev <
mity...@debian.org> escribió:

> On Wed, Jul 04, 2018 at 07:09:20AM -0300, eamanu15 wrote:
> > Hello Dmitry,
> >
> > I have the fixes almost already, Just, I have a doubt in this point:
> >
> > > - When building in the current sid, I get Lintian warnings about three
> files
> > >   shipped in /usr/lib/python3.7/dist-packages/.
> >
> > To fix this problem I could add in the d/rules the next line:
> >
> > override_dh_auto_install:
> > dh_auto_install
> > find ./debian/python3-github/usr/lib/ -type f -name python3.* -delete
> >
> > isn't?
>
> It is a directory, not a file. Also you need to do it after dh_python3
> runs.
> So better use this:
>
> override_dh_python3:
> dh_python3
> rm -rfv debian/python3-github/usr/lib/python3.*
>
> --
> Dmitry Shachnev
>
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Bug#900368: RFS: pygithub/1.40a3-1 [ITP]

[eamanu15]

Hello Dmitry,

I have the fixes almost already, Just, I have a doubt in this point:

- When building in the current sid, I get Lintian warnings about three files
>   shipped in /usr/lib/python3.7/dist-packages/.
>
>   That probably happens because of output of 2to3 is slightly different in
>   Python 3.6 and 3.7 (e.g. files.items() vs. iter(files.items())), and
>   dh_python3 does not remove the file if it does not match.
>
>   I would recommend removing debian/python3-github/usr/lib/python3.*
> manually
>   in debian/rules. Keeping debian-python@ in Cc in case someone has a
> better
>   idea.
>

To fix this problem I could add in the d/rules the next line:

override_dh_auto_install:
dh_auto_install
find ./debian/python3-github/usr/lib/ -type f -name python3.* -delete

isn't?

Regards!
Thanks!
Emmanuel
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Bug#900368: RFS: pygithub/1.40a3-1 [ITP]

[eamanu15]

Hello Dimitry,

Thanks for you email. I Will make the changes that you recommend.

I have a cuestion for you. When I update to the version 1.40, Do I merge
all the changelog entries, including 1.35-1 upload, isn't?

Thanks
Regards

Arias Emmanuel
eamanu.com


El mar., 3 de jul. de 2018 17:17, Dmitry Shachnev 
escribió:

> Control: merge 898416 898811 900368
>
> Hi Emmanuel!
>
> On Tue, May 29, 2018 at 12:35:25PM -0300, eamanu15 wrote:
> > Package: sponsorship-requests
> > Severity: normal
> >
> > Dear mentors,
> >
> > I am looking for a sponsor for my package "pygithub"
>
> Note that I am merging your three RFS bugs. If you want to ping, just reply
> to the existing bug, not file a new one.
>
> Here are my comments about your changes.
>
> - It would be nice if you based the repository on the existing Git
>   repository [1], rather than starting from scratch.
>
>   Also for new team repositories as this one, it is better to use Gbp-Pq
>   workflow as described in the team wiki [2].
>
> - Please merge the last three changelog entries, as 1.35-1 upload did not
>   happen.
>
> - When building in the current sid, I get Lintian warnings about three
> files
>   shipped in /usr/lib/python3.7/dist-packages/.
>
>   That probably happens because of output of 2to3 is slightly different in
>   Python 3.6 and 3.7 (e.g. files.items() vs. iter(files.items())), and
>   dh_python3 does not remove the file if it does not match.
>
>   I would recommend removing debian/python3-github/usr/lib/python3.*
> manually
>   in debian/rules. Keeping debian-python@ in Cc in case someone has a
> better
>   idea.
>
> - A new stable 1.40 release has been released on June 26th [3].
>   Can you update from alpha to the stable version?
>
>   Also please add uversionmangle to debian/watch (like here [4]), to make
> it
>   treat 1.40 as a higher version than 1.40aN.
>
> [1]:
> https://alioth-archive.debian.org/git/users/kaction-guest/pygithub.git.tar.xz
> [2]: https://wiki.debian.org/Python/GitPackagingPQ
> [3]: https://pypi.org/project/PyGithub/1.40/
> [4]: https://pypi.debian.net/PyGithub/watch
>
> --
> Dmitry Shachnev
>

Re: RFS: pcapy/0.11.3-1 [ITA]

[eamanu15]

Hello Sergio,

Sorry for the delay in my response.

In this week I will work on your reviews. When I fix the problems I will
push to salsa and will let it know you.

Thanks!
Regards!
Emmanuel

El sáb., 16 de jun. de 2018 a la(s) 16:38, Sergio Durigan Junior <
sergi...@debian.org> escribió:

> Control: owner -1 !
> Control: tags -1 + moreinfo
>
> On Thursday, June 07 2018, eamanu wrote:
>
> > Dear mentors,
> >
> > I am looking for a sponsor for my package "pcapy"
> >
> > * Package name: pcapy
> > Version : 0.11.3-1
> > Upstream Author : Core Security 
> > * URL : https://github.com/CoreSecurity/pcapy
> > * License : Apache Software License
> > Section : python
> >
> > It builds those binary packages:
> >
> > python-pcapy - Python interface to the libpcap packet capture library
> >
> > To access further information about this package, please visit the
> > following URL:
> >
> > https://mentors.debian.net/package/pcapy
> >
> >
> > Alternatively, one can download the package with dget using this command:
> >
> > dget -x
> > https://mentors.debian.net/debian/pool/main/p/pcapy/pcapy_0.11.3-1.dsc
> >
> > More information about hello can be obtained from
> https://www.example.com.
> >
> > Changes since the last upload:
> >
> > [ Jakub Wilk ]
> > * Use canonical URIs for Vcs-* fields.
> >
> > [ Ondřej Nový ]
> > * Fixed VCS URL (https)
> > * d/control: Set Vcs-* to salsa.debian.org
> > * d/changelog: Remove trailing whitespaces
> > * Remove debian/pycompat, it's not used by any modern Python helper
> >
> > [ Emmanuel Arias ]
> > * new upstream version
> > * update d/watch to download correctly the last upstream version
> > * update d/control to add Maintainer the DPMT
> > * update d/control to add me to Uploaders field (Closes: #895787)
> > * update debhelper on d/contorl from 5.0.37.2 to 11
> > * update Standards-Version from 3.9.2 to 4.1.4 on d/control
> > * add Testsuite: autopkgtest-pkg-python on d/control
> > * update d/compat from 5 to 11
> > * add to copyright file the debian files copyright
>
> Hi Emmanuel,
>
> Thanks for the package, and for your interest in adopting it!  The first
> question I have is about the VCS.  I tried finding your commits on the
> official Salsa repo, but wasn't able to.  Are you using any other
> repository for that?  It's much easier to review the changes when
> there's a repository, and I strongly suggest you use the official one
> for the packaging.
>
> As for the review, here's what I'd like you to address:
>
> 1) d/copyright should follow DEP-5.  Take a look at:
>
>   https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/
>
> and you'll be able to find instructions on the format of the file.  It
> shouldn't be too hard for you to convert the existing file.
>
> 2) The package doesn't need CDBS anymore, so you can safely remove it
> from the Build-Depends line.
>
> 3) The "Homepage" field can have a better URL:
>
>   https://www.coresecurity.com/corelabs-research/open-source-tools/pcapy
>
> 4) You should consider packaging a Python 3 package, as well as the
> Python 2 you're already packaging (in which case you could probably
> split the documentation part into its own package).  If Python 3 is not
> supported, you should contact upstream and probably file a bug against
> it.
>
> 5) Any reason why the package has "Suggests: doc-base"?
>
> 6) It's a good habit to export the PYBUILD_NAME variable (on d/rules):
>
>   export PYBUILD_NAME=pcapy
>
> This variable tells pybuild what's the name of your project.
>
> 7) It's a good idea to use (on d/rules):
>
>   export DEB_BUILD_MAINT_OPTIONS = hardening=+all
>
> since your package is building a shlib.
>
> 8) The package is installing the LICENSE file by default, but this is
> not needed since we have the d/copyright file.  Therefore, it'd be good
> if you could remove this file from the package.  You can do that by
> e.g. overriding dh_auto_install and rm'ing the file there.
>
>
> I think that's basically everything I've spotted.  Please let me know if
> you need any help.
>
> Cheers,
>
> --
> Sergio
> GPG key ID: 237A 54B1 0287 28BF 00EF  31F4 D0EB 7628 65FC 5E36
> Please send encrypted e-mail if possible
> http://sergiodj.net/
>
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

RFS: pcapy/0.11.3-1 [ITA]

[eamanu15]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: pcapy
Version : 0.11.3-1
Upstream Author : Core Security 
* URL : https://github.com/CoreSecurity/pcapy
* License : Apache Software License
Section : python

It builds those binary packages:

python-pcapy - Python interface to the libpcap packet capture library

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

https://mentors.debian.net/package/pcapy


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

dget -x
https://mentors.debian.net/debian/pool/main/p/pcapy/pcapy_0.11.3-1.dsc

More information about hello can be obtained from https://www.example.com.

Changes since the last upload:

[ Jakub Wilk ]
* Use canonical URIs for Vcs-* fields.

[ Ondřej Nový ]
* Fixed VCS URL (https)
* d/control: Set Vcs-* to salsa.debian.org
* d/changelog: Remove trailing whitespaces
* Remove debian/pycompat, it's not used by any modern Python helper

[ Emmanuel Arias ]
* new upstream version
* update d/watch to download correctly the last upstream version
* update d/control to add Maintainer the DPMT
* update d/control to add me to Uploaders field (Closes: #895787)
* update debhelper on d/contorl from 5.0.37.2 to 11
* update Standards-Version from 3.9.2 to 4.1.4 on d/control
* add Testsuite: autopkgtest-pkg-python on d/control
* update d/compat from 5 to 11
* add to copyright file the debian files copyright

Regards,
Emmanuel
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

RFS: pcapy/0.11.3-1 [ITA]

[eamanu15]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: pcapy
Version : 0.11.3-1
Upstream Author : Core Security 
* URL : https://github.com/CoreSecurity/pcapy
* License : Apache Software License
Section : python

It builds those binary packages:

python-pcapy - Python interface to the libpcap packet capture library

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

https://mentors.debian.net/package/pcapy


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

dget -x
https://mentors.debian.net/debian/pool/main/p/pcapy/pcapy_0.11.3-1.dsc

More information about hello can be obtained from https://www.example.com.

Changes since the last upload:

[ Jakub Wilk ]
* Use canonical URIs for Vcs-* fields.

[ Ondřej Nový ]
* Fixed VCS URL (https)
* d/control: Set Vcs-* to salsa.debian.org
* d/changelog: Remove trailing whitespaces
* Remove debian/pycompat, it's not used by any modern Python helper

[ Emmanuel Arias ]
* new upstream version
* update d/watch to download correctly the last upstream version
* update d/control to add Maintainer the DPMT
* update d/control to add me to Uploaders field (Closes: #895787)
* update debhelper on d/contorl from 5.0.37.2 to 11
* update Standards-Version from 3.9.2 to 4.1.4 on d/control
* add Testsuite: autopkgtest-pkg-python on d/control
* update d/compat from 5 to 11
* add to copyright file the debian files copyright

Regards,
Emmanuel
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Bug#900368: RFS: pygithub/1.40a3-1 [ITP]

[eamanu15]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: pygithub
   Version : 1.40a3-1
   Upstream Author : Author : Adam Dangoor 
   Vincent Jacques <
vinc...@vincent-jacques.net>
Jeremy Phelps <
jphe...@linuxfoundation.org>
* URL : https://pypi.python.org/pypi/PyGithub
* License : LGPL-3+
  Section : python

 It builds those binary packages:

python-github - Access to full Github API v3 from Python2
python3-github - Access the full Github API v3 from Python3

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

https://mentors.debian.net/package/pygithub
or https://salsa.debian.org/python-team/modules/pygithub

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

dget -x
https://mentors.debian.net/debian/pool/main/p/pygithub/pygithub_1.40a3-1.dsc
or
git clone g...@salsa.debian.org:python-team/modules/pygithub.git

More information about pygithub can be obtained from
http://pygithub.readthedocs.io/

Changes since the last upload:
  * New upstream release
  * Update Standards-Version from 4.1.3 to 4.1.4 version
  * Add Uploaders field from debian/control to intent to adopt the
 package (Closes: #851187)


Regards,
Emmanuel Arias
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Re: RFS: impacket/0.9.15-5 [ITA]

[eamanu15]

Thanks for yours comments! I will take it in the future.

Best regards!

El vie., 25 de may. de 2018 a la(s) 12:00, Adam Borowski <
kilob...@angband.pl> escribió:

> On Fri, May 25, 2018 at 10:10:41AM -0400, The Wanderer wrote:
> > On 2018-05-25 at 09:47, Adam Borowski wrote:
> >
> > > On Thu, May 24, 2018 at 09:48:23PM -0300, eamanu15 wrote:
> > >> Package: sponsorship-requests
> > >> Severity: normal
> > >
> > > This should be mailed to submit@bugs.d.o, not the mailing list. It
> > > did not get a tracking bug this way, thus those who use the BTS as
> > > their primary view wouldn't notice it.
> >
> > Actually, the original mail as I received it *did* have s@b.d.o in the
> > To: list; it just also had the mailing list's address present explicitly.
> >
> > How the software which normally results in a RFS bug getting passed on
> > to this mailing list handles that situation I'm not sure.
>
> Indeed:
> } To: "sub...@bugs.debian.org" <sub...@bugs.debian.org>,
> }"895...@bugs.debian.org" <895...@bugs.debian.org>, Arnaud
> Fontaine
> }<ar...@debian.org>, "python-modules-t...@lists.alioth.debian.org"
> }<python-modules-t...@lists.alioth.debian.org>, Debian Mentors
> List
> }<debian-mentors@lists.debian.org>
>
> And a bug _was_ created (#900041), just somehow not forwarded to this list.
> Probably because the list was already in the "To:" field.
>
> Closing it then, thanks for noticing.
>
>
> Meow!
> --
> ⢀⣴⠾⠻⢶⣦⠀ .globl _start↵.data↵rc: .ascii "/etc/init.d/rcS\0"↵.text↵_start
> ⣾⠁⢰⠒⠀⣿⡁ mov $57,%rax↵syscall↵cmp $0,%rax↵jne child↵parent:↵mov $61,%rax
> ⢿⡄⠘⠷⠚⠋⠀ mov $-1,%rdi↵xor %rsi,%rsi↵xor %rdx,%rdx↵syscall↵jmp parent↵child:
> ⠈⠳⣄ mov $59,%rax↵mov $rc,%rdi↵xor %rsi,%rsi↵xor %rdx,%rdx↵syscall
>
> --
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

RFS: impacket/0.9.15-5 [ITA]

[eamanu15]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: impacket
Version : 0.9.15-5
Upstream Author : Alberto Solino 
* URL : https://pypi.org/project/impacket/
* License : Apache Software License Modified
Section : python

It builds those binary packages:

python-impacket - Python module to easily build and dissect network
protocols

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

https://mentors.debian.net/package/impacket

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

dget -x
https://mentors.debian.net/debian/pool/main/i/impacket/impacket_0.9.15-5.dsc

or alternatively,

git clone https://salsa.debian.org/python-team/modules/impacket.git

More information about impacket can be obtained from
https://github.com/CoreSecurity/impacket

Changes since the last upload:

  [ Ondřej Nový ]
  * d/control: Set Vcs-* to salsa.debian.org
  * d/copyright: Use https protocol in Format field
  * d/watch: Use https protocol
  * d/changelog: Remove trailing whitespaces

  [ Emmanuel Arias ]
  * d/control: Change Maintainer field for Debian Python Module Team
  * d/control: Change Uploaders field for me (Closes: #895785)
  * d/control: Update debhelper from 9 to 11
  * d/control: Update Standards-Version  to 4.1.4
  * d/control: Add autopkgtest-pkg-python to Testsuite
  * d/compat: Update from 9 to 11
  * d/copyright: Add me on copyright of debian field.


Regards,
Emmanuel Arias
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

RFS: pygithub/1.40a3-1 [ITP]

[eamanu15]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: pygithub
   Version : 1.40a3-1
   Upstream Author : Author : Adam Dangoor 
   Vincent Jacques <
vinc...@vincent-jacques.net>
Jeremy Phelps <
jphe...@linuxfoundation.org>
* URL : https://pypi.python.org/pypi/PyGithub
* License : LGPL-3+
  Section : python

 It builds those binary packages:

python-github - Access to full Github API v3 from Python2
python3-github - Access the full Github API v3 from Python3

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

https://mentors.debian.net/package/pygithub
or https://salsa.debian.org/python-team/modules/pygithub

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

dget -x
https://mentors.debian.net/debian/pool/main/p/pygithub/pygithub_1.40a3-1.dsc
or
git clone g...@salsa.debian.org:python-team/modules/pygithub.git

More information about pygithub can be obtained from
http://pygithub.readthedocs.io/

Changes since the last upload:
  * New upstream release
  * Update Standards-Version from 4.1.3 to 4.1.4 version
  * Add Uploaders field from debian/control to intent to adopt the
 package (Closes: #851187)


Regards,
Emmanuel Arias
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Fwd: RFS: pygithub/1.40a3-1 [ITP]

[eamanu15]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: pygithub
   Version : 1.40a3-1
   Upstream Author : Author : Adam Dangoor 
   Vincent Jacques <
vinc...@vincent-jacques.net>
Jeremy Phelps <
jphe...@linuxfoundation.org>
* URL : https://pypi.python.org/pypi/PyGithub
* License : LGPL-3+
  Section : python

 It builds those binary packages:

python-github - Access to full Github API v3 from Python2
python3-github - Access the full Github API v3 from Python3

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

https://mentors.debian.net/package/pygithub
or https://salsa.debian.org/python-team/modules/pygithub

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

dget -x
https://mentors.debian.net/debian/pool/main/p/pygithub/pygithub_1.40a3-1.dsc
or
git clone g...@salsa.debian.org:python-team/modules/pygithub.git

More information about pygithub can be obtained from
http://pygithub.readthedocs.io/

Changes since the last upload:
  * New upstream release
  * Update Standards-Version from 4.1.3 to 4.1.4 version

Regards,
Emmanuel Arias
--
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

RFS: pygithub/1.40a3-1 [ITP]

[eamanu15]

  Package: sponsorship-requests
  Severity: normal

  Dear mentors,

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

 * Package name: pygithub
   Version : 1.40a3-1
   Upstream Author : Author : Adam Dangoor 
   Vincent Jacques <
vinc...@vincent-jacques.net>
Jeremy Phelps <
jphe...@linuxfoundation.org>
 * URL : https://pypi.python.org/pypi/PyGithub
 * License : LGPL-3+
   Section : python

  It builds those binary packages:

python-github - Access to full Github API v3 from Python2
 python3-github - Access the full Github API v3 from Python3

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

  https://mentors.debian.net/package/pygithub
  or https://salsa.debian.org/python-team/modules/pygithub

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

dget -x
https://mentors.debian.net/debian/pool/main/p/pygithub/pygithub_1.40a3-1.dsc
or
git clone g...@salsa.debian.org:python-team/modules/pygithub.git

  More information about pygithub can be obtained from
http://pygithub.readthedocs.io/

  Changes since the last upload:

* New upstream release
* Update Standards-Version from 4.1.3 to 4.1.4 version

  Regards,
   Emmanuel Arias
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

RFS: pygithub/1.35-1[ITA]

[eamanu15 .]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: pygithub
  Version : 1.35-1
  Upstream Author : Adam Dangoor 
Vincent Jacques 
Jeremy Phelps 
* URL : https://pypi.python.org/pypi/PyGithub
* License : LGPL-3+
  Section : python

It builds those binary packages:
python-github - Access to full Github API v3 from Python2
python3-github - Access the full Github API v3 from Python3

To access further information about this package, please visit the
following URL:
https://mentors.debian.net/package/pygithub

Alternatively, one can download the package with dget using this command:
dget -x
https://mentors.debian.net/debian/pool/main/p/pygithub/pygithub_1.35-1.dsc

Changes since the last upload:
   * New upstream release
   * Update Maintainer field from debian/control to intent to adopt
the package (Closes: #851187)
   * Update Standards-Version from  3.9.6 to 4.1.3 from debian control
according to the up-to-date standards
   * Add new maintainer on copyright debian/* files field from
debian/copyright to stay up-to-date
   * Remove override_dh_installchangelogs target from debian/rules due to
the new version (1.35) do not have README.rst file

Regards,
Emmanuel


-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Re: E: dsc: amd64 not in arch list

[eamanu15 .]

El lun., 15 de ene. de 2018 a la(s) 14:38, Paul R. Tagliamonte <
paul...@gmail.com> escribió:

> Cool. Like I said, I'd try `sbuild -A` -- did that work?
>
>   Paul
>
Thanks Paul! It work for me!

>
>
>
> On Jan 15, 2018 12:34 PM, "eamanu15 ." <emmanuelaria...@gmail.com> wrote:
>
> Hi Paul
>
> El lun., 15 de ene. de 2018 a la(s) 12:52, Paul R. Tagliamonte <
> paul...@gmail.com> escribió:
>
>> How are you running sbuild? You need to tell it if you want it to build
>> an arch:all package with a flag. -A iirc?
>>
>
> I Just run *sbuild *(as indicated on https://wiki.debian.org/sbuild) from
> the new version package folder.
> On ~/.sbuldrc I make this change:
>
> $build_arch_all = 1;$distribution = 'unstable';
>
> And I use lintian:
>
> $run_lintian = 1;$lintian_opts = ['-i', '-I'];
>
> Paul
>>
>>
>> On Jan 15, 2018 10:49 AM, "eamanu15 ." <emmanuelaria...@gmail.com> wrote:
>>
>> Dear Mentors,
>>
>> I start to use sbuild to package. So, I use this tutorial for sbuild
>> setup: https://wiki.debian.org/sbuild
>>
>> When I run sbuild, I have the next error: *E: dsc: amd64 not in arch
>> list or does not match any arch wildcards: all -- skipping*
>>
>> I don't find a solution for the problem on internet, do you have some
>> idea that what could be the problem?
>>
>> Thanks!
>> Regard!
>> Emmanuel
>>
>>
>> --
>> Arias Emmanuel
>> https://www.linkedin.com/in/emmanuel-arias-437a6a8a
>> http://eamanu.com
>>
>>
>>
>
> --
> Arias Emmanuel
> https://www.linkedin.com/in/emmanuel-arias-437a6a8a
> http://eamanu.com
>
>
>

-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Re: E: dsc: amd64 not in arch list

[eamanu15 .]

Hi Paul

El lun., 15 de ene. de 2018 a la(s) 12:52, Paul R. Tagliamonte <
paul...@gmail.com> escribió:

> How are you running sbuild? You need to tell it if you want it to build an
> arch:all package with a flag. -A iirc?
>

I Just run *sbuild *(as indicated on https://wiki.debian.org/sbuild) from
the new version package folder.
On ~/.sbuldrc I make this change:

$build_arch_all = 1;$distribution = 'unstable';

And I use lintian:

$run_lintian = 1;$lintian_opts = ['-i', '-I'];

Paul
>
>
> On Jan 15, 2018 10:49 AM, "eamanu15 ." <emmanuelaria...@gmail.com> wrote:
>
> Dear Mentors,
>
> I start to use sbuild to package. So, I use this tutorial for sbuild
> setup: https://wiki.debian.org/sbuild
>
> When I run sbuild, I have the next error: *E: dsc: amd64 not in arch list
> or does not match any arch wildcards: all -- skipping*
>
> I don't find a solution for the problem on internet, do you have some idea
> that what could be the problem?
>
> Thanks!
> Regard!
> Emmanuel
>
>
> --
> Arias Emmanuel
> https://www.linkedin.com/in/emmanuel-arias-437a6a8a
> http://eamanu.com
>
>
>

-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

E: dsc: amd64 not in arch list

[eamanu15 .]

Dear Mentors,

I start to use sbuild to package. So, I use this tutorial for sbuild setup:
https://wiki.debian.org/sbuild

When I run sbuild, I have the next error: *E: dsc: amd64 not in arch list
or does not match any arch wildcards: all -- skipping*

I don't find a solution for the problem on internet, do you have some idea
that what could be the problem?

Thanks!
Regard!
Emmanuel


-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Re: ITA: pygithub/1.35-1

[eamanu15 .]

Hello everybody,

Paul, Geert and Ghislain thanks for yours feedback. I am working now with
sbuild and I will packaging and will send it again to mentors.debian.

I am using this tutorial for sbuild setup: https://wiki.debian.org/sbuild

But I have this error: *E: dsc: amd64 not in arch list or does not match
any arch wildcards: all -- skipping*

I don't find a solution for the problem, do you have some idea that what
could be the problem?

Thank!
Regard!
Emmanuel


El dom., 14 de ene. de 2018 a la(s) 15:10, Ghislain Vaillant <
ghisv...@gmail.com> escribió:

> 2018-01-14 15:35 GMT+00:00 eamanu15 . <emmanuelaria...@gmail.com>:
> > Hello Geert,
> >
> > El dom., 14 de ene. de 2018 a la(s) 04:16, Geert Stappers
> > <stapp...@stappers.nl> escribió:
> >>
> >> On Sat, Jan 13, 2018 at 09:42:16PM -0300, eamanu15 . wrote:
> >> > El ene 13, 2018 9:41 PM, "Paul Wise" <p...@debian.org> escribió:
> >> > > On Sat, 2018-01-13 at 21:37 -0300, eamanu15 . wrote:
> >> > > > this is the only change that I have to make??
> >> > > No idea, I didn't review the package.
> >> > Ok, thanks.
> >>
> >> In the Original Post was this
> >>
> >> | Changes since the last upload:
> >> |   * New upstream release
> >> |   * Update Maintainer field from debian/control (Closes: #851187)
> >> |   * Update Standards-Version to 3.9-8
> >> |   * Remove override_dh_installchangelogs target from debian/rules
> >> |   * Update debian/copyright for debian files
>
> One additional comment, your changelog entries lack explicitness.
>
> "Update" means nothing if you don't provide further details.
>
> What did you update in d/control and d/copyright? What for?
>
> More explicit change logs will facilitate the work of future sponsors.
>
> >> The '3.9-8'  is '3.9.8' which is superseeded.
> >
> >
> > This was a typing error. Sorry.
>
> You should also ensure the packaging is up-to-date with current
> standards (4.1.3).
>
> The Upgrading-Checklist [1] can help you figure out what has changed
> since version 3.9.8.
>
> >> I think that packaging is done in an old environment.
> >> A newer environ should be used.
> >> There are several ways to do that, such as `sbuild`, `pbuilder`
> >> and plain good old `chroot`.
> >>
> > Do you prefer that I packaging  again using a new environment and send
> it to
> > mentors.debian?
>
> You should try your current packaging on a pbuilder, sbuild or chroot
> targetting unstable and run a recent version of Lintian on it to check
> for errors and warnings.
>
> [1] https://www.debian.org/doc/debian-policy/#document-upgrading-checklist
>
> Cheers,
> Ghis
>


-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Re: ITA: pygithub/1.35-1

[eamanu15 .]

Hello Geert,

El dom., 14 de ene. de 2018 a la(s) 04:16, Geert Stappers <
stapp...@stappers.nl> escribió:

> On Sat, Jan 13, 2018 at 09:42:16PM -0300, eamanu15 . wrote:
> > El ene 13, 2018 9:41 PM, "Paul Wise" <p...@debian.org> escribió:
> > > On Sat, 2018-01-13 at 21:37 -0300, eamanu15 . wrote:
> > > > this is the only change that I have to make??
> > > No idea, I didn't review the package.
> > Ok, thanks.
>
> In the Original Post was this
>
> | Changes since the last upload:
> |   * New upstream release
> |   * Update Maintainer field from debian/control (Closes: #851187)
> |   * Update Standards-Version to 3.9-8
> |   * Remove override_dh_installchangelogs target from debian/rules
> |   * Update debian/copyright for debian files
>
>
> The '3.9-8'  is '3.9.8' which is superseeded.
>

This was a typing error. Sorry.

>
> I think that packaging is done in an old environment.
> A newer environ should be used.
> There are several ways to do that, such as `sbuild`, `pbuilder`
> and plain good old `chroot`.
>
> Do you prefer that I packaging  again using a new environment and send it
to mentors.debian?

>
> Groeten
> Geert Stappers
> --
> Leven en laten leven
>
>

-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Re: ITA: pygithub/1.35-1

[eamanu15 .]

Ok, thanks.

El ene 13, 2018 9:41 PM, "Paul Wise" <p...@debian.org> escribió:

> On Sat, 2018-01-13 at 21:37 -0300, eamanu15 . wrote:
>
> > I will send again the mail with the correct data.
>
> No need to do that.
>
> > this is the only change that I have to make??
>
> No idea, I didn't review the package.
>
> --
> bye,
> pabs
>
> https://wiki.debian.org/PaulWise
>

Re: ITA: pygithub/1.35-1

[eamanu15 .]

oh!! sorry me!!

I will send again the mail with the correct data.

this is the only change that I have to make??

Thank you!
Regard,
Emmanuel

El ene 13, 2018 8:48 PM, "Paul Wise"  escribió:

> On Sat, Jan 13, 2018 at 11:48 PM, Emmanuel Arias wrote:
>
> > Source: https://pypi.python.org/pypi/PyGithub
> >   Upstream Author : Emmanuel Arias 
>
> This is incorrect, please do not claim authorship of code you did not
> write.
>
> https://github.com/orgs/PyGithub/people
> https://github.com/PyGithub/PyGithub/blob/master/MAINTAINERS
>
> --
> bye,
> pabs
>
> https://wiki.debian.org/PaulWise
>

ITA: pygithub/1.35-1

[eamanu15 .]

Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

Dear mentors,

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

* Package name: pygithub
  Version : 1.35-1
  Upstream Author : Emmanuel Arias 
* License : LGPL-3+
  Section : python
  Source: https://pypi.python.org/pypi/PyGithub

It builds those binary packages:
python-github - Access to full Github API v3 from Python2
python3-github - Access the full Github API v3 from Python3

To access further information about this package, please visit the
following URL:
  https://mentors.debian.net/package/pygithub

Alternatively, one can download the package with dget using this command:
dget -x 
https://mentors.debian.net/debian/pool/main/p/pygithub/pygithub_1.351.dsc

Changes since the last upload:
  * New upstream release
  * Update Maintainer field from debian/control (Closes: #851187)
  * Update Standards-Version to 3.9-8
  * Remove override_dh_installchangelogs target from debian/rules
  * Update debian/copyright for debian files

Thanks you!
Regards,
Emmanuel Arias




-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Bug#886834: RFS: cligh/0.3-3

[eamanu15 .]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: cligh
   Version : 0.3-3
   Upstream Author : Emmanuel Arias 
* URL : https://salsa.debian.org/debian/cligh
* License : BSD-3-clause

It builds those binary packages:

  cligh - Command-line interface to GitHub

To access further information about this package, please visit the
following URL:
https://mentors.debian.net/package/cligh


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

  dget -x https://mentors.debian.net/debian/pool/main/c/cligh/cligh_0.3-3.dsc

More information about hello can be obtained from https://www.example.com.

Changes since the last upload:
  * Fix obsolete-field-in-dep5-copyright issue
  * Fix spelling-error-in-changelog issue
  * Update Vcs-Browser and Vcs-Git on control file

  Regards,
   Emmanuel Arias



-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Re: Problem with Git Push

[eamanu15 .]

Hello Gianfranco, My username is @eamanu-guest or my mail
emmanuelaria...@gmail.com.
Thanks for all!!!

Regards

El vie., 5 de ene. de 2018 a la(s) 07:30, Gianfranco Costamagna <
locutusofb...@debian.org> escribió:

> Hello, please give me your salsa username and use that one.
> I'm going to delete the one in collab-maint right now :)
>
> G.
>
>
>
>
> Il Giovedì 4 Gennaio 2018 22:33, eamanu15 . <emmanuelaria...@gmail.com>
> ha scritto:
>
>
>
> Gianfranco,
>
>
>
> >this is a private repo
> >
> >please push there
> >git remote add upstream git+ssh://
> youru...@anonscm.debian.org/git/collab-maint/cligh.git
> >
> >I just created a clone of that repo, and we will need a new unstable
> upload with the new VCS fields in case.
> >
>
> I have this error:
>
> remote: error: insufficient permission for adding an object to repository
> database ./objects
> remote: fatal: failed to write object
> error: unpack failed: unpack-objects abnormal exit
> To git+ssh://anonscm.debian.org/git/collab-maint/cligh.git
>  ! [remote rejected] master -> master (unpacker error)
> error: failed to push some refs to 'git+ssh://
> eamanu-gu...@anonscm.debian.org/git/collab-maint/cligh.git'
>
> What happens? That sound like I don't authorized my ssh-key, but I do.
>
>
> --
>
> Arias Emmanuel
> https://www.linkedin.com/in/emmanuel-arias-437a6a8a
> http://eamanu.com
>


-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Re: Problem with Git Push

[eamanu15 .]

Gianfranco,


> this is a private repo
>
> please push there
> git remote add upstream git+ssh://
> youru...@anonscm.debian.org/git/collab-maint/cligh.git
>
> I just created a clone of that repo, and we will need a new unstable
> upload with the new VCS fields in case.
>

I have this error:






*remote: error: insufficient permission for adding an object to repository
database ./objectsremote: fatal: failed to write objecterror: unpack
failed: unpack-objects abnormal exitTo
git+ssh://anonscm.debian.org/git/collab-maint/cligh.git
 ! [remote rejected]
master -> master (unpacker error)error: failed to push some refs to
'git+ssh://eamanu-gu...@anonscm.debian.org/git/collab-maint/cligh.git
'*

What happens? That sound like I don't authorized my ssh-key, but I do.


-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Re: Problem with Git Push

[eamanu15 .]

Gianfranco,

Are there some chance that the repo of cligh is in Salsa?

El jue., 4 de ene. de 2018 a la(s) 11:01, eamanu15 . <
emmanuelaria...@gmail.com> escribió:

> please push there
>> git remote add upstream git+ssh://
>> youru...@anonscm.debian.org/git/collab-maint/cligh.git
>>
>> I just created a clone of that repo, and we will need a new unstable
>> upload with the new VCS fields in case.
>>
>> Ok, Thanks!.  I will make this tonight
>
>
> Regards!
> Emmanuel
>
>
> --
> Arias Emmanuel
> https://www.linkedin.com/in/emmanuel-arias-437a6a8a
> http://eamanu.com
>
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Re: Problem with Git Push to git clone git://anonscm.debian.org/user

[eamanu15 .]

This is what I have in  ~/src/pkg-package/.git/config among others lines
>
>[remote "origin"]
> url = https://anonscm.debian.org/git/team/pkg-package.git
> fetch = +refs/heads/*:refs/remotes/origin/*
>[remote "alioth"]
> url = ssh://stapp...@git.debian.org/git/team/pkg-package.git
> fetch = +refs/heads/*:refs/remotes/alioth/*
>

Ok, I understand. This is like to run *git remote add alioth [URL]* ?

>
> `git pull` reads from origin URL
>
> When I want to _write_ I use different path, the alioth URL, I do
>  `git push alioth`
>
>
> Groeten
> Geert Stappers
> --
> Leven en laten leven
>
>

-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Re: Problem with Git Push

[eamanu15 .]

>
> please push there
> git remote add upstream git+ssh://
> youru...@anonscm.debian.org/git/collab-maint/cligh.git
>
> I just created a clone of that repo, and we will need a new unstable
> upload with the new VCS fields in case.
>
> Ok, Thanks!.  I will make this tonight


Regards!
Emmanuel


-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Problem with Git Push

[eamanu15 .]

Dear mentors,

I am new on debian and I adopt my first package (cligh).

So, first I upload the new version of the package to mentors.debian (me
like maintainer) and then was uploaded to the official repository.

Now, in https://tracker.debian.org/pkg/cligh there is an action need that
is *The VCS repository is NOT up to date
, push the missing
commits. *For this reason, I go to the repository  and do a

*git clone git://anonscm.debian.org/users/kaction-guest/cligh.git*
After clone, I add the new changes and I try to make a push origin but I
have this error:

*The requested URL returned error: 403.*
What is the problem?

I have alioth user and Shared CVS / SSH authorized keys.

Do I need a personal repo? (If this is true, how could I create?)


Thanks!
Regards!
Emmanuel


-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Bug#882817: RFS: cligh/0.3-2 [ITA] -- Command-line interface to GitHub

[eamanu15 .]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: cligh
   Version : 0.3-2
 * URL :  https://github.com/eamanu/cligh
 * License :  Copyright (c) 2010 Christopher M. Brannon

This upload fixes thr RFA (#851186),
so please consider sponsoring it soon.


The package can be found on mentors.d.n:

  https://mentors.debian.net/package/cligh


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

dget -x https://mentors.debian.net/debian/pool/main/c/cligh
/cligh_0.3-1.1.dsc


For more information you can visit: http://the-brannons.com/software/cligh
.html

Regards
Emmanuel
-- 
Arias Emmanuel
https://www.linkedin.com/in/emmanuel-arias-437a6a8a
http://eamanu.com

Bug#881385: RFS: cligh/0.3-1.1 [ITA] -- Command-line interface to GitHub

[eamanu15 .]

Ok. Thanks!

El sáb., 11 de nov. de 2017 a la(s) 07:46, Andrey Rahmatullin <
w...@debian.org> escribió:

> On Sat, Nov 11, 2017 at 10:43:53AM +, eamanu15 . wrote:
> > So, I have to erase the line "Non-maintainer upload" from
> *debian/changelog
> > *file.
> Yes.
>
> > And then,  make some change in the code before change the Maintainer
> field
> > from *debian/control* file.
> Not "make some change in the code" but "improve the package in the ways it
> can be improved".
>
> --
> WBR, wRAR
>
-- 
Arias Emmanuel
http://eamanu.com

Bug#881385: RFS: cligh/0.3-1.1 [ITA] -- Command-line interface to GitHub

[eamanu15 .]

Hello Andrey,

Thank for you response!

OK. I understand.

So, I have to erase the line "Non-maintainer upload" from *debian/changelog
*file.

And then,  make some change in the code before change the Maintainer field
from *debian/control* file.

That is right?

Regards

El sáb., 11 de nov. de 2017 a la(s) 06:32, Andrey Rahmatullin <
w...@debian.org> escribió:

> Control: tags -1 + moreinfo
>
> On Sat, Nov 11, 2017 at 03:17:19AM +, eamanu15 . wrote:
> > Package: sponsorship-requests
> > Severity: normal
> >
> > Dear mentors,
> >
> > I am looking for a sponsor for my package "cligh"
> >
> >  * Package name: cligh
> >Version : 0.3-1.1
> This is a NMU version and the changelog says "Non-maintainer upload.".
> This is wrong as you are making a maintainer upload. lintian even tells
> you that.
> Also, it seems (from the changelog) that changing the maintainer field is
> the only change you did in the package, while it has things to improve
> (even obvious ones like the policy version and the debhelper compat
> level). You should do that.
>
> --
> WBR, wRAR
>
-- 
Arias Emmanuel
http://eamanu.com

Bug#881385: RFS: cligh/0.3-1.1 [ITA] -- Command-line interface to GitHub

[eamanu15 .]

Package: sponsorship-requests
Severity: normal

Dear mentors,

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

 * Package name: cligh
   Version : 0.3-1.1
 * URL :  https://github.com/eamanu/cligh

 * License :  Copyright (c) 2010 Christopher M. Brannon

This upload fixes thr RFA (#851186),
so please consider sponsoring it soon.


The package can be found on mentors.d.n:

  https://mentors.debian.net/package/cligh


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

dget -x
https://mentors.debian.net/debian/pool/main/c/cligh/cligh_0.3-1.1.dsc


For more information you can visit:
http://the-brannons.com/software/cligh.html

Regards
Emmanuel
-- 
Arias Emmanuel
http://eamanu.com

Re: Problems with upload packages

[eamanu15 .]

El jue., 9 de nov. de 2017 a la(s) 10:16, Andrey Rahmatullin <
w...@debian.org> escribió:

> On Thu, Nov 09, 2017 at 12:40:11PM +, eamanu15 . wrote:
> > So, I downloaded the package, I used the dsc to uncompress the folders,
> and
> > then I modified the "control file" and "changelog file" (with dch -i)
> with
> > the purpose tu add me how new Maintainer.
> >
> > Then, I build the package with* dpkg-buildpackage -us -uc -sa* and all is
> > ok.
> >
> > Next, I sign the *.changes with *debsign *.change.*
> >
> > Last, I upload the package using: *dupload *change.* Apparently the
> package
> > send to ftp correctly, but if I loggin to the ftp-upload-master via
> > Filezilla, I just see the *.tar.gz  and not all the tarball generated
> with
> > dpkg-builpackage.
> >
> > And in the https://tracker.debian.org/pkg/cligh not appear my changes.
> >
> > What is happening? What's wrong?
> You cannot upload packages directly to Debian, you need a sponsor. Please
> look at https://mentors.debian.net/intro-maintainers as an introduction
> (especially at the stepas 4 and 5).
>

Thanks! I will read the link!


> --
> WBR, wRAR
>
-- 
Arias Emmanuel
http://eamanu.com

Problems with upload packages

[eamanu15 .]

Hello everybody,

I am a new maintainer. I find an interest (for me) package: cligh (
https://tracker.debian.org/pkg/cligh).

This package was in RFA status and I try to adopted it, so I send my ITA
request. This is the #851186 on bugs.debian.org.

So, I downloaded the package, I used the dsc to uncompress the folders, and
then I modified the "control file" and "changelog file" (with dch -i) with
the purpose tu add me how new Maintainer.

Then, I build the package with* dpkg-buildpackage -us -uc -sa* and all is
ok.

Next, I sign the *.changes with *debsign *.change.*

Last, I upload the package using: *dupload *change.* Apparently the package
send to ftp correctly, but if I loggin to the ftp-upload-master via
Filezilla, I just see the *.tar.gz  and not all the tarball generated with
dpkg-builpackage.

And in the https://tracker.debian.org/pkg/cligh not appear my changes.

What is happening? What's wrong?

Reference: the star (*) mean *cligh_0.3-1.1*

Regards!
-- 
Arias Emmanuel
http://eamanu.com

Bug#879651: marked as done (RFS: passwordsafe/1.03+dfsg-1)

[eamanu15 .]

That looks good!

I am not mentor. I am new in debian project.  But that package sound great.

Regard!
eamanu

El mar., 24 de oct. de 2017 a la(s) 08:54, Debian Bug Tracking System <
ow...@bugs.debian.org> escribió:

> Your message dated Tue, 24 Oct 2017 13:50:44 +0200
> with message-id <20171024115044.ciacxcd66rgxr...@sk2.org>
> and subject line Re: Bug#879651: RFS: passwordsafe/1.03+dfsg-1
> has caused the Debian Bug report #879651,
> regarding RFS: passwordsafe/1.03+dfsg-1
> 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.)
>
>
> --
> 879651: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=879651
> Debian Bug Tracking System
> Contact ow...@bugs.debian.org with problems
>
>
>
> -- Forwarded message --
> From: Bill Blough 
> To: sub...@bugs.debian.org
> Cc:
> Bcc:
> Date: Mon, 23 Oct 2017 19:24:06 -0400
> Subject: RFS: passwordsafe/1.03+dfsg-1
> Package: sponsorship-requests
> Severity: normal
>
>   Dear mentors,
>
>   I am looking for a sponsor and/or someone to grant me upload permissions
>   (I am a DM) for my package "passwordsafe".
>
>  * Package name: passwordsafe
>Version : 1.03+dfsg-1
>Upstream Author : Rony Shapiro 
>  * URL : https://pwsafe.org
>  * License : Artistic-2.0
>Section : utils
>
>   It builds those binary packages:
>
> passwordsafe - Simple & Secure Password Management
> passwordsafe-common - architecture independent files for Password Safe
>
>   To access further information about this package, please visit the
> following URL:
>
>   https://mentors.debian.net/package/passwordsafe
>
>
>   Alternatively, one can download the package with dget using this command:
>
> dget -x
> https://mentors.debian.net/debian/pool/main/p/passwordsafe/passwordsafe_1.03+dfsg-1.dsc
>
>   More information about passwordsafe can be obtained from
> https://pwsafe.org
>
>   Changes since the last upload:
>
>   * Update upstream signing key
>   * New upstream version
>   * Refresh quilt patches
>   * Update standards version to 4.1.1
> - change copyright format URL to HTTPS
>   * Lintian fixes
> - Override false positive spelling error
> - Enable hardening flags
>
>
>   Regards,
>Bill Blough
>
>
>
>
> -- Forwarded message --
> From: Stephen Kitt 
> To: Bill Blough , 879651-d...@bugs.debian.org
> Cc:
> Bcc:
> Date: Tue, 24 Oct 2017 13:50:44 +0200
> Subject: Re: Bug#879651: RFS: passwordsafe/1.03+dfsg-1
> On Mon, Oct 23, 2017 at 07:24:06PM -0400, Bill Blough wrote:
> >   I am looking for a sponsor and/or someone to grant me upload
> permissions
> >   (I am a DM) for my package "passwordsafe".
>
> Looks good, uploaded, thanks for packaging this!
>
> (Gianfranco can address the DM side of things, or we can revisit this
> after a few uploads on my end.)
>
> Regards,
>
> Stephen
>
-- 
Arias Emmanuel
http://eamanu.com