Bug#860005: RFS: fortune-zh/2.2

2017-04-10 Thread lumin
Package: sponsorship-requests
Severity: normal

  Dear mentors,

  I am looking for a sponsor for my package "fortune-zh"

 * Package name: fortune-zh
   Version : 2.2
   Upstream Author : myself
 * URL :  https://anonscm.debian.org/cgit/chinese/fortune-zh.git
 * License : GPL-3+
   Section : games

  It builds those binary packages:

fortune-zh - Chinese Data files for fortune (dummy transitional package)
 fortunes-zh - Chinese Data files for fortune

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

  https://mentors.debian.net/package/fortune-zh


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

dget -x 
https://mentors.debian.net/debian/pool/main/f/fortune-zh/fortune-zh_2.2.dsc

  More information about hello can be obtained from

http://debomatic-amd64.debian.net/distribution#experimental/fortune-zh/2.2/buildlog

  Changes since the last upload:

fortune-zh (2.2) experimental; urgency=medium

  * Substitute the replacement Chiense characters with the original one.
There is still a character remains to be fixed, as said in d/TODO.
(Closes: #850905).
  * Rename binary package "fortune-zh" to "fortunes-zh" since the other
fortune cookie packages are named as "fortunes-*". The binary package
"fortune-zh" is now a dummy transitional package.
  * New lintian overrides for fortune-zh.



Bug#860005: RFS: fortune-zh/2.2

2017-04-10 Thread Gianfranco Costamagna
control: owner -1 !
control: tags -1 moreinfo

>  I am looking for a sponsor for my package "fortune-zh"
(Reading database ... 15451 files and directories currently installed.)

Preparing to unpack /tmp/fortunes-zh_2.2_all.deb ...
Unpacking fortunes-zh (2.2) ...
dpkg: error processing archive /tmp/fortunes-zh_2.2_all.deb (--unpack):
trying to overwrite '/usr/games/fortune-zh', which is also in package 
fortune-zh 2.1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Preparing to unpack /tmp/fortune-zh_2.2_all.deb ...
Unpacking fortune-zh (2.2) over (2.1) ...
Errors were encountered while processing:
/tmp/fortunes-zh_2.2_all.deb


G.



Bug#860005: RFS: fortune-zh/2.2

2017-04-10 Thread Lumin
Oops, the file '/usr/games/fortune-zh' is moved from "fortune-zh" to
"fortunes-zh".
Should I add conflict: fortune-zh (<= 2.1) for binary package
fortunes-zh to fix this?

:-)

On 10 April 2017 at 07:23, Gianfranco Costamagna
 wrote:
> control: owner -1 !
> control: tags -1 moreinfo
>
>>  I am looking for a sponsor for my package "fortune-zh"
> (Reading database ... 15451 files and directories currently installed.)
>
> Preparing to unpack /tmp/fortunes-zh_2.2_all.deb ...
> Unpacking fortunes-zh (2.2) ...
> dpkg: error processing archive /tmp/fortunes-zh_2.2_all.deb (--unpack):
> trying to overwrite '/usr/games/fortune-zh', which is also in package 
> fortune-zh 2.1
> dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
> Preparing to unpack /tmp/fortune-zh_2.2_all.deb ...
> Unpacking fortune-zh (2.2) over (2.1) ...
> Errors were encountered while processing:
> /tmp/fortunes-zh_2.2_all.deb
>
>
> G.



-- 
Best,
Lumin



Bug#860005: RFS: fortune-zh/2.2

2017-04-10 Thread Lumin
Hi, uploaded new source package to mentors.

With changes:

fortunes-zh: Breaks: fortune-zh (<= 2.1)

this works for me since several upgrade/downgrade tests are successful.
Does it work for you?

On 10 April 2017 at 07:35, Lumin  wrote:
> Oops, the file '/usr/games/fortune-zh' is moved from "fortune-zh" to
> "fortunes-zh".
> Should I add conflict: fortune-zh (<= 2.1) for binary package
> fortunes-zh to fix this?
>
> :-)
>
> On 10 April 2017 at 07:23, Gianfranco Costamagna
>  wrote:
>> control: owner -1 !
>> control: tags -1 moreinfo
>>
>>>  I am looking for a sponsor for my package "fortune-zh"
>> (Reading database ... 15451 files and directories currently installed.)
>>
>> Preparing to unpack /tmp/fortunes-zh_2.2_all.deb ...
>> Unpacking fortunes-zh (2.2) ...
>> dpkg: error processing archive /tmp/fortunes-zh_2.2_all.deb (--unpack):
>> trying to overwrite '/usr/games/fortune-zh', which is also in package 
>> fortune-zh 2.1
>> dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
>> Preparing to unpack /tmp/fortune-zh_2.2_all.deb ...
>> Unpacking fortune-zh (2.2) over (2.1) ...
>> Errors were encountered while processing:
>> /tmp/fortunes-zh_2.2_all.deb
>>
>>
>> G.
>
>
>
> --
> Best,
> Lumin



-- 
Best,
Lumin



Bug#860005: RFS: fortune-zh/2.2

2017-04-10 Thread Gianfranco Costamagna
Hello,

>Oops, the file '/usr/games/fortune-zh' is moved from "fortune-zh" to
>"fortunes-zh".
>Should I add conflict: fortune-zh (<= 2.1) for binary package
>fortunes-zh to fix this?

https://wiki.debian.org/PackageTransitionG.



Bug#859235: RFS: telegram-desktop/1.0.27-1 -- official telegram messaging application

2017-04-10 Thread Коля Гурьев
In the last commit ce2dcd9 I already modified libmicrosoft-gsl-dev build 
dependency to libmsgsl-dev (according to a new name of that package, see 
#859238). Also a repo address was changed to 
https://anonscm.debian.org/git/collab-maint/telegram-desktop.git


01.04.2017 05:37, Boyuan Yang пишет:

Now that the RFS is blocked by other packages, could you please try to add
patch for #859057? The patch is tested by someone on Ubuntu and is working
well (at least on little-endian machines).


I added a patch, but I didn't test it. If it works, I'll send it to the 
upstream.



Plus, could you please add the workaround for #859172? The patch is simple but
could avoid crashing on GTK-based DEs. We need a real solution in the future.

diff --git a/debian/control b/debian/control
index 91fa74cb..ffba1455 100644
--- a/debian/control
+++ b/debian/control
@@ -29,7 +29,7 @@ Vcs-Browser: https://github.com/mymedia2/tdesktop

 Package: telegram-desktop
 Architecture: any
-Depends: ${shlibs:Depends}, ${misc:Depends}, qt5-image-formats-plugins
(>=5.5)
+Depends: ${shlibs:Depends}, ${misc:Depends}, qt5-image-formats-plugins
(>=5.5), libappindicator3-1
 Description: official telegram messaging app
  Telegram is a messaging app with a focus on speed and security, it is
  super-fast, simple and free. You can use Telegram on all your devices at the


I doubt that it's related to appindicator. And I still don't know how to 
reproduce that error. But I hope it was fixed in the new version.




Bug#853903: RFS: scap-security-guide/0.1.31-6 [ITP] -- security guides and conformity checks using SCAP standard

2017-04-10 Thread phil

On 2017-03-31 18:54, Gianfranco Costamagna wrote:

Hello,


Hello !



sorry for not doing this earlier, but life happened, some
showstoppers were preventing me from uploading them and somebody else
sponsored it.
(and new packages can't go in Stretch, so during freeze there is no 
real hurry

to upload them)

However (even if I didn't upload the package), I would like to see
something fixed:

[...]


Thanks for the report. I've just updated the package taking your remarks 
into account :)

I'm starting the support of the new upstream version right now.



cheers!

G.


cheers,
--
Philippe THIERRY.



Bug#859235: marked as done (RFS: telegram-desktop/1.0.27-1 -- official telegram messaging application)

2017-04-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Apr 2017 16:21:26 +0200
with message-id <20170410142124.go5baewb6htzd...@mapreri.org>
and subject line Re: Bug#859235: RFS: telegram-desktop/1.0.27-1 -- official 
telegram messaging application
has caused the Debian Bug report #859235,
regarding RFS: telegram-desktop/1.0.27-1 -- official telegram messaging 
application
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.)


-- 
859235: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=859235
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---

Package: sponsorship-requests
Severity: normal

Dear mentors,

I've prepared a package with new version of Telegram Desktop. So I am
looking for a sponsor for my package "telegram-desktop"

 * Package name: telegram-desktop
   Version : 1.0.27-1
   Upstream Author : johnprestonm...@gmail.com
 * URL : https://desktop.telegram.org
 * License : GPLv3+ with OpenSSL exception
   Section : net

It builds those binary packages:

telegram-desktop - official telegram messaging app

To access further information about this package, please visit the 
following URL: https://mentors.debian.net/package/telegram-desktop


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

dget -x 
https://mentors.debian.net/debian/pool/main/t/telegram-desktop/telegram-desktop_1.0.27-1.dsc


Changes since the last upload:

  * New upstream release
  * Refresh patchs
  * Add attribution info (closes: #859027)
  * Fix build in i386 (closes: #859058)

I see some errors on mentors site. What do they mean?

Mattia, I send to you this request because you are my sponsor for the 
previous upload.


Regards,
 Nicholas Guriev
--- End Message ---
--- Begin Message ---
On Mon, Apr 10, 2017 at 01:27:11PM +0300, Коля Гурьев wrote:
> In the last commit ce2dcd9 I already modified libmicrosoft-gsl-dev build
> dependency to libmsgsl-dev (according to a new name of that package, see
> #859238). Also a repo address was changed to
> https://anonscm.debian.org/git/collab-maint/telegram-desktop.git

Alright, uploaded.

Please avoid pushing debian/ tags unless you really know which version
is going to be uploaded (besides, in the workflow I prefer I do the
tagging if I can (they are gpg-signed tag, moreover).


About things:
* please change the build-dep on debhlper to >= 10 instead of >= 10.0
* I'm quite not convinced of the need to list all the possible
  architectures: there are ways to detect the endianess and the "bits"
  without manually listing all the known architectures...

-- 
regards,
Mattia Rizzolo

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


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


Bug#857131: RFS: fgrun/2016.4.0-0.1 [RC, NMU]

2017-04-10 Thread Mattia Rizzolo
control: tag -1 moreinfo

On Fri, Mar 10, 2017 at 07:58:52AM -0700, Sean Whitton wrote:
> Since Markus has got involved in this thread, perhaps you can organise a
> team upload, and/or add Boyuan to the Uploaders: field.

Indeed.
Markus: would you please take this RFS to its end?

> > * This package has a longstanding unfixed RC bug (FTBFS) and fell out of
> > Stretch release. With absolutely zero reverse dependency and migration 
> > blocking, I believe fgrun should be able to enter unstable even though we 
> > are 
> > in freeze now (because it wouldn't affect other packages or Stretch release 
> > at 
> > all).
> 
> Note that the release team's freeze policy does not allow this.

I'm quite positive that the release team doesn't particularly care about
what happens to sid-only packages unless as long as they don't correlate
to anything that is in stretch (i.e. a package in stretch starting to
depending on a sid-only package).


-- 
regards,
Mattia Rizzolo

GPG Key: 66AE 2B4A FCCF 3F52 DA18  4D18 4B04 3FCD B944 4540  .''`.
more about me:  https://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#845784: marked as done (RFS: dropwizard-metrics [ITP])

2017-04-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Apr 2017 17:43:56 +0200
with message-id <20170410154354.boackdqywg5pi...@mapreri.org>
and subject line Re: Bug#845784: RFS: dropwizard-metrics [ITP]
has caused the Debian Bug report #845784,
regarding RFS: dropwizard-metrics [ITP]
to be marked as done.

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

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


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

X-Debbugs-CC: debian-j...@lists.debian.org

Dear mentors,

  I am looking for a sponsor for the package "dropwizard-metrics". This 
software was originally
  packaged by Tim Potter , but does not appear to have been 
uploaded or updated
  since Nov 2014. I have updated the package to the latest upstream and 
standards versions.
  .
  Amongst other things, it is a dependancy of spymemcached, which I am 
currently investigating
  packaging.

 * Package name: dropwizard-metrics
   Version : 3.1.2-1
   Upstream Author : Coda Hale, Yammer Inc.
 * URL : http://metrics.dropwizard.io/
 * License : Apache-2.0
   Section : java

  It builds those binary packages:

libdropwizard-metrics-java - capture JVM- and application-level metrics for 
Java applications

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

  https://mentors.debian.net/package/dropwizard-metrics


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

dget -x 
https://mentors.debian.net/debian/pool/main/d/dropwizard-metrics/dropwizard-metrics_3.1.2-1.dsc

  More information about dropwizard-metrics can be obtained from 
http://metrics.dropwizard.io/.

  The package source is being managed in the pkg-java team Alioth repository:

https://anonscm.debian.org/cgit/pkg-java/dropwizard-metrics.git

  Changes since the last upload:

  * Team upload
  * New upstream release (3.1.2)
  * Minimal changes to get updated package building
+ Remove old patches
+ Add new modules to libdropwizard-metrics-java.poms, ignore modules which
  won't build.
+ Update maven.rules and maven.ignoreRules
+ Add new dependencies to debian/control
  * Use secure VCS URLs
  * Update Standards-Version from 3.9.6 to 3.9.8 (no change required)
  * Update debian/copyright
  * Use secure URL for copyright format

 -- Christopher Hoskin   Sat, 26 Nov 2016 
17:00:10 +

  Regards,
   Christopher Hoskin
--- End Message ---
--- Begin Message ---
On Wed, Jan 04, 2017 at 08:09:15AM +, Christopher Hoskin wrote:
> Since filing the RFS I've completed the DD application process, and now have
> upload rights. Prior to receiving Tim's e-mail, I went ahead and uploaded my
> package to the NEW queue [2].

Then closing this…
(it appears to have even been accepted in the meantime)

-- 
regards,
Mattia Rizzolo

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


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


Bug#858860: marked as done (RFS: arpwatch/2.1a15-3 [ITA])

2017-04-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Apr 2017 16:23:18 +
with message-id 
and subject line closing RFS: arpwatch/2.1a15-3 [ITA]
has caused the Debian Bug report #858860,
regarding RFS: arpwatch/2.1a15-3 [ITA]
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.)


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


Dear mentors,

thanks for the help you have provided so far. I am now officially
looking for a sponsor for the arpwatch package, which I intend to
adopt. I've uploaded my current packaging work to mentors:
  https://mentors.debian.net/package/arpwatch

I've done the work in git. If you want to look at the git history,
you can clone the repository from
  https://git.somlen.de/arpwatch.git
and checkout the staged-changes branch. (I have not yet tagged the
Debian version because I'm quite sure there will be some iterations
before we can actually release…)

If possible I would like to keep the "official" packaging git (Vcs-Git)
on collab-maint; I suppose once I find a sponsor, she or he can push
there for me?


Because of the changes I have made to for native systemd
integration, the upgrade needs a few manual steps (documented in
NEWS). I would be happy if someone has ideas how to avoid that.


Gianfranco suggested also asking the pkg-security-team for possible
sponsors. It would be great if one of you could have a look and provide
guidance! If team maintenance is be possible, I'd like that very
much.


Regards
Lukas Schwaighofer


pgpBtzzuO4OVb.pgp
Description: OpenPGP digital signature
--- End Message ---
--- Begin Message ---
Package arpwatch version 2.1a15-3 is in experimental now.
https://packages.qa.debian.org/arpwatch--- End Message ---


Bug#860050: RFS: xtensor/0.8.4-1

2017-04-10 Thread Ghislain Antony Vaillant
Package: sponsorship-requests
Severity: normal

Dear mentors,

* Package name: xtensor
  Version : 0.8.4-1
  Upstream Author : Johan Mabille and Sylvain Corlay
* URL : http://quantstack.net/xtensor
* License : BSD
  Section : libs

One can check out the package by visiting the following URL:

  https://anonscm.debian.org/git/debian-science/packages/xtensor.git

Changes since the last upload:

  * New upstream version 0.8.4
  * Drop the patch queue, applied upstream
  * Fix the clean target when nodoc requested
  * Change doc-base registration to Programming/C++

Best regards,
Ghis


-- System Information:
Debian Release: 9.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: amd64 (x86_64)

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



Bug#860050: RFS: xtensor/0.8.4-1

2017-04-10 Thread Ghislain Vaillant
Absolutely, thanks Anton.

Le 10 avr. 2017 9:10 PM, "Anton Gladky"  a écrit :

> Hi Ghis,
>
> I will try to sponsor this package within the next 2 days, if it is OK for
> you.
>
> Anton
>
>
> 2017-04-10 21:46 GMT+02:00 Ghislain Antony Vaillant :
> > Package: sponsorship-requests
> > Severity: normal
> >
> > Dear mentors,
> >
> > * Package name: xtensor
> >   Version : 0.8.4-1
> >   Upstream Author : Johan Mabille and Sylvain Corlay
> > * URL : http://quantstack.net/xtensor
> > * License : BSD
> >   Section : libs
> >
> > One can check out the package by visiting the following URL:
> >
> >   https://anonscm.debian.org/git/debian-science/packages/xtensor.git
> >
> > Changes since the last upload:
> >
> >   * New upstream version 0.8.4
> >   * Drop the patch queue, applied upstream
> >   * Fix the clean target when nodoc requested
> >   * Change doc-base registration to Programming/C++
> >
> > Best regards,
> > Ghis
> >
> >
> > -- System Information:
> > Debian Release: 9.0
> >   APT prefers unstable
> >   APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
> > Architecture: amd64 (x86_64)
> >
> > Kernel: Linux 4.9.0-2-amd64 (SMP w/8 CPU cores)
> > Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
> > Shell: /bin/sh linked to /bin/dash
> > Init: systemd (via /run/systemd/system)
> >
>


Bug#860050: RFS: xtensor/0.8.4-1

2017-04-10 Thread Anton Gladky
Hi Ghis,

I will try to sponsor this package within the next 2 days, if it is OK for you.

Anton


2017-04-10 21:46 GMT+02:00 Ghislain Antony Vaillant :
> Package: sponsorship-requests
> Severity: normal
>
> Dear mentors,
>
> * Package name: xtensor
>   Version : 0.8.4-1
>   Upstream Author : Johan Mabille and Sylvain Corlay
> * URL : http://quantstack.net/xtensor
> * License : BSD
>   Section : libs
>
> One can check out the package by visiting the following URL:
>
>   https://anonscm.debian.org/git/debian-science/packages/xtensor.git
>
> Changes since the last upload:
>
>   * New upstream version 0.8.4
>   * Drop the patch queue, applied upstream
>   * Fix the clean target when nodoc requested
>   * Change doc-base registration to Programming/C++
>
> Best regards,
> Ghis
>
>
> -- System Information:
> Debian Release: 9.0
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
> Architecture: amd64 (x86_64)
>
> Kernel: Linux 4.9.0-2-amd64 (SMP w/8 CPU cores)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>



Bug#857131: RFS: fgrun/2016.4.0-0.1 [RC, NMU]

2017-04-10 Thread Markus Wanner
control: tag -1 -wontfix

On 04/10/2017 05:39 PM, Mattia Rizzolo wrote:
> On Fri, Mar 10, 2017 at 07:58:52AM -0700, Sean Whitton wrote:
> Markus: would you please take this RFS to its end?

I'm rather busy with stretch issues I'd like to fix (and then there's
the day job as well...)

I take it granted there's enough interest to re-introduce fgrun to
unstable (without an unblock request, that doesn't affect stretch, and
given there's nothing to possibly upgrade in stretch, there's no need
for an upload to experimental, only).

@Boyuan: could you please:

 a) change the watch file to point to the github mirror and
release tags you found? (Or provide some other way of automatically
fetching an orig.tar.gz?)

 b) commit your changes to alioth / collab-maint (do you have access,
there?)

 c) add yourself as an uploader, I'm happy to review and sponsor
uploads of fgrun for you.

Kind Regards

Markus Wanner




signature.asc
Description: OpenPGP digital signature


Bug#854693: marked as done (RFS: tslib/1.8-1 [ITP])

2017-04-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Apr 2017 22:20:24 +
with message-id 
and subject line closing RFS: tslib/1.8-1 [ITP]
has caused the Debian Bug report #854693,
regarding RFS: tslib/1.8-1 [ITP]
to be marked as done.

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

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


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

Dear mentors,

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

* Package name: tslib
  Version : 1.5-1
  Upstream Author : [Martin Kepplinger ]
* URL : [https://github.com/kergoth/tslib]
* License : [LGPL-2.1]
  Section : embedded

It builds those binary packages:

   libts - touch screen library
libts-bin  - touch screen library utilities
libts-dbg  - touch screen library debug symbols
libts-dev  - touch screen library, development files
tsconf - touch screen library common files

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

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


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

  dget -x
https://mentors.debian.net/debian/pool/main/t/tslib/tslib_1.5-1.dsc

More information about hello can be obtained from
https://github.com/kergoth/tslib.

Changes since the last upload:

  * Initial packaging of tslib. (Closes: #845181)
  * remove man pages. they are part of the project now.
  * remove all patches. they are dealt with upstream.
  * use dh and autoreconf in rules.
  * Upload to experimental for initial testing.


Regards,
 Martin Kepplinger
--- End Message ---
--- Begin Message ---
Package tslib version 1.8-1 is in unstable now.
https://packages.qa.debian.org/tslib--- End Message ---


Bug#855537: marked as done (RFS: aiohttp-cors/0.5.0-1 ITP #855498)

2017-04-10 Thread Debian Bug Tracking System
Your message dated Mon, 10 Apr 2017 22:20:24 +
with message-id 
and subject line closing RFS: aiohttp-cors/0.5.0-1 ITP #855498
has caused the Debian Bug report #855537,
regarding RFS: aiohttp-cors/0.5.0-1 ITP #855498
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.)


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

Dear mentors,

  I am looking for a sponsor for my package "aiohttp-cors"

 * Package name: aiohttp-cors
   Version : 0.5.0-1
   Upstream Author : Vladimir Rutsky 
 * URL  : https://github.com/aio-libs/aiohttp-cors
 * License : Apache 2.0
   Section  : python

  It builds those binary packages:

python3-aiohttp-cors - Cross Origin Resource Sharing (CORS)
support for aiohttp

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

  https://mentors.debian.net/package/aiohttp-cors

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

dget -x 
https://mentors.debian.net/debian/pool/main/a/aiohttp-cors/aiohttp-cors_0.5.0-1.dsc

  More information about aiohttp-corps can be obtained from
https://github.com/aio-libs/aiohttp-cors

  Regards,
   Brandon Weeks


smime.p7s
Description: S/MIME Cryptographic Signature
--- End Message ---
--- Begin Message ---
Package aiohttp-cors version 0.5.0-1 is in unstable now.
https://packages.qa.debian.org/aiohttp-cors--- End Message ---