Bug#832162: RFS: cgit/1.0+git2.8.3-3~bpo8+1 -- hyperfast web frontend for git repositories written in C

[Peter Colberg]

Package: sponsorship-requests
Severity: normal

Dear mentors,

I am looking for a sponsor to upload the package "cgit" to
jessie-backports. I have been added to the backports ACL for
subsequent maintenance.

git clone https://anonscm.debian.org/git/pkg-cgit/pkg-cgit.git
cd pkg-cgit && pristine-tar checkout ../cgit_1.0+git2.8.3.orig.tar.gz
git checkout debian/jessie-backports

Regards,
Peter


signature.asc
Description: PGP signature

Re: backport questions

[Ferenc Wágner]

Etienne Dysli-Metref  writes:

> I would like to backport Shibboleth packages [1] to jessie and wheezy.
>
> - What branch name should I use?
> Documentation for git-buildpackage [2] says "debian/" so that
> would yield "debian/jessie-backports-sloppy", but I've seen
> "backports/" earlier so I'm unsure.

I recommend debian/jessie-backports.

> - Can I push the backport branches to the repositories in [1]?

Yes, please do so.  Please discuss the necessary changes on our mailing
list beforehand, I'd like to keep the delta small.

> - What should the changelog entry look like? "Backport to "?

Start with what dch --bpo proposes, then add new bullets for your
backporting changes (if needed).

> - Are older "backport" changelog entries kept or removed when a new
> version is backported?
> The Backports contribution doc [3] says:
>
>> Backports of an updated version of a package that was backported 
>> before may have a changelog that merges entries of backports of 
>> previous versions, but this is not required.
>
> but I can't make sense out of this...

I think it means that you can keep them (interleaved by the unstable
entries), or you can merge them into a single entry at the tip.  The
former is probably easier to generate, while the latter is easier to
grasp.
-- 
Feri

Re: Dealing with "duplicate-font-file" lintian warning

[Tiago Ilieve]

Hi Dimitry,

On 22 July 2016 at 17:05, Dmitry Bogatov  wrote:
> `apt-get install dh-linktree`. Usage is simple, documentation is good,
> but you can take a look as example at cdist_4.2.1-1.

Thank you. That did the trick[1].

> Unfortunately, dh-linktree is not magic, and you have manually
> specify, what you want to replace with symlinks.

Actually is almost like magic. :-)

Regards,
Tiago.

[1]: https://anonscm.debian.org/git/collab-maint/grip.git/commit/?id=1cf2b0f

-- 
Tiago "Myhro" Ilieve
Blog: https://blog.myhro.info/
GitHub: https://github.com/myhro
LinkedIn: https://br.linkedin.com/in/myhro
Montes Claros - MG, Brasil

Re: Dealing with "duplicate-font-file" lintian warning

[Jakub Wilk]

* Tiago Ilieve , 2016-07-22, 15:49:
W: grip: duplicate-font-file 
usr/share/grip/grip/static/octicons/octicons.ttf also in fonts-octicons


Is there a helper to deal with this kind of issue? Like the 
"sphinxdoc"[2] one, which automatically replaces embedded JS files to 
their respective links?


dh_sphinxdoc is a tool to post-process documentation generated by Sphinx 
at build time. It is necessary, because the set of files you should 
symlink varies with Sphinx version.


But in this case, the files come directly from upstream tarball, so 
there's no need for a dedicated tool. Just use dh_link.


--
Jakub Wilk

Bug#832153: RFS: python-prov/1.4.0-1 [ITP]

[Ghislain Vaillant]

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name: python-prov
  Version : 1.4.0-1
  Upstream Author : Trung Dong Huynh
* URL : https://github.com/trungdong/prov
* License : Expat
  Section : python

It builds those binary packages:

  prov-tools - tools for prov
  python-prov - W3C Provenance Data Model (Python 2)
  python-prov-doc - documentation for prov
  python3-prov - W3C Provenance Data Model (Python 3)

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


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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/p/python-prov/python-prov_1.4.0-1.dsc


Changes since the last upload:

  * Initial release. (Closes: #823436)

Regards,
Ghislain Vaillant

Bug#832143: marked as done (RFS: ipykernel/4.3.1-2 (to experimental!))

[Debian Bug Tracking System]

Your message dated Fri, 22 Jul 2016 20:45:29 + (UTC)
with message-id <1334600355.5937353.1469220329799.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#832143: RFS: ipykernel/4.3.1-2 (to experimental!)
has caused the Debian Bug report #832143,
regarding RFS: ipykernel/4.3.1-2 (to experimental!)
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.)


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

Package: sponsorship-requests
Severity: normal

  Dear mentors,

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

 * Package name: ipykernel
   Version : 4.3.1-2
   Upstream Author : Jupyter Development Team
 * URL : https://github.com/ipython/ipykernel
 * License : BSD-3-clause
   Section : python

  It builds those binary packages:

python-ipykernel - IPython kernel for Jupyter (Python 2)
 python3-ipykernel - IPython kernel for Jupyter (Python 3)

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


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


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

dget -x 
https://mentors.debian.net/debian/pool/main/i/ipykernel/ipykernel_4.3.1-2.dsc


  It is packaged within the Debian Python Modules Team:
Vcs-Git: 
https://anonscm.debian.org/git/python-modules/packages/ipykernel.git
Vcs-Browser: 
https://anonscm.debian.org/cgit/python-modules/packages/ipykernel.git


  The changes since the last upload are:
ipykernel (4.3.1-2) experimental; urgency=medium

  [ Julien Cristau ]
  * Pre-install python2/python3 kernels for jupyter as part of the package.

  [ Julien Puydt ]
  * Push standards-version up.
  * Add depend on python-backports-shutil-get-terminal-size.

 -- Julien Puydt   Fri, 22 Jul 2016 21:33:39 
+0200


  It is part of the effort to package Jupyter in Debian.

  Cheers,

 Snark on #debian-python
--- End Message ---
--- Begin Message ---





Il Venerdì 22 Luglio 2016 22:17, Gianfranco Costamagna 
 ha scritto:
Hi
>   I am looking for a sponsor for my package "ipykernel"


done.


G.--- End Message ---

Re: How get overrides into ftp.debian.org/debian/indices/override.sid.main.gz ?

[Mattia Rizzolo]

On Fri, Jul 22, 2016 at 09:59:19PM +0200, Thomas Schmitt wrote:
> Well, i don't have a strong opinion myself but rather wonder how it was
> decided to put the lines into override.sid.main.gz .

All packages have an override line there.  That's an implementation
detail of the archive software.
at the first acceptance time the ftp guy get to chose whether to leave
what the maintainer picked up, or to change it.

> Are there reverse dependencies which require priority "optional" ?

dunno, but I can tell you that really ftpmasters don't care about
optional vs extra.  As most other people don't…

> Shall i change the priorities in debian/control ?

If you'd like to…
It's possibly nice to have the same value, not personally sure what it
would buy though.

> (Is it a bug or a feature that the new package tracker does not warn ?
>   https://tracker.debian.org/pkg/libburn
> )

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756750

-- 
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  `-


signature.asc
Description: PGP signature

Bug#832122: marked as done (RFS: shadowsocks-libev/2.4.8+ds-1 -- lightweight and secure socks5 proxy)

[Debian Bug Tracking System]

Your message dated Fri, 22 Jul 2016 20:15:50 + (UTC)
with message-id <676959472.5866962.1469218550993.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#832122: RFS: shadowsocks-libev/2.4.8+ds-1 -- 
lightweight and secure socks5 proxy
has caused the Debian Bug report #832122,
regarding RFS: shadowsocks-libev/2.4.8+ds-1 -- lightweight and secure socks5 
proxy
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.)


-- 
832122: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832122
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
package: sponsorship-requests
severity: normal
X-Debbugs-Cc: rogershim...@gmail.com, max.c...@gmail.com, 073p...@gmail.com

Dear mentors,

I am looking for a sponsor for my package "shadowsocks-libev"

 * Package name: shadowsocks-libev
   Version : 2.4.8+ds-1
   Upstream Author : Max Lv 
 * URL : https://www.shadowsocks.org
 * License : GPL-3+
   Section : net

It builds those binary packages:

 libshadowsocks-dev - lightweight and secure socks5 proxy (development files)
 libshadowsocks1 - lightweight and secure socks5 proxy (shared library)
 shadowsocks-libev - lightweight and secure socks5 proxy

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

  https://mentors.debian.net/package/shadowsocks-libev

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

  dget -x 
https://mentors.debian.net/debian/pool/main/s/shadowsocks-libev/shadowsocks-libev_2.4.8+ds-1.dsc

or you can use git-buildpackage to build:
  gbp clone --pristine-tar
https://anonscm.debian.org/git/collab-maint/shadowsocks-libev.git
  git checkout new
  gbp buildpackage -uc -us --git-ignore-branch --git-pristine-tar

Changes since the last upload:

  * Update to upstream v2.4.8
- Remove patches merged by upstream: 0003 0004 0005
- Update patch 0001: make it appliable to this version
- Update debian/control to add newly appended build-dep
- Update debian/rulesi to adjust param ordering as close as upstream
- Update debian/copyright to remove man/, which merged into doc/ folder
  * debian/patches:
- Cherry-Pick upstream patch 0003: add a few spaces to asciidoc to make
  lintian happy. Thanks to Max Lv for fixing this.

I pushed my changes to git repo:
  https://anonscm.debian.org/cgit/collab-maint/shadowsocks-libev.git/log/?h=new

If it's convenient for you, please kindly setup DM upload permission
of this package for me.
Thank you!

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

>I am looking for a sponsor for my package "shadowsocks-libev"


it should be good, let me know in case I didn't upload it correctly

(also I gave you DM)

G.--- End Message ---

Re: Dealing with "duplicate-font-file" lintian warning

[Dmitry Bogatov]

> I'm updating the "grip" package (bug #832000[1]), which resulted in
> the following lintian warning:
>
> W: grip: duplicate-font-file
> usr/share/grip/grip/static/octicons/octicons.ttf also in
> fonts-octicons
>
> Is there a helper to deal with this kind of issue? Like the
> "sphinxdoc"[2] one, which automatically replaces embedded JS files to
> their respective links? Or should I manually declare a dependency on
> "octions" package and symlink the correspondent font files[3] (as
> there's also other files besides the ".tff")?

`apt-get install dh-linktree`. Usage is simple, documentation is good,
but you can take a look as example at cdist_4.2.1-1.

Unfortunately, dh-linktree is not magic, and you have manually
specify, what you want to replace with symlinks.

-- 
Accept: text/plain, text/x-diff
Accept-Language: eo,en,ru
X-Web-Site: sinsekvu.github.io

How get overrides into ftp.debian.org/debian/indices/override.sid.main.gz ?

[Thomas Schmitt]

Hi,

on the old package tracker
  https://packages.qa.debian.org/libb/libburn.html
i see a problem report
  libburn-doc: Override says doc - optional, .deb says doc - extra
  libburn-dev: Override says libdevel - optional, .deb says libdevel - extra

Google brought me to
  https://wiki.debian.org/FtpMaster/Override
and
   http://ftp.debian.org/debian/indices/override.sid.main.gz
where i find these lines

  libburn-doc optionaldoc
  libburn-dev optionallibdevel

The announcement
  https://lists.debian.org/debian-devel/2011/01/msg00307.html
invites me to file a bug if i don't like the override.

Well, i don't have a strong opinion myself but rather wonder how it was
decided to put the lines into override.sid.main.gz .
Are there reverse dependencies which require priority "optional" ?
Shall i change the priorities in debian/control ?

(Is it a bug or a feature that the new package tracker does not warn ?
  https://tracker.debian.org/pkg/libburn
)


Have a nice day :)

Thomas

Bug#832143: RFS: ipykernel/4.3.1-2 (to experimental!)

[Julien Puydt]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

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

 * Package name: ipykernel
   Version : 4.3.1-2
   Upstream Author : Jupyter Development Team
 * URL : https://github.com/ipython/ipykernel
 * License : BSD-3-clause
   Section : python

  It builds those binary packages:

python-ipykernel - IPython kernel for Jupyter (Python 2)
 python3-ipykernel - IPython kernel for Jupyter (Python 3)

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


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


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

dget -x 
https://mentors.debian.net/debian/pool/main/i/ipykernel/ipykernel_4.3.1-2.dsc


  It is packaged within the Debian Python Modules Team:
Vcs-Git: 
https://anonscm.debian.org/git/python-modules/packages/ipykernel.git
Vcs-Browser: 
https://anonscm.debian.org/cgit/python-modules/packages/ipykernel.git


  The changes since the last upload are:
ipykernel (4.3.1-2) experimental; urgency=medium

  [ Julien Cristau ]
  * Pre-install python2/python3 kernels for jupyter as part of the package.

  [ Julien Puydt ]
  * Push standards-version up.
  * Add depend on python-backports-shutil-get-terminal-size.

 -- Julien Puydt   Fri, 22 Jul 2016 21:33:39 
+0200


  It is part of the effort to package Jupyter in Debian.

  Cheers,

 Snark on #debian-python

Bug#832142: RFS: nbformat/4.0.1-1 (ITP in experimental!)

[Julien Puydt]

Package: sponsorship-requests
Severity: wishlist

  Dear mentors,

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

 * Package name: nbformat
   Version : 4.0.1-1
   Upstream Author : Jupyter Development Team
 * URL : https://github.com/jupyter/nbformat
 * License : BSD-3-clause
   Section : python

  It builds those binary packages:

python-nbformat - Jupyter notebook format (Python 2)
 python-nbformat-doc - Jupyter notebook format (documentation)
 python3-nbformat - Jupyter notebook format (Python 3)

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


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


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

dget -x 
https://mentors.debian.net/debian/pool/main/n/nbformat/nbformat_4.0.1-1.dsc


  It is packaged within the Debian Python Modules Team:
Vcs-Git: https://anonscm.debian.org/git/python-modules/packages/nbformat.git
Vcs-Browser: 
https://anonscm.debian.org/cgit/python-modules/packages/nbformat.git


 This packaging work is part of the effort to get Jupyter in Debian.

 Cheers,

Snark on #debian-python

Dealing with "duplicate-font-file" lintian warning

[Tiago Ilieve]

Hi,

I'm updating the "grip" package (bug #832000[1]), which resulted in
the following lintian warning:

W: grip: duplicate-font-file
usr/share/grip/grip/static/octicons/octicons.ttf also in
fonts-octicons

Is there a helper to deal with this kind of issue? Like the
"sphinxdoc"[2] one, which automatically replaces embedded JS files to
their respective links? Or should I manually declare a dependency on
"octions" package and symlink the correspondent font files[3] (as
there's also other files besides the ".tff")?

Regards,
Tiago.

[1]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=832000
[2]: 
https://anonscm.debian.org/git/python-modules/packages/python-social-auth.git/commit/?id=0f00412
[3]: https://packages.debian.org/sid/all/octicons/filelist

-- 
Tiago "Myhro" Ilieve
Blog: https://blog.myhro.info/
GitHub: https://github.com/myhro
LinkedIn: https://br.linkedin.com/in/myhro
Montes Claros - MG, Brasil

Re: Question about license file

[Gianfranco Costamagna]

Hi

>wifite.py has the license statement in the header, IMHO this is sufficient.

after looking at the github repo, I see the project is made of a single py file,
so the internal statement might be good already!
Anyway, I opened an "upstream" issue [1]
>It should be no problem to create a tarball manually.
>The version in this case can be something like 2.0.85~gitedbdedd14


"create a tarball manually" is something that can be avoided with github
projects


www.github.com/user/project/tarball/branch << this gives you the tarball
of latest commit of the branch named "branch"

e.g.
https://github.com/derv82/wifite/tarball/master

and...
yes, I'm really lazy!


[1]https://github.com/derv82/wifite/issues/90

G.

Bug#825390: Are you still interested in your maldetect RFS?

[Sean Whitton]

Dear Emily,

Are you still interested in packaging maldetect for Debian?  We
generally close RFSs which have been reviewed, and where there is no
response to the review, after six weeks.

-- 
Sean Whitton


signature.asc
Description: PGP signature

Re: Question about license file

[Alex Mestiashvili]

On 07/22/2016 05:00 PM, Daniel Echeverry wrote:
> Hi Mentors!
> 
> I am Maintainer of wifite[1][2], Some time ago the upstream migrated
> the project to github[3] and made some Commits. I want update wifite
> with these new changes, but in github repo, the upstream doesn't
> include a license file, and  he hasn't published any tarball. I tried
> contact with the upstream to include a license file in the repo, but I
> can't get answer for several months :(

wifite.py has the license statement in the header, IMHO this is sufficient.

> 
> How can I update wifite with the news changes? Can I make the patch
> with the new changes??

It should be no problem to create a tarball manually.
The version in this case can be something like 2.0.85~gitedbdedd14

Regards,
Alex

Question about license file

[Daniel Echeverry]

Hi Mentors!

I am Maintainer of wifite[1][2], Some time ago the upstream migrated
the project to github[3] and made some Commits. I want update wifite
with these new changes, but in github repo, the upstream doesn't
include a license file, and  he hasn't published any tarball. I tried
contact with the upstream to include a license file in the repo, but I
can't get answer for several months :(

How can I update wifite with the news changes? Can I make the patch
with the new changes??

Thank you very much!

Regards!

[1]: https://packages.qa.debian.org/w/wifite.html
[2]: https://code.google.com/archive/p/wifite/
[3]: https://github.com/derv82/wifite

-- 
Daniel Echeverry
http://wiki.debian.org/DanielEcheverry
http://rinconinformatico.net
Linux user: #477840
Debian user

Bug#832122: RFS: shadowsocks-libev/2.4.8+ds-1 -- lightweight and secure socks5 proxy

[Roger Shimizu]

package: sponsorship-requests
severity: normal
X-Debbugs-Cc: rogershim...@gmail.com, max.c...@gmail.com, 073p...@gmail.com

Dear mentors,

I am looking for a sponsor for my package "shadowsocks-libev"

 * Package name: shadowsocks-libev
   Version : 2.4.8+ds-1
   Upstream Author : Max Lv 
 * URL : https://www.shadowsocks.org
 * License : GPL-3+
   Section : net

It builds those binary packages:

 libshadowsocks-dev - lightweight and secure socks5 proxy (development files)
 libshadowsocks1 - lightweight and secure socks5 proxy (shared library)
 shadowsocks-libev - lightweight and secure socks5 proxy

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

  https://mentors.debian.net/package/shadowsocks-libev

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

  dget -x 
https://mentors.debian.net/debian/pool/main/s/shadowsocks-libev/shadowsocks-libev_2.4.8+ds-1.dsc

or you can use git-buildpackage to build:
  gbp clone --pristine-tar
https://anonscm.debian.org/git/collab-maint/shadowsocks-libev.git
  git checkout new
  gbp buildpackage -uc -us --git-ignore-branch --git-pristine-tar

Changes since the last upload:

  * Update to upstream v2.4.8
- Remove patches merged by upstream: 0003 0004 0005
- Update patch 0001: make it appliable to this version
- Update debian/control to add newly appended build-dep
- Update debian/rulesi to adjust param ordering as close as upstream
- Update debian/copyright to remove man/, which merged into doc/ folder
  * debian/patches:
- Cherry-Pick upstream patch 0003: add a few spaces to asciidoc to make
  lintian happy. Thanks to Max Lv for fixing this.

I pushed my changes to git repo:
  https://anonscm.debian.org/cgit/collab-maint/shadowsocks-libev.git/log/?h=new

If it's convenient for you, please kindly setup DM upload permission
of this package for me.
Thank you!

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

Re: backport questions

[Etienne Dysli-Metref]

On 22/07/16 14:15, Alexander Wirt wrote:
>> And the distribution field should be the backport target
>> (jessie-backports-sloppy), right?
> Depends on your backport. The one that matches to your backport. And
> jessie-backports-sloppy is in every case wrong at this point in time. 

Ah right, yes! that should be jessie-backports or wheezy-backports-sloppy.

  Etienne



signature.asc
Description: OpenPGP digital signature

Re: backport questions

[Alexander Wirt]

On Fri, 22 Jul 2016, Etienne Dysli-Metref wrote:

> Thank you Alex :)
> 
> On 22/07/16 13:16, Alexander Wirt wrote:
> >> - Can I push the backport branches to the repositories in [1]?
> > The backports team doesn't care about the git, you will have to ask the 
> > other
> > maintainers. 
> 
> Ok
> 
> >> - What should the changelog entry look like? "Backport to "?
> > That + all backports specific changes to the package.
> And the distribution field should be the backport target
> (jessie-backports-sloppy), right?
Depends on your backport. The one that matches to your backport. And
jessie-backports-sloppy is in every case wrong at this point in time. 

Alex


signature.asc
Description: PGP signature

Re: backport questions

[Etienne Dysli-Metref]

Thank you Alex :)

On 22/07/16 13:16, Alexander Wirt wrote:
>> - Can I push the backport branches to the repositories in [1]?
> The backports team doesn't care about the git, you will have to ask the other
> maintainers. 

Ok

>> - What should the changelog entry look like? "Backport to "?
> That + all backports specific changes to the package.
And the distribution field should be the backport target
(jessie-backports-sloppy), right?

Cheers,
  Etienne



signature.asc
Description: OpenPGP digital signature

Re: backport questions

[Alexander Wirt]

On Fri, 22 Jul 2016, Etienne Dysli-Metref wrote:

> Hello mentors,
> 
> I would like to backport Shibboleth packages [1] to jessie and wheezy.
> 
> - What branch name should I use?
> Documentation for git-buildpackage [2] says "debian/" so that
> would yield "debian/jessie-backports-sloppy", but I've seen
> "backports/" earlier so I'm unsure.
> 
> - Can I push the backport branches to the repositories in [1]?
The backports team doesn't care about the git, you will have to ask the other
maintainers. 
> 
> - What should the changelog entry look like? "Backport to "?
That + all backports specific changes to the package.

> - Are older "backport" changelog entries kept or removed when a new
> version is backported?
> The Backports contribution doc [3] says:
> 
> > Backports of an updated version of a package that was backported 
> > before may have a changelog that merges entries of backports of 
> > previous versions, but this is not required.
> 
> but I can't make sense out of this...
You can, but you don't have to include the changelog entrys in the changes
file. We (ftpmasters)  don't enforce this (anymore). 

Alex - ftpmaster



signature.asc
Description: PGP signature

backport questions

[Etienne Dysli-Metref]

Hello mentors,

I would like to backport Shibboleth packages [1] to jessie and wheezy.

- What branch name should I use?
Documentation for git-buildpackage [2] says "debian/" so that
would yield "debian/jessie-backports-sloppy", but I've seen
"backports/" earlier so I'm unsure.

- Can I push the backport branches to the repositories in [1]?

- What should the changelog entry look like? "Backport to "?

- Are older "backport" changelog entries kept or removed when a new
version is backported?
The Backports contribution doc [3] says:

> Backports of an updated version of a package that was backported 
> before may have a changelog that merges entries of backports of 
> previous versions, but this is not required.

but I can't make sense out of this...

Thanks for your help,
  Etienne

[1] https://anonscm.debian.org/cgit/pkg-shibboleth/
[2]
http://honk.sigxcpu.org/projects/git-buildpackage/manual-html/gbp.import.html#GBP.BRANCH.NAMING
[3] https://backports.debian.org/Contribute/



signature.asc
Description: OpenPGP digital signature

Bug#832060: marked as done (RFS: logdata-anomaly-miner/0.0.3-1 [ITA] -- lightweight tool for log checking, log analysis)

[Debian Bug Tracking System]

Your message dated Fri, 22 Jul 2016 10:47:18 + (UTC)
with message-id <1235061744.5442906.1469184438618.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#832060: RFS: logdata-anomaly-miner/0.0.3-1 [ITA] -- 
lightweight tool for log checking, log analysis
has caused the Debian Bug report #832060,
regarding RFS: logdata-anomaly-miner/0.0.3-1 [ITA] -- lightweight tool for log 
checking, log analysis
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.)


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

Dear mentors,

I am looking for a sponsor for my package " logdata-anomaly-miner":

* Package name: logdata-anomaly-miner
* Version: 0.0.3-1
* Upstream Author: Roman Fiedler 
* URL: https://launchpad.net/logdata-anomaly-miner
* License: GPLv3
* Section: admin

  It builds those binary packages:

  logdata-anomaly-miner - lightweight tool for log checking, log analysis


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

URL:

https://mentors.debian.net/package/logdata-anomaly-miner


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

dget -x https://mentors.debian.net/debian/pool/main/h/hello/hello_3.1-4.dsc

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


Changes since the last upload:

* New upstream release (Closes: #832058).

Regards,
Roman Fiedler


PS: This mail will be the template for future requests.


smime.p7s
Description: S/MIME cryptographic signature
--- End Message ---
--- Begin Message ---
Hi,

>  logdata-anomaly-miner - lightweight tool for log checking, log analysis

>dget -x https://mentors.debian.net/debian/pool/main/h/hello/hello_3.1-4.dsc
>
>More information about hello can be obtained from https://www.example.com.


please fill with real links thanks


>PS: This mail will be the template for future requests.

please not, mentors creates the template for you when you dput (it is written
in the mail you receive IIRC), or ping me privately with just a dsc link.

Gianfranco--- End Message ---

Bug#832064: marked as done (RFS: meanwhile/1.0.2-9)

[Debian Bug Tracking System]

Your message dated Fri, 22 Jul 2016 10:34:29 + (UTC)
with message-id <1615723579.5372738.1469183669401.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#832064: RFS: meanwhile/1.0.2-9
has caused the Debian Bug report #832064,
regarding RFS: meanwhile/1.0.2-9
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.)


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

Dear mentors,

 I am looking for a sponsor for a QA upload:

* Package name: meanwhile
  Version : 1.0.2-9
  Upstream Author : Christopher O'Brien 
* URL : http://meanwhile.sf.net
* License : LGPL
  Section : net

 It builds those binary packages:

libmeanwhile-dev - development package for libmeanwhile1
libmeanwhile1 - open implementation of the Lotus Sametime Community Client 
protoc

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

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

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

   dget -x 
https://mentors.debian.net/debian/pool/main/m/meanwhile/meanwhile_1.0.2-9.dsc

Changes since the last upload:

  * Fix a login issue due to code optimization.  Closes: #764494 

Regards,
Breno Leitao


signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
Hi,


>I am looking for a sponsor for a QA upload:


uploaded,

G.--- End Message ---

Bug#832100: marked as done (RFS: eclib/20160720-1)

[Debian Bug Tracking System]

Your message dated Fri, 22 Jul 2016 10:13:26 + (UTC)
with message-id <1110607330.5332955.1469182406811.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#832100: RFS: eclib/20160720-1
has caused the Debian Bug report #832100,
regarding RFS: eclib/20160720-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.)


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

Package: sponsorship-requests
Severity: normal

  Dear mentors,

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

 * Package name: eclib
   Version : 20160720-1
   Upstream Author : John Cremona
 * URL : https://github.com/JohnCremona/eclib/
 * License : GPL-2+
   Section : math

  It builds those binary packages:

eclib-tools - Programs for modular symbols and elliptic curves over Q
 libec-dev  - Library for modular symbols and elliptic curves over Q 
(developme

 libec2 - Library for modular symbols and elliptic curves over Q

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


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


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

dget -x 
https://mentors.debian.net/debian/pool/main/e/eclib/eclib_20160720-1.dsc


  It is packaged within the Debian Science team:
Vcs-Git: https://anonscm.debian.org/git/debian-science/packages/eclib.git
Vcs-Browser: 
https://anonscm.debian.org/cgit/debian-science/packages/eclib.git



  This upload is a new upstream version -- a bugfix release for better 
C++11 support.


Cheers,

Snark on #debian-science
--- End Message ---
--- Begin Message ---
Hi,

>I am looking for a sponsor for my package "eclib"


Signed and uploaded.

G.--- End Message ---

Bug#832100: RFS: eclib/20160720-1

[Julien Puydt]

Package: sponsorship-requests
Severity: normal

  Dear mentors,

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

 * Package name: eclib
   Version : 20160720-1
   Upstream Author : John Cremona
 * URL : https://github.com/JohnCremona/eclib/
 * License : GPL-2+
   Section : math

  It builds those binary packages:

eclib-tools - Programs for modular symbols and elliptic curves over Q
 libec-dev  - Library for modular symbols and elliptic curves over Q 
(developme

 libec2 - Library for modular symbols and elliptic curves over Q

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


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


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

dget -x 
https://mentors.debian.net/debian/pool/main/e/eclib/eclib_20160720-1.dsc


  It is packaged within the Debian Science team:
Vcs-Git: https://anonscm.debian.org/git/debian-science/packages/eclib.git
Vcs-Browser: 
https://anonscm.debian.org/cgit/debian-science/packages/eclib.git



  This upload is a new upstream version -- a bugfix release for better 
C++11 support.


Cheers,

Snark on #debian-science

Bug#827933: RFS: yabar/0.4.0-3 [ITP]

[Jack Henschel]

On 07/22/2016 03:32 AM, Sean Whitton wrote:
> I just took a look at the yabar homepage.  It says that "Yabar is still
> in its infancy and far from being mature. Feel free to contribute or
> report bugs!"

Initially, I was also held of by this disclaimer.
However there are two reasons why I decided to package yabar for Debian anyway:
* I have seen people use yabar "in production", since it can easily be extended 
with custom scripts
* while using yabar myself I have not encountered any breaking/major issues.

> As a general rule, experimental software is not included in Debian.
> However, plenty of upstreams write "far from mature" when really the
> software is mature and is suitable for Debian.
> 
> Do you consider yabar to be sufficiently mature?

That is exactly how I would describe it. yabar is not complete and yabar has 
some issues (as can be seen on GitHub).
Nevertheless, yabar is not experimental software and I do not expect any 
breaking changes (i.e. config file syntax).

Best Regards,
Jack Henschel



signature.asc
Description: OpenPGP digital signature