Public bug reported:
Binary package hint: openarena-data
Affected source packages: openarena, openarena-data
Affected release: hardy-backports
Packages openarena and openarena-server were backported from intrepid to
hardy-backports. Due to the dependency openarena-data (= 0.7.7) of
these
*** This bug is a duplicate of bug 247587 ***
https://bugs.launchpad.net/bugs/247587
** This bug has been marked a duplicate of bug 247587
openarena 0.7.7 backported to Hardy, but openarena-data 0.7.7 not backported
--
Backport of package openarena requires backport of package
** Also affects: hardy-backports
Importance: Undecided
Status: New
--
warsow 0.42 backported to Hardy, but warsow-data 0.42 not backported
https://bugs.launchpad.net/bugs/246238
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Our main fileserver here (which is based on dapper, but uses an edgy
2.6.17 kernel (version 2.6.17-11-server, backported to dapper) because
we need NFSv4 with working krb5p support) is also hit by the problem.
Using no_subtree_check as export option seems to work around the
problem, but as I
And, by the way, the fix mentioned above is included in the version of
linux-source-2.6.17 that is in edgy-proposed (2.6.17-50.50). The newer
(by one week, timestamp-wise) release of linux-source-2.6.17 in edgy-
security (2.6.17-11.35) still contains the bug. The feisty kernel
(2.6.20) is also
Update: The version of 2.6.17 in edgy-proposed (linux-
source-2.6.17-50.50) is *not fixed*. Although it should (IMHO) not cause
the problems concerning permissions or stale NFS handles, it is missing
another security fix (the one that originally caused the problem, from
commit
Oops... The patch in the attachment above obviously mixed up spaces and
tabs... Use the --ignore-whitespace patch option when applying it.
--
Permission Denied on nfs clients for only some files
https://launchpad.net/bugs/62308
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
As there seems to be no activity on this bug yet, I did a binary search
in the bcollins/ubuntu-edgy git tree to find the problematic commit that
introduced the problem. (I use the http interface on git.kernel.org to
do this.)
The situation is quite confusing. There are two files named skge.c in
Included hw spin-lock patch for skge.c and skge.h (based on 2.6.15-27.48
sources). Fix seems to correct the problems in our setup.
** Attachment added: Patch for skge driver version 1.5 (skge.c, skge.h)
http://librarian.launchpad.net/4797263/patch.txt
--
skge driver broken: invalid call to
I just verified that this defect in the skge driver is also present in
the current git tree (URL given below) for edgy. It would be fine if it
could be fixed in time, as releasing edgy with this bug would prevent
installation of edgy on affected machines (without special workarounds),
as accessing
As Laurent already mentioned, the problem disappears when adding #,
c-format in the PO format of the file, in front of the problematic
entry. I think this is the key to understand what is really going wrong
here.
It seems that first running msgunfmt, followed by msgfmt, does not
necessarily yield
The problem in Bug 42264 seems to be related to the fact that gettext
has problems identifying C printf strings as such when C99 specifiers
like PRIuMAX are present, and requires a #, c-format hint in these
cases. Note that running msgunfmt on a MO, followed by msgfmt on the
intermediate PO, does
12 matches
Mail list logo
