[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#692538: marked as done (gcc-snapshot: FTBFS on hurd-i386: hurd-pthread.diff applied upstream)



Your message dated Wed, 21 Nov 2012 01:37:39 +0100
with message-id <50AC2253.50103@debian.org>
and subject line fixed
has caused the Debian Bug report #692538,
regarding gcc-snapshot: FTBFS on hurd-i386: hurd-pthread.diff applied upstream
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
692538: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692538
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: gcc-snapshot
Version: 20121106-1
Severity: important
Tags: patch

Hello,

hurd-pthread.diff was applied upstream, so please remove it from
gcc-snapshot, see attached change in rules.patch

Samuel

-- System Information:
Debian Release: wheezy/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.0.4 (SMP w/8 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

-- 
Samuel
N: beep beep Miam miam? 
y: ++
a: kill -MIAM -1
--- debian/rules.patch.orig	2012-11-07 11:00:06.000000000 +0100
+++ debian/rules.patch	2012-11-07 11:00:11.000000000 +0100
@@ -238,7 +238,7 @@
 endif
 
 ifeq ($(DEB_TARGET_ARCH_OS),hurd)
-  debian_patches += hurd-pthread hurd-changes
+  debian_patches += hurd-changes
 endif
 
 debian_patches += gcc-ice-hack gcc-ice-apport

--- End Message ---
--- Begin Message ---
fixed in the 20121120 upload.

--- End Message ---

Reply to: