summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--contributing.mdwn2
-rw-r--r--hurd/translator/random.mdwn2
-rw-r--r--open_issues/adduser.mdwn8
-rw-r--r--open_issues/glibc.mdwn18
-rw-r--r--open_issues/glibc/getlogin_r.mdwn45
-rw-r--r--open_issues/libasyncns.mdwn19
-rw-r--r--open_issues/nice_changes_priority_of_parent_shell.mdwn2
-rw-r--r--open_issues/nice_vs_mach_thread_priorities.mdwn2
-rw-r--r--open_issues/thread-cancel_c_55_hurd_thread_cancel_assertion___spin_lock_locked_ss_critical_section_lock.mdwn2
9 files changed, 25 insertions, 75 deletions
diff --git a/contributing.mdwn b/contributing.mdwn
index eaffe7b2..ba0d3c90 100644
--- a/contributing.mdwn
+++ b/contributing.mdwn
@@ -98,8 +98,6 @@ packages, and are thus good candidates for porting, in order to increase
archive coverage:
* umount functionality in busybox
-* hyperestraier
-* sane-backends-extras
* ruby1.9.1
Here is a [[list of packages that need porting|hurd/running/debian/porting]].
diff --git a/hurd/translator/random.mdwn b/hurd/translator/random.mdwn
index afb76953..9fc975f2 100644
--- a/hurd/translator/random.mdwn
+++ b/hurd/translator/random.mdwn
@@ -31,7 +31,7 @@ but they are not yet in the default installation.
the internals.
* [Entropy Gathering Daemon](http://egd.sourceforge.net/).
- * [request for packaging](http://bugs.debian.org/145498).
+ * [[!debbug desc="request for packaging" 145498]].
* [OSKit Entropy
Patch](http://lists.gnu.org/archive/html/bug-hurd/2003-01/msg00000.html) from
diff --git a/open_issues/adduser.mdwn b/open_issues/adduser.mdwn
index 7761ec61..713a1dd3 100644
--- a/open_issues/adduser.mdwn
+++ b/open_issues/adduser.mdwn
@@ -13,10 +13,10 @@ is included in the section entitled
[[!tag open_issue_porting]]
`adduser` does work as expected, the following warnings are spurious, they just
-appear when one doesn't have the nscd package. They do not appear on linux boxes
-because there posix_spawn doesn't report ENOENT for exec(). Posix indeed says
+appear when one doesn't have the nscd package. They do not appear on Linux boxes
+because there posix_spawn doesn't report ENOENT for exec(). POSIX indeed says
that `if the error occurs after the calling process successfully returns, the
-child process shall exit with exit status 127'. The hurd however reports all
+child process shall exit with exit status 127'. The Hurd however reports all
errors, thus the warning.
$ sudo adduser foo
@@ -34,4 +34,4 @@ errors, thus the warning.
Copying files from `/etc/skel' ...
[...]
-Reported at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=623199
+Reported at [[!debbug 623199]].
diff --git a/open_issues/glibc.mdwn b/open_issues/glibc.mdwn
index 734806a1..24fe8026 100644
--- a/open_issues/glibc.mdwn
+++ b/open_issues/glibc.mdwn
@@ -220,8 +220,13 @@ Last reviewed up to the [[Git mirror's d3bd58cf0a027016544949ffd27300ac5fb01bb8
`open_by_handle_at`, `process_vm_readv`, `process_vm_writev`, `sendmmsg`,
`setns`, `sync_file_range`
+ Check also the content of `gnu/stubs-32.h`, which lists all the functions
+ marked as stub which only return `ENOSYS`.
+
* `chflags`
+ Patch sent, [[!message-id "20120427012130.GZ19431@type.famille.thibault.fr"]].
+
IRC, OFTC, #debian-hurd, 2012-04-27:
<Steap> Does anyone have any idea why int main(void) { return
@@ -304,7 +309,7 @@ Last reviewed up to the [[Git mirror's d3bd58cf0a027016544949ffd27300ac5fb01bb8
We should be easily able to implement that one.
- * `futimesat`, `readlinkat`
+ * `futimesat`
If we have all of 'em (check Linux kernel), `#define __ASSUME_ATFCTS`.
@@ -411,6 +416,9 @@ Last reviewed up to the [[Git mirror's d3bd58cf0a027016544949ffd27300ac5fb01bb8
* In `sysdeps/unix/sysv/linux/Makefile`, there are a bunch of
`-DHAVE_SENDFILE` -- but we do have `sendfile`, too.
+ Define `__ASSUME_SENDFILE` to 1 in `kernel-features.h`, if `sendfile`
+ works.
+
* `/usr/include/pthread.h` overwrite issue
`make`, after editing `nss/nss_db/db-initgroups.c`:
@@ -1121,6 +1129,14 @@ There is quite a baseline of failures.
* `posix/tst-getconf`
+ It fails because of unimplemented pathconf cases: `_PC_ALLOC_SIZE_MIN`,
+ `_PC_REC_INCR_XFER_SIZE`, `_PC_REC_MAX_XFER_SIZE`, `_PC_REC_MIN_XFER_SIZE`,
+ `_PC_REC_XFER_ALIGN`, `_PC_SYMLINK_MAX`, `_PC_2_SYMLINKS`.
+
+ `_CS_GNU_LIBPTHREAD_VERSION` will be cleanly solved with
+ [[!message-id "201209302353.51055.toscano.pino@tiscali.it"]] and libpthread
+ compiled as add-on.
+
Ends with:
getconf POSIX_ALLOC_SIZE_MIN /: /home/thomas/tmp/glibc/tschwinge/Roger_Whittaker.build-gcc-4.4-486/posix/getconf: pathconf: /: Invalid argument
diff --git a/open_issues/glibc/getlogin_r.mdwn b/open_issues/glibc/getlogin_r.mdwn
deleted file mode 100644
index 9980ea1f..00000000
--- a/open_issues/glibc/getlogin_r.mdwn
+++ /dev/null
@@ -1,45 +0,0 @@
-[[!meta copyright="Copyright © 2012 Free Software Foundation, Inc."]]
-
-[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
-id="license" text="Permission is granted to copy, distribute and/or modify this
-document under the terms of the GNU Free Documentation License, Version 1.2 or
-any later version published by the Free Software Foundation; with no Invariant
-Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
-is included in the section entitled [[GNU Free Documentation
-License|/fdl]]."]]"""]]
-
-[[!meta title="getlogin_r"]]
-
-[[!tag open_issue_glibc]]
-
-
-# IRC, freenode, #hurd, 2012-04-23
-
- * pinotree spots how our getlogin_r() implementation uses a static
- buffer...
- <braunr> oO
- <pinotree> braunr: yeah, the _r means "reentrantbutnotreally" xD
- <braunr> pinotree: that's amazing ..
- <antrik> pinotree: without having checked the actual implementation, that
- doesn't sound like a problem...
- <antrik> caching doesn't break reentrancy. the problem with the plain
- getlogin() is that a static buffer is *returned to the user*
- <pinotree> antrik: http://paste.debian.net/164727/
- <braunr> ah, caching
- <pinotree> i don't think this is caching at all
- <antrik> pinotree: OK, not actually caching... but same effect as far as I
- can tell
- <antrik> pinotree: or is it the fixed size of the temporary variable you
- are concerned about?
- <pinotree> antrik: my concern was about the "static" of the buffer used for
- the get_login rpc
- <antrik> pinotree: I'm not sure that's a problem. can the login actually
- ever change for a running process?
- <pinotree> dunno
- <pinotree> but if so, it would be pointless to do the rpc every time
- instead of just once
- <antrik> pinotree: true
- * pinotree would just make it non-static and be safe
- <antrik> pinotree: well, one might argue that allocating a KiB of stack
- space is not very friendly, especially in a low-level library...
- <antrik> not sure what the general policy is about such things in libc
diff --git a/open_issues/libasyncns.mdwn b/open_issues/libasyncns.mdwn
deleted file mode 100644
index bbd34bff..00000000
--- a/open_issues/libasyncns.mdwn
+++ /dev/null
@@ -1,19 +0,0 @@
-[[!meta copyright="Copyright © 2010 Free Software Foundation, Inc."]]
-
-[[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable
-id="license" text="Permission is granted to copy, distribute and/or modify this
-document under the terms of the GNU Free Documentation License, Version 1.2 or
-any later version published by the Free Software Foundation; with no Invariant
-Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license
-is included in the section entitled [[GNU Free Documentation
-License|/fdl]]."]]"""]]
-
-[[!tag open_issue_porting]]
-
-IRC, unknown channel, unknown date.
-
- <pinotree> tschwinge: btw, would you be able to tell if and what's wrong with a socket-related problem?
- <pinotree> it is reproducible with a very small self-contained C library
- <pinotree> http://0pointer.de/lennart/projects/libasyncns/
- <pinotree> it has a test case with it, which fails
- <pinotree> tschwinge: if that can ring some bell, imho the problem is related to SOCK_STREAM sockets created with socketpair and used with send/recv
diff --git a/open_issues/nice_changes_priority_of_parent_shell.mdwn b/open_issues/nice_changes_priority_of_parent_shell.mdwn
index d731ef82..a8a08f90 100644
--- a/open_issues/nice_changes_priority_of_parent_shell.mdwn
+++ b/open_issues/nice_changes_priority_of_parent_shell.mdwn
@@ -10,6 +10,6 @@ License|/fdl]]."]]"""]]
[[!tag open_issue_gnumach open_issue_glibc]]
- * <http://bugs.debian.org/44039>
+ * [[!debbug 44039]]
* Also see [[nice_vs_mach_thread_priorities]].
diff --git a/open_issues/nice_vs_mach_thread_priorities.mdwn b/open_issues/nice_vs_mach_thread_priorities.mdwn
index e6b68134..6a890eca 100644
--- a/open_issues/nice_vs_mach_thread_priorities.mdwn
+++ b/open_issues/nice_vs_mach_thread_priorities.mdwn
@@ -11,7 +11,7 @@ License|/fdl]]."]]"""]]
[[!tag open_issue_gnumach open_issue_glibc]]
This issue has been known for some time, due to coreutils' testsuite choking
-when testing *nice*: <http://bugs.debian.org/190581>.
+when testing *nice*: [[!debbug 190581]].
There has been older discussion about this, too, but this is not yet captured
here.
diff --git a/open_issues/thread-cancel_c_55_hurd_thread_cancel_assertion___spin_lock_locked_ss_critical_section_lock.mdwn b/open_issues/thread-cancel_c_55_hurd_thread_cancel_assertion___spin_lock_locked_ss_critical_section_lock.mdwn
index 72af3f35..cf41550d 100644
--- a/open_issues/thread-cancel_c_55_hurd_thread_cancel_assertion___spin_lock_locked_ss_critical_section_lock.mdwn
+++ b/open_issues/thread-cancel_c_55_hurd_thread_cancel_assertion___spin_lock_locked_ss_critical_section_lock.mdwn
@@ -12,7 +12,7 @@ License|/fdl]]."]]"""]]
[[!tag open_issue_hurd]]
-<http://bugs.debian.org/46859>, <http://bugs.debian.org/195360>
+[[!debbug 46859]], [[!debbug 195360]]
IRC, unknown channel, unknown date: