Dear mentors,
I am looking for a sponsor for my package "yaskkserv".
* Package name: yaskkserv
Version : 0.3.8-1
Upstream Author : Tadashi Watanabe <[EMAIL PROTECTED]>
* URL : http://umiushi.org/~wac/yaskkserv/
* License : GPL2
Section : utils
It bui
hi,
Thank you for your comments.
On Thu, May 24, 2012 at 3:33 PM, gregor herrmann wrote:
>> The library has already been removed from the archive, you will need
>> to reintroduce it, meaning you need an ITP.
>>
>> The existing packaging can be found on snapshot.d.o:
>>
>> http://snapshot.debian.
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "mysqltuner".
* disclaimer *
This is not a hijacking. I've contacted current maintainer (CC-ing),
and kindly replied as welcome taking over.
So, I think this RFS will save our trouble (to orpha
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "bzr-email"
* Package name: bzr-email
Version : 0.0.1~bzr58-1
Upstream Author : Canonical Ltd
* URL : https://launchpad.net/bzr-email
* License : GPL-2+
hi,
I've explored RC bugs list, and consider helping to close this:
http://bugs.debian.org/cgi-bin/bugreport.cgi?archive=no&bug=668209
It seems that videolan binary package depends on old (build-time) xulrunner,
and needs to be recompiled against current xulrunner.
So, there is no need to touch t
hi,
On Fri, Jun 29, 2012 at 1:20 AM, Andrew Starr-Bochicchio
wrote:
> I'm sending this on to the pkg-bazaar list. Would you be interested in
> maintaining this as part of that team?
Does the team needs some help?
Though I'm not a skilled python developer, bzr packaging is important
for me to use
hi,
Thanks for your mentoring.
On Thu, Jun 28, 2012 at 8:30 PM, Arno Töll wrote:
> you do not need to prepare binNMU "patch". A binNMU is built from the
> same source package and thus does not need a patch at all. Just someone
> who triggers a rebuild.
>
> See [1] for instructions to request a b
hi,
Thanks for your time,
On Wed, Jul 11, 2012 at 8:58 PM, Bart Martens wrote:
> Looking at this package:
> http://mentors.debian.net/package/bzr-email
> Version:0.0.1~bzr58-1
> Uploaded: 2012-06-28 00:14
>
> How was bzr-email_0.0.1~bzr58.orig.tar.gz created ?
> http://www.debian.o
hi,
On Thu, Jul 12, 2012 at 12:22 AM, Bart Martens wrote:
> I meant to suggest this part of developers-reference :
>
> Detailed information on how the repackaged source was obtained, and on
> how
> this can be reproduced should be provided in debian/copyright.
OK (I assumed that its D
hi,
On Fri, Jul 20, 2012 at 9:42 PM, Thibaut Paumard
wrote:
> package sponsorship-requests
> user sponsorship-reque...@packages.debian.org
> usertags 679344 not-fit-for-wheezy
> Now that the freeze has started, this package is not fit for wheezy.
> During freeze, it is generally better to upload
hi,
On Sat, Jul 21, 2012 at 4:12 PM, Bart Martens wrote:
> The package at mentors is no longer there. What happened ?
This package is NEW, and there is no hope to be included in wheezy.
So, as suggested, I try to tag this bug as not-for-wheezy and delete package
from mentors.
# but I failed to
hi,
Thank you for reviewing this package!
On Sun, Jul 22, 2012 at 3:48 AM, Bart Martens wrote:
> I found this in debian/copyright :
>
> Source: branch from http://launchpad.net/bzr-email and hand-packed
> by "tar cf - | gzip -9".
>
> That's not really "detailed information". I figured
hi,
On Mon, Jul 23, 2012 at 8:36 PM, Bart Martens wrote:
>> (adding also DMUA):
>> - DM-Upload-Allowed.
>
> Did you agree that with someone who is going to sponsor this ?
No. That is simply my intent, means "I want to add DMUA: yes", and
I hope it would also reviewed to be or not to be.
In
Dear mentors,
I am looking for a sponsor for the new version 1.8.77-1
of orphaned package "qdbm".
It builds these binary packages:
libqdbm++-dev - QDBM Database Libraries for C++ [development]
(transitional packa
libqdbm-dev - QDBM Database Libraries [development]
libqdbm-java - QDBM Database Lib
Dear mentors,
I am looking for a sponsor for the new version 1.4.13-1
of orphaned package "hyperestraier".
It builds these binary packages:
hyperestraier - a full-text search system for communities
libestraier-dev - a full-text search system Libraries [development]
libestraier-java - Hyper Estrai
Dear mentors,
I am looking for a sponsor for my package "goldencheetah".
* Package name: goldencheetah
Version : 2.0.0-1
Upstream Author : Sean Rhea
* URL : http://goldencheetah.org/
* License : GPL2
Section : misc
It builds these binary packages:
g
hi,
I'm trying to upload a package to incoming queue as DM, but it fails.
> Reject Reasons:
> lur...@gmail.com is not in Maintainer or Uploaders of source package yaskkserv
I'm sure that what tutorial says
(http://wiki.debian.org/DebianMaintainer/Tutorial):
1) DMUA: yes
2) my key is in debian-m
hi,
Thanks for your replies!
On Tue, Jul 26, 2011 at 9:06 PM, Ryan Kavanagh wrote:
> Have you tried replying to the email and asking ftp-masters what went
> wrong? I had a similar issue last week and they told me that the issue
> was caused by a space before the comma in the Uploaders field of a
hi,
Thanks for your comment.
On Fri, Aug 12, 2011 at 10:05 PM, Keith Lawson wrote:
>> Don't use libqdbm15. Upstream might (and probably will!) use such SONAME
>> for their own purposes in the future.
>>
>> Are there actually any packages in Debian using gdbm symbols provided by
>> libqdbm? If th
hi,
On Sat, Aug 13, 2011 at 11:57 PM, Satoru KURASHIKI wrote:
> I guess there is no PHP code which using GDBM code. If there is, they
> had falled into troubles after php switched to link from gdbm to qdbm, because
> PHP source package also doesn't include hovel.h.
>
> I thin
hi,
Thank you checking it!
On Mon, Jul 29, 2013 at 9:07 PM, wrote:
> ruby-serverspec: Newer version (0.7.2) available.
> debian/control: don't you use anonscm.debian.org repository?
>
I'm considering to use github as its repository, so will do (after
I could deal with it using git-buildpackage
hi,
On Mon, Jul 29, 2013 at 10:55 AM, Nobuhiro Iwamatsu wrote:
> I just upload this package.
>
Thanks sponsoring it!
regards,
--
KURASHIKI Satoru
hi,
On Thu, Nov 7, 2013 at 10:58 PM, wrote:
> uploaded.
>
Thanks!
regards,
--
KURASHIKI Satoru
hi,
On Fri, Dec 20, 2013 at 6:15 PM, wrote:
> checked and uploaded.
>
Thanks!
regards,
--
KURASHIKI Satoru
hi,
On Wed, Dec 25, 2013 at 7:13 AM, Nobuhiro Iwamatsu wrote:
> Hi,
>
> I just upload this package.
>
Thanks!
regards,
--
KURASHIKI Satoru
hi,
On Wed, Dec 25, 2013 at 9:14 AM, Satoru KURASHIKI wrote:
> debian/control:
>> You are using obsolete field. You can use upstream-contact instead
>> of maintainer
>> and upstream-name instead of name.
>>
>
>
debian/changelog?
>
s/changelog/copyright/
orz
regards,
--
KURASHIKI Satoru
hi,
On Wed, Dec 25, 2013 at 7:08 AM, Nobuhiro Iwamatsu wrote:
> Hi,
>
> I checked your package.
>
Thanks for reviewing,
>
> debian/control:
> You are using obsolete field. You can use upstream-contact instead
> of maintainer
> and upstream-name instead of name.
>
debian/changelog?
I've up
hi,
On Thu, Dec 26, 2013 at 1:27 PM, Nobuhiro Iwamatsu wrote:
> >> debian/changelog?
> >
> >
> > s/changelog/copyright/
> >
> > orz
> >
>
> yes, sorry.
> And I just uploaded.
>
Thanks.
regards,
--
KURASHIKI Satoru
hi,
On Tue, Jan 7, 2014 at 9:26 AM, Russ Allbery wrote:
> Antonio Terceiro writes:
>
> > Our goal is to remove ruby1.8 and switch to ruby2.0 as the default,
> > ASAP, so it would be nice if you started building extensions for 1.9.1
> > and 2.0 (only).
>
> Okay, thanks. I haven't attempted a bu
hi,
On Tue, Jan 7, 2014 at 8:02 PM, Antonio Terceiro wrote:
> If you drop the binary packages from the control file and upload, the
> old binaries should go away automatically.
Thanks for your comment!
> > Are there any considerations? -- I'm sure they have no rdepends.
>
> Not having rdepend
hi,
On Sun, Mar 30, 2014 at 2:58 AM, Hilko Bengen wrote:
> I have looked at revision 0.20-1 and I'd be happy to upload your
> package.
>
Thanks for your interest :-)
> About the Lintian warnings (binary-without-manpage): I noticed that
> /usr/bin/plsense actually contains some help. Using Pod
Package: sponsorship-requests
Severity: wishlist
User: debian-de...@debian.or.jp
Usertags: debianjp
Control: block 743022 by -1
Dear mentors,
I am looking for a sponsor for my package "python-social-auth"
* Package name: python-social-auth
Version : 0.1.23-1
Upstream Autho
hi,
On Mon, Nov 25, 2013 at 4:06 PM, KURASHIKI Satoru wrote:
> * Package name: plsense
>Version : 0.10+git20131030-1
I've uploaded updated plsense (0.3.1-1) to mentors.
http://mentors.debian.net/package/plsense
dget -x http://mentors.debian.net/debian/pool/main/p/plsense/plsens
hi,
On Wed, Oct 22, 2014 at 9:54 PM, wrote:
> uploaded.
Thank you!
regards,
--
KURASHIKI Satoru
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/cam0xxk-b1ghu
hi,
Thank you reviewing.
On Fri, Oct 24, 2014 at 11:40 AM, wrote:
> this is application package, so ruby- prefix removed package name
> "serverspec-runner" is suitable.
>
> Naming of ruby packages
> https://wiki.debian.org/Teams/Ruby/Packaging#Naming_of_ruby_packages
According to guideline, It
hi,
On Fri, Oct 24, 2014 at 11:06 AM, wrote:
> uploaded.
Thanks!
regards,
--
KURASHIKI Satoru
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
https://lists.debian.org/cam0xxk8qcwtrxz
hi,
On Fri, Oct 24, 2014 at 12:18 PM, wrote:
> "serverspec" is mainly used as a library (framework), not as an application,
> so "ruby-serverspec" is suitable package name for it.
> naming unification is not much important, i think.
OK, I've changed package name, and re-upload to mentors.d.o. (
hi,
Thanks for reviewing!
On Wed, Jan 21, 2015 at 8:56 PM, wrote:
> - d/copyright: copyright holder is not only "Best Practical Solutions"
>but also Audrey Tang .
> - d/docs: maybe missing.
I've fixed them and re-uploaded to mentors.
> - d/p/01-fix-plugindir.patch: where comes from?
I pi
hi,
On Mon, Jan 26, 2015 at 11:13 AM, wrote:
> describe its origin somewhere (changelog, README.Debian, etc.)
> you should add new entry about debian/patches/01-fix-plugindir.patch
> and describe its origin here. of cource, this patch's license stays GPL-2.
Sorry for late, I've fixed these iss
39 matches
Mail list logo
