Re: Question about license file

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

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

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

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

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

Question about license file

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

Re: Question about license file

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

Dealing with "duplicate-font-file" lintian warning

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Re: backport questions

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

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

* 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

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

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 :

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

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

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

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

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

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

Re: backport questions

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

Re: backport questions

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 >

Re: backport questions

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!

Bug#832100: RFS: eclib/20160720-1

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+

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

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

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

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

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

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

backport questions

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

Re: backport questions

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