Re: File type misclassification
>>> Sigh. Seems like a magic string for the "TeXshop" TeX editor. But I >>> think just ruling out [VT] is still asking for trouble. >> I think a bug report to the TeXshop is in order. > Uh, you people are joking, right? Nope! > It is not a bug in TeXshop if Emacs' magic-mode-alist goes out of control > and calls everything "PostScript". The %! thingy is not Emacs's invention. It's how postscript was specified. And for that reason `file greek-utf8.tex' agrees with Emacs. This said, I'd be happy to see the %! entry removed from magic-mode-alist, because I think magic-mode-alist should really be kept to its absolute strictest minimum. Stefan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: File type misclassification
opening the following file in emacs-snapshot from Ubuntu Edgy (sorry, I don't have a fresher CVS Emacs at work) will throw the buffer into PostScript mode, presumably because it starts with "%!". This seems rather like overkill. Same old problem where the file's content and the file's extension do not agree on what the file actually contains. And once again, the file extension is the better predictor whereas Emacs uses magic-mode-alist in preference to auto-mode-alist. > Sigh. Seems like a magic string for the "TeXshop" TeX editor. But I > think just ruling out [VT] is still asking for trouble. I think a bug report to the TeXshop is in order. >> 3) Remove it from magic-mode-alist. > Also an option in my book. Agreed, a very good option I'd say. Especially since editing postscript is rather uncommon. Stefan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: File type misclassification
> To take this out of magic-mode-alist, and leave recognition of > Postscript to file names alone, might be a good change, but I am not > sure of usage practices. Who put this entry in magic-mode-alist, and why? Stefan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#382511: marked as done (libwmf0.2-7: Multiple vulnerabilities in embedded libgd2 copy)
Your message dated Wed, 21 Mar 2007 10:17:03 + with message-id <[EMAIL PROTECTED]> and subject line Bug#382511: fixed in libwmf 0.2.8.4-5 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) --- Begin Message --- Package: libwmf Version: 0.2.8.4-2 Severity: important Tags: security patch Hi! libwmf contains an ancient (2001!) copy of libgd2, which is vulnerable against CVE-2004-0941, CVE-2004-0990 (integer overflows which can be exploited for arbitrary code execution with crafted PNGs) and CVE-2006-2906 (DoS with crafted GIFs). I did not verify whether these can be exploited through libwmf, therefore I did not set this to 'grave'. However, this should be fixed just to be on the safe side. Original libgd2 patches: http://people.ubuntu.com/patches/libgd2.CVE-2004-0941_0990.diff http://people.ubuntu.com/patches/libgd2.CVE-2006-2906.diff The best solution would be to build against the system libgd2 and ignore the code copy completely. This avoids code copies (which are *VERY* *VERY* hard to find), and thus such vulnerabilities, at all. Thank you for considering, Martin -- Martin Pitthttp://www.piware.de Ubuntu Developer http://www.ubuntu.com Debian Developer http://www.debian.org In a world without walls and fences, who needs Windows and Gates? signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: libwmf Source-Version: 0.2.8.4-5 We believe that the bug you reported is fixed in the latest version of libwmf, which is due to be installed in the Debian FTP archive: libwmf-bin_0.2.8.4-5_i386.deb to pool/main/libw/libwmf/libwmf-bin_0.2.8.4-5_i386.deb libwmf-dev_0.2.8.4-5_i386.deb to pool/main/libw/libwmf/libwmf-dev_0.2.8.4-5_i386.deb libwmf-doc_0.2.8.4-5_all.deb to pool/main/libw/libwmf/libwmf-doc_0.2.8.4-5_all.deb libwmf0.2-7_0.2.8.4-5_i386.deb to pool/main/libw/libwmf/libwmf0.2-7_0.2.8.4-5_i386.deb libwmf_0.2.8.4-5.diff.gz to pool/main/libw/libwmf/libwmf_0.2.8.4-5.diff.gz libwmf_0.2.8.4-5.dsc to pool/main/libw/libwmf/libwmf_0.2.8.4-5.dsc 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. Loic Minier <[EMAIL PROTECTED]> (supplier of updated libwmf 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: Wed, 21 Mar 2007 10:51:18 +0100 Source: libwmf Binary: libwmf-dev libwmf-bin libwmf-doc libwmf0.2-7 Architecture: source all i386 Version: 0.2.8.4-5 Distribution: experimental Urgency: low Maintainer: Loic Minier <[EMAIL PROTECTED]> Changed-By: Loic Minier <[EMAIL PROTECTED]> Description: libwmf-bin - Windows metafile conversion tools libwmf-dev - Windows metafile conversion development libwmf-doc - Windows metafile documentation libwmf0.2-7 - Windows metafile conversion library Closes: 382511 Changes: libwmf (0.2.8.4-5) experimental; urgency=low . * Convert the package to the new Gtk modules handling; closes: #382511. - Bump up the libgtk2.0-dev build-dep to >= 2.10.1-1. - Call dh_gtkmodules with an appropriate LD_LIBRARY_PATH. - Drop debian/postinst and debian/postrm. Files: 6d6c00f3314f611a5c41fc6bf935737b 777 libs optional libwmf_0.2.8.4-5.dsc b10d2690878607c8c93edc3fc91275bc 7634 libs optional libwmf_0.2.8.4-5.diff.gz 75d9037e673358a080433c646936911f 174188 libs optional libwmf0.2-7_0.2.8.4-5_i386.deb bd25e2b3bbd979f62ef6d339b2452059 16890 graphics optional libwmf-bin_0.2.8.4-5_i386.deb fdddbfcdbd6fd4974059eacf4aba1171 193138 libdevel optional libwmf-dev_0.2.8.4-5_i386.deb 13ed0bf94ce4a76e0b08d27d51eb6159 271704 doc optional libwmf-doc_0.2.8.4-5_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFGAQFi4VUX8isJIMARAiIRAJwNJzqTyQCjt+DnXAo1Y5pl7EdpYACfZ54f cwXczaGBbtr8uu0k0cZsDXQ= =XrH9 -END PGP SIGNATURE- --- End Message ---
Processed: Undo mistaken closure
Processing commands for [EMAIL PROTECTED]: > reopen 382511 Bug#382511: libwmf0.2-7: Multiple vulnerabilities in embedded libgd2 copy 'reopen' may be inappropriate when a bug has been closed with a version; you may need to use 'found' to remove fixed versions. Bug reopened, originator not changed. > 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]
daunt impedance
Remember paypal? C E O AMERICA I N C SYM-C E O A Cannot go wrong at 6 cents This could hit in short and over in the long run AN ALL AMERICAN COMPANY Get IN Before the rush TOMORROW cohesion because of injuries, illnesses, trades and suspensions. The Nuggets led the Pirates to a 68-55 record, a trip to the round of 16 in the 2000 got 25 points from Leandro Barbosa , never led in this one and fell behind by their fourth straight win, a 131-107 blowout of the Phoenix Suns on Saturday -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of barcode_0.98-3_i386.changes
barcode_0.98-3_i386.changes uploaded successfully to localhost along with the files: barcode_0.98-3.dsc barcode_0.98-3.tar.gz barcode_0.98-3_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
barcode_0.98-3_i386.changes ACCEPTED
Accepted: barcode_0.98-3.dsc to pool/main/b/barcode/barcode_0.98-3.dsc barcode_0.98-3.tar.gz to pool/main/b/barcode/barcode_0.98-3.tar.gz barcode_0.98-3_i386.deb to pool/main/b/barcode/barcode_0.98-3_i386.deb Override entries for your package: barcode_0.98-3.dsc - source graphics barcode_0.98-3_i386.deb - optional graphics Announcing to debian-devel-changes@lists.debian.org Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
outstretched overland
Digital payment is the way of the future C E O AMERICA I N C SYmb-CEO A Cannot go wrong at 6 cents Add this to your radar AN ALL AMERICAN COMPANY Get IN Before the rush TOMORROW "There were moments of delight and success (this season)," Martin said. scandal, the school's lackluster facilities and Ellerbe's awful recruiting. coach on March 31, 2011, to earn a deferred-compensation package after the school's -- with three 20-win seasons -- and 43-53 in the Big Ten. He was under contract -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of libhdf4_4.1r4-19_i386.changes
libhdf4_4.1r4-19_i386.changes uploaded successfully to localhost along with the files: libhdf4_4.1r4-19.dsc libhdf4_4.1r4-19.diff.gz libhdf4g-doc_4.1r4-19_all.deb libhdf4g_4.1r4-19_i386.deb libhdf4g-dev_4.1r4-19_i386.deb libhdf4g-run_4.1r4-19_i386.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
libhdf4 override disparity
There are disparities between your recently accepted upload and the override file for the following file(s): libhdf4g-dev_4.1r4-19_i386.deb: package says section is devel, override says libdevel. Either the package or the override file is incorrect. If you think the override is correct and the package wrong please fix the package so that this disparity is fixed in the next upload. If you feel the override is incorrect then please reply to this mail and explain why. [NB: this is an automatically generated mail; if you replied to one like it before and have not received a response yet, please ignore this mail. Your reply needs to be processed by a human and will be in due course, but until then the installer will send these automated mails; sorry.] -- Debian distribution maintenance software (This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
libhdf4_4.1r4-19_i386.changes ACCEPTED
Accepted: libhdf4_4.1r4-19.diff.gz to pool/main/libh/libhdf4/libhdf4_4.1r4-19.diff.gz libhdf4_4.1r4-19.dsc to pool/main/libh/libhdf4/libhdf4_4.1r4-19.dsc libhdf4g-dev_4.1r4-19_i386.deb to pool/main/libh/libhdf4/libhdf4g-dev_4.1r4-19_i386.deb libhdf4g-doc_4.1r4-19_all.deb to pool/main/libh/libhdf4/libhdf4g-doc_4.1r4-19_all.deb libhdf4g-run_4.1r4-19_i386.deb to pool/main/libh/libhdf4/libhdf4g-run_4.1r4-19_i386.deb libhdf4g_4.1r4-19_i386.deb to pool/main/libh/libhdf4/libhdf4g_4.1r4-19_i386.deb Override entries for your package: libhdf4_4.1r4-19.dsc - source graphics libhdf4g-dev_4.1r4-19_i386.deb - optional libdevel libhdf4g-doc_4.1r4-19_all.deb - optional doc libhdf4g-run_4.1r4-19_i386.deb - optional graphics libhdf4g_4.1r4-19_i386.deb - optional libs Announcing to debian-devel-changes@lists.debian.org Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Joint Venture Opportunity
Hello Hope you are well and that business is good. Luke here from the Overseas Property Webshow, we swapped links a while ago. Today I have a very interesting proposal for you. Q: how would you like two one-way inbound links from the home page of two different well established and minimum Google page rank 4 sites for one link back from your site? The site I would like you to link to is http://www.nirvanainternational.com Anchor text can be any of the following three phrases Turkey property Investment property in Turkey Property for sale in Turkey let me know and I'll send you a list of site for you to pick your links from ;-) Many thanks and I look forward to hearing from you. Kindest regards Luke Fitzsimmons Overseas Property Webshow 7 the square Wimborne Dorset BH21 1JA +44 (0) 1202 842200 [EMAIL PROTECTED] www.pi-marketing.co.uk www.fplwebshows.com www.overseaspropertywebshow.com -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: File type misclassification
> In contrast, %! is far too generic to be useful. It may be a > heuristic for a PostScript interpreter to decide whether it is getting > fed PostScript on stdin. But it does not sound like a useful > heuristic for a text editor to decide whether a named file contains > PostScript code or anything else. Complete agreement. But it still means that TeXshop should avoid the "%!" magic characters because they have a conflicting meaning in some contexts. I don't claim that TeXshop should change for the sake of Emacs: it should change because its choice is fundamentally wrong, whether that bites Emacs users or not is irrelevant. >> This said, I'd be happy to see the %! entry removed from >> magic-mode-alist, because I think magic-mode-alist should really be >> kept to its absolute strictest minimum. > I don't think that "%!PS" has comparable potential to do accidental > harm. Whether it does noticeable good is a different question > altogether. Obviously using a stricter regexp is good in my book since it means that magic-mode-alist is used less often. > However, dvips -i produces PostScript files where the extension is > replaced by a serial number. Those will not be recognized as > PostScript without magic number detection. "%!PS" is completely > sufficient for that purpose, however. Well, I find the likelihood of someone trying to edit with Emacs the output of "dvips -i" sufficiently low that it doesn't justify in my eye the use of a magic-mode-alist entry for it. That's just an opinion. Maybe a better solution is to make dvips output file names of the form foo.NNN.ps rather than foo.ps.NNN. > So I think that "%!PS" _does_ have some usefulness, and it is clearly > not as overboard as "%!". We agree that it's a step in the right direction. Stefan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: File type misclassification
Stefan Monnier <[EMAIL PROTECTED]> writes: > opening the following file in emacs-snapshot from Ubuntu Edgy > (sorry, I don't have a fresher CVS Emacs at work) will throw the > buffer into PostScript mode, presumably because it starts with > "%!". This seems rather like overkill. > > Same old problem where the file's content and the file's extension do not > agree on what the file actually contains. And once again, the file > extension is the better predictor whereas Emacs uses magic-mode-alist in > preference to auto-mode-alist. > >> Sigh. Seems like a magic string for the "TeXshop" TeX editor. But I >> think just ruling out [VT] is still asking for trouble. > > I think a bug report to the TeXshop is in order. Uh, you people are joking, right? It is not a bug in TeXshop if Emacs' magic-mode-alist goes out of control and calls everything "PostScript". >>> 3) Remove it from magic-mode-alist. >> Also an option in my book. > > Agreed, a very good option I'd say. Especially since editing > postscript is rather uncommon. Since I don't seem too good at explaining what appears as common sense to me, I'll fix the magic expression myself to "#!PS". That's still a less drastic change than removing it altogether, and most people seem to agree that the latter option would be quite feasible. This won't catch "#!\n" which seems to be used in some hand-crafted PS files, but then the handcrafted files (vasarely.ps, for example) should be discernible by file extension, and one would have to actually use some generic line-ending recognizer instead of "\n", anyway, since PostScript has no fixed line-ending convention. If others find they want even the "#!PS" gone (which I don't really see as a problem), or add some form of "#!lineend", feel free to discuss and fix. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#415807: error while running gnump3d-index
Package: gnump3d Version: 2.9.3-1sarge3 Severity: normal I have this everyday in my inbox: /etc/cron.daily/gnump3d: Use of uninitialized value in numeric eq (==) at /usr/bin/gnump3d-index line 365. -- System Information: Debian Release: 3.1 Architecture: i386 (i686) Kernel: Linux 2.6.8-3-386 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages gnump3d depends on: ii debconf [debconf-2.0] 1.4.30.13 Debian configuration management sy ii logrotate 3.7-5 Log rotation utility ii perl 5.8.4-8sarge5 Larry Wall's Practical Extraction ii perl-modules 5.8.4-8sarge5 Core Perl modules -- debconf information: * gnump3d/user: gnump3d * gnump3d/root: /data/music * gnump3d/port: -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
