Re: AUTORM: bug closed but still marked for autoremoval

2016-05-11 Thread Jerome BENOIT
Hello Again, On 11/05/16 12:07, Santiago Vila wrote: > On Wed, May 11, 2016 at 10:31:46AM +, Gianfranco Costamagna wrote: > >> You need to make the package migrate into stretch if you want the >> autoremoval to stop >> https://buildd.debian.org/status/package.php?p=singular&suite=unstable >>

Re: AUTORM: bug closed but still marked for autoremoval

2016-05-11 Thread Santiago Vila
On Wed, May 11, 2016 at 10:31:46AM +, Gianfranco Costamagna wrote: > You need to make the package migrate into stretch if you want the autoremoval > to stop > https://buildd.debian.org/status/package.php?p=singular&suite=unstable > armhf is not build anymore, so you can choose from: > 1) fixi

Re: AUTORM: bug closed but still marked for autoremoval

2016-05-11 Thread Gianfranco Costamagna
Hi Jerome You need to make the package migrate into stretch if you want the autoremoval to stop https://buildd.debian.org/status/package.php?p=singular&suite=unstable armhf is not build anymore, so you can choose from: 1) fixing polybori 2) file a bug against ftpmasters to remove singular [armhf]

AUTORM: bug closed but still marked for autoremoval

2016-05-11 Thread Jerome BENOIT
Hello Forum: my package singular [1] is marked for autoremoval while the involved bug has been fixed for a while. I suspect the involved bug [2] is in fact not considered as closed bug the robots. Any idea on how to fix it ? Thanks in advance, Jerome [1] https://packages.qa.debian.org/s/singu