Issues which are
a result of a broken installation or incorrect configuration should
not be reported as bugs.
(and you tell the reportbug maintainer?) don't judge too quick: the
fact that there was an error during installation doesn't mean there
was anything wrong on my part, only a series of
On 01/19/2014 10:23 AM, Sandro Tosi wrote:
(and you tell the reportbug maintainer?)
What does this have to do with the maintainer of reportbug? reportbug is
just the utility used to report canonical bug reports.
don't judge too quick: the
fact that there was an error during installation
On Sun, Jan 19, 2014 at 11:14 AM, John Paul Adrian Glaubitz
glaub...@physik.fu-berlin.de wrote:
On 01/19/2014 10:23 AM, Sandro Tosi wrote:
(and you tell the reportbug maintainer?)
What does this have to do with the maintainer of reportbug? reportbug is
just the utility used to report
On 01/19/2014 11:42 AM, Sandro Tosi wrote:
don't judge too quick: the
fact that there was an error during installation doesn't mean there
was anything wrong on my part, only a series of situations which lead
there without being able to replicate it. think before you preach.
Several people
No. If you mess around with your installation resulting in the
packages failing to upgrade or behaving unexpectedly as a result,
you can't file a bug and blame the authors or maintainers of
the software.
I mess around with my installation and blame someone? I suggest
you to think best before
On 01/19/2014 01:31 PM, Sandro Tosi wrote:
I mess around with my installation and blame someone? I suggest
you to think best before writing such thing - you don't deserve my
time, so I won't reply any further.
There is no need to be huffy.
Again, if you want someone to look at the problem you
I think I experienced that as consequence of a dist-upgrade.
Fixing the bug instead of just closing it would also be my
preference. I realize that this may be a tough task, as
the situation will probably not be easy to reproduce.
If you've changed something to make co-installation work,
it's
On 01/19/2014 03:35 PM, Claus Fischer wrote:
If you've changed something to make co-installation work,
it's probably best to close the bug and wait if it re-appears.
libsane has already been converted for MultiArch, hence such
issues should no longer arise.
If they do, it's ok to file another
close 725435
thanks
Co-installation of libsane for different architectures works now, I just
verified it. I am therefore closing this bug report. Issues which are
a result of a broken installation or incorrect configuration should
not be reported as bugs.
Thanks,
Adrian
--
.''`. John Paul
Package: libsane
Version: 1.0.23-3
Severity: grave
Hello,
when installing gnome, libsane fails to be installed due to:
Unpacking libsane:amd64 (from .../libsane_1.0.23-3_amd64.deb) ...
dpkg: error processing /var/cache/apt/archives/libsane_1.0.23-3_amd64.deb
(--unpack):
trying to overwrite
10 matches
Mail list logo
