Your message dated Mon, 1 Aug 2016 07:14:29 + (UTC)
with message-id
<1877651163.12990155.1470035669099.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#833094: RFS: uligo/0.3-7 [RC][QA]
has caused the Debian Bug report #833094,
regarding RFS: uligo/0.3-7 [RC][QA]
to be marked as done.
Your message dated Mon, 1 Aug 2016 07:19:41 + (UTC)
with message-id <357450355.12920625.1470035981747.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#833082: RFS: fsvs/1.2.7-1 [QA]
has caused the Debian Bug report #833082,
regarding RFS: fsvs/1.2.7-1 [QA]
to be marked as done.
This mea
control: owner -1 !
control: tags -1 moreinfo
> I am looking for a sponsor for my package "vim-lastplace"
1) please use for debian copyright the same license as upstream if possible
(this makes easier to forward patches)
2) I'm not sure about the directories and installation path
│ ├── vim
Your message dated Mon, 1 Aug 2016 09:01:29 + (UTC)
with message-id
<1600392794.13103591.1470042089575.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#833100: RFS: python-schema/0.6.2-1 [ITP]
has caused the Debian Bug report #833100,
regarding RFS: python-schema/0.6.2-1 [ITP]
to be mar
2016-08-01 10:01 GMT+01:00 Gianfranco Costamagna :
> control: owner -1 !
> control: tags -1 moreinfo
>
> >I am looking for a sponsor for my package "python-schema"
>
> looks good to me, just a few typo in the source
> occured ==> occurred
>
>
Forwarded upstream here:
https://github.com/keleshe
Hi,
>Is it worth keeping a patch downstream for such a trivial fix?
I don't think it is worth a patch, lets keep patches for real bugs :)
G.
Hi.First, let's be clear. I currently do not want to have an active activity as
a Debian maintainer. I recently created a free/libre C project, and I would
like to create clean Debian packages for it, and integrate them in Debian main.
I have no problem to be the maintainer of them, but currentl
Hi,
>I would like to create 3 packages for the core part: lib (for the shared
>library object), dev (for headers), and doc (for documentation generated by
>doxygen).
maybe two binaries? I guess you need one package for each repo.
e.g.
git1 providing the lib and headers
git2 providing the core
Hi,
On 01/08/16 16:43, Gianfranco Costamagna wrote:
>> I would like to create 3 packages for the core part: lib (for the shared
>> library object), dev (for headers), and doc (for documentation generated by
>> doxygen).
>
>
> maybe two binaries? I guess you need one package for each repo.
> e.
>I'm not sure I follow. Three binary packages (lib, dev, doc) is fairly
>standard for a shared library package. I would expect each git repo to
>be a separate source package, unless they are very tightly coupled together.
that was what I meant :)
the doc can be the doxygen for the library, or so
Hi Gianfranco,
On 01.08.2016 10:38, Gianfranco Costamagna wrote:
> 1) please use for debian copyright the same license as upstream if possible
>
> (this makes easier to forward patches)
Done.
>
> 2) I'm not sure about the directories and installation path
>
> │ ├── vim-lastplace
> │ │
Your message dated Mon, 1 Aug 2016 18:55:17 + (UTC)
with message-id
<1285590481.13673923.1470077717780.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#833105: RFS: vim-lastplace/3.0.2-1 [ITP]
has caused the Debian Bug report #833105,
regarding RFS: vim-lastplace/3.0.2-1 [ITP]
to be mar
Hi,
>yes, but it seems still sometime wrong
it is good, just called "3.0.2-2"
please use -1 as versioning and dput -f on mentors until it gets accepted.
>we should be near :)
last thing: how do I enable such extension?
G.
Hi,
On 01.08.2016 22:35, Gianfranco Costamagna wrote:
> it is good, just called "3.0.2-2"
>
> please use -1 as versioning and dput -f on mentors until it gets accepted.
>
Ah ok, sorry. :-) I removed the package and uploaded it again as 3.0.2-1 .
> last thing: how do I enable such extension?
I
On 07/27/2016 03:28 AM, Sean Whitton wrote:
> I can't sponsor the package, but I hope that the following review is
> useful to you.
Thanks for your very in-depth review, it is very helpful!
> 1. You should install the examples to /usr/share/doc/yabar/examples, not
> /usr/share/yabar/examples. You
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "yuma123"
* Package name: yuma123
Version : 2.8-1
Upstream Author : Vladimir Vassilev
* URL :https://sourceforge.net/projects/yuma123
* License : BSD
S
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for the package "pam-u2f"
* Package name: pam-u2f
Version : 1.0.4-0.3
Upstream Author : Yubico AG
* URL : https://developers.yubico.com/pam-u2f/
* License : BSD-2-clau
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "chapel-minimal"
* Package name: chapel-minimal
Version : 1.13.1-1
Upstream Author : Ben Albrecht
* URL : chapel.cray.com
* License : Apache
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package "node-es6-promise"
* Package name: node-es6-promise
Version : 3.2.2+ds-1
Upstream Author : Yehuda Katz, Tom Dale, Stefan Penner and
contributors (Conversion to ES6 AP
Hello Dear,
Glad to know you from your website.
We are a professional bicycle factory in China for more than 10 years.
We manufacture bikes with good price and quality. OEM order accepted.
Kindly let me know if we could cooperate in the furture.
Thank you, looking forward to your reply.
With K
Hi,
>Ah ok, sorry. :-) I removed the package and uploaded it again as 3.0.2-1 .
usually there is no need to remove the package on mentors
>In the vim-policy[1] by the vim package team they recommend to use
>vim-addon-manager. That means, install the debian package
>vim-addon-manager (which is
21 matches
Mail list logo
