Bug#1003659: bullseye-pu: package python-django/2:2.2.26-1~deb11u1
- To: "Adam D. Barratt" <adam@adam-barratt.org.uk>, 1003659@bugs.debian.org
- Subject: Bug#1003659: bullseye-pu: package python-django/2:2.2.26-1~deb11u1
- From: "Chris Lamb" <lamby@debian.org>
- Date: Tue, 01 Mar 2022 12:49:03 -0000
- Message-id: <[🔎] 510ca68d-c082-4a84-9618-b4aa91003108@www.fastmail.com>
- Reply-to: "Chris Lamb" <lamby@debian.org>, 1003659@bugs.debian.org
- In-reply-to: <f39099b2ff5fe5f8226b9cc04a78ec1781087643.camel@adam-barratt.org.uk>
- References: <164207250030.1065044.15750685554313721461@copycat> <e697633dcb7263b73609980e5c15ee5be6d0c777.camel@adam-barratt.org.uk> <164207250030.1065044.15750685554313721461@copycat> <6a35c689-1657-4029-8ad0-3d536b4c44f6@www.fastmail.com> <f39099b2ff5fe5f8226b9cc04a78ec1781087643.camel@adam-barratt.org.uk> <164207250030.1065044.15750685554313721461@copycat>
Hi Adam,
>> > > * Fix a traceback around the handling of
>> > > RequestSite/get_current_site() due
>> > > to a circular import by backporting commit 78163d1a from
>> > > upstream. Thanks
>> > > to Raphaël Hertzog for the report. (Closes: #1003478)
>> >
>> > That change doesn't look like it made it to unstable yet; is that
>> > correct?
>>
>> I'm sorry, I had assumed it would have been incorporated into the
>> latest upstream releases that I uploaded around the same time. Now
>> that I look, it is not in the cutting-edge version in experimental
>> either.
>>
>
> No worries. I have to admit that I was surprised that it hadn't made it
> into a release upstream yet either.
>
>> (I assume you would want to see it there before accepting this pu,
>> right?)
>
> Yes, please. In general, any issues that are being resolved in (o)pu
> shouldn't affect unstable, either because they're not relevant there or
> because a fix was already applied.
This change is now in unstable and testing (2:3.2.12-2). :)
Regards,
--
,''`.
: :' : Chris Lamb
`. `'` lamby@debian.org 🍥 chris-lamb.co.uk
`-
Reply to: