On Sun, 12 Jul 2015, Adam D. Barratt wrote:
On Sun, 2015-07-12 at 11:43 +0200, Stefan Fritsch wrote:
#789914 affects jessie + stretch, too. I have added a 'found' to the
bts so it should now migrate. I would prefer to have the current
package migrate before a new upload.
Was that mail
On Sun, 2015-07-12 at 11:43 +0200, Stefan Fritsch wrote:
On Thursday 09 July 2015 14:35:17, Jean-Michel Vourgère wrote:
Ops, actually, the message changed, and #789914 now seems to be the
source of the migration blockade.
#789914 affects jessie + stretch, too. I have added a 'found' to the
On Thursday 09 July 2015 14:35:17, Jean-Michel Vourgère wrote:
Ops, actually, the message changed, and #789914 now seems to be the
source of the migration blockade.
#789914 affects jessie + stretch, too. I have added a 'found' to the
bts so it should now migrate. I would prefer to have the
Dear apache2 maintainers
You might have notice that apache2 2.4.12 is still stuck in unstable.
Here's an extract from a discussion I had on IRC on Monday:
--- 8
(14:30:14) nirgal: Hi there. After no longer building some Jessie
transitional packages, we filled a RM request in
Ops, actually, the message changed, and #789914 now seems to be the
source of the migration blockade.
--
To UNSUBSCRIBE, email to debian-apache-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive:
5 matches
Mail list logo