Bug#791463: Quick review

2016-03-11 Thread Pali Rohár
On Monday 07 March 2016 17:49:00 Pali Rohár wrote:
> On Monday 07 March 2016 14:31:44 Andrew Shadura wrote:
> > On 6 March 2016 at 21:16, Pali Rohár  wrote:
> > >> > But should not be cleandir part of that --buildsystem=bmake? Or
> > >> > why not?
> > >> 
> > >> You're actually very right in this, I'm going to implement that
> > >> right now.
> > > 
> > > Now I tested bmake version 20160220-2 and looks like it is
> > > working... Should I upload new version to mentors?
> > 
> > Please do.
> 
> Done. I uploaded last upstream version.

It is OK now? What else is needed?

-- 
Pali Rohár
pali.ro...@gmail.com



Bug#791463: Quick review

2016-03-11 Thread Andrew Shadura
On 11 March 2016 at 09:41, Pali Rohár  wrote:
>> > > Now I tested bmake version 20160220-2 and looks like it is
>> > > working... Should I upload new version to mentors?
>> >
>> > Please do.
>>
>> Done. I uploaded last upstream version.
>
> It is OK now? What else is needed?


Sorry, I haven't had time to have a look, busy week. I will though.

-- 
Cheers,
  Andrew



Bug#817863: marked as done (RFS: android-platform-system-core/1:6.0.1+r16-3)

2016-03-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Mar 2016 10:24:25 +
with message-id 
and subject line Bug#817863: fixed in android-platform-system-core 1:6.0.1+r16-3
has caused the Debian Bug report #817863,
regarding RFS: android-platform-system-core/1:6.0.1+r16-3
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.)


-- 
817863: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817863
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 "android-platform-system-core"

* Package name: android-platform-system-core
  Version : 1:6.0.1+r16-3
  Upstream Author : The Android Open Source Project
* URL : https://android.googlesource.com/platform/system/core
* License : Apache-2.0
  Section : devel

  It builds those binary packages:

adb   - Android Debug Bridge
 android-libadb - Library for Android Debug Bridge
 android-libadb-dev - Library for Android Debug Bridge - Development files
 android-libbacktrace - Android backtrace library
 android-libbacktrace-dev - Android backtrace library - Development files
 android-libbase - Android base library
 android-libbase-dev - Android base library - Development files
 android-libcutils - Android utils library for C
 android-libcutils-dev - Android utils library for C - Development files
 android-liblog - Android NDK logger interfaces
 android-liblog-dev - Android NDK logger interfaces - Development files
 android-libsparse - Android Sparse library
 android-libsparse-dev - Android Sparse library - Development files
 android-libutils - Android Utility Function Library
 android-libutils-dev - Android Utility Function Library - Development files
 android-libziparchive - Android zip archive library
 android-libziparchive-dev - Android zip archive library - Development files
 android-libzipfile - Transitional dummy package
 android-libzipfile-dev - Transitional dummy package
 android-platform-system-core-headers - Shared headers in AOSP
repository platform/system/core
 fastboot   - Android fastboot tool

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

  http://mentors.debian.net/package/android-platform-system-core


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

dget -x 
http://mentors.debian.net/debian/pool/main/a/android-platform-system-core/android-platform-system-core_6.0.1+r16-3.dsc

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

  Changes since the last upload:

  * Fix package name typo: android-{zipfile=>libzipfile}(-dev)


  Regards,
   Kai-Chung Yan


-- 
/*
* 殷啟聰 | Kai-Chung Yan
* 一生只向真理與妻子低頭
* Undergraduate student in National Taichung University of Education
* LinkedIn: 
* Blog: 
*/
--- End Message ---
--- Begin Message ---
Source: android-platform-system-core
Source-Version: 1:6.0.1+r16-3

We believe that the bug you reported is fixed in the latest version of
android-platform-system-core, 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 817...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Kai-Chung Yan  (supplier of updated 
android-platform-system-core 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: Sun, 06 Mar 2016 15:02:52 +0800
Source: android-platform-system-core
Binary: android-liblog android-liblog-dev android-libcutils 
android-libcutils-dev adb android-libsparse android-libsparse-dev 
android-libutils android-libutils-dev android-libziparchive 
android-libziparchive-dev android-platform-system-core-headers 
android-libbacktrace android-libbacktrace-dev android-libadb android-libadb-dev 
android-libbase android-libbase-dev fastboot android-libzipfile 
android-libzipfile-dev
Architecture: source amd64 all
Version: 1:6.0.1+r16-3
Distribution: unstable
Urgency: medium
Maintainer: Android tools Maintainer 

Changed-By: Kai-Chung Yan 
Description:
 adb- Android Debug Bridge
 android-libadb - Library for Android Debug Bridge
 android-libadb-dev - Library for A

Re: Packaging pythonpy

2016-03-11 Thread Tiago Ilieve
Hi Ben,

On 10 March 2016 at 22:19, Ben Finney  wrote:
> Not by itself. You need to run something that will actually use that
> substitution variable.
>
> By default you should be using Pybuild in new packages for Python code.
> This will bring many benefits, including interpolate the substvars for
> Python.

Following the Pybuild wiki page[1], I've added "dh-python" as a build
dependency and added the following to "debian/rules":

diff --git a/debian/rules b/debian/rules
index cc0781a..ae03e14 100755
--- a/debian/rules
+++ b/debian/rules
@@ -1,7 +1,10 @@
 #!/usr/bin/make -f

+export PYBUILD_NAME=pythonpy
+
 %:
-   dh $@ --with python2
+   dh $@ --with python2 --buildsystem=pybuild


 override_dh_auto_build:

But that doesn't changed anything. The
"python-script-but-no-python-dep" error still persists.

Am I missing something here?

> Still needed. Build dependencies are not affected by Debhelper. If the
> build depends on ‘foo’, use of Debhelper won't take away the need to
> declare “Build-Depends: foo”.

Got it.

> That directory is effectively auto-generated garbage for a Debian
> package, it needs to be cleaned.
>
> Use the ‘clean’ target to remove files you don't need. Debhelper's
> ‘dh_clean’ is useful here, see its man page.

The Python FAQ wiki page has a section about "debian/clean" and Python
eggs[2], which I was already following. What is strange is that the
upstream tarball has five files in its ".egg-info/" folder:

- dependency_links.txt
- entry_points.txt
- PKG-INFO
- SOURCES.txt
- top_level.txt

But the built package has only three:

- dependency_links.txt
- PKG-INFO
- top_level.txt

So, it looks like the original files are being properly removed, but
are created again later. Any idea about how to overcome this?

Regards,
Tiago.

[1]: https://wiki.debian.org/Python/Pybuild
[2]: https://wiki.debian.org/Python/FAQ#How_should_we_package_Python_eggs.3F

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



Bug#814852: RFS: openfst/1.5.1-1 -- weighted finite-state transducers library

2016-03-11 Thread Jakub Wilk

* Giulio Paci , 2016-03-08, 22:24:

we do seem to have an s390x buildd with only 3GB of RAM:
https://db.debian.org/machines.cgi?host=zemlinsky


So we may have a failure there. :-/


Perhaps. But with the current limits, the package would be built with 
-j1 there, so reducing parallelism further wouldn't help. Let's not 
worry about zemlinsky for now. :)


Comments in src/extensions/python/*.cc say that the files were generated 
by Cython, but I don't see their Cython sources in the tarball. :-\


--
Jakub Wilk



Bug#817804: marked as done (RFS: tinymux/2.6.5.34-1.1 NMU)

2016-03-11 Thread Debian Bug Tracking System
Your message dated Fri, 11 Mar 2016 16:25:27 +
with message-id 
and subject line closing RFS: tinymux/2.6.5.34-1.1 NMU
has caused the Debian Bug report #817804,
regarding RFS: tinymux/2.6.5.34-1.1 NMU
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.)


-- 
817804: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=817804
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: sponsorship-requests
Severity: normal [important for RC bugs, wishlist for new packages]

Dear mentors,

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

 Package name: tinymux
 Version : 2.6.5.34-1
 Upstream Author : Stephen Dennis 
 URL : http://www.tinymux.org
 License : GPL
 Section : games

It builds those binary packages:

  tinymux- text-based multi-user virtual world server

To access further information about this package, please visit the
following URL:
http://mentors.debian.net/package/tinymux


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

  dget -x 
http://mentors.debian.net/debian/pool/main/t/tinymux/tinymux_2.6.5.34-1.dsc

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

Changes since the last upload:

tinymux (2.6.5.34-1) unstable; urgency=low

  * Non-maintainer upload
  * Fix "FTBFS with GCC 6: narrowing conversion"  (Closes: #811780)
  * Fix "use autotools-dev to update config.{sub,guess} for new arches"
 (Closes: #736863)
  * Fix "[Mayhem] Bug report on tinymux: netmux crashes with exit status
139"  (Closes: #716615)
  * Fix "run dh-autoreconf to update for new architectures"  (Closes: #759448)

 -- Stephen Dennis   Thu, 10 Mar 2016 06:01:09 +


Regards,
Stephen Dennis
--- End Message ---
--- Begin Message ---
Package tinymux version 2.6.5.34-1.1 is in unstable now.
https://packages.qa.debian.org/tinymux--- End Message ---


Re: migration from non-free to main

2016-03-11 Thread Gianfranco Costamagna
Hi,

probably some overrides/new queue trips will be needed too
https://wiki.debian.org/Teams/FTPMaster

cheers,

G.




Il Venerdì 11 Marzo 2016 4:30, Ben Finney  ha 
scritto:
Jerome BENOIT  writes:

> One of my package, nayty not to mention it [1], has a new copyright
> notice [2] that is compatible now.

Great news!

The license text looks unfamiliar. Please discuss it on the
‘debian-legal’ forum to verify that this work is now DFSG-conformant.

> Is there any special procedure to follow to migrate a package from
> non-free to main ?

Set that in the ‘debian/control’ file. The generated source package will
contain the correct information for where the package is uploaded.

The first upload to “main” may need to pass through the NEW queue. You
won't need to do anything special for that to happen, but you should be
aware of it.

-- 
\ “This [Bush] Administration is not sinking. This Administration |
  `\   is soaring. If anything they are rearranging the deck chairs on |
_o__) the Hindenburg.” —Steven Colbert, 2006-04-29 |
Ben Finney



Bug#812216: RFS suspended until further notice

2016-03-11 Thread Gianfranco Costamagna
control: reopen -1

reopening
g.
On Wed, 9 Mar 2016 21:19:46 + (UTC) Gianfranco Costamagna 
 wrote:
> Control: tags -1 moreinfo
> Adjusting tags then :)
> On Wed, 9 Mar 2016 19:46:00 + Ghislain Vaillant  
> wrote:
> > Just notifying prospective sponsors to refrain for sponsoring this
> > package for now until notified otherwise please.
> > 
> > This package needs further care now that the JUCE is in the archive.
> > 
> > Cheers,
> > Ghislain
> > 
> > 
> 
> Sent from Yahoo Mail on Android



signature.asc
Description: OpenPGP digital signature


Bug#813850: RFS: amanda/3.3.8-1 -- Advanced Maryland Automatic Network Disk Archiver

2016-03-11 Thread Jose M Calhariz
One more iteration.


On 09/03/16 20:11, Mattia Rizzolo wrote:
> On Mon, Mar 07, 2016 at 09:27:20PM +, Jose M Calhariz wrote:
>> On 29/02/16 23:09, Mattia Rizzolo wrote:
>>> * guessing you are using git-buildpackage, why didn't you just
>>>   `gbp import-dsc` to import the NMU?
>> My changes are older than the NMU.  So I did not tried to import the NMU.
> umh, yes, otherwise you'd have needed to the re-apply the commits on top
> of the import.
>
>>> * the *.dirs files don't need to list directories for files installed by
>>>   other dh_* things, so I'm confident at least line 3,4,5 of
>>>   amanda-server.dirs are useless, haven't looked at the others
>> The debian/rules relies on cp and install to copy the files into the
>> directories listed in *.dirs
>> I don't like, I would prefer the format:
>>  mkdir $dir && cp $file $dir
>>
>> What you recomend?
> there are several reasons to prefer using dh_* tools to do that.
> for the basic example of `mkdir $dir && cp $file $dir` the better way to
> do it is to add a .install file with just '$file $dir' and it'll just do
> the work.
>
> That said, I'm now sure that you don't need those lines (as in, I
> removed them and it just works, after moving to dh_lintian(1)).
>
> please try to have a look at all of the things in *.dirs and see if
> really them all are needed.  there are not many install(1) or cp(1) or
> mv(1) calls that needs them (sure, there are other things that do,
> though).

I managed to remove some lines from *.dirs.

>
>>> * I'm not happy with the old style rules file, but guess I can't ask
>>>   that much in this case, and I can live well with it anyway :)
>> Thank you.  This package is being tested on my backup server for some
>> weeks.  I don't want
>> to make changes that may invalidate my tests.  The version 3.3.9 is all
>> ready available and I
>> can change the rules style for amanda 3.3.9.
> ok.
> Just, I'd love to show you that several stuff you do manually can be
> instead done by some tools that are already there since a lot of times
> and really do the job.
> * cp of config.{sub,guess}: there is dh_autotools_dev since a lot of
>   times, since mid-January there is the "native"
>   dh_update_autotools_config(1) which is also run automatically by
>   dh(1)
> * some of the stuff done in the clean target are done by
>   dh_auto_clean(1)
> * that cp ChangeLog should already be done automatically by
>   dh_installchangelogs(1)
> * all those lines to install lintian should be just done by
>   dh_lintian(1) (just rename the *.lintian to *.lintian-overrides); for
>   avoidance of doubts, this one thing I want to see changed, the other
>   can wait for the time you'll rewrite the thing :)
>
>> This is for today.
> yeah, one step at time.
>
> Some more things from d/rules:
>
> * that $(shell pwd) can be $(CURDIR)
Done
> * you should remove the config.{sub,guess} you copy over
Done
> * what's that "source diff" target?? seams some old things that does
>   nothing now, maybe it can be removed?
Done
> * do you know why dh_makeshlibs is called with --noscripts?
It silence a lintian warning "amanda-common:
postinst-has-useless-call-to-ldconfig"
> * the -l of that dh_shlibdeps should be uneeded.
Done
> * that fiddling with substvars seems to be uneeded: whilst something
>   does put amanda-common in *.substvars in shlibs:Depends, something
>   else in dpkg merges that dependency with what you already specify in
>   d/control and keeps the one more restrictive (the versioned one you
>   specify in d/control) => 4 lines less.
Done
> * on a site note, do you know that the nice thing of using variables
>   with only one letter in a makefile makes possible to just use $c
>   instead of $(c) ? :)
I don't like that and I don't like this 3 variable names, so they will
go away on next upstream release.

>
> more:
>
> * d/copyright looks outdated, at least with regards to years.  Also, I'd
>   love to see a DEP-5 compliant copyright file
I don't know how to identify what license is used on Amanda.
I don't know what license was used to create the debian package.  Should
I contact the previous
DD that worked on this?

> * may you rename d/docs to d/amanda-common.docs, just for clearity?
Done

> * please add DEP-3 compliant headers to the patches lacking it, it's
>   otherwise uneededly difficult to understand what a patch is for (and
>   also just "Description: fix blalba." is annoying, really some
>   description ought to be loger with a sequel "by changing foo to bar so
>   that blabla can do incredible stuff and so build again", but this is
>   not required for my sponsorship offer, just a nice to have in a
>   future, maybe; also I guess the newer upstream will for sure drop some
>   patches, so this may become moot soon! ;))
>
>> Tomorrow I will look into "lintian -I --pedantic"
> yes please :)
>
>
> With the fix of some lintian tags, I think this is about all I'd like
> before sponsoring this.

Kind regards
Jose M Calhariz




signature.asc
Description: O

Bug#816919: RFS: newsbeuter/2.9-1 [ITA]

2016-03-11 Thread Nikos Tsipinakis
On Fri, Mar 11, 2016 at 12:49:38AM +0100, gregor herrmann wrote:
> Will take a closer look tomorrow; a first look shows that the package
> might profit from some modernization (d/copyright in Copyright Format
> 1.0;

Done.

> dh(1) in debian/rules; migration to new dbgsym packages (cf.
> dh_strip(1)'s --dbgsym-migration)), etc.).

Done.

> lintian and blhc report:
> 
> P: newsbeuter source: no-dep5-copyright

Done.

> I: newsbeuter: spelling-error-in-binary usr/bin/newsbeuter occured occurred

Sneaked this one in the translation-fix patch.

> I: newsbeuter: hardening-no-fortify-functions usr/bin/newsbeuter
> I: newsbeuter: hardening-no-fortify-functions usr/bin/podbeuter

Fixed.

> W-dpkg-buildflags-missing|CPPFLAGS 59 (of 59) missing|

Fixed.


-- 
Best Regards,
Nikos Tsipinakis



Bug#817949: RFS: niceshaper/1.2.0-1 [ITP]

2016-03-11 Thread Mariusz Jedwabny

Package: sponsorship-requests
Severity: wishlist

Dear mentors,

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

* Package name: niceshaper
  Version : 1.2.0-1
  Upstream Author : Mariusz Jedwabny 
* URL : http://niceshaper.jedwabny.net
* License : GPL-2
  Section : net

It builds those binary packages:

  niceshaper - Dynamic Traffic Shaper

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

  http://mentors.debian.net/package/niceshaper


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

  dget -x 
http://mentors.debian.net/debian/pool/main/n/niceshaper/niceshaper_1.2.0-1.dsc

More information about niceshaper can be obtained from 
http://niceshaper.jedwabny.net.

Changes since the last upload:

niceshaper (1.2.0-1) unstable; urgency=low

  * New upstream release.

 -- Mariusz Jedwabny   Wed, 09 Mar 2016 20:35:56 +


Regards,
 Mariusz Jedwabny



Bug#813850: RFS: amanda/3.3.8-1 -- Advanced Maryland Automatic Network Disk Archiver

2016-03-11 Thread Mattia Rizzolo
On Fri, Mar 11, 2016 at 08:10:40PM +, Jose M Calhariz wrote:
> I managed to remove some lines from *.dirs.

cool.

> > * do you know why dh_makeshlibs is called with --noscripts?
> It silence a lintian warning "amanda-common:
> postinst-has-useless-call-to-ldconfig"

umh, I wonder why dh adds the trigger, then.
Well, I think I'm going to ignore this particular thing and postpone it
to the new version where several other things will change.

> > * on a site note, do you know that the nice thing of using variables
> >   with only one letter in a makefile makes possible to just use $c
> >   instead of $(c) ? :)
> I don't like that and I don't like this 3 variable names, so they will
> go away on next upstream release.

even better!

> > * d/copyright looks outdated, at least with regards to years.  Also, I'd
> >   love to see a DEP-5 compliant copyright file
> I don't know how to identify what license is used on Amanda.

The license is correctly reported on most of the headers, and in
/COPYRIGHT.  It's a MIT-like license, unluckily not Expat.
If I were you I'd probably use the name 'custom' for it.

> I don't know what license was used to create the debian package.  Should
> I contact the previous DD that worked on this?

I'm positive bdale intended to use the same license as upstream, yes,
contacting him is better.  He is usually responsive (at least via IRC).
(clearly I'm talking about bdale, I think it's safe to assume the other
are ok with that license).


Please address this thing of the copyright and then I'm good to upload
it :)

-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  http://mapreri.org  : :'  :
Launchpad user: https://launchpad.net/~mapreri  `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia  `-


signature.asc
Description: PGP signature


Bug#816919: RFS: newsbeuter/2.9-1 [ITA]

2016-03-11 Thread gregor herrmann
Control: owner -1 !
Control: tag -1 + moreinfo

On Fri, 11 Mar 2016 23:34:06 +0200, Nikos Tsipinakis wrote:

Thanks for all your work, that's really exciting, and I'm happy to
sponsor this upload.

> On Fri, Mar 11, 2016 at 12:49:38AM +0100, gregor herrmann wrote:
> > Will take a closer look tomorrow; a first look shows that the package
> > might profit from some modernization (d/copyright in Copyright Format
> > 1.0;
> Done.

The order of the paragraphs is a bit unusual; normally the "Files"
sections come before the "License" sections.
 
> > dh(1) in debian/rules; migration to new dbgsym packages (cf.
> > dh_strip(1)'s --dbgsym-migration)), etc.).
> Done.

Cool. - I just think that the newsbeuter-dbg transition package
should depend on newsbeuter-dbgsym instead of newsbeuter. (Or you can
just drop it; I see the point but so far I haven't seen any other
transition packages for debugging symbols; but it's fine for me to
keep it.)
 
> > I: newsbeuter: spelling-error-in-binary usr/bin/newsbeuter occured occurred
> Sneaked this one in the translation-fix patch.

Nice :)
 
> > I: newsbeuter: hardening-no-fortify-functions usr/bin/newsbeuter
> > I: newsbeuter: hardening-no-fortify-functions usr/bin/podbeuter
> Fixed.

Excellent!
 
So alltogether there are no real blockers for me to upload this
version; I'd just like to wait for you on a decision about the
newsbeuter-dbg package, and if you want to keep it, to change the
dependency to newsbeuter-dbgsym.

A little reformatting of d/copyright would be nice but this is just
aesthetical. And in the future, modernizing d/rules would be nice.


Cheers,
gregor

-- 
 .''`.  Homepage https://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
 : :' : Debian GNU/Linux user, admin, and developer -  https://www.debian.org/
 `. `'  Member of VIBE!AT & SPI, fellow of the Free Software Foundation Europe
   `-   NP: Flying Pickets: Space Oddity


signature.asc
Description: Digital Signature


HTTPS Only 3.1 (Request For Comment And Sponsor, Browser Security, Open Source, Python)

2016-03-11 Thread David Leo
Hi there!

The Problem: When was the last month without browser vulnerability? Ah, never.

This tiny tool can secure users' most important online assets: browser is only 
able to access HTTPS of whitelist domains.

Details:
(http://seclists.org/fulldisclosure/2016/Mar/1)

When we browse the web, top threats are:
1. Remote code execution - everything is lost
2. Man in the middle - sniffing, and tampering
3. Phishing - simple, old, and still quite useful
4. Cross site scripting - data of the vulnerable domain is lost
5. CSRF - unauthorized action

So, what if the browser can only access HTTPS of whitelist domains? With HTTPS, 
"man in the middle" is fixed. And with the whitelist, other attacks become very 
difficult, some even become impossible(such as phishing). Phishing is a huge 
headache in this era, because URLs can be hidden in legitimate redirection(such 
as t.co).

URLs:
Project Home Page - https://www.httpsonly.net/
Source Code - https://github.com/httpsonly/httpsonly

Request:
Could you please help add this tool to Debian?

Kind Regards,



Bug#817961: RFS: awesfx/0.5.1e-1 [RC] [ITA]

2016-03-11 Thread Dmitry Eremin-Solenikov
Package: sponsorship-requests
Severity: important

Dear mentors,

I am looking for a sponsor for the package "awesfx"

 * Package name: awesfx
   Version : 0.5.1e-1
   Upstream Author : Takashi Iwai 
 * URL : http://www.alsa-project.org/~tiwai/awedrv.html
 * License : GPL-2+
   Section : sound

It builds those binary packages:

awesfx - utility programs for AWE32/64 and Emu10k1 driver

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

  http://mentors.debian.net/package/awesfx


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

dget -x 
http://mentors.debian.net/debian/pool/main/a/awesfx/awesfx_0.5.1e-1.dsc

Right now package was removed from testing suite, because of RC bug #800262,
usage of deprecated debhelper compat level.

Current maintainer of awesfx (Ove Kaaven) asked to consider him MIA, so I'm 
adopting
the package.

Changes since the last upload:
  * New upstream release.
  * New maintainer.
  * Update to debhelper 9. Closes: #800262, #817311.
  * Update to standards version 3.9.6.
  * Use linux-any architecture. Closes: #745179.
  * Stop providing libawe.a, it seems nobody uses it. At least nobody
complained about missing headers for this library.
  * Provide udev rules to automatically load sound fonts.
  * Suggest soundfont packages.
  * Enable hardening of built utilities.
  * Provide doc-base files.
  * List myself as an uploader.

-- 
With best wishes
Dmitry

-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_GB.utf8, LC_CTYPE=en_GB.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)



Bug#816266: RE:Bug#816266: RFS: python-qtawesome/0.3.0-1 [ITP]

2016-03-11 Thread PICCA Frederic-Emmanuel
Hello Ghislain,

I am wondering it this python-qtawesome package should not be replace by the 
already available one [1]

python-xstatic-font-awesome.

It would be great if we could convince the spyder upstream to use the 
python-xstatic system instead of embeding third party solutions.

Cheers

Fred

https://pypi.python.org/pypi/XStatic-Font-Awesome