On 30/10/15 15:29, Alec Leamas wrote:
On 30/10/15 12:45, Ghislain Vaillant wrote:
Just my 2 cents here but quoting d-mentors FAQ [1]:
"There are cases where upstream ships a tarball which already contains a
debian directory. This is undesirable, even if you're upstream yourself
or can commit
On 30/10/15 12:45, Ghislain Vaillant wrote:
> Just my 2 cents here but quoting d-mentors FAQ [1]:
>
> "There are cases where upstream ships a tarball which already contains a
> debian directory. This is undesirable, even if you're upstream yourself
> or can commit there. Keep the released tarballs
Your message dated Fri, 30 Oct 2015 15:17:30 + (UTC)
with message-id <148785.8189966.1446218250936.javamail.ya...@mail.yahoo.com>
and subject line Re: Bug#803437: RFS: pickleshare -- File system based database
that uses Python pickles
has caused the Debian Bug report #803437,
regarding RFS
Great to see activity going and please pardon me staying silent on this
issue ;)
Cheers everyone!
--
Yaroslav O. Halchenko
Center for Open Neuroscience http://centerforopenneuroscience.org
Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755
Phone: +1 (603) 646-9834
Just my 2 cents here but quoting d-mentors FAQ [1]:
"There are cases where upstream ships a tarball which already contains a
debian directory. This is undesirable, even if you're upstream yourself
or can commit there. Keep the released tarballs (used as .orig.tar.gz)
and the debian directory s
and please note: there is currently an RC bug open against the package.
you might want to help fixing that bug as a start.
cheers,
G
Il Venerdì 30 Ottobre 2015 12:14, Gianfranco Costamagna
ha scritto:
BTW if you really think as upstream that the package is in a bad state, and the
maintain
BTW if you really think as upstream that the package is in a bad state, and the
maintainer are not answering to mails
please contact MIA team
https://wiki.debian.org/Teams/MIA
and based on the issues on the current version (e.g. does the current debian
version has serious/security bugs?)
you ca
On 30/10/15 09:51, Gianfranco Costamagna wrote:
> Hi Alec,
>
>>
>> I'm not seeking any argument as to why the Debian packages are still
>> 0.9.0. It's the debian packager's decision. Full stop.
>
>
> the argument might be: we were in the freeze because of jessie release at
> that time,
> so no
On 30/10/15 09:51, Leopold Palomo-Avellaneda wrote:
> El Divendres, 30 d'octubre de 2015, a les 09:34:09, Alec Leamas va escriure:
>> Dear list,
>>
>> I'm the upstream LIRC [2] maintainer. We are currently in the 0.9.4
>> cycle which tentatively will be released around Christmas. The debian
>> off
wonderful,
and BTW don't forget to subscribe to the package
(in the pts page on the bottom there is a subscribe by mail box)
this way you will be notified on bugs, and prevent the package from
disappearing again.
(well, first you need to make it enter unstable again :p)
cheers,
G.
Il Vener
Hi Tim,
>Hmm, I'm not really sure what you mean with that, but alright.
well, I started packaging in 2013 and I didn't provide good packages on the
first tries.
(actually I'm still doing packaging mistakes)
You seem to be a better packager than me, and you told you are on your first
packagin
Hi Alec,
(can't answer for the maintainers, just giving my personal pinion)
>This is my first contact with the Debian community. I might be doing all
>sorts of errors, including sending a questionable message to the wrong
>list. Just tell me, I'll listen.
it is fine by me
>I'm the upstream LI
El Divendres, 30 d'octubre de 2015, a les 09:34:09, Alec Leamas va escriure:
> Dear list,
>
> This is my first contact with the Debian community. I might be doing all
> sorts of errors, including sending a questionable message to the wrong
> list. Just tell me, I'll listen.
>
> I'm the upstream L
Dear list,
This is my first contact with the Debian community. I might be doing all
sorts of errors, including sending a questionable message to the wrong
list. Just tell me, I'll listen.
I'm the upstream LIRC [2] maintainer. We are currently in the 0.9.4
cycle which tentatively will be released
Control: owner -1 !
Control: tags -1 moreinfo
Hi, the packaging looks good to me, hovewer a typo in packaging is preventing
python3-path from
being added to the python3 package runtime dependencies.
I guess replacing
Depends: ${misc:Depends}, ${python:Depends}
to
Depends: ${misc:Depends}, ${pyt
Package: sponsorship-requests
Severity: wishlist
Hi,
I'm looking for a sponsor for my package:
* Package name:pickleshare
Version: 0.5
Upstream author: Ville Vainio
* URL: https://github.com/pickleshare/pickleshare
* License: Expat
Progr. lang.:Python
16 matches
Mail list logo
