Bug#913346: libsane1: Cannot update libsane1

2019-01-08 Thread John Paul Adrian Glaubitz
Control: severity -1 normal On 1/8/19 4:26 PM, John Paul Adrian Glaubitz wrote: > It's not serious for Debian since the package never entered testing in > the first place. Adjusting severity accordingly. Please don't set the severity to serious unless providing a reference to the corresponding

Bug#913346: libsane1: Cannot update libsane1

2019-01-08 Thread John Paul Adrian Glaubitz
Hello! On 1/3/19 11:51 PM, Jeremy Bicha wrote: > This issue is more serious for Ubuntu which will need to keep a > libsane1 transitional package around until after 20.04 LTS. It's not serious for Debian since the package never entered testing in the first place. > I've prepared an NMU for

Bug#913346: libsane1: Cannot update libsane1

2019-01-03 Thread Jeremy Bicha
Control: tags -1 +patch This issue is more serious for Ubuntu which will need to keep a libsane1 transitional package around until after 20.04 LTS. I am attaching the patch I applied in Ubuntu for this issue. Please consider applying it in Debian too. Thanks, Jeremy Bicha From

Bug#913346: libsane1: Cannot update libsane1

2018-11-09 Thread Ricardo F. Peliquero
Package: libsane1 Version: 1.0.27-3 Severity: grave Justification: renders package unusable Dear Maintainer, libsane1 cannot be updated using aptitude. It seems to be a dependancy problem. libsane1 depends on libsane-common (= 1.0.27-3) Should it make any sense to change it to this: