[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#874623: marked as done (unblock: cpl/7.0-5)

Your message dated Fri, 08 Sep 2017 08:44:02 +0100
with message-id <61074f8ff12b8dbffe9d1ad2fcddeac4@mail.adam-barratt.org.uk>
and subject line Re: Bug#874623: unblock: cpl/7.0-5
has caused the Debian Bug report #874623,
regarding unblock: cpl/7.0-5
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
874623: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=874623
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: release.debian.org
Severity: normal
User: release.debian.org@packages.debian.org
Usertags: unblock
Please unblock package cpl.

The package no longer builds a package for the contrib area, so it
should be able to migrate to testing the normal way.

BTW, it would have been nice to contact me and discuss the problem
before just blocking the package. It is not so simple to find out the
cause, and the tracker is quite misleading here (it says that I should
check the freeze policy).

Thank you

Best regards

Ole

--- End Message ---
--- Begin Message --- 
On 2017-09-08 8:29, Ole Streicher wrote:

The package no longer builds a package for the contrib area, so it
should be able to migrate to testing the normal way.


Thanks for the update. I've removed the hint.


BTW, it would have been nice to contact me and discuss the problem
before just blocking the package.
Well, the bug is arguably more in the archive rather than your package (aside from whether one believes that building packages in main + contrib from one source package is a reasonable thing to do, which there is some disagreement on). 


It is not so simple to find out the
cause, and the tracker is quite misleading here (it says that I should
check the freeze policy).
Thanks for pointing that out, I've reverted to the non-freeze text referring to debian-release. 

Regards,

Adam

--- End Message ---
Reply to: