Processing commands for cont...@bugs.debian.org:
> affects 915195 src:uwsgi
Bug #915195 [release.debian.org] nmu: apr_1.6.5-1
Added indication that 915195 affects src:uwsgi
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
915195:
> * Depend on python3-dev since we're not building for all Python
> interpreters.
> Closes: #913069
>
> That's a release.debian.org tracking bug, not a bug against your package.
> Please don't close such bugs in uploads to the archive.
>
> In this particular case, I would guess you
Control: reopen -1
Hi,
libarcus (3.3.0-2) unstable; urgency=medium
.
[ Gregor Riepl ]
* Blacklisted incompatible python3-sip version (4.19.11+dfsg-1)
* Added new symbols that appear with current build dependencies.
Closes: #914953
* Depend on python3-dev since we're not
Processing control commands:
> reopen -1
Bug #913069 {Done: Gregor Riepl } [release.debian.org]
transition: python3.7 as default
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer
Your message dated Mon, 10 Dec 2018 12:04:04 +
with message-id
and subject line Bug#913069: fixed in libarcus 3.3.0-2
has caused the Debian Bug report #913069,
regarding transition: python3.7 as default
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Mon, 10 Dec 2018 12:04:30 +
with message-id
and subject line Bug#915822: fixed in ossim 2.6.0-2
has caused the Debian Bug report #915822,
regarding nmu: ossim_2.6.0-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Hi,
Did something strange happen with the glew transition ? glew 2.1.0 has
entered testing, which I don't understand.
On the transitions page https://release.debian.org/transitions/ glew is
listed as "almost complete" with 24% done (!)
Should rebuilds on the other deps be triggered ?
7 matches
Mail list logo
