+1,11 @@
+celery (3.1.23-6) unstable; urgency=medium
+
+ * Change celeryd to depend on python-celery-common instead of python-celery.
+Closes: #858305.
+ * Add celeryd depends on lsb-base.
+
+ -- Brian May <b...@debian.org> Fri, 24 Mar 2017 17:00:36 +1100
+
celery (3.1.23-5) unstable; u
) unstable; urgency=medium
+
+ * Don't move grid.png to wrong spot in python3 package. Closes: #858811.
+
+ -- Brian May <b...@debian.org> Mon, 27 Mar 2017 18:15:43 +1100
+
djangorestframework (3.4.0-1) unstable; urgency=medium
* New upstream release.
diff -Nru djangorestframework-3.4.0/
Package: python3-djangorestframework
Version: 3.4.0-1
Severity: important
grid.png is installed here:
/usr/share/doc/python3-djangorestframework/img/grid.png
But the following file:
/usr/lib/python3/dist-packages/rest_framework/static/rest_framework/css/bootstrap-tweaks.css
Expects to find it
On Tue, Nov 11, 2014 at 11:40:56AM +1100, Brian May wrote:
> A bug report has been filled against debian-policy for a httpd-wsgi3
> virtual package for Python 3 WSGI, see #768117.
This happened years ago...
Please change the provides to use httpd-wsgi3 instead of httpd-wsgi.
--
Brian
Nish Aravamudan <nish.aravamu...@canonical.com> writes:
>> I have pushed a change through to git that will fix this on the next
>> release.
I just uploaded this to unstable. Are you able to test this?
(note I did not fix the bashism issue yet)
Thanks
--
Brian May <b...@debian.org>
Brian May <b...@debian.org> writes:
>> File "/usr/lib/python2.7/dist-packages/kombu/five.py", line 6, in
>>
>> import vine.five
>> ImportError: No module named vine.five
Just to keep this bug report up-to-date:
This particular problem is eas
ersion of kombu with an epoch in the version. However if you
have any better solutions available, I am all ears.
For example, is it possible to delete the package from the archive and
reupload the old version?
--
Brian May <b...@debian.org>
On 2017-03-24 08:36, Chris Lamb wrote:
> Oh, did I mark it as such? Apologies if so :)
No, the bug was absolutely correct - the error was my brain :-).
gt; ImportError: No module named vine.five
Just for the record, this does *not* affect the version in testing.
(which initially had me concerned because vine is not in testing)
--
Brian May <b...@debian.org>
arbitrary (unless override in the defaults file) and may be wrong for
the given project. Or may change unexpectedly. e.g. installing
python3-celery will make it default to python3.
Would be better I think if the project supplied its own init.d script.
--
Brian May <b...@debian.org>
d have started by
trying to submit a smaller change (e.g. maybe the first patch in the
series).
I don't see any response to this email.
Doesn't inspire confidence :-(
--
Brian May <b...@debian.org>
se that got lost I also filed an upstream bug
>
> http://bugs.ledger-cli.org/show_bug.cgi?id=1203
Thanks!
It looks like upstream knows about it, but considering that annoucement
was made January last year, aren't treating it as a priority.
--
Brian May <b...@debian.org>
t the moment to move
Debian to Python 3.x, as Python 2.7 is no longer being developed
anymore.
After the release of stretch I believe the plan is not to accept any new
Python 2 packages. Eventually this is going to become an RC bug as a
result of phasing out Python 2.7.
--
Brian May <b...@debian.org>
Sorry about that!
Ok, I will fix it up.
Thanks for letting me know.
--
Brian May <b...@debian.org>
Brian May <b...@debian.org> writes:
> However, more importantly, the release team is very unlikely to let a
> new upstream version into unstable.
err... Obviously I meant testing.
:-(
--
Brian May <b...@debian.org>
to unstable.
So, unfortunately, I am inclined to remmend reverting all changes on the
master branch since debian/2.1-3 for now. If you want, I can do
this. Because if any future RC bugs occur during the freeze, we need to
be able to make new releases from from the master branch for the same
ups
Santiago Vila <sanv...@debian.org> writes:
> Maybe this "only" fails shortly after February 28th, but we really want
> tests to never fail. It is possible that this package assumes one or more
> things in the following list?:
Fixed in unstable and unblock request sent:
/changelog 2016-09-28 11:05:44.0 +1000
+++ parsedatetime-2.1/debian/changelog 2017-03-11 11:46:48.0 +1100
@@ -1,3 +1,9 @@
+parsedatetime (2.1-3) unstable; urgency=medium
+
+ * Add patch to fix FTBFS error after February. Closes: #856625.
+
+ -- Brian May <b...@debian.org> Sat,
Brian May <b...@debian.org> writes:
> Ok, I got a suggestion to run the failing test by itself. It fails
> everytime. As reported in the upstream bug report.
Unblock request sent: #857429
--
Brian May <b...@debian.org>
:23.0
+1000
+++ django-pipeline-1.6.8/debian/changelog 2017-03-10 18:54:37.0
+1100
@@ -1,3 +1,9 @@
+django-pipeline (1.6.8-3) unstable; urgency=medium
+
+ * Work around for random build failures. Closes: #851722.
+
+ -- Brian May <b...@debian.org> Fri, 10 Mar 2017 18:54:37
nth is 30 days. It allows
some margin for error, so 31 days might be OK, however by the looks of
it, 28 days is not OK.
I have forwarded this upstream:
https://github.com/bear/parsedatetime/issues/215
--
Brian May <b...@debian.org>
Source: ledger
Version: 3.1.2~pre1+g3a00e1c+dfsg1-2+b1
Severity: wishlist
Apparently there is a fork with Python 3 support here:
https://github.com/afh/ledger/tree/wip/python3
This is referenced here:
https://groups.google.com/forum/#!topic/ledger-cli/C99w-79Jq8o
I am not sure what the
Brian May <b...@debian.org> writes:
> Santiago Vila <sanv...@unex.es> writes:
>
>> So I think forwarding the bug would make sense. Just tell upstream the
>> truth, namely, that you have received a bug saying the package fails
>> to build randomly.
>
&
Santiago Vila <sanv...@unex.es> writes:
> So I think forwarding the bug would make sense. Just tell upstream the
> truth, namely, that you have received a bug saying the package fails
> to build randomly.
See https://github.com/jazzband/django-pipeline/issues/622
--
Brian May <b...@debian.org>
and amavisd-milter for stretch.
libdbd-mysql-perl is fixed in testing now.
Can amavisd-new get unblocked?
Thanks
(oh amavisd-milter is a seperate package, seperate maintainer, no need
to unlock it)
--
Brian May <b...@debian.org>
Brian May <b...@debian.org> writes:
> amavisd-new has already been removed from testing. I think the chances
> of getting it back in are remote - however I have asked the release team
> - see #856067.
The release gods^h^h^h^h^h team has spoken. They say they will accept
a
bug gets fixed it
might help distribute amavisd-new some other way (maybe outside Debian).
--
Brian May <b...@debian.org>
Brian May <b...@debian.org> writes:
> Possibly only happens in Perl's tainted mode; I have asked for
> confirmation.
Actually is a fair bit more complicated then that. See:
https://github.com/perl5-dbi/DBD-mysql/issues/78#issuecomment-282425847
The fix is simple. Understanding
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Request dialog concerning amavisd-new situation.
amavisd-new has a release critical bug. #847311. The justification given
was "causes non-serious data loss" presumably because emails were
Package: libdbd-mysql-perl
Version: 4.041-1
Severity: grave
Justification: causes non-serious data loss
When reading floats from mysql, they are always read as 0.
As values are currupted and as it is the cause of a grave bug in another
package, I have set this to grave.
Possibly only happens in
Antonio Terceiro <terce...@debian.org> writes:
> Package: python3-django-celery
> Version: 3.1.17-3.1
> Severity: grave
> Forwarded: https://github.com/celery/django-celery/pull/458
> Justification: renders package unusable
Unblock request sent #855899
--
Brian May <b...@debian.org>
+1,10 @@
+django-celery (3.1.17-4) unstable; urgency=medium
+
+ * Add 0010-Fix-management-command-handling-for-django-1.10.patch to
+fix management command. Closes: #855877.
+
+ -- Brian May <b...@debian.org> Thu, 23 Feb 2017 08:10:49 +1100
+
django-celery (3.1.17-3.1) unstable; urgency=
better off asking on the amavisd-new user mailing
list, as I get the impression this is a help/support request, not a bug
report.
https://lists.amavis.org/cgi-bin/mailman/listinfo/amavis-users
--
Brian May <b...@debian.org>
Source: six
Version: 1.10.0-3
Severity: important
Please package python-six-doc. This is required so that we can fix
#852512 in python-django.
Thanks
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable'), (500, 'oldstable'), (100,
-mysql-perl, or how intrusive the
fix might be.
One thing certain however, I don't believe this bug can be fixed (or
worked around even) by changing amavisd-new.
--
Brian May <b...@debian.org>
Brian May <b...@debian.org> writes:
> From the upstream bug report it is sounding increasingly likely that
> this is a Perl bug, related to tainted mode.
>
> The upstream developer is working on getting some solid evidence to
> prove this.
A bug has now been reporte
tream developer is working on getting some solid evidence to
prove this.
--
Brian May <b...@debian.org>
Upstream has asked for some rather detailed information:
https://github.com/perl5-dbi/DBD-mysql/issues/78
The information I asked for will do for now, then we can decide if this
more extensive information is required.
--
Brian May <b...@debian.org>
dings were changed). I would like confirmation that this matches what
is installed on the LOC's system. The above commands should answer that.
--
Brian May <b...@debian.org>
tell, this documentation isn't packaged in Debian.
> 'formtools': ('https://django-formtools.readthedocs.io/en/latest/',
> None),
> 'psycopg2': ('http://initd.org/psycopg/docs/', None),
> }
I think everything else is packaged, just missing a python-six-doc
package.
--
Brian May <b...@debian.org>
Henrique de Moraes Holschuh <h...@debian.org> writes:
>> https://github.com/perl5-dbi/DBD-mysql/issues/78
>
> Thanks!
Please read the latest message on the above report...
--
Brian May <b...@debian.org>
returning valid data.
Just found this bug report:
https://github.com/perl5-dbi/DBD-mysql/issues/78
--
Brian May <b...@debian.org>
with this would be:
1. Try to reproduce the problem with upstream git.
2. Try to do a git bisect.
I am stuck on step 1.
Unfortunately the original bug report is lacking in details required to
reproduce this. e.g. the tables (structure and data) that in mysql.
--
Brian May <b...@debian.org>
Michael Fladischer <mich...@fladi.at> writes:
> Updating to 1.2.0 would solve this but the freeze is already in place, so it's
> either backporting the fix from upstream[0] or asking fo an exeption from
> release team.
Unblock request sent for backport: #854833
--
Brian May <b...@debian.org>
+
+ * Add patch to fix Django 1.10 support. Closes: #854716.
+ * Update Vcs-* headers for git repository.
+ * disable_broken_tests.patch regenerated from git-dpm but unchanged.
+
+ -- Brian May <b...@debian.org> Sat, 11 Feb 2017 08:34:43 +1100
+
django-cors-headers (1.1.0-1) unstable; urgen
s not work".
If you use the old style MIDDLEWARE_CLASSES setting, it works fine, same
as before.
The problems only occur if you want to use the new style MIDDLEWARE
setting.
I can confirm that the supplied patch soles the problem.
--
Brian May <b...@debian.org>
r way.
However, probably fare easy to get approval for one commit as opposed to
all of these:
https://github.com/ottoyiu/django-cors-headers/compare/1.1.0...1.2.0
> [0]
> https://github.com/ottoyiu/django-cors-headers/commit/870b1d9deb54ff4c1fefedc39dff02519abb32c5
I will have a l
it was removed from stretch and I don't think we can get it
back in now.
At least it should be easy to backport as required.
--
Brian May <b...@debian.org>
me.localtime(timestamp+time.timezone).tm_isdst
> ValueError: timestamp out of range for platform time_t
>
> --
> Ran 45 tests in 7.922s
>
> FAILED (errors=2)
> debian/rules:27: recipe for target 'override_dh_auto_test' failed
--
Brian May <b...@debian.org>
lly notice it anyway). If Brian doesn't beat me
> to it, I'm happy to update to 1.7.1 once it's available.
Considering the coming freeze, might be best to upload a fix before
then... If you want this in stretch that is.
--
Brian May <b...@debian.org>
rg/~sanvila/build-logs/django-pipeline/
>
> If this is really a bug in one of the build-depends, please use reassign and
> affects,
> so that this is still visible in the page for this package.
>
> The bug should be reproducible with sbuild on a single CPU virtual machine,
> provided you try enough times (as the failure happens randomly).
>
> Thanks.
>
> ___
> Python-modules-team mailing list
> python-modules-t...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/python-modules-team
--
Brian May <b...@debian.org>
D_TEST_ARGS="PYTHONPATH=. python{version}
/usr/bin/django-admin test -v3 --settings=tests.settings" dh_auto_test
Thanks!
--
Brian May <b...@debian.org>
are in soft
freeze (meaning no new packages, no re-entry, normal migrations). Don't
want to risk uploading a new package that gets into stretch and creates
RC bugs - it might mean the package fails to get into Stretch.
--
Brian May <b...@debian.org>
t schroot
and look for alternatives???
--
Brian May <b...@debian.org>
Brian May <b...@debian.org> writes:
> Not sure if I can git push to the openstack git repository, so I haven't
> done so (and I might have to redo it anyway). If I can get this working,
> I might move it to DPMT.
Ok, just building and uploading.
Note that this isn't going
If I can get this working,
I might move it to DPMT.
--
Brian May <b...@debian.org>
your next
> upload without asking for an unblock.
If somebody wants me to do a NMU of some random package that I do not
maintain, I really do need to asked before the freeze. I can't subscribe
to every bug report for every package just in case somebody might ask me
to do a NMU.
--
Brian May <b...@debian.org>
was sent to the BTS only, not me. I have a backlog right
now, will see what I can do.
--
Brian May <b...@debian.org>
at a time.
>
> We really should fix this for stretch.
Does this bug really warrant being serious? As it is we risk having this
package removed from testing. Is this justified?
--
Brian May <b...@debian.org>
}) = 0 (Timeout)
select(10, [9], [], NULL, {1, 0}) = 0 (Timeout)
select(10, [9], [], NULL, {1, 0}) = 0 (Timeout)
select(10, [9], [], NULL, {1, 0}) = 0 (Timeout)
select(10, [9], [], NULL, {1, 0}) = 0 (Timeout)
etc
Work arounds would be appreciated.
Thanks.
--
Brian May &l
Sandro Tosi <mo...@debian.org> writes:
> On Tue, 15 Dec 2015 16:40:34 +1100 Brian May <b...@debian.org> wrote:
>> Source: python-django-south
>> Version: 1.0.0-1
>> Severity: grave
>> Justification: renders package unusable
>>
>> Packa
ge
> the latest version and verify it works with django 1.10? thanks!!
Done.
--
Brian May <b...@debian.org>
Brian May <b...@debian.org> writes:
> If I try to sleep with the modem active, it sometimes causes the
> computer to enter a state where it will not sleep anymore, and it will
> not talk to the LTE modem anymore.
Looks like if I leave it for several minutes, it sometimes comes goo
Package: modemmanager
Version: 1.6.2-1
Severity: important
If I try to sleep with the modem active, it sometimes causes the
computer to enter a state where it will not sleep anymore, and it will
not talk to the LTE modem anymore.
If I downgrade to modemmanager 1.4.x it works perfectly.
If I
In the past I have found I need to set (in debian/rules):
export SETUPTOOLS_SCM_PRETEND_VERSION=$(shell cat PKG-INFO | sed -n
's/^Version: //p')
otherwise the version won't come out correctly.
--
Brian May <b...@debian.org>
ant
> libjs-* package and install a symlink to the minified file provided by
> that package, instead of another minified copy of the library.
Help to fix this appreciated. Am very short on time recently.
Thanks.
--
Brian May <b...@debian.org>
go 1.10 support regressed with changes between pre-alpha and final
release; 1.10 currently not supported.
See upstream bug at
https://github.com/carljm/django-model-utils/issues/232
--
Brian May <b...@debian.org>
he package currently FTBFS - I am assuming Django 1.10 issues
- so I won't be able to do an upload anytime soon.
Regards
--
Brian May <b...@debian.org>
eaches the archive.
No objections from me.
If you want to skip the 2 day delay, that is fine with me also.
Thanks!
--
Brian May <b...@debian.org>
Santiago Vila <sanv...@unex.es> writes:
> Hope this helps.
Hopefully the fix I just applied to git is correct and will solve this.
Not going to upload however, as I can't build due to some of the tests
failing (I think this is an unrelated issue).
--
Brian May <b...@debian.org>
Thomas Goirand <z...@debian.org> writes:
> I have sent a (one liner) fix to the Git. Can you please review it, and
> allow me to upload it (or upload it yourself)?
Please go ahead and upload.
Thanks
--
Brian May <b...@debian.org>
Package: python-factory-boy
Version: 2.7.0-2
Severity: important
Apologies if this actually is a bug in python-fake-factory, not sure.
(sid-amd64-default)root@prune:/home/brian/tree/karaage/karaage-debian# apt-get
install python3-factory-boy python-factory-boy
Reading package lists... Done
Ben Finney <ben+deb...@benfinney.id.au> writes:
> Which bug report requests the archive override for the Section of this
> package? As noted in the initial bug report:
Bug #833034
--
Brian May <b...@debian.org>
Package: ftp.debian.org
Severity: normal
See bug #832192.
a “system resource” as
> much as any other daemon that provides services to applications behind
> the scenes.
>
> The sections aren't going to fit all packages perfectly, though. If
> you can justify the package fitting some other section by functional
> description, go for it.
--
Brian May <b...@debian.org>
can be
> closed or not.
Looks fine to me
--
Brian May <br...@microcomaustralia.com.au>
system administrators, it is a deamon used
mainly by Python applications.
I looked at memcached which serves a similar role; it is in the web
section - not convinced that is correct either.
--
Brian May <b...@debian.org>
/939/commits/8b006bd7fda55e47e29412896c511c7244398f82
If so, we might need to update the ticket to say it wasn't fixed:
https://github.com/mkdocs/mkdocs/issues/938
--
Brian May <b...@debian.org>
normal team upload (not NMU).
Otherwise I can do the upload too if you want me to.
--
Brian May <b...@debian.org>
3
> Severity: wishlist
> Tags: patch
> User: reproducible-bui...@lists.alioth.debian.org
> Usertags: timestamps
> X-Debbugs-Cc: reproducible-bui...@lists.alioth.debian.org
>
> Whilst working on the "reproducible builds" effort [0], we noticed
> that python-mkdocs cou
Brian May <b...@debian.org> writes:
> I think you might be confused; these a warnings only. The build-depends
> installs the required packages.
Oh, I guess you were talking about depends on the binary packages, not
the build-depends.
Will upload after I finish doing some tests.
't think anything is
broken here or that the serious severity is justified.
--
Brian May <b...@debian.org>
inistrators selecting
> ‘python-django-extensions’ or ‘python3-django-extensions’ will receive
> the suggestion.
Was going to upload a fix for this, but opened bug #828207 instead.
--
Brian May <b...@debian.org>
Source: python-django-extensions
Version: 1.6.7-2
Severity: serious
Justification: FTBFS
Guessing this might be a Django issue with 1.10~beta1-1:
dh_auto_test -- --system=custom --test-args="{interpreter} -m pytest
--ds=tests.testapp.settings --cov=django_extensions"
I: pybuild base:184:
or
`calendar.timegm(time.gmtime())` is. It is annoyingly complicated to get
a Unix timestamp in Python. Although Python >= 3.3 makes it easier with
`datetime.datetime.utcnow().timestamp()`. Not sure how the `datetime`
module went so long without the ability to return a timestamp."
--
Brian May <b...@debian.org>
ething that should be forwarded upstream?
https://github.com/mkdocs/mkdocs/issues
--
Brian May <b...@debian.org>
he syntax of the
> script (patch included) which stopped the spurious e-mails.
I have made this change in git. Thanks.
In future, unified diffs are a lot better then context diffs. See the -u
parameter to diff.
--
Brian May <b...@debian.org>
fake-factory/
--
Brian May <b...@debian.org>
ntially be relying on this (broken)
behaviour.
Regards
--
Brian May <b...@debian.org>
-maintainer upload.
+ * Fix FTBFS. Add python-pep8 to build-depends. Closes: #818060.
+
+ -- Brian May <b...@debian.org> Mon, 02 May 2016 11:12:25 +1000
+
shortuuid (0.4.3-1) unstable; urgency=medium
* New upstream release
diff -Nru shortuuid-0.4.3/debian/control shortuuid-0.4.3/debian/c
access to PAPT (so I could fix another package), however
so far haven't got a response.
I would sooner maintain them in collab-maint rather then PAPT, because I
don't really want to have to convert my git repositories to
subversion. I believe subversion is still required by PAPT.
--
Brian May <b...@debian.org>
licenses that I can see
here:
https://en.wikipedia.org/wiki/BSD_licenses
--
Brian May <b...@debian.org>
Package: wnpp
Severity: wishlist
Owner: Brian May <b...@debian.org>
* Package name: python-mkdocs-bootstrap
Version : 0.1.1
Upstream Author : Dougal Matthews <dou...@dougalmatthews.com.com>
* URL : https://pypi.python.org/pypi/mkdocs-bootstrap/
* License
Package: wnpp
Severity: wishlist
Owner: Brian May <b...@debian.org>
* Package name: python-mkdocs-bootswatch
Version : 0.4.0
Upstream Author : Dougal Matthews <dou...@dougalmatthews.com.com>
* URL : https://pypi.python.org/pypi/mkdocs-bootswatc
Neil Williams <codeh...@debian.org> writes:
> python-django and python-django-tables2 from jessie work but if either
> one is pulled in from jessie-backports without the other, restarting
> apache2 causes a HTTP500.
I am not sure I see how adding the Breaks header helps resolve
you upgrade django-tables and then upgrade django?
Apart from the Breaks header, all other the changes look fine and I will
look at making these changes to the unstable version.
--
Brian May <b...@debian.org>
gs to git.
Only possible concern: Is it ok to disable intersphinx like this? I
assume the documentation will still be good, just the links to external
documentation won't appear as links. Is this correct?
--
Brian May <b...@debian.org>
an error, feel free to close this bug
report.
--
Brian May <b...@debian.org>
Package: sbuild
Version: 0.68.0-1
Severity: important
Hello,
According to the documentation:
--extra-repository=spec
Add a repository to the list of apt sources during the package
build. The repository specification is a line suitable for an
Brian May <b...@debian.org> writes:
> The patch looks good to me, I should be able to incooporate it into git
> and upload today.
Thanks for the patch. I have just uploaded a fixed version to Debian.
--
Brian May <b...@debian.org>
201 - 300 of 1212 matches
Mail list logo
