Hi,
I solved the conflict and uploaded a new source package to mentors.
Sorry,
Snark on #debian-python
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "node-mocha-lcov-reporter"
* Package name: node-mocha-lcov-reporter
Version : 1.2.0-1
Upstream Author : Steven Looman
* URL : https://github.com/StevenLooma
Hi,
wait, there's a conflict with the git repository...
Snark on #debian-python
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "testpath"
* Package name: testpath
Version : 0.3+dfsg-1
Upstream Author : Jupyter Development Team
* URL : https://github.com/jupyter/testpath
* License
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "pickleshare"
* Package name: pickleshare
Version : 0.7.2-1
Upstream Author : Ville Vainio
* URL : https://github.com/pickleshare/pickleshare
* License
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "ptyprocess"
* Package name: ptyprocess
Version : 0.5.1-1
Upstream Author : Thomas Kluyver
* URL : https://github.com/pexpect/ptyprocess
* License
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for the package "twinkle":
git clone https://anonscm.debian.org/git/pkg-voip/twinkle.git
cd twinkle && pristine-tar checkout
../twinkle_1.9.0+git20160321.0.64a0816+dfsg.orig.tar.xz
For verification,
On 13-05-2016 11:46, Adam Borowski wrote:
>> On 10-05-2016 02:43, Lucas Castro wrote
>>> I am looking for a sponsor for my package "lsm"
>>>
>>> * Package name: lsm
>>> Upstream Author : Mika Ilmaranta
>>> * URL : http://lsm.foobar.fi/
>>>
>>> dget -x
>>> https://mentors.d
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for a new version of emacs-buttercup.
Buttercup is an alternative framework for writing test suites for Emacs
Lisp addons that various addons are adopting in preference or in
addition to the ERT testing frame
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for an update to dh-elpa. It fixes two bugs
introduced in the previous upload.
* Package name: dh-elpa
Version : 0.0.21
Upstream Author : David Bremner & Sean Whitton
* URL : http
Hi,
>Isn't I'm supposed to raise the version number? or is "+nmu1" enough?
I'm not sure, but in fact dch --nmu is not raising it, so I guess
1.8.2+nmu1 is fine, so the maintainer can still bump and release an NMU
acknowledge
called 1.8.3
>It part of the fix, but not needed to fix #818540 (a
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package ws-butler.
This package provides ws-butler-mode and ws-butler-global-mode. Upon
saving a file in Emacs, these modes delete trailing whitespace on lines
of the buffer that have been edited.
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package ebib.
ebib is a useful editor for .bib files in Emacs. It integrates with
RefTeX and LaTeX-mode to easily add bibliographic references to your
documents.
I intend to maintain this as part o
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package parsebib.
I am packaging this library as a dependency of ebib, another ITP of
mine. I intend to maintain it as part of the pkg-emacsen team.
* Package name: parsebib
Version :
Hi again G :)
> 1) why 1.8.3+nmu1 and not 1.8.2+nmu1?
Isn't I'm supposed to raise the version number? or is "+nmu1" enough?
> 2) why UNRELEASED? please set unstable
I didn't noticed it.
> "* Validate deb file with sha256sum." <-- isn't this part of the fix for bug
> #818540?
It part of the fix
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package smex.
> Smex is a M-x enhancement for Emacs. Built on top of Ido, it provides
> a convenient interface to your recently and most frequently used
> commands.
Smex is a very widely used Emacs
Your message dated Fri, 13 May 2016 19:44:06 + (UTC)
with message-id <1811360997.3276704.1463168646682.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#824209: RFS: path.py/8.2.1+dfsg-1
has caused the Debian Bug report #824209,
regarding RFS: path.py/8.2.1+dfsg-1
to be marked as done.
T
Your message dated Fri, 13 May 2016 19:46:16 + (UTC)
with message-id <858957668.3193131.1463168776372.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#824208: RFS: node-jsesc/1.0.0-1
has caused the Debian Bug report #824208,
regarding RFS: node-jsesc/1.0.0-1
to be marked as done.
This m
control: owner -1 !
control: tags -1 moreinfo
Hi, some questions about versioning and changelog:
1) why 1.8.3+nmu1 and not 1.8.2+nmu1?
2) why UNRELEASED? please set unstable
"* Validate deb file with sha256sum." <-- isn't this part of the fix for bug
#818540?
the other stuff LGTM, I hope to s
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "path.py"
* Package name: path.py
Version : 8.2.1+dfsg-1
Upstream Author : Mikhail Gusarov
* URL : https://github.com/jaraco/path.py
* License : Expa
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "node-jsesc"
* Package name: node-jsesc
Version : 1.0.0-1
Upstream Author : Mathias Bynens
* URL : http://mths.be/jsesc
* License : Expat
Section
Your message dated Fri, 13 May 2016 17:16:04 +0200
with message-id <20160513151604.ga1...@angband.pl>
and subject line uploaded
has caused the Debian Bug report #823668,
regarding RFS: twofish/0.3-5
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is no
> On 10-05-2016 02:43, Lucas Castro wrote
> > I am looking for a sponsor for my package "lsm"
> >
> > * Package name: lsm
> > Upstream Author : Mika Ilmaranta
> > * URL : http://lsm.foobar.fi/
> >
> > dget -x
> > https://mentors.debian.net/debian/pool/main/l/lsm/lsm_1.0.4-1.
Hi Lucio,
On 05/11/2016 12:28 PM, Gianfranco Costamagna wrote:
>> >So the next step will be to join the multimedia-team?
>
> please join it now, and put VCS fields under your package.
> (and ask me to create the repository if you want one)
>
> I see some packages under pkg-multimedia umbrella ha
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "pepperflashplugin-nonfree":
* Package name : pepperflashplugin-nonfree
Version : 1.8.3+nmu1
Upstream Author : Bart Martens
* URL : http://wiki.debian.org/Pepp
Hi Ghislain,
simply let the source package of pyzo build a transitional dummy package
with the name iep.
See https://wiki.debian.org/Renaming_a_Package
Best,
Tobias
On 05/13/2016 10:52 AM, Ghislain Vaillant wrote:
> Dear all,
>
> I am the package maintainer of iep and pyzo, two Python IDEs targ
Hello Ghislain,
>I wanted to get your opinion on how to best handle the transition
> from iep to pyzo. I would like everyone currently using iep to
> automatically transit to pyzo via a package update, so that I can
> safely ask iep to be removed from the archive.>
I'd suggest method 2:
https:
Dear all,
I am the package maintainer of iep and pyzo, two Python IDEs targeted
the scientific audience. Pyzo is the official successor of iep, meaning
the latter won't be maintained upstream anymore in favour of the
former. In terms of version numbers, the upstream developers started
Pyzo (now a
Hi Paul,
thanks for your quick reply.
[...]
> Interesting. Personally if I were upstream I'd drop the curl method and
> go with pip but I understand it is a simple and thus useful hack.
So would I, but I respect upstream's wishes and there was also a user
who preferred the simple, stand-alone sc
Your message dated Fri, 13 May 2016 07:42:37 + (UTC)
with message-id <1255851459.2480125.1463125357816.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#824161: RFS: pyfr/1.4.0-2
has caused the Debian Bug report #824161,
regarding RFS: pyfr/1.4.0-2
to be marked as done.
This means that y
30 matches
Mail list logo
