Bug#847969: marked as done (RFS: libpam-ldap/186-2)

2016-12-28 Thread Debian Bug Tracking System
Your message dated Thu, 29 Dec 2016 11:29:54 +0500
with message-id <20161229062954.o7g7k7p4awl4l...@belkar.wrar.name>
and subject line Re: Bug#847969: RFS: libpam-ldap/186-2
has caused the Debian Bug report #847969,
regarding RFS: libpam-ldap/186-2
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.)


-- 
847969: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=847969
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 "libpam-ldap"

* Package name: libpam-ldap
  Version : 186-2
  Upstream Author : [fill in name and email of upstream]
* URL : [fill in URL of upstreams web site]
* License : [fill in]
  Section : admin

It builds those binary packages:

  libpam-ldap - Pluggable Authentication Module for LDAP

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

https://mentors.debian.net/package/libpam-ldap


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

dget -x 
https://mentors.debian.net/debian/pool/main/libp/libpam-ldap/libpam-ldap_186-2.dsc


Changes since the last upload:

It fixes #844666 bug.
 

Regards,
  Lucas Castro




signature.asc
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Uploaded, thanks.

-- 
WBR, wRAR


signature.asc
Description: PGP signature
--- End Message ---


Bug#847969: RFS: libpam-ldap/186-2

2016-12-28 Thread Andrey Rahmatullin
Uploaded, thanks.

-- 
WBR, wRAR


signature.asc
Description: PGP signature


Bug#849521: Package updated

2016-12-28 Thread Taylor Kline
Removed moreinfo tag since I have corrected or overrode all lintian
errors/warnings.

Rationale for my changes should be evident from the email exchanges above.

Looking forward to any feedback and potential sponsorship 😄 thanks so much!

-Taylor



Bug#849521: Assistance with packaging ruTorrent

2016-12-28 Thread Taylor Kline
> Remove the file from the tarball, you shouldn't use it anyway, use the
> libjs-jquery-flot package instead.

Oh, nice! Thank you for pointing that out! Got it :)

> > 2. Two source-is-missing errors that are false positives because of a long
> > line in the source file.
> Why do you think they are false positives? Very long lines aren't usually
> user-editable.

They are false positives because the long lines are strings with HTML tags, i.e.

   ""

> > But if I create a
> >
> >   debian/rutorrent.lintian-overrides
> >
> > with the contents:
> >
> >   rutorrent source: source-is-missing plugins/extsearch/init.js
> >
> > then I get an error:
> >
> >   rutorrent: malformed-override Override of source-is-missing for package
> > type source (expecting binary)
> >
> > How can I successfully override these?
> debian/rutorrent.lintian-overrides contains overrides for the rutorrent
> binary package. The manual says "If the override is for a source package,
> you have to place it at debian/source/lintian-overrides or
> debian/source.lintian-overrides (the former path is preferred)."

Now I continue to get the lintian error and then have a warning:

  rutorrent source: unused-override source-is-missing plugins/extsearch/init.js

😕 any idea why lintian will not use the override?

- ACTUALLY, GOT IT --
I left the above for future reference for anyone else confused, but I
had to copy the entire line:

  rutorrent source: source-is-missing plugins/extsearch/init.js line
length is 288 characters (>256)

Looks like lintian is very particular in this way.

Now I just have my questions from part 3 remaining 😊 I was actually
able to drop-in a excanvas and libphp-snoopy, so it's only
libjs-jquery that I cannot drop in version 3 without breaking the
entire system. I would really like to push forward with including
jquery v1.11.2 in the missing-sources if possible.

Thanks so much for your help so far.

-Taylor



Bug#848687: RFS: yasnippet-snippets_0~git20161123-1

2016-12-28 Thread Sean Whitton
Hello Alberto,

On Wed, Dec 28, 2016 at 11:43:29PM +0100, Alberto Luaces wrote:
> I have now pushed a new release.

Did someone else upload 0~git20161123-1?

If not, you should merge the changelog entries for -1 and -2.  It's just
confusing to have changlog entries that never made it into the Debian
archive.

After merging them, be sure to run `dch -r` to update the timestamp.

Also, I think you need to put a tag '0_git20161123' on the upstream
branch.  That's how gbp generates a tarball.

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#849489: RFS: darksnow/0.7.1-1 [QA]

2016-12-28 Thread David Davies-Jones
Hello again

I shall go through it with a fine toothcomb over the next few days. Yes,
this may be a better method. At the moment, I make changes as I can, which
can result in loosing track of what I've done. I shall experiment with
using git like this and see how I go on. With the packages that I've been
putting up to mentors I've been constructing a mental checklist of what I'm
learning, need to start putting it down in writing and following it rigidly.

I shall let you know when I've reuploaded

Many Thanks

David

On 28 December 2016 at 22:47, Sean Whitton  wrote:

> control: owner -1 !
>
> Hello David,
>
> On Wed, Dec 28, 2016 at 09:12:49PM +, David Davies-Jones wrote:
> > I've tried addressing the issues you've raised and re-uploaded to
> mentors. If
> > there are any more problems please let me know
>
> Thanks for your updated package.  I'm sorry not to have raised this in
> my previous message, but there are other changes you've made that are
> not documented in the changelog.  For example, you dropped some
> build-dependencies, and you renamed a quilt patch.  Please check the
> difference between 0.6.1-3 and 0.7.1-1 carefully.
>
> Tip: it's easier if you work in git, rather than just handling source
> packages.  This is what I just did to review your work:
>
> % dget -d https://mentors.debian.net/debian/pool/main/d/darksnow/
> darksnow_0.7.1-1.dsc
> % dgit clone darksnow
> % dgit import-dsc ../darksnow_0.7.1-1.dsc david
> % git checkout david
> % git diff dgit/dgit/sid..HEAD
>
> By the way, it would be good to forward your darksnow.desktop upstream
> (that won't be reflected in your QA upload, of course).
>
> --
> Sean Whitton
>


Bug#849489: RFS: darksnow/0.7.1-1 [QA]

2016-12-28 Thread Sean Whitton
Hello David,

On Wed, Dec 28, 2016 at 10:53:00PM +, David Davies-Jones wrote:
> I shall go through it with a fine toothcomb over the next few days. Yes, this
> may be a better method. At the moment, I make changes as I can, which can
> result in loosing track of what I've done. I shall experiment with using git
> like this and see how I go on. With the packages that I've been putting up to
> mentors I've been constructing a mental checklist of what I'm learning, need 
> to
> start putting it down in writing and following it rigidly.

Cool.  It's not arduous once you're in the habit of updating the
changelog every time you make a git commit.  I'm biased here, but a
decent git workflow is in this tutorial: dgit-maint-merge(7)

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#849489: RFS: darksnow/0.7.1-1 [QA]

2016-12-28 Thread Sean Whitton
control: owner -1 !

Hello David,

On Wed, Dec 28, 2016 at 09:12:49PM +, David Davies-Jones wrote:
> I've tried addressing the issues you've raised and re-uploaded to mentors. If
> there are any more problems please let me know

Thanks for your updated package.  I'm sorry not to have raised this in
my previous message, but there are other changes you've made that are
not documented in the changelog.  For example, you dropped some
build-dependencies, and you renamed a quilt patch.  Please check the
difference between 0.6.1-3 and 0.7.1-1 carefully.

Tip: it's easier if you work in git, rather than just handling source
packages.  This is what I just did to review your work:

% dget -d 
https://mentors.debian.net/debian/pool/main/d/darksnow/darksnow_0.7.1-1.dsc
% dgit clone darksnow
% dgit import-dsc ../darksnow_0.7.1-1.dsc david
% git checkout david
% git diff dgit/dgit/sid..HEAD

By the way, it would be good to forward your darksnow.desktop upstream
(that won't be reflected in your QA upload, of course).

--
Sean Whitton


signature.asc
Description: PGP signature


Bug#848687: RFS: yasnippet-snippets_0~git20161123-1

2016-12-28 Thread Alberto Luaces
Sean Whitton writes:

> Hello Alberto,
>
> On Wed, Dec 28, 2016 at 09:31:53PM +0100, Alberto Luaces wrote:
>> Thanks, Sean.  I have addressed the gbp.conf and changelog issues and I
>> think the realease is ready to go.
>
> Thanks again for your work.
>
> gbp.conf says upstream-branch=upstream but your upstream sources are on
> a branch called 'master' ...

Thanks for noticing!  Strangely enough, I missed that because gbp
buildpackage was successful nevertheless.

I have now pushed a new release.



Bug#848687: RFS: yasnippet-snippets_0~git20161123-1

2016-12-28 Thread Sean Whitton
Hello Alberto,

On Wed, Dec 28, 2016 at 09:31:53PM +0100, Alberto Luaces wrote:
> Thanks, Sean.  I have addressed the gbp.conf and changelog issues and I
> think the realease is ready to go.

Thanks again for your work.

gbp.conf says upstream-branch=upstream but your upstream sources are on
a branch called 'master' ...

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#849581: RFS: numpydoc/0.6.0+ds1-1

2016-12-28 Thread Ghislain Vaillant
Package: sponsorship-requests
Severity: normal

Dear mentors,

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

* Package name: numpydoc
  Version : 0.6.0+ds1-1
  Upstream Author : Pauli Virtanen and others
* URL : https://github.com/numpy/numpydoc
* License : BSD
  Section : python

It builds those binary packages:

  python-numpydoc - Sphinx extension to support docstrings in Numpy format -- 
Python 2
  python3-numpydoc - Sphinx extension to support docstrings in Numpy format -- 
Python 3

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

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

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

  dget -x 
https://mentors.debian.net/debian/pool/main/n/numpydoc/numpydoc_0.6.0+ds1-1.dsc

Successful build on debomatic:

  
http://debomatic-amd64.debian.net/distribution#unstable/numpydoc/0.6.0+ds1-1/buildlog

Changes since the last upload:

  * Team upload

  [ Ondřej Nový ]
  * Fixed VCS URL (https)

  [ Ghislain Antony Vaillant ]
  * Filter upstream tarball from vendored sphinx.ext.linkcode
  * New upstream release
  * Update copyright file
  * Bump versioned depends on Python to 2.7 and 3.4
  * Bump standards version to 3.9.8, no changes required
  * Add packaging testsuite
  * Rearrange copyright paragraphs to fix Lintian warnings
  * Add build dependency on dh-python
  * Improve description of the Python 2 binary package
  * cme fix dpkg-control:
- Drop versioned dependency on python-all
- Drop versioned dependency on python[,3]-sphinx
- Wrap and sort
  * cme fix dpkg-copyright: use HTTPS URI in Format field

Regards,
Ghislain Vaillant



Bug#849553: marked as done (RFS: python-coards/1.0.5-1 [ITP])

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 21:27:01 +
with message-id <1482960421.1926.4.ca...@gmail.com>
and subject line 
has caused the Debian Bug report #849553,
regarding RFS: python-coards/1.0.5-1 [ITP]
to be marked as done.

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

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


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

Dear mentors,

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

* Package name: python-coards
  Version : 1.0.5-1
  Upstream Author : Roberto De Almeida
* URL : http://code.dealmeida.net/coards
* License : Expat
  Section : python

It builds those binary packages:

  python-coards - COARDS-compliant time parser (Python 2)
  python3-coards - COARDS-compliant time parser (Python 3)

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

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

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

  dget -x https://mentors.debian.net/debian/pool/main/p/python-coards/p
ython-coards_1.0.5-1.dsc

Successful build on debomatic:

  http://debomatic-amd64.debian.net/distribution#unstable/python-coards
/1.0.5-1/buildlog

Changes since the last upload:

  * Initial release. (Closes: #849541)

Regards,
Ghis
--- End Message ---
--- Begin Message ---
sponsored by Andreas Tille--- End Message ---


Bug#849560: marked as done (RFS: python-imageio/2.1.1+ds1-1 [ITP])

2016-12-28 Thread Debian Bug Tracking System
Your message dated Wed, 28 Dec 2016 21:26:22 +
with message-id <1482960382.1926.3.ca...@gmail.com>
and subject line 
has caused the Debian Bug report #849560,
regarding RFS: python-imageio/2.1.1+ds1-1 [ITP]
to be marked as done.

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

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


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

Dear mentors,

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

* Package name: python-imageio
  Version : 2.1.1+ds1-1
  Upstream Author : Almar Klein 
* URL : https://github.com/imageio/imageio
* License : BSD
  Section : python

It builds those binary packages:

  python-imageio - library for reading and writing image data (Python
2)
  python-imageio-doc - documentation for imageio
  python3-imageio - library for reading and writing image data (Python
3)

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

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

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

  dget -x https://mentors.debian.net/debian/pool/main/p/python-imageio/
python-imageio_2.1.1+ds1-1.dsc

Successful build on debomatic:

  http://debomatic-amd64.debian.net/distribution#unstable/python-imagei
o/2.1.1+ds1-1/buildlog

Changes since the last upload:

  * Initial release. (Closes: #769767)

Regards,
Ghis
--- End Message ---
--- Begin Message ---
sponsored by Andreas Tille--- End Message ---


Bug#849489: RFS: darksnow/0.7.1-1 [QA]

2016-12-28 Thread David Davies-Jones
Hello

I've tried addressing the issues you've raised and re-uploaded to mentors.
If there are any more problems please let me know

Many thanks

David Jones

On 27 December 2016 at 22:07, Sean Whitton  wrote:

> control: tag -1 +moreinfo
>
> Dear David,
>
> Thanks for your source package.  A few comments:
>
> On Tue, Dec 27, 2016 at 08:04:33PM +, David Davies-Jones wrote:
> >  * QA upload.
> >  * New upstream release (Closes: #839027)
> >  * Set maintainer to QA Group
>
> It would be good to refer to the orphaning bug here.  E.g. "(see
> #xx)".
>
> >
> >  * Converted rules to dh format
> >  * Compat level 10
> >  * Converted patches to quilt & refreshed
>
> Did you change the source package format?  Please say this explicitly.
>
> >
> >  * Converted copyright to DEP-5
> >  * Standards version 3.9.8
>
> Did you have to update anything in the packaging to conform to this new
> standards version?  If not, it's conventional to append "(no changes
> required)".
>
> >  * Replaced menu file with desktop
>
> I think you mean "with a desktop file" -- and do you mean the menu file
> in the debian/ directory?  Please be more explicit.
>
> Changes missing from changelog:
>
> - added d/clean
> - stopped installing darksnow_icon.xpm
>
> --
> Sean Whitton
>


Bug#849521: Assistance with packaging ruTorrent

2016-12-28 Thread Andrey Rahmatullin
On Wed, Dec 28, 2016 at 02:56:17PM -0500, Taylor Kline wrote:
> 1. A source-is-missing error:
> 
>   js/jquery.flot.js line length is 3134 characters (>512)
> 
> This one occurs because the library flot (https://github.com/flot/flot),
> which does not have a later release from the included release in 2014, has
> an inlined function of 3134 characters:
> https://github.com/flot/flot/blob/master/jquery.flot.js
> 
> Any tips on a good way to correct this?
Remove the file from the tarball, you shouldn't use it anyway, use the
libjs-jquery-flot package instead.

> 2. Two source-is-missing errors that are false positives because of a long
> line in the source file.
Why do you think they are false positives? Very long lines aren't usually
user-editable.

> But if I create a
> 
>   debian/rutorrent.lintian-overrides
> 
> with the contents:
> 
>   rutorrent source: source-is-missing plugins/extsearch/init.js
> 
> then I get an error:
> 
>   rutorrent: malformed-override Override of source-is-missing for package
> type source (expecting binary)
> 
> How can I successfully override these?
debian/rutorrent.lintian-overrides contains overrides for the rutorrent
binary package. The manual says "If the override is for a source package,
you have to place it at debian/source/lintian-overrides or
debian/source.lintian-overrides (the former path is preferred)."


-- 
WBR, wRAR


signature.asc
Description: PGP signature


Bug#848687: RFS: yasnippet-snippets_0~git20161123-1

2016-12-28 Thread Alberto Luaces
Thanks, Sean.  I have addressed the gbp.conf and changelog issues and I
think the realease is ready to go.

Please tell me if you think that something is still missing.



Bug#849521: Assistance with packaging ruTorrent

2016-12-28 Thread Taylor Kline
Hello JavaScript Team,

I have a package pending with a Request for Sponsorship (my first package),
and I am blocked with the following lintian errors:

1. A source-is-missing error:

  js/jquery.flot.js line length is 3134 characters (>512)

This one occurs because the library flot (https://github.com/flot/flot),
which does not have a later release from the included release in 2014, has
an inlined function of 3134 characters:
https://github.com/flot/flot/blob/master/jquery.flot.js

Any tips on a good way to correct this?

---

2. Two source-is-missing errors that are false positives because of a long
line in the source file.

But if I create a

  debian/rutorrent.lintian-overrides

with the contents:

  rutorrent source: source-is-missing plugins/extsearch/init.js

then I get an error:

  rutorrent: malformed-override Override of source-is-missing for package
type source (expecting binary)

How can I successfully override these?

---

3. embedded-javascript-library warnings because upstream has packaged their
dependencies. The dependency versions are very old, for example:

Based on the md5sum of jquery.js, upstream is using jQuery v1.11.2.

libjs-jquery is 3.1.1-2, two major versions ahead, thus I doubt I can drop
in this replacement and test thoroughly enough to ship it with any
confidence that there won't be many run-time bugs.

And if I can't drop in a replacement, I would feel quite a hindrance to the
developer bothering him with updating his JavaScript dependencies that
currently work just fine.

I have noticed that, for example, the "wordpress" package has overrides:
# Opportunistic replacement is in place but the Debian version does
# not match the wordpress version
wordpress: embedded-javascript-library
usr/share/wordpress/wp-includes/js/jquery/jquery.form.js please use
libjs-jquery-form
wordpress: embedded-javascript-library
usr/share/wordpress/wp-includes/js/jquery/jquery.form.min.js please use
libjs-jquery-form
...

Is it acceptable for me to do the same, at least for the time being?

---

Package can be seen here:

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

and the associated RFS:

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


Bug#849521: RFS: rutorrent/3.7-1 [ITP] -- A front-end for the rTorrent torrent client

2016-12-28 Thread Taylor Kline
Thank you for your prompt attention! I will email the JS mailing list.

On Wed, Dec 28, 2016 at 4:28 AM, Sean Whitton 
wrote:

> control: tag -1 +moreinfo
>
> Dear Taylor,
>
> Thanks for this package.  Looks interesting.
>
> On Tue, Dec 27, 2016 at 11:26:30PM -0500, Taylor Kline wrote:
> > lintian is throwing the following 'serious' errors that I haven't been
> entirely
> > sure what to do with:
> >
> >   jquery.flot.js source missing - this file has an inlined function of
> 3134
> > characters. Unfortunately this cannot be corrected in a straightforward
> manner
> > because the flot library has not been maintained since 2014.
>
> It would violate DFSG if you didn't include the source.  The upload
> would be rejected by the ftp-masters.  So you need to replace this file
> with something that has source code.  The Debian javascript team might
> be able to help.
>
> > There are also a few warnings about using embedded js libraries. The
> versions
> > included are much older than the libjs versions available in the Debian
> > packaging system. Thus it may take some conversations with upstream to
> > integrate these wishlist items.
>
> You need to have these conversations with upstream before this can go
> into Debian: all Debian packages need to use the packaged versions of
> libraries.
>
> If you're able to resolve these issues, please remove the moreinfo tag
> from this bug.
>
> --
> Sean Whitton
>


Bug#849560: RFS: python-imageio/2.1.1+ds1-1 [ITP]

2016-12-28 Thread Ghislain Vaillant
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name: python-imageio
  Version : 2.1.1+ds1-1
  Upstream Author : Almar Klein 
* URL : https://github.com/imageio/imageio
* License : BSD
  Section : python

It builds those binary packages:

  python-imageio - library for reading and writing image data (Python
2)
  python-imageio-doc - documentation for imageio
  python3-imageio - library for reading and writing image data (Python
3)

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

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

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

  dget -x https://mentors.debian.net/debian/pool/main/p/python-imageio/
python-imageio_2.1.1+ds1-1.dsc

Successful build on debomatic:

  http://debomatic-amd64.debian.net/distribution#unstable/python-imagei
o/2.1.1+ds1-1/buildlog

Changes since the last upload:

  * Initial release. (Closes: #769767)

Regards,
Ghis



Bug#849553: RFS: python-coards/1.0.5-1 [ITP]

2016-12-28 Thread Ghislain Vaillant
Hi Ben, thanks for reviewing my package.

On Thu, 2016-12-29 at 02:17 +1100, Ben Finney wrote:
> Please add a paragraph to the description(s) which state what “the
> COARDS convention” means — enough for someone unfamiliar with that term
> to decide whether they want the package.

Done, please have a look at the updated package on mentors.

Cheers,
Ghis



Bug#849553: RFS: python-coards/1.0.5-1 [ITP]

2016-12-28 Thread Ben Finney
Ghislain Vaillant  writes:

> I am looking for a sponsor for my package "python-coards"

Thank you for working to improve Debian.

The package description should give the reader enough information to
make a decision about whether they are interested in the package.

That entails that any jargon which cannot be assumed as common knowledge
must be briefly explained.

=
Description: COARDS-compliant time parser (Python 2)
 This module is intended to help parse time values represented using the
 COARDS convention.
 […]
=

Please add a paragraph to the description(s) which state what “the
COARDS convention” means — enough for someone unfamiliar with that term
to decide whether they want the package.

-- 
 \  “Some forms of reality are so horrible we refuse to face them, |
  `\ unless we are trapped into it by comedy. To label any subject |
_o__)unsuitable for comedy is to admit defeat.” —Peter Sellers |
Ben Finney 



Bug#849553: RFS: python-coards/1.0.5-1 [ITP]

2016-12-28 Thread Ghislain Vaillant
Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name: python-coards
  Version : 1.0.5-1
  Upstream Author : Roberto De Almeida
* URL : http://code.dealmeida.net/coards
* License : Expat
  Section : python

It builds those binary packages:

  python-coards - COARDS-compliant time parser (Python 2)
  python3-coards - COARDS-compliant time parser (Python 3)

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

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

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

  dget -x https://mentors.debian.net/debian/pool/main/p/python-coards/p
ython-coards_1.0.5-1.dsc

Successful build on debomatic:

  http://debomatic-amd64.debian.net/distribution#unstable/python-coards
/1.0.5-1/buildlog

Changes since the last upload:

  * Initial release. (Closes: #849541)

Regards,
Ghis



Bug#849521: RFS: rutorrent/3.7-1 [ITP] -- A front-end for the rTorrent torrent client

2016-12-28 Thread Sean Whitton
control: tag -1 +moreinfo

Dear Taylor,

Thanks for this package.  Looks interesting.

On Tue, Dec 27, 2016 at 11:26:30PM -0500, Taylor Kline wrote:
> lintian is throwing the following 'serious' errors that I haven't been 
> entirely
> sure what to do with:
> 
>   jquery.flot.js source missing - this file has an inlined function of 3134
> characters. Unfortunately this cannot be corrected in a straightforward manner
> because the flot library has not been maintained since 2014.

It would violate DFSG if you didn't include the source.  The upload
would be rejected by the ftp-masters.  So you need to replace this file
with something that has source code.  The Debian javascript team might
be able to help.

> There are also a few warnings about using embedded js libraries. The versions
> included are much older than the libjs versions available in the Debian
> packaging system. Thus it may take some conversations with upstream to
> integrate these wishlist items.

You need to have these conversations with upstream before this can go
into Debian: all Debian packages need to use the packaged versions of
libraries.

If you're able to resolve these issues, please remove the moreinfo tag
from this bug.

-- 
Sean Whitton


signature.asc
Description: PGP signature


Bug#848687: RFS: yasnippet-snippets_0~git20161123-1

2016-12-28 Thread Sean Whitton
control: owner -1 !
control: tag -1 +moreinfo

Hello Alberto,

On Mon, Dec 19, 2016 at 04:48:05PM +0100, Alberto Luaces wrote:
> After cloning the mentioned repository, one can generate both the source
> and the binary packages from it issuing
> 
> gbp buildpackage --git-debian-branch=debian --git-upstream-branch=master

You should provide a debian/gbp.conf that contains these settings.  Take
a look at other pkg-emacsen team repos.

Before I can sponsor this, I need you to update your changelog entry.
The date is 1st December, but you made changes almost two weeks after
that, so you need to re-run `dch -r`, after your final changes.
Further, you made a lot of changes to debian/ but none of them are
listed in your changelog entry.  Please add them.

-- 
Sean Whitton


signature.asc
Description: PGP signature