* Ole Streicher , 2013-02-12, 14:46:
http://mentors.debian.net/debian/pool/main/p/python-astropy/python-astropy_0.2~b2-1.dsc
Where can I download .orig.tar from? uscan says: "Newest version on
remote site is 0.1, local version is 0.2~b2"
debian/control contains a mixture of tabs and spaces,
Den 12. feb. 2013 16:04, skreiv Yaroslav Halchenko:
fresh entry in debian/NEWS and probably debian/changelog ?
Thanks. I've done this now, along with a friendly message upstream
begging for these changes to be handled more elegantly by the
application in the future.
Andreas
--
To UNSUBSCRIB
On Wed, Feb 13, 2013 at 12:15:00AM +0800, Thomas Goirand wrote:
> The only problem is that I quite hate SVN (mostly because I never
> learn it).
Just can use git-svn just fine:
'git svn clone' instead of 'git clone'
'git svn rebase' instead of 'git pull'
'git svn dcommit' instead of 'git push'
* Thomas Goirand , 2013-02-13, 00:15:
The only problem is that I quite hate SVN (mostly because I never learn
it). Don't you guys have plans to switch to git at some point? I've
seed that in /git/python-modules/packages there's already 3 packages.
Is it fine to switch to Git?
http://lists.ali
On 02/12/2013 11:13 PM, Dmitrijs Ledkovs wrote:
> On 12 February 2013 15:08, Dmitry Shachnev wrote:
>> Hi Thomas,
>>
>> On Tue, Feb 12, 2013 at 7:00 PM, Thomas Goirand wrote:
>>> ...
>>> So I wonder, how is the python module packaging policy? Since this
>>> module is marked as team maintained, an
On Feb 12, 2013, at 12:49 AM, Dmitrijs Ledkovs wrote:
>> Debian HPIJS and HPLIP maintainers
>>hplip
>>
>> Matthias Klose
>>python-reportlab
>>
>Does this mean that hplip & python-reportlab are now have all their
>dependenices ported to python3 and hence can also be ported? \o/
I *think*
On 12 February 2013 15:08, Dmitry Shachnev wrote:
> Hi Thomas,
>
> On Tue, Feb 12, 2013 at 7:00 PM, Thomas Goirand wrote:
>> ...
>> So I wonder, how is the python module packaging policy? Since this
>> module is marked as team maintained, and that I've been accepted in the
>> python module packag
Andreas Noteng writes:
> Hello. What is the preffered way of handling situations where a configuration
> file in ~/ needs to be deleted upon package upgrade?
There is nothing the package can do, touching files under the users home
directory is not allowed by policy (and for a very good reason).
Hi Thomas,
On Tue, Feb 12, 2013 at 7:00 PM, Thomas Goirand wrote:
> ...
> So I wonder, how is the python module packaging policy? Since this
> module is marked as team maintained, and that I've been accepted in the
> python module packaging team on Alioth, am I allowed to just refresh the
> packa
fresh entry in debian/NEWS and probably debian/changelog ?
On Tue, 12 Feb 2013, Andreas Noteng wrote:
> Hello. What is the preffered way of handling situations where a
> configuration file in ~/ needs to be deleted upon package upgrade?
> Regards
> Andreas Noteng
--
Yaroslav O. Halchenko
http:/
Hi,
Because I'm currently packaging Openstack Grizzly, which will be out
next April, I need a newer version of python-mock. So I filled:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699147
but no reply so far, and this worries me.
I haven't done the bug fillings for other python modules whic
Hello. What is the preffered way of handling situations where a
configuration file in ~/ needs to be deleted upon package upgrade?
Regards
Andreas Noteng
--
To UNSUBSCRIBE, email to debian-python-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian
Dear mentors,
I am looking for review for my package "python-astropy". I still don't
need a sponsor since the packaged version is just a beta version, with
the final release expected soon. To speed up the process, I'd however
like to start to sort out packaging problems already now.
* Package nam
13 matches
Mail list logo
