27;t yet have arm64 support; that
will happen in time.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
lerDebacle
This bug is not itself RC, but it will be a blocking issue for RC bugs
I'm about to file.
I intend to submit a patch for this shortly.
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
until 2022. So
I'm tentatively filing this bug as RC-severity.
Further context and an overview of related bugs will be published at:
https://wiki.debian.org/InstallerDebacle
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
supported release until 2022. So
I'm tentatively filing this bug as RC-severity.
Further context and an overview of related bugs will be published at:
https://wiki.debian.org/InstallerDebacle
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
p (buf, sum, 32))
Further context and an overview of related bugs will be published at:
https://wiki.debian.org/InstallerDebacle
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
9
if (item->sum[1])
return check_sum (target, "sha1sum", item->sum[1], buf_name);
if (item->sum[0])
return check_sum (target, "md5sum", item->sum[0], buf_name);
Further context and an overview of related bugs will be published at:
https://wiki.debian.org/Insta
nd the testsuite to check parsing of the
SHA256 fields; that also would result in a larger diff however.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/debian/changelog b/debian/changelog
index 3dd29e1..1b7fcd8 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,7 +1,16 @@
l
t use
the md5sums field, and the struct size is not changing); though if they
do use, I'd prefer they FTBFS so that we find out.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
bizarre that we've published SHA256 sums in the
archive since 2007 and *still* don't use them here. I think there is a
greater risk that we forget, or be too lazy, than we do this 'too soon'.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
Hi,
Bastian Blank wrote:
> This change breaks the existing ABI and therefor needs an ABI bump, but
> it is missing from the patch.
I agree, that should be done. Thanks.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
hed log.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
/usr/bin/sha256sum /tmp/net-retriever-1817-Packages
/usr/bin/sha256sum /tmp/net-retriever-1872-Packages
/usr/bin/sha256sum /tmp/net-retriever-1872-Packages
/usr/bin/sha256sum /tmp/net-retriever-1872-Packages
/usr/bin/md5sum /var/cache/a
entation needed
to change then.
In the ideal world, the code itself would be the clear, authoritative
reference of what it is doing. I wish that we can remove all references
to md5 and sha1 there.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
ncrease it if changing SHA256 to SHA512 in the future. A
more thorough rework of this code might store the hash type (as an enum)
and length, in the di_package struct instead.
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
Steven Chamberlain wrote:
> Attached is [...]
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/anna.c b/anna.c
index 4b68816..e03d34a 100644
--- a/anna.c
+++ b/anna.c
@@ -318,8 +318,8 @@ install_modules(di_packages *status, di_packages *packages) {
}
}
-
which remains the same length). The
dynamically-sized buffer it points to, would change from storing an MD5
to a SHA256 hash, and would only cause a regression where something is
still trying to validate MD5).
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/configure.ac b/configure.ac
Thanks for your comments!
Cyril Brulebois wrote:
> Steven Chamberlain (2017-02-27):
> > (If we really wanted, we could maybe avoid the ABI bump: [...]
>
> Given the number of reverse dependencies, I doubt this is worth abusing
> md5 storage for sha256 things.
Maybe I should
Steven Chamberlain wrote:
> replace sum[0] with sha256 and leave sum[1] empty;
> [...] (we would drop the MD5- and SHA1-parsing code
> and make absolutely sure nobody is still using those).
The new patch attached would do that, and it remains otherwise
ABI-compatible.
It aims to be
Updated patch, which assumes the libdebian-installer4-dev package will
not be renamed. Build-Depend on a recent enough version that provides
sha256 fields.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/debian/changelog b/debian/changelog
index d6682ca..20e33a0 100644
--- a
Control: tags -1 + patch
Hi,
The attached patch is based on having
libdebian-installer_bug856210_v3.patch applied:
* libdebian-installer4-dev would not change its name
* sum[1] is already empty/unusable
* sum[0] would become the sha256 field
Thanks,
Regards,
--
Steven Chamberlain
ste
ebian.org/debian-release/2017/02/msg01033.html
I think we should wait for them to answer before doing anything else.
Based on KiBi's feedback I thought it better to swap sum[0] and sum[1],
and remove the SHA1 parsing also.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Descri
Bastian Blank wrote:
> On Tue, Feb 28, 2017 at 10:00:01PM +0000, Steven Chamberlain wrote:
> > That differs from the latest version of my patch, and from what I sent
> > earlier today to the release team when asking about a potential unblock:
> > https://lists.debian.org/d
sonal interactions beyond that, is just too
much. That is the real "debacle"; it is not surprising to me now, that
this did not happen yet in 10 years, or that no enthusiastic new
contributor had already done this.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Descr
Package: libblkmaker
Version: 0.5.3-1
Severity: grave
Tags: fixed-upstream
Hi,
The version of libblkmaker in sid/stretch supports bitcoin blocks up to
version 4 only:
http://sources.debian.net/src/libblkmaker/0.5.3-1/blkmaker.h/#L15
But since early 2016, the tip of the blockchain uses predemonan
Package: kfreebsd-10
Version: 10.1~svn274115-9
Severity: grave
Tags: security upstream patch
Hi,
Local users can trigger a kernel panic, or possibly escalate privileges,
by exploiting a flaw in the IRET handler in kfreebsd-9 and -10:
https://www.freebsd.org/security/advisories/FreeBSD-SA-15:21.am
m_bus_socket: No such file or directory)
Did you try rebooting the machine before starting Xorg? Perhaps you
could find something relevant in your logs with:
$ cd /var/log && sudo grep dbus dpkg.log syslog
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
severity 868929 important
thanks
(linux-)amd64 is not in this package's Architectures: field, therefore
FTBFS on that arch cannot be a RC bug? (Though I'd be interested in
fixing it someday).
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
or is fatal, and
causes a "fail-whale" with only an option to log out.
Probably GNOME is not suitable for that hardware, then. It was a really
unfortunate experience for the (first-time) user, though.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
(again) to build it on linux.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: Digital signature
le: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: sysvinit (via /sbin/init)
Date: Fri, 27 Mar 2020 21:26:21 +
From: Steven Chamberlain
Subject: Add extra libs required to build aicasm
--- a/sys/dev/aic7xxx/aicasm/Makefile
+++ b/sy
Package: src:mame
Version: 0.178-1
Severity: serious
Justification: FTBFS, but built successfully in the past
Hi,
On linux-arm64, mame since 0.176-3 FTBFS, because:
https://buildd.debian.org/status/fetch.php?pkg=mame&arch=arm64&ver=0.178-1&stamp=1475578747
| Compiling src/emu/emumem.cpp...
| g++
ent, it looks to me like the initscripts in the base system
don't depend on implied (indirect) child dependencies. Perhaps
deliberately, or else the dependency graph would become more complex and
probably more difficult to maintain in the long run.
p.s., I made a pretty graph of this: http://p
n libdbd-pgsql (no description available)
pn libdbd-sqlite3 (no description available)
-- no debconf information
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
wi
ose files for writing, and that must be when permissions are changed.
If anything new has been written to your auth.log or daemon.log since
you checked, I think the permissions will have changed now.
Maybe that helps to narrow down where in the code this is happening?
Regards,
--
S
ested in affile_open_file to see if it's >= 0. Could the size or
signedness of mode_t be different on FreeBSD to Linux, resulting in the
0x?
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject
ed patch, which I've only managed to
build on amd64 yet and not kFreeBSD, so it hasn't been properly tested.
Fortunately the uid/gid types are still u32 on kFreeBSD so there is no
issue with those.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff -Nru syslog-ng-3.1.3.orig/src/af
ing of
dir_perm(), or otherwise 0700 if it wasn't defined. Directories that
have already been created by syslog-ng are never chmod'd again, so won't
be automatically fixed by this patch.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-r
Package: grub-installer
Version: 1.84
Severity: grave
Tags: d-i
User: debian-...@lists.debian.org
Usertags: kfreebsd
X-Debbugs-Cc: debian-...@lists.debian.org
Hi,
Wouter's workaround for bug #681227 now requires that GRUB's target is a
block device (and was amended to allow dummy targets as well)
as well. If
it does trigger a FTBFS, it's because we missed something, or something
wrong with the build environment that we need to know about. We might
need to drop it someday for a new upstream release but hopefully not.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCR
]; then
> continue
> fi
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
if [ ! -b $bootdev -a $bootdev != dummy ]; then
+ if ! [ "$bootdev" = dummy -o -b "$bootdev" -o -c "$bootdev" ];
then
continue
fi
grub_install_params=
if ! is_floppy "
On 29/12/12 16:47, Steven Chamberlain wrote:
> I can provide a similar patch for freebsd-utils which has the same
> issues, but the only problem I could confirm yet was a segfault in
> ifconfig bridge configuration (#696514) due to it.
Attached is a similar patch for freebsd-util
g those as they are and I haven't enabled the
-Werror flag for this package yet.
Thanks!
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
ting for kernels, I think it is preferred that you
test for __FreeBSD_kernel__, instead of just __FreeBSD__ which is a bit
ambigious, and only defined on a pure FreeBSD (with BSD libc) system.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.d
or GNU/Hurd
Yet more examples:
http://codesearch.debian.net/search?q=BSD.*BSD_kernel.*BSD
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
On 31/12/12 17:06, Dirk Eddelbuettel wrote:
> On 31 December 2012 at 16:36, Steven Chamberlain wrote:
> | So Dirk, I think we now have this horror:
> |
> | #elif defined(linux) || defined(__linux) || defined(__FreeBSD__) ||
> | defined(__FreeBSD_kernel__) || defined(__NetBSD__)
middot which I'm not sure how you would type, and finally
... ']... enter key?
On a QWERTY keyboard these sequences of keys are all adjacent!
To the original submitter of the bug report: do you have a cat?
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
signature.asc
Description: OpenPGP digital signature
: info: Installing grub on '/dev/sdb
>>> w33sxs34rfvbg789iokm·']'
> On 02/01/13 22:49, Steven Chamberlain wrote:
>> To the original submitter of the bug report: do you have a cat?
>
> No. The machine is my work desktop. I do have a QWERTY keyboard
>
9 926cee22
Of course there are still ways to improve, e.g. offering a list of
partitions to choose from instead of free-text input, but anything like
that must surely wait until another release.
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
diff --git a/grub-installer b/grub-installer
ind
ng of this situation into the installer is now
probably not possible, due to string freeze.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
CVE-2012-5083 - 2D
Is it safe to say that's because these issues did not affect OpenJDK?
Thank you very much for your help,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". T
that
britney/UDD/apt-listbugs sees that it is not RC-buggy.
Thanks!
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
e instead of an embedded copy?
The libjs-jquery/1.7.2 package seems it was already immune to this
issue. (Proof of concept at http://ma.la/jquery_xss/ - save it locally
and you can swap out the jquery.js to test other versions).
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBS
t know.
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
sure why you were seeing egid=27, but user 'michael' was already
a member of that group.
Only the superuser can use initgroups()... so I'm not sure this is a
security problem?
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.deb
ase there is some other problem.
Thank you,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
that later (it won't be release-critical though).
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
Index: psmisc-22.19/src/pstree.c
===
--- psmisc-22.19.orig/src/pstree.c 2012-05-20 00:10:36.0 +0100
+++ psmisc-22.19/src
oned in the docs unfortunately.)
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
ck-recursive] Error 1
> make[1]: Leaving directory `/tmp/tmp.qZtvS03tZP/procps-3.3.3'
> dh_auto_test: make -j1 check returned exit code 2
> make: *** [build] Error 29
> dpkg-buildpackage: error: debian/rules build gave error exit status 2
By the way, I also noticed this whi
hangelogs of
1.12.2-2+deb7u2 have been deleted.
Let's hope this problem is fixed in 1.12.2-3 now available in sid:
http://cdn.debian.net/debian/pool/main/c/cairo/
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with
-p-u).
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
4 (x86_64)
Kernel: kFreeBSD 9.0-2-amd64-xenhvm
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Author: Steven Chamberlain
Description: This patch avoids FTBFS due to wrong calculation of timeout
If the current minute or second wraps around past 59
, but now we have
found the true cause of it I think).
Thanks!
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
her than if it is dropped and they are left with the last version
that oldstable had.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
bpo.5-openvz-amd64:
*
linux-image-2.6.32-bpo.5-openvz-amd64/postinst/missing-firmware-2.6.32-bpo.5-openvz-amd64:
linux-image-2.6.32-bpo.5-openvz-amd64/prerm/removing-running-kernel-2.6.32-bpo.5-openvz-amd64:
true
linux-image-2.6.32-bpo.5-openvz-amd64/postinst/depmod-error-initrd-2.6.32-bpo.
e
APT policy: (500, 'oldstable'), (500, 'testing'), (500, 'stable')
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
on-apt where there's a
FIXME regarding a possible memory leak. But the segfault seems to be
happening whether progress reporting is requested or not.
In any case I think this bug ought to be reassigned to the python-apt
package, whose authors will know much more about this than I do.
Regards,
?? ()
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
t this package is removed from testing,
so that it is not released with Squeeze.
Many thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
RLF to LF conversion (fromdos), and a modification to
apply with 'patch -p1' (sed -i 's/src/openttd\/src/'). The direct URL
to it is:
http://security.openttd.org/en/patch/28.patch
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-re
code in two places that would not
compile on systems other than Linux.
The result builds and appears okay when quickly tested kfreebsd-i386.
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
Description: fix to build on non-Linux arches
Fix the build where it seems a code fix for Linux was
needed now in your patch to fix Gem/Dylib.cpp (due
to #673286 affecting a piece of kFreeBSD-specific code I think).
Please see attached. Tested with a successful build on kfreebsd-i386.
Thanks!
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
Index: gem-0.93.3/src/Gem/Dylib.cpp
egory will have unistd.h; and as of GCC-4.7 they are
going to have to include it.
Thanks!
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
Description: fix GCC 4.7 build on 'other' platforms like GNU/kFreeBSD
Assume that all platforms in the 'other' category will have unistd.
ePattern(Pattern) is undefined for the type Matcher
> [javac] --
> [javac] 71 problems (2 errors, 69 warnings)
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
bar!"; <>'
Hi Axel,
I recall that setproctitle was implemented as a no-op in libbsd. So
that is probably a known bug / unimplemented yet.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a
n became available) :
> setproctitle() NOT found.
and it can't find prctl (Linux) either:
> prctl() NOT found.
This leaves Perl_magic_set() in mg.c non-functional.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
w
more.
This used to happen when a bundled via_drm.h included via_drmclient.h.
Now the system's has replaced it, but that includes
drm.h before via_drmclient.h, using the C99 integer types without
including stdint.h first.
Therefore the openchrome 0.2.904+svn1050 package (still) builds on
kfree
e_drv can build again:
--- /usr/include/libdrm/drm.h.orig
+++ /usr/include/libdrm/drm.h
@@ -46,6 +46,7 @@
#include
#include
+#include
typedef int8_t __s8;
typedef uint8_t __u8;
typedef int16_t __s16;
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email t
__s64;
+typedef __uint64_t __u64;
typedef unsigned long drm_handle_t;
#endif
Thanks!
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
gards,
--
Steven Chamberlain
ste...@pyro.eu.org
Description: include stdint.h, a prerequisite of via_drm.h on BSD
Must include stdint.h here because it is a prerequisite of drm.h
(which gets included from via_drm.h).
.
Fixes a FTBFS seen on GNU/kFreeBSD.
Author: Steven Chamberlain
Bug-Debian:
needs a new
upload. The others can use the patch from the advisory.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hi,
I think this was due to GCC PR c++/26155 and fixed in gcc-4.7 4.7.0-13.
After that version becomes available on the amd64 buildds, please could
it be given back for rebuild?
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ
Hi,
I think this was also due to GCC PR c++/26155 and fixed in gcc-4.7
4.7.0-13. After that version becomes available on the i386 buildds,
please could it be given back for rebuild?
Thanks,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ
ml
[3]
http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=35;filename=20-BSD-stdint-prerequisite.diff;att=1;bug=677260
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
all of them.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
al CPU version 1.0
> stepping: 3
>
> flags : fpu de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov
> pat pse36 b19 mmx fxsr xmm sse2
> cpu MHz : 2500.04
> bogomips: 2500.04
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
T
made it usable again.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
t on demand. Sorry for the inconvenience!
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
./../sys/cddl/compat/opensolaris/sys/types.h:60:1:
> error: unknown type name ‘id_t’
> /home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../sys/cddl/compat/opensolaris/sys/types.h:61:1:
> error: unknown type name ‘mode_t’
> /home/steven/zfs
ether to include this header?
It looks to me like it would work.
This way we'd be helping out GNU/Hurd at the same time, the fix would be
more appropriate for upstream and it helps with future portability.
Thanks again,
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE,
AF_LINK being
defined on a platform, and the existence of a net/if_dl.h containing the
definition of sockaddr_dl.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
for
FreeBSD || FreeBSD_kernel would not be appropriate. It might "work" but
would only replace one portability issue with another.
The new test for AF_LINK && !GNU looks even worse to me. Does GNU/Hurd
_really_ define AF_LINK and yet not provide a net/if_dl.h with a
definition for sock
On 20/06/12 22:09, Nicholas Bamber wrote:
> On 20/06/12 22:04, Steven Chamberlain wrote:
>> This debdiff doesn't address the main point of my original mail:
>> sockaddr_dl and net/if_dl.h are not (k)FreeBSD-specific, so a test for
>> FreeBSD || FreeBSD_kernel would not
#x27;m fine with that, as it would be consistent, and it addresses the most
important point which was the original test for (k)FreeBSD being too
specific.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of &qu
u're right, it's fine now in up-to-date sid chroot.
I'd originally tried to build it in a Wheezy environment that hadn't
been updated in a while. This problem is gone after updating to the
latest freebsd-buildutils in Wheezy.
Thanks for reviewing and applying the patch.
,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hi,
This bug prevents gcc-4.6 from migrating to testing with
important-severity bug fixes as peter explains:
http://lists.debian.org/4fe22188.9020...@p10link.net
Is it still the Release Team's wish to roll back the change at this late
stage?
Regards,
--
Steven Chamberlain
ste...@pyro.e
binaries" as a
dependency, which provides the missing pdftex. I think that package
needs to be added to Build-Depends.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Package: libwebkitgtk-1.0-0
Version: 1.8.1-3.3
Followup-For: Bug #651636
Still frequently crashing on mipsel with 1.8.1-3.3 :
Program terminated with signal 11, Segmentation fault.
#0 0x7562b9d4 in WTF::fastFree(void*) ()
from /usr/lib/libjavascriptcoregtk-1.0.so.0
No symbol table info availa
Package: libapache2-mod-php5filter
Version: 5.4.4-7
Severity: grave
File: /etc/apache2/mods-available/php5filter.conf
Tags: security
Hi,
I just tested a dist-upgrade from squeeze -> wheezy on a system that was
using libapache2-mod-php5 to run conventionally-named .php scripts.
Immediately after
ble memory has to be at least
the size of an uncompressed kernel image, plus the value set for
MFSROOT_LIMIT, and still leave enough for the d-i userland.
Regards,
--
Steven Chamberlain
ste...@pyro.eu.org
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of &q
1 - 100 of 718 matches
Mail list logo
