Re: Bug#725499: RFS: monit/1:5.6-1~bpo70+1
+++ Wookey [2013-10-14 04:25 +0100]: +++ Sergey B Kirpichev [2013-10-06 20:30 +0400]: Package: sponsorship-requests Severity: normal Dear mentors, I was asked to update monit's backport for wheezy: * Package name: monit Version : 1:5.6-1~bpo70+1 OK, that looks (and builds) fine. According to http://backports.debian.org/Contribute/ I can't upload until I've been authorised, so I've asked. I'll upload when that's sorted. I've been given the relevant supercow powers so have now uploaded. Wookey -- Principal hats: Linaro, Emdebian, Wookware, Balloonboard, ARM http://wookware.org/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131015113418.gv32...@stoneboat.aleph1.co.uk
Gitorious and debian/watch file
Hello, I need help to create a wonderful watch file. The source is gitorious. I read again and again this page : https://wiki.debian.org/debian/watch#Gitorious I did test again and again but nothing works. I did also search on codesearch.debian.net from #debian-mentors advice. And I saw, I was not alone. I try here, maybe someone has successful with watch file and Gitorious symbiosis. -- Cordialement, Blanc Pierre -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOGTLeKdDifAv21t+=7xbnegw+srwqotd27mzv9pzrxcvvm...@mail.gmail.com
Re: Gitorious and debian/watch file
When asking questions about watch files, at minimum you should point at the download page or website of the project you are asking about. Otherwise we have no idea how to answer your question. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKTje6F-5EhzO8LrVUmeHG8ivue4onQ8OOG857A=nzytdp5...@mail.gmail.com
Re: Gitorious and debian/watch file
It's a general question non specific to my package :) The url is https://gitorious.org/osm-c-tools/osmctools On Tue, Oct 15, 2013 at 5:27 PM, Paul Wise p...@debian.org wrote: When asking questions about watch files, at minimum you should point at the download page or website of the project you are asking about. Otherwise we have no idea how to answer your question. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKTje6F-5EhzO8LrVUmeHG8ivue4onQ8OOG857A=nzytdp5...@mail.gmail.com -- Cordialement, Blanc Pierre -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAOGTLeJBhyGwJsJQGmH7zWtAtRjX3ePCyN7BXosD=07ox9s...@mail.gmail.com
Re: Gitorious and debian/watch file
Creating a watch file for Gitorious will most likely require a redirect service to translate the refs JSON to download URLs. Take for example your osm-c-tools package, it has JSON data with the repo branches and tags available at: https://gitorious.org/osm-c-tools/osmctools/refs The tags can be translated to the tarball URL using the hash: https://gitorious.org/osm-c-tools/osmctools/archive/9cb724682b14840e1fd020eee7a380926424d603.tar.gz It's an ugly filename, but you can mangle that in the watch to become osmctools-0.1.tar.gz Kind Regards, Bas -- GnuPG: 0xE88D4AF1 (new) / 0x77A975AD (old) -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/525d6220.6020...@xs4all.nl
Re: Gitorious and debian/watch file
On Tue, Oct 15, 2013 at 11:33 PM, Pierre Blanc wrote: It's a general question non specific to my package :) Hmm, none of these work any longer: http://codesearch.debian.net/search?q=gitorious.org+path%3Adebian%2Fwatch Unfortunately it appears that gitorious changed their code and now it is incompatible with uscan. Please contact gitorious and ask them to create pages with links to archives for each of the tags for a git repo. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caktje6g7pqwcoe5mtjkvnr5aos61qknnfu9xsaulupsf-kc...@mail.gmail.com
Re: Gitorious and debian/watch file
Hello, On 15 October 2013 17:41, Sebastiaan Couwenberg sebas...@xs4all.nl wrote: https://gitorious.org/osm-c-tools/osmctools/archive/ 9cb724682b14840e1fd020eee7a380926424d603.tar.gz It's an ugly filename, but you can mangle that in the watch to become osmctools-0.1.tar.gz Same link works for tags: https://gitorious.org/osm-c-tools/osmctools/0.1.tar.gz So the only real problem is to find the right tag. -- WBR, Andrew -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CACujMDOYmKnPw28KMKF0Yt3V=klbnt+zq-irtqadrk5hdyu...@mail.gmail.com
Re: Gitorious and debian/watch file
On 10/15/2013 05:58 PM, Andrew Shadura wrote:
Same link works for tags:
https://gitorious.org/osm-c-tools/osmctools/0.1.tar.gz
That's nice to know, but it only works when you add 'archive/' before
the 0.1.tar.gz.
So the only real problem is to find the right tag.
Those are listed in the refs JSON.
I've wipped up a QD Gitorious watch service, you can see it working for
osm-c-tools at:
http://linuxminded.nl/tmp/gitorious-watch/?project=osm-c-toolsrepo=osmctools
The code in question comes down to the gitorious-watch.pl as attached,
that's a CLI tool and just a proof-of-concept. The online code just
formats the output as HTML.
I could make this into a CGI to run on Alioth where previous watch file
redirect services were also hosted IIRC.
Regards,
Bas
--
GnuPG: 0xE88D4AF1 (new) / 0x77A975AD (old)
#!/usr/bin/perl -w
use strict;
use File::Basename;
use Getopt::Long qw(:config bundling no_ignore_case);
use HTTP::Request::Common;
use LWP::UserAgent;
use URI::Escape;
use JSON;
my %cfg = (
project = '',
repo= '',
verbose = 0,
help= 0,
);
my $result = GetOptions(
'p|project=s' = \$cfg{project},
'r|repo=s'= \$cfg{repo},
'v|verbose' = \$cfg{verbose},
'h|help' = \$cfg{help},
);
if(!$result || $cfg{help}) {
print STDERR \n if(!$result);
print Usage: . basename($0) . -p PROJECT -r REPO [OPTIONS]\n\n;
print Options:\n;
print -p, --project NAME Project name on Gitorious\n;
print -r, --repo NAME Repository name on Gitorious\n;
print -v, --verbose Enable verbose output\n;
print -h, --help Display this usage information\n;
exit 1;
}
my $ua = LWP::UserAgent-new(agent = 'gitorious-redirect');
if($cfg{project} $cfg{repo}) {
my $base_url = 'https://gitorious.org/';
$base_url .= URI::Escape::uri_escape($cfg{project}).'/';
$base_url .= URI::Escape::uri_escape($cfg{repo});
my $url = $base_url.'/refs';
print Retrieving URL: $url ... if($cfg{verbose});
my $req = HTTP::Request-new(GET = $url);
my $res = $ua-request($req);
if($res-is_success) {
print Success\n if($cfg{verbose});
my $json = $res-content;
my $data = JSON::decode_json($json);
if($data-{tags} @{$data-{tags}}) {
print Tag | URL\n;
foreach my $tag (@{$data-{tags}}) {
my ($name, $hash) = @{$tag};
my $url = $base_url.'/archive/';
$url .= URI::Escape::uri_escape($hash).'.tar.gz';
print $name | $url\n;
}
}
else {
print Error: No tags found in Gitorious repo!\n;
exit 1;
}
}
else {
print Failed!\n if($cfg{verbose});
print Error: Failed to retrieve URL! ($url)\n;
print HTTP Status: .$res-code. .$res-message.\n;
exit 1;
}
}
else {
print No project and/or repo specified, cannot query Gitorious without them.\n;
exit 1;
}
Re: Gitorious and debian/watch file
Hello, On Tue, 15 Oct 2013 18:25:37 +0200 Sebastiaan Couwenberg sebas...@xs4all.nl wrote: On 10/15/2013 05:58 PM, Andrew Shadura wrote: Same link works for tags: https://gitorious.org/osm-c-tools/osmctools/0.1.tar.gz That's nice to know, but it only works when you add 'archive/' before the 0.1.tar.gz. Oops, my bad, I've accidentally removed that from the URL. -- WBR, Andrew signature.asc Description: PGP signature
Bug#726333: marked as done (RFS: libgaiagraphics/0.5-1)
Your message dated Tue, 15 Oct 2013 16:23:57 + with message-id e1vw7pz-0003cf...@quantz.debian.org and subject line closing RFS: libgaiagraphics/0.5-1 has caused the Debian Bug report #726333, regarding RFS: libgaiagraphics/0.5-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.) -- 726333: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=726333 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sponsorship-requests Severity: normal Dear mentors, As part of the upcoming SpatiaLite transition am I looking for a sponsor for my package libgaiagraphics. Please refer to the thread on debian-gis@ for more information on this transition: https://lists.debian.org/debian-gis/2013/10/msg9.html Package name: libgaiagraphics Version : 0.5-1 Upstream Author : Alessandro Furieri a.furi...@lqt.it URL : https://www.gaia-gis.it/fossil/libgaiagraphics License : LGPL-3.0+ Section : libs It builds those binary packages: libgaiagraphics-dev - Gaia common graphics support - development headers libgaiagraphics1 - Gaia common graphics support libgaiagraphics1-dbg - Gaia common graphics support - debugging symbols To access further information about this package, please visit the following URL: http://mentors.debian.net/package/libgaiagraphics Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/libg/libgaiagraphics/libgaiagraphics_0.5-1.dsc More information about libgaiagraphics can be obtained from https://www.gaia-gis.it/fossil/libgaiagraphics. Changes since the last upload: * New upstream release. * Add myself to uploaders. * Use canonical URLs in Vcs-* fields. * Use dh-autoreconf for retooling. * Build depend on libtiff-dev instead of libtiff5-dev. * Add build dependency on libxml2-dev. * Use upstream version without debian revision when generating symbols. * Pass all hardening flags to configure. * Add lintian overrides for no upstream changelog, link to upstream timeline. * Improve extended description for the shared library package. * Update symbols file for 0.5 on amd64. * Update copyright file. * Bump debhelper compatibility to 9. * Enable Multi-Arch for libgaiagraphics1. Regards, Sebastiaan Couwenberg ---End Message--- ---BeginMessage--- Package libgaiagraphics version 0.5-1 is in experimental now. http://packages.qa.debian.org/libgaiagraphics---End Message---
Bug#725499: marked as done (RFS: monit/1:5.6-1~bpo70+1)
Your message dated Tue, 15 Oct 2013 16:23:58 + with message-id e1vw7pa-0003du...@quantz.debian.org and subject line closing RFS: monit/1:5.6-1~bpo70+1 has caused the Debian Bug report #725499, regarding RFS: monit/1:5.6-1~bpo70+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.) -- 725499: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725499 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sponsorship-requests Severity: normal Dear mentors, I was asked to update monit's backport for wheezy: when you have a moment, could you please upgrade the Monit Debian Wheezy package? The Monit team from v5.5.2 (now 5.6) has fixed an annoying bug, where the favicon was missing, causing 404 responses each time the user visits the http console (and hence potentially triggering firewall measures). I would like to update Monit on my server, but unfortunately the latest package that I find for Debian Wheezy is v5.4-2. It would be awesome of you could update it. Looking forward to hear from you, thanks a lot! I am looking for a sponsor for my package monit. * Package name: monit Version : 1:5.6-1~bpo70+1 * URL : http://mmonit.com/monit/ * License : AGPL-3+ with OpenSSL exception Section : admin It builds those binary packages: monit - utility for monitoring and managing daemons or similar programs To access further information about this package, please visit the following URL: http://mentors.debian.net/package/monit Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/m/monit/monit_5.6-1~bpo70+1.dsc Regards, Sergey B Kirpichev ---End Message--- ---BeginMessage--- Package monit has been removed from mentors.---End Message---
Bug#714688: marked as done (RFS: rekonq/2.3.1-1)
Hello, tags 714688 wontfix thanks Closing because of #712808 I mentioned briefly in that bug report that rekonq is not the only general purpose web browser using qtwebkit: * arora is also using it and it wasn't removed from the archive. * Konqueror can be configured to use qtwebkit as engine, however it wasn't removed from the archive nor patched to not use qtwebkit * qupzilla is using it and it wasn't removed from the archive So the way I see it, debian could deal with this in three different ways: 1. removing rekonq, arora and qupzilla from unstable and patch konqueror to not use qtwebkit 2. not removing anything and let rekonq be re-uploaded to debian sid 3. remove the browser which I am maintaining (note that I am uploading fresh rekonq packages to a debian derivative) while at the same time other browsers based on qtwebkit are available in unstable My favourite option is 2. The option 1 is not my favourite but acceptable for me because at least it's coherent. The option 3 is the one which is currently being done. The way I see it it's completely unacceptable and I'm considering to escalate this to the tech-ctte if we are going to continue with it. Last but not least, if we go for the option 1 at least I would expect to be able to upload rekonq to experimental. signature.asc Description: This is a digitally signed message part.
Bug#726325: subtitlecomposer/0.5.3-4 [RC] -- Subtitles editor for KDE
Just a quick note: I have re-uploaded it removing a dupe entry in the changelog. signature.asc Description: This is a digitally signed message part.
Bug#726451: Fwd: RFS: python-lepl/5.1.3-2 [ITA] -- recursive descent parser library
Package: sponsorship-requests Severity: normal Dear mentors, I am looking for a sponsor for my package python-lepl * Package name: python-lepl Version : 5.1.3-2 Upstream Author : Andrew Cooke and...@acooke.org and contributors * URL : http://www.acooke.org/lepl/ * License : LGPL-2.1 or MPL-1.1 Section : python It builds those binary packages: python-lepl - recursive descent parser library python3-lepl - recursive descent parser library (Python 3) To access further information about this package, please visit the following URL: http://mentors.debian.net/package/python-lepl Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/p/python-lepl/python-lepl_5.1.3-2.dsc More information about hello can be obtained from http://www.example.com. Changes since the last upload: * New maintainer (Closes: #706288) * Bump Standards-Version to 3.9.4 * Change debhelper version to =9 * Remove lintian-overrides Regards, Radu-Bogdan Croitoru
Packaging AngularJS application as part of the python twisted application
Dear mentors, python hackers, Debian developers I'm maintaining buildbot[1] packages for quite some time. While current packaging of this application is not that hard, the upcoming 0.9 release includes a new web interface organized as python module called 'buildbot_www'. This module is in fact an AngularJS web application that build-depends on nodejs and npm. The current procedure of release this module implies following steps: 1) git clone git://github.com/buildbot/buildbot 2) git checkout -tb nine origin/nine 3) cd www 4) python setup.py sdist The last command performs the actual building of the python module: 1) npm/bower downloads necessary Javascript libraries (download 152Mb of js libraries in .tar.gz) 2) the main (minified/uglified) Javascript file is generated 3) other js/css resources are generated using tools like coffeescript and less 4) html files are generated as well In the end these files are included in the resulting python module tarball. It is totally valid python sdist tarball that can be packaged using ordinary rules of Python packaging. But according to the Debian policy this tarball cannot be considered as a source tarball since it contains generated code, minified js/css etc. I have raised the discussion on the upstream mailing list[2]. Their intention is understandable: current approach allows python developers to work on python code whithout bothering with nodejs/npm while frontend devs could easily hack web iterface without need of python backend. Thanks to the conversation on IRC with Ben Finney, I've detected some potential ideas that should be addressed upstream: 1) provide valid (from Debian's PoV) source tarball for buildbot_www Python module 2) have separate source tarball with bundled javascript dependencies that can be handled by DebSrc 3.0 format as additional upstream tarball; also make possible to use this external tarball in the build process without need of internet connection, It would be possible to replace external js deps with ones already packaged for Debian as well, for example. What steps can be done in such case? What can be done better? Please share your thoughts. I believe, there would appear more similar projects in the future, so the conversation should be useful for a lot more people. Thanks. [1]: http://buildbot.net [2]: http://thread.gmane.org/gmane.comp.python.buildbot.devel/9744 -- Best regards, Andriy Senkovych -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAMS_SFKWukZ4Kzekcxg29z=s6jxfwyaquyl8pwn9ceho_aq...@mail.gmail.com
Re: Packaging AngularJS application as part of the python twisted application
(Thanks, Andrii, for including me in this conversation. You may not have known that I'm subscribed to this forum, so no need to send copies to me.) Andrii Senkovych jolly_ro...@itblog.org.ua writes: The last command performs the actual building of the python module: 1) npm/bower downloads necessary Javascript libraries (download 152Mb of js libraries in .tar.gz) So, this is a hack to get Python's distutils to effectively depend on some non-Python software. Those who ignore proper dependency management are doomed to re-implement it, badly :-( 2) the main (minified/uglified) Javascript file is generated 3) other js/css resources are generated using tools like coffeescript and less 4) html files are generated as well These three sound like candidates for upstream using a generic build tool like GNU make or one of the Python-based ones (how do we feel about Fabric?). In the end these files are included in the resulting python module tarball. It is totally valid python sdist tarball that can be packaged using ordinary rules of Python packaging. But according to the Debian policy this tarball cannot be considered as a source tarball since it contains generated code, minified js/css etc. I've encountered much the same thing, sadly. The result is a lot of busy work to separate the download-source-and-repackage from the build-from-source steps, untangling a lot of what upstream have done. Thanks to the conversation on IRC with Ben Finney, I've detected some potential ideas that should be addressed upstream: 1) provide valid (from Debian's PoV) source tarball for buildbot_www Python module A simple start would be a ‘debian/get-foo’ program to download and package the source for the ECMAScript, HTML, etc. More complex measures may be needed, but I'd see how far that takes you first. 2) have separate source tarball with bundled javascript dependencies that can be handled by DebSrc 3.0 format as additional upstream tarball Yes, the output of the above program would be this file. So you'd have it as part of either ‘uscan’ configuration, or as part of a ‘get-orig-source’ target in ‘debian/rules’. What steps can be done in such case? What can be done better? Please share your thoughts. I believe, there would appear more similar projects in the future, so the conversation should be useful for a lot more people. I think we're going to have to (as the Debian Python community? as the broader Debian maintainer community?) come up with a unified approach to dealing with the rapidly increasing tendency for upstream releases bundling doing this. -- \ “If consumers even know there's a DRM, what it is, and how it | `\ works, we've already failed.” —Peter Lee, Disney corporation, | _o__) 2005 | Ben Finney -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/7wy55ujdje@benfinney.id.au
Re: Packaging AngularJS application as part of the python twisted application
On Wed, Oct 16, 2013 at 7:54 AM, Ben Finney wrote: I think we're going to have to (as the Debian Python community? as the broader Debian maintainer community?) come up with a unified approach to dealing with the rapidly increasing tendency for upstream releases bundling doing this. Upstream bundling happens in too many different ways to deal with that in any way other than to push back every time an upstream wants to add yet more embedded code copies[1] to Debian. Tell them to do things in a sane way otherwise we can't add their stuff into Debian. Tell them to read the upstream guide (and update it if need be). Tell them to release proper source tarballs that are exactly the same as their VCS. Tell them to not commit generated files to their VCS. Tell them to never include copies of their dependencies in their VCS. Tell them to switch from systems without sane repository and dependency systems (such as Android, MacOS X and Windows) to GNU/Linux distributions like Debian. Tell them to think about sysadmins before themselves. http://wiki.debian.org/EmbeddedCodeCopies http://wiki.debian.org/UpstreamGuide -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caktje6ehwzs8n1ecab4t2cdkcbupm+uabkok-n2lrd0ayfr...@mail.gmail.com
Fwd: RFS: cl-launch (updated package)
Dear Debian Mentors and Debian Lispers, I am looking for a sponsor for the new version 3.22.1-1 of my package cl-launch. It builds these binary packages: cl-launch - uniform frontend to running Common Lisp code from the shell The package appears to be lintian clean. The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/c/cl-launch - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/c/cl-launch/cl-launch_3.022.1-1.dsc I would be glad if someone uploaded this package for me. Kind regards —♯ƒ • François-René ÐVB Rideau •ReflectionCybernethics• http://fare.tunes.org Intentions are not so much direct descriptions of actual mind processes as Schelling points in the way social animals communicate. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAN7nBXfuwzY0PzD6udLFbo8VUzUZfYdr_aiLjDAEuLEer=h...@mail.gmail.com
Bug#710175: marked as done (RFS: svtplay-dl/0.9.2013.05.06-1 [ITP] -- download videos from video on demand sites)
Your message dated Wed, 16 Oct 2013 04:23:32 + with message-id e1vwidw-kc...@quantz.debian.org and subject line closing RFS: svtplay-dl/0.9.2013.05.06-1 [ITP] -- download videos from video on demand sites has caused the Debian Bug report #710175, regarding RFS: svtplay-dl/0.9.2013.05.06-1 [ITP] -- download videos from video on demand sites 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.) -- 710175: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710175 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sponsorship-requests Severity: wishlist Control: block 709922 by -1 Dear mentors, I am looking for a sponsor for my package svtplay-dl * Package name: svtplay-dl Version : 0.9.2013.05.06-1 Upstream Author : Johan Andersson j...@i19.se * URL : http://github.com/spaam/svtplay-dl * License : MIT Section : utils It builds the following binary package: svtplay-dl - program to download videos from video on demand sites The package seems to be lintian clean with the exception of no-upstream-changelog (caused by upstream not currently keeping a changelog). I have added an override for this warning. To access further information about this package, please visit the following URL: http://mentors.debian.net/package/svtplay-dl Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/s/svtplay-dl/svtplay-dl_0.9.2013.05.06-1.dsc The packaging is available in git (it uses single-debian-patch with all changes on branches in git): https://github.com/olof/debian-svtplay-dl git://github.com/olof/debian-svtplay-dl.git The current state of the packaging is available on the branch master-next (a rebaseable branch). This is a new package, and it closes ITP #709922 [1]: svtplay-dl (0.9.2013.05.06-1) unstable; urgency=low * Initial release. (Closes: #709922) -- Olof Johansson o...@ethup.se Tue, 28 May 2013 22:12:16 +0200 1: http://bugs.debian.org/709922 Regards, -- --- | Olof Johansson http://stdlib.se/ | | irc: zibri https://github.com/olof | --- signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Package svtplay-dl has been removed from mentors.---End Message---
