Please SRU ghc6 in Hardy to fix correctness bug
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
darcs (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Hardy |
Invalid
|
Undecided
|
Unassigned | ||
ghc6 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Hardy |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: ghc6
Hello all,
The version of GHC in Hardy has an important correctness bug in the getSymbolicLink
There are two choices:
1) Simply upload the version in Intrepid to Hardy with a suitably modified version number. There have been only bug/buildfix updates to the package between the two releases, as evidenced by the changelog:
ghc6 (6.8.2-6ubuntu2) intrepid; urgency=low
* libraries/
<http://
accessing getSymbolicLink
LP: #263773.
* Run autoreconf in libraries/unix so that the configure.ac change
takes effect.
* debian/control: Set Maintainer from myself to MOTU.
-- Stefan Potyra <email address hidden> Sat, 27 Sep 2008 22:19:03 +0200
ghc6 (6.8.2-6ubuntu1) intrepid; urgency=low
* Merge from Debian unstable (LP: #270601), remaining changes:
+ make lpia similar to i386 in debian/rules
+ add lpia to debian/ghc6_vars via debian/rules
+ add manpage for runghc
-- Iain Lane <email address hidden> Mon, 15 Sep 2008 20:26:40 +0100
ghc6 (6.8.2-6) unstable; urgency=medium
* New maintainer.
* Made the perl script driver/
var (Closes: #489157)
* Copied libraries/
libraries/
setResource
-- Kari Pahula <email address hidden> Wed, 03 Sep 2008 23:41:18 +0300
ghc6 (6.8.2-5ubuntu1) intrepid; urgency=low
* Rebase to unstable, remaining changes:
+ make lpia similar to i386 in debian/rules
(Adam Conrad who thanked Ian Lynagh).
+ add lpia to debian/ghc6_vars via debian/rules (Adam Conrad).
+ add manpage for runghc (Efrain Valles Pulgar), referring to
LP bug #95985. Added: debian/runghc.man, and modified
debian/rules.
+ change Maintainer field to myself in debian/control.
-- Stefan Potyra <email address hidden> Sat, 10 May 2008 12:19:35 +0200
ghc6 (6.8.2-5) unstable; urgency=low
* Don't build template-haskell if we're not building GHCi.
The package is largely useless without GHCi, and some of the buildds
were having trouble building template-haskell. We'll need to fix
this some other way if GHCi is to be available on every arch, though...
-- Ian Lynagh (wibble) <email address hidden> Thu, 01 May 2008 12:32:13 +0000
ghc6 (6.8.2-4) unstable; urgency=low
* Small wibbles to debian/watcher.sh.
* Add a build-dep on procps (debian/watcher.sh runs ps).
-- Ian Lynagh (wibble) <email address hidden> Wed, 26 Mar 2008 17:12:18 +0000
ghc6 (6.8.2-3) unstable; urgency=low
* Every 10 minutes, print any "ps ux" lines that mention gcc or ghc.
According to folks on IRC, this is standard practice. It means that
we don't have to worry about security buildds having different
timeouts to the normal builders.
* Apply upstream patch:
FIX #2073: Don't add empty lines to GHCI's history
Ian Lynagh <email address hidden>
Closes: #461170.
-- Ian Lynagh (wibble) <email address hidden> Mon, 24 Mar 2008 22:09:02 +0000
None of these changes are intrusive and would have any unwelcome side-effects.
2) Backport the important fix from bug #263773. This is the fix that we really want as it is both a correctness bug and a performance bug in Darcs. If option 1 is unpalatable then I would urge that we at least do this. sistpoty has analysed the ABI and determined that the fix does not change it, so the chance for regressions is slim to none.
MOTU-SRU members, please determine if option 1 is appropriate, or if not then please accept option 2.
Thank you for your time,
Iain
Just to add:
Personally I'm in favor of just using the current intrepid version. It has seen a round of testing now, and less changes mean less chances to break.
Some test-cases for the bugs:
TEST CASE 1, concerning bug #263773:
Test the following on an 32bit system (e.g. i386). Unfixed, it will give random results (should be: inode number)
<code>
import System.Posix.Files
main = do Posix.Files. getFileStatus "/" >>= print . System. Posix.Files. fileID
System.
</code>
TEST CASE 2, concerning bug #270601 is listed in that bug.
For the watcher.sh/printing s.th. every 10 minutes: Most probably it won't build on sparc due to timing out (see bug #194912, prior to that change it needed manual buildd admin intervention).