Bug#397571: debian-reference: FTBFS: ERROR: reference.zh-tw.pdf could not be generated properly
From: Jens Seidel [EMAIL PROTECTED]
On Thu, Nov 09, 2006 at 03:34:15AM +0100, Danai SAE-HAN wrote:
Okay, I checked out the SGML-generated .tex file, and it seems very
much that Perl or something else misinterprets some of the CJK
characters.
The command I used to create the .tex file was:
debiandoc2latex -l zh_TW.Big5 reference.zh-tw.sgml
Examples of these misinterpreted characters:
in titledoc.sgml: 程 - 琵{
in preface.sgml: 開 - 跚}
閱 - 閱textbackslash{}
誤 - 蓋textasciitilde{}
Misinterprets? I remember that this was intentional! Extract from
fixlatex script which is applied after the SGML/Perl magic:
(zh_TW)
perl -p \
-e 's/([\x80-\xff])\\textbackslash\{\}/$1\\/g;' \
-e 's/([\x80-\xff])\\textasciitilde\{\}/$1\~/g;' \
-e 's/([\x80-\xff])\\textasciicircum\{\}/$1\^/g;' \
-e 's/([\x80-\xff])\\\}/$1\}/g;' \
-e 's/([\x80-\xff])\\\{/$1\{/g;' \
-e 's/([\x80-\xff])\\\_/$1_/g;' $1 |
bg5conv $2
That's the only code I'm aware of which substitutes characters. I have
to confess that the code is cryptic and I do not fully understand it.
But it was provided by a Chinese person and introduced to support zh_TW
documents and building did not worked without in the past.
The funny thing is that I also looked into the bg5conv code and noticed
that it does also very similar tasks (only a few substitutions). I once
tried to merge both so that the substitutions can be called together on
pieces of text inside the LaTeX processor (and not afterwards for speed
up and simplicity) but ...
The code works, and the output of bg5conv is then saved to
reference.zh-tw.tex-in. Run latex on this file (not bg5latex) and it
should work.
And perhaps a few other characters. I find it strange that not all
characters suffer from this problem, but only some. Perhaps Perl
doesn't have a complete map of the Big5 encoding?
A quick fix would perhaps be to put everything in a sed script.
I would prefer the opposite: deleting the above substitutions. Can you
please check these? Are they still necessary?
They're necessary. In the weekend I'll experiment with UTF-8.
BTW: Are you a Chinese? Or do you also have to guess whats right and
what not?
I'm Chinese, but I only recently learned Mandarin Chinese. I can read
and write some Chinese, but not proficiently enough to be able to
proofread the output.
What about the other languages? Japanese doesn't substitute strings but
failed with the same error that [EMAIL PROTECTED] was not defined ...
$ debiandoc2latex -l ja reference.ja.sgml
The result won't run with latex because it misses the HBF fonts.
For Japanese, there's a much better way now to get nice fonts: the use
of DNP Type1 fonts. You will need a slight change in though:
--- LaTeX~ 2005-02-13 17:04:27.0 +0100
+++ LaTeX 2006-11-10 02:03:16.130041713 +0100
@@ -11,7 +11,7 @@
'copyright notice' = '���ɽ��',
'pdfhyperref' = 'CJKbookmarks',
'before begin document' = '\\usepackage{CJK}',
- 'after begin document' = '\\begin{CJK}{JIS}{song}
+ 'after begin document' = '\\begin{CJK}[dnp]{JIS}{min}
\\renewcommand{\\vpageref}[1]{on page \\pageref{#1}}
\\def\\prefacename{�
\\def\\refname{ʸ ��}
Now latex will run fine (provided latex-cjk-japanese and
latex-cjk-japanese-wadalab are installed; if you depend on
latex-cjk-all, then it should be okay).
Because of the many \text* commands it's best to keep using bg5latex
instead of just latex, which apparently doesn't work. Fixing the
FTBS is much more important now ATM, so let's stick to bg5latex.
But it worked in the past. Do you still think it is necessary to use
bg5latex? This would make just more code language specific.
I'll try to make it run by latex. Another solution might be to make
a new zh_TW.UTF-8 version and use the CJKutf8 package. Then we don't
need to use converters and such.
Perhaps doing so with zh_TW, zh_CN and ja_JP will transform the HTML
into UTF-8 encoding as well, which would be a good thing IMHO.
Best regards
Danai SAE-HAN
韓達耐
--
題目:《王充道送水仙花五十支》
作者:黃庭堅（１０４５－１１０５）
凌波仙子生塵襪，水上輕盈步微月。
是誰招此斷腸魂，種作寒花寄愁絕。
含香體素欲傾城，山礬是弟梅是兄。
坐對真成被花惱，出門一笑大江橫。
Bug#395080: CVE-2006-5444/5:security issues in asterisk
hello, this has been fixed in the latest branch of asterisk (1.2.13)and in 1.4for a temporary fix, ( if its the bug im thinking your talking about )just edit /etc/asterisk/modules.conf and noload=chan_skinny.so On 11/9/06, Frédéric Brière [EMAIL PROTECTED] wrote: On Tue, Oct 24, 2006 at 10:14:45PM +0200, Stefan Fritsch wrote: The skinny issue is CVE-2006-5444.Is there a reason why this issue has not yet been fixed in sarge?-- Frédéric Brière* [EMAIL PROTECTED] =[EMAIL PROTECTED] IS NO MORE:http://www.abacomsucks.com =___Pkg-voip-maintainers mailing list[EMAIL PROTECTED] http://lists.alioth.debian.org/mailman/listinfo/pkg-voip-maintainers-- --- Brandon Kruse
Bug#397835: Perhaps a doubt
Although I have no difficulty to believe that the bug report is valid, AFAIK Alvaro (who committed these files) himself doesn't remember where/who these icons are from. I would be interested to know what evidence you have that the icons are based on Microsoft's. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#395080: CVE-2006-5444/5:security issues in asterisk
On Fri, Nov 10, 2006 at 04:07:14AM +, Brandon Kruse wrote: hello, this has been fixed in the latest branch of asterisk (1.2.13) and in 1.4 Yes, I know this is fixed in sid. What I want to know is why this buffer overflow is still present in sarge. The fix seems rather straightforward, and patches have been proposed in #394025. for a temporary fix, ( if its the bug im thinking your talking about ) just edit /etc/asterisk/modules.conf and noload=chan_skinny.so I'm not using chan_skinny, so I'm not actually worried about being bitten by this particular bug. However, from what I understand, this is a theoretically exploitable security bug which has been allowed to sit for three weeks, without any update nor announcement for sarge users. *That* is why I'm worried. -- Frédéric Brière*[EMAIL PROTECTED] = [EMAIL PROTECTED] IS NO MORE: http://www.abacomsucks.com =
Bug#397828: efp.nes is a game..
The recommends should be a depends (and fceu-sdl is renamed to fceu). -- see shy jo signature.asc Description: Digital signature
Bug#366172: libnss-ldap: abort during useradd (ber_free_buf error)
tags 366172 moreinfo unreproducible thanks Scott, On Tue, Aug 22, 2006 at 09:21:13AM -0700, Scott Anderson wrote: Are you still seeing this error with useradd? Does it happen with libnss-ldap 251-5, which is now the current version in testing/unstable? Yes. I just ran the following: % sudo /usr/sbin/useradd -d /var/lib/nfs -g nogroup -s /bin/false -u 115 testuseradd useradd: /build/buildd/openldap2-2.1.30/libraries/liblber/io.c:161: ber_free_buf: Assertion `((ber)-ber_opts.lbo_valid==0x2)' failed. Sorry it's taken so long to resolve this bug, but it remains unreproducible in the general case. Two things that would probably help me pin this bug: - output of strace -ff run on your useradd command - a gdb backtrace from the same at the point of the assertion. Your continued help and patience is very much appreciated. Since no one else is reporting this problem, I will most likely downgrade this bug within the next week (thus leaving it possibly unfixed for etch) if you aren't able to send me a backtrace, due to the difficulty in debugging this blind. I'm having problems with libnss-ldap in other ways too. 1. It crashes dbus when booting. 2. It checks for system users on my ldap server even though I only have local system users 3. It times out twice using 'getent passwd' and 'id user' (I've shortened the timeout to only 2 seconds each to work around it...) AIUI, these problems should at least be addressed now in unstable, so fortunately it might now be a bit less painful to debug the remaining assertion bug. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#366172: libnss-ldap: abort during useradd (ber_free_buf error)
Processing commands for [EMAIL PROTECTED]: tags 366172 moreinfo unreproducible Bug#366172: libnss-ldap: abort during useradd (ber_free_buf error) There were no tags set. Tags added: moreinfo, unreproducible thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397874: Uninstallable because of conflicting binary svn-clean which is also in kdesdk-scipts
Package: subversion-tools Version: 1.4.0-5 Severity: serious subversion-tools tries to install /usr/bin/svn-clean which is also in package kdesdk-scripts. As the installation fails because of this, I set the priority to serious. Cheers, Michael -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (300, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.19-rc5 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages subversion-tools depends on: ii libconfig-inifiles-perl 2.39-2 Read .ini-style configuration file ii liburi-perl 1.35-2 Manipulates and accesses URI strin ii perl5.8.8-6.1Larry Wall's Practical Extraction ii python 2.4.4-1 An interactive high-level object-o ii python-subversion 1.4.2dfsg1-1 Python bindings for Subversion ii subversion 1.4.2dfsg1-1 Advanced version control system Versions of packages subversion-tools recommends: ii exim4 4.63-10metapackage to ease exim MTA (v4) ii exim4-daemon-heavy [mail-tran 4.63-10exim MTA (v4) daemon with extended ii rcs 5.7-18 The GNU Revision Control System -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397048: gtk-gnutella: FTBFS on ARM
This is supposed to be fixed in a portable manner in 0.96.3 now. -- Christian -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#395857: libextutils-autoinstall-perl: FTBFS: test fails
On Fri, Nov 10, 2006 at 03:35:37AM +0100, Mohammed Adnene Trojette wrote: Automatic build of libextutils-autoinstall-perl_0.61-1 on avidan by sbuild/i386 98 Build started at 20061028-0010 It builds fine here. (don't take other mails sent here into account by my new nmudiff). Please Julien, could you try building the package again? Yes, but I don't think it'll help. I mean, it seems that it only fails if HOME is nonexistent, and it tries to create it. # Expected: mkdir /nonexistent: Permission denied at /usr/share/perl/5.8/CPAN.pm line 1257\nBEGIN failed--compilation aborted at (eval 9) line 22.\n But this behaviour is bad. It should not get out of its build tree. If you want to quickly fix that, just disable the test during the build step. Cheers, -- Julien Danjou .''`. Debian Developer : :' : http://julien.danjou.info `. `' http://people.debian.org/~acid `- 9A0D 5FD9 EB42 22F6 8974 C95C A462 B51E C2FE E5CD signature.asc Description: Digital signature
Bug#396670: jailer: FTBFS: error: can not find install-sh
On Fri, Nov 10, 2006 at 03:22:33AM +0100, Ana Guerrero wrote: Hola Javier, It seems after some time stuck at the UploadQueue, it was removed. Could you try to upload it again? Done. Javier signature.asc Description: Digital signature
Bug#397874: Uninstallable because of conflicting binary svn-clean which is also in kdesdk-scipts
[Michael Biebl] subversion-tools tries to install /usr/bin/svn-clean which is also in package kdesdk-scripts. Thanks for noticing. I'll add a 'Conflicts: kdesdk-scripts' - this requires subversion-tools to be priority 'extra', but fortunately it already is. I think svn-clean is generally useful to have and it's exactly the sort of thing that belongs in a package like subversion-tools, so I don't want to just drop it. I do note that the 'svn-clean' in kdesdk-scripts is pretty much functionally identical, but messing with alternatives is way overkill. Thanks, Peter signature.asc Description: Digital signature
Bug#397831: ivtv: keep 0.8.x release out of testing until matching 2.6.18 kernel enters.
On Thu, 2006-11-09 at 16:54 -0800, Steve Langasek wrote: On Thu, Nov 09, 2006 at 09:01:11PM +, Ian Campbell wrote: Package: ivtv Version: 0.8.0-1 Severity: serious The ivtv module source has a very tight dependency on the kernel version. Therefore the 0.8.x releases must be used with a 2.6.18 kernel. This bug has been filed to keep ivtv 0.8.x out of testing until the correct kernel has propagated. Well, 2.6.18 is the target kernel for etch, and it should reach testing immediately after d-i RC1 is released at the end of the week. So maybe this bug isn't really worth the trouble? I scanned the debian-kernel and debian-release archives and didn't see any special planning going on so I assumed it would follow some approximation of the normal testing propagation rules. So when I saw 2.6.18-5 uploaded yesterday I thought that would mean at least another 10 days (and it's still buggy 43) before it reached testing while ivtv is currently 4/10. Even if things are going to be manually pushed through the bug provides me with peace of mind that things will happen at the right time. Anyhow, I'm actively following what's going on with the kernel and I'll take care of ivtv once I see the kernel move so if you want to ignore the issue you can. It's a pain that these keep out of testing bugs have to be RC and therefore end up on your radar and taking up your time. Would it have helped if I'd added the etch-ignore tag when I filed it? Not that I expect to have to do it again, since the driver ought to be merged with the upstream kernel by etch+1. Ian. -- Ian Campbell The more complex the mind, the greater the need for the simplicity of play. -- Kirk, Shore Leave, stardate 3025.8 signature.asc Description: This is a digitally signed message part
Bug#396922: marked as done (FTBFS: Missing Build Dependency on libgmp3-dev)
Your message dated Wed, 08 Nov 2006 23:47:17 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#396922: fixed in guile-1.8 1.8.1+1-1.1 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: guile-1.8 Version: 1.8.1+1-1 Severity: serious Hi, guile-1.8 is failing to build during configure stage with this error: checking for __gmpz_init in -lgmp... no configure: error: GNU MP not found, see README make: *** [debian/stamp/config] Error 1 debuild: fatal error at line 1224: debian/rules build failed In README file, upstream author has indicated that the following dependencies are necessary to build guile-1.8: - libltdl from libtool. (like it is indicated in #395235). - GNU MP, at least version 4.1. To solve this bug, you must add a Build Dependency on libgmp3-dev (= 4.1) in debian/control. Add this dependency may be the solution to solve #395290 too. Thanks. Regards, -- .---. Ludovic RESLINGER / \ [EMAIL PROTECTED]@./ Trumpet Student in CNR /`\_/`\ Free Software Developer // )X( \\ | \ : )|_ _,'| .''`. /`\_` _/ \ @==TTT=::_ | : :' : \__/'---'\__/ ((_=HHH___)) `.| `. `'` `---UUU---'= `- signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: guile-1.8 Source-Version: 1.8.1+1-1.1 We believe that the bug you reported is fixed in the latest version of guile-1.8, which is due to be installed in the Debian FTP archive: guile-1.8-dev_1.8.1+1-1.1_i386.deb to pool/main/g/guile-1.8/guile-1.8-dev_1.8.1+1-1.1_i386.deb guile-1.8-doc_1.8.1+1-1.1_all.deb to pool/main/g/guile-1.8/guile-1.8-doc_1.8.1+1-1.1_all.deb guile-1.8-libs_1.8.1+1-1.1_i386.deb to pool/main/g/guile-1.8/guile-1.8-libs_1.8.1+1-1.1_i386.deb guile-1.8_1.8.1+1-1.1.diff.gz to pool/main/g/guile-1.8/guile-1.8_1.8.1+1-1.1.diff.gz guile-1.8_1.8.1+1-1.1.dsc to pool/main/g/guile-1.8/guile-1.8_1.8.1+1-1.1.dsc guile-1.8_1.8.1+1-1.1_i386.deb to pool/main/g/guile-1.8/guile-1.8_1.8.1+1-1.1_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Schepler [EMAIL PROTECTED] (supplier of updated guile-1.8 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 9 Nov 2006 03:11:16 +0100 Source: guile-1.8 Binary: guile-1.8-doc guile-1.8 guile-1.8-libs guile-1.8-dev Architecture: source i386 all Version: 1.8.1+1-1.1 Distribution: unstable Urgency: low Maintainer: Rob Browning [EMAIL PROTECTED] Changed-By: Daniel Schepler [EMAIL PROTECTED] Description: guile-1.8 - The GNU extension language and Scheme interpreter guile-1.8-dev - Development files for Guile 1.8 guile-1.8-doc - Documentation for Guile 1.8 guile-1.8-libs - Main Guile libraries Closes: 395235 395290 396922 Changes: guile-1.8 (1.8.1+1-1.1) unstable; urgency=low . * NMU to fix RC bugs. * Build-Depend on libltdl3-dev (closes: #395235), libgmp3-dev (closes: #396922), and texinfo. * Build-Depend on locales and generate de_DE.ISO-8859-1 for use by the testsuite. * Add the above *-dev dependencies also to guile-1.8-dev (closes: #395290). Files: 834e819184b53ebc17b6075e3376e344 758 interpreters optional guile-1.8_1.8.1+1-1.1.dsc dade667d8732e9d2c77c4fa4082d1202 10872 interpreters optional guile-1.8_1.8.1+1-1.1.diff.gz f55a09b9347bd26b696c7c49fe836e02 20642 doc optional guile-1.8-doc_1.8.1+1-1.1_all.deb cf494c7521dc707785ddc44fe236e02e 7270 interpreters optional guile-1.8_1.8.1+1-1.1_i386.deb 06d59bfea13ba91cbba516783da86917 556652 devel optional guile-1.8-dev_1.8.1+1-1.1_i386.deb 13361d30384ac1894a282e0558c4a389 668038 libs optional guile-1.8-libs_1.8.1+1-1.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFUrqrNC3LAyACFJARArmlAJ40WBkW+ck1lKjo5tf4lX/dKnqqDwCeOSK8 bEaCvKfszTVwd23YXxb/IVQ= =zXAP -END PGP SIGNATURE- ---End Message---
Bug#395290: marked as done (guile-1.8-dev: fails lilypond configure checks)
Your message dated Wed, 08 Nov 2006 23:47:17 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#395290: fixed in guile-1.8 1.8.1+1-1.1 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: guile-1.8-dev Severity: grave Version: 1.8.1+1-1 Hi Rob...wonderful that guile 1.8 is now in Debian! Thanks for all the hard work. Unfortunately, some lilypond checks related to guile fail. checking libguile.h usability... no checking libguile.h presence... no checking for libguile.h... no These checks seem to be because libguile.h includes gmp.h, which guile-1.8-dev does not depend on. It seems that guile-1.8-dev should depend on libgmp3-dev. Installing the package myself causes the libguile.h configure checks to work. checking for scm_boot_guile in -lguile... no checking for scm_boot_guile... no These checks fail because guile-config reports that -lltdl is needed, but since there is no dependency on it, the link check looking for scm_boot_guile fails. Installing libltdl3-dev causes the configure checks to work. (Note that this part is *not* a duplicate of #395235; that bug asks for libltdl3-dev to be added as a Build-Depends, and this one asks for it to be added as a regular dependency for guile-1.8-dev.) Thomas ---End Message--- ---BeginMessage--- Source: guile-1.8 Source-Version: 1.8.1+1-1.1 We believe that the bug you reported is fixed in the latest version of guile-1.8, which is due to be installed in the Debian FTP archive: guile-1.8-dev_1.8.1+1-1.1_i386.deb to pool/main/g/guile-1.8/guile-1.8-dev_1.8.1+1-1.1_i386.deb guile-1.8-doc_1.8.1+1-1.1_all.deb to pool/main/g/guile-1.8/guile-1.8-doc_1.8.1+1-1.1_all.deb guile-1.8-libs_1.8.1+1-1.1_i386.deb to pool/main/g/guile-1.8/guile-1.8-libs_1.8.1+1-1.1_i386.deb guile-1.8_1.8.1+1-1.1.diff.gz to pool/main/g/guile-1.8/guile-1.8_1.8.1+1-1.1.diff.gz guile-1.8_1.8.1+1-1.1.dsc to pool/main/g/guile-1.8/guile-1.8_1.8.1+1-1.1.dsc guile-1.8_1.8.1+1-1.1_i386.deb to pool/main/g/guile-1.8/guile-1.8_1.8.1+1-1.1_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Schepler [EMAIL PROTECTED] (supplier of updated guile-1.8 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 9 Nov 2006 03:11:16 +0100 Source: guile-1.8 Binary: guile-1.8-doc guile-1.8 guile-1.8-libs guile-1.8-dev Architecture: source i386 all Version: 1.8.1+1-1.1 Distribution: unstable Urgency: low Maintainer: Rob Browning [EMAIL PROTECTED] Changed-By: Daniel Schepler [EMAIL PROTECTED] Description: guile-1.8 - The GNU extension language and Scheme interpreter guile-1.8-dev - Development files for Guile 1.8 guile-1.8-doc - Documentation for Guile 1.8 guile-1.8-libs - Main Guile libraries Closes: 395235 395290 396922 Changes: guile-1.8 (1.8.1+1-1.1) unstable; urgency=low . * NMU to fix RC bugs. * Build-Depend on libltdl3-dev (closes: #395235), libgmp3-dev (closes: #396922), and texinfo. * Build-Depend on locales and generate de_DE.ISO-8859-1 for use by the testsuite. * Add the above *-dev dependencies also to guile-1.8-dev (closes: #395290). Files: 834e819184b53ebc17b6075e3376e344 758 interpreters optional guile-1.8_1.8.1+1-1.1.dsc dade667d8732e9d2c77c4fa4082d1202 10872 interpreters optional guile-1.8_1.8.1+1-1.1.diff.gz f55a09b9347bd26b696c7c49fe836e02 20642 doc optional guile-1.8-doc_1.8.1+1-1.1_all.deb cf494c7521dc707785ddc44fe236e02e 7270 interpreters optional guile-1.8_1.8.1+1-1.1_i386.deb 06d59bfea13ba91cbba516783da86917 556652 devel optional guile-1.8-dev_1.8.1+1-1.1_i386.deb 13361d30384ac1894a282e0558c4a389 668038 libs optional guile-1.8-libs_1.8.1+1-1.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFUrqrNC3LAyACFJARArmlAJ40WBkW+ck1lKjo5tf4lX/dKnqqDwCeOSK8 bEaCvKfszTVwd23YXxb/IVQ= =zXAP -END PGP SIGNATURE- ---End Message---
Bug#395235: marked as done (guile-1.8: FTBFS: configure: error: libltdl not found.)
Your message dated Wed, 08 Nov 2006 23:47:17 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#395235: fixed in guile-1.8 1.8.1+1-1.1 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: guile-1.8 Version: 1.8.1+1-1 Severity: serious Hi, Your package is failing to build with the following error: checking for lt_dlinit in -lltdl... no configure: error: libltdl not found. See README. make: *** [debian/stamp/config] Error 1 Please add a build dependency on libltdl3-dev Kurt ---End Message--- ---BeginMessage--- Source: guile-1.8 Source-Version: 1.8.1+1-1.1 We believe that the bug you reported is fixed in the latest version of guile-1.8, which is due to be installed in the Debian FTP archive: guile-1.8-dev_1.8.1+1-1.1_i386.deb to pool/main/g/guile-1.8/guile-1.8-dev_1.8.1+1-1.1_i386.deb guile-1.8-doc_1.8.1+1-1.1_all.deb to pool/main/g/guile-1.8/guile-1.8-doc_1.8.1+1-1.1_all.deb guile-1.8-libs_1.8.1+1-1.1_i386.deb to pool/main/g/guile-1.8/guile-1.8-libs_1.8.1+1-1.1_i386.deb guile-1.8_1.8.1+1-1.1.diff.gz to pool/main/g/guile-1.8/guile-1.8_1.8.1+1-1.1.diff.gz guile-1.8_1.8.1+1-1.1.dsc to pool/main/g/guile-1.8/guile-1.8_1.8.1+1-1.1.dsc guile-1.8_1.8.1+1-1.1_i386.deb to pool/main/g/guile-1.8/guile-1.8_1.8.1+1-1.1_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Schepler [EMAIL PROTECTED] (supplier of updated guile-1.8 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 9 Nov 2006 03:11:16 +0100 Source: guile-1.8 Binary: guile-1.8-doc guile-1.8 guile-1.8-libs guile-1.8-dev Architecture: source i386 all Version: 1.8.1+1-1.1 Distribution: unstable Urgency: low Maintainer: Rob Browning [EMAIL PROTECTED] Changed-By: Daniel Schepler [EMAIL PROTECTED] Description: guile-1.8 - The GNU extension language and Scheme interpreter guile-1.8-dev - Development files for Guile 1.8 guile-1.8-doc - Documentation for Guile 1.8 guile-1.8-libs - Main Guile libraries Closes: 395235 395290 396922 Changes: guile-1.8 (1.8.1+1-1.1) unstable; urgency=low . * NMU to fix RC bugs. * Build-Depend on libltdl3-dev (closes: #395235), libgmp3-dev (closes: #396922), and texinfo. * Build-Depend on locales and generate de_DE.ISO-8859-1 for use by the testsuite. * Add the above *-dev dependencies also to guile-1.8-dev (closes: #395290). Files: 834e819184b53ebc17b6075e3376e344 758 interpreters optional guile-1.8_1.8.1+1-1.1.dsc dade667d8732e9d2c77c4fa4082d1202 10872 interpreters optional guile-1.8_1.8.1+1-1.1.diff.gz f55a09b9347bd26b696c7c49fe836e02 20642 doc optional guile-1.8-doc_1.8.1+1-1.1_all.deb cf494c7521dc707785ddc44fe236e02e 7270 interpreters optional guile-1.8_1.8.1+1-1.1_i386.deb 06d59bfea13ba91cbba516783da86917 556652 devel optional guile-1.8-dev_1.8.1+1-1.1_i386.deb 13361d30384ac1894a282e0558c4a389 668038 libs optional guile-1.8-libs_1.8.1+1-1.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFUrqrNC3LAyACFJARArmlAJ40WBkW+ck1lKjo5tf4lX/dKnqqDwCeOSK8 bEaCvKfszTVwd23YXxb/IVQ= =zXAP -END PGP SIGNATURE- ---End Message---
Bug#379628: [Linux-NTFS-Dev] CALL FOR HELP: Vista beta compatibility testing (was: ntfsresize: resizing a Vista NTFS partition ...)
Hi, Vista went gold. Unfortunately nobody could test the problem with the latest Vista BETA, hence we don't know if the problem still exists or Microsoft fixed it. Thanks to all who did everything he could. On Thu, 9 Nov 2006, Frans Pop wrote: No, but I'm surprised that data partitions should be affected too. Of course they will also suffer from the starting sector problem we have in partman/parted (which we should be able to fix), but I would not have expected them to be corrupted by ntfsresize. It doesn't look to be a filesystem corruption issue at all. The problem is exactly that. Seemingly the Microsoft boot process completely ignores the consistent NTFS and tries to boot via some other way but hangs. Of course I don't expect Microsoft to fix ntfsresize, the problem is not there. The problem is how they boot or shutdown. They must be able to detect that the underlaying file system was consistently changed and they should adjust their boot process accordingly. Or they should tell the world what state their OS is and developers can detect, deny and let users know what they should exactly do to be able to make modifications safely from non-Windows OSes. I think Microsoft doesn't know they have a problem because nobody told them yet. Bug reporting needs beta access but none of us is Vista beta tester. Are you really sure of this? Andree confirmed that it's true for data partitions as well. You should have got a copy too. Szaka -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397676: Bug#397571: debian-reference: FTBFS: ERROR: reference.zh-tw.pdf could not be generated properly
Danai SAE-HAN (韓達耐) [EMAIL PROTECTED] wrote: Package: debiandoc-sgml Problem: update to latex-cjk and better CJK support Appointed to Danai. File to check: release-notes.ja.sgml Package: apt-howto No problems. Reported by Frank. Package: debian-reference Problems. Reported by Frank, Jens. Appointed to Danai. Files to check: reference.zh-tw.sgml reference-zh-cn.sgml reference-ja.sgml Package: harden-doc Builds without problems. Package: maint-guide Same problem as debian-reference and debian-zh-faq, this time in the japanese version (I already mentioned this in the bug report to #397676) Package: mediawiki1.5-math Package: mediawiki1.7-math Why do you think these are a problem? How do they Build-depend on latex-cjk? Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
Bug#397705: stellarium: FTBFS: configure: error: freetype library not foun
Obviously there is a dependency problem with freetype.. Fabien Lucas Nussbaum wrote: Package: stellarium Version: 0.8.1-1 Severity: serious Justification: FTBFS on i386, very likely to fail everywhere else Usertags: grid5000 Hi, During a rebuild of all packages in etch, I discovered that your package failed to build on i386. Relevant parts: checking for i486-linux-gnu-g++... (cached) i486-linux-gnu-g++ checking whether we are using the GNU C++ compiler... (cached) yes checking whether i486-linux-gnu-g++ accepts -g... (cached) yes checking dependency style of i486-linux-gnu-g++... (cached) gcc3 checking for i486-linux-gnu-ranlib... ranlib checking for FT_Init_FreeType in -lfreetype... no configure: error: freetype library not found ./configure: line 12356: exit: please: numeric argument required ./configure: line 12356: exit: please: numeric argument required make: *** [configure-stamp] Error 255 The full build log is available from http://ox.blop.info/bazaar/buildlogs/20061107/ About the archive rebuilt: The rebuilt was done on about 30 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing an etch i386 environment (not unstable). Internet was not accessible from the build systems. The builds were processed as root. About Grid'5000: Grid'5000 is an highly reconfigurable experimental Grid platform gathering 9 sites and featuring a total of 5000 CPUs. It serves as a testbed for research in Grid Computing. See https://www.grid5000.fr/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397717: lmodern: install failed with error message warning: directory /usr/lib/X11/fonts/Type1 does not exist
follows is the result of dpkg-reconfigure -plow (with lmodern.postinst including set -ex). adding a fresh lm.map to '/usr/share/texmf/fonts/map/dvips/lm/' seems to have fixed the _configuration_ problem, but a clean installation still fails. attached is the original output from updmap.. ~ % sudo dpkg-reconfigure -plow lmodern (0) [EMAIL PROTECTED]:22:07 2715 + which update-fonts-dir + update-fonts-scale Type1 warning: /usr/lib/X11/fonts/Type1 does not exist or is not a directory + update-fonts-dir --x11r7-layout Type1 warning: /usr/lib/X11/fonts/Type1 does not exist or is not a directory + case $1 in + update-updmap --quiet + update-language + update-fmtutil + dhit_libkpathsea_configured + kpsewhich --version + which mktexlsr + dhit_update_lsr_files ++ mktemp -p /tmp mktexlsr. + tempfile=/tmp/mktexlsr.hWl10322 + printf 'Running mktexlsr. This may take some time... ' Running mktexlsr. This may take some time... + mktexlsr + rm -f /tmp/mktexlsr.hWl10322 + echo done. done. + for i in map + '[' map = map ']' + which updmap-sys + dhit_create_fontmaps ++ mktemp -p /tmp updmap. + tempfile=/tmp/updmap.aVE10415 + printf 'Running updmap-sys. This may take some time... ' Running updmap-sys. This may take some time... + updmap-sys + rm -f /tmp/updmap.aVE10415 + echo done. done. + '[' map = format ']' + '[' map = language ']' + FILE=/etc/defoma/hints/lmodern.hints + '[' configure = configure ']' + test -x /usr/bin/defoma-font + /usr/bin/defoma-font reregister-all /etc/defoma/hints/lmodern.hints ~ % -- == $mysig = EOS; the old lighter in the gun in the rabbit trick. (kfg) daniël bosold [EMAIL PROTECTED] [EMAIL PROTECTED] http://www.bosold.net aim: cyclist38 icq: cyfacKid EOS updmap.tdCx7665 Description: Binary data
Bug#397655: debian-zh-faq: FTBFS in etch: Problem with latex-cjk
Guanghui Yu [EMAIL PROTECTED] wrote: Hi It's caused by latex-cjk fonts name changes. I will update debian-zh-faq as soon as possible. No, sorry, that is not the problem. The new font packages do provide the old names, so this should work (and if it doesn't, it will fail when parsing the build-deps, not during compilation). Updating the Build-Deps is a good thing, but it won't solve this bug: This needs changes in debiandoc-sgml. Therefore it's right that this is now a bug of the latter package. Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
Processed: third try...
Processing commands for [EMAIL PROTECTED]: merge 397676 397655 Bug#397655: debian-zh-faq: FTBFS in etch: Problem with latex-cjk Bug#397676: debiandoc-sgml: Creates unprocessable LaTeX code for CJK languages Merged 397655 397676. stop Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397750: Wrong currency
package: interchange
severity: grave
Mixing language and currency locales can cause the wrong currency to
display in the shop.
[setlocale currency=en_US]
while the current locale is de_DE, Interchange overwrites the currency
keys in the de_DE repository:
if ($currency) {
my $curr = $Vend::Cfg-{Locale_repository}{$currency};
for(@Vend::Config::Locale_directives_currency) {
$Vend::Cfg-{$_} = $curr-{$_}
if defined $curr-{$_};
}
for(@Vend::Config::Locale_keys_currency) {
$Vend::Cfg-{Locale}{$_} = $curr-{$_}
if defined $curr-{$_};
}
}
}
So it isn't possible to switch back to de_DE currency and get the
correct currency symbol:
[setlocale currency=de_DE]
Bye
Racke
--
LinuXia Systems = http://www.linuxia.de/
Expert Interchange Consulting and System Administration
ICDEVGROUP = http://www.icdevgroup.org/
Interchange Development Team
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#397659: jspwiki: FTBFS: source code not available
Processing commands for [EMAIL PROTECTED]: reassign 397659 ftp.debian.org Bug#397659: jspwiki: FTBFS: source code not available Bug reassigned from package `jspwiki' to `ftp.debian.org'. merge 397659 391193 Bug#391193: orig.tar.gz not in pool/main for jspwiki 2.2.33 Bug#397659: jspwiki: FTBFS: source code not available Merged 391193 397659. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397753: adept continues installation even if you say no
Package: adept Version: 2.1.2 Severity: grave Justification: causes non-serious data loss Tags: security X-Debbugs-Cc: [EMAIL PROTECTED] Here's the scenario. apt-get upgrade shows you a bunch of packages which aren't upgradable because its newer version got some more dependencies. Example: You had package a.1 installed on your system. The testing repository now has a.2 which has an additional dependency b.1 Now when you manually say apt to install package a.2, it also downloads the new dependency packages b.1. If you have apt-listbugs installed, and you find that there's a bug filed against b.1 which is fixed in b.2 which currently is in testing, a user normally says 'N' and aborts the installation to wait till b.2 propagates to testing. All fine till here. Doing the same thing in adept doesn't work. Adept informs you that package a.1 has an upgrade available. It also shows that b.1 needs be installed. The user hits, Fetch button. Adept downloads the package, runs apt-listbugs, then waits for the user intervention for the bugs listed. Again as a user you say 'N', but adept *ignores* the 'N' you passed and proceeds ahead with installation of the vulnerable b.1 package I hope I've made the bug report clear. Thanks, Ritesh -- System Information: Debian Release: 4.0 APT prefers testing APT policy: (990, 'testing'), (550, 'unstable'), (500, 'stable'), (350, 'experimental'), (150, 'edgy'), (150, 'dapper') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-xps Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages adept depends on: ii adept-installer 2.1.2 simple user interface for applicat ii adept-manager 2.1.2 package manager for KDE ii adept-notifier2.1.2 system tray notifier of available ii adept-updater 2.1.2 system update tool for KDE adept recommends no packages. -- no debconf information -- Ritesh Raj Sarraf RESEARCHUT - http://www.researchut.com Necessity is the mother of invention. Stealing logic from one person is plagiarism, stealing from many is research. The great are those who achieve the impossible, the petty are those who cannot - rrs -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#379628: [Linux-NTFS-Dev] CALL FOR HELP: Vista beta compatibility testing (was: ntfsresize: resizing a Vista NTFS partition ...)
On Thursday 09 November 2006 09:03, Szakacsits Szabolcs wrote: Are you really sure of this? Andree confirmed that it's true for data partitions as well. You should have got a copy too. But that seems completely inconsistent with what you wrote in the rest of the mail: that it is a problem with 'how they boot or shutdown'. pgpvsaqQ0dJ36.pgp Description: PGP signature
Bug#397243: xoscope: oscope gone missing when rebult
Hi Nicolas Thanks for your bugreport. I am sorry, but I did not have enough time to track down the issue and provide a fix, as I am relocating from australia to germany over the holidays. The journey takes some time, so if somebody comes up with a fix, please feel free to NMU, otherwise I will look into that issue as soon as possible. I sadly did not have access to a non-i386 arch/non-64bit here, but I know that upstream had some problems with porting, so I do not know how useful xoscope on other archs than i386 is. Sorry for the inconvience, get hopefully back to you in a couple of days. Cheers Steffen pgp1eAajdFdv0.pgp Description: PGP signature
Bug#396055: unionfs-source: sioq missing upstream too ...
Package: unionfs-source Version: 1.3.20061029.0124+debian-1 Followup-For: Bug #396055 Hi, ... Almost two weeks since this RC bug is open, without any activity. Also, it seems to me this module was never built, or the failure would have been noticed. A quick google shows : http://www.mail-archive.com/unionfs-cvs@mail.fsl.cs.sunysb.edu/msg00585.html Which is a CVS commit message with the log : Forgot to add the sioq.h file and dated : Wed, 23 Aug 2006 15:52:11 -0700 So, i wonder why this was not fixed in the : * New upstream snapshot: (Dated 20061029) The plan is to disable unionfs module builds until these issues are fixed. Friendly, Sven Luther -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-powerpc Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397560: blender: FTBFS: /usr/bin/ld: cannot find -lsh
On Wed, Nov 08, 2006 at 09:57:35AM +0100, Lucas Nussbaum wrote: During a rebuild of all packages in etch, I discovered that your package failed to build on i386. Relevant parts: Compiling == 'buildinfo.c' Linking program == 'blender' /usr/bin/ld: cannot find -lsh: collect2: ld returned 1 exit status Incidentally, the unstable m68k build which occurred three weeks after uploading the latest version of blender failed the same way. I'd guess changes in the build environment in the meantime might have caused this, but this demands further investigations. I'll get to this as soon as I can. Cheers, Flo signature.asc Description: Digital signature
Bug#397310: our workaround
Thank you Joseph - that fixed mine, too :-) Eddy. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#379628: [Linux-NTFS-Dev] CALL FOR HELP: Vista beta compatibility testing (was: ntfsresize: resizing a Vista NTFS partition ...)
[Frans: Could you please keep all interested parties CC'd? They don't get your emails and I must add Andree and linux-ntfs-dev manually every time. Thanks.] On Thu, 9 Nov 2006, Frans Pop wrote: On Thursday 09 November 2006 09:03, Szakacsits Szabolcs wrote: Andree confirmed that it's true for data partitions as well. You should have got a copy too. But that seems completely inconsistent with what you wrote in the rest of the mail: that it is a problem with 'how they boot or shutdown'. Nobody seems to know what a data partition has to do with booting. Also nobody confirmed yet that there is indeed a problem with Vista Gold. Btw, what partition scheme does Vista use? Isn't it GPT? Couldn't the problem be somehow related to that? Ntfsresize completely ignores the storage type by design. It can be file, MBR, GPT, LDM, whatever. It works 100% independently of them, so the storage type related work can be and often __must__ be done independently. There is this MS document (Vista is based on W2K3): http://technet2.microsoft.com/WindowsServer/en/library/bdeda920-1f08-4683-9ffb-7b4b50df0b5a1033.mspx?mfr=true If somebody has the time (sorry, I don't) then perhaps he could take a look. Maybe there is something useful info related to this problem. Szaka -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397759: fails to configure: mv: cannot stat `/etc/chrony/chrony.keys.1.21-2': No such file or directory
Package: chrony Version: 1.21z-4 Severity: serious Justification: 6.2 Tags: patch This code: if dpkg --compare-versions $2 lt-nl 1.21-3 ; then mv /etc/chrony/chrony.keys.$2 /etc/chrony/chrony.keys mv /etc/chrony/chrony.conf.$2 /etc/chrony/chrony.conf fi in the postinst makes the postinst not idempotent, and makes my chrony fail to configure: [EMAIL PROTECTED]:~$ sudo dpkg --configure --pending Setting up chrony (1.21z-4) ... mv: cannot stat `/etc/chrony/chrony.keys.1.21-2': No such file or directory dpkg: error processing chrony (--configure): subprocess post-installation script returned error exit status 1 Errors were encountered while processing: chrony I suggest something like: if dpkg --compare-versions $2 lt-nl 1.21-3 ; then if [ -f /etc/chrony/chrony.keys.$2 ]; then mv /etc/chrony/chrony.keys.$2 /etc/chrony/chrony.keys fi if [ -f /etc/chrony/chrony.conf.$2 ]; then mv /etc/chrony/chrony.conf.$2 /etc/chrony/chrony.conf fi fi -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: sparc (sparc64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-sparc64 Locale: LANG=fr_LU.UTF-8, LC_CTYPE=fr_LU.UTF-8 (charmap=UTF-8) Versions of packages chrony depends on: ii libc62.3.6.ds1-6 GNU C Library: Shared libraries ii libncurses5 5.5-4 Shared libraries for terminal hand ii libreadline5 5.1-9 GNU readline and history libraries ii ucf 2.0015 Update Configuration File: preserv chrony recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity of 397753 is important
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.22 severity 397753 important Bug#397753: adept continues installation even if you say no Severity set to `important' from `grave' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397659: jspwiki: FTBFS: source code not available
reassign 397659 jspwiki thanks The problem of uploading a new upstream version is that the later versions of the upstream (2.4.x) are currently non-buildable using only free tools Then please reupload the same upstream version of the package, with a changed upstream version number (e.g., 2.2.33.ds1). So, I'm merging this bug into the one filed against ftp.debian.org, as this is not really JSPWiki's problem but a problem of our package management system. While this is true, the package management system is not going to be fixed before etch, but the problem with the source for jspwiki not being included in main does need to be fixed. Reassigning back to jspwiki. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: libpoe-component-client-dns-perl: diff for NMU version 1:0.99-1.1
Processing commands for [EMAIL PROTECTED]: tags 395369 + patch Bug#395369: libpoe-component-client-dns-perl: FTBFS: Failed test t/04_errors.t There were no tags set. Tags added: patch thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392016: elog in stable is also vulnerable
* Ulf Harnhammar [2006-11-08 23:14:16+0100] I've just verified that elog in stable is vulnerable to all issues mentioned in bug #392016. Thank you very much for looking into this! I've got another report attached below. I'll look into this problem also and will keep this bug report open as I think elog should not enter to Etch due to all potential security issues which increase the work-load on our security team during the stable release cycle. --8--- FYI Hi, We are working with Mr. Stefan Ritt on this issue and waiting for the fix. Thanks, OS2A Forwarded Conversation Subject: ELOG Web Logbook Remote Denial of Service Vulnerability From: OS2A BTO [EMAIL PROTECTED] To: [EMAIL PROTECTED] Date: Wed, Nov 8, 2006 at 6:12 PM Attachments: os2a_1008.txt Hi, We recently came across a Denial of Service vulnerability in ELOG's elogd server which allows attackers to crash the service, thereby preventing legitimate access. Attached is our security advisory which describes the vulnerability in detail. Please let us know the time you might require to fix this issue. And also let us know if you have any questions. A quick and positive response from your side would be highly appreciated. Thanks, OS2A Team. From: Stefan Ritt [EMAIL PROTECTED] To: OS2A BTO [EMAIL PROTECTED] Date: Wed, Nov 8, 2006 at 6:31 PM Dear OS2A team, thank you for reporting this vulnerability and for the detailed analysis, I really appreciate. I fixed this problem and just released version 2.6.2-7 (SVN revision 1746). Best regards, Stefan Ritt -- Dr. Stefan Ritt Phone: +41 56 310 3728 Paul Scherrer Institute FAX: +41 56 310 2199 OLGA/021 mailto:[EMAIL PROTECTED] CH-5232 Villigen PSI http://midas.psi.ch/~stefan [Quoted text hidden] ELOG Web Logbook Remote Denial of Service Vulnerability OS2A ID: OS2A_1008Status: 10/31/2006 Issue Discovered 11/08/2006 Reported to the Vendor -- Fixed by Vendor -- Advisory Released Class: Denial of Service Severity: Medium Overview: - The Electronic Logbook (ELOG) is part of a family of applications known as weblogs. ELOG is a remarkable implementation of a weblog in its simplicity of use and versatility. http://midas.psi.ch/elog/index.html Description: Remote exploitation of a denial of service vulnerability in ELOG's elogd server allows attackers to crash the service, thereby preventing legitimate access. The [global] section in configuration file elogd.cfg is used for settings common to all logbooks. The vulnerability is due to improper handling of an HTTP GET request if logbook name 'global' (or any logbook name prefixed with global) is used in the request. When such a request is received, a NULL pointer dereference occurs, leading to a crash of the service. Only authenticated users can exploit this vulnerability if the application is configured with password. Impact: --- Successful exploitation allows a remote attacker to crash the elogd server. Affected Software(s): - ELOG 2.6.2 and prior. Proof of Concept: - The HTTP GET request given below is sufficient to crash affected server: http://www.example.com/global/ Analysis: --- #gdb ./elogd ... ... (gdb) break show_elog_list Breakpoint 2 at 0x809d6e0 (gdb) c Continuing. (no debugging symbols found) elogd 2.6.2 built Nov 8 2006, 01:25:48 revision 1699 Falling back to default group elog Falling back to default user elog Indexing logbooks ... done Server listening on port 8080 ... Breakpoint 2, 0x0809d6e0 in show_elog_list () (gdb) c Continuing. Program received signal SIGSEGV, Segmentation fault. 0x0809eb7a in show_elog_list () (gdb) bt #0 0x0809eb7a in show_elog_list () #1 0x in ?? () (gdb) i r eax0x0 0 ecx0x9d43d88164904328 edx0x0 0 ebx0x0 0 esp0xbfa8aca0 0xbfa8aca0 ebp0x80df40c0x80df40c esi0xbfb27050 -1078824880 edi0x0 0 eip0x809eb7a0x809eb7a eflags 0x200246 2097734 cs 0x73 115 ss 0x7b 123 ds 0x7b 123 es 0x7b 123 fs 0x0 0 gs 0x33 51 (gdb) x/i $eip 0x809eb7a show_elog_list+5274:mov(%eax),%eax The vulnerable code is at Line:16774 of elogd.c, n_msg = *lbs-n_el_index; where the pointer lbs is dereferenced before being null checked. --- elogd.c, Line:16772 - }
Bug#395369: libpoe-component-client-dns-perl: diff for NMU version 1:0.99-1.1
tags 395369 + patch
thanks
Hi,
The following is the diff for my libpoe-component-client-dns-perl 1:0.99-1.1
NMU.
diff -Nru /tmp/CmM0ZHoSXf/libpoe-component-client-dns-perl-0.9802/CHANGES
/tmp/mwuOukjqNi/libpoe-component-client-dns-perl-0.99/CHANGES
--- /tmp/CmM0ZHoSXf/libpoe-component-client-dns-perl-0.9802/CHANGES
2005-08-08 00:38:12.0 +0200
+++ /tmp/mwuOukjqNi/libpoe-component-client-dns-perl-0.99/CHANGES
2006-05-21 22:46:28.0 +0200
@@ -1,3 +1,39 @@
+=
+2006-05-21 20:45:46 v0_99
+=
+
+ 2006-05-21 20:45:11 (r58) by rcaputo; DNS.pm M
+
+Bump up the version.
+
+ 2006-05-21 20:44:39 (r57) by rcaputo; DNS.pm M
+
+Fix shutdown(). It was not performing nearly enough cleanup.
+
+Replace some post() calls with call() to avoid race conditions. In
+general, method interfaces should use call() rather than post() so
+that they affect internal structures synchronously.
+
+ 2006-05-21 20:43:08 (r56) by rcaputo
+ t/02_tag_args.t M; t/03_api_3.t M; t/05_api_4.t M; t/06_hosts.t M
+
+Turn on ASSERT_DEFAULT for some of the tests. Add _stop handlers so
+they don't fail with all POE asserts on.
+
+ 2006-03-24 03:58:51 (r55) by rcaputo; DNS.pm M
+
+Belatedly bump up the version.
+
+===
+2005-12-05 18:36:03 v0_9803
+===
+
+ 2005-12-05 18:34:05 (r53) by rcaputo; t/04_errors.t M
+
+Add the CATCH_EXCEPTIONS toggle that lets me catch my own damn
+errors. Sweet! Also expanded the common test code so that line
+numbers would be properly reported.
+
===
2005-08-07 22:37:35 v0_9802
===
@@ -51,67 +87,6 @@
Change cvs-log.perl to svn-log.perl in Makefile.PL.
-=
-2004-10-07 03:34:35 v0_98
-=
-
- 2004-10-07 03:34:35 (r42) by rcaputo; DNS.pm M
-
-Bump the version to 0.98 for release, and document the deprecations
-more carefully.
-
- 2004-10-07 03:16:45 (r41) by rcaputo; DNS.pm M
-
-Add code to look for /etc/hosts in various other places on Windows
-systems. Oh, the horrors!
-
- 2004-10-07 03:04:31 (r40) by rcaputo
- t/04_errors.t M; t/05_api_4.t A; MANIFEST M
-
-Added new tests to cover the additional public interface.
-
- 2004-10-07 03:03:42 (r39) by rcaputo; DNS.pm M
-
-Added the version 4 interface, which is just a method in front of
-the version 3 interface. The method-based interface lets us build a
-resolver cache later. The component will be able to return resolver
-answers from the cache without incurring any POE event loop overhead.
-
-Documented the new interface. Updated the SYNOPSIS to show it. Tested
-the SYNOPSIS code.
-
-Changed the private event handler names to include a leading
-underscore, so that Pod::Coverage will automatically discount them in
-its reports.
-
-Switched to object methods as event handlers. Moved the HEAP data
-into $self. This lets us get at the data members from the public
-object methods and the public/private event handlers.
-
- 2004-10-07 01:23:43 (r38) by rcaputo; DNS.pm M
-
-Rewrite the documentation to explain the new interface.
-
- 2004-10-07 01:23:08 (r37) by rcaputo; t/03_api_3.t M
-
-Remove some unnecessary code from this test. A previous test was
-copied as the basis for this one, and some useless code came along.
-
- 2004-10-06 18:06:11 (r36) by rcaputo
- DNS.pm M; t/03_api_3.t A; t/04_errors.t A; MANIFEST M; Makefile.PL M
-
-Add a saner (currently undocumented) API, and maintain backward
-compatibility. Increase test coverage to 80%.
-
- 2004-06-12 16:51:31 (r35) by rcaputo; DNS.pm M
-
-Overlord Q reported a syntax error in the SYNOPSIS. This change
-corrects the mistake and improves the code's readability.
-
- 2004-02-13 02:21:12 (r34) by rcaputo; MANIFEST M
-
-Add META.yml to the MANIFEST.
-
==
End of Excerpt
==
diff -Nru /tmp/CmM0ZHoSXf/libpoe-component-client-dns-perl-0.9802/DNS.pm
/tmp/mwuOukjqNi/libpoe-component-client-dns-perl-0.99/DNS.pm
--- /tmp/CmM0ZHoSXf/libpoe-component-client-dns-perl-0.9802/DNS.pm
2005-08-08 00:37:12.0 +0200
+++ /tmp/mwuOukjqNi/libpoe-component-client-dns-perl-0.99/DNS.pm
2006-05-21 22:45:24.0 +0200
@@ -1,4 +1,4 @@
-# $Id: DNS.pm 51 2005-08-01 17:07:05Z rcaputo $
+# $Id: DNS.pm 58 2006-05-21 20:45:11Z rcaputo $
# License and documentation are after __END__.
package POE::Component::Client::DNS;
@@ -6,7 +6,7 @@
use strict;
use vars qw($VERSION);
-$VERSION = '0.9802';
+$VERSION = '0.99';
use Carp qw(croak);
@@ -14,6 +14,8 @@
use Net::DNS;
use POE;
+use constant DEBUG = 0;
+
# Keep track of requests for each response socket. Used to pass data
# around select_read().
@@ -35,6 +37,7 @@
sub SF_HOSTS_INODE () { 7 }
sub SF_HOSTS_CACHE () { 8 }
sub
Bug#395369: marked as done (libpoe-component-client-dns-perl: FTBFS: Failed test t/04_errors.t)
Your message dated Thu, 09 Nov 2006 02:17:26 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#395369: fixed in libpoe-component-client-dns-perl 1:0.99-1 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: libpoe-component-client-dns-perl Version: 0.9802-1 Severity: serious Justification: FTBFS on i386, very likely to fail everywhere Usertags: grid5000 Hi, During a rebuild of all packages in etch, I discovered that your package failed to build on i386. The same failure could be reproduced in a sid chroot. Relevant parts: /usr/bin/make test make[1]: Entering directory `/root/libpoe-component-client-dns-perl-0.9802' PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0, 'blib/lib', 'blib/arch') t/*.t t/01_resolve.ok t/02_tag_argsok t/03_api_3...ok t/04_errors..NOK 4 # Failed test 'Must include a 'context' in Client::DNS request' # in t/04_errors.t at line 17. t/04_errors..NOK 5 # Failed test 'Must include a 'host' in Client::DNS request' # in t/04_errors.t at line 17. # Looks like you failed 2 tests of 9. t/04_errors..dubious Test returned status 2 (wstat 512, 0x200) DIED. FAILED tests 4-5 Failed 2/9 tests, 77.78% okay t/05_api_4...ok t/06_hosts...ok Failed Test Stat Wstat Total Fail List of Failed --- t/04_errors.t2 512 92 4-5 Failed 1/6 test scripts. 2/27 subtests failed. Files=6, Tests=27, 5 wallclock secs ( 1.22 cusr + 0.03 csys = 1.25 CPU) Failed 1/6 test programs. 2/27 subtests failed. make[1]: *** [test_dynamic] Error 255 make[1]: Leaving directory `/root/libpoe-component-client-dns-perl-0.9802' make: *** [build-stamp] Error 2 About the archive rebuilt: The rebuilt was done on about 60 AMD64 nodes of the Grid'5000 platform, using a chroot containing an etch i386 environment (not unstable). Internet was not accessible from the build nodes. About Grid'5000: The Grid'5000 project aims at building a highly reconfigurable experimental Grid platform gathering 9 sites and featuring a total of 5000 CPUs. Its main purpose is to serve as an experimental testbed for research in Grid Computing. To learn more about Grid'5000, read https://www.grid5000.fr/ -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Source: libpoe-component-client-dns-perl Source-Version: 1:0.99-1 We believe that the bug you reported is fixed in the latest version of libpoe-component-client-dns-perl, which is due to be installed in the Debian FTP archive: libpoe-component-client-dns-perl_0.99-1.diff.gz to pool/main/libp/libpoe-component-client-dns-perl/libpoe-component-client-dns-perl_0.99-1.diff.gz libpoe-component-client-dns-perl_0.99-1.dsc to pool/main/libp/libpoe-component-client-dns-perl/libpoe-component-client-dns-perl_0.99-1.dsc libpoe-component-client-dns-perl_0.99-1_all.deb to pool/main/libp/libpoe-component-client-dns-perl/libpoe-component-client-dns-perl_0.99-1_all.deb libpoe-component-client-dns-perl_0.99.orig.tar.gz to pool/main/libp/libpoe-component-client-dns-perl/libpoe-component-client-dns-perl_0.99.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Ablassmeier [EMAIL PROTECTED] (supplier of updated libpoe-component-client-dns-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 9 Nov 2006 11:00:13 +0100 Source: libpoe-component-client-dns-perl Binary:
Bug#397717: lmodern: install failed with error message warning: directory /usr/lib/X11/fonts/Type1 does not exist
daniel bosold [EMAIL PROTECTED] wrote: follows is the result of dpkg-reconfigure -plow (with lmodern.postinst including set -ex). adding a fresh lm.map to '/usr/share/texmf/fonts/map/dvips/lm/' seems to have fixed the _configuration_ problem, but a clean installation still fails. Ah, thank you - that is valuable information. The point is that lmodern 1.00 is not supposed to use lm.map any more... Please send us the output of kpsewhich --format='web2c files' updmap.cfg ls /etc/texmf/updmap.d/10lmodern.cfg* grep lm.map /etc/texmf/updmap.d/* and the file /etc/texmf/updmap.d/10lmodern.cfg It's possible that you have refused to accept the new version of this file, and therefore updmap still wants to use lm.map. Florent, should we add a check to lmodern's postinst, so that users get a clearer error message? Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
Bug#384223: marked as done (powermanga-data: non-free data included in the package)
Your message dated Thu, 09 Nov 2006 02:47:19 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#384223: fixed in powermanga 0.80-dfsg-1 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: powermanga-data Version: 0.80-3 Severity: serious Justification: Policy 2.1 There are no information on where data files came from, but at least one of the included files appears to be non-free: /usr/share/games/powermanga/sounds/bonus4.wav The following strings are included in the file: Windows 95 Utopia Sound Scheme 1995 Microsoft Corporation Utopia Question It is one of the Windows standard sounds. It is not free (and also non distributable at all, not even on non-free section). Origin from all other data files (sound, music, graphics...) should be clarified, since they can be in the same situation. Upstream authors should include information stating whether data is made from scratch or based on other sources. It is always a good idea to add some information on origin of artwork and tools used. When data is based on other free sources, credits and a pointer to the proper license should be given. When data is based on non-free (or unlicensed) sources, obviously can't be distributed by Debian and need to be replaced. And when data is created from scratch, a short notice is appreciated to make it clear. ---End Message--- ---BeginMessage--- Source: powermanga Source-Version: 0.80-dfsg-1 We believe that the bug you reported is fixed in the latest version of powermanga, which is due to be installed in the Debian FTP archive: powermanga-data_0.80-dfsg-1_all.deb to pool/main/p/powermanga/powermanga-data_0.80-dfsg-1_all.deb powermanga_0.80-dfsg-1.diff.gz to pool/main/p/powermanga/powermanga_0.80-dfsg-1.diff.gz powermanga_0.80-dfsg-1.dsc to pool/main/p/powermanga/powermanga_0.80-dfsg-1.dsc powermanga_0.80-dfsg-1_i386.deb to pool/main/p/powermanga/powermanga_0.80-dfsg-1_i386.deb powermanga_0.80-dfsg.orig.tar.gz to pool/main/p/powermanga/powermanga_0.80-dfsg.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sam Hocevar (Debian packages) [EMAIL PROTECTED] (supplier of updated powermanga package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 9 Nov 2006 11:15:24 +0100 Source: powermanga Binary: powermanga powermanga-data Architecture: source i386 all Version: 0.80-dfsg-1 Distribution: unstable Urgency: high Maintainer: Debian Games Team pkg-games-devel@lists.alioth.debian.org Changed-By: Sam Hocevar (Debian packages) [EMAIL PROTECTED] Description: powermanga - vertical shoot 'em up with colourful 3D graphics powermanga-data - graphics and audio data for powermanga Closes: 384223 397707 Changes: powermanga (0.80-dfsg-1) unstable; urgency=high . * Repackage previous upload as non-native. * Acknowledge NMU (Closes: #384223). * debian/control: + Add missing build-depends on zlib1g-dev (Closes: #397707). Files: e8af6eb1b5b30c4aaebabd14d4f494eb 813 games optional powermanga_0.80-dfsg-1.dsc 9a148e00d5291f9238c195dfd9cc1071 6815266 games optional powermanga_0.80-dfsg.orig.tar.gz 38b90dcc228743a405954ee6eb45f082 544 games optional powermanga_0.80-dfsg-1.diff.gz dfca415a9355a82b5966b49923980134 6393218 games optional powermanga-data_0.80-dfsg-1_all.deb f5005eb0778fb5345ab29751ad10a99b 133538 games optional powermanga_0.80-dfsg-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFUwECfPP1rylJn2ERAiWtAJ4qsgwmUe8pT6NbwrClyIbYFLMiKQCeO/eW GxjKTM6IueKuw1FShxJd20E= =8wXc -END PGP SIGNATURE- ---End Message---
Bug#354850: marked as done (mysql-server: upgrade 4.1-5.0 may break installation)
Your message dated Thu, 09 Nov 2006 02:52:37 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#354544: fixed in mysql-dfsg-5.0 5.0.26-3 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: mysql-server Version: 5.0.18-8 Severity: normal Hello, when upgrading from 4.1 to 5.0, I get a message cannot upgrade if ISAM tables are present. Ok... why not convert them? But hey, the old server which could have done it is already removed at the time I get this message, and the installation process just bails out... bummer! I suggest that the upgrade script _first_ determines if there are any ISAM tables left over, then offers to automatically convert them to MyISAM (or just do it, don't know), and then removes the old server and installs the new one, not the other way round. Currently, I have: $ dpkg -l mysql-server Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- iU mysql-server 5.0.18-8 mysql database server (current version) Thank you! Best, --Toni++ PS: No need to fix it just for me... -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.27-2-686-smp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages mysql-server depends on: pn mysql-server-5.0 none (no description available) mysql-server recommends no packages. -- debconf information: * mysql-server/skip_networking: false mysql-server/really_downgrade_from_41: false mysql-server/want_chroot: false * mysql-server/start_on_boot: true mysql-server/postrm_remove_databases: false * mysql-server/mysql_install_db_notes: mysql-server/nis_warning: mysql-server/mysql_update_hints1: * mysql-server/postrm_remove_database: false mysql-server/fix_privileges_warning: ---End Message--- ---BeginMessage--- Source: mysql-dfsg-5.0 Source-Version: 5.0.26-3 We believe that the bug you reported is fixed in the latest version of mysql-dfsg-5.0, which is due to be installed in the Debian FTP archive: libmysqlclient15-dev_5.0.26-3_amd64.deb to pool/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.26-3_amd64.deb libmysqlclient15off_5.0.26-3_amd64.deb to pool/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.26-3_amd64.deb mysql-client-5.0_5.0.26-3_amd64.deb to pool/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.26-3_amd64.deb mysql-client_5.0.26-3_all.deb to pool/main/m/mysql-dfsg-5.0/mysql-client_5.0.26-3_all.deb mysql-common_5.0.26-3_all.deb to pool/main/m/mysql-dfsg-5.0/mysql-common_5.0.26-3_all.deb mysql-dfsg-5.0_5.0.26-3.diff.gz to pool/main/m/mysql-dfsg-5.0/mysql-dfsg-5.0_5.0.26-3.diff.gz mysql-dfsg-5.0_5.0.26-3.dsc to pool/main/m/mysql-dfsg-5.0/mysql-dfsg-5.0_5.0.26-3.dsc mysql-server-4.1_5.0.26-3_amd64.deb to pool/main/m/mysql-dfsg-5.0/mysql-server-4.1_5.0.26-3_amd64.deb mysql-server-5.0_5.0.26-3_amd64.deb to pool/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.26-3_amd64.deb mysql-server_5.0.26-3_all.deb to pool/main/m/mysql-dfsg-5.0/mysql-server_5.0.26-3_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. sean finney [EMAIL PROTECTED] (supplier of updated mysql-dfsg-5.0 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 03 Nov 2006 18:34:46 +0100 Source: mysql-dfsg-5.0 Binary: libmysqlclient15-dev mysql-client mysql-client-5.0 mysql-server mysql-server-4.1 mysql-server-5.0 mysql-common libmysqlclient15off Architecture: source all amd64 Version: 5.0.26-3 Distribution: unstable Urgency: high Maintainer: Christian Hammers [EMAIL PROTECTED] Changed-By: sean finney [EMAIL PROTECTED] Description: libmysqlclient15-dev - mysql database development files libmysqlclient15off - mysql database client library mysql-client - mysql
Processed: Re: Advice on PIC issue
Processing commands for [EMAIL PROTECTED]: tags 397603 + pending Bug#397603: cyrus-sasl2: FTBFS on amd64 (PIC linking issue) There were no tags set. Bug#397605: cyrus-sasl2: FTBFS on hppa (PIC linking issue) Tags added: pending thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397707: marked as done (powermanga: FTBFS: lispreader.hpp:28:18: error: zlib.h: No such file or directory)
Your message dated Thu, 09 Nov 2006 02:47:19 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#397707: fixed in powermanga 0.80-dfsg-1 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: powermanga Version: 0.80+dfsg-1 Severity: serious Justification: FTBFS on i386, very likely to fail everywhere else Usertags: grid5000 Hi, During a rebuild of all packages in etch, I discovered that your package failed to build on i386. Relevant parts: if g++ -DHAVE_CONFIG_H -I. -I. -I..-DPREFIX=\/usr\ -DSCOREFILE=\/var/games/powermanga/powermanga.hi\ -I -I/usr/include/SDL -D_GNU_SOURCE=1 -D_REENTRANT -O3 -Wall -I/usr/include/SDL -D_GNU_ SOURCE=1 -D_REENTRANT -MT powermanga-afficheEtoiles.o -MD -MP -MF .deps/powermanga-afficheEtoiles.Tpo -c -o powermanga-afficheEtoiles.o `test -f 'afficheEtoiles.cpp' || echo './'`afficheEtoiles. cpp; \ then mv -f .deps/powermanga-afficheEtoiles.Tpo .deps/powermanga-afficheEtoiles.Po; else rm -f .deps/powermanga-afficheEtoiles.Tpo; exit 1; fi In file included from configfile.hpp:29, from powermanga.hpp:1196, from afficheEtoiles.cpp:23: lispreader.hpp:28:18: error: zlib.h: No such file or directory lispreader.hpp:110: error: 'gzFile' has not been declared make[3]: *** [powermanga-afficheEtoiles.o] Error 1 The full build log is available from http://ox.blop.info/bazaar/buildlogs/20061107/ About the archive rebuilt: The rebuilt was done on about 30 AMD64 nodes of the Grid'5000 platform, using a clean chroot containing an etch i386 environment (not unstable). Internet was not accessible from the build systems. The builds were processed as root. About Grid'5000: Grid'5000 is an highly reconfigurable experimental Grid platform gathering 9 sites and featuring a total of 5000 CPUs. It serves as a testbed for research in Grid Computing. See https://www.grid5000.fr/ -- | Lucas Nussbaum | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | ---End Message--- ---BeginMessage--- Source: powermanga Source-Version: 0.80-dfsg-1 We believe that the bug you reported is fixed in the latest version of powermanga, which is due to be installed in the Debian FTP archive: powermanga-data_0.80-dfsg-1_all.deb to pool/main/p/powermanga/powermanga-data_0.80-dfsg-1_all.deb powermanga_0.80-dfsg-1.diff.gz to pool/main/p/powermanga/powermanga_0.80-dfsg-1.diff.gz powermanga_0.80-dfsg-1.dsc to pool/main/p/powermanga/powermanga_0.80-dfsg-1.dsc powermanga_0.80-dfsg-1_i386.deb to pool/main/p/powermanga/powermanga_0.80-dfsg-1_i386.deb powermanga_0.80-dfsg.orig.tar.gz to pool/main/p/powermanga/powermanga_0.80-dfsg.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sam Hocevar (Debian packages) [EMAIL PROTECTED] (supplier of updated powermanga package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 9 Nov 2006 11:15:24 +0100 Source: powermanga Binary: powermanga powermanga-data Architecture: source i386 all Version: 0.80-dfsg-1 Distribution: unstable Urgency: high Maintainer: Debian Games Team pkg-games-devel@lists.alioth.debian.org Changed-By: Sam Hocevar (Debian packages) [EMAIL PROTECTED] Description: powermanga - vertical shoot 'em up with colourful 3D graphics powermanga-data - graphics and audio data for powermanga Closes: 384223 397707 Changes: powermanga (0.80-dfsg-1) unstable; urgency=high . * Repackage previous upload as non-native. * Acknowledge NMU (Closes: #384223). * debian/control: + Add missing build-depends on zlib1g-dev (Closes: #397707). Files: e8af6eb1b5b30c4aaebabd14d4f494eb 813 games optional powermanga_0.80-dfsg-1.dsc 9a148e00d5291f9238c195dfd9cc1071 6815266 games optional powermanga_0.80-dfsg.orig.tar.gz 38b90dcc228743a405954ee6eb45f082 544 games optional powermanga_0.80-dfsg-1.diff.gz dfca415a9355a82b5966b49923980134 6393218 games optional powermanga-data_0.80-dfsg-1_all.deb f5005eb0778fb5345ab29751ad10a99b 133538 games optional powermanga_0.80-dfsg-1_i386.deb -BEGIN PGP
Bug#387498: mips: system() hangs when compiled with -pg (gprof profiling(.
reassign 387498 linux-2.6
retitle 387498 [hppa/mipsel] system() hangs when compiled with -pg (gprof
profiling)
thanks
=
[EMAIL PROTECTED]:~$ cat t.c
int
main(int argc,char * argv[]) {return system(argv[1]);}
[EMAIL PROTECTED]:~$ [EMAIL PROTECTED]:~$ cc -g t.c -o t
[EMAIL PROTECTED]:~$ ./t echo g
g
[EMAIL PROTECTED]:~$ echo $?
0
[EMAIL PROTECTED]:~$ cc -g -pg t.c -o t
[EMAIL PROTECTED]:~$ ./t echo g
[1]+ Stopped ./t echo g
[EMAIL PROTECTED]:~$ cat t.c
int
main(int argc,char * argv[]) {return system(argv[1]);}
[EMAIL PROTECTED]:~$ [EMAIL PROTECTED]:~$ cc -g t.c -o t
[EMAIL PROTECTED]:~$ ./t echo g
g
[EMAIL PROTECTED]:~$ echo $?
0
[EMAIL PROTECTED]:~$ cc -g -pg t.c -o t
[EMAIL PROTECTED]:~$ ./t echo g
[1]+ Stopped ./t echo g
I confirm the problem is solved with the latest kernel (2.6.18-4) on
mips. I will test on hppa and mipsel later.
That proves that the bug is really a kernel bug and not a libc6 bug, I
am therefore reassigning the bug to linux-2.6 only.
--
.''`. Aurelien Jarno | GPG: 1024D/F1BCDB73
: :' : Debian developer | Electrical Engineer
`. `' [EMAIL PROTECTED] | [EMAIL PROTECTED]
`-people.debian.org/~aurel32 | www.aurel32.net
Bug#397603: Advice on PIC issue
tags 397603 + pending thanks On Wed, 2006-11-08 at 13:03 -0200, Henrique de Moraes Holschuh wrote: Usually, linking libs with non-pic code is a bug in the makefile, especially when libtool is being used (libtool should be handling this fine, and if we relibtoolize, it *really* should be handling it fine). When using libtool + automake (1.9 or 1.10), it gets especially difficult to get it wrong :-) Yeah! :) I can't reproduce this consistently on a vserver running on an amd64 box. It seems that just before submitting that bug, I was able to reproduce it, but now I can't reproduce it any more. That said, I want to try the suggestion below. On Wed, 2006-11-08 at 20:39 +0100, Andreas Metzler wrote: Anybody for this - a phony target re-generating proper ./libs/libsasldb.a? libsasldb.a: libsasldb.la $(SASL_DB_BACKEND_STATIC) cd .libs $(AR) cru $@ $(SASL_DB_BACKEND_STATIC) I think you've helped me see the problem :) The above is good, but I would do it the other way around, so to speak. The way I read sasldb/Makefile.am, the last rule is for generating the static version of libsasldb.a. If the idea is to put shared objects in .libs and static objects in ., then I'd propose the following patch: --- sasldb/Makefile.am (revision 133) +++ sasldb/Makefile.am (working copy) @@ -63,6 +63,6 @@ EXTRA_libsasldb_a_SOURCES = libsasldb.a: libsasldb.la $(SASL_DB_BACKEND_STATIC) - $(AR) cru .libs/$@ $(SASL_DB_BACKEND_STATIC) + $(AR) cru $@ $(SASL_DB_BACKEND_STATIC) This results in the following build log fragment (some warnings removed to make it easier to follow): x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../include -I/usr/include/mysql -I/usr/include/postgresql -I/usr/include -Wall -W -Wall -g -O2 -Wl,-z,defs -MT db_berkeley.lo -MD -MP -MF .deps/db_berkeley.Tpo -c db_berkeley.c -fPIC -DPIC -o .libs/db_berkeley.o x86_64-linux-gnu-gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../include -I/usr/include/mysql -I/usr/include/postgresql -I/usr/include -Wall -W -Wall -g -O2 -Wl,-z,defs -MT db_berkeley.lo -MD -MP -MF .deps/db_berkeley.Tpo -c db_berkeley.c -o db_berkeley.o /dev/null 21 /bin/sh ../libtool --tag=CC --mode=link x86_64-linux-gnu-gcc -Wall -W -Wall -g -O2 -Wl,-z,defs -o libsasldb.la allockey.lo db_berkeley.lo -lresolv ar cru .libs/libsasldb.a .libs/allockey.o .libs/db_berkeley.o ranlib .libs/libsasldb.a creating libsasldb.la (cd .libs rm -f libsasldb.la ln -s ../libsasldb.la libsasldb.la) ar cru libsasldb.a db_berkeley.o allockey.o So lines 1 and 2 create PIC and non-PIC versions, respectively. Line 4 creates an archive with PIC versions, and the last line creates an archive with non-PIC versions. Apparently libtool takes care of the PIC case, and the Makefile.am rule takes care of the non-PIC case. (?) I'm tagging this pending and committing the above with a Closes: line in the changelog. If it doesn't work (either when the buildds have run the next upload, or someone with an amd64/hppa box has tested this) we'll just reopen the bug. Cheers, -- Fabian Fagerholm [EMAIL PROTECTED] signature.asc Description: This is a digitally signed message part
Bug#354544: marked as done (ISAM trap in package upgrade)
Your message dated Thu, 09 Nov 2006 02:52:37 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#354544: fixed in mysql-dfsg-5.0 5.0.26-3 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: mysql-server-5.0 Version: 5.0.18-8 Hi, ugly trap in mysql-server-package: When the preinst script finds any .ISM files in /var/lib/mysql, it denies the upgrade. But then, the old mysql-server-package is already removed, and current debian distribution does not contain the old mysql-server anymore. No chance to update the databases to a newer file format anymore, no way to get a mysql-server running. regards Hadmut ---End Message--- ---BeginMessage--- Source: mysql-dfsg-5.0 Source-Version: 5.0.26-3 We believe that the bug you reported is fixed in the latest version of mysql-dfsg-5.0, which is due to be installed in the Debian FTP archive: libmysqlclient15-dev_5.0.26-3_amd64.deb to pool/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.26-3_amd64.deb libmysqlclient15off_5.0.26-3_amd64.deb to pool/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.26-3_amd64.deb mysql-client-5.0_5.0.26-3_amd64.deb to pool/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.26-3_amd64.deb mysql-client_5.0.26-3_all.deb to pool/main/m/mysql-dfsg-5.0/mysql-client_5.0.26-3_all.deb mysql-common_5.0.26-3_all.deb to pool/main/m/mysql-dfsg-5.0/mysql-common_5.0.26-3_all.deb mysql-dfsg-5.0_5.0.26-3.diff.gz to pool/main/m/mysql-dfsg-5.0/mysql-dfsg-5.0_5.0.26-3.diff.gz mysql-dfsg-5.0_5.0.26-3.dsc to pool/main/m/mysql-dfsg-5.0/mysql-dfsg-5.0_5.0.26-3.dsc mysql-server-4.1_5.0.26-3_amd64.deb to pool/main/m/mysql-dfsg-5.0/mysql-server-4.1_5.0.26-3_amd64.deb mysql-server-5.0_5.0.26-3_amd64.deb to pool/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.26-3_amd64.deb mysql-server_5.0.26-3_all.deb to pool/main/m/mysql-dfsg-5.0/mysql-server_5.0.26-3_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. sean finney [EMAIL PROTECTED] (supplier of updated mysql-dfsg-5.0 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 03 Nov 2006 18:34:46 +0100 Source: mysql-dfsg-5.0 Binary: libmysqlclient15-dev mysql-client mysql-client-5.0 mysql-server mysql-server-4.1 mysql-server-5.0 mysql-common libmysqlclient15off Architecture: source all amd64 Version: 5.0.26-3 Distribution: unstable Urgency: high Maintainer: Christian Hammers [EMAIL PROTECTED] Changed-By: sean finney [EMAIL PROTECTED] Description: libmysqlclient15-dev - mysql database development files libmysqlclient15off - mysql database client library mysql-client - mysql database client (current version) mysql-client-5.0 - mysql database client binaries mysql-common - mysql database common files (e.g. /etc/mysql/my.cnf) mysql-server - mysql database server (current version) mysql-server-4.1 - mysql database server (transitional package) mysql-server-5.0 - mysql database server binaries Closes: 354544 354850 394262 Changes: mysql-dfsg-5.0 (5.0.26-3) unstable; urgency=high . [sean finney] * Fix for the deadly ISAM trap. Now during upgrades we will do our very best to convert pre-existing ISAM format tables using the binaries from the previous package. Success is not guaranteed, but this is probably as good as it gets. Note that this also necessitates re-introducing an (empty transitional) mysql-server-4.1 package. Closes: #354544, #354850 * Remove a couple spurious and wrongly placed WARNING statements from 45_warn-CLI-passwords.dpatch. thanks to Dan Jacobsen for pointing these out. Closes: #394262 Files: e4ef4cda4bae61b24c3ee5286dd7afe4 1108 misc optional mysql-dfsg-5.0_5.0.26-3.dsc 47fbff160c79ed2b9c54b02d7ca578e8 137055 misc optional mysql-dfsg-5.0_5.0.26-3.diff.gz bf564226fd807fdd409fa69ea8f73a88 46386 misc optional mysql-common_5.0.26-3_all.deb ec8c7d79fe783aa50211d841e434b509 43654 misc optional mysql-server_5.0.26-3_all.deb e25082866196f38890efe8b3b8ba487e 41578 misc optional mysql-client_5.0.26-3_all.deb edb0bf35bb4fd45b70564c253e11f627 1813094 libs optional
Processed: Re: jspwiki: FTBFS: source code not available
Processing commands for [EMAIL PROTECTED]: reassign 397659 ftp.debian.org Bug#397659: jspwiki: FTBFS: source code not available Bug#391193: orig.tar.gz not in pool/main for jspwiki 2.2.33 Bug reassigned from package `ftp.debian.org' to `ftp.debian.org'. severity 397659 normal Bug#397659: jspwiki: FTBFS: source code not available Bug#391193: orig.tar.gz not in pool/main for jspwiki 2.2.33 Severity set to `normal' from `serious' retitle 397659 Moving a package from contrib to main in a non-orig-source upload doesn't move the orig.tar.gz Bug#397659: jspwiki: FTBFS: source code not available Changed Bug title. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#354850: marked as done (mysql-server: upgrade 4.1-5.0 may break installation)
Your message dated Thu, 09 Nov 2006 02:52:37 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#354850: fixed in mysql-dfsg-5.0 5.0.26-3 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: mysql-server Version: 5.0.18-8 Severity: normal Hello, when upgrading from 4.1 to 5.0, I get a message cannot upgrade if ISAM tables are present. Ok... why not convert them? But hey, the old server which could have done it is already removed at the time I get this message, and the installation process just bails out... bummer! I suggest that the upgrade script _first_ determines if there are any ISAM tables left over, then offers to automatically convert them to MyISAM (or just do it, don't know), and then removes the old server and installs the new one, not the other way round. Currently, I have: $ dpkg -l mysql-server Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed |/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- iU mysql-server 5.0.18-8 mysql database server (current version) Thank you! Best, --Toni++ PS: No need to fix it just for me... -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.27-2-686-smp Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages mysql-server depends on: pn mysql-server-5.0 none (no description available) mysql-server recommends no packages. -- debconf information: * mysql-server/skip_networking: false mysql-server/really_downgrade_from_41: false mysql-server/want_chroot: false * mysql-server/start_on_boot: true mysql-server/postrm_remove_databases: false * mysql-server/mysql_install_db_notes: mysql-server/nis_warning: mysql-server/mysql_update_hints1: * mysql-server/postrm_remove_database: false mysql-server/fix_privileges_warning: ---End Message--- ---BeginMessage--- Source: mysql-dfsg-5.0 Source-Version: 5.0.26-3 We believe that the bug you reported is fixed in the latest version of mysql-dfsg-5.0, which is due to be installed in the Debian FTP archive: libmysqlclient15-dev_5.0.26-3_amd64.deb to pool/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.26-3_amd64.deb libmysqlclient15off_5.0.26-3_amd64.deb to pool/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.26-3_amd64.deb mysql-client-5.0_5.0.26-3_amd64.deb to pool/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.26-3_amd64.deb mysql-client_5.0.26-3_all.deb to pool/main/m/mysql-dfsg-5.0/mysql-client_5.0.26-3_all.deb mysql-common_5.0.26-3_all.deb to pool/main/m/mysql-dfsg-5.0/mysql-common_5.0.26-3_all.deb mysql-dfsg-5.0_5.0.26-3.diff.gz to pool/main/m/mysql-dfsg-5.0/mysql-dfsg-5.0_5.0.26-3.diff.gz mysql-dfsg-5.0_5.0.26-3.dsc to pool/main/m/mysql-dfsg-5.0/mysql-dfsg-5.0_5.0.26-3.dsc mysql-server-4.1_5.0.26-3_amd64.deb to pool/main/m/mysql-dfsg-5.0/mysql-server-4.1_5.0.26-3_amd64.deb mysql-server-5.0_5.0.26-3_amd64.deb to pool/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.26-3_amd64.deb mysql-server_5.0.26-3_all.deb to pool/main/m/mysql-dfsg-5.0/mysql-server_5.0.26-3_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. sean finney [EMAIL PROTECTED] (supplier of updated mysql-dfsg-5.0 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 03 Nov 2006 18:34:46 +0100 Source: mysql-dfsg-5.0 Binary: libmysqlclient15-dev mysql-client mysql-client-5.0 mysql-server mysql-server-4.1 mysql-server-5.0 mysql-common libmysqlclient15off Architecture: source all amd64 Version: 5.0.26-3 Distribution: unstable Urgency: high Maintainer: Christian Hammers [EMAIL PROTECTED] Changed-By: sean finney [EMAIL PROTECTED] Description: libmysqlclient15-dev - mysql database development files libmysqlclient15off - mysql database client library mysql-client - mysql
Bug#354544: marked as done (ISAM trap in package upgrade)
Your message dated Thu, 09 Nov 2006 02:52:37 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#354850: fixed in mysql-dfsg-5.0 5.0.26-3 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: mysql-server-5.0 Version: 5.0.18-8 Hi, ugly trap in mysql-server-package: When the preinst script finds any .ISM files in /var/lib/mysql, it denies the upgrade. But then, the old mysql-server-package is already removed, and current debian distribution does not contain the old mysql-server anymore. No chance to update the databases to a newer file format anymore, no way to get a mysql-server running. regards Hadmut ---End Message--- ---BeginMessage--- Source: mysql-dfsg-5.0 Source-Version: 5.0.26-3 We believe that the bug you reported is fixed in the latest version of mysql-dfsg-5.0, which is due to be installed in the Debian FTP archive: libmysqlclient15-dev_5.0.26-3_amd64.deb to pool/main/m/mysql-dfsg-5.0/libmysqlclient15-dev_5.0.26-3_amd64.deb libmysqlclient15off_5.0.26-3_amd64.deb to pool/main/m/mysql-dfsg-5.0/libmysqlclient15off_5.0.26-3_amd64.deb mysql-client-5.0_5.0.26-3_amd64.deb to pool/main/m/mysql-dfsg-5.0/mysql-client-5.0_5.0.26-3_amd64.deb mysql-client_5.0.26-3_all.deb to pool/main/m/mysql-dfsg-5.0/mysql-client_5.0.26-3_all.deb mysql-common_5.0.26-3_all.deb to pool/main/m/mysql-dfsg-5.0/mysql-common_5.0.26-3_all.deb mysql-dfsg-5.0_5.0.26-3.diff.gz to pool/main/m/mysql-dfsg-5.0/mysql-dfsg-5.0_5.0.26-3.diff.gz mysql-dfsg-5.0_5.0.26-3.dsc to pool/main/m/mysql-dfsg-5.0/mysql-dfsg-5.0_5.0.26-3.dsc mysql-server-4.1_5.0.26-3_amd64.deb to pool/main/m/mysql-dfsg-5.0/mysql-server-4.1_5.0.26-3_amd64.deb mysql-server-5.0_5.0.26-3_amd64.deb to pool/main/m/mysql-dfsg-5.0/mysql-server-5.0_5.0.26-3_amd64.deb mysql-server_5.0.26-3_all.deb to pool/main/m/mysql-dfsg-5.0/mysql-server_5.0.26-3_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. sean finney [EMAIL PROTECTED] (supplier of updated mysql-dfsg-5.0 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Fri, 03 Nov 2006 18:34:46 +0100 Source: mysql-dfsg-5.0 Binary: libmysqlclient15-dev mysql-client mysql-client-5.0 mysql-server mysql-server-4.1 mysql-server-5.0 mysql-common libmysqlclient15off Architecture: source all amd64 Version: 5.0.26-3 Distribution: unstable Urgency: high Maintainer: Christian Hammers [EMAIL PROTECTED] Changed-By: sean finney [EMAIL PROTECTED] Description: libmysqlclient15-dev - mysql database development files libmysqlclient15off - mysql database client library mysql-client - mysql database client (current version) mysql-client-5.0 - mysql database client binaries mysql-common - mysql database common files (e.g. /etc/mysql/my.cnf) mysql-server - mysql database server (current version) mysql-server-4.1 - mysql database server (transitional package) mysql-server-5.0 - mysql database server binaries Closes: 354544 354850 394262 Changes: mysql-dfsg-5.0 (5.0.26-3) unstable; urgency=high . [sean finney] * Fix for the deadly ISAM trap. Now during upgrades we will do our very best to convert pre-existing ISAM format tables using the binaries from the previous package. Success is not guaranteed, but this is probably as good as it gets. Note that this also necessitates re-introducing an (empty transitional) mysql-server-4.1 package. Closes: #354544, #354850 * Remove a couple spurious and wrongly placed WARNING statements from 45_warn-CLI-passwords.dpatch. thanks to Dan Jacobsen for pointing these out. Closes: #394262 Files: e4ef4cda4bae61b24c3ee5286dd7afe4 1108 misc optional mysql-dfsg-5.0_5.0.26-3.dsc 47fbff160c79ed2b9c54b02d7ca578e8 137055 misc optional mysql-dfsg-5.0_5.0.26-3.diff.gz bf564226fd807fdd409fa69ea8f73a88 46386 misc optional mysql-common_5.0.26-3_all.deb ec8c7d79fe783aa50211d841e434b509 43654 misc optional mysql-server_5.0.26-3_all.deb e25082866196f38890efe8b3b8ba487e 41578 misc optional mysql-client_5.0.26-3_all.deb edb0bf35bb4fd45b70564c253e11f627 1813094 libs optional
Bug#397766: Under AMD64 plaform, libdts-dev should be compiled with -fPIC option
Package: libdts-dev Version: 0.0.2-svn-1 Severity: grave When compiling ffmpeg under Debian AMD64, the compiler complains about libdts-dev headers. gcc -shared -Wl,-soname,libavcodec.so.51 -Wl,--warn-common -pthread -rdynamic -export-dynamic -Wl,--as-needed -Wl,-rpath-link,/home/jmpoure/logiciels/ffmpeg/ffmpeg/libavcodec -Wl,-rpath-link,/home/jmpoure/logiciels/ffmpeg/ffmpeg/libavformat -Wl,-rpath-link,/home/jmpoure/logiciels/ffmpeg/ffmpeg/libavutil -o libavcodec.so.51 bitstream.o utils.o allcodecs.o mpegvideo.o jrevdct.o jfdctfst.o jfdctint.o mjpeg.o resample.o resample2.o dsputil.o motion_est.o imgconvert.o mpeg12.o mpegaudiodec.o simple_idct.o ratecontrol.o eval.o error_resilience.o fft.o mdct.o raw.o golomb.o cabac.o faandct.o parser.o vp3dsp.o h264idct.o rangecoder.o pnm.o h263.o msmpeg4.o h263dec.o opt.o bitstream_filter.o audioconvert.o imgresample.o i386/fdct_mmx.o i386/cputest.o i386/dsputil_mmx.o i386/mpegvideo_mmx.o i386/motion_est_mmx.o i386/simple_idct_mmx.o i386/idct_mmx_xvid.o i386/fft_sse.o i386/vp3dsp_mmx.o i386/vp3dsp_sse2.o i386/fft_3dn.o i386/fft_3dn2.o i386/snowdsp_mmx.o i386/idct_mmx.o i386/cavsdsp_mmx.o aasc.o ac3enc.o alac.o asv1.o avs.o bmp.o cavs.o cavsdsp.o cinepak.o cljr.o cook.o cscd.o lzo.o cyuv.o dsicinav.o dvbsubdec.o dvbsub.o dvdsubdec.o dvdsubenc.o dv.o 8bps.o ffv1.o huffyuv.o flac.o flacenc.o flashsv.o flicvideo.o 4xm.o fraps.o gifdec.o lzw.o gif.o h261.o h264.o idcinvideo.o imc.o indeo2.o indeo3.o interplayvideo.o dpcm.o kmvc.o loco.o mace.o mmvideo.o mpegaudio.o msrle.o msvideo1.o lcl.o nuv.o rtjpeg.o png.o qdm2.o qdrw.o qpeg.o qtrle.o ra144.o ra288.o roqvideo.o rpza.o rv10.o shorten.o smacker.o smc.o snow.o sonic.o svq1.o targa.o vp3.o tiertexseqv.o tiff.o truemotion1.o truemotion2.o truespeech.o tscc.o tta.o ulti.o vc1.o vc1dsp.o vcr1.o vmdav.o vmnc.o vorbis.o vorbis_data.o vorbis_enc.o vp5.o vp56.o vp56data.o vp6.o vqavideo.o wavpack.o wmadec.o wnv1.o ws-snd1.o xan.o xl.o zmbv.o pcm.o adpcm.o adx.o g726.o faad.o faac.o xvidff.o xvid_rc.o x264.o mp3lameaudio.o oggvorbis.o libgsm.o a52dec.o liba52/bit_allocate.o liba52/bitstream.o liba52/downmix.o liba52/imdct.o liba52/parse.o liba52/crc.o liba52/resample.o dtsdec.o pthread.o -L/home/jmpoure/logiciels/ffmpeg/ffmpeg/libavutil -lavutil -lm -lz -ldts -lm -lgsm -lmp3lame -lm -lvorbis -lvorbisenc -logg -logg -lxvidcore -lx264 -lfaac -lfaad -ldl /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/4.1.2/../../../../lib64/libdts.a(parse.o): relocation R_X86_64_32S against `a local symbol' can not be used when making a shared object; recompile with -fPIC /usr/lib/gcc/x86_64-linux-gnu/4.1.2/../../../../lib64/libdts.a: ne peut lire les symboles: Mauvaise valeur collect2: ld a retourné 1 code d'état d'exécution Under AMD64 plaform, libdts-dev should be compiled with -fPIC option. Kind regards, Jean-Michel
Bug#397683: marked as done (trac 0.10.1 is available; it includes a security fix for a CSRF vulnerability)
Your message dated Thu, 09 Nov 2006 03:17:17 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#397683: fixed in trac 0.10.1-1 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: trac Version: 0.10-3dkg1 Severity: grave Tags: security Justification: user security hole Trac 0.10.1 is now available. It contains a fix for a CSRF vulnerability: http://trac.edgewall.org/wiki/TracDownload It would be great if this new version could make it into debian soon. Thanks for maintaining trac in debian! --dkg -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing'), (200, 'unstable'), (101, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages trac depends on: ii python2.4.3-11 An interactive high-level object-o ii python-clearsilver0.10.3-4 python bindings for clearsilver ii python-pysqlite2 2.3.2-1python interface to SQLite 3 ii python-subversion 1.4.0-5Python bindings for Subversion ii python-support0.5.4 automated rebuilding support for p ii subversion1.4.0-5Advanced version control system Versions of packages trac recommends: ii apache2 2.2.3-3Next generation, scalable, extenda ii apache2-mpm-prefork [httpd] 2.2.3-3Traditional model for Apache HTTPD pn python-setuptools none (no description available) -- no debconf information ---End Message--- ---BeginMessage--- Source: trac Source-Version: 0.10.1-1 We believe that the bug you reported is fixed in the latest version of trac, which is due to be installed in the Debian FTP archive: trac_0.10.1-1.diff.gz to pool/main/t/trac/trac_0.10.1-1.diff.gz trac_0.10.1-1.dsc to pool/main/t/trac/trac_0.10.1-1.dsc trac_0.10.1-1_all.deb to pool/main/t/trac/trac_0.10.1-1_all.deb trac_0.10.1.orig.tar.gz to pool/main/t/trac/trac_0.10.1.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jesus Climent [EMAIL PROTECTED] (supplier of updated trac package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 9 Nov 2006 11:53:53 +0200 Source: trac Binary: trac Architecture: source all Version: 0.10.1-1 Distribution: unstable Urgency: high Maintainer: Jesus Climent [EMAIL PROTECTED] Changed-By: Jesus Climent [EMAIL PROTECTED] Description: trac - Enhanced wiki and issue tracking system for software development Closes: 397683 397725 Changes: trac (0.10.1-1) unstable; urgency=high . * New Upstream Release (Closes: #397683) * Depend on python-psycopg2 (Closes: #397725) * Security fix, hence urgency=high. No DSA or CVS available yet. * Upstream changes (most important ones): - fixed CSRF vulnerability - better database handling - only TICKET_ADMIN can assign a passed milestone to a ticket - failed to upload attachments - more (comprehensive list can be found at http://trac.edgewall.org/query?status=closedmilestone=0.10.1) Files: fb668f2aaf4d87edda38e9ebd39df3fa 706 web optional trac_0.10.1-1.dsc 55e10547c92cf39d64ab7ae4040c238d 439941 web optional trac_0.10.1.orig.tar.gz 2a7e1d9396e161c958cc8192f43c1704 7783 web optional trac_0.10.1-1.diff.gz 8f575b632aad2b9cfbabe3d7a41b1016 382038 web optional trac_0.10.1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFUwiRZvwdf4aUbWkRAkPSAKDFmAReUtN2gpM/WB2UcY9j/HmhOwCfTqzg CWGhNR242YvxkOqkBnn6Nv4= =HC1L -END PGP SIGNATURE- ---End Message---
Bug#393451: linux-image-2.6.17-2-xen-k7: similar problems here - versions from unstable are fine
Package: linux-image-2.6.17-2-xen-k7 Followup-For: Bug #393451 Yesterday, when upgrading an old xen installation to testing, I saw similar kernel panics. I didn't take screen shots, so I can't tell if it was really the same bug, bug it also panicked during startup of the domUs. I solved the problem by installing linux-image-2.6.18-1-xen-k7 and xen-hypervisor-3.0.3-1-i386 (and xen-utils-3.0.3-1) from unstable, which didn't cause any panik by now. Jan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397768: ieee80211: build-depends on the wrong version of the kernel
Package: ieee80211 Version: 1.1.14-1 Severity: serious Daniel, ieee80211 build-depends on linux-headers-2.6.17-2-all, but the current kernel version in unstable now is 2.6.18-2. Since etch will ship with 2.6.18, this package needs to be updated for the new kernel in order to be included in the release. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397771: sasl2-bin: authentication failure upon upgrade
Package: sasl2-bin Version: 2.1.22-1 Severity: critical Justification: breaks the whole system Upon upgrading my sasl2-bin, none of my user able to send email via postfix-tls. I tried below action and these are the outcome mail:~# ps waux | grep saslauthd root 24048 0.0 0.1 7140 2440 ?Ss 18:18 0:00 /usr/sbin/saslauthd -a pam -c -O -n 5 root 24053 0.0 0.1 7264 2636 ?S18:18 0:00 /usr/sbin/saslauthd -a pam -c -O -n 5 root 24054 0.0 0.1 7140 2448 ?S18:18 0:00 /usr/sbin/saslauthd -a pam -c -O -n 5 root 24055 0.0 0.1 7140 2440 ?S18:18 0:00 /usr/sbin/saslauthd -a pam -c -O -n 5 root 24056 0.0 0.1 7140 2440 ?S18:18 0:00 /usr/sbin/saslauthd -a pam -c -O -n 5 root 25347 0.0 0.0 1872 624 pts/1R+ 19:32 0:00 grep saslauthd mail:/var/run/saslauthd# perl -MMIME::Base64 -e 'print encode_base64(foobar\0foobar\0foobar);' ZGhpcwBkaGlzAGF6c2I= mail:/var/run/saslauthd# telnet localhost 25 Trying 127.0.0.1... Connected to localhost.localdomain. Escape character is '^]'. 220 mail.foobar.com ESMTP Postfix (AZRB) EHLO mail.foobar.com 250-mail.foobar.com 250-PIPELINING 250-SIZE 250-ETRN 250-STARTTLS 250-AUTH NTLM LOGIN PLAIN DIGEST-MD5 CRAM-MD5 250-AUTH=NTLM LOGIN PLAIN DIGEST-MD5 CRAM-MD5 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN AUTH PLAIN ZGhpcwBkaGlzAGF6c2I= 535 5.7.0 Error: authentication failed: authentication failure quit 221 2.0.0 Bye Connection closed by foreign host. mail:/var/run/saslauthd# testsaslauthd -u foobar -p foobar 0: OK Success. mail:/var/run/saslauthd# -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: i386 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-11-em64t-p4 Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Versions of packages sasl2-bin depends on: ii libc62.3.6.ds1-8 GNU C Library: Shared libraries ii libcomer 1.39+1.40-WIP-2006.10.02+dfsg-2 common error description library ii libdb4.2 4.2.52+dfsg-1 Berkeley v4.2 Database Libraries [ ii libkrb53 1.4.4-4 MIT Kerberos runtime libraries ii libldap2 2.1.30-13.2 OpenLDAP libraries ii libpam0g 0.79-4 Pluggable Authentication Modules l ii libsasl2 2.1.22-1Authentication abstraction library ii libssl0. 0.9.8c-3SSL shared libraries ii lsb-base 3.1-19 Linux Standard Base 3.1 init scrip sasl2-bin recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: unmerging 397659, reassign 397659 to jspwiki ..., severity of 397659 is serious
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.22 unmerge 397659 Bug#397659: Moving a package from contrib to main in a non-orig-source upload doesn't move the orig.tar.gz Bug#391193: orig.tar.gz not in pool/main for jspwiki 2.2.33 Disconnected #397659 from all other report(s). reassign 397659 jspwiki Bug#397659: Moving a package from contrib to main in a non-orig-source upload doesn't move the orig.tar.gz Bug reassigned from package `ftp.debian.org' to `jspwiki'. retitle 397659 jspwiki: FTBFS: source code not available Bug#397659: Moving a package from contrib to main in a non-orig-source upload doesn't move the orig.tar.gz Changed Bug title. severity 397659 serious Bug#397659: jspwiki: FTBFS: source code not available Severity set to `serious' from `normal' End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397766: Under AMD64 plaform, libdts-dev should be compiled with -fPIC option
severity 397766 wishlist thanks On Thu, Nov 09, 2006 at 12:04:36PM +0100, Jean-Michel Pouré wrote: Package: libdts-dev Version: 0.0.2-svn-1 Severity: grave When compiling ffmpeg under Debian AMD64, the compiler complains about libdts-dev headers. gcc -shared -Wl,-soname,libavcodec.so.51 -Wl,--warn-common -pthread -rdynamic -export-dynamic -Wl,--as-needed -Wl,-rpath-link,/home/jmpoure/logiciels/ffmpeg/ffmpeg/libavcodec -Wl,-rpath-link,/home/jmpoure/logiciels/ffmpeg/ffmpeg/libavformat -Wl,-rpath-link,/home/jmpoure/logiciels/ffmpeg/ffmpeg/libavutil -o libavcodec.so.51 bitstream.o utils.o allcodecs.o mpegvideo.o jrevdct.o jfdctfst.o jfdctint.o mjpeg.o resample.o resample2.o dsputil.o motion_est.o imgconvert.o mpeg12.o mpegaudiodec.o simple_idct.o ratecontrol.o eval.o error_resilience.o fft.o mdct.o raw.o golomb.o cabac.o faandct.o parser.o vp3dsp.o h264idct.o rangecoder.o pnm.o h263.o msmpeg4.o h263dec.o opt.o bitstream_filter.o audioconvert.o imgresample.o i386/fdct_mmx.o i386/cputest.o i386/dsputil_mmx.o i386/mpegvideo_mmx.o i386/motion_est_mmx.o i386/simple_idct_mmx.o i386/idct_mmx_xvid.o i386/fft_sse.o i386/vp3dsp_mmx.o i386/vp3dsp_sse2.o i386/fft_3dn.o i386/fft_3dn2.o i386/snowdsp_mmx.o i386/idct_mmx.o i386/cavsdsp_mmx.o aasc.o ac3enc.o alac.o asv1.o avs.o bmp.o cavs.o cavsdsp.o cinepak.o cljr.o cook.o cscd.o lzo.o cyuv.o dsicinav.o dvbsubdec.o dvbsub.o dvdsubdec.o dvdsubenc.o dv.o 8bps.o ffv1.o huffyuv.o flac.o flacenc.o flashsv.o flicvideo.o 4xm.o fraps.o gifdec.o lzw.o gif.o h261.o h264.o idcinvideo.o imc.o indeo2.o indeo3.o interplayvideo.o dpcm.o kmvc.o loco.o mace.o mmvideo.o mpegaudio.o msrle.o msvideo1.o lcl.o nuv.o rtjpeg.o png.o qdm2.o qdrw.o qpeg.o qtrle.o ra144.o ra288.o roqvideo.o rpza.o rv10.o shorten.o smacker.o smc.o snow.o sonic.o svq1.o targa.o vp3.o tiertexseqv.o tiff.o truemotion1.o truemotion2.o truespeech.o tscc.o tta.o ulti.o vc1.o vc1dsp.o vcr1.o vmdav.o vmnc.o vorbis.o vorbis_data.o vorbis_enc.o vp5.o vp56.o vp56data.o vp6.o vqavideo.o wavpack.o wmadec.o wnv1.o ws-snd1.o xan.o xl.o zmbv.o pcm.o adpcm.o adx.o g726.o faad.o faac.o xvidff.o xvid_rc.o x264.o mp3lameaudio.o oggvorbis.o libgsm.o a52dec.o liba52/bit_allocate.o liba52/bitstream.o liba52/downmix.o liba52/imdct.o liba52/parse.o liba52/crc.o liba52/resample.o dtsdec.o pthread.o -L/home/jmpoure/logiciels/ffmpeg/ffmpeg/libavutil -lavutil -lm -lz -ldts -lm -lgsm -lmp3lame -lm -lvorbis -lvorbisenc -logg -logg -lxvidcore -lx264 -lfaac -lfaad -ldl /usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/4.1.2/../../../../lib64/libdts.a(parse.o): relocation R_X86_64_32S against `a local symbol' can not be used when making a shared object; recompile with -fPIC /usr/lib/gcc/x86_64-linux-gnu/4.1.2/../../../../lib64/libdts.a: ne peut lire les symboles: Mauvaise valeur collect2: ld a retourné 1 code d'état d'exécution Under AMD64 plaform, libdts-dev should be compiled with -fPIC option. libdts-dev contains a static library; static libraries are not required to be built with -fPIC. The Debian package of ffmpeg does not have this problem, because it also doesn't build a shared library for libavcodec. The libdts-dev package is not unusable, it's just not usable for the purpose you want to put it to, which is not RC. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/
Processed: Re: Bug#397766: Under AMD64 plaform, libdts-dev should be compiled with -fPIC option
Processing commands for [EMAIL PROTECTED]: severity 397766 wishlist Bug#397766: Under AMD64 plaform, libdts-dev should be compiled with -fPIC option Severity set to `wishlist' from `grave' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#368560: mesa: material under SGI Free Software License B is not DFSG-free
tags 368560 etch-ignore thanks I'm granting an etch-ignore tag for this bug because I understand that there is work in progress to persuade the copyright holder to free the code in question, so we should conceivably see a change in the licensing during the lifetime of etch. (Of course, removing mesa from the distribution would completely not be an option anyway, so the only other choice would have been to delay the release and wait for someone to reimplement this code...) Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397478: sdd: FTBFS: /bin/sh: incs/x86_64-linux-cc/Inull: No such file or directory
Daniel Baumann [EMAIL PROTECTED] wrote: the attached patch adds the needed rules to build succesfully on amd64. However, I took it from sfind which ships a more updated rules-set. Unfortunately, it is licensed under CDDL only, and sdd is GPL only, hence the patch is incompatible. Don't be afraid: The program 'sdd' and The Schily Makefile system are independent projects (GPL speech: works). As the GPL is an OSI aproved license, it must not contaminate other projects like The Schily Makefile system, so there is no problem with taking a recent makefilesystem and combine it with an old sdd. Note that your problem would not be present if you did use smake to compile as smake includes auto make features that allow compilation on previously unknown platforms. Joerg, could you please release an updated version of sdd (if GPL or CDDL doesn't matter)? I am currently worting in a fix for a star bug that has a higher priority. I'll see what I can do. Jörg -- EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin [EMAIL PROTECTED](uni) [EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/ URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
Processed: Re: mesa: material under SGI Free Software License B is not DFSG-free
Processing commands for [EMAIL PROTECTED]: tags 368560 etch-ignore Bug#368560: mesa: material under SGI Free Software License B is not DFSG-free Tags were: sarge-ignore upstream Tags added: etch-ignore thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397768: ieee80211: build-depends on the wrong version of the kernel
On Thu, Nov 09, 2006 at 03:14:09AM -0800, Steve Langasek wrote: ieee80211 build-depends on linux-headers-2.6.17-2-all, but the current kernel version in unstable now is 2.6.18-2. Since etch will ship with 2.6.18, this package needs to be updated for the new kernel in order to be included in the release. After checking with the kernel maintainers, it appears that ieee80211, ipw2100, and ipw2200 all have up-to-date versions shipped with the 2.6.18 kernel. I'm going to go ahead and assume there are no other reasons why these three packages need to ship with etch, then, and tag them for removal from testing. Thanks, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397478: sdd: FTBFS: /bin/sh: incs/x86_64-linux-cc/Inull: No such file or directory
Joerg Schilling wrote: The program 'sdd' and The Schily Makefile system are independent projects (GPL speech: works). As the GPL is an OSI aproved license, it must not contaminate other projects like The Schily Makefile system, so there is no problem with taking a recent makefilesystem and combine it with an old sdd. As you know, this is not possible in Debian. Note that your problem would not be present if you did use smake to compile as smake includes auto make features that allow compilation on previously unknown platforms. It seems, that we'd like to get rid of smake, hence I did intentionally not using it. I am currently worting in a fix for a star bug that has a higher priority. I'll see what I can do. Ok. As a workaround, I just placed the symlinks to the old i586 rules, so no license problems because no new code is imported. However, updated smake rules in sdd would be nice to see at a later point. Thanks, Daniel -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: Re: changes with postfix -- sasl2-bin ?
Processing commands for [EMAIL PROTECTED]: tags 397771 + patch Bug#397771: sasl2-bin: authentication failure upon upgrade There were no tags set. Tags added: patch severity 397771 important Bug#397771: sasl2-bin: authentication failure upon upgrade Severity set to `important' from `critical' reassign 397771 postfix Bug#397771: sasl2-bin: authentication failure upon upgrade Bug reassigned from package `sasl2-bin' to `postfix'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#392028: marked as done (redhat-cluster: Package unuseable without built tree)
Your message dated Thu, 09 Nov 2006 04:02:14 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#392028: fixed in redhat-cluster 1.03.00-1 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: redhat-cluster Version: 1.02.00-8 Severity: grave Justification: renders package unusable The ccs-binaries built with this package search the required magma-plugins in the original built directory. The binary packages are unuseable because of this problem. If the built directory is removed after building from source package, the package stops working. This bus ist identical to #381434 and #374541 and renders the package unuseable in production envirements. -- System Information: Debian Release: Sid Architecture: amd64 Kernel: Linux 2.6.18-1-xen-amd64 Locale: LANG=C, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) ---End Message--- ---BeginMessage--- Source: redhat-cluster Source-Version: 1.03.00-1 We believe that the bug you reported is fixed in the latest version of redhat-cluster, which is due to be installed in the Debian FTP archive: ccs_1.03.00-1_s390.deb to pool/main/r/redhat-cluster/ccs_1.03.00-1_s390.deb cman_1.03.00-1_s390.deb to pool/main/r/redhat-cluster/cman_1.03.00-1_s390.deb fence_1.03.00-1_s390.deb to pool/main/r/redhat-cluster/fence_1.03.00-1_s390.deb gfs-tools_1.03.00-1_s390.deb to pool/main/r/redhat-cluster/gfs-tools_1.03.00-1_s390.deb gnbd-client_1.03.00-1_s390.deb to pool/main/r/redhat-cluster/gnbd-client_1.03.00-1_s390.deb gnbd-server_1.03.00-1_s390.deb to pool/main/r/redhat-cluster/gnbd-server_1.03.00-1_s390.deb gulm_1.03.00-1_s390.deb to pool/main/r/redhat-cluster/gulm_1.03.00-1_s390.deb libccs-dev_1.03.00-1_s390.deb to pool/main/r/redhat-cluster/libccs-dev_1.03.00-1_s390.deb libcman-dev_1.03.00-1_s390.deb to pool/main/r/redhat-cluster/libcman-dev_1.03.00-1_s390.deb libcman1_1.03.00-1_s390.deb to pool/main/r/redhat-cluster/libcman1_1.03.00-1_s390.deb libdlm-dev_1.03.00-1_s390.deb to pool/main/r/redhat-cluster/libdlm-dev_1.03.00-1_s390.deb libdlm1_1.03.00-1_s390.deb to pool/main/r/redhat-cluster/libdlm1_1.03.00-1_s390.deb libgulm-dev_1.03.00-1_s390.deb to pool/main/r/redhat-cluster/libgulm-dev_1.03.00-1_s390.deb libgulm1_1.03.00-1_s390.deb to pool/main/r/redhat-cluster/libgulm1_1.03.00-1_s390.deb libiddev-dev_1.03.00-1_s390.deb to pool/main/r/redhat-cluster/libiddev-dev_1.03.00-1_s390.deb libmagma-dev_1.03.00-1_s390.deb to pool/main/r/redhat-cluster/libmagma-dev_1.03.00-1_s390.deb libmagma1_1.03.00-1_s390.deb to pool/main/r/redhat-cluster/libmagma1_1.03.00-1_s390.deb magma-plugin-gulm_1.03.00-1_s390.deb to pool/main/r/redhat-cluster/magma-plugin-gulm_1.03.00-1_s390.deb magma-plugin-sm_1.03.00-1_s390.deb to pool/main/r/redhat-cluster/magma-plugin-sm_1.03.00-1_s390.deb redhat-cluster-source_1.03.00-1_all.deb to pool/main/r/redhat-cluster/redhat-cluster-source_1.03.00-1_all.deb redhat-cluster_1.03.00-1.diff.gz to pool/main/r/redhat-cluster/redhat-cluster_1.03.00-1.diff.gz redhat-cluster_1.03.00-1.dsc to pool/main/r/redhat-cluster/redhat-cluster_1.03.00-1.dsc redhat-cluster_1.03.00.orig.tar.gz to pool/main/r/redhat-cluster/redhat-cluster_1.03.00.orig.tar.gz A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bastian Blank [EMAIL PROTECTED] (supplier of updated redhat-cluster package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 9 Nov 2006 12:39:42 +0100 Source: redhat-cluster Binary: libmagma-dev libcman-dev ccs gnbd-server libdlm1 libiddev-dev fence magma-plugin-sm libcman1 magma-plugin-gulm cman gulm redhat-cluster-source libgulm-dev gfs-tools libgulm1 gnbd-client libmagma1 libdlm-dev libccs-dev Architecture: source s390 all Version: 1.03.00-1 Distribution: unstable Urgency: low Maintainer: Bastian Blank [EMAIL PROTECTED] Changed-By: Bastian Blank [EMAIL PROTECTED] Description: ccs- Cluster configuration system cman - Cluster manager fence - I/O fencing system gfs-tools - Global File System - management tools gnbd-client - Global network block device - client tools
Bug#397759: fails to configure: mv: cannot stat `/etc/chrony/chrony.keys.1.21-2': No such file or directory
Hi Lionel, On Thu, Nov 09, 2006 at 10:49:53AM +0100, Lionel Elie Mamane wrote: This code: if dpkg --compare-versions $2 lt-nl 1.21-3 ; then mv /etc/chrony/chrony.keys.$2 /etc/chrony/chrony.keys mv /etc/chrony/chrony.conf.$2 /etc/chrony/chrony.conf fi in the postinst makes the postinst not idempotent, and makes my chrony fail to configure: Idempotency is not a release-critical requirement per se. Can you comment on why this code failed for you at all? Did the postinst script in fact run twice, and fail with a *different* problem the first time through? Or did it fail because these files are missing from your system for some other reason? The only lines after this in the postinst are: ucf --sum-file /usr/share/chrony/chrony.conf.md5sum /etc/chrony/chrony.conf.new /etc/chrony/chrony.conf rm /etc/chrony/chrony.conf.new invoke-rc.d chrony start Idempotency is only an issue if one of these lines fails, since otherwise the postinst will complete successfully the first time and never again be called with the same arguments. Thus I think identifying the underlying failure on your system is at least as important as making the mv commands more robust. Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397768: ieee80211: build-depends on the wrong version of the kernel
Steve Langasek wrote: After checking with the kernel maintainers, it appears that ieee80211, ipw2100, and ipw2200 all have up-to-date versions shipped with the 2.6.18 kernel. I'm going to go ahead and assume there are no other reasons why these three packages need to ship with etch, then, and tag them for removal from testing. No, this was discussed with aba and he before. Additionally, ieee80211 is needed for ipw2945. Thanks for not doing it, Daniel -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: [EMAIL PROTECTED] Internet: http://people.panthera-systems.net/~daniel-baumann/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397768: ieee80211: build-depends on the wrong version of the kernel
On Thu, Nov 09, 2006 at 01:24:10PM +0100, Daniel Baumann wrote: Steve Langasek wrote: After checking with the kernel maintainers, it appears that ieee80211, ipw2100, and ipw2200 all have up-to-date versions shipped with the 2.6.18 kernel. I'm going to go ahead and assume there are no other reasons why these three packages need to ship with etch, then, and tag them for removal from testing. No, this was discussed with aba and he before. Additionally, ieee80211 is needed for ipw2945. ipw2945 is not in the archive. What does it need from ieee80211 that it couldn't get instead from the linux 2.6.18 packages? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397717: lmodern: install failed with error message warning: directory /usr/lib/X11/fonts/Type1 does not exist
as to this question:
It's possible that you have refused to accept the new version of this
file, and therefore updmap still wants to use lm.map.
I'm not sure at which point i would have refused to use a file. i have
no personally modified latex files outside my home dir so i would have
accepted any modifications to /etc files (most probably anyway).
here is the information you requested:
% sudo kpsewhich --format='web2c files' updmap.cfg
/var/lib/texmf/web2c/updmap.cfg
% ls /etc/texmf/updmap.d/10lmodern.cfg*
/etc/texmf/updmap.d/10lmodern.cfg
% grep lm.map /etc/texmf/updmap.d/*
/etc/texmf/updmap.d/10lmodern.cfg:Map cork-lm.map
/etc/texmf/updmap.d/10local.cfg:Map lm.map
/etc/texmf/updmap.d/10tetex-base.cfg:# files or the all-in-one file
lm.map, not both at the same time.
/etc/texmf/updmap.d/10tetex-base.cfg:## Map cork-lm.map
/etc/texmf/updmap.d/10tetex-base.cfg:## Map qx-lm.map
/etc/texmf/updmap.d/10tetex-base.cfg:## Map texnansi-lm.map
/etc/texmf/updmap.d/10tetex-base.cfg:## Map ts1-lm.map
/etc/texmf/updmap.d/10tetex-base.cfg:## Map lm.map
# # # # #
# contensts of /etc/texmf/updmap.d/10lmodern.cfg
# # # # #
# Don't delete the following pseudo-comment unless you know what you are doing.
# -_- DebPkgProvidedMaps -_-
# This file will *not* be included in updmap.cfg if the lmodern package is
# removed. Please read update-updmap(1) for details.
#
# This file is part of the set of files used to (indirectly) generate the
# final map files such as psfonts_{t1,pk}.map, {pdftex,dvipdfm}_{,n}dl14.map,
# ps2pk.map, builtin35.map and download35.map under /var/lib/texmf/fonts/map/
# (with psfonts.map being a symbolic link to one of psfonts_{t1,pk}.map,
# pdftex.map a symbolic link to one of pdftex_{,n}dl14.map and dvipdfm.map a
# symbolic link to one of dvipdfm_{,n}dl14.map, the choice depending on your
# updmap configuration, which you can customize by altering the files in
# /etc/texmf/updmap.d/ and running update-updmap).
#
# You should *not* modify the aforementioned final map files under
# /var/lib/texmf/fonts/map/ directly, for they are automatically generated by
# updmap-sys(1). Instead, you should read update-updmap(1), updmap-sys(1) and
# if you actually need to make changes to the aforementioned final map files,
# you should make the changes in /etc/texmf/updmap.d/, use update-updmap to
# regenerate /var/lib/texmf/web2c/updmap.cfg and finally updmap-sys to
# regenerate the final map files.
#
# Reading /etc/texmf/updmap.d/00updmap.cfg can also help understand how all
# this works.
#
#
# Declare the basic Latin Modern map files for use by the updmap-sys(1)
# machinery.
Map lm-ec.map
Map lm-el.map
Map lm-math.map
Map lm-qx.map
Map lm-rm.map
Map lm-t5.map
Map lm-texnansi.map
Map lm-ts1.map
#
# This map file is for compatibility with old DVI files.
Map cork-lm.map
--
==
$mysig = EOS;
the old lighter in the gun in the rabbit trick. (kfg)
daniël bosold
[EMAIL PROTECTED]
[EMAIL PROTECTED]
http://www.bosold.net
aim: cyclist38
icq: cyfacKid
EOS
Bug#397216: libastro-fits-cfitsio-perl: FTBFS: wrong byteswap on mipsel and arm
* Niko Tyni [EMAIL PROTECTED] [2006-11-08 15:03]: I'm Ccing the #339758 submitter, Rafael Laboissiere [EMAIL PROTECTED]. Hope this is OK with him. No problem. Thanks for your thorough investigation on the problem. -- Rafael -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397605: marked as done (cyrus-sasl2: FTBFS on hppa (PIC linking issue))
Your message dated Thu, 09 Nov 2006 04:32:16 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#397603: fixed in cyrus-sasl2 2.1.22.dfsg1-1 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: cyrus-sasl2 Version: 2.1.22-1 Severity: serious cyrus-sasl2 fails to build from source on hppa: --8-- Making all in plugins make[3]: Entering directory `/build/buildd/cyrus-sasl2-2.1.22/plugins' /bin/sh ../libtool --tag=CC --mode=link hppa-linux-gnu-gcc -Wall -W -Wall -g -O2 -Wl,-z,defs -module -export-dynamic -rpath /usr/lib/sasl2 -o libsasldb.la -version-info 2:22:0 sasldb.lo sasldb_init.lo plugin_common.lo ../sasldb/libsasldb.la -ldb-4.2 -lresolv -lresolv hppa-linux-gnu-gcc -shared .libs/sasldb.o .libs/sasldb_init.o .libs/plugin_common.o -Wl,--whole-archive ../sasldb/.libs/libsasldb.a -Wl,--no-whole-archive /usr/lib/libdb-4.2.so -lresolv -Wl,-z -Wl,defs -Wl,-soname -Wl,libsasldb.so.2 -o .libs/libsasldb.so.2.0.22 /usr/bin/ld: ../sasldb/.libs/libsasldb.a(db_berkeley.o): relocation R_PARISC_DPREL21L can not be used when making a shared object; recompile with -fPIC ../sasldb/.libs/libsasldb.a(db_berkeley.o): could not read symbols: Bad value collect2: ld returned 1 exit status make[3]: *** [libsasldb.la] Error 1 make[3]: Leaving directory `/build/buildd/cyrus-sasl2-2.1.22/plugins' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/build/buildd/cyrus-sasl2-2.1.22' make[1]: *** [all] Error 2 make[1]: Leaving directory `/build/buildd/cyrus-sasl2-2.1.22' make: *** [build-arch-stamp] Error 2 ** Build finished at 20061107-1558 FAILED [dpkg-buildpackage died] --8-- http://buildd.debian.org/fetch.cgi?pkg=cyrus-sasl2;ver=2.1.22-1;arch=hppa;stamp=1162940348 The cause is apparently that autotools creates non-PIC static libraries which are then used to create a PIC shared library, which doesn't work on hppa. ---End Message--- ---BeginMessage--- Source: cyrus-sasl2 Source-Version: 2.1.22.dfsg1-1 We believe that the bug you reported is fixed in the latest version of cyrus-sasl2, which is due to be installed in the Debian FTP archive: cyrus-sasl2-doc_2.1.22.dfsg1-1_all.deb to pool/main/c/cyrus-sasl2/cyrus-sasl2-doc_2.1.22.dfsg1-1_all.deb cyrus-sasl2_2.1.22.dfsg1-1.diff.gz to pool/main/c/cyrus-sasl2/cyrus-sasl2_2.1.22.dfsg1-1.diff.gz cyrus-sasl2_2.1.22.dfsg1-1.dsc to pool/main/c/cyrus-sasl2/cyrus-sasl2_2.1.22.dfsg1-1.dsc cyrus-sasl2_2.1.22.dfsg1.orig.tar.gz to pool/main/c/cyrus-sasl2/cyrus-sasl2_2.1.22.dfsg1.orig.tar.gz libsasl2-2-dev_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-2-dev_2.1.22.dfsg1-1_i386.deb libsasl2-2_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-2_2.1.22.dfsg1-1_i386.deb libsasl2-dev_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-dev_2.1.22.dfsg1-1_i386.deb libsasl2-modules-gssapi-heimdal_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules-gssapi-heimdal_2.1.22.dfsg1-1_i386.deb libsasl2-modules-gssapi-mit_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules-gssapi-mit_2.1.22.dfsg1-1_i386.deb libsasl2-modules-ldap_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules-ldap_2.1.22.dfsg1-1_i386.deb libsasl2-modules-otp_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules-otp_2.1.22.dfsg1-1_i386.deb libsasl2-modules-sql_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules-sql_2.1.22.dfsg1-1_i386.deb libsasl2-modules_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules_2.1.22.dfsg1-1_i386.deb libsasl2_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2_2.1.22.dfsg1-1_i386.deb sasl2-bin_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/sasl2-bin_2.1.22.dfsg1-1_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabian Fagerholm [EMAIL PROTECTED] (supplier of updated cyrus-sasl2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 9 Nov 2006 14:12:40 +0200 Source: cyrus-sasl2 Binary:
Bug#397759: fails to configure: mv: cannot stat `/etc/chrony/chrony.keys.1.21-2': No such file or directory
On Thu, Nov 09, 2006 at 04:14:43AM -0800, Steve Langasek wrote:
On Thu, Nov 09, 2006 at 10:49:53AM +0100, Lionel Elie Mamane wrote:
This code:
if dpkg --compare-versions $2 lt-nl 1.21-3 ; then
mv /etc/chrony/chrony.keys.$2 /etc/chrony/chrony.keys
mv /etc/chrony/chrony.conf.$2 /etc/chrony/chrony.conf
fi
in the postinst makes the postinst not idempotent, and makes my chrony
fail to configure:
Idempotency is not a release-critical requirement per se.
OK.
Can you comment on why this code failed for you at all?
I'm not sure. The code assumes that when upgrading from version
earlier than 1.21-3, you *must* have a
/etc/chrony/chrony.keys.${OLD_VERSION} file. I've never noticed any
file with that name on my systems from woody times up to now, but I
may just not have seen them. Maybe these are files that an older
version *may* have left behind but does not necessarily leave behind?
Which would give a different reason than idem-potency for this to be a
bug.
I actually doubt that *all* past versions left such files, but maybe
all since sarge and maintainer made a conscious decision not to
support earlier-than-sarge upgrades (which we don't support in
general).
Did the postinst script in fact run twice, and fail with a
*different* problem the first time through?
I don't know. I didn't touch that machine in some weeks, and now
aptitude told me:
dpkg was interrupted, please run dpkg --configure -a
I did that, many packages got configured, and configuration of chrony
failed. Maybe I had left an earlier upgrade session in a screen
session, forgot about it and then rebooted the machine at a later
time, interrupting dpkg brutally. Or I had an upgrade session in a SSH
session which died, which SIGHUP-killed the running dpkg. Yes, that
looks like a plausible scenario.
The only lines after this in the postinst are:
ucf --sum-file /usr/share/chrony/chrony.conf.md5sum
/etc/chrony/chrony.conf.new /etc/chrony/chrony.conf
Complementing the above scenario, it is plausible that dpkg/ucf would
have been interrupted when ucf was waiting for my input (changes in
config files, what shall be done? package version / your version /
merge / show differences / ...). On non-critical and slow machines
(such as this one), I often start an upgrade, leave it running and
come back a few hours/days later to find dpkg/ucf/debconf waiting for
my input.
In this scenario, the root cause of the failure is indeed the lack of
idem-potency in itself.
rm /etc/chrony/chrony.conf.new
invoke-rc.d chrony start
Idempotency is only an issue if one of these lines fails, since
otherwise the postinst will complete successfully the first time and
never again be called with the same arguments. Thus I think
identifying the underlying failure on your system is at least as
important as making the mv commands more robust.
I replaced the lines as in my suggestion, reran dpkg --configure
--pending, and configuration succeeded, with ucf asking me a
question, which is compatible with above scenario, but also with the
files not existing in the first place.
--
Lionel
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397605: marked as done (cyrus-sasl2: FTBFS on hppa (PIC linking issue))
Your message dated Thu, 09 Nov 2006 04:32:16 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#397605: fixed in cyrus-sasl2 2.1.22.dfsg1-1 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: cyrus-sasl2 Version: 2.1.22-1 Severity: serious cyrus-sasl2 fails to build from source on hppa: --8-- Making all in plugins make[3]: Entering directory `/build/buildd/cyrus-sasl2-2.1.22/plugins' /bin/sh ../libtool --tag=CC --mode=link hppa-linux-gnu-gcc -Wall -W -Wall -g -O2 -Wl,-z,defs -module -export-dynamic -rpath /usr/lib/sasl2 -o libsasldb.la -version-info 2:22:0 sasldb.lo sasldb_init.lo plugin_common.lo ../sasldb/libsasldb.la -ldb-4.2 -lresolv -lresolv hppa-linux-gnu-gcc -shared .libs/sasldb.o .libs/sasldb_init.o .libs/plugin_common.o -Wl,--whole-archive ../sasldb/.libs/libsasldb.a -Wl,--no-whole-archive /usr/lib/libdb-4.2.so -lresolv -Wl,-z -Wl,defs -Wl,-soname -Wl,libsasldb.so.2 -o .libs/libsasldb.so.2.0.22 /usr/bin/ld: ../sasldb/.libs/libsasldb.a(db_berkeley.o): relocation R_PARISC_DPREL21L can not be used when making a shared object; recompile with -fPIC ../sasldb/.libs/libsasldb.a(db_berkeley.o): could not read symbols: Bad value collect2: ld returned 1 exit status make[3]: *** [libsasldb.la] Error 1 make[3]: Leaving directory `/build/buildd/cyrus-sasl2-2.1.22/plugins' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/build/buildd/cyrus-sasl2-2.1.22' make[1]: *** [all] Error 2 make[1]: Leaving directory `/build/buildd/cyrus-sasl2-2.1.22' make: *** [build-arch-stamp] Error 2 ** Build finished at 20061107-1558 FAILED [dpkg-buildpackage died] --8-- http://buildd.debian.org/fetch.cgi?pkg=cyrus-sasl2;ver=2.1.22-1;arch=hppa;stamp=1162940348 The cause is apparently that autotools creates non-PIC static libraries which are then used to create a PIC shared library, which doesn't work on hppa. ---End Message--- ---BeginMessage--- Source: cyrus-sasl2 Source-Version: 2.1.22.dfsg1-1 We believe that the bug you reported is fixed in the latest version of cyrus-sasl2, which is due to be installed in the Debian FTP archive: cyrus-sasl2-doc_2.1.22.dfsg1-1_all.deb to pool/main/c/cyrus-sasl2/cyrus-sasl2-doc_2.1.22.dfsg1-1_all.deb cyrus-sasl2_2.1.22.dfsg1-1.diff.gz to pool/main/c/cyrus-sasl2/cyrus-sasl2_2.1.22.dfsg1-1.diff.gz cyrus-sasl2_2.1.22.dfsg1-1.dsc to pool/main/c/cyrus-sasl2/cyrus-sasl2_2.1.22.dfsg1-1.dsc cyrus-sasl2_2.1.22.dfsg1.orig.tar.gz to pool/main/c/cyrus-sasl2/cyrus-sasl2_2.1.22.dfsg1.orig.tar.gz libsasl2-2-dev_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-2-dev_2.1.22.dfsg1-1_i386.deb libsasl2-2_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-2_2.1.22.dfsg1-1_i386.deb libsasl2-dev_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-dev_2.1.22.dfsg1-1_i386.deb libsasl2-modules-gssapi-heimdal_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules-gssapi-heimdal_2.1.22.dfsg1-1_i386.deb libsasl2-modules-gssapi-mit_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules-gssapi-mit_2.1.22.dfsg1-1_i386.deb libsasl2-modules-ldap_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules-ldap_2.1.22.dfsg1-1_i386.deb libsasl2-modules-otp_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules-otp_2.1.22.dfsg1-1_i386.deb libsasl2-modules-sql_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules-sql_2.1.22.dfsg1-1_i386.deb libsasl2-modules_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules_2.1.22.dfsg1-1_i386.deb libsasl2_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2_2.1.22.dfsg1-1_i386.deb sasl2-bin_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/sasl2-bin_2.1.22.dfsg1-1_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabian Fagerholm [EMAIL PROTECTED] (supplier of updated cyrus-sasl2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 9 Nov 2006 14:12:40 +0200 Source: cyrus-sasl2 Binary:
Processed: Re: mips: system() hangs when compiled with -pg (gprof profiling(.
Processing commands for [EMAIL PROTECTED]: reassign 387498 linux-2.6 Bug#387498: mipsel: system() hangs when compiled with -pg (gprof profiling) Bug reassigned from package `linux-2.6,libc6' to `linux-2.6'. retitle 387498 [hppa/mipsel] system() hangs when compiled with -pg (gprof profiling) Bug#387498: mipsel: system() hangs when compiled with -pg (gprof profiling) Changed Bug title. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: tagging bugs that are closed by packages in NEW as pending
Processing commands for [EMAIL PROTECTED]: # the following bugs are closed by packages in NEW # tags 00 pending Bug number 00 not found. (Is it archived?) tags 391275 pending Bug#391275: linux-2.6: please add CONFIG_SX=m in the 686 kernel image There were no tags set. Tags added: pending tags 391342 pending Bug#391342: ITP: jsmath -- TeX equations in HTML documents There were no tags set. Tags added: pending tags 396462 pending Bug#396462: mplayer: please provide a default skin or gmplayer won't start There were no tags set. Tags added: pending tags 396849 pending Bug#396849: ITP: libauthen-simple-perl -- Simple and consistent framework for authentication There were no tags set. Tags added: pending tags 396927 pending Bug#396927: ITP: xyssl -- lightweight crypto and SSL/TLS library There were no tags set. Tags added: pending tags 397139 pending Bug#397139: ftbfs alpha + ia64 There were no tags set. Tags added: pending tags 397281 pending Bug#397281: BUG: [EMAIL PROTECTED]/irq/handle.c:177/__do_IRQ() Tags were: patch Warning: Unknown package 'linux-image-2.6.18-1-xen-vserver-686' Tags added: pending thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: reassign 389803 to linux-2.6, reassign 393451 to linux-2.6, forcibly merging 389803 393451
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.22 reassign 389803 linux-2.6 Bug#389803: linux-image-2.6.17-2-xen-686 - crashs with 4 guest domains Bug#391448: xen-hypervisor-3.0-unstable-1-i386: dom0 crashes when starting the 3rd domU Bug reassigned from package `linux-image-2.6.17-2-xen-686' to `linux-2.6'. reassign 393451 linux-2.6 Bug#393451: linux-image-2.6.17-2-xen-k7: Kernel panic - not syncing: Fatal exception in interrupt reboot Bug reassigned from package `linux-image-2.6.17-2-xen-k7' to `linux-2.6'. forcemerge 389803 393451 Bug#389803: linux-image-2.6.17-2-xen-686 - crashs with 4 guest domains Bug#393451: linux-image-2.6.17-2-xen-k7: Kernel panic - not syncing: Fatal exception in interrupt reboot Bug#391448: xen-hypervisor-3.0-unstable-1-i386: dom0 crashes when starting the 3rd domU Forcibly Merged 389803 391448 393451. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397478: marked as done (sdd: FTBFS: /bin/sh: incs/x86_64-linux-cc/Inull: No such file or directory)
Your message dated Thu, 09 Nov 2006 04:33:02 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#397478: fixed in sdd 1.52-6 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: sdd Version: 1.52-5 Severity: serious Hi, Your package is failing to build on amd64 with various errors it's not showing on other arches. This first line that seems to be really different is during clean is: p incs/x86_64-linux-cc make[1]: p: Command not found make[1]: [incs/x86_64-linux-cc/Inull] Error 127 (ignored) /bin/sh: incs/x86_64-linux-cc/Inull: No such file or directory make[1]: *** [incs/x86_64-linux-cc/Inull] Error 1 make[1]: Leaving directory `/build/buildd/sdd-1.52' make: [clean] Error 2 (ignored) Then during binary-arch it does about the same again: p incs/x86_64-linux-cc make[1]: p: Command not found make[1]: [incs/x86_64-linux-cc/Inull] Error 127 (ignored) /bin/sh: incs/x86_64-linux-cc/Inull: No such file or directory make[1]: *** [incs/x86_64-linux-cc/Inull] Error 1 make[1]: Leaving directory `/build/buildd/sdd-1.52' make: *** [install] Error 2 For some reason this is only affecting amd64, not sure why. Kurt ---End Message--- ---BeginMessage--- Source: sdd Source-Version: 1.52-6 We believe that the bug you reported is fixed in the latest version of sdd, which is due to be installed in the Debian FTP archive: sdd_1.52-6.diff.gz to pool/main/s/sdd/sdd_1.52-6.diff.gz sdd_1.52-6.dsc to pool/main/s/sdd/sdd_1.52-6.dsc sdd_1.52-6_amd64.deb to pool/main/s/sdd/sdd_1.52-6_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Baumann [EMAIL PROTECTED] (supplier of updated sdd package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 9 Nov 2006 13:10:00 +0100 Source: sdd Binary: sdd Architecture: source amd64 Version: 1.52-6 Distribution: unstable Urgency: low Maintainer: Daniel Baumann [EMAIL PROTECTED] Changed-By: Daniel Baumann [EMAIL PROTECTED] Description: sdd- File duplication and conversion tool, similar to 'dd' Closes: 397478 Changes: sdd (1.52-6) unstable; urgency=low . * Adding symlinks for amd64 to fixing outdated smake rules (Closes: #397478). Files: 06294a3fadca70104325edb676103868 549 utils optional sdd_1.52-6.dsc 5b7632d4121adc7a775a3f387e90d222 3654 utils optional sdd_1.52-6.diff.gz abe70c1c789eff8473068a2ebc3ece14 36808 utils optional sdd_1.52-6_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFUxts+C5cwEsrK54RAqPxAKCk6MPojyf/qIEgq7XTkMgJU4awHQCgoaLZ fRa/cDmmS2yh+0nw7yEctOY= =KHEb -END PGP SIGNATURE- ---End Message---
Bug#397603: marked as done (cyrus-sasl2: FTBFS on amd64 (PIC linking issue))
Your message dated Thu, 09 Nov 2006 04:32:16 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#397605: fixed in cyrus-sasl2 2.1.22.dfsg1-1 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: cyrus-sasl2 Version: 2.1.22-1 Severity: serious cyrus-sasl2 fails to build from source on amd64 because autotools generates non-PIC static libraries which are then used to create a PIC shared library. This works on i386 but not on amd64. A build log fragment [0]: --8-- Making all in plugins make[3]: Entering directory `/build/buildd/cyrus-sasl2-2.1.22/plugins' /bin/sh ../libtool --tag=CC --mode=link x86_64-linux-gnu-gcc -Wall -W -Wall -g -O2 -Wl,-z,defs -module -export-dynamic -rpath /usr/lib/sasl2 -o libsasldb.la -version-info 2:22:0 sasldb.lo sasldb_init.lo plugin_common.lo ../sasldb/libsasldb.la -ldb-4.2 -lresolv x86_64-linux-gnu-gcc -shared .libs/sasldb.o .libs/sasldb_init.o .libs/plugin_common.o -Wl,--whole-archive ../sasldb/.libs/libsasldb.a -Wl,--no-whole-archive /usr/lib/libdb-4.2.so -lresolv -Wl,-z -Wl,defs -Wl,-soname -Wl,libsasldb.so.2 -o .libs/libsasldb.so.2.0.22 /usr/bin/ld: ../sasldb/.libs/libsasldb.a(allockey.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC ../sasldb/.libs/libsasldb.a(allockey.o): could not read symbols: Bad value collect2: ld returned 1 exit status make[3]: *** [libsasldb.la] Error 1 make[3]: Leaving directory `/build/buildd/cyrus-sasl2-2.1.22/plugins' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/build/buildd/cyrus-sasl2-2.1.22' make[1]: *** [all] Error 2 make[1]: Leaving directory `/build/buildd/cyrus-sasl2-2.1.22' make: *** [build-arch-stamp] Error 2 ** Build finished at 20061108-0430 FAILED [dpkg-buildpackage died] --8-- [0] http://buildd.debian.org/fetch.cgi?pkg=cyrus-sasl2;ver=2.1.22-1;arch=amd64;stamp=1162960218 -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-1-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) ---End Message--- ---BeginMessage--- Source: cyrus-sasl2 Source-Version: 2.1.22.dfsg1-1 We believe that the bug you reported is fixed in the latest version of cyrus-sasl2, which is due to be installed in the Debian FTP archive: cyrus-sasl2-doc_2.1.22.dfsg1-1_all.deb to pool/main/c/cyrus-sasl2/cyrus-sasl2-doc_2.1.22.dfsg1-1_all.deb cyrus-sasl2_2.1.22.dfsg1-1.diff.gz to pool/main/c/cyrus-sasl2/cyrus-sasl2_2.1.22.dfsg1-1.diff.gz cyrus-sasl2_2.1.22.dfsg1-1.dsc to pool/main/c/cyrus-sasl2/cyrus-sasl2_2.1.22.dfsg1-1.dsc cyrus-sasl2_2.1.22.dfsg1.orig.tar.gz to pool/main/c/cyrus-sasl2/cyrus-sasl2_2.1.22.dfsg1.orig.tar.gz libsasl2-2-dev_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-2-dev_2.1.22.dfsg1-1_i386.deb libsasl2-2_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-2_2.1.22.dfsg1-1_i386.deb libsasl2-dev_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-dev_2.1.22.dfsg1-1_i386.deb libsasl2-modules-gssapi-heimdal_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules-gssapi-heimdal_2.1.22.dfsg1-1_i386.deb libsasl2-modules-gssapi-mit_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules-gssapi-mit_2.1.22.dfsg1-1_i386.deb libsasl2-modules-ldap_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules-ldap_2.1.22.dfsg1-1_i386.deb libsasl2-modules-otp_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules-otp_2.1.22.dfsg1-1_i386.deb libsasl2-modules-sql_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules-sql_2.1.22.dfsg1-1_i386.deb libsasl2-modules_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules_2.1.22.dfsg1-1_i386.deb libsasl2_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2_2.1.22.dfsg1-1_i386.deb sasl2-bin_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/sasl2-bin_2.1.22.dfsg1-1_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabian Fagerholm [EMAIL PROTECTED] (supplier of updated cyrus-sasl2 package) (This
Bug#397310: apache2: PAM authentication broke
Package: apache2 Version: 2.2.3-2 Followup-For: Bug #397310 PAM authenification worked before, pam config is untouched. Directory /data/htdocs/admin AuthPAM_Enabled on AuthType Basic AuthName admin require user xyz /Directory Fails now with: [Thu Nov 09 13:20:09 2006] [error] Internal error: pcfg_openfile() called with NULL filename [Thu Nov 09 13:20:09 2006] [error] [client 84.163.240.100] (9)Bad file descriptor: Could not open password file: (null) [Thu Nov 09 13:20:09 2006] [info] [client 84.163.240.100] Connection closed to child 0 with standard shutdown I already reenabled the authz_user module, but no success. Module dav_svn is also broken after the upgrade, but i didn't look into it. just disabled it for now. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-2-amd64-k8-smp Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages apache2 depends on: ii apache2-mpm-prefork 2.2.3-3Traditional model for Apache HTTPD apache2 recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397603: marked as done (cyrus-sasl2: FTBFS on amd64 (PIC linking issue))
Your message dated Thu, 09 Nov 2006 04:32:16 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#397603: fixed in cyrus-sasl2 2.1.22.dfsg1-1 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: cyrus-sasl2 Version: 2.1.22-1 Severity: serious cyrus-sasl2 fails to build from source on amd64 because autotools generates non-PIC static libraries which are then used to create a PIC shared library. This works on i386 but not on amd64. A build log fragment [0]: --8-- Making all in plugins make[3]: Entering directory `/build/buildd/cyrus-sasl2-2.1.22/plugins' /bin/sh ../libtool --tag=CC --mode=link x86_64-linux-gnu-gcc -Wall -W -Wall -g -O2 -Wl,-z,defs -module -export-dynamic -rpath /usr/lib/sasl2 -o libsasldb.la -version-info 2:22:0 sasldb.lo sasldb_init.lo plugin_common.lo ../sasldb/libsasldb.la -ldb-4.2 -lresolv x86_64-linux-gnu-gcc -shared .libs/sasldb.o .libs/sasldb_init.o .libs/plugin_common.o -Wl,--whole-archive ../sasldb/.libs/libsasldb.a -Wl,--no-whole-archive /usr/lib/libdb-4.2.so -lresolv -Wl,-z -Wl,defs -Wl,-soname -Wl,libsasldb.so.2 -o .libs/libsasldb.so.2.0.22 /usr/bin/ld: ../sasldb/.libs/libsasldb.a(allockey.o): relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC ../sasldb/.libs/libsasldb.a(allockey.o): could not read symbols: Bad value collect2: ld returned 1 exit status make[3]: *** [libsasldb.la] Error 1 make[3]: Leaving directory `/build/buildd/cyrus-sasl2-2.1.22/plugins' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/build/buildd/cyrus-sasl2-2.1.22' make[1]: *** [all] Error 2 make[1]: Leaving directory `/build/buildd/cyrus-sasl2-2.1.22' make: *** [build-arch-stamp] Error 2 ** Build finished at 20061108-0430 FAILED [dpkg-buildpackage died] --8-- [0] http://buildd.debian.org/fetch.cgi?pkg=cyrus-sasl2;ver=2.1.22-1;arch=amd64;stamp=1162960218 -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-1-686 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) ---End Message--- ---BeginMessage--- Source: cyrus-sasl2 Source-Version: 2.1.22.dfsg1-1 We believe that the bug you reported is fixed in the latest version of cyrus-sasl2, which is due to be installed in the Debian FTP archive: cyrus-sasl2-doc_2.1.22.dfsg1-1_all.deb to pool/main/c/cyrus-sasl2/cyrus-sasl2-doc_2.1.22.dfsg1-1_all.deb cyrus-sasl2_2.1.22.dfsg1-1.diff.gz to pool/main/c/cyrus-sasl2/cyrus-sasl2_2.1.22.dfsg1-1.diff.gz cyrus-sasl2_2.1.22.dfsg1-1.dsc to pool/main/c/cyrus-sasl2/cyrus-sasl2_2.1.22.dfsg1-1.dsc cyrus-sasl2_2.1.22.dfsg1.orig.tar.gz to pool/main/c/cyrus-sasl2/cyrus-sasl2_2.1.22.dfsg1.orig.tar.gz libsasl2-2-dev_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-2-dev_2.1.22.dfsg1-1_i386.deb libsasl2-2_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-2_2.1.22.dfsg1-1_i386.deb libsasl2-dev_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-dev_2.1.22.dfsg1-1_i386.deb libsasl2-modules-gssapi-heimdal_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules-gssapi-heimdal_2.1.22.dfsg1-1_i386.deb libsasl2-modules-gssapi-mit_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules-gssapi-mit_2.1.22.dfsg1-1_i386.deb libsasl2-modules-ldap_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules-ldap_2.1.22.dfsg1-1_i386.deb libsasl2-modules-otp_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules-otp_2.1.22.dfsg1-1_i386.deb libsasl2-modules-sql_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules-sql_2.1.22.dfsg1-1_i386.deb libsasl2-modules_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules_2.1.22.dfsg1-1_i386.deb libsasl2_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2_2.1.22.dfsg1-1_i386.deb sasl2-bin_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/sasl2-bin_2.1.22.dfsg1-1_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabian Fagerholm [EMAIL PROTECTED] (supplier of updated cyrus-sasl2 package) (This
Bug#365183: marked as done ([NONFREE-DOC] Package contains IETF RFC/I-D)
Your message dated Thu, 09 Nov 2006 04:32:16 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#365183: fixed in cyrus-sasl2 2.1.22.dfsg1-1 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: libsasl2 Severity: serious Hi! It seems your package contains non-free RFC/I-Ds: usr/share/doc/libsasl2/draft-ietf-sasl-anon-02.txt.gz libs/libsasl2 usr/share/doc/libsasl2/draft-ietf-sasl-crammd5-01.txt.gzlibs/libsasl2 usr/share/doc/libsasl2/draft-ietf-sasl-gssapi-00.txt.gz libs/libsasl2 usr/share/doc/libsasl2/draft-ietf-sasl-plain-03.txt.gz libs/libsasl2 usr/share/doc/libsasl2/draft-ietf-sasl-rfcbis-03.txt.gz libs/libsasl2 usr/share/doc/libsasl2/draft-ietf-sasl-rfc2831bis-02.txt.gz libs/libsasl2 usr/share/doc/libsasl2/draft-ietf-sasl-saslprep-04.txt.gz libs/libsasl2 The license on I-Ds is not DFSG-free, see: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=199810 http://release.debian.org/removing-non-free-documentation I believe the options are: 1) Remove the file from the package (which may include re-packaging the source code). 2) Move the files to a non-free package (which may also include re-packaging the source code). If you disagree with this, because this bug is reported for several packages at once, it seems better to discuss this on debian-legal, in this thread: http://thread.gmane.org/gmane.linux.debian.devel.legal/25993 The severity is serious, because this violates the Debian policy http://www.debian.org/doc/debian-policy/ch-archive.html#s-dfsg. I'm sorry if this report is filed in error, I went over many packages looking for suspicious filenames, and there may be false positives. Thanks, Simon ---End Message--- ---BeginMessage--- Source: cyrus-sasl2 Source-Version: 2.1.22.dfsg1-1 We believe that the bug you reported is fixed in the latest version of cyrus-sasl2, which is due to be installed in the Debian FTP archive: cyrus-sasl2-doc_2.1.22.dfsg1-1_all.deb to pool/main/c/cyrus-sasl2/cyrus-sasl2-doc_2.1.22.dfsg1-1_all.deb cyrus-sasl2_2.1.22.dfsg1-1.diff.gz to pool/main/c/cyrus-sasl2/cyrus-sasl2_2.1.22.dfsg1-1.diff.gz cyrus-sasl2_2.1.22.dfsg1-1.dsc to pool/main/c/cyrus-sasl2/cyrus-sasl2_2.1.22.dfsg1-1.dsc cyrus-sasl2_2.1.22.dfsg1.orig.tar.gz to pool/main/c/cyrus-sasl2/cyrus-sasl2_2.1.22.dfsg1.orig.tar.gz libsasl2-2-dev_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-2-dev_2.1.22.dfsg1-1_i386.deb libsasl2-2_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-2_2.1.22.dfsg1-1_i386.deb libsasl2-dev_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-dev_2.1.22.dfsg1-1_i386.deb libsasl2-modules-gssapi-heimdal_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules-gssapi-heimdal_2.1.22.dfsg1-1_i386.deb libsasl2-modules-gssapi-mit_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules-gssapi-mit_2.1.22.dfsg1-1_i386.deb libsasl2-modules-ldap_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules-ldap_2.1.22.dfsg1-1_i386.deb libsasl2-modules-otp_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules-otp_2.1.22.dfsg1-1_i386.deb libsasl2-modules-sql_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules-sql_2.1.22.dfsg1-1_i386.deb libsasl2-modules_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2-modules_2.1.22.dfsg1-1_i386.deb libsasl2_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/libsasl2_2.1.22.dfsg1-1_i386.deb sasl2-bin_2.1.22.dfsg1-1_i386.deb to pool/main/c/cyrus-sasl2/sasl2-bin_2.1.22.dfsg1-1_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabian Fagerholm [EMAIL PROTECTED] (supplier of updated cyrus-sasl2 package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 9 Nov 2006 14:12:40 +0200 Source: cyrus-sasl2 Binary: libsasl2-modules-ldap libsasl2-2 libsasl2 libsasl2-2-dev sasl2-bin cyrus-sasl2-doc libsasl2-dev libsasl2-modules-gssapi-heimdal libsasl2-modules-otp libsasl2-modules-sql libsasl2-modules libsasl2-modules-gssapi-mit Architecture: source i386 all
Processed: setting package to grub grub-disk grub-doc, tagging 394020, tagging 396315
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.24 package grub grub-disk grub-doc Ignoring bugs not assigned to: grub grub-doc grub-disk tags 394020 + pending Bug#394020: grub: /usr/sbin/grub-install missing Tags were: pending Bug#393450: /sbin/grub-install wants me to call non existing /usr/sbin/grub-install Tags added: pending tags 396315 + pending Bug#396315: 'man update-grub' typo: simliar Tags were: patch Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#396840: using pyversions in debian/rules is not reliable
I think this is the same problem as mentioned in the bug. I'm trying to build and upload a new release of python-psyco, and the built package is wrong because `pyversions -r debian/control` returns python2.4 even though debian/control says that XS-Python-Version is =2.2, 2.6. I have python-all installed, so I would expect the call to pyversions to return python2.3 python2.4 python2.5 Any package building C extension modules rebuilt with the current setup will only compile the C extension for python2.4, which is not what we want. -- Alexandre Fayolle LOGILAB, Paris (France) Formations Python, Zope, Plone, Debian: http://www.logilab.fr/formations Développement logiciel sur mesure: http://www.logilab.fr/services Informatique scientifique: http://www.logilab.fr/science Reprise et maintenance de sites CPS: http://www.migration-cms.com/ signature.asc Description: Digital signature
Bug#397571: debian-reference: FTBFS: ERROR: reference.zh-tw.pdf could not be generated properly
(I droped Lucas, as it becomes out of topic related to the FTBS. Osamu
and I are subscribed to the bug.)
Hi Danai,
On Thu, Nov 09, 2006 at 03:34:15AM +0100, Danai SAE-HAN wrote:
Okay, I checked out the SGML-generated .tex file, and it seems very
much that Perl or something else misinterprets some of the CJK
characters.
The command I used to create the .tex file was:
debiandoc2latex -l zh_TW.Big5 reference.zh-tw.sgml
Examples of these misinterpreted characters:
in titledoc.sgml: 程 - 琵{
in preface.sgml: 開 - 跚}
閱 - 閱textbackslash{}
誤 - 蓋textasciitilde{}
Misinterprets? I remember that this was intentional! Extract from
fixlatex script which is applied after the SGML/Perl magic:
(zh_TW)
perl -p \
-e 's/([\x80-\xff])\\textbackslash\{\}/$1\\/g;' \
-e 's/([\x80-\xff])\\textasciitilde\{\}/$1\~/g;' \
-e 's/([\x80-\xff])\\textasciicircum\{\}/$1\^/g;' \
-e 's/([\x80-\xff])\\\}/$1\}/g;' \
-e 's/([\x80-\xff])\\\{/$1\{/g;' \
-e 's/([\x80-\xff])\\\_/$1_/g;' $1 |
bg5conv $2
That's the only code I'm aware of which substitutes characters. I have
to confess that the code is cryptic and I do not fully understand it.
But it was provided by a Chinese person and introduced to support zh_TW
documents and building did not worked without in the past.
The funny thing is that I also looked into the bg5conv code and noticed
that it does also very similar tasks (only a few substitutions). I once
tried to merge both so that the substitutions can be called together on
pieces of text inside the LaTeX processor (and not afterwards for speed
up and simplicity) but ...
Please note that debiandoc-sgml is (more or less) language independent. The
general code is tools/lib/Format/LaTeX.pm which embeds a few (really, only
a few) language specific settings such as the language name required for babel
(if used at all). I added also the general 'before begin document',
'after begin document' and 'before end document' hooks, which are used
by Asian languages to embed CJK. Example from
tools/lib/Locale/zh_TW.Big5/LaTeX:
'pdfhyperref' = 'CJKbookmarks',
'before begin document' = '\\usepackage{CJK}',
'after begin document' = '\\begin{CJK}{Bg5}{kai}
\\renewcommand{\\vpageref}[1]{\(²Ä \\pageref{#1} ¶\)}',
'before end document' = '\\clearpage
\\end{CJK}'
That's the complete magic.
And perhaps a few other characters. I find it strange that not all
characters suffer from this problem, but only some. Perhaps Perl
doesn't have a complete map of the Big5 encoding?
A quick fix would perhaps be to put everything in a sed script.
I would prefer the opposite: deleting the above substitutions. Can you
please check these? Are they still necessary?
BTW: Are you a Chinese? Or do you also have to guess whats right and
what not?
What about the other languages? Japanese doesn't substitute strings but
failed with the same error that [EMAIL PROTECTED] was not defined ...
Because of the many \text* commands it's best to keep using bg5latex
instead of just latex, which apparently doesn't work. Fixing the
FTBS is much more important now ATM, so let's stick to bg5latex.
But it worked in the past. Do you still think it is necessary to use
bg5latex? This would make just more code language specific.
And on a sidenote, in zh-tw/install.sgml Windwos 95/98/Me should
become Windows 95/98/Me of course.
I will fix it, thanks.
I appreciate your hints, please continue,
Jens
Bug#397781: python-rrd: rrdtool module fails to import
Package: python-rrd Version: 1.2.15-0.1 Severity: grave Justification: renders package unusable I have reproduced this bug on two different ia32 sid systems. I'm not sure about the bug severity but I guess it makes the package unusable for most users. Here's the problem: $ python -c 'import rrdtool' Traceback (most recent call last): File string, line 1, in ? ImportError: dynamic module does not define init function (initrrdtool) $ nm -D /usr/lib/python2.4/site-packages/rrdtool.so | grep initrrd 0f20 T initrrdtoolmodule It looks like the module entry point does not have the right name for some reason (but I may be mistaken). -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (150, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.18-1-686 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages python-rrd depends on: ii libc62.3.6.ds1-8 GNU C Library: Shared libraries ii librrd2 1.2.15-0.1 Time-series data storage and displ python-rrd recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: setting package to grub grub-disk grub-doc, tagging 394020
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.24 package grub grub-disk grub-doc Ignoring bugs not assigned to: grub grub-doc grub-disk tags 394020 + pending Bug#394020: grub: /usr/sbin/grub-install missing There were no tags set. Bug#393450: /sbin/grub-install wants me to call non existing /usr/sbin/grub-install Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: setting package to grub grub-disk grub-doc, tagging 394020, tagging 396315
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.9.24 package grub grub-disk grub-doc Ignoring bugs not assigned to: grub grub-doc grub-disk tags 394020 + pending Bug#394020: grub: /usr/sbin/grub-install missing Tags were: pending Bug#393450: /sbin/grub-install wants me to call non existing /usr/sbin/grub-install Tags added: pending tags 396315 + pending Bug#396315: 'man update-grub' typo: simliar Tags were: pending patch Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: severity 397747 serious
Processing commands for [EMAIL PROTECTED]: severity 397747 serious Bug#397747: grace6: missing dependency on gconf2 Severity set to `serious' from `important' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397759: fails to configure: mv: cannot stat `/etc/chrony/chrony.keys.1.21-2': No such file or directory
Lionel Elie Mamane writes:
The code assumes that when upgrading from version earlier than 1.21-3,
you *must* have a /etc/chrony/chrony.keys.${OLD_VERSION} file.
If true this is certainly a bug. I'll look at it ASAP.
--
John Hasler
[EMAIL PROTECTED]
Elmwood, WI USA
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#397717: lmodern: install failed with error message warning: directory /usr/lib/X11/fonts/Type1 does not exist
severity 397717 normal thanks daniel bosold [EMAIL PROTECTED] wrote: I'm not sure at which point i would have refused to use a file. i have no personally modified latex files outside my home dir so i would have accepted any modifications to /etc files (most probably anyway). It seems you might not have modified files yourself, but called updmap to do that... % grep lm.map /etc/texmf/updmap.d/* /etc/texmf/updmap.d/10lmodern.cfg:Map cork-lm.map /etc/texmf/updmap.d/10local.cfg:Map lm.map The 10local.cfg probably comes from your calling updmap-sys --enable Map lm.map sometime in the past. It's probable that this was suggested by some non-Debian lmodern installation instructions. And it should work on Debian, too - but only if lm.map is installed. Since lm.map in 1.00 is buggy, the Debian package doesn't install it. So just remove the file 10local.cfg, and the lm.map that you have put into /usr/share/texmf (which, by the way, you should never have done: this directory is in the realm of dpkg, and local additions should go into /usr/local/share/texmf). Then call update-updmap, now lmodern should configure or reconfigure fine. I'm leaving the bug open, we should think whether we can provide better error messages - and maybe it's not a good idea to exclude lm.map from the deb? But the good thing about it is that problems show up early. As for the error message, we cannot add a check in lmodern's postinst explicitly. But we could do the following in tex-common: --- scripts/postinst-tex(Revision 1922) +++ scripts/postinst-tex(Arbeitskopie) @@ -22,10 +22,15 @@ rm -f $tempfile echo done. else +exec 2 echo echo updmap-sys failed. Output has been stored in echo $tempfile echo Please include this file if you report a bug. + echo + echo Sometimes, not accepting conffile updates in /etc/texmf/updmap.d + echo causes updmap-sys to fail. Please check for files with extension + echo .dpkg-new or .ucf-new in this directory echo exit 1 fi (shouldn't all those error messages go to 2? Or all messages - how about debconf being active at this time?) Regards, Frank -- Dr. Frank Küster Single Molecule Spectroscopy, Protein Folding @ Inst. f. Biochemie, Univ. Zürich Debian Developer (teTeX/TeXLive)
Bug#349812: marked as done (backup-manager: security update overwrote conffile)
Your message dated Thu, 09 Nov 2006 14:55:06 +0100 with message-id [EMAIL PROTECTED] and subject line backup-manager: security update overwrote conffile has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: backup-manager Version: 0.5.7-1sarge1 Severity: grave Justification: renders package unusable Because /etc/backup-manager.conf is not marked as a conffile, the last security update overwrote my configuration of /etc/backup-manager.conf. I configured an upload via ftp and also MB_POST_BACKUP_COMMAND. The complete configuration is lost, so that no backup to the ftp site was made. The hint in README.Debian to not edit the .conf file and to use debconf instead is useless, since not all options are handled by debconf. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (99, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-2-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages backup-manager depends on: ii debconf 1.4.30.13 Debian configuration management sy ii gzip 1.3.5-10sarge1 The GNU compression utility -- debconf information: backup-manager/upload-passwd: (password omitted) backup-manager/upload-key: * backup-manager/name-format: long backup-manager/burning-device: /dev/cdrom backup-manager/upload-hosts: backup-manager/upload-dir: /var/archives/uploads backup-manager/upload-user-ftp: * backup-manager/cron_frequency: daily * backup-manager/directories: /etc /home /var/lib/dpkg * backup-manager/blacklist: /var/archives * backup-manager/filetype: tar.gz * backup-manager/time-to-live: 30 backup-manager/burning-maxsize: 650 * backup-manager/backup-repository: /var/archives backup-manager/burning-method: CDRW backup-manager/upload-user-scp-warning: backup-manager/transfert_mode: scp * backup-manager/burning-enabled: false * backup-manager/dump_symlinks: false backup-manager/upload-user-scp: bmngr backup-manager/cron_remove_deprecated: false * backup-manager/want_to_upload: false ---End Message--- ---BeginMessage--- Version: 0.5.8-1 This bug has been fixed in testing and unstable with the upload of version 0.5.8-1, so I'm closing it (with a Version: pseudoheader) to document this status as completely as possible. The bug still affects the version of backup-manager in sarge. -- Alexis Sukrieh s ---End Message---
Bug#393450: marked as done (/sbin/grub-install wants me to call non existing /usr/sbin/grub-install)
Your message dated Thu, 09 Nov 2006 05:32:22 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#394020: fixed in grub 0.97-19 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: grub Version: 0.97-18 Severity: normal # grub-install /dev/sdb You shouldn't call /sbin/grub-install. Please call /usr/sbin/grub-install instead! Installation finished. No error reported. This is the contents of the device map /boot/grub/device.map. Check if this is correct or not. If any of the lines is incorrect, fix it and re-run the script `grub-install'. (hd0) /dev/sda (hd1) /dev/sdb # ls -la /usr/sbin/grub-install ls: /usr/sbin/grub-install: No such file or directory # -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.8-2-386 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages grub depends on: ii libc62.3.6.ds1-4 GNU C Library: Shared libraries ii libncurses5 5.5-3 Shared libraries for terminal hand grub recommends no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: grub Source-Version: 0.97-19 We believe that the bug you reported is fixed in the latest version of grub, which is due to be installed in the Debian FTP archive: grub-disk_0.97-19_all.deb to pool/main/g/grub/grub-disk_0.97-19_all.deb grub-doc_0.97-19_all.deb to pool/main/g/grub/grub-doc_0.97-19_all.deb grub_0.97-19.diff.gz to pool/main/g/grub/grub_0.97-19.diff.gz grub_0.97-19.dsc to pool/main/g/grub/grub_0.97-19.dsc grub_0.97-19_i386.deb to pool/main/g/grub/grub_0.97-19_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Otavio Salvador [EMAIL PROTECTED] (supplier of updated grub package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 9 Nov 2006 11:15:39 -0200 Source: grub Binary: grub-disk grub grub-doc Architecture: source i386 all Version: 0.97-19 Distribution: unstable Urgency: low Maintainer: Grub Maintainers [EMAIL PROTECTED] Changed-By: Otavio Salvador [EMAIL PROTECTED] Description: grub - GRand Unified Bootloader grub-disk - GRUB bootable disk image grub-doc - Documentation for GRand Unified Bootloader Closes: 367889 393488 394020 395275 396315 397021 397775 Changes: grub (0.97-19) unstable; urgency=low . [ Leandro Dorileo ] * Changed how grub handles the saved default entry in the savedefault(once) patch in stage2/stage2.c cmain function, changed grub-reboot to print the warning already being printed in grub-set-default to default file. Closes: #367889, #397021. . [ Otavio Salvador ] * Applied patch from Christian Eckerle [EMAIL PROTECTED] to not always prepend /boot in front of the kernel line for xen if /boot is on its on partition. Closes: #393488. * Applied patch from Mike Kasick [EMAIL PROTECTED] to fix the handle of null options. Closes: #395275. * Applied patch from Markus Schulz [EMAIL PROTECTED] to fix xen kernel name detection. Closes: #397775. * Fix grub-install and update-grub mess. Closes: #394020. * Applied patch from A. Costa [EMAIL PROTECTED] to fix a typo on update-grub.8. Closes: #396315. Files: 74e3f44a2419ec9a262bd069df714069 896 admin optional grub_0.97-19.dsc 4652025be57682293e1190211d45a879 72468 admin optional grub_0.97-19.diff.gz 82a86a9f95c5eecc10397909548787d8 372894 admin optional grub_0.97-19_i386.deb 36548030dc29a6d956b5f789022141d4 243594 admin optional grub-disk_0.97-19_all.deb 7887807b12b150619888924904e5ff89 271774 doc optional grub-doc_0.97-19_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFUyowLqiZQEml+FURAuzpAJ9AQdFXqju1Hg2d4+8VAE53QppeYACeOO9N KN6dsVokGdlsm7JKoDNe0gQ= =dGqy -END PGP SIGNATURE- ---End Message---
Processed: Re: Bug#397717: lmodern: install failed with error message warning: directory /usr/lib/X11/fonts/Type1 does not exist
Processing commands for [EMAIL PROTECTED]: severity 397717 normal Bug#397717: lmodern: install failed with error message warning: directory /usr/lib/X11/fonts/Type1 does not exist Severity set to `normal' from `grave' thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#394020: marked as done (grub: /usr/sbin/grub-install missing)
Your message dated Thu, 09 Nov 2006 05:32:22 -0800 with message-id [EMAIL PROTECTED] and subject line Bug#394020: fixed in grub 0.97-19 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) ---BeginMessage--- Package: grub Version: 0.97-18 Severity: serious On both a newly installed and an existing AMD64 system: $ ls -1 /usr/sbin/grub* /usr/sbin/grub /usr/sbin/grub-floppy /usr/sbin/grub-install.real /usr/sbin/grub-md5-crypt /usr/sbin/grub-reboot /usr/sbin/grub-set-default /usr/sbin/grub-terminfo AFAIK there should also be a wrapper 'grub-install' in /usr/sbin. pgpm3oCnFjEba.pgp Description: PGP signature ---End Message--- ---BeginMessage--- Source: grub Source-Version: 0.97-19 We believe that the bug you reported is fixed in the latest version of grub, which is due to be installed in the Debian FTP archive: grub-disk_0.97-19_all.deb to pool/main/g/grub/grub-disk_0.97-19_all.deb grub-doc_0.97-19_all.deb to pool/main/g/grub/grub-doc_0.97-19_all.deb grub_0.97-19.diff.gz to pool/main/g/grub/grub_0.97-19.diff.gz grub_0.97-19.dsc to pool/main/g/grub/grub_0.97-19.dsc grub_0.97-19_i386.deb to pool/main/g/grub/grub_0.97-19_i386.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Otavio Salvador [EMAIL PROTECTED] (supplier of updated grub package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 9 Nov 2006 11:15:39 -0200 Source: grub Binary: grub-disk grub grub-doc Architecture: source i386 all Version: 0.97-19 Distribution: unstable Urgency: low Maintainer: Grub Maintainers [EMAIL PROTECTED] Changed-By: Otavio Salvador [EMAIL PROTECTED] Description: grub - GRand Unified Bootloader grub-disk - GRUB bootable disk image grub-doc - Documentation for GRand Unified Bootloader Closes: 367889 393488 394020 395275 396315 397021 397775 Changes: grub (0.97-19) unstable; urgency=low . [ Leandro Dorileo ] * Changed how grub handles the saved default entry in the savedefault(once) patch in stage2/stage2.c cmain function, changed grub-reboot to print the warning already being printed in grub-set-default to default file. Closes: #367889, #397021. . [ Otavio Salvador ] * Applied patch from Christian Eckerle [EMAIL PROTECTED] to not always prepend /boot in front of the kernel line for xen if /boot is on its on partition. Closes: #393488. * Applied patch from Mike Kasick [EMAIL PROTECTED] to fix the handle of null options. Closes: #395275. * Applied patch from Markus Schulz [EMAIL PROTECTED] to fix xen kernel name detection. Closes: #397775. * Fix grub-install and update-grub mess. Closes: #394020. * Applied patch from A. Costa [EMAIL PROTECTED] to fix a typo on update-grub.8. Closes: #396315. Files: 74e3f44a2419ec9a262bd069df714069 896 admin optional grub_0.97-19.dsc 4652025be57682293e1190211d45a879 72468 admin optional grub_0.97-19.diff.gz 82a86a9f95c5eecc10397909548787d8 372894 admin optional grub_0.97-19_i386.deb 36548030dc29a6d956b5f789022141d4 243594 admin optional grub-disk_0.97-19_all.deb 7887807b12b150619888924904e5ff89 271774 doc optional grub-doc_0.97-19_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFUyowLqiZQEml+FURAuzpAJ9AQdFXqju1Hg2d4+8VAE53QppeYACeOO9N KN6dsVokGdlsm7JKoDNe0gQ= =dGqy -END PGP SIGNATURE- ---End Message---
Bug#397571: debian-reference: FTBFS: ERROR: reference.zh-tw.pdf could not be generated properly
On Thu, Nov 09, 2006 at 02:08:54PM +0100, Jens Seidel wrote:
(I droped Lucas, as it becomes out of topic related to the FTBS. Osamu
and I are subscribed to the bug.)
Hi Danai,
On Thu, Nov 09, 2006 at 03:34:15AM +0100, Danai SAE-HAN wrote:
Okay, I checked out the SGML-generated .tex file, and it seems very
much that Perl or something else misinterprets some of the CJK
characters.
The command I used to create the .tex file was:
debiandoc2latex -l zh_TW.Big5 reference.zh-tw.sgml
Then debantex script from debiandoc-sgml was used. This was I vaguely
remenber for woody environment work around.
Examples of these misinterpreted characters:
in titledoc.sgml: 程 - 琵{
in preface.sgml: 開 - 跚}
閱 - 閱textbackslash{}
誤 - 蓋textasciitilde{}
Misinterprets? I remember that this was intentional! Extract from
fixlatex script which is applied after the SGML/Perl magic:
(zh_TW)
perl -p \
-e 's/([\x80-\xff])\\textbackslash\{\}/$1\\/g;' \
-e 's/([\x80-\xff])\\textasciitilde\{\}/$1\~/g;' \
-e 's/([\x80-\xff])\\textasciicircum\{\}/$1\^/g;' \
-e 's/([\x80-\xff])\\\}/$1\}/g;' \
-e 's/([\x80-\xff])\\\{/$1\{/g;' \
-e 's/([\x80-\xff])\\\_/$1_/g;' $1 |
bg5conv $2
This part is not used when building debian-reference. Package special
bin/fixlatex is used instead. It will be nice to remove these old junk.
It seems to fail when it does not find required fonts.
The best package to install font issue is latex-cjk-all package.
Let me see.
Processed (with 1 errors): merge 397747 394967
Processing commands for [EMAIL PROTECTED]: merge 397747 394967 Bug#394967: grace6: fails to configure Bug#397747: grace6: missing dependency on gconf2 Merged 394967 397747. done Unknown command or malformed arguments to command. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: gnusim8085: diff for NMU version 1.2.90-1.1
Processing commands for [EMAIL PROTECTED]: tags 396377 + patch Bug#396377: FTBFS: Missing Build-Conflicts with automake* There were no tags set. Tags added: patch thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#396377: gnusim8085: diff for NMU version 1.2.90-1.1
tags 396377 + patch thanks Hi, The following is the diff for my gnusim8085 1.2.90-1.1 NMU. diff -u gnusim8085-1.2.90/debian/changelog gnusim8085-1.2.90/debian/changelog --- gnusim8085-1.2.90/debian/changelog +++ gnusim8085-1.2.90/debian/changelog @@ -1,3 +1,10 @@ +gnusim8085 (1.2.90-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fixed FTBS, automake problems. (Closes: #396377) + + -- Ana Beatriz Guerrero Lopez [EMAIL PROTECTED] Thu, 9 Nov 2006 15:23:29 +0100 + gnusim8085 (1.2.90-1) unstable; urgency=low * New upstream release. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#396377: gnusim8085: diff for NMU version 1.2.90-1.1
tags 396377 + patch thanks Hi, The following is the diff for my gnusim8085 1.2.90-1.1 NMU. diff -u gnusim8085-1.2.90/debian/changelog gnusim8085-1.2.90/debian/changelog --- gnusim8085-1.2.90/debian/changelog +++ gnusim8085-1.2.90/debian/changelog @@ -1,3 +1,10 @@ +gnusim8085 (1.2.90-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fixed FTBS, automake problems. (Closes: #396377) + + -- Ana Beatriz Guerrero Lopez [EMAIL PROTECTED] Thu, 9 Nov 2006 15:23:29 +0100 + gnusim8085 (1.2.90-1) unstable; urgency=low * New upstream release. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Processed: gnusim8085: diff for NMU version 1.2.90-1.1
Processing commands for [EMAIL PROTECTED]: tags 396377 + patch Bug#396377: FTBFS: Missing Build-Conflicts with automake* Tags were: patch Tags added: patch thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#396377: gnusim8085: diff for NMU version 1.2.90-1.1
tags 396377 + patch thanks Hi, The following is the diff for my gnusim8085 1.2.90-1.1 NMU. diff -u gnusim8085-1.2.90/debian/changelog gnusim8085-1.2.90/debian/changelog --- gnusim8085-1.2.90/debian/changelog +++ gnusim8085-1.2.90/debian/changelog @@ -1,3 +1,10 @@ +gnusim8085 (1.2.90-1.1) unstable; urgency=medium + + * Non-maintainer upload. + * Fixed FTBS, automake problems. (Closes: #396377) + + -- Ana Beatriz Guerrero Lopez [EMAIL PROTECTED] Thu, 9 Nov 2006 15:23:29 +0100 + gnusim8085 (1.2.90-1) unstable; urgency=low * New upstream release. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
