On May 26, 2017 12:30:17 AM EDT, Neil Williams wrote:
>On Fri, 26 May 2017 04:11:49 +
>Scott Kitterman wrote:
>
>> I don't see any way to completely resolve this before stretch
>> releases other than removing lava-server.
>
>This is a *django*
On Fri, 26 May 2017 04:11:49 +
Scott Kitterman wrote:
> I don't see any way to completely resolve this before stretch
> releases other than removing lava-server.
This is a *django* bug! There is no evidence that lava-server is
responsible for this - it just has to use
I don't see any way to completely resolve this before stretch releases other
than removing lava-server.
Scott K
___
Python-modules-team mailing list
Python-modules-team@lists.alioth.debian.org
Processing commands for cont...@bugs.debian.org:
> reopen 863267
Bug #863267 {Done: Scott Kitterman } [src:python-django]
python-django: Upgrades from jessie to stretch
Bug reopened
Ignoring request to alter fixed versions of bug #863267 to the same values
previously set
>
Processing commands for cont...@bugs.debian.org:
> found 794461 1.3.0-1
Bug #794461 {Done: Thomas Goirand } [python-mock]
RequirementParseError: Expected version spec in funcsigs; python_version<"3.3"
at ; python_version<"3.3"
Marked as found in versions python-mock/1.3.0-1.
>
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:python-feather-format
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> #
> user bts-link-upstr...@lists.alioth.debian.org
Setting user to
#
# bts-link upstream status pull for source package src:python-feather-format
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #819997 (http://bugs.debian.org/819997)
# Bug title:
binary:python-iso3166 is NEW.
binary:python3-iso3166 is NEW.
binary:python3-iso3166 is NEW.
binary:python-iso3166 is NEW.
source:python-iso3166 is NEW.
Your package has been put into the NEW queue, which requires manual action
from the ftpteam to process. The upload was otherwise valid (it had a
python-iso3166_0.8.git20170319-1_amd64.changes uploaded successfully to
localhost
along with the files:
python-iso3166_0.8.git20170319-1.dsc
python-iso3166_0.8.git20170319.orig.tar.gz
python-iso3166_0.8.git20170319-1.debian.tar.xz
python-iso3166_0.8.git20170319-1_all.deb
On Thu, 2017-05-25 at 17:41 +1000, Brian May wrote:
> Ian Campbell writes:
>
> > Yet 1.10.x is going to be in Stretch, according to [0]? If users
> > want
> > LTS then why aren't we shipping that in our upcoming stable release
> > (whether its instead of or in addition to the
On Thu, May 25, 2017 at 05:41:39PM +1000, Brian May wrote:
> Ian Campbell writes:
>
> > Yet 1.10.x is going to be in Stretch, according to [0]? If users want
> > LTS then why aren't we shipping that in our upcoming stable release
> > (whether its instead of or in addition to the
Ian Campbell writes:
> Yet 1.10.x is going to be in Stretch, according to [0]? If users want
> LTS then why aren't we shipping that in our upcoming stable release
> (whether its instead of or in addition to the latest release)?
In general the Django LTS releases occur after on
12 matches
Mail list logo