Please keep me on the Cc: list, as I'm not subscribed.
Sorry :( I have to pick this up again, as I screwed up last time and
not much happened since I started this thread.
Won't bother the subsurface mailing list with debian packaging details.
On Fri, 1 Mar 2013, Christian PERRIER wrote:
>
> > Ol
Package: wnpp
Severity: wishlist
Owner: Christopher Baines
* Package name: ruby-dbf
Version : 2.0.3
Upstream Author : Keith Morrison
* URL : http://github.com/infused/dbf
* License : Expat
Programming Lang: Ruby
Description : small fast Ruby library fo
Package: wnpp
Severity: wishlist
Owner: "Siim P�der"
* Package name: estonianidcard
Version : 3.7.0:
Upstream Author : ria
* URL : http://www.ria.ee/
* License : LGPL 2.1
Programming Lang: metapackage
Description : Metapackage installing all the packa
On 01/03/2013 00:13, Cristian Ionescu-Idbohrn wrote:
> On Thu, 28 Feb 2013, Robert Wolfe wrote:
>>
>> Um, forgot about me already, hmm? :)
>
> But, of course not. Do you want to be Cc:ed?
>
>> And yes, libdivecomputer-3.0.1 in .DEB format
>
> That should probably be:
>
> subsurface-3.0.1
Package: wnpp
Severity: wishlist
Owner: "Siim Põder"
* Package name: esteidcerts
Version : 3.7.0
Upstream Author : RIA
* URL : http://www.ria.ee/
* License : LGPL 2.1
Programming Lang: certificates
Description : Estonian ID card root, intermediate and
Package: wnpp
Severity: wishlist
Owner: Christopher Baines
* Package name: ruby-georuby
Version : 2.0.0-1
Upstream Author : Guilhem Vellut
* URL : http://georuby.rubyforge.org/
* License : Expat
Programming Lang: Ruby
Description : Ruby data holder for
Package: wnpp
Severity: wishlist
Owner: "Siim Põder"
* Package name: esteidpkcs11loader
Version : 3.7.0
Upstream Author : RIA
* URL : http://www.ria.ee/
* License : LGPL 2.1
Programming Lang: javascript
Description : Loads pkcs#11 module for web authe
> The maintainer seems MIA since June 2012, not responding to bug
> reports nor direct mails.
> The two most recent upstream releases not packaged.
Why would this be a reason to *remove* a package? Especially after
such a short time. The package hasn't even been orphaened.
I have seen packages in
Quoting Cristian Ionescu-Idbohrn (cristian.ionescu-idbo...@axis.com):
> Yes, I finally found that list (it's pkg-running-devel, isn't it?) and I
> had a look. Sadly, it looks more like a spam-box than a development
> mailinglist. Can anything be done about that? I'd gladly join that list
> if t
On 03/03/2013 12:51 AM, Wouter Verhelst wrote:
> On Thu, Feb 28, 2013 at 11:07:22AM +0100, Stefano Zacchiroli wrote:
>> On Thu, Feb 28, 2013 at 10:39:26AM +0100, Daniel Pocock wrote:
>>> Has anybody had experience controlling access to git repositories, for
>>> example, to give users access but pre
On 03/01/2013 02:20 AM, Daniel Pocock wrote:
>
> DD access is also an `all or nothing' scenario, and it is tightly
> controlled in other ways.
>
> What I was anticipating is how we can provide more access for upstreams
> and other non-DDs using the guest account mechanism or potentially some
> kind
On Sun, Mar 3, 2013 at 11:21 PM, Thomas Goirand wrote:
> So yes, I would think having a safe, backup of Alioth is important.
> Now, what worries me is that I didn't read any of the Alioth admins
> explaining what is currently in production. I've searched, and the
> only info I found was hosted pro
On Sun, 3 Mar 2013, Sylvestre Ledru wrote:
>
> As a Debian Developer and as a professional diver, I am interested to
> help on this.
That sounds great. Thanks for volunteering.
> I have been in touch with Khalid to help him on this and he replied:
> "No problem for to co-maintaince
>
> I'm sorry
On Sun, 3 Mar 2013, John Paul Adrian Glaubitz wrote:
>
> > The maintainer seems MIA since June 2012, not responding to bug
> > reports nor direct mails.
> > The two most recent upstream releases not packaged.
>
> Why would this be a reason to *remove* a package? Especially after
> such a short time
Hi,
Sorry to answer only now... I was busy with my work. I think I can update the
package soon.
Sincerely,
Le 3 mars 2013 à 18:36, Cristian Ionescu-Idbohrn
a écrit :
> On Sun, 3 Mar 2013, John Paul Adrian Glaubitz wrote:
>>
>>> The maintainer seems MIA since June 2012, not responding to bug
Joost,
On 03/01/2013 09:51 AM, Joost Yervante Damad wrote:
>Package name: python-v8
> Version: 1.0-preview-r446
> Upstream Author: Xiaohai Lu
> URL: http://code.google.com/p/pyv8/
> License: APL2.0
> Description: python interface for the v8 javascript engine
I
Hi,
On 03/03/2013 08:33 PM, Dirk Hohndel wrote:
Would you consider adding one of the active contributors to Subsurface
as a co-maintainer? This is currently a really fast moving project
(3.0.2 will come out tonight or tomorrow, 3.1 is planned for next month)
and it might be easier to have someon
Khalid El Fathi writes:
> Hi,
>
> Sorry to answer only now... I was busy with my work. I think I can update the
> package soon.
That's great news.
Would you consider adding one of the active contributors to Subsurface
as a co-maintainer? This is currently a really fast moving project
(3.0.2 wi
On 03/03/2013 08:51 PM, Dirk Hohndel wrote:
I'd also be happy to review and sponsor any uploads.
We have several people who offered to step up, a couple of them are
copied on this email...
Great. Just in case ;).
PS: would it be useful for me to include the Debian packaging files in
the git
John Paul Adrian Glaubitz writes:
>
> On 03/03/2013 08:33 PM, Dirk Hohndel wrote:
>> Would you consider adding one of the active contributors to Subsurface
>> as a co-maintainer? This is currently a really fast moving project
>> (3.0.2 will come out tonight or tomorrow, 3.1 is planned for next mon
On Sun, 3 Mar 2013, John Paul Adrian Glaubitz wrote:
>
> The license issue was just an example (hence the braces). The reasoning is
> that the Debian packaging is supposed to be independent of upstream,
> especially since we cannot always follow upstream, during a freeze, for
> example.
> Assume we
On 03/03/2013 10:35 PM, Cristian Ionescu-Idbohrn wrote:
On Sun, 3 Mar 2013, John Paul Adrian Glaubitz wrote:
The license issue was just an example (hence the braces). The reasoning is
that the Debian packaging is supposed to be independent of upstream,
especially since we cannot always follow u
John Paul Adrian Glaubitz writes:
> The license issue was just an example (hence the braces). The reasoning
> is that the Debian packaging is supposed to be independent of upstream,
> especially since we cannot always follow upstream, during a freeze, for
> example.
That makes sense.
> Assume
Hello,
Cython converts a Python-like source code into .c or .cpp, which can
then be compiled into a Python extension (as .so) with a C compiler. The
Cython generated C file contains lots of glue code and helper functions
that presumably may change from Cython version to Cython version.
If a debi
Package: wnpp
Severity: wishlist
Owner: Victor Vasiliev
* Package name: python-autobahn
Version : 0.5.14
Upstream Author : Tavendo GmbH
* URL : http://autobahn.ws/python
* License : Apache 2.0
Programming Lang: Python
Description : WebSocket/WAMP implem
On 03/04/2013 03:37 AM, John Paul Adrian Glaubitz wrote:
> A great place for maintaining the packaging for Debian is github, for
> example.
Many DDs, including myself, think it's better to host Debian stuff on
Debian infrastructure (that is: alioth.debian.org), and that the
problem with platforms s
Hi Nikolaus,
Nikolaus Rath wrote:
> If a debian package uses Cython in its build process, does it need to
> declare Built-Using: cython?
I don't think typical licenses require that, no.
The policy text could use a lot of help in this area. See
http://bugs.debian.org/688251 if you have ideas fo
27 matches
Mail list logo
