tag 903576 +unreproducible
severity 903576 important
thanks
Hi,
I tried to reproduce this issue on a clean Debian stretch.
I installed docker-ce and aufs-dkms and switched the storage engine to aufs.
Docker build runs without any errors.
Also please note that docker recommends the use of
severity 908059 important
tag 908059 +moreinfo
thanks
Hi,
The crash is caused by a segmentation fault in st_renderbuffer_delete.
>From the stack trace you're providing, it's line 239 in mesa. which
doesn't make sense to me.
line 239:if (ctx) {
This doesn't look like it can cause a
Dear maintainer,
Please consider updating nuget for the release as the current version
in the archive is quite outdated.
The latest recommended version is v4.8.1
Also as written by the original reporter, more recent versions of
nuget are required for several packages.
Philipp
In fact, if you had been listening to me from day one, you'd realize
that I'm not even asking you to actually fix this problem.
I'm merely asking you to make the users who aren't using your personally
preferred use case, but are nevertheless using an apparently valid and
supported use case,
control: severity -1 important
Josip,
Please don't upgrade the severity of this bug.
The defaults actually prevent further data loss for the majority of drbd users.
In the normal setup the drbd device is the main storage device so the
defaults make sense.
If you have a suggestion for a better
Hi Josip
Actually, I think a general sync wasn't previously added in that situation
because it might cause a problem with the filesystem on the faulty DRBD
device itself, thereby causing the problem b) you described.
That's why I put in sync then sleep and reboot. But it's just an idea.
Hi,
I just tried to reproduce this problem, but the segfault or hang did not
occur.
* installed a clean sid chroot:
* used your config
* enabled the proxy_html module
* restarted apache
* apache still works properly
my versions:
apache2-mpm-prefork: 2.2.22-7
libapache2-mod-proxy-html: 3.0.1-1.1
Ok, it's not as simple as I thought.
The problem is: DKMS doesn't create packages to install its kernel
modules. That means it is not possible to add a Conflict between dkms-
built and module-assistant/pre-compiled packages.
The mkdeb command of dkms only creates a deb similar to our drbd8-
Package: drbd0.7
Severity: serious
As one of the maintainers of this package I request removal from testing.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Hey Norbert,
I'll replace the exit 1 with just a warning, that it couldn't be compiled
automatically and I'll fix module-assistant.
This should fix both 539218 and 539219.
Is that ok for you?
Philipp
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of
to me. Looks like a mistake.
Philipp Hug
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Luk,
This is not quite true, iscsitarget-module is provided by the package built
from iscsitarget-source.
Daniel Baumann will add those to linux-modules-extra-2.6 soon, so we'll have
prebuilt packages soon.
Anyway: I'll change the Depends to Recommends to make it poossible to install
it
I can install open-iscsi on a fresh etch install without any problems.
* kernel 2.6.18-4-xen-amd64 (debian)
could you please add the following info to the bug report:
* kernel version (debian, vanilla, ...)
* dmesg and syslog output
can you successfully load the following kernel modules?
*
Source: drbd8
Severity: serious
This package doesn't belong into etch. It's a pre-release of drbd0.8
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: drbd0.7-module-source
Version: 0.7.21-3
Severity: serious
Justification: FTBFS
DRBD 0.7.21 depends on devfs headers in the kernel. these headers don't exist in
current Debian kernels.
Please upgrade to 0.7.22.
-- System Information:
Debian Release: 4.0
APT prefers testing
APT
Jason,
I'll probably upgrade to 2.0-727. It should be compatible with Debian
kernels.
You can expect a new version this weekend.
philipp
Jason Martens wrote:
Package: open-iscsi
Version: 1.0.485-3
Severity: Grave
Open-iscsi version 1.0.485 is out of date, and the tools should not work
merge 356723 326841 344316
retitle 344316 invalid characters in search.htm cause segfault in search.cgi
thanks
See description of bug 344316.
the search.htm was wrong and contained invalid characters which caused a
segfault in search.cgi
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a
upload.
+ * C++ 'c2' transition (Closes: #332835)
+
+ -- Philipp Hug [EMAIL PROTECTED] Sat, 5 Nov 2005 20:08:14 +0100
+
xdb (1.2.0-5) unstable; urgency=low
* rebuild for g++-3.2
diff -urN xdb-1.2.0.lastupload/debian/control xdb-1.2.0/debian/control
--- xdb-1.2.0.lastupload/debian/control
This bug will be fixed in the next upstream version.
See: http://www.mnogosearch.org/bugs/index.php?id=1004edit=2
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
I fixed the mnogosearch package to also look for postgre headers in
/usr/include/postgresql/8.0
a new package will be uploaded soon
philipp
On Sunday 14 August 2005 15.02, Andreas Jochens wrote:
Package: mnogosearch
Version: 3.2.31-1
Severity: serious
When building 'mnogosearch' on unstable,
Joerg,
This bug doesn't apply to the drbd package as it is in unstable.
It only applies to the binary kernel packages cyril has built and uploaded
manually and are not part of the archive at the moment...
Can we tag this bug as sarge-ignore or what's the correct way of handling such
bugs?
Alright, I'll create a new source package which will invoke module-assistant
to build the binaries...
So we won't need the script anymore.
One issue: How can we keep in sync with updated kernel versions? Every new
versions needs to go through NEW because of changed package names...
Ideas?
22 matches
Mail list logo
