Johannes Schauer Marin Rodrigues writes:
> thank you! Would you like me to take care of filing the unblock request with
> release.debian.org or would you like to take care of that yourself?
Can you please do this?
Thanks
--
Brian May @ Debian
o believe this is an openldap issue.
--
Brian May
On Sat, Aug 06, 2022 at 03:57:47PM +0200, julien.pu...@gmail.com wrote:
> reassign 1015044 sshutle 1.0.1-1
errr, typo here in the package name.
--
Brian May
his file. Which breaks Debian
packages.
If you don't agree with me, then assign this bug back to sshuttle and I
will deal with it. In fact latest upstream sshuttle removes
setuptools-scm support anyway.
--
Brian May
On Mon, Aug 15, 2022 at 11:32:45AM +1000, Brian May wrote:
> Actaully, I am confused, how come this list here is different from the
> list in #1016884?
Sorry, too much multi-tasking here..
That does show the exact same symbol rk_closefrom was removed.
This is a duplicate bug.
--
Brian May
verride_dh_makeshlibs] Error 25
Actaully, I am confused, how come this list here is different from the
list in #1016884?
--
Brian May
.0 1.4.0+git20110226
> +#MISSING: 7.7.0+dfsg-4+b1# rk_closefrom@HEIMDAL_ROKEN_1.0 1.4.0+git20110226
What would be considered an acceptable solution here?
Presumably I can't just delete the symbol, that might break stuff.
Also see https://github.com/heimdal/heimdal/issues/1006
--
Brian May
I think this is a duplicate of #1016884.
--
Brian May
p/version.py 2022-07-26 07:58:22.490171539 +1000
@@ -1,5 +1,5 @@
# coding: utf-8
# file generated by setuptools_scm
# don't change, don't track in version control
-version = '1.1.0'
-version_tuple = (1, 1, 0)
+__version__ = version = '1.1.0'
+__version_tuple__ = version_tuple = (1, 1, 0)
--
Brian May
Brian May writes:
> * Patch breaks compilation on latest Heimdal release:
https://github.com/heimdal/heimdal/issues/849
Upstream solution is use the git version :-(
--
Brian May
'
make[1]: *** [debian/rules:38: override_dh_auto_configure] Error 2
Anyway, just my status for now. Help appreciated :-)
--
Brian May
Package: kdenlive
Version: 20.08.2-1
Severity: grave
Justification: renders package unusable
If I try to start kdenlive on a new system that has never run kdenlive
before, it aborts with an error.
$ kdenlive
Using modified system locale without group separator for numbers
NEW LC_ALL en_AU.UTF-8
M
Dmitry Shachnev writes:
> I would be happy to update the packaging to the latest upstream
> release (1.1) and upload it, if the maintainer (Brian) wants so.
That is good with me.
Thanks.
--
Brian May
Control: tag -1 pending
Hello,
Bug #943238 in sshuttle reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
https://salsa.debian.org/debian/sshuttle/-/commit/367c14f9a89a3e77e77264925d9e7c0a
Package: lua-cgi
Version: 5.2~alpha2-1
Severity: serious
Justification: renders package useless
As far as I can tell - please do say if I am wrong - this package is
completely useless with LUA5.1, as packaged.
When run with the following code:
=== cut ===
session = require("cgilua.session")
sess
is looks like it could be non-trivial to fix.
--
Brian May
Mark Hindley writes:
> Since this upload was an LTS NMU, I should have copied you in.
Thanks for the report. It looks like the fix for CVE-2019-10871 might be
broken, and I might have to revert this change.
--
Brian May
Brian May writes:
> If it is not needed anymore, and nobody has the time to maintain it,
> might be best to remove it.
Removal request sent, see Bug#940923.
--
Brian May
so that they expire before the 2038 armageddon so the
> test suite will pass on 32-bit operating systems until the underlying
> issues can be resolved.
>
Thanks for this.
--
Brian May
Brian May writes:
> This implies it should be possible for ap application to request 64 bit
> time_t, but not sure how.
I see proposals to setting _TIME_BITS=64 from 2015, however I don't
actually see any reference to this being implemented yet.
https://lwn.net/Articles/664800/
--
Brian May
Brian May writes:
> My vague understanding is that this might already be possible by
> defining __USE_TIME_BITS64.
I may not have got this exactly right:
/*
* The event structure itself
* Note that __USE_TIME_BITS64 is defined by libc based on
* application's request to use 64
is might already be possible by
defining __USE_TIME_BITS64.
Having problems trying to verify this right now however.
--
Brian May
b.com/quanah/heimdal/commit/e3cd069e5c40b455541508b81ffeb0563e882aed
--
Brian May
check-tester \
check-uu
TESTS = $(SCRIPT_TESTS)
=== cut ===
--
Brian May
, then I
> can try to cook up the required patch.
I would appreciate any fix that will fix this for both 32bit and 64bit
- preferably as simple as possible, so I can get the recent security
fixes into buster.
(also please do CC me in BTS emails)
Thanks!
--
Brian May
On 2019-04-10 09:32, MK wrote:
Any chance of having this pushed into debian-release for buster via an unblock request?
This seems important to anyone running a mail server with amavis in buster.
I believe it was unblocked already:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=926580
It
Tobias Frost writes:
> I've prepared an NMU for amavisd-new (versioned as 1:2.11.0-6.1) and
> uploaded it to DELAYED/10. Please feel free to tell me if I
> should delay it longer.
Thanks. This looks good to me. Feel free to upload immediately without
the delay if you want.
--
Brian May
ment
from upstream. The problem has been fixed in the latest RC version of
celery.
I have a suspicion that the stable version of celery will work fine with
billiard 3.6.0.0, but not tested it.
--
Brian May
> I don't know whether this is an issue from amavisd-new or dpkg
> (start-stop-daemon) but feel free to assign it properly.
Bug #921557 is relevant here.
--
Brian May
report.
I thought I had fixed the problem when I applied the patch in #913548
because there is no mention in that bug report that the patch is not
sufficient.
I really do not have any time to waste on such matters.
Regards
--
Brian May
ime to maintain it,
might be best to remove it.
--
Brian May
uild-indep] Error 2
> dpkg-buildpackage: error: debian/rules build-indep subprocess returned exit
> status 2
>
I simply cannot reproduce this error.
Are you sure you didn't accidentally delete the supplied
./lib/hcrypto/engine.h file?
Regards
--
Brian May
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
es. 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
and suggest
that we should think about removing the package from Debian testing and
unstable instead.
--
Brian May
72a61486ecce299e4e1a8b8aeaae655664f1619f
Author: Brian May
Date: Fri Jul 21 17:54:46 2017 +1000
Remove license.txt kludge
diff --git a/debian/changelog b/debian/changelog
index c7ba647..5eb14fd 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+django-guardian (1.4.9-2) UNRELEASED
Salvatore Bonaccorso writes:
> I just have prepared both and uploading to security-master for jessie-
> and stretch-security (the patch applied straightforward).
Thanks!
--
Brian May
Guido Günther 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
Adrian Bunk writes:
>> * sphinx_celery
>
> https://tracker.debian.org/pkg/sphinx-celery
Looks like there is only a Python3 version of the package...
--
Brian May
like the latest celery requires two new packages not
yet in Debian:
* sphinx_celery
* cyanide
--
Brian May
71a4139d7bed13934e89a3a999c18b795746cdde
Author: Brian May
Date: Fri Jul 7 20:55:46 2017 +1000
Fix Python 3 depends
diff --git a/debian/changelog b/debian/changelog
index fe98d12..987625b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -3,6 +3,7 @@ django-xmlrpc (0.1.7-1) UNRELEASED; urgency
d4447764ce7f7fbbe89cb07c7f82b21bda6b09aa
Author: Brian May
Date: Fri Jul 7 17:40:24 2017 +1000
Fix Python3 depends
diff --git a/debian/changelog b/debian/changelog
index 72423fe..0f6ab08 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+django-cors-headers (2.1.0+github-2
ends "main.html" %}
File "/<>/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
ithub.com/django-extensions/django-extensions/issues/1072
--
Brian May
569f82e3b14d7607ecbe6388428536f8c7e5e8b3
Author: Brian May
Date: Tue Jul 4 08:28:21 2017 +1000
Add new changelog entry for 0.5.5-1.
diff --git a/debian/changelog b/debian/changelog
index 11e8cf6..54c1e4b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+django-simple
a32c05f3f201b3e8e7913b5b3e8e3599a9c91c93
Author: Brian May
Date: Mon Jul 3 08:03:09 2017 +1000
Updates for 3.6.3-1
diff --git a/debian/changelog b/debian/changelog
index 8ab50b5..a7e3e2c 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,9 @@
+djangorestframework (3.6.3-1
df7fa09c9cb9e381c1e6d2001ff05582fa89d7fe
Author: Brian May
Date: Mon Jul 3 07:35:41 2017 +1000
Update changelog entry for 1.0.4-1.
diff --git a/debian/changelog b/debian/changelog
index 34d3396..023bc53 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,9 +1,10 @@
-django-filter (0.13.0-2
or in 0.88 seconds ====
--
Brian May
Brian May 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
3d3c4a83f34747c3ca14dba4f1d71329f40ad24e
Author: Brian May
Date: Sun Jun 25 13:14:22 2017 +1000
Update changelog for 1.4.8-1
diff --git a/debian/changelog b/debian/changelog
index f947d8e..fed99d6 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,13 +1,17 @@
-django-guardian (1.4.4-2
pped 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
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
https://code.djangoproject.com/ticket/282
control: forwarded -1 https://code.djangoproject.com/ticket/28250#ticket
Brian May 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
> feedback.
Done: https://code.djangopr
ainst Django.
--
Brian May
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
feedback.
C. My idea for a work around is to write code that will directly update
the Django migration tables to indicate that this migration really has
been applied.
--
Brian May
lied. It does this check
before applying any migrations.
I don't know for sure what is correct 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
.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
Neil Williams writes:
> Upgrading directly to Stretch:
Just to clarify: Was this upgrading the entire system to stretch, or
just the relevant packages?
--
Brian May
Brian May 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 built packages however
theory -
for locally built packages however.
--
Brian May
duce this locally. I use a 32bit schroot.
--
Brian May
Brian May writes:
> I believe this is fixed in version 1.7.1 which is in unstable.
Unblock request sent:
#860717
--
Brian May
https://bugs.python.org/issue29346
python-passlib applied a work around:
https://bitbucket.org/ecollins/passlib/commits/80f838f5771f6753b0e46716ab25b48641aeef89
--
Brian May
Brian May 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
Brian May 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 easy to fix, and I have m
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 :-).
5850e207f04d0abac535ceb94e0b66457d80d53b
Author: Brian May
Date: Fri Mar 24 08:25:20 2017 +1100
Add missing build depends on python-vine and python3-vine. Closes: #858540.
diff --git a/debian/changelog b/debian/changelog
index 4d08da1..4d8c416 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10
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
will fix it up.
Thanks for letting me know.
--
Brian May
Brian May 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
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
upstream version.
--
Brian May
Santiago Vila 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: #857430
--
Brian May
ows
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
Brian May 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
amavisd-new back in the archive:
xed it
might help distribute amavisd-new some other way (maybe outside Debian).
--
Brian May
Brian May 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 what the bug breaks is
agrees. It is
> too late but i'd try anyway, the debdiff between 2.10.1-2~deb8u1 and
> 2.10.1-4 shouldn't be big
I have also sent an unblock request. Or rather request for dialog with
the release team. #856067
Feel free to submit extra details to this if appropriate.
http://bugs.debian.org/856067
--
Brian May
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 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
d20c791c221ece23520063bee1d308db3a9dff88
Author: Brian May
Date: Tue Feb 21 08:21:57 2017 +1100
Add breaks/replaces headers
diff --git a/debian/changelog b/debian/changelog
index 6598864..dc16f1d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+slimit (0.8.1-3) UNRELEASED; urgency=medium
bug is in Perl or libdbd-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
Brian May 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 reported against Perl.
https://rt.perl
is working on getting some solid evidence to
prove this.
--
Brian May
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
#x27;t changed within 6 years (line
endings 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
Henrique de Moraes Holschuh writes:
>> https://github.com/perl5-dbi/DBD-mysql/issues/78
>
> Thanks!
Please read the latest message on the above report...
--
Brian May
ug lies solely in p5-DBD-mysql
not returning valid data.
Just found this bug report:
https://github.com/perl5-dbi/DBD-mysql/issues/78
--
Brian May
ould 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
Michael Fladischer 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
u 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
ably 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 look.
--
Brian May
6c3fd23496be891868525437c03c65fddb9ec7e9
Author: Brian May
Date: Thu Feb 9 17:09:33 2017 +1100
Incorporate changes from NMU 1.3.7-1.1
diff --git a/debian/changelog b/debian/changelog
index f2437e4..76ae468 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,15 @@
+python-mysqldb (1.3.7-1.1
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
ae7f415511ffb46b06f4696497b589baa239943c
Author: Brian May
Date: Tue Jan 31 17:32:05 2017 +1100
Remove century tests
diff --git a/debian/changelog b/debian/changelog
index f07ca2d..6ed8457 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -2,6 +2,7 @@ faker (0.7.7-2) UNRELEASED; urgency=medium
* Fix
08f626e51cf15c88213d6b2474bd56156b0b8ee4
Author: Brian May
Date: Sun Jan 29 08:59:39 2017 +1100
Add upstream patch for UnboundLocalError
diff --git a/debian/changelog b/debian/changelog
index 84d5377..f07ca2d 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,10 @@
+faker (0.7.7-2) UNRELEASED
(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
look for alternatives???
--
Brian May
Brian May 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 to really help,
working,
I might move it to DPMT.
--
Brian May
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
1 - 100 of 298 matches
Mail list logo
