control: close -1
Hello, at the end the rename has been renamed again in experimental so this bug
can be closed.
However, since many packages outside Debian might need libsane and not libsane1
I opened a new bug report to track this:
https://bugs.debian.org/962936
G.
On Mon, 21 Jan 2019
On Mon, Jan 21, 2019 at 9:23 AM John Paul Adrian Glaubitz
wrote:
> Well, I have a different opinion on that. I do not consider a temporary
> issue in unstable a bug affecting anything but developers.
3 months isn't temporary. While I think Testing is a better fit for
users than Unstable (maybe
On 1/21/19 2:53 PM, Jeremy Bicha wrote:
> Respectfully, Debian Policy doesn't cover every single point. I think
> the principle that you should be able to smoothly upgrade unstable is
> such an undisputed principle that it hasn't needed to be stated in
> Policy yet. piuparts is one tool to monitor
Hello John,
>No, it didn't. What makes you think so? The version of sane-backends with
>the libsane1 package was never migrated to testing, see:
you are right, I'm not sure why I missed this :)
If you want to cancel or reschedule my delayed upload, feel free to do it,I
still would like to know
On Mon, Jan 21, 2019 at 4:08 AM John Paul Adrian Glaubitz
wrote:
> If someone can point me to the point in the policy where it says that
> upgrades and migrations in unstable need to be smooth and without
> such issues, I am happy to revise my point of view.
Respectfully, Debian Policy doesn't
On 1/21/19 9:52 AM, Gianfranco Costamagna wrote:
>>If someone is using unstable, I expect them to be able to resolve
>>such issues themselves. unstable isn't a release, it's a development
>>version of Debian.
>
> ehm, this bug hit testing too :/
No, it didn't. What makes you think so? The
Hello,
>If someone is using unstable, I expect them to be able to resolve
>such issues themselves. unstable isn't a release, it's a development
>version of Debian.
ehm, this bug hit testing too :/
>I don't understand why some users install unstable without understanding>the
>ramifications of
On 1/8/19 4:46 PM, Jeremy Bicha wrote:
> Are you telling me that it's not supported to be able to smoothly
> upgrade unstable?
If someone is using unstable, I expect them to be able to resolve
such issues themselves. unstable isn't a release, it's a development
version of Debian.
> The issue
On Tue, Jan 8, 2019 at 10:26 AM John Paul Adrian Glaubitz
wrote:
> It's not serious for Debian since the package never entered testing in
> the first place.
>
> > I've prepared an NMU for sane-backends (versioned as 1.0.27-3.2) and
> > uploaded it to DELAYED/15. Please feel free to tell me if I
>
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
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
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
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:
13 matches
Mail list logo
