uld you feel about turning this on in the
> krb5.conf shipped by krb5-config?
The concept sounds fine to me. I may be restricted in how much time I
can spend on such a project however.
--
Brian May
I can remove this Breaks for my upload.
Alternatively, if you want, just upload a fixed package to unstable, and
if all other requirements have been met it should be fine I think.
--
Brian May <b...@debian.org>
Dmitry Shachnev <mity...@debian.org> writes:
> The fixed version won’t reach testing *first* because I have added
> Breaks: mkdocs-bootswatch (<< 0.5) to it.
What is the reason for this? Does mkdocs still try to use
mkdocs-bootswatch if it is availabe?
--
Brian May <b...@debian.org>
keep it.
>
> Can you please file a removal bug yourself? As only you can file a RoM bug.
Will do so.
I note the python-mkdocs package in sid still build-depends on both
these packages. So probably should wait until a fixed package reaches
testing first.
--
Brian May <b...@debian.org>
lease remove it.
Thanks
--
Brian May <b...@debian.org>
mind if I do that? Also can I switch from git-dpm to gbp using
> the DPMT workflow (https://wiki.debian.org/Python/GitPackagingPQ)?
Please go ahead on both. Conversion to gbp should be easy too, no
patches to unapply.
--
Brian May <b...@debian.org>
.
I already tried to update both these packages, but IIRC got stuck trying
to get lintian happy. I have pushed my changes to salsa.
--
Brian May <b...@debian.org>
Joey Hess <i...@joeyh.name> writes:
> -x with the IP of the ssh server does avoid the problem
Suggestions with how to deal with this appreciated. Unfortunately I
cannot think of any good solutions.
--
Brian May <b...@debian.org>
, use of "-x" to exclude packets for the
remote server should solve the problem.
Regards
--
Brian May <b...@debian.org>
/github.com/sshuttle/sshuttle/issues/224
--
Brian May <b...@debian.org>
Package: ftp.debian.org
Severity: normal
Hello,
django-celery is broken, deprecated upstream, and has been replaced by
other packages that are already in Debian, such as django-celery-results
and django-celery-beat.
This was discussed on debian-python, see:
accessing settings.
I believe this bug report, and several others you filled recently that
contain this same text are false.
Like it or not, it is just not possible to import Django libraries
without providing a valid django settings file. This is not a sign that
something is broken.
--
Brian May <b...@debian.org>
Attached is a patch that appears to solve this. I haven't subjected it
to much testing yet however.
--
Brian May <b...@debian.org>
--- /usr/bin/gcalcli 2016-09-18 01:31:26.0 +1000
+++ /tmp/gcalcli 2018-03-27 17:10:23.647889928 +1100
@@ -1553,8 +1553,8 @@
co
Package: gcalcli
Version: 3.4.0-1
Severity: normal
This only happens with --nodeclined:
Traceback (most recent call last):
File "/usr/bin/gcalcli", line 2649, in
BowChickaWowWow()
File "/usr/bin/gcalcli", line 2499, in BowChickaWowWow
gcal.AgendaQuery()
File "/usr/bin/gcalcli",
>> Curiously, changes to tags don't seem to be preserved after the program
>> exits. This may or may not be related.
>
> Do you mean in the case that it aborts, or when it exits normally?
Only when my script aborts after completion.
--
Brian May <b...@debian.org>
On 2018-03-16 11:28, David Bremner wrote:
> I suspect it has to do with changes in memory management in python3.
>
> You hide the problem by adding
>
> del(db)
>
> at the end of your script.
Unfortunately, I still seem to be getting this abort error, although not
as often.
Curiously,
meters */
uint16* td_transferfunction[3];
float* td_refblackwhite;
[...]
} TIFFDirectory;
So I am guessing when you access td_transferfunction[3], you are
actually accessing td_refblackwhite, which - surprise surprise - happens
to be NULL.
--
Brian May <b...@debian.org>
David Bremner <da...@tethera.net> writes:
> You hide the problem by adding
>
> del(db)
>
> at the end of your script.
>
> You can read some discussion at
>
> https://notmuchmail.org/pipermail/notmuch/2016/021622.html
Thanks for this, and the work around.
The wor
Package: python3-notmuch
Version: 0.23.7-3
Severity: important
If I try to run the following program on Debian Stretch:
=== cut ===
#!/usr/bin/python3
import notmuch
db = notmuch.Database(mode=notmuch.Database.MODE.READ_WRITE)
def abcdef():
pass
q_new = notmuch.Query(db, 'tag:new')
=== cut
here is
already talk on debian-python about moving everything to Python3.
--
Brian May <b...@debian.org>
Package: getmail4
Version: 4.53.0-1+deb9u1
Severity: wishlist
I think the following packages are required for the
--store-password-in-gnome-keyring option to work. These should be listed
in the recommends (or maybe suggests) header.
* python-gnomekeyring
* python-gobject
This list may not be
the CA list. This includes
removing the StartCom and WoSign certificates to as they are now
untrusted by the major browser vendors.
--- cut ---
Or do I need more details? e.g. the list of certificates added/removed
from debian/changelog?
--
Brian May <b...@debian.org>
oking at fixing the dependancies. I CCed him.
Possibly there are errors in the git packaging that need to be fixed. I
stopped as soon as I encountered problems, because I did not have the
time to fix them.
--
Brian May <b...@debian.org>
onse (yet) from Michael Shuler, I am wondering
if we should go ahead and upload the wheezy version anyway?
As far as I can tell, the only change required to the debian-wheezy
branch is that the distribution in the changelog refers to "wheezy"
instead of "wheezy-security".
Regards
--
Brian May <b...@debian.org>
Emmanuel Lacour <elac...@easter-eggs.com> writes:
> after upgrade to 0.78.0-1, I can no longer establish tunnel. I get the
> following error:
What is the server you are attempting to connect to?
What is the output of "ip route" when run on the server?
--
Brian May <b...@debian.org>
.org/pypi/django-ranged-response/0.2.0
--
Brian May <b...@debian.org>
. Especially as it has been removed
from Jessie and Stretch.
--
Brian May <b...@debian.org>
arly.
Sorry, very short of time lately. Are you able to submit a bug report
upstream?
https://github.com/heimdal/heimdal/issues/
Thanks
--
Brian May <b...@debian.org>
this bug (yet again), and suggest
that we should think about removing the package from Debian testing and
unstable instead.
--
Brian May <b...@debian.org>
here doesn't seem to be any need
to keep this private.
--
Brian May <b...@debian.org>
hasn't been approved by
upstream...
Thanks.
--
Brian May <b...@debian.org>
against it to see if any fail. Although I think I may
have just described a transition anyway :-).
--
Brian May <b...@debian.org>
Michael Biebl <bi...@debian.org> writes:
> Is this problem still reproducible with a recent version of systemd?
Sorry, I can't even remember making this report now.
Stretch seems fine.
Please close it.
--
Brian May <b...@debian.org>
make sense.
I don't know why you might be getting errors from the cronjob, however I
think you are going to have to rethink your diagnoses. Or send me the
actual error cron in giving you.
--
Brian May <b...@debian.org>
least on a temp basis. Uploaded.
--
Brian May <b...@debian.org>
changes to git (or offer an alternative suggestion), I
should be able to review and upload a new package.
Thanks!
--
Brian May <b...@debian.org>
e upstream package is no longer Python3 compatable -
if I understood correctly.
--
Brian May <b...@debian.org>
writes:
> On Tue, Jul 18, 2017 at 05:35:07PM +1000, Brian May wrote:
>>Does the attached patch look good to you?
>
> Yes, that's exactly what I had in mind. Tested here and looks fine.
>
> Changelog typo: "explicity". Guessing you already spotted it.
>
> The path
Ryan Tandy <r...@nardis.ca> writes:
> Simply removing override_dh_auto_test should be enough. 01ee541a31 looks
> like an unnecessary change to me; AFAICT, debhelper has always supported
> 'make check'.
With this change, the tests fail. Still trying to understand why.
-
k of any reason why we need rpath set however. Which doesn't
mean reasons don't exist...
Patches to fix this welcome!
--
Brian May <b...@debian.org>
lace
> upstream.
It seems like there is not going to be a new celery release anytime
soon:
https://github.com/celery/celery/pull/3958#issuecomment-313997326
Are you able to provide a link to the commit that fixed this?
--
Brian May <b...@debian.org>
ty issue? Do we need to investigate fixes
for Wheezy, Jessie, and Stretch (depending on when this bug was first
introduced)?
--
Brian May <b...@debian.org>
commit 88132b00b2629c25caeb8fc30492a45afc2da610
Author: Brian May <br...@linuxpenguins.xyz>
Date: Tue Jul 18 17:32:27 2
m. Means binaries are more likely to
work across distributions.
I only hope that upstream have finished breaking ABI compatability...
--
Brian May <b...@debian.org>
On 2017-07-18 08:30, Brian May wrote:
> Please read the bull details of 868640 for more information, and for
> details of similar situation that occured before the Stretch
> release. #848694
Apologies for the typo.
s/bull/full/
ar situation that occured before the Stretch
release. #848694
--
Brian May <b...@debian.org>
ested, but the release team strongly disliked
this solution.
We ended up patching these symbols back in.
I am not particularly keen on maintaining a growing set of patches that
maintain backward compatability for eternanity while deliberately
breaking compatability with other non-Debian-distributions however.
--
Brian May <b...@debian.org>
previously undetected regression. i.e. it
changes the signature back to what it should have been. I fix that was
included in 7.4.0, that is now in unstable.
Unfortunately, as stable now has the bad signature, I really have no
idea what to do with this.
Suggestions? Maybe I should ask on debian-devel?
--
Brian May <b...@debian.org>
Salvatore Bonaccorso <car...@debian.org> writes:
> I just have prepared both and uploading to security-master for jessie-
> and stretch-security (the patch applied straightforward).
Thanks!
--
Brian May <b...@debian.org>
> the backtrack:
Hello,
If there any chance you could test this with version 7.4.0, which I just
uploaded to unstable?
Thanks
--
Brian May <b...@debian.org>
Guido Günther <a...@sigxcpu.org> writes:
> I've uploaded heimdal with the attached debdiff to delayed/2. Let me
> know if you're o.k. with it and I'll reuplod without delay.
Thanks a lot for this.
I just uploaded version 7.4.0 so your upload is not required.
--
Brian May <b...@debian.org>
Package: ftp.debian.org
Severity: normal
python-django-south is broken and not compatable with any supported
version for Django. See #807994.
Please remove from unstable and testing.
Thanks
Source: python-livereload
Version: 2.4.0-1
Severity: normal
The latest version of this package is required by the latest version of
python-mkdocs.
Thanks
-- System Information:
Debian Release: 9.0
APT prefers oldoldstable
APT policy: (500, 'oldoldstable'), (500, 'stable'), (500,
Adrian Bunk <b...@debian.org> writes:
>> * sphinx_celery
>
> https://tracker.debian.org/pkg/sphinx-celery
Looks like there is only a Python3 version of the package...
--
Brian May <b...@debian.org>
elery.
However it looks like the latest celery requires two new packages not
yet in Debian:
* sphinx_celery
* cyanide
--
Brian May <b...@debian.org>
ot;/<>/docs_theme/main.html", line 7, in top-level template
code
{% if page.title %}{{ page.title }} - {% endif %}{{ config.site_name
}}
File "/usr/lib/python3/dist-packages/jinja2/environment.py", line 430, in
getattr
return getattr(obj, attribute)
jinja2.exceptions.UndefinedError: 'page' is undefined
--
Brian May <b...@debian.org>
ded it upstream:
https://github.com/django-extensions/django-extensions/issues/1072
--
Brian May <b...@debian.org>
seconds
--
Brian May <b...@debian.org>
Brian May <b...@debian.org> writes:
> Looks like fixing this is going to require python3-tablib package. We
> have a python-tablib package, not a python3-tablib one though.
>
> I filled a bug report against python-tablib source.
#865855
--
Brian May <b...@debian.org>
Source: python-tablib
Version: 0.9.11-2
Severity: normal
This is required to build the latest version of django-tables.
Thanks.
-- System Information:
Debian Release: 9.0
APT prefers oldoldstable
APT policy: (500, 'oldoldstable'), (500, 'stable'), (500, 'oldstable'), (100,
'unstable')
Chris Lamb <la...@debian.org> writes:
> Brian May wrote:
>>
>> Bug #852512 reported by you has been fixed in the Git repository. You can
>> see the changelog below, and you can check the diff of the fix at:
>>
>>
>> https://anonscm.debian.org/c
d why you made
the above changes.
--
Brian May <b...@debian.org>
Brian May <b...@debian.org> writes:
> 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
get loaded?
Maybe it stopped loading apps the moment it detects a bad dependancy?
After looking at the code, this doesn't exactly make sense, but maybe
something here might help regardless.
--
Brian May <b...@debian.org>
On 2017-05-26 19:05, Neil Williams wrote:
> No. This is django making the wrong decision about problems it has
> previously supported when trying to include bug fixes for other
> problems. It is a regression in django 1.10
Feel free to argue this point in
control: forwarded -1 https://code.djangoproject.com/ticket/28250#ticket
Brian May <b...@debian.org> writes:
> B. Create a Django bug report pointing to our test case. They may or may
> not accept it as a bug in Django, however it would be good to get their
> feedbac
Django.
--
Brian May <b...@debian.org>
this migration really has
been applied.
--
Brian May <b...@debian.org>
rrect behaviour here. However I am
inclined to think maybe this isn't a Django 1.10 fault, because the
migration in Jessie clearly says it depends on a migration that was
never applied - because it doesn't even exist at this point.
--
Brian May <b...@debian.org>
s is what is triggering the Django 1.10 bug.
To the best of my knowledge this should still be supported.
If I am right, then it should be possible to work around this by
manually applying the migration in fake mode.
--
Brian May <b...@debian.org>
Neil Williams <codeh...@debian.org> writes:
> Upgrading directly to Stretch:
Just to clarify: Was this upgrading the entire system to stretch, or
just the relevant packages?
--
Brian May <b...@debian.org>
+djangorestframework (3.0.5-0.2) experimental; urgency=medium
+
+ * Non-maintainer upload.
+ * Fix broken links to media files. Remove debian/*.links, these symlinks are
+no longer relevant.
+
+ -- Brian May <b...@debian.org> Mon, 16 Mar 2015 14:20:11 +1100
+
> I noticed after send
er to
version 3.4.0-2 which is in stretch and sid.
In any case, it sounds like this bug, which *is* fixed in 3.4.0-2:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=858811
--
Brian May <b...@debian.org>
Currently blocked by
https://github.com/jenisys/parse_type/issues/7
--
Brian May <b...@debian.org>
Package: wnpp
Severity: wishlist
Owner: Brian May <b...@debian.org>
* Package name: python-parse-type
Version : 0.3.4
Upstream Author : Jens Engel
* URL : https://github.com/jenisys/parse_type
* License : BSD-3-clause
Programming Lang: Python
Descr
this under the Debian Python Modules Team umbrella.
--
Brian May <b...@debian.org>
control: retitle -1 ITP: python-pytest-bdd -- BDD library for the py.test runner
control: owner -1 !
I intend to package python-pytest-bdd for debian, under the Debian
Python Modules Team Umbrella.
I need it for some personal Debian packages I am creating.
--
Brian May <b...@debian.org>
:35.0 +1000
+++ heimdal-7.1.0+dfsg/debian/changelog 2017-04-26 19:38:20.0 +1000
@@ -1,3 +1,10 @@
+heimdal (7.1.0+dfsg-13) unstable; urgency=medium
+
+ * Add missing symbols base64_decode and base64_encode back into
+libroken. Closes: #848694.
+
+ -- Brian May <b...@debian.org>
roblem - at least in theory -
for locally built packages however.
--
Brian May <b...@debian.org>
Brian May <b...@debian.org> writes:
> In this case I don't think interference with gcrypt is likely, as the
> only package in Debian that uses Heimdal is OpenAFS, and neither Heimdal
> or OpenAFS depend on heimdal. Might be a problem - at least in theory
> for locally buil
install the latest clients without the latest
libraries.
After the Stretch release this bug is going to become irrelevant, as we
don't support upgrades from Jessie to Buster.
--
Brian May <b...@debian.org>
Control: reassign -1 ansible
Control: retitle -1 Ansible cannot parse python-passlib version number
Control: forward -1 https://github.com/ansible/ansible/issues/20199
Control: tag -1 upstream
Definitely. If you look at the Python package versioning PEP [1],
1.7.0.post20170421091442 is a
Brian May <b...@debian.org> writes:
> In what way do you consider this a bug in python-passlib and not
> ansible?
Looks like an Ansible bug to me:
https://github.com/ansible/ansible/issues/20199
--
Brian May <b...@debian.org>
t saying you are wrong, just trying to understand this better)
--
Brian May <b...@debian.org>
esting-proposed-updates; urgency=medium
+
+ * Fix FTBFS with timestampe overlow overflow on i386. Closes: #860619.
+
+ -- Brian May <b...@debian.org> Sun, 23 Apr 2017 08:16:49 +1000
+
python-passlib (1.7.0-1) unstable; urgency=medium
* Team upload.
diff -Nru python-passlib-1.7.0/debian/gbp
Aurelien ROUGEMONT <arougem...@synthesio.com> writes:
> Tags: patch
Why did you give this a patch tag? I don't see any patches...
> --- Please enter the report below this line. ---
Care to provide any more details?
--
Brian May <b...@debian.org>
uldn't reproduce this locally. I use a 32bit schroot.
--
Brian May <b...@debian.org>
Brian May <b...@debian.org> writes:
> I believe this is fixed in version 1.7.1 which is in unstable.
Unblock request sent:
#860717
--
Brian May <b...@debian.org>
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package python-passlib
Fixes a RC FTBFS issue on i386. See #860619.
The version in unstable is a new upstream version that fixes the problem
(and was already uploaded). The
Brian May <b...@debian.org> writes:
> This is actually Python 3.6 bug:
Actually that claim makes no sense as Python 3.6 isn't in Debian testing
or unstable yet.
--
Brian May <b...@debian.org>
s://bugs.python.org/issue29100
https://bugs.python.org/issue29346
python-passlib applied a work around:
https://bitbucket.org/ecollins/passlib/commits/80f838f5771f6753b0e46716ab25b48641aeef89
--
Brian May <b...@debian.org>
ntal; the latter is perplexing to me.
As far as I can tell, libstdc++6 doesn't actually depend on
python3-taglib. No idea why your results show otherwise.
blumindo is not in unstable or stretch. Guessing you were looking at the
version in experimental.
--
Brian May <b...@debian.org>
't see anything in testing.
(no, I do not I consider this grounds for an RM by itself).
--
Brian May <b...@debian.org>
.
+
+ -- Brian May <b...@debian.org> Mon, 10 Apr 2017 17:21:35 +1000
+
heimdal (7.1.0+dfsg-11) unstable; urgency=medium
* Remove legacy provides/conflicts/replaces headers. Old daemons
diff -Nru heimdal-7.1.0+dfsg/debian/patches/CVE-2017-6594
heimdal-7.1.0+dfsg/debian/patches/CVE-201
ething I should
be trying to get fixed in stretch? I suspect maybe not, it looks like
X32 isn't a Debian supported platform. If you disagree, please give good
reasons that would statisfy the Debian release team.
--
Brian May <b...@debian.org>
ug=850723#10.
You already fixed this bug in libtommath, but this bug is against
Heimdal not libtommath. As the bug is not fixed in Heimdal so we have to
keep this bug report open.
--
Brian May <b...@debian.org>
re was a change commited
to the Debian git repository, however never included in any released
version.
I have tried to reproduce this problem, without the change, and not had
any success.
Regards
--
Brian May <b...@debian.org>
legacy provides/conflicts/replaces headers. Old daemons
+such as ftp have been removed. Closes: #236902, #859664.
+
+ -- Brian May <b...@debian.org> Sat, 08 Apr 2017 11:38:13 +1000
+
heimdal (7.1.0+dfsg-9) unstable; urgency=medium
* Switch back to collab-maint URL until pkg-heimdal permi
-sudo-bash package should be able to scrape a
given wikipedia page to obtain the URL that it should download the bash
script from. With a check to ensure it is prefixed with http:// not
https://. That way anybody can update the URL as required, not just the
Debian developer.
Oh, sorry, not April 1st anymore :-(
--
Brian May <b...@debian.org>
-3.1.23/debian/changelog 2017-03-24 17:00:36.0 +1100
+++ celery-3.1.23/debian/changelog 2017-03-30 07:55:02.0 +1100
@@ -1,3 +1,9 @@
+celery (3.1.23-7) unstable; urgency=medium
+
+ * Fix bashisms in initd scripts. Closes: #858298.
+
+ -- Brian May <b...@debian.org> Thu,
ck request sent: #858864
--
Brian May <b...@debian.org>
101 - 200 of 1212 matches
Mail list logo
