Bug#681922: sml-mode: can't be compiled with emacs24
Thanks for your bug report. However, I am no longer a Debian developer. Cheers, /JP (Sent from my phone) On 17/07/2012, at 22.00, Hilko Bengen ben...@debian.org wrote: Package: sml-mode Version: 4.1-2 Severity: serious Dear Maintainer, I tried installing sml-mode. Installation failed while it was being compiled for Emacs 24. Output is shown below. Cheers, -Hilko $ sudo apt-get install sml-mode [sudo] password for bengen: Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: sml-mode 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 58.3 kB of archives. After this operation, 258 kB of additional disk space will be used. Get:1 http://localhost/debian/ sid/main sml-mode all 4.1-2 [58.3 kB] Fetched 58.3 kB in 0s (168 kB/s) Selecting previously unselected package sml-mode. (Reading database ... 497625 files and directories currently installed.) Unpacking sml-mode (from .../sml-mode_4.1-2_all.deb) ... Processing triggers for install-info ... install-info: warning: no info dir entry in `/usr/share/info/ocaml.info.gz' Setting up sml-mode (4.1-2) ... Install emacsen-common for emacs Install emacsen-common for emacs23 install/sml-mode: Handling install for emacsen flavor emacs23 Wrote /usr/share/emacs23/site-lisp/sml-mode/sml-compat.elc Wrote /usr/share/emacs23/site-lisp/sml-mode/sml-proc.elc Wrote /usr/share/emacs23/site-lisp/sml-mode/sml-mode-startup.elc Wrote /usr/share/emacs23/site-lisp/sml-mode/sml-move.elc Wrote /usr/share/emacs23/site-lisp/sml-mode/sml-defs.elc Wrote /usr/share/emacs23/site-lisp/sml-mode/sml-mode.elc Wrote /usr/share/emacs23/site-lisp/sml-mode/sml-util.elc Install emacsen-common for emacs24 install/sml-mode: Handling install for emacsen flavor emacs24 Wrote /usr/share/emacs24/site-lisp/sml-mode/sml-compat.elc In toplevel form: sml-proc.el:93:1:Error: Constant symbol `:group' specified in defvar Wrote /usr/share/emacs24/site-lisp/sml-mode/sml-mode-startup.elc In toplevel form: sml-move.el:26:1:Error: Constant symbol `:group' specified in defvar In toplevel form: sml-defs.el:25:1:Error: Constant symbol `:group' specified in defvar In toplevel form: sml-mode.el:73:1:Error: Constant symbol `:group' specified in defvar In toplevel form: sml-util.el:25:1:Error: Constant symbol `:group' specified in defvar ERROR: install script from emacsen-common package failed dpkg: error processing sml-mode (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: sml-mode E: Sub-process /usr/bin/dpkg returned an error code (1) -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages sml-mode depends on: ii dpkg1.16.7 ii emacsen-common 2.0.3 ii install-info4.13a.dfsg.1-10 sml-mode recommends no packages. sml-mode suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#628590: make siggen depends on oss-compat
Hi, I am no longer a Debian Developer, so it would be great if someone else could take over or just upload the fix. Cheers, /JP -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#641348: New version of trac-mercurial
New version with bug fixes: http://dl.dropbox.com/u/4213259/deb/trac-mercurial_0.12.0.27%2Br10693-0.2.debian.tar.gz Cheers, -- Jens Peter Secher, GPG fingerprint 0EE5978AFE63E8A1. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#641348: trac-mercurial 0.12
Hi, the trac-mercurial package does not work well with Trac 0.12, so I have created an updated package: http://dl.dropbox.com/u/4213259/deb/trac-mercurial_0.12.0.27-0.1.debian.tar.gz It includes a get-orig-source target that extracts the source directly from SVN. I am no longer a DD so I cannot upload, but I have a number of other trac-related packages for Trac 0.12 lying around: trac-autocompleteusers 0.4.2 trac-batchmodify 0.8.0 trac-estimationtools 0.4.5 trac-wikiprint 1.8.4 None of them are signed AFAIR, but I can sign them and make available if needed. Cheers, -- Jens Peter Secher, GPG fingerprint 0EE5978AFE63E8A1. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#621890: haxe kfreebsd buildd
On 2011-04-30 10:57, Mehdi Dogguy wrote: I removed it because it wasn't ready when we needed to migrate OCaml. Now OCaml migrated, haxe will migrate again as soon as it's fixed everywhere (e.g. on kfeeebsd-*). Besides, I don't see any reason to exclude haxe from kfeebsd-*, it should be able to build again (somehow). Great, thanks! Cheers, /JP -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#621890: haxe kfreebsd buildd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, it seem that me...@debian.org has somehow requested that haxe is removed from testing. I assume it is because it does not build on kfreebsd. (Is it?) Now, when I build the package manually on kfreebsd, it works fine. There have been such buildd problems before with the exact same error message. So, I cannot do anything about it. Does this mean that I have to exclude the haxe package from kfreebsd? Please advice. - -- Jens Peter Secher, GPG fingerprint 0EE5978AFE63E8A1. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iJwEAQECAAYFAk27PbkACgkQiFVdEFPVQL/0XAQAws6SPYnH8JbuNiuAZm0Fl8UN SgXijaAIdP8aoVMPBWw361W6Agy0OE7kfEFI95wX8Q4nK4kjE8WRU0q55JiRjgQE Lbwsff3VLuMU6ci0K/qhaaAZdub9FsZGRkZSxGJxiMD2E7uzAMRZe4wjFxvQGIOq UIgxnNXrSk6e2RA67Zk= =1Sso -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#621890: haxe kfreebsd buildd
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, it seem that me...@debian.org has somehow requested that haxe is removed from testing. I assume it is because it does not build on kfreebsd. (Is it?) Now, when I build the package manually on kfreebsd-amd64, it works fine. There have been such buildd problems before with the exact same error message. So, I cannot do anything about it. Does this mean that I have to exclude the haxe package from kfreebsd? Please advice. Cheers, - -- Jens Peter Secher, GPG fingerprint 0EE5978AFE63E8A1. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iJwEAQECAAYFAk27QqgACgkQiFVdEFPVQL9VhAP/YpbJ4KNDtS7LUx3zoV6Pdmcl L4SdMVp3v/1xONaAE7FTmVAfKBAetspUyMyoEG8NSt2hXhDGZtEASLgJmnyji6nT v77a2UVvKQBaLtjkFf8GH1AtFxMKcdgh1QPZX/RUdBecSxRPEnOSfXyCMm3xceWg MBaHitVYqmndmJZW8Jw= =BEYx -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#619856: Test suite failure on armel arch
Hi Wei Dai, have gotten access to the armel machines? Cheers, /JP -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#621890: haxe: FTBFS on kfreebsd-*: Uncaught exception - load.c(176) : Module not found : haxedoc.neko
This seems to be the same problem as Bug #557290, so I think the problem is in the buildd. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#619856: Test suite failure on armel arch
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wei Dai, can I get you to sign and send me an RSA SSH key? Then it should be possible for me to sponsor [1] an account for you on an armel machine [2]. Cheers, /JP [1] http://dsa.debian.org/doc/guest-account [2] http://db.debian.org/machines.cgi?host=abel -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iJwEAQECAAYFAk2ktUkACgkQiFVdEFPVQL+2BQP/YQQLCkKq9+Hivh/V/PaVdafF GPPtPclGTLm8ZlLWFD70vIENISBuscQTk2cijyJHsfTkz+JoqrckHZTllj0mN9XG zq5vWUCF0U1xlThHi4gzAVK53ibcx9M4tJwxLQWXEimhYfiE00ZNbjn3HwXeusNX 8DZ812F2tr1vhn1ZCrQ= =Hpjw -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582395: modifying files from another package
On 4 June 2010 20:01, Steve Langasek vor...@debian.org wrote: I see the profile contained in the package is /usr/share/pam-configs/silent-ssh-single-sign-on, but in the prerm you're calling 'pam-auth-update --package --remove pam-ssh'. The argument to pam-auth-update needs to be the name of the profile: i.e., silent-ssh-single-sign-on. Ahh, sorry about that. I will fix it. Cheers, -- Jens Peter Secher. _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#582395: modifying files from another package
pam-ssh uses pam-auth-update (from libpam-runtime) in postinst and prerm, as advocated in http://lists.debian.org/debian-devel/2009/03/msg3.html, so I guess piuparts is flawed. Cheers, -- Jens Peter Secher. _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572266: dovecot-common: dovecot-auth crashes with segfault
On 8 March 2010 14:38, Erich Schubert er...@debian.org wrote: * Use pam-auth-update together with the new setup file /usr/share/pam-configs/silent-ssh-single-sign-on to automatically enable the traditional functionality. My best guess is just that this new configuration setup caused the module to become activated while it wasn't before. So the bug could have been present for much longer when libpam-ssh was actually configured. I suspect you are right. I wonder whether there is a way to check for such errors automatically with lintian; they are bound to arise now and then, aren't they? I do not see how. Anyways, I will upload a new version of pamssh with proper prefixed names to avoid conflicts. Cheers, -- Jens Peter Secher. _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572266: Name conflicts with other PAM modules
I am working on prefixing all generic names with the prefix pamssh_ to avoid name conflicts with other PAM modules. -- Jens Peter Secher, GPG fingerprint 0EE5978AFE63E8A1. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#572266: dovecot-common: dovecot-auth crashes with segfault
Timo Sirainen wrote: And the problem is specifically that Dovecot also has buffer_free() function. Can you elaborate on this? Cheers, -- Jens Peter Secher, GPG fingerprint 0EE5978AFE63E8A1. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#569806: Please reschedule AMD64 build for mercurial-buildpackage
Please reschedule AMD64 build for mercurial-buildpackage: the new version of package neko should fix #569806. Cheers, -- Jens Peter Secher. _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#569806: [Neko] nekoml execve(2) strange behavior
On 20 February 2010 08:53, Jens Peter Secher j...@debian.org wrote: http://hg.debian.org/hg/collab-maint/neko/file/tip/debian/patches/kfreebsd-compile-fix.diff http://hg.debian.org/hg/collab-maint/neko/file/tip/debian/patches/kfreebsd-executable-path.diff and in addition I have the following in the Makefile: ## Both AMD64 and all kFreeBSDs seem to have problems with the type ## punning used in the Neko source. ifeq (amd64,$(DEB_HOST_ARCH)) cflags += -fno-strict-aliasing endif ifeq (kfreebsd,$(DEB_HOST_ARCH_OS)) cflags += -fno-strict-aliasing endif Well, the above does not solve all problems: A program suite (mercurial-buildpackage) which I have implemented in haXe gives the following error on GNU/kFreeBSD: haxe -neko mercurial-buildpackage.n -main MercurialBuildPackage -cmd 'nekotools boot mercurial-buildpackage.n' Uncaught exception - load.c(176) : Module not found : mercurial-buildpackage.neko I guess the mentioning of the .neko file must mean that something goes wrong in haxe/genneko.ml ? Cheers, -- Jens Peter Secher. _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#569806: Please reschedule AMD64 build for mercurial-buildpackage
neko-1.8.1-5 seems to have fixed the spurious stack overflows etc. which means that mercurial-buildpackage should build fine now. So if someone could reschedule AMD64 build for mercurial-buildpackage, it would be great. Cheers, -- Jens Peter Secher. _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#552954: libcrypto++: FTBFS: tests blocked
I think the loop is the result of this gas bug: http://sourceware.org/bugzilla/show_bug.cgi?id=10856 Matthias, is there a plan for your fix to be included in Debian? Cheers, -- Jens Peter Secher. _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546791: changetrack: shell command injection via filename
2009/9/17 Marek Grzybowski marek.grzybow...@atm.com.pl:
Andrzej Lemieszek (in CC) found few more, and He escaped them, so use rcs
should be safe to:
His patch:
[...]
+ my $realfile_esc = escape_shell_chars ($realfile);
[...]
- `cp $realfile $compfile`;
+ `cp $realfile_esc $compfile_esc`;
[...]
+sub escape_shell_chars
+{
+ my $arg = shift;
+ $arg =~ s/[;\*\|`\$!#\(\)\[\]\{\}:'\s]/\\$/g;
+ return $arg;
+}
This is not going work. When $realfile_esc is different from
$realfile, then it makes no sense to copy the non-existent
$realfile_esc. I will go for the solution of rejecting weird file
names.
Cheers,
--
Jens Peter Secher.
_DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_.
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#546791: changetrack: shell command injection via filename
Thanks for the bug report.
I am considering applying the following fix:
if( $realfile =~ m/[\r\n\f`\$]/ ) {
if(!$opt_q)
{ print Skipping non-sane filename '$realfile'\n;}
@diff = (@diff, Non-sane: '$realfile'\n);
next;
}
for outright rejecting weird filenames. Can you come up with other
problematic characters in filenames?
Cheers,
--
Jens Peter Secher.
_DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_.
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525071: libcrypto++ segfault on i386?
I cannot identify the exact place where things go wrong, so I have uploaded the following files to http://people.debian.org/~jps/segfault/ RandomFunctions.cpp amule libcrypto++8-dbg_5.6.0-2_i386.deb libcrypto++8_5.6.0-2_i386.deb The amule binary is non-stripped and the interesting point is the singleton in RandomFunctions.cpp, so you can set a break-point in the get() method. The exact shape of the singleton is my creation; the RandomFunctions.cpp looks a little different in the original amule, but the segfault appears in both implementations. The interesting thing is that the segfault does not happen in the exact same place when the RandomFunction is changed a bit. Therefore I suspect there could be some alignment problems, also considering that the segfault does not happen on x64. The -dbg package contains the debugging symbols for the crypto++ package. Cheers, -- Jens Peter Secher. _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525071: libcrypto++ segfault on i386?
the program on the way to this segfault, I noticed the following strange thing during construction of the SHA256: (gdb) bt full #0 SecBlock (this=0xbfd200f0, size=16) at secblock.h:283 No locals. #1 0xb7c1f051 in FixedSizeSecBlock (this=0xbfd200f0) at secblock.h:458 No locals. #2 0xb7c22b2f in IteratedHash (this=0xbfd200e0) at iterhash.h:56 No locals. #3 0xb7c60767 in AlgorithmImpl (this=0xbfd200e0) at simple.h:25 No locals. #4 0xb7c60799 in ClonableImpl (this=0xbfd200e0) at simple.h:17 No locals. #5 0xb7c62495 in IteratedHashWithStaticTransform (this=0xbfd200e0) at iterhash.h:88 No locals. #6 0xb7c62525 in SHA256 (this=0xbfd200e0) at sha.h:21 No locals. Am I right in thinking that SecBlock(size=16) looks odd considering that everything else in the trace use sizes of 32? Cheers, -- Jens Peter Secher. _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#525071: libcrypto++ segfault on i386?
2009/5/8 Wei Dai wei...@weidai.com:
I don't think that's it. 16 is the number of word32, and should be correct.
One problem is here:
[...]
Note that m_state.m_ptr = 0x0, which means m_state hasn't been constructed
when the segfault happened.
Ahh, thanks.
[...]
I see this:
key = (const byte *) 0xb7f70980 Z\213\f$\211\004$\213D$\004Â\f
This variable isn't in my copy of randpool.cpp. Is it something you added to
help debugging?
Yes, sorry I didn't mention this, but I modified randpool.cpp:
void RandomPool::IncorporateEntropy(const byte *input, size_t length)
{
SHA256 hash;
const byte *key = m_key;
hash.Update(key, 32);
hash.Update(input, length);
hash.Final(m_key);
m_keySet = false;
}
because it first seemed that the segfault happened in the cast operator.
If you can't figure this out, please send me instructions to reproduce the
bug.
Thanks, I will try some more now that I know what to watch. But just
in case; are you by any chance able to run on a Debian / Ubuntu
system? Because if you are, I could upload some unoptimised packages
with debugging symbols included which makes it easier to follow what
is going on.
Cheers,
--
Jens Peter Secher.
_DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_.
A. Because it breaks the logical sequence of discussion.
Q. Why is top posting bad?
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#519627: Update of haxe
I am in the process of making new versions of the haxe and neko packages and putting them under hg.debian.org. -- Jens Peter Secher. _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#504627: neko: Did not remove conffiles when purged
2008/11/9 Sam Morris [EMAIL PROTECTED]: On Sun, 2008-11-09 at 00:25 +0100, Jens Peter Secher wrote: [...] This makes sense, but I'm _sure_ that dpkg --search told me that the files were owned by neko, not libapache2-mod-neko. Is it possible that they used to be owned by neko, but transitioned to the other package at some point, and that didn't work properly? Of course, now the files are gone, I can't reproduce the bug. But if I look at my dpkg status file, there is no mention of libapache2-mod-neko; that is, dpkg has _never_ seen it in an installed state on this machine: OK, so when the apache module was separated out into its own package (around June 2007), I must have made a mistake in the upgrade process. But I am not sure what to do about it now... Cheers, -- Jens Peter Secher. _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#504627: neko: Did not remove conffiles when purged
Hi, thanks for your bug report. With respect to the two conffiles /etc/apache2/mods-available/neko.conf /etc/apache2/mods-available/neko.load they belong to the package libapache2-mod-neko, and if you simply purge neko with something like aptitude purge neko then libapache2-mod-neko will _not_ get purged automatically, that is, the above conffiles will stay on the machine. You should also have been instructed to run /etc/init.d/apache2 restart and after doing that, your apache2 will work fine and treat Neko files as binary blobs. However, if you instead run aptitude purge libapache2-mod-neko then you will indeed get the conffiles removed. All this is how it is expected to work on a Debian system. With respect to the file /etc/apache/conf.d/mod_neko it is a configuration file Apache 1.3, and not part of libapache2-mod-neko, so many it is a left-over from some manual install of neko? Can you confirm or unconfirm the above observations? Cheers, -- Jens Peter Secher. _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#475963: [pkg-mono-group] Bug#475963: file conflicts between packages
On 15/04/2008, Mirco Bauer [EMAIL PROTECTED] wrote: both mono-2.0-devel and siggen ship `/usr/bin/sgen' but do neither conflict, nor add a diversion, thus fail to be installed in the same environment: Jens, could you please rename /usr/bin/sgen to something else? Like siggen.sgen maybe? When I get back home next week, I will rename it signalgen. -- Jens Peter Secher. _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#441510: FTBFS: haxe
It seems that ocamlp4 (OCaml Preprocessor Pretty Printer) is not included in OCaml 3.10, which might have something to do with this (quote from wikipedia): OCaml version 3.10.0, released in May 2007, introduced a significantly modified and backwards-incompatible version of Camlp4. De Rauglaudre maintains a separate backwards-compatible version, which has been renamed Camlp5. I have not found a good way to deal with this yet. -- Jens Peter Secher. _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#412567: Verified: neko broken on HPPA
The problem is that apparently the neko compiler is broken on HPPA. I have verified the problem on paer.debian.org. Working on a solution. Cheers, -- Jens Peter Secher. _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#406033: neko_1.5.2-2(ia64/unstable): FTBFS: unaligned load/store in neko
On 1/8/07, Samuel Thibault [EMAIL PROTECTED] wrote: [EMAIL PROTECTED], le Sun 07 Jan 2007 21:41:46 -0700, a écrit : /bin/sh: line 1: 31492 Bus error LD_LIBRARY_PATH=../bin: NEKOPATH=../boot:../bin ../bin/neko nekoml -v neko/Main.nml nekoml/Main.nml The attached patch fixes the build both on sparc and ia64 architectures, i.e. works fine with align-requiriging, big-endian and 64bits architectures, so should be fine for others. Thanks, I just worked out an alternative patch which I have tested on HPPA, but yours looks more safe. Unfortunately I have _just_ uploaded it. If my patch do not work out on 64-bit, I will revert and use yours. And I will pass it upstream anyways. -- Jens Peter Secher _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_ A. Because it breaks the logical sequence of discussion Q. Why is top posting bad?
Bug#395411: debian-installer: [daily 20061026] fails to set up route + fails to see mirrors
Package: debian-installer Severity: critical Justification: prevents install Downloaded the daily etch netinst ISO image from http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso Booted fine on a ThinkPad T42, detected CD drive and built-in Intel PRO/1000 net card. Problem 1: DHCP gets the machine an IP address, but I get the message: The network autoconfiguration was successful. However, no default route was set ... Continue without a default route? This is strange, because if I continue installation selecting 'Yes', keeps hitting Enter (giving no name server, no domain name, etc.), no network mirror, install from CD only, install GRUB, and reboot the newly installed system, the route is set fine: debian:~# route ... 192.168.1.0 *255.255.255.0 ... default 192.168.1.1 0.0.0.0... by the default configuration: debian:~# cat /etc/network/interfaces ... allow-hotplug eth0 iface eth0 inet dhcp Problem 2: If I instead choose 'No', and configure the network manually, choose any network mirror, the installer tells me: The installer failed to access the mirror. ... But if I inspect VT4, I can see that what is tried is: wget -q http://mirrors.dotsrc.org/debian//dists/testing/main/binary-i386/Release -O - | grep Architecture If I do that from the VT3, it works fine. I guess is missing a | cut -d' ' -f 2 at the end? Cheers, /JP -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (700, 'testing'), (400, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=en_DK, LC_CTYPE=en_DK (charmap=ISO-8859-1) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#391736: lua-mode: fails to install
Hmm, yes, it seems that installing emacs and lua-mode together breaks, whereas first installing emacs, then intalling lua-mode works. Investigating... -- Jens Peter Secher _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_ A. Because it breaks the logical sequence of discussion Q. Why is top posting bad? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#389665: Debian and Software patents
Thank you for your bug report regarding patents on IDEA, RC2, RC5, and RC6, all present in libcrypto++. Debian's general stand on software patents is to ignore patents when such patents are not being actively enforced. So Debian, as an organisation, will not remove algorithms on the sole ground that they are patented. Personally, I will not remove any well-proven functionality just because it is patent-encumbered, unless someone sends me (or Debian) a cease-and-desist letter. This decision is not based on me being too lazy to do anything about such problems, quite the opposite: I feel that not giving in to the pressure of the lobby defending the so-called intellectual property is the right way to defend Debian's notion of freedom. However, the ftp-masters might have different opinions, therefore they are CC'ed. Regards, -- Jens Peter Secher _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_ A. Because it breaks the logical sequence of discussion Q. Why is top posting bad? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378373: haxe - FTBFS: ocamlopt: command not found
On 7/17/06, Samuel Mimram [EMAIL PROTECTED] wrote: ocamlopt, the native ocaml compiler is not available on every architecture. Where it is not available, the bytecode compiler (ocamlc) should be used instead. All this is explained in ocaml's policy[1]. Apparently, what you need to do is to change the lines 24 and 25 of install.ml to: let bytecode = true let native = false on architectures where /usr/bin/ocamlopt cannot be found. Thanks, I will try that out when I get access to one of those machines. -- Jens Peter Secher _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_ A. Because it breaks the logical sequence of discussion Q. Why is top posting bad? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#378373: haxe - FTBFS: ocamlopt: command not found
Hi, Maybe you can help me out with the build failure of haxe on s390. Automatic build of haxe_20060715-1 on lxdebian.bfinv.de by sbuild/s390 85 [...] ocamlc -c enum.mli bitSet.mli dynArray.mli extArray.mli extHashtbl.mli extList.mli extString.mli global.mli IO.mli option.mli pMap.mli std.mli uChar.mli uTF8.mli base64.mli unzip.mli refList.mli optParse.mli dllist.mli ocamlopt -c enum.ml sh: ocamlopt: command not found Exit Code 127 - Stopped Error while running ocaml install.ml -nodoc -d .. -n make: *** [build-stamp] Error 1 ** Build finished at 20060715-1322 FAILED [dpkg-buildpackage died] According to the build log, ocaml-nox version 3.09.2-5 is being installed and on my i386 system the ocamlopt binary is in that very package: [EMAIL PROTECTED]:~$ apt-file search ocamlopt ocaml-native-compilers: usr/bin/ocamlopt.opt ocaml-nox: usr/bin/ocamlopt ocaml-nox: usr/share/man/man1/ocamlopt.1.gz ocaml-nox: usr/share/man/man1/ocamlopt.opt.1.gz Same FTBFS problem happens on arm, hppa, and mips, but I am having trouble loging into such Debian machines after the breakin. When things settle down I will try to investigate myself. Cheers, -- Jens Peter Secher _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_ A. Because it breaks the logical sequence of discussion Q. Why is top posting bad? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#328975: (no subject)
I am trying to build a new version of libcrypto++ on paer right now, using GCC 3.4. -- Jens Peter Secher _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#328975: Please ignore libcrypto++5.2.1c2-6
Wouter Verhelst [EMAIL PROTECTED] writes: On Sat, Sep 24, 2005 at 09:55:43AM +0200, Jens Peter Secher wrote: libcrypto++5.2.1c2-6 is in needs-build state, but I am pretty sure it won't build cleanly, since it didn't on other architectures using GCC 3.4, so please remove it from the build queue. Sorry, I see that libcrypto++ previously failed to build with an internal compiler error. Did you try to build it with GCC 3.4 for that reason? If so, you can revert that change -- gcc 4.0 has seen a recent update which should fix those ICEs. Great thanks. -- Jens Peter Secher _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#328975: libcrypto++: FTBFS on arm, m68k, hppa
Dude, I have uploaded a version of libcrypto++ with the only modification being your patch to use GCC 3.4, but it fails to build on said architectures, and only those architectures. You wrote that you had successfully built the package with your patch, so what gives? It seems an awful waste to use 5.5 hours [1] on each of those hard-pressed architectures... -- Jens Peter Secher _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_ [1] Build needed 05:23:28, 155252k disk space -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#318518: libcrypto++: FTBFS: gcc 4 problem
Status report I am almost done with solving all the problems for libcrypto++ with respect to the GCC4 transition. My plan is as follows. I will upload to experimental and/or test the build on other architectures than i386. If everything works smoothly, I will upload to sid. -- Jens Peter Secher _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#318518: libcrypto++: FTBFS: gcc 4 problem
I am working on fixing the anonymous enum' is/uses anonymous type problems. Please do not upload without coordinating with me; I have a bunch of other pacthes that should go in. Cheers, -- Jens Peter Secher _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher get2net dk_ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
