Bug#718981: Review of your ruby-colorator package
Hi, sorry for my late response, thanks for your kindly review. At Thu, 20 Feb 2014 16:07:08 +0100, Dominique Dumont wrote: > > Good work: your package builds fine without lintian warnings. > > There's still some issues: > * fix debian/copyright: upstream license is MIT, not expat (the text is > correct, the license shortname is not) https://www.debian.org/doc/packaging-manuals/copyright-format/1.0/ Sec: License specification "There are many versions of the MIT license. Please use Expat instead, when it matches." Thus I write License as "Expat" in debian/copyright. It's my mistake? If yes, I'll fix many other packages "debian/copyright" as MIT instead of Expat. Best Wishes, Youhei --- Youhei SASAKI GPG fingerprint: 4096/RSA: 66A4 EA70 4FE2 4055 8D6A C2E6 9394 F354 891D 7E07 -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87lhx2gx88.wl%uwab...@gfd-dennou.org
Bug#739845: ITP: roger-router -- AVM FRITZ!Box remote control and monitor
Package: wnpp Severity: wishlist Owner: Rolf Leggewie * Package name: roger-router Version : 1.8.4 Upstream Author : Jan-Michael Brummer * URL : http://www.tabos.org * License : (GPL, LGPL, Expat) Description : AVM FRITZ!Box remote control and monitor Roger Router is the successor to the abandoned ffgtk project. It is developed by the same people who were in charge of ffgtk. I am the current maintainer for ffgtk in Debian and I would like to continue to make Roger Router available to the Debian community. Fritz Fun (ffgtk) is a remote control software for the popular AVM all-in-one hardware home router Fritz!Box. It allows fax and call handling, call monitoring as well as administration of the DSL connection. The program can trigger scripts for a number of events such as missed calls or to pause the music player on incoming calls. . You need an AVM FRITZ!Box or this software will be fairly useless to you. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140223050152.20032.82689.report...@www.google-analytics.com
Bug#739842: RFP: fontconfig-infinality -- The purpose of these patches is to freely provide the nicest font rendering of any operating system. The second goal is to provide customization so that the e
Package: wnpp Severity: wishlist Package name: fontconfig-infinality Version : 2.4.12 Upstream Author : http://www.infinality.net/ URL : https://github.com/Infinality/fontconfig-infinality License : GPL Programming Lang: Description : The purpose of these patches is to freely provide the nicest font rendering of any operating system. The second goal is to provide customization so that the end user is able to adjust the settings to his or her taste. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140223024708.11129.89777.reportbug@debian.debian
Bug#739836: ITP: healpix-cxx -- presentation of data for spherical surface
Package: wnpp Severity: wishlist Owner: Steffen Moeller * Package name: healpix-cxx * URL : http://healpix.sourceforge.net * License : GPL-2+ Programming Lang: C++ Description : presentation of data for spherical surface The package is about to be uploaded, maintained by Leo in debian-science/healpix/healpix-cxx -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/trinity-0f701f1a-d619-4300-bd86-62e20f4b1b37-1393118019898@3capp-gmx-bs37
Bug#739815: RFA: signing-party -- Various OpenPGP related tools
Hi, I'd also be happy to give a hand by becoming an adopter. Cheers, -- Guilhem. signature.asc Description: Digital signature
Bug#738292: marked as done (ITA: fabric -- Simple Pythonic remote deployment tool)
Your message dated Sat, 22 Feb 2014 23:33:25 +
with message-id
and subject line Bug#738292: fixed in fabric 1.8.2-1
has caused the Debian Bug report #738292,
regarding ITA: fabric -- Simple Pythonic remote deployment tool
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.)
--
738292: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=738292
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: wnpp
Severity: normal
X-Debbugs-CC: debian-de...@lists.debian.org
I am orphaning this package so that it can be more actively maintained.
Full Git maintenance history is available - see the Vcs-Git headers in
debian/control.
Source: fabric
Section: net
Priority: optional
Maintainer: Debian QA Group
Build-Depends: debhelper (>= 7.0.50~), python-all (>= 2.6.6-3~)
Build-Depends-Indep: python-setuptools, python-sphinx, python-paramiko
Standards-Version: 3.9.3
Vcs-Git: git://github.com/lamby/pkg-fabric.git
Vcs-Browser: https://github.com/lamby/pkg-fabric
Homepage: http://fabfile.org/
Package: fabric
Architecture: all
Depends: ${misc:Depends}, ${python:Depends}, python-paramiko (>= 1.6),
python-pkg-resources, python-nose Suggests: libjs-jquery
Description: Simple Pythonic remote deployment tool
Fabric is designed to upload files and run shell commands on a number of
servers in parallel or serially. These commands are grouped in tasks
(which are regular Python functions) and specified in a 'fabfile.'
.
It is similar to Capistrano, except it's implemented in Python and doesn't
expect you to be deploying Rails applications.
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` la...@debian.org
`-
--- End Message ---
--- Begin Message ---
Source: fabric
Source-Version: 1.8.2-1
We believe that the bug you reported is fixed in the latest version of
fabric, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 738...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Ana Beatriz Guerrero Lopez (supplier of updated fabric
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Sat, 22 Feb 2014 23:01:27 +0100
Source: fabric
Binary: fabric
Architecture: source all
Version: 1.8.2-1
Distribution: unstable
Urgency: medium
Maintainer: Ana Beatriz Guerrero Lopez
Changed-By: Ana Beatriz Guerrero Lopez
Description:
fabric - Simple Pythonic remote deployment tool
Closes: 738292
Changes:
fabric (1.8.2-1) unstable; urgency=medium
.
* New upstream release.
* New maintainer. (Closes: #738292)
* Bump debian/compat to 8
* Update Standards-Version: 3.9.5, no changes required.
* Change Vcs-Git and Vcs-Git fields to my github copy.
* Modify debian/copyright to add myself in the packaging copyright.
* Add patch no_adsense.patch, to remove Google Adsense in the html
documentation.
* Disable sphinx extension "releases", it is not included in Debian. See
patch disable_sphinx_extension.patch.
Checksums-Sha1:
8a219a7292faccc1461e2d736f3c0cf7e10e69f6 1904 fabric_1.8.2-1.dsc
5931fac0d35cba57c17f4553ccfde53443828e91 251398 fabric_1.8.2.orig.tar.gz
32cb946fb4c995dbb1cb67b66001727853fcc473 4232 fabric_1.8.2-1.debian.tar.xz
b8fe72bba0c5d9969e9fdbbeed07a63f4532fc5f 292020 fabric_1.8.2-1_all.deb
Checksums-Sha256:
def364fff4861320f776e8e47c6d975ea34a5866c96f8947211715cd17bc5fe6 1904
fabric_1.8.2-1.dsc
ae810aee9114c5e7ef3ce7a0f6fb6293d1dfcfcfa846aa4e007f3ae42beaf62b 251398
fabric_1.8.2.orig.tar.gz
ef111d0b5752c68a064daa680998a2fd3adf7880bec565923337089023de2170 4232
fabric_1.8.2-1.debian.tar.xz
dce6bbba8844f7318bc869de8153511d6866c4583853aaa2d81f22106ad9cc68 292020
fabric_1.8.2-1_all.deb
Files:
3ef340c56b67aaf24f2ada2221cda65a 1904 net optional fabric_1.8.2-1.dsc
8666ee90d093cdb393f1b168cc0f5672 251398 net optional fabric_1.8.2.orig.tar.gz
a620ad888bbd0d5f3e41a9a733cf0894 4232 net optional fabric_1.8.2-1.debian.tar.xz
adb091a6b8c97d87b24556f76b057b8e 292020 net optional fabric_1.8.2-1_all.deb
-BEGIN PGP SIGNATURE-
Version: GnuPG v1
Comment: Signed by Ana Guerrero
iQIcBAEBCAAGBQJTCTAaAAoJELNGT4lqoVlIhTkQAJjAL5ih0djWNj4Q0
Bug#730356: marked as done (ITP: kscreen -- KDE monitor hotplug and screen handling)
Your message dated Sat, 22 Feb 2014 22:00:06 + with message-id and subject line Bug#730356: fixed in kscreen 1.0.2.1-1 has caused the Debian Bug report #730356, regarding ITP: kscreen -- KDE monitor hotplug and screen handling 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.) -- 730356: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=730356 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist Owner: Rohan Garg * Package name: kscreen Version : 1.0.2 Upstream Author : Alejandro Fiestas Olivares * URL : http://download.kde.org/stable/kscreen/ * License : GPL-2.0+, LGPL-2.1+, BSD Programming Lang: C++ Description : KDE monitor hotplug and screen handling The KDE multiple monitor support is trying be as smart as possible adapting the behavior of it to each use case making the configuration of monitors as simple as plugging them to your computer. --- End Message --- --- Begin Message --- Source: kscreen Source-Version: 1.0.2.1-1 We believe that the bug you reported is fixed in the latest version of kscreen, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 730...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Maximiliano Curia (supplier of updated kscreen package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Fri, 21 Feb 2014 01:46:40 +0100 Source: kscreen Binary: kscreen kscreen-dbg Architecture: source amd64 Version: 1.0.2.1-1 Distribution: unstable Urgency: low Maintainer: Debian KDE Extras Team Changed-By: Maximiliano Curia Description: kscreen- KDE monitor hotplug and screen handling kscreen-dbg - KDE monitor hotplug and screen handling, debug info Closes: 730356 Changes: kscreen (1.0.2.1-1) unstable; urgency=low . [ Rohan Garg ] * Initial release (Closes: #730356) . [ Maximiliano Curia ] * Add autopkgtests. * New patch: add_switchDisplayTwoScreensNoCommonMode_json Checksums-Sha1: 35c94817917befd5c434f60c75d7964ff5218e14 2159 kscreen_1.0.2.1-1.dsc 0ff884e83db29a8751a9fd52ce6bb99403267420 79372 kscreen_1.0.2.1.orig.tar.xz 4b747df3336b4b45b9cdf1e046f72d062dc61b49 6220 kscreen_1.0.2.1-1.debian.tar.xz ff848509ad7738da21a93b24c01108d318b9514e 129562 kscreen_1.0.2.1-1_amd64.deb 26102480293239a3491b25dc390b0ee86208e347 1518602 kscreen-dbg_1.0.2.1-1_amd64.deb Checksums-Sha256: 5b83a4adcbae55d5c66a2639ce3d5600c41e599eef096169c962dfc260054fbe 2159 kscreen_1.0.2.1-1.dsc bb9c77ec11f209bfe8170da04f979dbb5cb031681de457fea355517049cca005 79372 kscreen_1.0.2.1.orig.tar.xz 58e19be41165420f81559e98c01fe943635660721048d50235e5c815ac2c0030 6220 kscreen_1.0.2.1-1.debian.tar.xz fc2ac6ba8db1a2d2d345c5c48f5c2cad5de6dd127bf9d0f4c4f7d4f601001b07 129562 kscreen_1.0.2.1-1_amd64.deb e2827784f756337b9fcb61d8fb87772eed0fa9b228da34286f77119d07b47720 1518602 kscreen-dbg_1.0.2.1-1_amd64.deb Files: 29228162d3df588ba4c7f0366afb40d8 2159 kde optional kscreen_1.0.2.1-1.dsc cd3d6ffdb0e44c418c2804fc72b8391b 79372 kde optional kscreen_1.0.2.1.orig.tar.xz d3bb8b0b1d18c3a04cf756f78e0a5a1b 6220 kde optional kscreen_1.0.2.1-1.debian.tar.xz f02e85ba341405fb08b075b7793e9caa 129562 kde optional kscreen_1.0.2.1-1_amd64.deb 1cf012267bf9360dc9f8ba8474985e33 1518602 debug extra kscreen-dbg_1.0.2.1-1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBCAAGBQJTBqM+AAoJEMcZdpmymyMqk/kP/jRutjQ7yydkrs3afSKWZ3RU 6o/RQYPloY9nbkc9Wwy2JLJ8oQqY1ecrAZpzjbVta0XOQs7EjM5JaCKhye/tt+NV qMa+dAfNy+tjFqqBvhBe3NcjJVANbl7gBTcHKMIdB3Ve7WkwYTURXxBjQAxUhgRk qo/wyJXP/JNB4Q2AXjMTjqd/yN8yhOGZ1iei9YTydkceP/f1iprvUKCaZcXKBfRt I0BHPGwqBpC8AQvc48P78XyoCiom6bNe17q4e+LysPP4b+Dl4iHZ556s3mMRYJv4 BiW/xqA7mNZSwdVObZNtO3E+yF3tCuiKO8WmsJxmrxKMTJ6TTRuKRytJzTI2GLci vcOdT6w+GlR5Fcr2KyG6cy470hA7+5DGE0UKnSf6D1vMXT+DnZpLoQB50YHeo+t1 uq+LfTInS+KteOjcjSFB3RDBbmt2pqS1Ba1X+KF3dNWgafEEDmTAe4mhqXm3DS5V Y54DvCNRdViO5rg1Hp33JyiQZ1x7XR4H3+sjLOv9OPHvjl5L5kYSc7+VxHMYMD6+ zY80CASM3K6hhyTfCw2LbLaTM1r6FxUVcjwT3M98yJFobh9znSUe/ThlYmDP1+d8 zA9LTXkggD5aS6pVHsyADCtLfXA63wGh6BhyVJQdO6o7X/BDTFmnMHXHJsPUcwDb Bmeo9xuqZH3X+slB9uYu =Wfld -END PGP SIGNATURE
Bug#739084: marked as done (ITA: maradns -- simple security-focused authoritative)
Your message dated Sat, 22 Feb 2014 21:23:33 + with message-id and subject line Bug#739084: fixed in maradns 2.0.09-1 has caused the Debian Bug report #739084, regarding ITA: maradns -- simple security-focused authoritative 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.) -- 739084: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739084 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: normal The current maintainer of maradns, Nicholas Bamber , has orphaned this package. Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see http://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Package: maradns Binary: maradns, maradns-zoneserver, duende, maradns-docs Version: 1.4.12-5 Maintainer: Nicholas Bamber Build-Depends: debhelper (>= 8.9.10~), python-dev (>= 2.6.6-3~), html2text Architecture: any all Standards-Version: 3.9.3 Format: 3.0 (quilt) Files: 1c7b9046f4054d4c2d1e262b816045c0 1969 maradns_1.4.12-5.dsc f45dcd5dd8d488a7a6c5e18fef8414c0 1178772 maradns_1.4.12.orig.tar.bz2 e86af7630840910dee28cfa2a9291eaf 40307 maradns_1.4.12-5.debian.tar.gz Vcs-Browser: http://github.com/periapt/maradns Vcs-Git: git://github.com/periapt/maradns.git Checksums-Sha1: 39b1a447ad627df2152d1ab36702f36048fe88b4 1969 maradns_1.4.12-5.dsc 7198e3292c199a9ec3e831f76f96c25ad6a86956 1178772 maradns_1.4.12.orig.tar.bz2 4ac006ac6690e53203e94446137e1e7cb1717d1f 40307 maradns_1.4.12-5.debian.tar.gz Checksums-Sha256: e2368bac5ff72b24ef2370bad70294ac5d7c2c1e9b49143ec5483f9c062f0e19 1969 maradns_1.4.12-5.dsc 72c0e0fd10e4d9ed70d8c7addb9b0abd2cf2d23f6b477db3aefd69c9faa0893b 1178772 maradns_1.4.12.orig.tar.bz2 93f539dedfcc0e982f18be82ad893f7f6ea3e3b8495e1a5ae8411d6a36ba6909 40307 maradns_1.4.12-5.debian.tar.gz Homepage: http://maradns.org Package-List: duende deb admin optional maradns deb net extra maradns-docs deb doc extra maradns-zoneserver deb net extra Directory: pool/main/m/maradns Priority: source Section: net Package: maradns Version: 2.0.06-2 Installed-Size: 770 Maintainer: Nicholas Bamber Architecture: amd64 Depends: libc6 (>= 2.4), adduser, lsb-base, duende (>= 1.4.06-3) Recommends: python, maradns-zoneserver Suggests: maradns-deadwood Description-en: simple security-focused authoritative Domain Name Service server MaraDNS is easy to configure DNS server that functions as an authoritative domain name server. MaraDNS is optimised for serving a small number of domains quickly and efficiently. Well suited to host your own private DNS server for making up subdomains with minimal fuss. Maradns is security-aware by utilising a special string library which is resistant to buffer overflows and mandating to run as an unprivileged user. . For the recursive name server component and IPv6 support see maradns-deadwood. For TCP and domain transfer support see maradns-zoneserver. Description-md5: e9564392a6e45370574aec923ab20e1e Homepage: http://maradns.org Tag: implemented-in::c, interface::daemon, network::server, protocol::dns, role::program Section: net Priority: extra Filename: pool/main/m/maradns/maradns_2.0.06-2_amd64.deb Size: 389708 MD5sum: a7938b73f906ab7effaf10a9d39a6023 SHA1: f59b555930866e42aec14096e8a2ec891847b697 SHA256: 1c10033ecaf2645c4a48e8c159b06c523298e52fc725fb435ff01457e3f11b31 Package: maradns Version: 1.4.12-5 Installed-Size: 747 Maintainer: Nicholas Bamber Architecture: amd64 Depends: libc6 (>= 2.4), adduser, lsb-base, duende (>= 1.4.06-3), ucf Recommends: python, maradns-zoneserver Description-en: simple security-focused Domain Name Service server MaraDNS is easy to configure DNS server that functions as a recursive and/or authoritative name server. MaraDNS is optimised for serving a small number of domains quickly and efficiently. Well suited to host your own private DNS server for making up subdomains with minimal fuss. Maradns is security-aware by utilising a special string library which is resistant to buffer overflows and mandating to run as an unprivileged user. Description-md5: cb012063520a6eefaa8b1a4f484d8980 Homepage: http://maradns.org Tag: implemented-in::c, interface::daemon, network::server, protocol::dns, role::program Section: net Priority: extra Filename: pool/main/m/maradns/maradns_1.4.12-5_amd64.deb Size: 412774 MD5sum: f70962dc253e99a8d09cadd3f8c29e6b SHA1: ce7870922fda1fb0c245958ba8f4d88f5fb0ae4
Bug#739815: RFA: signing-party -- Various OpenPGP related tools
I would be interested in becoming an adopter for this package. Let me know what the process would be. Cheers, Justin On Feb 22, 2014 12:57 PM, "Thijs Kinkhorst" wrote: > Package: wnpp > Severity: normal > > We request an adopter for the signing-party package. There's currently > a number of co-maintainers but the majority of them have indicated to > have no time to contribute a lot to the package. > > The package is an interesting collection of tools and in the BTS there's > a number of useful patches and reports that need to be evaluated and > where relevant, applied to the package. > > Since the team is also upstream there's a lot of flexibility and > freedom to make changes that you see fit. > > The packaging is currently in svn but a move to another vcs if so > preferred is perfectly fine. > > The package description is: > signing-party is a collection for all kinds of PGP/GnuPG related things, > including tools for signing keys, keyring analysis, and party preparation. > . > * caff: CA - Fire and Forget signs and mails a key > * pgp-clean: removes all non-self signatures from key > * pgp-fixkey: removes broken packets from keys > * gpg-mailkeys: simply mail out a signed key to its owner > * gpg-key2ps: generate PostScript file with fingerprint paper strips > * gpgdir: recursive directory encryption tool > * gpglist: show who signed which of your UIDs > * gpgsigs: annotates list of GnuPG keys with already done signatures > * gpgparticipants: create list of party participants for the organiser > * gpgwrap: a passphrase wrapper > * keyanalyze: minimum signing distance (MSD) analysis on keyrings > * keylookup: ncurses wrapper around gpg --search > * sig2dot: converts a list of GnuPG signatures to a .dot file > * springgraph: creates a graph from a .dot file > > Let me know if there are any questions. > > Cheers, > Thijs > > > -- > To UNSUBSCRIBE, email to debian-security-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: > http://lists.debian.org/20140222174337.7773.73170.reportbug@localhost.localdomain > >
Processed (with 1 errors): ITP: think-rotate -- Rotation scripts for ThinkPad X220 Tablet
Processing commands for cont...@bugs.debian.org: > retitle 731035 ITP: thinkpad-scripts -- Rotation scripts for ThinkPad Bug #731035 [wnpp] ITP: think-rotate -- Rotation scripts for ThinkPad X220 Tablet. Changed Bug title to 'ITP: thinkpad-scripts -- Rotation scripts for ThinkPad' from 'ITP: think-rotate -- Rotation scripts for ThinkPad X220 Tablet.' > X220 Tablet. Unknown command or malformed arguments to command. > stop Stopping processing here. Please contact me if you need assistance. -- 731035: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731035 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.13931038185698.transcr...@bugs.debian.org
Bug#729203: Packaging for FFmpeg avoiding conflicts with libav
Hi, [only replying with my lintian maintainer hat here, from the sec. point of view it would take a more lengthy mail] On Saturday 22 February 2014 18:39:20 Andreas Cadhalpun wrote: [...] > * E: embedded-library: I don't understand this one: >Does it complain about libavfilter embedding libavfilter? >Seems like a bug in lintian. It complains because it has detected a copy of libavfilter in a package which is none of the ones it knows that are the "source" of it. So arguably, yes, it's a bug. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140045.01046.geiss...@debian.org
Bug#729203: Packaging for FFmpeg avoiding conflicts with libav
On Sat, Feb 22, 2014 at 11:18 AM, Andreas Cadhalpun
wrote:
> Hi Antoine,
>
>
> On 22.02.2014 18:56, Antoine Beaupr=E9 wrote:
>>
>> On 2014-02-22 12:39:20, Andreas Cadhalpun wrote:
>>> The ffmpeg package does not provide qt-faststart to avoid a conflict
>>> with libav-tools.
>>
>>
>> Fair enough - there could be a qt-faststart binary package which could
>> conflict with libav-tools.
>
>
> Upstream thinks qt-faststart is not used very often nowadays and there ar=
e
> not many differences between the ffmpeg and the libav version. So anyone =
who
> needs qt-faststart can install libav-tools. I don't see a need for a
> qt-faststart binary package, but if there were bugs in the libav version
> that are not in the ffmpeg version, we could create a qt-faststart packag=
e.
IIRC FFmpeg qt-faststart is faster than Libav because of
http://git.videolan.org/?p=3Dffmpeg.git;a=3Dcommitdiff;h=3Df4d9148fe282879b=
9fcc755767c9c04de9ddbcfa.
>
>
>>> I'm not sure if this package will build on every architecture, because =
I
>>> can't test that.
>>
>>
>> Maybe an upload to experimental could test that? :)
>
>
> I intended to suggest this first, but unfortunately something in
> experimental is broken, which leads to a test failure of ffmpeg, more
> specifically the test acodec-flac fails in experimental.
> It doesn't fail in unstable and testing, so an upload to unstable should =
be
> fine.
> But if it fails to build on some architecture, it will not enter testing,=
so
> there should be no problem in uploading to unstable.
>
>
>>> I fixed most of the lintian problems, but some remain:
>>>
>>>* E: debian-watch-file-pubkey-file-is-missing:
>>> This is a bug in lintian [2].
>>>* E: embedded-library: I don't understand this one:
>>> Does it complain about libavfilter embedding libavfilter?
>>> Seems like a bug in lintian.
>>
>>
>> Not sure about those.
>
>
> Well, the first is a bug in lintian due to the transition from
> debian/upstream-signing-key.pgp to debian/upstream/signing-key.{asc,pgp},
> discussed on debian-devel recently.
> The second is a mystery to me.
Does the libav package has those warnings?
>
>
>>>* W: manpage-has-errors-from-man:
>>> I don't know how to fix the manpages. Can someone help?
>>
>>
>> I had the manpage errors as well, I think we can ignore those for now.
>
>
> I figured this as well, but maybe someone knows how to fix it.
That is upstream problem. See e.g. ffmpeg/doc/ffmpeg.texi ll. 805 [1].
>
>
>>> With this package, users can install either ffmpeg or libav-tools and
>>> developers can either depend on lib*-ffmpeg-dev or on lib*-dev and
>>> everyone should be happy.
>>
>>
>> That would be awesome.
>
>
> Exactly my opinion. ;)
> By the way, of course users can also install both ffmpeg and libav-tools =
and
> also packages build against ffmpeg and other packages build against libav=
.
Yay! I didn't think of a way good enough like that.
>
>
>>> Adrian, do you agree that this is sane?
>>>
>>> If the security team is not willing to support both, they can ask the T=
C
>>> to decide which one to use, but this does not prevent an upload of
>>> FFmpeg.
>>
>>
>> I don't see why security would complain: as things stand there are
>> hundreds of security issues that have been fixed in ffmpeg (see the
>> Google audit) which have not been fixed in libav... It seems to me
>> ffmpeg is only more secure than libav at this point...
>
>
> Previously, Moritz M=FChlenhoff from the security team voiced his concern=
s
> about having to apply security fixes for both [1]:
> "But we still try to minimise such cases as much as possible. And for
> libav/ffmpeg this simply isn't managable at all due to the huge stream
> of security issues trickling in. We need definitely need to pick one
> solution only."
>
> I do not share these concerns, as there are e.g. mysql and mariadb happil=
y
> coexisting, but then again, I'm not on the security team.
>
> But should they decide that it will not be possible to support both packa=
ges
> for security updates, your argumentation would clearly favor ffmpeg over
> libav, probably leading to the removal of libav from the archive.
> From my point of view this would be wrong, as I think the users and
> developers should decide for themselves, which package they want to use, =
and
> preventing one from being distributed in Debian only produces a great amo=
unt
> of dissatisfaction and unhappiness among the users and developers.
Thank you so much for all your work!
[1] http://git.videolan.org/?p=3Dffmpeg.git;a=3Dblob;f=3Ddoc/ffmpeg.texi;h=
=3D1244cc4e031a26536f6f3587e50a00114adc8e85;hb=3DHEAD#l805
--
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/CA+Yu1_UP=GkCc26MOmgY-sNXp1GmC9gXec6E=x+jzmjnsbp...@mail.gmail.com
Bug#729203: Packaging for FFmpeg avoiding conflicts with libav
Hi Antoine,
On 22.02.2014 18:56, Antoine Beaupré wrote:
On 2014-02-22 12:39:20, Andreas Cadhalpun wrote:
>> Thus I have started from scratch and packaged FFmpeg 2.1.3 [1] (see
>> attached debian.tar.xz).
>
> Awesome!
;)
I have taken care to avoid conflicts with libav as far as possible, but
the development files have to conflict, as it is really no good idea to
build against both ffmpeg and libav at the same time.
You mean the -dev libraries?
Yes.
The ffmpeg package does not provide qt-faststart to avoid a conflict
with libav-tools.
Fair enough - there could be a qt-faststart binary package which could
conflict with libav-tools.
Upstream thinks qt-faststart is not used very often nowadays and there
are not many differences between the ffmpeg and the libav version. So
anyone who needs qt-faststart can install libav-tools. I don't see a
need for a qt-faststart binary package, but if there were bugs in the
libav version that are not in the ffmpeg version, we could create a
qt-faststart package.
I'm not sure if this package will build on every architecture, because I
can't test that.
Maybe an upload to experimental could test that? :)
I intended to suggest this first, but unfortunately something in
experimental is broken, which leads to a test failure of ffmpeg, more
specifically the test acodec-flac fails in experimental.
It doesn't fail in unstable and testing, so an upload to unstable should
be fine.
But if it fails to build on some architecture, it will not enter
testing, so there should be no problem in uploading to unstable.
I fixed most of the lintian problems, but some remain:
* E: debian-watch-file-pubkey-file-is-missing:
This is a bug in lintian [2].
* E: embedded-library: I don't understand this one:
Does it complain about libavfilter embedding libavfilter?
Seems like a bug in lintian.
Not sure about those.
Well, the first is a bug in lintian due to the transition from
debian/upstream-signing-key.pgp to
debian/upstream/signing-key.{asc,pgp}, discussed on debian-devel recently.
The second is a mystery to me.
* W: manpage-has-errors-from-man:
I don't know how to fix the manpages. Can someone help?
I had the manpage errors as well, I think we can ignore those for now.
I figured this as well, but maybe someone knows how to fix it.
With this package, users can install either ffmpeg or libav-tools and
developers can either depend on lib*-ffmpeg-dev or on lib*-dev and
everyone should be happy.
That would be awesome.
Exactly my opinion. ;)
By the way, of course users can also install both ffmpeg and libav-tools
and also packages build against ffmpeg and other packages build against
libav.
Adrian, do you agree that this is sane?
If the security team is not willing to support both, they can ask the TC
to decide which one to use, but this does not prevent an upload of FFmpeg.
I don't see why security would complain: as things stand there are
hundreds of security issues that have been fixed in ffmpeg (see the
Google audit) which have not been fixed in libav... It seems to me
ffmpeg is only more secure than libav at this point...
Previously, Moritz Mühlenhoff from the security team voiced his concerns
about having to apply security fixes for both [1]:
"But we still try to minimise such cases as much as possible. And for
libav/ffmpeg this simply isn't managable at all due to the huge stream
of security issues trickling in. We need definitely need to pick one
solution only."
I do not share these concerns, as there are e.g. mysql and mariadb
happily coexisting, but then again, I'm not on the security team.
But should they decide that it will not be possible to support both
packages for security updates, your argumentation would clearly favor
ffmpeg over libav, probably leading to the removal of libav from the
archive.
From my point of view this would be wrong, as I think the users and
developers should decide for themselves, which package they want to use,
and preventing one from being distributed in Debian only produces a
great amount of dissatisfaction and unhappiness among the users and
developers.
I think this package is ready for upload, but I'm neither DD nor DM, so
I can't do this.
I would be hesistant in doing so, considering the controversy, but if we
reach consensus here, i'd be happy to sponsor it.
As I understand it, the whole controversy here was about a conflict
between FFmpeg and libav due to having the same sonames. My packaging
avoids this, so the only remaining issue raised so far is the security
teams concern.
But if you have some time to review my packaging, I would be grateful
for any comments/improvements.
Best regards,
Andreas
1: https://lists.debian.org/debian-devel/2014/02/msg00668.html
--
To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debia
Bug#739819: O: libfinance-quote-perl -- Perl module for retrieving stock quotes from a variety of sources
package: wnpp I currently lack the skills to properly maintain this package, the latest upstream release has a test failure and i don't know perl.
Bug#739816: O: mailping
Package: wnpp Severity: normal I'm orphaning the package 'mailping' which can measure email round trip times in a munin setup. I have only done a single upload to fix a number of issues, and no urgent problems have been reported since. However, it packaging can probably use some modernisation and I'm orphaning it because I don't use it myself anymore. The package description: mailping - monitor email service availability and functioning Monitor email service availability and functioning. Tests the whole route from SMTP submission to local delivery, not just whether an SMTP server accepts TCP connections. Multiple email servers can be tested by creating a remote alias that points back to a local address, and sending test emails to it. The results of this monitoring are available as graphs via Munin plugins, and can be connected to Nagios to send alerts when the test emails no longer get delivered, or if the delivery takes too long. I'm Ccing the munin maintainers since there may be an interesting party among them for adopting the package. -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140222180804.7925.14883.reportbug@localhost.localdomain
Bug#729203: Packaging for FFmpeg avoiding conflicts with libav
On 2014-02-22 12:39:20, Andreas Cadhalpun wrote: > Hi all, > > I have looked at the packaging provided by Antoine and it seems - no > offense intended - a little bit messy. Hehe, none taken. To my defense, I did that in about an hour, using Marillat's packages... :) > Thus I have started from scratch and packaged FFmpeg 2.1.3 [1] (see > attached debian.tar.xz). Awesome! > I have taken care to avoid conflicts with libav as far as possible, but > the development files have to conflict, as it is really no good idea to > build against both ffmpeg and libav at the same time. You mean the -dev libraries? > The ffmpeg package does not provide qt-faststart to avoid a conflict > with libav-tools. Fair enough - there could be a qt-faststart binary package which could conflict with libav-tools. > The libraries are build with --enable-raise-major, which bumps the > sonames by 100 to get i.e. libavcodec155, thus avoiding conflicts. > Note that there is also --enable-incompatible-libav-abi that would allow > packages build against libav to be used with the ffmpeg library, but > upstream thinks this would not work the other way round as well. And I > think there wouldn't be too much use for FFmpeg libraries that can only > be used as a drop in replacement the libav ones, but not to compile > programs. Makes sense. > As the libav development packages are called libavcodec-dev etc., FFmpeg > has to use different names and I chose libavcodec-ffmpeg-dev and so on. I guess that makes sense... > I'm not sure if this package will build on every architecture, because I > can't test that. Maybe an upload to experimental could test that? :) > Any build failures could probably be sorted out by disabling some > features for some architectures, as I enabled as many features as > possible for building on linux-amd64, as long as the result is still > GPLv2 licensed. (Only four codecs are GPLv3.) Makes sense as well. > I fixed most of the lintian problems, but some remain: > > * E: debian-watch-file-pubkey-file-is-missing: >This is a bug in lintian [2]. > * E: embedded-library: I don't understand this one: >Does it complain about libavfilter embedding libavfilter? >Seems like a bug in lintian. Not sure about those. > * W: manpage-has-errors-from-man: >I don't know how to fix the manpages. Can someone help? I had the manpage errors as well, I think we can ignore those for now. > * I: no-symbols-control-file: >If anyone wants to create one, feel free to do so. > > With this package, users can install either ffmpeg or libav-tools and > developers can either depend on lib*-ffmpeg-dev or on lib*-dev and > everyone should be happy. That would be awesome. > Adrian, do you agree that this is sane? > > If the security team is not willing to support both, they can ask the TC > to decide which one to use, but this does not prevent an upload of FFmpeg. I don't see why security would complain: as things stand there are hundreds of security issues that have been fixed in ffmpeg (see the Google audit) which have not been fixed in libav... It seems to me ffmpeg is only more secure than libav at this point... > I think this package is ready for upload, but I'm neither DD nor DM, so > I can't do this. I would be hesistant in doing so, considering the controversy, but if we reach consensus here, i'd be happy to sponsor it. > Rogério, Jackson are you willing to review my packaging and then > upload/maintain it? I can help e.g. rebuilding reverse-dependencies for > future transitions and similar stuff. > > In fact, If have rebuild the 109 reverse build-dependencies of src:libav > simply exchanging lib*-dev with lib*-ffmpeg-dev and 59 build > successfully, only 50 FTBFS (similarly many fail building with libav 10 > [3], probably due to the same reasons [4]). > Most failures are due to missing AVCODEC_MAX_AUDIO_FRAME_SIZE and > CodecID. Only two packages check for a version smaller than 100 and thus > fail to configure. > > I hope FFmpeg will be back in Debian soon. Good work, cheers! A. -- We have no friends but the mountains. - Kurdish saying pgpPs93E49Gzp.pgp Description: PGP signature
Bug#739815: RFA: signing-party -- Various OpenPGP related tools
Package: wnpp Severity: normal We request an adopter for the signing-party package. There's currently a number of co-maintainers but the majority of them have indicated to have no time to contribute a lot to the package. The package is an interesting collection of tools and in the BTS there's a number of useful patches and reports that need to be evaluated and where relevant, applied to the package. Since the team is also upstream there's a lot of flexibility and freedom to make changes that you see fit. The packaging is currently in svn but a move to another vcs if so preferred is perfectly fine. The package description is: signing-party is a collection for all kinds of PGP/GnuPG related things, including tools for signing keys, keyring analysis, and party preparation. . * caff: CA - Fire and Forget signs and mails a key * pgp-clean: removes all non-self signatures from key * pgp-fixkey: removes broken packets from keys * gpg-mailkeys: simply mail out a signed key to its owner * gpg-key2ps: generate PostScript file with fingerprint paper strips * gpgdir: recursive directory encryption tool * gpglist: show who signed which of your UIDs * gpgsigs: annotates list of GnuPG keys with already done signatures * gpgparticipants: create list of party participants for the organiser * gpgwrap: a passphrase wrapper * keyanalyze: minimum signing distance (MSD) analysis on keyrings * keylookup: ncurses wrapper around gpg --search * sig2dot: converts a list of GnuPG signatures to a .dot file * springgraph: creates a graph from a .dot file Let me know if there are any questions. Cheers, Thijs -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140222174337.7773.73170.reportbug@localhost.localdomain
Bug#729203: Packaging for FFmpeg avoiding conflicts with libav
Hi all, I have looked at the packaging provided by Antoine and it seems - no offense intended - a little bit messy. Thus I have started from scratch and packaged FFmpeg 2.1.3 [1] (see attached debian.tar.xz). I have taken care to avoid conflicts with libav as far as possible, but the development files have to conflict, as it is really no good idea to build against both ffmpeg and libav at the same time. The ffmpeg package does not provide qt-faststart to avoid a conflict with libav-tools. The libraries are build with --enable-raise-major, which bumps the sonames by 100 to get i.e. libavcodec155, thus avoiding conflicts. Note that there is also --enable-incompatible-libav-abi that would allow packages build against libav to be used with the ffmpeg library, but upstream thinks this would not work the other way round as well. And I think there wouldn't be too much use for FFmpeg libraries that can only be used as a drop in replacement the libav ones, but not to compile programs. As the libav development packages are called libavcodec-dev etc., FFmpeg has to use different names and I chose libavcodec-ffmpeg-dev and so on. I'm not sure if this package will build on every architecture, because I can't test that. Any build failures could probably be sorted out by disabling some features for some architectures, as I enabled as many features as possible for building on linux-amd64, as long as the result is still GPLv2 licensed. (Only four codecs are GPLv3.) I fixed most of the lintian problems, but some remain: E: ffmpeg source: debian-watch-file-pubkey-file-is-missing W: ffmpeg: manpage-has-errors-from-man usr/share/man/man1/ffmpeg-all.1.gz 1267: warning [p 13, 2.5i, div `an-div', 0.2i]: can't break line W: ffmpeg: manpage-has-errors-from-man usr/share/man/man1/ffmpeg-filters.1.gz 273: warning [p 2, 9.2i]: can't break line W: ffmpeg: manpage-has-errors-from-man usr/share/man/man1/ffmpeg.1.gz 1267: warning [p 13, 2.5i, div `an-div', 0.2i]: can't break line W: ffmpeg: manpage-has-errors-from-man usr/share/man/man1/ffplay-all.1.gz 9728: warning [p 87, 11.8i]: can't break line W: ffmpeg: manpage-has-errors-from-man usr/share/man/man1/ffprobe-all.1.gz 10045: warning [p 73, 2.2i]: can't break line W: ffmpeg: manpage-has-errors-from-man usr/share/man/man1/ffserver-all.1.gz 9745: warning [p 85, 15.5i]: can't break line E: libavfilter103: embedded-library usr/lib/x86_64-linux-gnu/libavfilter.so.103.90.100: libavfilter I: libavfilter103: no-symbols-control-file usr/lib/x86_64-linux-gnu/libavfilter.so.103.90.100 E: libavdevice155: embedded-library usr/lib/x86_64-linux-gnu/libavdevice.so.155.5.100: libavdevice I: libavdevice155: no-symbols-control-file usr/lib/x86_64-linux-gnu/libavdevice.so.155.5.100 E: libpostproc152: embedded-library usr/lib/x86_64-linux-gnu/libpostproc.so.152.3.100: libpostproc I: libpostproc152: no-symbols-control-file usr/lib/x86_64-linux-gnu/libpostproc.so.152.3.100 I: libavcodec155: no-symbols-control-file usr/lib/x86_64-linux-gnu/libavcodec.so.155.39.101 I: libswscale102: no-symbols-control-file usr/lib/x86_64-linux-gnu/libswscale.so.102.5.101 E: libavutil152: embedded-library usr/lib/x86_64-linux-gnu/libavutil.so.152.48.101: libavutil I: libavutil152: no-symbols-control-file usr/lib/x86_64-linux-gnu/libavutil.so.152.48.101 I: libavformat155: no-symbols-control-file usr/lib/x86_64-linux-gnu/libavformat.so.155.19.104 I: libswresample100: no-symbols-control-file usr/lib/x86_64-linux-gnu/libswresample.so.100.17.104 * E: debian-watch-file-pubkey-file-is-missing: This is a bug in lintian [2]. * E: embedded-library: I don't understand this one: Does it complain about libavfilter embedding libavfilter? Seems like a bug in lintian. * W: manpage-has-errors-from-man: I don't know how to fix the manpages. Can someone help? * I: no-symbols-control-file: If anyone wants to create one, feel free to do so. With this package, users can install either ffmpeg or libav-tools and developers can either depend on lib*-ffmpeg-dev or on lib*-dev and everyone should be happy. Adrian, do you agree that this is sane? If the security team is not willing to support both, they can ask the TC to decide which one to use, but this does not prevent an upload of FFmpeg. I think this package is ready for upload, but I'm neither DD nor DM, so I can't do this. Rogério, Jackson are you willing to review my packaging and then upload/maintain it? I can help e.g. rebuilding reverse-dependencies for future transitions and similar stuff. In fact, If have rebuild the 109 reverse build-dependencies of src:libav simply exchanging lib*-dev with lib*-ffmpeg-dev and 59 build successfully, only 50 FTBFS (similarly many fail building with libav 10 [3], probably due to the same reasons [4]). Most failures are due to missing AVCODEC_MAX_AUDIO_FRAME_SIZE and CodecID. Only two packages check for a version smaller than 100 and thus fail to configure.
Processed: limit package to wnpp, tagging 739463
Processing commands for cont...@bugs.debian.org: > #libsharyanto-file-util-perl (0.56-1) unstable; urgency=low > # > # * Initial Release (Closes: #739463) > # > limit package wnpp Limiting to bugs with field 'package' containing at least one of 'wnpp' Limit currently set to 'package':'wnpp' > tags 739463 + pending Bug #739463 [wnpp] ITP: libsharyanto-file-util-perl -- SHARYANTO's module of file related utilities Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 739463: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739463 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.139308975316116.transcr...@bugs.debian.org
Processed: ITA: nqc -- Not Quite C compiler for LEGO Mindstorms RCX
Processing commands for cont...@bugs.debian.org: > owner 697553 ! Bug #697553 [wnpp] RFA: nqc -- Not Quite C compiler for LEGO Mindstorms RCX Owner recorded as Slavko . > retitle 697553 ITA: nqc -- Not Quite C compiler for LEGO Mindstorms RCX Bug #697553 [wnpp] RFA: nqc -- Not Quite C compiler for LEGO Mindstorms RCX Changed Bug title to 'ITA: nqc -- Not Quite C compiler for LEGO Mindstorms RCX' from 'RFA: nqc -- Not Quite C compiler for LEGO Mindstorms RCX' > thanks Stopping processing here. Please contact me if you need assistance. -- 697553: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697553 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.139308646527295.transcr...@bugs.debian.org
Bug#697553: ITA: nqc -- Not Quite C compiler for LEGO Mindstorms RCX
owner 697553 ! retitle 697553 ITA: nqc -- Not Quite C compiler for LEGO Mindstorms RCX thanks Hi, i am wiling to maintain the package, i have new package prepared to upload ;-) regards -- Slavko http://slavino.sk signature.asc Description: PGP signature
Processed: sipvicious: changing back from ITP to RFP
Processing commands for cont...@bugs.debian.org: > retitle 479308 RFP: sipvicious -- Tools to audit SIP based VoIP systems Bug #479308 [wnpp] ITP: sipvicious -- Tools to audit SIP based VoIP systems Changed Bug title to 'RFP: sipvicious -- Tools to audit SIP based VoIP systems' from 'ITP: sipvicious -- Tools to audit SIP based VoIP systems' > noowner 479308 Bug #479308 [wnpp] RFP: sipvicious -- Tools to audit SIP based VoIP systems Removed annotation that Bug was owned by Victor Seva . > thanks Stopping processing here. Please contact me if you need assistance. -- 479308: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479308 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.c.139308629626008.transcr...@bugs.debian.org
Bug#479308: sipvicious: changing back from ITP to RFP
retitle 479308 RFP: sipvicious -- Tools to audit SIP based VoIP systems noowner 479308 thanks -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAAgy_VnP9ve8aD900_0OaM=flfaen21ymlntbzgbhyzbnhx...@mail.gmail.com
Bug#692465: status
I have a slightly updated version in git://github.com/barak/aiccu.git Barring objections I will upload it to a delayed queue. I would warmly welcome co-maintainers. (The easiest way to do this would be to just send a pull request with yourself added to Uploaders: in debian/control.) The main pending issues as I see them: - proper integration into "network manager", right now it comes up but the gnome icon stays "three dots" instead of "UP!" - any tweaks needed for systemd integration. - sixxs now allows username/tunnel as the user id, with the ability to set a per-tunnel password. The could be integrated. - when there is more than one tunnel available, it is not always properly set in aiccu.conf, requiring manual editing. --Barak. -- Barak A. Pearlmutter Hamilton Institute & Dept Comp Sci, NUI Maynooth, Co. Kildare, Ireland http://www.bcl.hamilton.ie/~barak/ -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/87mwhj5dea@cs.nuim.ie
Bug#650836: marked as done (RFP: sshdfilter -- ssh brute force attack blocker)
Your message dated Sat, 22 Feb 2014 13:25:56 +0100 with message-id <8761o7fi5n@gkar.ganneff.de> and subject line close it has caused the Debian Bug report #650836, regarding RFP: sshdfilter -- ssh brute force attack blocker 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.) -- 650836: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=650836 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wnpp Severity: wishlist * Package name: sshdfilter Version : 1.5.7 Upstream Author : Richard Gregory * URL : http://www.csc.liv.ac.uk/~greg/sshdfilter/ * License : GNU General Public License Programming Lang: Pperl Description : ssh brute force attack blocker sshdfilter blocks the frequent brute force attacks on ssh daemons, it does this by directly reading the sshd logging output (or syslog output) and generating iptables (or ipfw) rules, the process can be quick enough to block an attack before they get a chance to enter any password at all. -- ilf Über 80 Millionen Deutsche benutzen keine Konsole. Klick dich nicht weg! -- Eine Initiative des Bundesamtes für Tastaturbenutzung signature.asc Description: Digital signature --- End Message --- --- Begin Message --- upstream homepage dead, close the rfp. (also, fail2ban exists) -- bye, Joerg I wouldn't call it a registry, though. How about "link farm"? :) hard links, hard links with a link link here and a link link there here a link, there a link, everywhere a link link--- End Message ---
Processed: Re: Bug#739762: RFP: umtsmon -- graphical program for connecting cellphones or gsm-modems to the internet
Processing control commands: > reassign -1 wnpp Bug #739762 [umtsmon] Umtsmon - graphical programm for connecting cellphones or gsm-modems to the internet Warning: Unknown package 'umtsmon' Bug reassigned from package 'umtsmon' to 'wnpp'. No longer marked as found in versions 0.9. Ignoring request to alter fixed versions of bug #739762 to the same values previously set > retitle -1 RFP: umtsmon -- graphical program for connecting cellphones or > gsm-modems to the internet Bug #739762 [wnpp] Umtsmon - graphical programm for connecting cellphones or gsm-modems to the internet Changed Bug title to 'RFP: umtsmon -- graphical program for connecting cellphones or gsm-modems to the internet' from 'Umtsmon - graphical programm for connecting cellphones or gsm-modems to the internet' -- 739762: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739762 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-wnpp-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/handler.s.b739762.139307058826057.transcr...@bugs.debian.org
