On Mon, Mar 02, 2020 at 01:14:59PM +1030, heman wrote:
> hi Tomas, thanks for the response, pretty sure the docker image was the
> official debian:buster from dockerhub. I'll double check.
>
> I hadn't thought of looking for an issue reporting link on dockerhub, as I
> figured it would be part o
On Sun, Feb 23, 2020 at 11:40:36PM +1030, heman wrote:
I've read https://www.debian.org/Bugs/Reporting
but it is still completely unclear to me how I can report what I
consider to be a bug or flaw with the debian docker image, as it is
not a package, but a container image created from multiple pa
On Sun, Feb 23, 2020 at 11:40:36PM +1030, heman wrote:
> Hi,
>
> I've read https://www.debian.org/Bugs/Reporting
> but it is still completely unclear to me how I can report what I
> consider to be a bug or flaw with the debian docker image [...]
That depends on where you got this Debian docker im
Hi,
I've read https://www.debian.org/Bugs/Reporting
but it is still completely unclear to me how I can report what I
consider to be a bug or flaw with the debian docker image, as it is
not a package, but a container image created from multiple packages.
(from reading the page at the above URL it w
Am Montag, 25. November 2019, 20:07:56 CET schrieb Goran Delcev:
Hi Goran,
this bug is known since almost 2 years. I reported it in the list, sent a
bugreport tzo
powerdevil (and askeds the list, which package might be responsible for it),
but got
no solution. People told me, the kernel itself
On Wed, 16 Feb 2011 09:32:56 +0100, Per Edlund wrote:
> I need help on how to report a bug in the installer.
http://wiki.debian.org/DebianInstaller/Bugs
http://www.debian.org/Bugs/Reporting.en.html
> I've tried to install Debian Squeeze (6.0) on a Dell PowerEdge 1750 for
> a day and it failes wi
Hi!
I need help on how to report a bug in the installer.
I've tried to install Debian Squeeze (6.0) on a Dell PowerEdge 1750 for a
day and it failes with Kernel Panic when detecting the network.
First I tried to upgrade Lenny to Squeeze, that failed (could make it work
by using the old kernel th
On 2010-10-26 05:05 +0200, Brian Sammon wrote:
>> As I explained in that bug report, it's an incompatibility between the
>> Squeeze kernel and Lenny userland. Unfortunately, there is no way to
>> express this in package conflicts to ensure that it does not occur on
>> partial upgrades.
>
> Okay,
On Lu, 25 oct 10, 23:05:56, Brian Sammon wrote:
> I don't think I have a custom kernel/udev/boot configuration. Is this
> problem
> going to happen to everyone who tries to run squeeze on an Inspiron 8500?
> Everyone who tries to run squeeze on a nvidia system?
But you are not running squeeze
> As I explained in that bug report, it's an incompatibility between the
> Squeeze kernel and Lenny userland. Unfortunately, there is no way to
> express this in package conflicts to ensure that it does not occur on
> partial upgrades.
Okay, so I'm clear:
You're saying the Lenny xserver-xorg-vide
On 2010-10-24 21:17 +0200, Brian Sammon wrote:
> I entered a bug that upgrading udev from lenny to unstable breaks X. (It
> also
> breaks with the squeeze version of udev )
> ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600551 )
>
> The bug was closed without any changes to the package, o
On Du, 24 oct 10, 15:17:50, Brian Sammon wrote:
> I entered a bug that upgrading udev from lenny to unstable breaks X. (It
> also
> breaks with the squeeze version of udev )
> ( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600551 )
>
> The bug was closed without any changes to the package,
I entered a bug that upgrading udev from lenny to unstable breaks X. (It also
breaks with the squeeze version of udev )
( http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=600551 )
The bug was closed without any changes to the package, or any other package.
While I've found a workaround, I'm con
13 matches
Mail list logo
