Iceweasel and chromium stable and secure versions

2013-02-28 Thread Henry Jensen
Hello,

I noticed that chromium got updated to the newest stable and secure
version 25.0.1364.97. Can we expect that Chromium will receive further
updates in the future during the lifetime of Debian 7.0, perhaps as
part of the Update-Repository (formerly known as volatile)?

And what about Iceweasel. Upstream Firefox 10.x is EOL now. 

Regards,

Henry



-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20130228181813.dc7b44d0.hjen...@gmx.de



3dm2 and iceweasel/firefox 10 - Connection reset

2012-02-27 Thread Henry Jensen
Hello,

I am running 3dm2 from http://hwraid.le-vert.net/ on several Debian boxes.

Since the upgrade to iceweasel 10, I can't connect to the 3dm2 web interface 
any more and get a The connection was reset error page instead. Other 
browsers are still working. 
It is only the combination Iceweasel 10 and 3dm2. 

On a windows box with Firefox 10 shows the same behavior - connection reset. A 
shot analysis with wireshark shows indeed that the 3dm2 builtin https server 
sends a RST. Firefox 3.6.x works.

Can anyone confirm that the 3dm2 web interface isn't working with 
iceweasel/firefox 10?

Regards,

Henry







-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120227162047.fd083797.hjen...@gmx.de



kernel source package with applied patches

2011-08-15 Thread Henry Jensen
Hello,

I plan to create a source tarball of the Debian Linux kernel with
patches already applied in oder to build a kernel, based on Debian
kernel sources, on other, non-Debian based distros.

As far as I can tell I must do it the following way.

- Download linux-2.6_[version].orig.tar.gz
- Download linux-2.6_[version]-[patchlevel].dsc
- Download linux-2.6_[version]-[patchlevel].diff.gz

- Running dpkg-source -x linux-2.6_[version]-[patchlevel].dsc

This produces the directory linux-2.6-[version]. Patches aren't applied
yet and can be found at the subdirectory debian/patches.

To apply the patches I run

- fakeroot debian/rules source

Now I can see that the patches are applied. According to
http://kernel-handbook.alioth.debian.org/ch-common-tasks.html the
patched kernel source is now at debian/build/source. So all I must do
is to create a tarball of that subdirectory. Am I correct so far?

Regards,

Henry


-- 
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org 
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110815154218.20c85c6b.hjen...@gmx.de



Can't recompile kernel any more

2008-02-14 Thread Henry Jensen
Hello,

I regularly re-compile the Debian Linux kernel because I need 
capability build as a module. This is because I use dazuko, an interface
for on-access virus scanners (see www.dazuko.org). Dazuko depends
on having capability built as a module. 

The only thing I do is to set 
CONFIG_SECURITY_CAPABILITIES=y
to:
CONFIG_SECURITY_CAPABILITIES=m
in debian/arch/config

This worked until now. Now, with 2.6.18.dfsg.1-18etch1, I get the following 
error:


python2.4 debian/bin/abicheck.py debian/build/build-i386-none-486 i386 none 486
ABI has changed!  Refusing to continue.

Changed symbols:
cap_bprm_apply_creds module: vmlinux - 
security/commoncap
cap_bprm_secureexec  module: vmlinux - 
security/commoncap
cap_bprm_set_securitymodule: vmlinux - 
security/commoncap
cap_capable  module: vmlinux - 
security/commoncap
cap_capget   module: vmlinux - 
security/commoncap
cap_capset_check module: vmlinux - 
security/commoncap
cap_capset_set   module: vmlinux - 
security/commoncap
cap_inode_removexattrmodule: vmlinux - 
security/commoncap
cap_inode_setxattr   module: vmlinux - 
security/commoncap
cap_netlink_recv module: vmlinux - 
security/commoncap
cap_netlink_send module: vmlinux - 
security/commoncap
cap_ptrace   module: vmlinux - 
security/commoncap
cap_settime  module: vmlinux - 
security/commoncap
cap_syslog   module: vmlinux - 
security/commoncap
cap_task_post_setuid module: vmlinux - 
security/commoncap
cap_task_reparent_to_initmodule: vmlinux - 
security/commoncap
cap_vm_enough_memory module: vmlinux - 
security/commoncap
make[2]: *** [debian/stamps/build-i386-none-486-kernel-package] Error 1
make[2]: Leaving directory `/usr/src/deb/linux-2.6-2.6.18.dfsg.1'
make[1]: *** [build-i386-none-486-real] Error 2
make[1]: Leaving directory `/usr/src/deb/linux-2.6-2.6.18.dfsg.1'
make: *** [debian/stamps/build-base] Error 2

What can I do about this?


Regards,
Henry


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]