Bug#693114: dovecot-core: Mailboxes inaccessible after upgrade
Package: dovecot Version: 1:2.1.7-4 Severity: serious Dear Maintainer, After an update from 1:2.1.7-2 to 1:2.1.7-4, I could not access my mailboxes at ~/Maildir any more. (This may be related to #644121.) I noticed the following line in conf.d/10-mail.conf: , | mail_location = mbox:~/mail:INBOX=/var/mail/%u ` My git (etckeeper) repository shows that previously, mail_location had been commented out. Commenting it out again fixes the problem for me. (Is ~/Maildir the default value set at compile time?) Below I have pasted the only dovecot-related output I was able to capture from the screen session. It is clear that conf.d/10-mail.conf has been overwritten during the upgrade. , | Setting up dovecot-core (1:2.1.7-4) ... | Installing new version of config file /etc/init.d/dovecot ... | Replacing config file /etc/dovecot/conf.d/10-mail.conf with new version | Replacing config file /etc/dovecot/conf.d/10-ssl.conf with new version | | Creating config file /etc/dovecot/conf.d/10-tcpwrapper.conf with new version | | Creating config file /etc/dovecot/conf.d/15-mailboxes.conf with new version | | Creating config file /etc/dovecot/conf.d/auth-checkpassword.conf.ext with new version | | Creating config file /etc/dovecot/conf.d/auth-sql.conf.ext with new version | You already have ssl certs for dovecot. | However you should move them out of /etc/ssl | and into /etc/dovecot and update the configuration | in /etc/dovecot/conf.d/10-ssl.conf accordingly. | See /usr/share/dovecot-core/NEWS.Debian for details. | Starting IMAP/POP3 mail server: dovecot. ` Cheers, -Hilko -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#684852: [Python-modules-team] Bug#684852: nmu
On 2012-11-12 22:47, Michael Gilbert wrote: Hi, I've uploaded an nmu fixing this issue to delayed/5. Please see attached patch. I don't understand your version number. Please see devref [1] and consider that this does not appear to be a native package. 1: http://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu-changelog -- Jonathan Wiltshire j...@debian.org Debian Developer http://people.debian.org/~jmw 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 directhex i have six years of solaris sysadmin experience, from 8-10. i am well qualified to say it is made from bonghits layered on top of bonghits -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693096: [dwarves] pahole just segfaults
Control: tags -1 + moreinfo unreproducible On Tue, Nov 13, 2012 at 12:10:20AM +, Franz Schrober wrote: Just noticed that pahole just segfault when giving him a object file after I upgraded from libelf 0.152+b1 to 0.153-1. Downgrading fixes the problem Unable to reproduce with libelf1 0.153-1 and 0.153-2. -- WBR, wRAR signature.asc Description: Digital signature
Processed: Re: Bug#693096: [dwarves] pahole just segfaults
Processing control commands: tags -1 + moreinfo unreproducible Bug #693096 [dwarves] [dwarves] pahole just segfaults Added tag(s) unreproducible and moreinfo. -- 693096: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693096 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#651795: Debian support for non-standard kernels
Hi all, because of this bug lustre-source has been removed from Wheezy. From my point of view that's a pity. I wonder if there's a general Debian policy that regulates that kernel module sources and kernel patches are not suitable for a release if they are not applicable to the default release kernel. What's the point of rolling your own kernel then? Is there a list of kernel versions that a certain Debian release is compatible with (e.g. is 2.6.32 too old for Wheezy?). Lustre may not build on 3.1 but having the Lustre sources debianized and in the Debian release still eases building and deployment of lustre on Debian a lot. And it prevents duplication of work done by everyone who wants to run Lustre on Debian. Cheers, Christo smime.p7s Description: S/MIME Cryptographic Signature
Bug#669382: latex209-base: unowned file /usr/local/share/texmf/ls-R after purge (policy 6.8, 9.1.2)
On Tue, Nov 13, 2012 at 10:09:01 +0900, Norbert Preining wrote: If the release managers agree I will upload the NMU, but it does not make sense to upload a big NMU with lots of changes and then it is not going into wheezy. The release managers won't agree to anything without seeing what changes you're talking about. Cheers, Julien signature.asc Description: Digital signature
Bug#685251: Fixing Debian bug #685251 for the ryu plugin in Openstack
On Fri, Nov 9, 2012 at 05:03:58 +0800, Thomas Goirand wrote: Please let me know if the attached patch would be accepted by the release team and avoid Quantum to be removed. Sigh. If you want to be sure it'll be accepted then just upload the minimal fix for the RC bug and leave it at that (2012.1-6 doesn't seem to list a bug number, so without more explanations it doesn't qualify). I'm not going to review every single one of your uploads 5 times. Cheers, Julien signature.asc Description: Digital signature
Bug#685251: Fixing Debian bug #685251 for the ryu plugin in Openstack
On 11/13/2012 07:08 PM, Julien Cristau wrote: On Fri, Nov 9, 2012 at 05:03:58 +0800, Thomas Goirand wrote: Please let me know if the attached patch would be accepted by the release team and avoid Quantum to be removed. Sigh. If you want to be sure it'll be accepted then just upload the minimal fix for the RC bug and leave it at that (2012.1-6 doesn't seem to list a bug number, so without more explanations it doesn't qualify). As I wrote, these changes were not mine. I don't think it's appropriate to write sigh or to be pissed *at me*. The only thing I did was working on the issue the release team cared about, and fixing it, I'm not responsible for the other changes, and I don't intend to assume responsibility for them regarding the unblock. It wasn't nice that these changes were uploaded without caring about the SID to Wheezy migration. Numerous times, I wrote about it to both Ola and Loic. I'm not surprised about the resulting conversation with the release team. But since that's not my work, and that I would like to respect what the others do, I still want to leave them the job to answer about it. So please, Ola and Loic, explain and deal with the release team. If you guys think the changes are necessary, tell why. If you think they should be removed, please do the necessary git revert (or at the very least, let me know that you would agree if I was to do it). And finally, I hope this is a lesson and that it wont happen again, and that you will bare with me and the rest of the PKG Openstack team. I'm not going to review every single one of your uploads 5 times. You don't have to, you can accept it the first time! :) Thomas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#659994: [regression] icedove: symbol lookup error: [...]/libdbusservice.so: undefined symbol: NS_Alloc
Moritz Muehlenhoff j...@inutil.org writes: On Fri, Feb 24, 2012 at 01:55:54PM +0100, Ansgar Burchardt wrote: Am 21.02.2012 19:46, schrieb Christoph Goehre: On Mi, Feb 15, 2012 at 05:34:45 +0100, Ansgar Burchardt wrote: since the last security update for icedove, the program does not start on several computers here. Instead the following error message is displayed: /usr/lib/icedove/icedove-bin: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc I could reproduce it, but I need to move my .icedove profile away. If I downgrade to libc6 version 2.11.2-10, everything is working fine. So here my steps to reproduce: 1) add deb http://snapshot.debian.org/archive/debian/20111215/ squeeze main to /etc/apt/sources.list and run 'apt-get update' 2) install older libc6 apt-get install libc-bin=2.11.2-10 libc-dev-bin=2.11.2-10 libc6=2.11.2-10 libc6-dev=2.11.2-10 libc6-i386=2.11.2-10 locales=2.11.2-10 3) rerun Icedove Same here: icedove starts with the older version of libc6, but not with version 2.11.3-3. The same is true when also downgrading icedove to 3.0.11-1+squeeze6 (works with old libc6, not with newer libc6). I can also upgrade libc6 to 2.11.3-3 and icedove continues working, but if I also change the version of icedove (by either upgrading or downgrading), icedove again refuses to start. So this seems to be something triggered by running icedove after an update. Does this still occur with Squeeze 6.0.6 ? Yes, this still happens here: # dpkg -l icedove libc6 ii icedove 3.0.11-1+squeeze14 mail/news client with RSS and integrated spam filter support ii libc6 2.11.3-4Embedded GNU C Library: Shared libraries # icedove /usr/lib/icedove/icedove-bin: symbol lookup error: /usr/lib/icedove/components/libdbusservice.so: undefined symbol: NS_Alloc Ansgar -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693114: dovecot-core: Mailboxes inaccessible after upgrade
On Tue, 13 Nov 2012, Hilko Bengen wrote: Package: dovecot Version: 1:2.1.7-4 Severity: serious Dear Maintainer, After an update from 1:2.1.7-2 to 1:2.1.7-4, I could not access my mailboxes at ~/Maildir any more. (This may be related to #644121.) No I don't think so. This on the other hand: I noticed the following line in conf.d/10-mail.conf: , | mail_location = mbox:~/mail:INBOX=/var/mail/%u ` From /usr/share/doc/dovecot-core/README.Debian (and NEWS.Debian) * In conf.d/10-mail.conf, the default mail_location is set to mbox:~/mail:INBOX=/var/mail/%u This has to be set because Dovecots auto-detection of mailboxes fails when a user has no mail. I tried to provide a reasonable default but advanced users will certainly want to change this. Related to this, you might see an error in the logs about dovecot not being able to chgrp certain files. This is because the default user mailboxes in Debian belong to group mail which dovecot is not part of (nor should be.) The Debian package has been patched so that the error will not be fatal but for a more permanent solution, see here: http://wiki2.dovecot.org/Errors/ChgrpNoPerm for some discussion. Or you can set mail_location (and the equivalent settings in your MDA) so that mailboxes are in the users home directory. My git (etckeeper) repository shows that previously, mail_location had been commented out. Commenting it out again fixes the problem for me. (Is ~/Maildir the default value set at compile time?) No but auto-detection worked because you already had mail. If you hadn't you would have run into #623440 I'm really stuck as to how to handle this. Debian policy demands /var/mail be owned by group mail. If I had left the status quo, all new users would have had the same problem you've faced. But fixing it for them causes problems for you. I'm leaving this bug open in case you (or anyone else) have some solution but I really don't think anything more can be done. -- Jaldhar H. Vyas jald...@debian.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682050: nmu
Now see if you had contacted the maintainer prior to performing the NMU upload you would have found out that your information was in fact flawed. BTS #690080 was to inform of the new upstream maintainer only a month ago and I've been in contact privately. Furthermore 1.9 was only released within the last week by said new upstream maintainer. That my friend is why you contact the maintainer and find out if assistance is in fact needed or else you're just mucking shit up and pissing the maintainer off considerably. On 12.11.2012 22:17, Michael Gilbert wrote: On Mon, Nov 12, 2012 at 9:50 PM, Jeremy T. Bouse wrote: Not my problem... You put the burden on me, I'm giving you the burden since you obviously took the time failing to contact me to ask and ascertain whether the maintainer might actually be in the process of doing anything with the package. I read the bug traffic, and the latest maintainer activity was four months ago. That's usually a strong indicator that the package needs help. The RC issues were introduced by a previous NMU, the issues are resolved in the new upstream release so as far as I'm concerned their wont-fix issues in this version. I understand that this was introduced by the prior nmu, and that's why this nmu is reverting that broken one. But as I'm turning the package over to you, do what you like. You may as well orphan it so it can get cared for either by the QA team or someone who really cares about it. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#680084: nmu
On Tue, Nov 13, 2012 at 00:30:06 +0100, Julien Cristau wrote: On Mon, Nov 12, 2012 at 16:57:30 -0500, Michael Gilbert wrote: Hi, I've uploaded an nmu fixing this issue to delayed/7. The extra time is to give you a chance to do a maintainer upload instead. Please see attached patch. Isn't this bug just a dupe of 684293, in which case it doesn't need an os-prober change? Also, 'nmu' is the worst Subject ever. Including context helps. Cheers, Julien signature.asc Description: Digital signature
Bug#693134: funguloid: crashes on start with OGRE EXCEPTION
Package: funguloids Version: 1.06-9 Severity: grave Justification: renders package unusable Dear Maintainer, funguloids crashes upon start with the following message. The (to me) suspicious lines are towards the end where it talks about trying to load an x86_64 library on my 32bit system. Creating resource group General Creating resource group Internal Creating resource group Autodetect SceneManagerFactory for type 'DefaultSceneManager' registered. Registering ResourceManager for type Material Registering ResourceManager for type Mesh Registering ResourceManager for type Skeleton MovableObjectFactory for type 'ParticleSystem' registered. OverlayElementFactory for type Panel registered. OverlayElementFactory for type BorderPanel registered. OverlayElementFactory for type TextArea registered. Registering ResourceManager for type Font ArchiveFactory for archive type FileSystem registered. ArchiveFactory for archive type Zip registered. DDS codec registering FreeImage version: 3.15.1 This program uses FreeImage, a free, open source image library supporting all common bitmap formats. See http://freeimage.sourceforge.net for details Supported formats: bmp,ico,jpg,jif,jpeg,jpe,jng,koa,iff,lbm,mng,pbm,pbm,pcd,pcx,pgm,pgm,png,ppm,ppm,ras,tga,targa,tif,tiff,wap,wbmp,wbm,psd,cut,xbm,xpm,gif,hdr,g3,sgi,exr,j2k,j2c,jp2,pfm,pct,pict,pic,3fr,arw,bay,bmq,cap,cine,cr2,crw,cs1,dc2,dcr,drf,dsc,dng,erf,fff,ia,iiq,k25,kc2,kdc,mdc,mef,mos,mrw,nef,nrw,orf,pef,ptx,pxn,qtk,raf,raw,rdc,rw2,rwl,rwz,sr2,srf,sti Registering ResourceManager for type HighLevelGpuProgram Registering ResourceManager for type Compositor MovableObjectFactory for type 'Entity' registered. MovableObjectFactory for type 'Light' registered. MovableObjectFactory for type 'BillboardSet' registered. MovableObjectFactory for type 'ManualObject' registered. MovableObjectFactory for type 'BillboardChain' registered. MovableObjectFactory for type 'RibbonTrail' registered. Loading library /usr/lib/x86_64-linux-gnu/OGRE-1.7.4/RenderSystem_GL An exception has occured: OGRE EXCEPTION(7:InternalErrorException): Could not load dynamic library /usr/lib/x86_64-linux-gnu/OGRE-1.7.4/RenderSystem_GL. System Error: /usr/lib/x86_64-linux-gnu/OGRE-1.7.4/RenderSystem_GL.so: cannot open shared object file: No such file or directory in DynLib::load at /build/buildd-ogre_1.7.4+dfsg1-6-i386-HFTCPD/ogre-1.7.4+dfsg1/OgreMain/src/OgreDynLib.cpp (line 91)funguloids: /usr/include/OGRE/OgreSharedPtr.h:160: T* Ogre::SharedPtrT::operator-() const [with T = Ogre::Material]: Assertion `pRep' failed. Abgebrochen Cheers, Armin -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages funguloids depends on: ii dpkg 1.16.9 ii funguloids-data 1.06-9 ii libalut0 1.1.0-3 ii libc62.13-36 ii libgcc1 1:4.7.2-4 ii liblua5.1-0 5.1.5-4 ii libmad0 0.15.1b-7 ii libogre-1.7.41.7.4+dfsg1-6 ii libois-1.3.0 1.3.0+dfsg0-5 ii libopenal1 1:1.14-4 ii libstdc++6 4.7.2-4 ii libvorbisfile3 1.3.2-1.3 funguloids recommends no packages. funguloids suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692622: marked as done (non-free files in upstream tarball (The Software shall be used for Good, not Evil))
Your message dated Tue, 13 Nov 2012 13:47:33 + with message-id e1tygpx-ew...@franck.debian.org and subject line Bug#692622: fixed in jmol 12.2.32+dfsg2-1 has caused the Debian Bug report #692622, regarding non-free files in upstream tarball (The Software shall be used for Good, not Evil) 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 692622: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692622 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: jmol Version: 12.2.32+dfsg-1 Severity: serious The upstream tarball contains files under the non-free JSON license: % rgrep -l 'The Software shall be used for Good, not Evil.' . ./debian/copyright ./src/com/json/CDL.java ./src/com/json/JSONStringer.java ./src/com/json/XMLTokener.java ./src/com/json/HTTPTokener.java ./src/com/json/JSONML.java ./src/com/json/JSONTokener.java ./src/com/json/HTTP.java ./src/com/json/JSONObject.java ./src/com/json/CookieList.java ./src/com/json/XML.java ./src/com/json/JSONWriter.java ./src/com/json/Cookie.java ./src/com/json/JSONArray.java Ansgar ---End Message--- ---BeginMessage--- Source: jmol Source-Version: 12.2.32+dfsg2-1 We believe that the bug you reported is fixed in the latest version of jmol, which is due to be installed in the Debian FTP archive. 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 692...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Banck mba...@debian.org (supplier of updated jmol 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 12 Nov 2012 14:14:02 +0100 Source: jmol Binary: jmol libjmol-java jmol-applet libjmol-java-doc Architecture: source all Version: 12.2.32+dfsg2-1 Distribution: unstable Urgency: low Maintainer: Michael Banck mba...@debian.org Changed-By: Michael Banck mba...@debian.org Description: jmol - Molecular Viewer jmol-applet - Jmol Java applet libjmol-java - Java library for molecular structures libjmol-java-doc - API documentation for libjmol-java Closes: 692622 Changes: jmol (12.2.32+dfsg2-1) unstable; urgency=low . * New repackaged upstream tarball, removing the src/com/json directory due to licensing issues (closes: #692622). * debian/patches/remove_json.patch: New patch, adapting the codebase to the removal of the src/com/json package, taken from upstream revision 17710. * debian/get-orig-source.sh: Remove src/com/json directory when repackaging. Checksums-Sha1: 65f321e035eaf444f274a2eb0957cae8c2466394 1693 jmol_12.2.32+dfsg2-1.dsc f91cc9a61766d486fd95d671cd8ffc5bad1d67ab 7523011 jmol_12.2.32+dfsg2.orig.tar.gz fdf4d7fb7a3294e026d4bd266ca9fb3271927162 15179 jmol_12.2.32+dfsg2-1.debian.tar.gz 5701b40e452589c25e64514d4c7e706753553be1 258708 jmol_12.2.32+dfsg2-1_all.deb 825066f1a39c6c61ff16c7c3cc30aa00918ac982 8307600 libjmol-java_12.2.32+dfsg2-1_all.deb 48064f5b8b2994677f82cd705931cc2692031f3a 4792722 jmol-applet_12.2.32+dfsg2-1_all.deb 56c284a7c82477233e3bcbe0f2d9b7d5b26771c8 3038576 libjmol-java-doc_12.2.32+dfsg2-1_all.deb Checksums-Sha256: 0b94819b22f99d704299661dddf2fd2eddc2b031b740543266a207590a83a339 1693 jmol_12.2.32+dfsg2-1.dsc 3e1207ad262b8240182d494e224c1dc8645650ff9f16661b6c68d846985cb875 7523011 jmol_12.2.32+dfsg2.orig.tar.gz da2f874ea05d7c106bef7ac73178537aceffb7881fe10247b370a00f5c630a08 15179 jmol_12.2.32+dfsg2-1.debian.tar.gz 789df91ce5cea45eb81a80385aa885dc57ceb024a2f933566787c71755ab334b 258708 jmol_12.2.32+dfsg2-1_all.deb a57ffeebd0be194fc53328c19dc0b6dd7ee065000318d315a6dc69072e38856a 8307600 libjmol-java_12.2.32+dfsg2-1_all.deb d76d0eb88363fc61e0a0328457ad91a2c56c01039dffe9a629367fe3937f8382 4792722 jmol-applet_12.2.32+dfsg2-1_all.deb 0d3afe54b9da3d3e6d8f38f3cec394bf8b37ceda2dc900b9e1a633df0a4d61e4 3038576 libjmol-java-doc_12.2.32+dfsg2-1_all.deb Files: 68dad3930338e24c466a5b9d03124194 1693 science optional jmol_12.2.32+dfsg2-1.dsc 857534304372c33c5f6c0551cb5c5bb9 7523011 science optional jmol_12.2.32+dfsg2.orig.tar.gz 45c6412a266b1722f08273b4b4719e23 15179 science optional jmol_12.2.32+dfsg2-1.debian.tar.gz bb48589a995b85218bc1fb17ec815342 258708 science optional jmol_12.2.32+dfsg2-1_all.deb 1326eb57486314c08f37424962f9436e
Bug#693134: funguloid: crashes on start with OGRE EXCEPTION
Am 13.11.2012 14:26, schrieb Armin Haas: Loading library /usr/lib/x86_64-linux-gnu/OGRE-1.7.4/RenderSystem_GL Indeed, this path is hard-coded in /usr/share/games/funguloids/plugins.cfg, which is in funguloids-data (arch:all). - Fabian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693138: debian reference claims wheezy is already stable
Package: www.debian.org Severity: grave Hi, http://www.debian.org/doc/manuals/debian-reference/ch02.en.html claims wheezy is the stable release. Please revert to the squeeze version until wheezy is released. We found out on IRC as a user stumbled over that page and installed wheezy instead of squeeze. Thanks, Martin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693134: funguloid: crashes on start with OGRE EXCEPTION
tags 693134 pending thanks Am 13.11.2012 14:58, schrieb Fabian Greffrath: Indeed, this path is hard-coded in /usr/share/games/funguloids/plugins.cfg, which is in funguloids-data (arch:all). Fixed in SVN, thanks for the bug report! - Fabian -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689493: src:youtube-dl: missing source for Windows binary
Hi Rogério, I haven't heard anything about this bug, and I'd be pretty sad to see wheezy released without youtube-dl, so I'm going to go ahead with the NMU in the next few days. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#693134: funguloid: crashes on start with OGRE EXCEPTION
Processing commands for cont...@bugs.debian.org: tags 693134 pending Bug #693134 [funguloids] funguloid: crashes on start with OGRE EXCEPTION Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 693134: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693134 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 693138 is normal
Processing commands for cont...@bugs.debian.org: severity 693138 normal Bug #693138 [www.debian.org] debian reference claims wheezy is already stable Severity set to 'normal' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 693138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690817: Request for upgrading drupal7 [backports] package
Hi, Laurent Bigonville wrote: It would be nice if the drupal7 package could be updated to 7.14-1.1. This revision is containing a security fix. Indeed. But then again, that's an NMU and the backports previously were from the same maintainer as the normal package. So maybe someone else than Luigi should care about the backport. Gunnar (who did the NMU for Sid/Wheezy) seems to be willing to also do the backport. Cc'ing him. Luigi, are you busy at the moment? I was used to quite prompt replies and in-time Drupal updates as well as in-time backports in the past, but I haven't seen any replies, etc. from you for a few months now. JFYI: The drupal7 backports seem to have been pure rebuilds in the past. So for those who are eager to get the security fixes as a .deb, the package from Wheezy is an option, even on Squeeze. Works fine for me on Squeeze (and did so before there were backports of drupal7). I though would be happy to see a proper backport (i.e. rebuild) nevertheless, e.g. for those who want the comfort of APT. :-) Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 signature.asc Description: Digital signature
Processed: severity of 693138 is grave
Processing commands for cont...@bugs.debian.org: #From the developer reference (...) causes data loss, or introduces a security hole (...) severity 693138 grave Bug #693138 [www.debian.org] debian reference claims wheezy is already stable Severity set to 'grave' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 693138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 693138 is grave
Processing commands for cont...@bugs.debian.org: #From the developer reference (...) causes data loss, or introduces a security hole (...) severity 693138 grave Bug #693138 [www.debian.org] debian reference claims wheezy is already stable Ignoring request to change severity of Bug 693138 to the same value. thanks Stopping processing here. Please contact me if you need assistance. -- 693138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 693138 is grave
Processing commands for cont...@bugs.debian.org: #From the developer reference (...) causes data loss, or introduces a security hole (...); Getting new users to install testing instead of stable can introduce security holes and/or data loss. I therefore think severity grave is appropriate. Yours Martin severity 693138 grave Bug #693138 [www.debian.org] debian reference claims wheezy is already stable Ignoring request to change severity of Bug 693138 to the same value. thanks Stopping processing here. Please contact me if you need assistance. -- 693138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693138: severity of 693138 is grave
On Tue, Nov 13, 2012 at 16:01:23 +0100, Martin Wuertele wrote: #From the developer reference (...) causes data loss, or introduces a security hole (...) severity 693138 grave The debian reference causes none of that. The debian web site neither. Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669382: latex209-base: unowned file /usr/local/share/texmf/ls-R after purge (policy 6.8, 9.1.2)
Hi Julien, hi all On Di, 13 Nov 2012, Julien Cristau wrote: If the release managers agree I will upload the NMU, but it does not make sense to upload a big NMU with lots of changes and then it is not going into wheezy. The release managers won't agree to anything without seeing what changes you're talking about. Sorry, I thought it is enough that the patch is in the bug report. Anyway, here attached the diff with the take over into Debian TeX Maint group (with agreement from the original maintainer, see debian-tex-maint@ mailing list). Please let me know what you think. Best wishes Norbert Norbert Preiningpreining@{jaist.ac.jp, logic.at, debian.org} JAIST, Japan TeX Live Debian Developer DSA: 0x09C5B094 fp: 14DF 2E6C 0307 BE6D AD76 A9C0 D2BF 4AA3 09C5 B094 CHIPPING ONGAR (n.) The disgust and embarrassment (or 'ongar') felt by an observer in the presence of a person festooned with kirbies (q.v.) when they don't know them well enough to tell them to wipe them off, invariably this 'ongar' is accompanied by an involuntary staccato twitching of the leg (or 'chipping') --- Douglas Adams, The Meaning of Liff diff --git a/debian/changelog b/debian/changelog index 27166da..96e510c 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,15 @@ +latex209 (25.mar.1992-13) unstable; urgency=low + + * Take over maintenance into the Debian TeX Group + * fix RC bug (Closes: #669382) (create files that are not removed) by: +- remove all maintainer scripts +- create the necessary code with dh_installtex +- add necessary build-dep on tex-common + * add latex209-bin.preinst to fix up old conffile so that debconf does +not ask unnecessary questions + + -- Norbert Preining prein...@debian.org Tue, 13 Nov 2012 14:50:17 +0900 + latex209 (25.mar.1992-12.5) unstable; urgency=low * Non-maintainer upload. diff --git a/debian/control b/debian/control index 58abf57..056ac89 100644 --- a/debian/control +++ b/debian/control @@ -1,10 +1,10 @@ Source: latex209 Section: tex Priority: optional -Maintainer: TSUCHIYA Masatoshi tsuch...@namazu.org -Build-Depends: debhelper ( 5.0.0) +Maintainer: Debian TeX maintainers debian-tex-ma...@lists.debian.org +Build-Depends: debhelper ( 5.0.0), tex-common (= 3) Standards-Version: 3.8.4 -Uploaders: Atsuhito Kohda ko...@debian.org +Uploaders: Atsuhito Kohda ko...@debian.org, Norbert Preining prein...@debian.org Package: latex209-base Architecture: all diff --git a/debian/copyright b/debian/copyright index 24811aa..308bddb 100644 --- a/debian/copyright +++ b/debian/copyright @@ -1,8 +1,8 @@ This package was debianized by Nakahara Hayao nakah...@mis.hiroshima-u.ac.jp for Debian JP Project on Sat, 29 Nov 1997 19:33:58 +0900. -Currently maintained by TSUCHIYA Masatoshi tsuch...@namazu.org, who -is sponsored by Masayuki Hatta mha...@debian.org. +Currently maintained by the Debian TeX Maintainer, +former maintainer was TSUCHIYA Masatoshi tsuch...@namazu.org. It was downloaded from ftp.riken.go.jp (one of CTAN sites). URL is ftp://ftp.riken.go.jp/pub/tex-archive/obsolete/macros/latex209/distribs/latex209.tar diff --git a/debian/latex209-base.postinst b/debian/latex209-base.postinst deleted file mode 100644 index 2f86fdf..000 --- a/debian/latex209-base.postinst +++ /dev/null @@ -1,44 +0,0 @@ -#! /bin/sh -# postinst script for latex209-base -# -# see: dh_installdeb(1) - -set -e - -# summary of how this script can be called: -#* postinst `configure' most-recently-configured-version -#* old-postinst `abort-upgrade' new version -#* conflictor's-postinst `abort-remove' `in-favour' package -# new-version -#* deconfigured's-postinst `abort-deconfigure' `in-favour' -# failed-install-package version `removing' -# conflicting-package version -# for details, see /usr/doc/packaging-manual/ -# -# quoting from the policy: -# Any necessary prompting should almost always be confined to the -# post-installation script, and should be protected with a conditional -# so that unnecessary prompting doesn't happen if a package's -# installation fails and the `postinst' is called with `abort-upgrade', -# `abort-remove' or `abort-deconfigure'. - -TEXMF=/usr/share/texmf - -case $1 in -configure) - mktexlsr $TEXMF - ;; -abort-upgrade|abort-remove|abort-deconfigure) - ;; -*) -echo postinst called with unknown argument \`$1' 2 -exit 0 - ;; -esac - -# dh_installdeb will replace this with shell code automatically -# generated by other debhelper scripts. - -#DEBHELPER# - -exit 0 diff --git a/debian/latex209-base.postrm b/debian/latex209-base.postrm deleted file mode 100644 index b394982..000 --- a/debian/latex209-base.postrm +++ /dev/null @@ -1,39 +0,0
Processed: tagging 692615
Processing commands for cont...@bugs.debian.org: tags 692615 + fixed-upstream Bug #692615 [src:transmission] transmission: non-free files in upstream tarball (The Software shall be used for Good, not Evil) Added tag(s) fixed-upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 692615: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692615 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693138: severity of 693138 is grave
* Julien Cristau jcris...@debian.org [2012-11-13 16:09]: On Tue, Nov 13, 2012 at 16:01:23 +0100, Martin Wuertele wrote: #From the developer reference (...) causes data loss, or introduces a security hole (...) severity 693138 grave The debian reference causes none of that. The debian web site neither. If the website points users to false information that at least is a serious issue. The Debian reference at should not point users to wheezy claiming it is already stable. Grave might be a bit harsh, however a severity of normal hides the actual problem in my opinion. Is it that much of a problem to have the Debian reference point to the ohne for squeeze as long as wheezy is not released? Yours Martin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692615: transmission: non-free files in upstream tarball (The Software shall be used for Good, not Evil)
Hi, This has been fixed upstream by replacing JSON_parser.* with jsonsl. The solution for wheezy depends on whether the release-team accepts such a potentially disruptive change. For more info, see: https://lists.debian.org/debian-release/2012/11/msg00531.html Cheers -- Leo costela Antunes [insert a witty retort here] -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: bug 692992 is forwarded to http://bugzilla.adiscon.com/show_bug.cgi?id=380
Processing commands for cont...@bugs.debian.org: forwarded 692992 http://bugzilla.adiscon.com/show_bug.cgi?id=380 Bug #692992 [src:rsyslog] FTBFS on kfreebsd-* Set Bug forwarded-to-address to 'http://bugzilla.adiscon.com/show_bug.cgi?id=380'. thanks Stopping processing here. Please contact me if you need assistance. -- 692992: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692992 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693138: severity of 693138 is grave
Control: reassign -1 debian-reference Le 13/11/2012 11:28, Martin Wuertele a écrit : * Julien Cristau jcris...@debian.org [2012-11-13 16:09]: On Tue, Nov 13, 2012 at 16:01:23 +0100, Martin Wuertele wrote: #From the developer reference (...) causes data loss, or introduces a security hole (...) severity 693138 grave The debian reference causes none of that. The debian web site neither. If the website points users to false information that at least is a serious issue. The Debian reference at should not point users to wheezy claiming it is already stable. Grave might be a bit harsh, however a severity of normal hides the actual problem in my opinion. Is it that much of a problem to have the Debian reference point to the ohne for squeeze as long as wheezy is not released? Yes it does, since the debian-reference package shipped in Wheezy should point accurately to Wheezy as stable. If the debian-reference maintainers wish to play the revert-revert-revert-revert game (à la tasksel), they could to do so until Wheezy is release, but that's up to them (and definitely not a grave issue in their package). If an upload of the package is needed and they forget to revert that change, that will be an issue, so I'm not sure it's worth changing it. Reassigning where it belongs in the mean time. Regards David signature.asc Description: OpenPGP digital signature
Processed: Re: Bug#693138: severity of 693138 is grave
Processing control commands: reassign -1 debian-reference Bug #693138 [www.debian.org] debian reference claims wheezy is already stable Bug reassigned from package 'www.debian.org' to 'debian-reference'. Ignoring request to alter found versions of bug #693138 to the same values previously set Ignoring request to alter fixed versions of bug #693138 to the same values previously set -- 693138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#652378: CVE-2011-1431 in TLS patch
On Fri, 16 Dec 2011 22:01:26 +0100, Moritz Muehlenhoff wrote: The source package embeds the qmail TLS patch, which is affected by this STARTTLS issue: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-1431 It appears as if the TLS patch isn't applied, it makes sense however to update the patch anyway. BTW, shouldn't this package be removed altogether now that netqmail is in the archive? Ansgar has filed an RM bug now: #692558 Cheers, gregor -- .''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06 : :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/ `. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe `- NP: Red Hot Chili Peppers: Road Trippin signature.asc Description: Digital signature
Bug#693138: marked as done (debian reference claims wheezy is already stable)
Your message dated Tue, 13 Nov 2012 12:33:02 -0400 with message-id 50a2763e.6030...@debian.org and subject line Re: Bug#693138: severity of 693138 is grave has caused the Debian Bug report #693138, regarding debian reference claims wheezy is already stable 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 693138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: www.debian.org Severity: grave Hi, http://www.debian.org/doc/manuals/debian-reference/ch02.en.html claims wheezy is the stable release. Please revert to the squeeze version until wheezy is released. We found out on IRC as a user stumbled over that page and installed wheezy instead of squeeze. Thanks, Martin ---End Message--- ---BeginMessage--- -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, 12:25 jcristau taffit: your debian-reference reassign makes no sense whatsoever afaict 12:26 jcristau if the website wants to use the stable debian-reference then it can do that. but the debian-reference package in wheezy should talk about wheezy... 12:28 taffit The Debian website wishes to display the most up to date debian-reference 12:28 jcristau then close the bug Agreed. Regards David -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJQonY9AAoJELgqIXr9/gnybvsP/j8/arE76EYtIRItwXc5OI4E ckqJ3LroPuqFjN9Q2twJW6CnupILQMrlmKEAX7Zzl8dk7f1MsWpq6D/V7sorVbNh X3YviTfG9bViQd5TfZWhrnCMjvYV8te+HQiipeUrcxu0YcS217vjVF6gFpTiwRhy nRxUjkneXjT6nPD9uPhVDYNfjqgaC6xVjZH47cGVWTqffHb4qs0mX/RbRyiCPUcM uoniM7r7feOWFt/DvqmQz67MXcfE0OxTgSRhLexpVAXyfA76w6EQ+1VSdjg7f4cE /Jdgcv72puWP4atc6UtPIQjDv8HfZddq5noxAw+W4hJ1fdxHZyMmUBtGAeZ86I1y Ki40++/ueNFYIh+HmlCgcr6dqfkeQyzeQ2aLBJnBY4Y0eXD+88DpIbd23xinyihO UHcYh1d0qrzTQpATuZJxaBOgT8s/IH57h6i7iFlO3E9/GG7peoxgPGeCMaoUHp1B ozW3gjGC5lzi8REe7TVJgggM5gp+KXE8BN/qKCIMdt+v6HCmt5zIo3MO+syz8SrX 5CDPwDS1O6NfOl6mor5cIAWg84U3efD8kOhjEqpe4ZGI0o6Ty+LpeLXyh7aNwaHW dcGnnq7HrmdMA7cywYuRkJ9dGwjASgVrnW0z57tiyUgAcXCXtmFR8PQcfpmV4sn8 hLoEz9U9UTiWPHbPNG/e =0PuU -END PGP SIGNATUREEnd Message---
Bug#693138: severity of 693138 is grave
* David Prévot taf...@debian.org [2012-11-13 17:22]: Le 13/11/2012 11:28, Martin Wuertele a écrit : (...) Is it that much of a problem to have the Debian reference point to the ohne for squeeze as long as wheezy is not released? Yes it does, since the debian-reference package shipped in Wheezy should point accurately to Wheezy as stable. If the debian-reference maintainers wish to play the revert-revert-revert-revert game (à la tasksel), they could to do so until Wheezy is release, but that's up to them (and definitely not a grave issue in their package). If an upload of the package is needed and they forget to revert that change, that will be an issue, so I'm not sure it's worth changing it. Reassigning where it belongs in the mean time. FTR: the bug is about what is shown on [1], not on the debian-reference package itself. Would it make sense to split it by release just as we do with the installation manual [2]? [1] http://www.debian.org/doc/manuals/debian-reference/ [2] http://www.debian.org/releases/stable/installmanual/ Yours Martin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693138: closed by David Prévot taf...@debian.org (Re: Bug#693138: severity of 693138 is grave)
12:25 jcristau taffit: your debian-reference reassign makes no sense whatsoever afaict 12:26 jcristau if the website wants to use the stable debian-reference then it can do that. but the debian-reference package in wheezy should talk about wheezy... 12:28 taffit The Debian website wishes to display the most up to date debian-reference 12:28 jcristau then close the bug Agreed. Looks more like wontfix than closed to me. Your Martin -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693147: ttytter: Package breaks against Twitter API 1.1
Subject: ttytter: Package breaks against Twitter API 1.1 Package: ttytter Version: 2.0.1-1 Justification: renders package unusable Severity: grave Dear Maintainer, As of 4 October 2012, this version will no longer function properly against Twitter API 1.1 and unanticipted errors are expected to arise over time as Twitter further adjusts their API. A new version that is more API-compliant has not yet been released but is currently in beta. See: http://www.floodgap.com/software/ttytter/beta/ for more information. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: armel (armv5tel) Kernel: Linux 3.2.0-3-kirkwood Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ttytter depends on: ii curl 7.26.0-1 ii lynx 2.8.8dev.12-2 ii perl 5.14.2-14 Versions of packages ttytter recommends: ii libterm-readline-gnu-perl 1.20-2+b1 ii libtimedate-perl 1.2000-1 ttytter suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685540: asterisk-flite, asterisk-espeak: binnmu required
Indeed this is fixable through a binNMU. Sorry for missing this earlier, Jonas. Original ones were built against versions 1.8. Sanity check: after module is built, install it and asterisk on a system (or copy /usr/lib/asterisk/modules/app_flite.so to the test system), and run: asterisk -rx 'module load app_flite.so' # Should give no error, except one about missing config file asterisk -rnx 'core show application Flite' # Should give a help text and not an error For eSpeak: asterisk -rx 'module load app_espeak.so' # Should give no error, except one about missing config file asterisk -rnx 'core show application eSpeak' # Should give a help text and not an error -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692620: marked as done (non-free files in upstream tarball (The Software shall be used for Good, not Evil))
Your message dated Tue, 13 Nov 2012 18:32:25 + with message-id e1tylhd-yy...@franck.debian.org and subject line Bug#692620: fixed in josm-plugins 0.0.svn28420+ds2-1 has caused the Debian Bug report #692620, regarding non-free files in upstream tarball (The Software shall be used for Good, not Evil) 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 692620: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692620 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: josm-plugins Version: 0.0.svn28420+ds1-1 Severity: serious The upstream tarball contains files under the non-free JSON license: % rgrep -l 'The Software shall be used for Good, not Evil.' . ./livegps/src/org/json/JSONArray.java ./livegps/src/org/json/JSONTokener.java ./livegps/src/org/json/JSONObject.java Ansgar ---End Message--- ---BeginMessage--- Source: josm-plugins Source-Version: 0.0.svn28420+ds2-1 We believe that the bug you reported is fixed in the latest version of josm-plugins, which is due to be installed in the Debian FTP archive. 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 692...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Paleino da...@debian.org (supplier of updated josm-plugins 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 13 Nov 2012 19:18:28 +0100 Source: josm-plugins Binary: josm-plugins Architecture: source all Version: 0.0.svn28420+ds2-1 Distribution: testing Urgency: low Maintainer: Debian OpenStreetMap Team pkg-osm-ma...@lists.alioth.debian.org Changed-By: David Paleino da...@debian.org Description: josm-plugins - Plugins for JOSM Closes: 692620 Changes: josm-plugins (0.0.svn28420+ds2-1) testing; urgency=low . * New repacked tarball: remove livegps from downloaded plugins, since it contains files under the non-free JSON license. Also disabled plugin surveyor, which depends on livegps. (Closes: #692620) Checksums-Sha1: 498b23aacbeb647c1b48756a3cf66ac092b8fc2e 1713 josm-plugins_0.0.svn28420+ds2-1.dsc 3a71e1b69ccb35e70491285608d6fed75ccc7cd6 348372 josm-plugins_0.0.svn28420+ds2.orig.tar.gz 71c9482ec844a247f43bacd46a3a05ce0c919cad 10481 josm-plugins_0.0.svn28420+ds2-1.debian.tar.gz ba39ec12882ce3ece872aa1dfe88da1af932e200 347320 josm-plugins_0.0.svn28420+ds2-1_all.deb Checksums-Sha256: 976368dbe0df7b882a1cbf26c44965886db2ac8b1ddc91c727bf6f343e888a2f 1713 josm-plugins_0.0.svn28420+ds2-1.dsc a9282d18062f42c2a24ea8110663c9ff0553002ae21bf1b1adaf2589c1e46c75 348372 josm-plugins_0.0.svn28420+ds2.orig.tar.gz 963f9c6b707bf4dd8889842f70ebc61161e1c77db8382012f6b8c06292ba4829 10481 josm-plugins_0.0.svn28420+ds2-1.debian.tar.gz dd8b4dbec135ead54eac7b1114c7e5d71334c40c301850829a8c2c9599ae488c 347320 josm-plugins_0.0.svn28420+ds2-1_all.deb Files: ac32464dc736b21de8e3500318cfc963 1713 utils extra josm-plugins_0.0.svn28420+ds2-1.dsc 22a39dcaa7171791c925ecb5c6944557 348372 utils extra josm-plugins_0.0.svn28420+ds2.orig.tar.gz 01aa1e5eb8a33d0c706ed505952b59c8 10481 utils extra josm-plugins_0.0.svn28420+ds2-1.debian.tar.gz 379655c42d9009512d6d1acb240d7dca 347320 utils extra josm-plugins_0.0.svn28420+ds2-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlCikGQACgkQ5qqQFxOSsXSOoQCfWr2iC5ERSufuCVkm8RXZPK6B +tgAnA9Bm5YfpUVjvGx17Qn7hupUNc3+ =idlc -END PGP SIGNATUREEnd Message---
Bug#660736: Subject: icedove deads on undefined symbol
Hello Niklaus, Am 12.11.2012 23:57, schrieb Niklaus: nm -D /usr/lib/icedove/libxpcom.so | grep NS_GetServiceManager reports this: 26f8 T NS_GetServiceManager U NS_GetServiceManager_P So far as I understand this, it's indeed an undefined symbol. Hm, helpfull? Yes, I wanted to that is there. :) I forced a new installation of the icedove-package, but even LD_PRELOAD=/usr/lib/icedove/libxpcom_core.so icedove produces the old error: /usr/lib/icedove/icedove-bin: symbol lookup error: /usr/lib/icedove/components/libimgicon.so: undefined symbol: NS_GetServiceManager O.K. the package seem so be not corrupted, as the error did happen with the reinstall too. :/ So far, so bad. NS_GetServiceManager seems to bee a part of the GNUstep-Package, wich I have installed just by curiousity. Maybe that are Symbols named to like NS_*, but thats are not symbols needed by icedove. It is not realy usable and buggy like hell, but nevertheless very intresting because you can see the roots of todays Macintosh-Desktops! Don't tell me, that I must remove this whole stuff... ;-) Looks strange for me, that icedove is interferring in some way with these very special GNUstep libraries. No, icedove doesn't need this. carsten@x201s:/usr/lib/icedove $ ldd icedove-bin linux-vdso.so.1 = (0x7fff4a9bd000) libxul.so = not found libxpcom_core.so = not found libpthread.so.0 = /lib/libpthread.so.0 (0x7fbd3f918000) libc.so.6 = /lib/libc.so.6 (0x7fbd3f5b6000) /lib64/ld-linux-x86-64.so.2 (0x7fbd3fb53000 carsten@x201s:/usr/lib/icedove $ ldd libxpcom_core.so linux-vdso.so.1 = (0x717ff000) libplds4.so.0d = /usr/lib/libplds4.so.0d (0x7f2f76521000) libplc4.so.0d = /usr/lib/libplc4.so.0d (0x7f2f7631d000) libnspr4.so.0d = /usr/lib/libnspr4.so.0d (0x7f2f760de000) libpthread.so.0 = /lib/libpthread.so.0 (0x7f2f75ec2000) libdl.so.2 = /lib/libdl.so.2 (0x7f2f75cbe000) libgtk-x11-2.0.so.0 = /usr/lib/libgtk-x11-2.0.so.0 (0x7f2f7569c000) libm.so.6 = /lib/libm.so.6 (0x7f2f7541a000) libstdc++.so.6 = /usr/lib/libstdc++.so.6 (0x7f2f75106000) libgcc_s.so.1 = /lib/libgcc_s.so.1 (0x7f2f74eef000) libc.so.6 = /lib/libc.so.6 (0x7f2f74b8d000) /lib64/ld-linux-x86-64.so.2 (0x7f2f769fb000) libgdk_pixbuf-2.0.so.0 = /usr/lib/libgdk_pixbuf-2.0.so.0 (0x7f2f74971000) libgdk-x11-2.0.so.0 = /usr/lib/libgdk-x11-2.0.so.0 (0x7f2f746c3000) libpangocairo-1.0.so.0 = /usr/lib/libpangocairo-1.0.so.0 (0x7f2f744b7000) libX11.so.6 = /usr/lib/libX11.so.6 (0x7f2f7417c000) libXcomposite.so.1 = /usr/lib/libXcomposite.so.1 (0x7f2f73f79000) libXdamage.so.1 = /usr/lib/libXdamage.so.1 (0x7f2f73d77000) libXfixes.so.3 = /usr/lib/libXfixes.so.3 (0x7f2f73b72000) libatk-1.0.so.0 = /usr/lib/libatk-1.0.so.0 (0x7f2f7395) libcairo.so.2 = /usr/lib/libcairo.so.2 (0x7f2f73692000) libgio-2.0.so.0 = /usr/lib/libgio-2.0.so.0 (0x7f2f733e) libpangoft2-1.0.so.0 = /usr/lib/libpangoft2-1.0.so.0 (0x7f2f731b5000) libpango-1.0.so.0 = /usr/lib/libpango-1.0.so.0 (0x7f2f72f69000) libfreetype.so.6 = /usr/lib/libfreetype.so.6 (0x7f2f72ce1000) libfontconfig.so.1 = /usr/lib/libfontconfig.so.1 (0x7f2f72aab000) libgobject-2.0.so.0 = /usr/lib/libgobject-2.0.so.0 (0x7f2f72864000) libgmodule-2.0.so.0 = /usr/lib/libgmodule-2.0.so.0 (0x7f2f72661000) libgthread-2.0.so.0 = /usr/lib/libgthread-2.0.so.0 (0x7f2f7245c000) librt.so.1 = /lib/librt.so.1 (0x7f2f72254000) libglib-2.0.so.0 = /lib/libglib-2.0.so.0 (0x7f2f71f78000) libXext.so.6 = /usr/lib/libXext.so.6 (0x7f2f71d65000) libXrender.so.1 = /usr/lib/libXrender.so.1 (0x7f2f71b5b000) libXinerama.so.1 = /usr/lib/libXinerama.so.1 (0x7f2f71959000) libXi.so.6 = /usr/lib/libXi.so.6 (0x7f2f71749000) libXrandr.so.2 = /usr/lib/libXrandr.so.2 (0x7f2f71541000) libXcursor.so.1 = /usr/lib/libXcursor.so.1 (0x7f2f71337000) libz.so.1 = /usr/lib/libz.so.1 (0x7f2f7111f000) libxcb.so.1 = /usr/lib/libxcb.so.1 (0x7f2f70f03000) libpixman-1.so.0 = /usr/lib/libpixman-1.so.0 (0x7f2f70c7b000) libpng12.so.0 = /lib/libpng12.so.0 (0x7f2f70a55000) libxcb-shm.so.0 = /usr/lib/libxcb-shm.so.0 (0x7f2f70853000) libxcb-render.so.0 = /usr/lib/libxcb-render.so.0 (0x7f2f7064a000) libpcre.so.3 = /lib/libpcre.so.3 (0x7f2f7041a000) libresolv.so.2 = /lib/libresolv.so.2 (0x7f2f70204000) libselinux.so.1 = /lib/libselinux.so.1 (0x7f2f6ffe5000) libexpat.so.1 = /usr/lib/libexpat.so.1
Bug#687335: Support armhf and s390x in the security archive
Raphael Geissert geiss...@debian.org writes: This is just to keep a record of things that need to be done before the release: * Add support for the armhf architecture to the security archive * Add support for the s390x architecture to the security archive I added the new architectures to the archive. * Work with the buildd people to give them access to sec's incoming That's not done yet. Ansgar -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 693158 is grave
Processing commands for cont...@bugs.debian.org: severity 693158 grave Bug #693158 [xserver-xorg-input-penmount] Xorg: symbol lookup error: ...penmount_drv.so: undefined symbol: xf86XInputSetScreen Severity set to 'grave' from 'important' thanks Stopping processing here. Please contact me if you need assistance. -- 693158: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693158 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693158: Xorg: symbol lookup error: ...penmount_drv.so: undefined symbol: xf86XInputSetScreen
On Tue, Nov 13, 2012 at 20:05:18 +0100, Guenter Bartsch wrote: Package: xserver-xorg-input-penmount Version: 1:1.5.0-1+b2 Severity: important Dear Maintainer, penmount driver will crash the Xorg server on every touch attempt because it seems to use outdated API functions: Xorg: symbol lookup error: /usr/lib/xorg/modules/input/penmount_drv.so: undefined symbol: xf86XInputSetScreen the attached patch fixes it (at the expense of probably losing multiple screen support, but at least for single-screen setups the package remains useful and stable). Thanks for the patch. Out of interest, does using inputattach (from the package of the same name; see /usr/share/doc/inputattach/README.Debian for setup instructions) work with your device? (That should use the standard xserver-xorg-input-evdev driver, which contrary to xserver-xorg-input-penmount is still being maintained.) Cheers, Julien signature.asc Description: Digital signature
Bug#692534: Fails to build sqldeveloper package with chmod: missing operand after `755'
On Mon, Nov 12, 2012 at 5:09 PM, Salvatore Bonaccorso car...@debian.org wrote: Hi Steven On Wed, Nov 07, 2012 at 10:48:15AM +0100, Steven Post wrote: Package: sqldeveloper-package Version: 0.2.3+nmu1 Severity: grave Dear maintainer, The command make-sql-developer fails to build the sqldeveloper package with a rather unhelpful message. Terminal output: $ make-sqldeveloper-package -b sqldeveloper sqldeveloper-3.2.20.09.87-no-jre.zip chmod: missing operand after `755' Try `chmod --help' for more information. Omitting the -b parameter has no effect on the output. As you migth have seen, I uploaded a NMU to a delayed queue. You can test the package in [1] if you like. [1]: http://ftp-master.debian.org/deferred/ Hi: I've uploaded to mentors.debian.net https://mentors.debian.net/package/sqldeveloper-package version 0.3.0, that addresses this issue (along all other bugs reported both on Debian and on Ubuntu). I'm not quite sure how will the package be moved to ftp-master (last time one of the Developers offered to move it). Thank you for all the feedback and regards, -- Lazarus -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660736: Subject: icedove deads on undefined symbol
LD_BIND_NOW works for me. After this icedove starts normally again without LD_BIND_NOW. After upgrade, I had to call icedove with LD_BIN_NOW again. question is... why is icedove only the one application on my system having this problem. The problem seems to depend on the libc6. There are similarly problems on Bug #659994 with this, that's why Christoph has merged the bugs. Please try if icedove is startable by LD_BIND_NOW=1 icedove And check if the install of an older libc will also be a opinion. Please look into #659994 and also into #617759 (please take time). Regards Carsten -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660736: Subject: icedove deads on undefined symbol
On 11/13/2012 08:29 PM, Miloslav Semler wrote: LD_BIND_NOW works for me. After this icedove starts normally again without LD_BIND_NOW. After upgrade, I had to call icedove with LD_BIN_NOW again. question is... why is icedove only the one application on my system having this problem. The problem seems to depend on the libc6. There are similarly problems on Bug #659994 with this, that's why Christoph has merged the bugs. Please try if icedove is startable by LD_BIND_NOW=1 icedove And check if the install of an older libc will also be a opinion. Please look into #659994 and also into #617759 (please take time). Regards Carsten Hello all! Success! I can confirm what Miloslav wrote: After starting icedove _once_ with LD_BIND_NOW=1 it starts up agin regulary without this prefix. Now it's all OK with me, but I'm not sure, if the bug is realy solved. Keep in mind, that I have set my apt policy to stable, and things like this should not happen there, I'm right? Have a nice day, my regards, Niklaus -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: severity of 693087 is critical
Processing commands for cont...@bugs.debian.org: severity 693087 critical Bug #693087 [libpam-rsa] segfault in xscreensaver, screen revealed Severity set to 'critical' from 'normal' thanks Stopping processing here. Please contact me if you need assistance. -- 693087: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693087 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693147: The package ttytter
On Tue, 2012-11-13 at 15:35 -0500, Stephen Michael Kellat wrote: It was suggested to me that I contact the Debian Release Team about this package. I filed a grave bug on it and ask that it be pulled from Wheezy. You filed that bug approximately four hours ago afaics; generally one would give the maintainer time to respond before invoking the release team. CCing the bug so we can try and avoid having two divergent streams of discussion. Regards, Adam -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692534: Fails to build sqldeveloper package with chmod: missing operand after `755'
Hi Lazarus On Tue, Nov 13, 2012 at 07:37:11PM +, Lazarus Long wrote: On Mon, Nov 12, 2012 at 5:09 PM, Salvatore Bonaccorso car...@debian.org wrote: Hi Steven On Wed, Nov 07, 2012 at 10:48:15AM +0100, Steven Post wrote: Package: sqldeveloper-package Version: 0.2.3+nmu1 Severity: grave Dear maintainer, The command make-sql-developer fails to build the sqldeveloper package with a rather unhelpful message. Terminal output: $ make-sqldeveloper-package -b sqldeveloper sqldeveloper-3.2.20.09.87-no-jre.zip chmod: missing operand after `755' Try `chmod --help' for more information. Omitting the -b parameter has no effect on the output. As you migth have seen, I uploaded a NMU to a delayed queue. You can test the package in [1] if you like. [1]: http://ftp-master.debian.org/deferred/ Hi: I've uploaded to mentors.debian.net https://mentors.debian.net/package/sqldeveloper-package version 0.3.0, that addresses this issue (along all other bugs reported both on Debian and on Ubuntu). I'm not quite sure how will the package be moved to ftp-master (last time one of the Developers offered to move it). Thank you for all the feedback and regards, Thanks for your reply! Should I cancel my NMU from the delayed queue? But please note, the debdiff between 0.2.3+nmu1 and 0.3.0 looks quite big. If you plan an upload (and need sponsoring) could you have a look at [1] for the wheezy freeze_policy? At this stage of the freeze only some important issues, and clearly RC bugs should be addressed to have the package in wheezy; so it might be to late for some of the addressed issues. [1]: http://release.debian.org/wheezy/freeze_policy.html Please let me know if you have some questions. Regards, Salvatore signature.asc Description: Digital signature
Processed: Add no-await trigger support and Breaks to fix ca-certificates-java breakage
Processing control commands: tag -1 patch Bug #537051 [ca-certificates] ca-certificates 20090709: installation error Added tag(s) patch. -- 537051: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=537051 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#537051: Add no-await trigger support and Breaks to fix ca-certificates-java breakage
Control: tag -1 patch Please find the attached patches which fix this problem. I've tested them a bit, but please review them. ca-certificates (20121112+nmu1) unstable; urgency=low * Non-maintainer upload * Breaks ca-certificates-java (20121112+nmu1); partially fixing #537051. * Provide update-ca-certificates and update-ca-certificates-fresh triggers. * Call the triggers using no-await so that the configuration files from the newer version of ca-certificates-java are in places before the upgrade. Closes: #537051. ca-certificates-java (20121112+nmu1) unstable; urgency=low * Non-maintainer upload * Fix test for dpkg-query in postinst; there was an extraneous --version here. [Probably don't even need to bother to check for dpkg-query, but why not.] (Closes: #690204) * Library path for softokn3pkg and nsspkg is potentially wrong if there are multiple different paths; fix it. * Do not run the hook if ca-certificates-java has been removed but not purged. * Use the new trigger support provided by ca-certificates (=20121112). -- Don Armstrong d...@debian.org Mon, 12 Nov 2012 15:45:50 -0800 I plan on uploading an NMU for ca-certificates-java as soon as I have an ACK from the ca-certificates team that the fix looks reasonable (unless I hear from ca-certificates-java that they want to do it.) [I can also upload a fixed ca-certificates and pull my changes into ca-certificates unless y'all want to handle that.] Don Armstrong -- THERE IS NO GRAVITY THE WORLD SUCKS -- Vietnam War Penquin Lighter http://gallery.donarmstrong.com/clippings/vietnam_there_is_no_gravity.jpg http://www.donarmstrong.com http://rzlab.ucr.edu From 7731133fe1266d1722cad212fd8750ca5e324c58 Mon Sep 17 00:00:00 2001 From: Don Armstrong d...@debian.org Date: Tue, 13 Nov 2012 13:04:01 -0800 Subject: [PATCH 2/2] * Breaks ca-certificates-java (20121112+nmu1); partially fixing #537051. * Provide update-ca-certificates and update-ca-certificates-fresh triggers. * Call the triggers using no-await so that the configuration files from the newer version of ca-certificates-java are in places before the upgrade. Closes: #537051. --- debian/ca-certificates.triggers |4 debian/changelog| 12 debian/control |2 ++ debian/postinst | 21 +++-- 4 files changed, 37 insertions(+), 2 deletions(-) create mode 100644 debian/ca-certificates.triggers diff --git a/debian/ca-certificates.triggers b/debian/ca-certificates.triggers new file mode 100644 index 000..14dec6e --- /dev/null +++ b/debian/ca-certificates.triggers @@ -0,0 +1,4 @@ +interest-noawait update-ca-certificates +interest-noawait update-ca-certificates-fresh +interest update-ca-certificates +interest update-ca-certificates-fresh diff --git a/debian/changelog b/debian/changelog index 861abed..a59fed5 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,15 @@ +ca-certificates (20121112+nmu1) unstable; urgency=low + + * Non-maintainer upload + * Breaks ca-certificates-java (20121112+nmu1); partially fixing #537051. + * Provide update-ca-certificates and update-ca-certificates-fresh +triggers. + * Call the triggers using no-await so that the configuration files from +the newer version of ca-certificates-java are in places before the +upgrade. Closes: #537051. + + -- Don Armstrong d...@debian.org Mon, 12 Nov 2012 15:58:11 -0800 + ca-certificates (20121105) unstable; urgency=low * Update mozilla/certdata.txt to version 1.86 Closes: #683728 diff --git a/debian/control b/debian/control index 5ef776e..8f84573 100644 --- a/debian/control +++ b/debian/control @@ -13,9 +13,11 @@ Vcs-Browser: http://git.debian.org/?p=collab-maint/ca-certificates.git Package: ca-certificates Architecture: all +Pre-Depends: dpkg (= 1.16.1) Depends: openssl (= 1.0.0), ${misc:Depends} Enhances: openssl Multi-Arch: foreign +Breaks: ca-certificates-java (20121112+nmu1) Description: Common CA certificates This package includes PEM files of CA certificates to allow SSL-based applications to check for the authenticity of SSL connections. diff --git a/debian/postinst b/debian/postinst index 198c57e..9964e27 100644 --- a/debian/postinst +++ b/debian/postinst @@ -142,12 +142,29 @@ EOF # fix bogus symlink to ca-certificates.crt on upgrades; see # Debian #643667; drop after wheezy if dpkg --compare-versions $2 lt-nl 20111025; then - update-ca-certificates --fresh + dpkg-trigger --no-await update-ca-certificates-fresh else - update-ca-certificates + dpkg-trigger --no-await update-ca-certificates fi ;; +triggered) + for trigger in $2; do + case $trigger in + update-ca-certificates) + update-ca-certificates + ;; + update-ca-certificates-fresh) + update-ca-certificates --fresh + ;; + *) + echo postinst called with unknown trigger \`$2'2 + exit 1 + ;;
Processed: Add no-await trigger support and Breaks to fix ca-certificates-java breakage
Processing control commands: tag -1 patch Bug #690204 [ca-certificates-java] ca-certificates{, -java}: many errors during squeeze-wheezy upgrades, probably related to configuration order and update.d/ Added tag(s) patch. -- 690204: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690204 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#685251: Fixing Debian bug #685251 for the ryu plugin in Openstack
Hi Thomas and Julien The 2012.1-6 upload was done before the freeze and the plan was to have it included in testing before the freeze. Apparently that did not happen. I was under the impression that the freeze would be to uploads after the freeze, not to the packages that had not yet done the transition. Apparently I was wrong, and if that have cause this problem, I'm sorry for that. We did not have any bug report about the issues for that change. Instead I did those changes in order to solve problems that were similar to issues in other packages. It was more of a cleanup work in order to avoid bug reports in the future. We did have issues with the conflicts, replaces, breaks in other packages and if I remember correctly they were important also for this package. It is some time since I did this so I do not remember all the details. I think the 2012.1-6 upload was a good thing for the package, especially for upgrade from earlier versions. That is however not such a big problem for this release as it has not been part of stable before. It may be an issue for later releases though. From a release team perspective I understand that you do not want large last minute changes to packages. I can not motivate the change to be that strong to be forced in. If you want I can make a proposed patch based on the changes Thomas made for 2012.1-7 and void the changes for 2012.1-6. I do however think the changes done in 2012.1-6 was good and we should have them in for next release (after the one that is frozen now). This means that I do not think we should revert them for next release, but I do not have a big problem to do it for testing. I hope this clarifies the situation a bit. Cheers, // Ola tis 2012-11-13 klockan 20:16 +0800 skrev Thomas Goirand: On 11/13/2012 07:08 PM, Julien Cristau wrote: On Fri, Nov 9, 2012 at 05:03:58 +0800, Thomas Goirand wrote: Please let me know if the attached patch would be accepted by the release team and avoid Quantum to be removed. Sigh. If you want to be sure it'll be accepted then just upload the minimal fix for the RC bug and leave it at that (2012.1-6 doesn't seem to list a bug number, so without more explanations it doesn't qualify). As I wrote, these changes were not mine. I don't think it's appropriate to write sigh or to be pissed *at me*. The only thing I did was working on the issue the release team cared about, and fixing it, I'm not responsible for the other changes, and I don't intend to assume responsibility for them regarding the unblock. It wasn't nice that these changes were uploaded without caring about the SID to Wheezy migration. Numerous times, I wrote about it to both Ola and Loic. I'm not surprised about the resulting conversation with the release team. But since that's not my work, and that I would like to respect what the others do, I still want to leave them the job to answer about it. So please, Ola and Loic, explain and deal with the release team. If you guys think the changes are necessary, tell why. If you think they should be removed, please do the necessary git revert (or at the very least, let me know that you would agree if I was to do it). And finally, I hope this is a lesson and that it wont happen again, and that you will bare with me and the rest of the PKG Openstack team. I'm not going to review every single one of your uploads 5 times. You don't have to, you can accept it the first time! :) Thomas -- --- Inguza Technology AB --- MSc in Information Technology / o...@inguza.comAnnebergsslingan 37\ | o...@debian.org 654 65 KARLSTAD| | http://inguza.com/Mobile: +46 (0)70-332 1551 | \ gpg/f.p.: 7090 A92B 18FE 7994 0C36 4FE4 18A1 B1CF 0FE5 3DD9 / --- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689012: Bug #689012: chrony: Refuses to start: Fatal error : Cannot read information from uname
Hello, I have seen that this bug have changed to grave. Please can you try the attached patch? It solves bug #691340 and #642209 for chrony 1.24-3.1 and should also solve this bug. I am working out an update of the wheezy package in the next days. --- Have a nice day. Joachim (Germany) diff -Nru chrony-1.24.orig/rtc_linux.c chrony-1.24/rtc_linux.c --- chrony-1.24.orig/rtc_linux.c +++ chrony-1.24/rtc_linux.c @@ -541,9 +541,13 @@ int RTC_Linux_Initialise(void) { - int major, minor, patch; char *direc; + /* All kernel versions since 2.2.x have RTC support. */ + /* This test is obsolete for some years (see chrony 1.26). */ +#if 0 + int major, minor, patch; + /* Check whether we can support the real time clock. Linux 1.2.x - haven't checked yet @@ -597,6 +601,7 @@ break; /* OK for all patch levels */ } } +#endif /* Setup details depending on configuration options */ setup_config();
Bug#690199: marked as done (ogre-1.8: incomplete debian/copyright)
Your message dated Tue, 13 Nov 2012 21:47:57 + with message-id e1tyokr-0007ho...@franck.debian.org and subject line Bug#690199: fixed in ogre-1.8 1.8.0+dfsg1-3 has caused the Debian Bug report #690199, regarding ogre-1.8: incomplete debian/copyright 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 690199: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690199 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ogre-1.8 Severity: serious Version: 1.7.4-5 On Wed, Oct 10, 2012 at 10:32:45PM +0100, Manuel A. Fernandez Montecelo wrote: Hello, I need permissions to upload from now on the packages from this team that I maintain since several years ago (ogre and ogre-1.8) ... If somebody could do this, I would be thankful. Hi Manuel, You ask to renew your upload permissions, but debian/copyright in ogre-1.8 is not complete, see for example Copyright 1998-2002 by Neil Hodgson in Tools/MaterialEditor/wxscintilla_1.69.2/src/scintilla/src/LexPython.cxx. Regards, Bart Martens ---End Message--- ---BeginMessage--- Source: ogre-1.8 Source-Version: 1.8.0+dfsg1-3 We believe that the bug you reported is fixed in the latest version of ogre-1.8, which is due to be installed in the Debian FTP archive. 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 690...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Manuel A. Fernandez Montecelo manuel.montez...@gmail.com (supplier of updated ogre-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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 13 Nov 2012 20:02:38 + Source: ogre-1.8 Binary: libogre-1.8-dev libogre-1.8.0 libogre-1.8.0-dbg ogre-1.8-doc ogre-1.8-tools blender-ogrexml-1.8 Architecture: source amd64 all Version: 1.8.0+dfsg1-3 Distribution: unstable Urgency: low Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Changed-By: Manuel A. Fernandez Montecelo manuel.montez...@gmail.com Description: blender-ogrexml-1.8 - Blender Exporter for OGRE libogre-1.8-dev - 3D Object-Oriented Graphics Rendering Engine (development files) libogre-1.8.0 - 3D Object-Oriented Graphics Rendering Engine (libraries) libogre-1.8.0-dbg - 3D Object-Oriented Graphics Rendering Engine (debugging libs) ogre-1.8-doc - 3D Object-Oriented Graphics Rendering Engine (documentation) ogre-1.8-tools - 3D Object-Oriented Graphics Rendering Engine (tools) Closes: 690199 Changes: ogre-1.8 (1.8.0+dfsg1-3) unstable; urgency=low . * Document some files oversought in debian/copyright (Closes: #690199). Thanks Bart Martens and Anton Gladky for reporting and collaborating in fixing the problem. Checksums-Sha1: ce5d6768f0217ab569b563decd3990636c7b773a 2595 ogre-1.8_1.8.0+dfsg1-3.dsc 6b36722da9c988b1ac0d1b49e5f00c450b73cc82 26650 ogre-1.8_1.8.0+dfsg1-3.debian.tar.gz 4823edf9d0536da2a754929e1b25580e4cbf13ef 1230428 libogre-1.8-dev_1.8.0+dfsg1-3_amd64.deb a30ef777ea1d2832e246fa773e7a81f762a21089 3472920 libogre-1.8.0_1.8.0+dfsg1-3_amd64.deb cd5dc15d51cdcfb5a92ace5bb695c7e5ec47cb2b 57540722 libogre-1.8.0-dbg_1.8.0+dfsg1-3_amd64.deb a3997dfba9379f99593ac6055102c54db6e623f8 32601092 ogre-1.8-doc_1.8.0+dfsg1-3_all.deb d9378a3a26623f38753f0a46967d03fd70470e94 227108 ogre-1.8-tools_1.8.0+dfsg1-3_amd64.deb 2288298db2ba616549283636ec46b33d32abbc10 195686 blender-ogrexml-1.8_1.8.0+dfsg1-3_all.deb Checksums-Sha256: 51499225e98a9782c3981c2f8dc0d6528b9b59682fc99101fe85a0a7d34ae385 2595 ogre-1.8_1.8.0+dfsg1-3.dsc 8b632c39f976659f69aae9855ea3815f923b2e057818681a675385fd241f2323 26650 ogre-1.8_1.8.0+dfsg1-3.debian.tar.gz 18163adef6dc889ca7ff1f11d023b2d0f6b065fc15af53e753ad7022ea6a 1230428 libogre-1.8-dev_1.8.0+dfsg1-3_amd64.deb fb58d5297b4b4b10a484f6cec737491fd0580a90cb74ee0b8b31649eb36bc873 3472920 libogre-1.8.0_1.8.0+dfsg1-3_amd64.deb ef9f449d5e8746c266e313de3371f1dcdbd84376957bb6119f195d3c226a6a16 57540722 libogre-1.8.0-dbg_1.8.0+dfsg1-3_amd64.deb b9e678976be70cdf049169add9411381ab4fdbfc7cb0934fa742839a1c7e9790 32601092 ogre-1.8-doc_1.8.0+dfsg1-3_all.deb 533436f95e91e962702ff0891ed862c67e2c342333061260dbde68cae0d0 227108 ogre-1.8-tools_1.8.0+dfsg1-3_amd64.deb bdecdd14589f541ca6cae0d9c4fc62914849331b475abc9fa651fdc43ac11945 195686
Bug#692620: marked as done (non-free files in upstream tarball (The Software shall be used for Good, not Evil))
Your message dated Tue, 13 Nov 2012 22:17:28 + with message-id e1tyonq-0004ed...@franck.debian.org and subject line Bug#692620: fixed in josm-plugins 0.0.svn28937+ds1-1 has caused the Debian Bug report #692620, regarding non-free files in upstream tarball (The Software shall be used for Good, not Evil) 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 692620: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692620 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: josm-plugins Version: 0.0.svn28420+ds1-1 Severity: serious The upstream tarball contains files under the non-free JSON license: % rgrep -l 'The Software shall be used for Good, not Evil.' . ./livegps/src/org/json/JSONArray.java ./livegps/src/org/json/JSONTokener.java ./livegps/src/org/json/JSONObject.java Ansgar ---End Message--- ---BeginMessage--- Source: josm-plugins Source-Version: 0.0.svn28937+ds1-1 We believe that the bug you reported is fixed in the latest version of josm-plugins, which is due to be installed in the Debian FTP archive. 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 692...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. David Paleino da...@debian.org (supplier of updated josm-plugins 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 13 Nov 2012 22:52:14 +0100 Source: josm-plugins Binary: josm-plugins Architecture: source all Version: 0.0.svn28937+ds1-1 Distribution: unstable Urgency: low Maintainer: Debian OpenStreetMap Team pkg-osm-ma...@lists.alioth.debian.org Changed-By: David Paleino da...@debian.org Description: josm-plugins - Plugins for JOSM Closes: 692620 Changes: josm-plugins (0.0.svn28937+ds1-1) unstable; urgency=low . * New upstream snapshot. * New repacked tarball: removed livegps plugin, which had files under the problematic JSON license. Also removed surveyor plugin, which depends on it. (Closes: #692620) * Updated debian/copyright. * Updated debian/control: - included plugins in long description - bump JOSM dependency to = 5576 * Removed Andreas Putzo from Uploaders. Checksums-Sha1: 1e533edd4eae3b396b38c8196e69d1ecdbe111d1 1638 josm-plugins_0.0.svn28937+ds1-1.dsc 59fe11c7866e0d1d99482615aa869ef7f859abe9 276238 josm-plugins_0.0.svn28937+ds1.orig.tar.gz 669d85b6226222c1d558401bc5fef5cf87253df6 10396 josm-plugins_0.0.svn28937+ds1-1.debian.tar.gz 3050aa5d6e5aa6cc0f1968994c6fcf81bae8e173 350230 josm-plugins_0.0.svn28937+ds1-1_all.deb Checksums-Sha256: 38ecba7d7dfb462e70283da8c8961525d9ca05318b70b13136c7554968797c4b 1638 josm-plugins_0.0.svn28937+ds1-1.dsc 54f5b8e197be10574c2592aaa6ea6532787ca245306b23d4ffb26a9409846892 276238 josm-plugins_0.0.svn28937+ds1.orig.tar.gz 9636276a64f8e4c4275375107443377c21dbbce61144745eb3df4f3f40628371 10396 josm-plugins_0.0.svn28937+ds1-1.debian.tar.gz a8f5e5df8b2c9846842bb9aeab62161a9a1b2ddaff493c94b3bcb7e302f8ea19 350230 josm-plugins_0.0.svn28937+ds1-1_all.deb Files: 5dfe40866064349583b1f0a1e6657ebf 1638 utils extra josm-plugins_0.0.svn28937+ds1-1.dsc 60c2847f0e7b916c2ce484f2ddca7da1 276238 utils extra josm-plugins_0.0.svn28937+ds1.orig.tar.gz 361887b542071c104eb15162144c33e4 10396 utils extra josm-plugins_0.0.svn28937+ds1-1.debian.tar.gz ac8227ca3e22b77ebeb6b479f9cf281e 350230 utils extra josm-plugins_0.0.svn28937+ds1-1_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlCiwzIACgkQ5qqQFxOSsXSikwCeIgmN7beGADGU+iJlZtFajEos bCkAoKrjdw7qmje73rcZnwrB02Hd9ELK =/kae -END PGP SIGNATUREEnd Message---
Bug#692992: marked as done (FTBFS on kfreebsd-*)
Your message dated Tue, 13 Nov 2012 22:17:42 + with message-id e1tyone-0004yh...@franck.debian.org and subject line Bug#692992: fixed in rsyslog 7.2.1-2 has caused the Debian Bug report #692992, regarding FTBFS on kfreebsd-* 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 692992: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692992 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: src:rsyslog Version: 7.2.1-1 Severity: serious User: debian-...@lists.debian.org Usertags: kfreebsd Hi, the current version of rsyslog from experimental (7.2.1) FTBFS on kfreebsd-*. It would be great if the kfreebsd porters would have a look and provide a patch. Cheers, Michael -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.5-trunk-amd64 (SMP w/4 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash ---End Message--- ---BeginMessage--- Source: rsyslog Source-Version: 7.2.1-2 We believe that the bug you reported is fixed in the latest version of rsyslog, which is due to be installed in the Debian FTP archive. 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 692...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Biebl bi...@debian.org (supplier of updated rsyslog 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 13 Nov 2012 22:56:58 +0100 Source: rsyslog Binary: rsyslog rsyslog-doc rsyslog-mysql rsyslog-pgsql rsyslog-mongodb rsyslog-gssapi rsyslog-gnutls rsyslog-relp Architecture: source amd64 all Version: 7.2.1-2 Distribution: experimental Urgency: low Maintainer: Michael Biebl bi...@debian.org Changed-By: Michael Biebl bi...@debian.org Description: rsyslog- reliable system and kernel logging daemon rsyslog-doc - documentation for rsyslog rsyslog-gnutls - TLS protocol support for rsyslog rsyslog-gssapi - GSSAPI authentication and encryption support for rsyslog rsyslog-mongodb - MongoDB output plugin for rsyslog rsyslog-mysql - MySQL output plugin for rsyslog rsyslog-pgsql - PostgreSQL output plugin for rsyslog rsyslog-relp - RELP protocol support for rsyslog Closes: 692992 Changes: rsyslog (7.2.1-2) experimental; urgency=low . * Fix example configuration for logging to tty8. * Disable imptcp on non-Linux plattforms as this module is Linux-specific. Making it available everywhere would require more extensive porting work. * debian/patches/02-imkmsg-includes.patch: Don't include sys/klog.h on non-Linux plattforms. * debian/patches/03-sysinfo.patch: Getting the uptime via sysinfo() is Linux-specific, so only use that on architectures supporting it. * Use dh-autoreconf to update the build system. * Thanks Guillem Jover for the patches to make rsyslog compile on non-Linux. (Closes: #692992) Checksums-Sha1: 46717f5054820421bd85a38ae27cdf415076dad4 2422 rsyslog_7.2.1-2.dsc dcea004a6980236f4b2459cf058942ef8d9ef99c 29007 rsyslog_7.2.1-2.debian.tar.gz aaabb02d1ad7e561c4e63e7aae01efc15d8cb07f 658726 rsyslog_7.2.1-2_amd64.deb 7cd1653d853d35e9f090c828f12df465fa9561bc 1169890 rsyslog-doc_7.2.1-2_all.deb eb6891ba2199cdec57ea06c4ca8abe59608a1f40 137024 rsyslog-mysql_7.2.1-2_amd64.deb 481b1e2acca4fe641ff55d262c2025d984055fcd 135682 rsyslog-pgsql_7.2.1-2_amd64.deb d50b42364b87fbe68f0a9a4995f1820211c9877d 137828 rsyslog-mongodb_7.2.1-2_amd64.deb 2fd02a146fdfff40ebec1c770cd7c576280b1526 143556 rsyslog-gssapi_7.2.1-2_amd64.deb c3a5738dbad46da354bde699c5279a92e66fc397 142346 rsyslog-gnutls_7.2.1-2_amd64.deb 9d313ee9c9d60f1e0a551a80c6fdb213b59c75e0 137896 rsyslog-relp_7.2.1-2_amd64.deb Checksums-Sha256: 27ec722cf7e9f2ad3162fe00b4a882eeff6fc1ffd1ff07d5b6deafd7abe58680 2422 rsyslog_7.2.1-2.dsc 1d60e690bb94fa720c4d9150bb82f75242683227c2d903b2a6a8c6d535ebf351 29007 rsyslog_7.2.1-2.debian.tar.gz 30b6a6ed52af1d7cda8cd67ba8178b7c8e04164f8a9963f47f5056c55438b416 658726 rsyslog_7.2.1-2_amd64.deb 3adc88d2eb1723c4417a3f2d8f70b5e795252233d6b7a569f128e3ac0293f0bc 1169890 rsyslog-doc_7.2.1-2_all.deb
Processed: Re: Bug#692397: libogre-1.7.4: Segmentation fault when using a skeleton
Processing commands for cont...@bugs.debian.org: severity 692397 serious Bug #692397 [libogre-1.7.4] libogre-1.7.4: Segmentation fault when using a skeleton Severity set to 'serious' from 'important' stop Stopping processing here. Please contact me if you need assistance. -- 692397: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692397 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#691933: libphp-jpgraph: diff for NMU version 1.5.2-12.1
tags 691933 + patch tags 691933 + pending thanks Dear maintainer, I've prepared an NMU for libphp-jpgraph (versioned as 1.5.2-12.1) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Regards. David diff -u libphp-jpgraph-1.5.2/debian/changelog libphp-jpgraph-1.5.2/debian/changelog --- libphp-jpgraph-1.5.2/debian/changelog +++ libphp-jpgraph-1.5.2/debian/changelog @@ -1,3 +1,14 @@ +libphp-jpgraph (1.5.2-12.1) unstable; urgency=low + + * Non-maintainer upload. + * debian/control: +- Drop ttf-mscorefonts-installer from dependencies. (Closes: #691933) +- Depends on fonts-liberation instead of dummy ttf-liberation + transitional package. + * src/jpgraph_dir.php: adjust to fonts-liberation path. + + -- David Prévot taf...@debian.org Tue, 13 Nov 2012 19:29:03 -0400 + libphp-jpgraph (1.5.2-12) unstable; urgency=low * Add support for free LIBERATION fonts diff -u libphp-jpgraph-1.5.2/debian/control libphp-jpgraph-1.5.2/debian/control --- libphp-jpgraph-1.5.2/debian/control +++ libphp-jpgraph-1.5.2/debian/control @@ -7,7 +7,7 @@ Package: libphp-jpgraph Architecture: all -Depends: libapache2-mod-php5 | php5 | php5-cgi, php5-gd, ttf-liberation | ttf-mscorefonts-installer +Depends: libapache2-mod-php5 | php5 | php5-cgi, php5-gd, fonts-liberation Description: Object oriented graph library for php5 JpGraph is an object oriented class library for php5. JpGraph makes it easy to draw both quick and dirty graphs with a minimum of code diff -u libphp-jpgraph-1.5.2/src/jpgraph_dir.php libphp-jpgraph-1.5.2/src/jpgraph_dir.php --- libphp-jpgraph-1.5.2/src/jpgraph_dir.php +++ libphp-jpgraph-1.5.2/src/jpgraph_dir.php @@ -29,5 +29,5 @@ // Add Free liberation font as suggested by Alain Peyrat -DEFINE(LIBERATION_DIR,/usr/share/fonts/truetype/ttf-liberation/); +DEFINE(LIBERATION_DIR,/usr/share/fonts/truetype/liberation/); ? signature.asc Description: Digital signature
Processed: libphp-jpgraph: diff for NMU version 1.5.2-12.1
Processing commands for cont...@bugs.debian.org: tags 691933 + patch Bug #691933 [libphp-jpgraph] libphp-jpgraph depends on contrib: ttf-mscorefonts-installer Added tag(s) patch. tags 691933 + pending Bug #691933 [libphp-jpgraph] libphp-jpgraph depends on contrib: ttf-mscorefonts-installer Ignoring request to alter tags of bug #691933 to the same tags previously set thanks Stopping processing here. Please contact me if you need assistance. -- 691933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691933 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: limit source to libphp-jpgraph, tagging 691933
Processing commands for cont...@bugs.debian.org: #libphp-jpgraph (1.5.2-12.1) unstable; urgency=low # # * debian/control: #- Drop ttf-mscorefonts-installer from dependencies. (Closes: #691933) #- Depends on fonts-liberation instead of dummy ttf-liberation # transitional package. # limit source libphp-jpgraph Limiting to bugs with field 'source' containing at least one of 'libphp-jpgraph' Limit currently set to 'source':'libphp-jpgraph' tags 691933 + pending Bug #691933 [libphp-jpgraph] libphp-jpgraph depends on contrib: ttf-mscorefonts-installer Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 691933: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691933 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692623: missing source files for src/cson_amalgamation.c
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 After a quick lookup, i think the source files for the src/cson_amalgamation.c and src/cson_amalgamation.h files are kept in the repository: http://fossil.wanderinghorse.net/repos/cson/index.cgi/index (a sub-project of fossil ?) Cheers, Pedro m42 Ribeiro -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJQotuLAAoJELLf3v2QhfNw518P/iKI0cNfELkWCmOXr1GlwW6S x+mh5sm2fHqLFRx1+ygDT/pnpskw3jUanSwyudlH7kVGREamuEHjeYe59Gr9LMJ/ NZTWCAmIUi3myU62O2lypqtP3xzTkkw6FVjGLbExZsFuyhC2TsFMFxDI7KczAe+M HlH3m6UX6OeQtqqyHivVx8JLoOvRE1FOSSIjG8hb2omvzw1wXZMQygHfZF5Q8SOe 45RLKK5JKOXwEvgHgy6Jfgbg0Tn0/0QJqFbF7lYMuP9MruItoGjX6px1h6s1uScM bC99R73jBHO/SXe2kq8IIrm66Q7e7XsDQdgZUVwqtLIzRTo3VunxyN/8oj9/py6g 5AXrbmFAVuB7ZI5b00kyC074zl7qizgKjx1uv+yQFk2ZaESg1VPoGg4XheQRnR+3 FEYFnuWXHV3s49rrmB91j/katS0z6rqPw/GRg1goLDTn0yrC1Urs4oq7qZZYuLsA /gcPBx49Rn/ySs7JonR+L/jBXKnBknrWgjTHOpBFhct3cCzQ4ratD+5dcEVFWJf7 xE1+0Wq/+XD0e5heqgqBQtWjamqD5t599SXRpoybFXYg5rv4/rcJwsUGsbMNCvHH ayU+yrqDC8Zryb0NdzCOkBUYui+ep1Pcq4sdJ8Bj535DrrZfTdrV5x3+NF53LWtp Mric9Hc3/jNjU6FAjDjk =QoBD -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690200: marked as done (ogre: incomplete debian/copyright)
Your message dated Wed, 14 Nov 2012 00:02:47 + with message-id e1tyqrl-0003k7...@franck.debian.org and subject line Bug#690200: fixed in ogre 1.7.4+dfsg1-7 has caused the Debian Bug report #690200, regarding ogre: incomplete debian/copyright 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 690200: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690200 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ogre Version: 1.7.4-5 Severity: serious Bug 690199 is also in ogre, see for example Copyright 1998-2002 by Neil Hodgson in Tools/MaterialEditor/wxscintilla_1.69.2/src/scintilla/src/LexPython.cxx. ---End Message--- ---BeginMessage--- Source: ogre Source-Version: 1.7.4+dfsg1-7 We believe that the bug you reported is fixed in the latest version of ogre, which is due to be installed in the Debian FTP archive. 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 690...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Manuel A. Fernandez Montecelo manuel.montez...@gmail.com (supplier of updated ogre 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 13 Nov 2012 22:05:00 + Source: ogre Binary: libogre-dev libogre-1.7.4 libogre-1.7.4-dbg ogre-doc ogre-tools blender-ogrexml Architecture: source amd64 all Version: 1.7.4+dfsg1-7 Distribution: unstable Urgency: low Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Changed-By: Manuel A. Fernandez Montecelo manuel.montez...@gmail.com Description: blender-ogrexml - Blender Exporter for OGRE libogre-1.7.4 - 3D Object-Oriented Graphics Rendering Engine (libraries) libogre-1.7.4-dbg - 3D Object-Oriented Graphics Rendering Engine (debugging libs) libogre-dev - 3D Object-Oriented Graphics Rendering Engine (development files) ogre-doc - 3D Object-Oriented Graphics Rendering Engine (documentation) ogre-tools - 3D Object-Oriented Graphics Rendering Engine (tools) Closes: 690200 692397 Changes: ogre (1.7.4+dfsg1-7) unstable; urgency=low . * Document some files oversought in debian/copyright (Closes: #690200). Thanks Bart Martens and Anton Gladky for reporting and collaborating in fixing the problem. * Patches: - Add remove-alignment.patch to drop obsolete stack alignment hack that breaks with gcc-4.7 (removed in upstream 1.8.1), and causes crashes on some architectures when using skeletons (possibly affecting a broad range of OGRE applications). The patch is a modified version by me from the patch applied to 1.8.1, upstream does not support 1.7 series anymore. Thanks to Julian Taylor and Kai Mast for the report and point to upstream patch to 1.8 (#687013), and Nicolas Bourdaud for pointing to the problem in 1.7 series as well (Closes: #692397). Checksums-Sha1: f86daa6a92df3483822c93d1f243200078e1282d 2527 ogre_1.7.4+dfsg1-7.dsc eb0cb4186d1a68db10c5d77815da094aa83b3bc9 26221 ogre_1.7.4+dfsg1-7.debian.tar.gz d679a6527a285c24bfbbc61a2fcdef94d22fc1ac 1205676 libogre-dev_1.7.4+dfsg1-7_amd64.deb e701f77cb81f591cc7a8e4df44d166bf0a0ce0da 3386442 libogre-1.7.4_1.7.4+dfsg1-7_amd64.deb 822ba18ac2037a38aeda7e2303b567c35d027b87 51508088 libogre-1.7.4-dbg_1.7.4+dfsg1-7_amd64.deb 4fd447245321f5e14663906ba8d120b9ab9ef09f 16151204 ogre-doc_1.7.4+dfsg1-7_all.deb 02ad6e3efd145b7b91debf429eee59319f9b41e1 241624 ogre-tools_1.7.4+dfsg1-7_amd64.deb 3d4fb6066d25684f041fad0eb6d9e64f98a65d00 219166 blender-ogrexml_1.7.4+dfsg1-7_all.deb Checksums-Sha256: 4abe7197ebc5011ee157643be4ab6ad3e07745ce7250b51b09cc74268f64128c 2527 ogre_1.7.4+dfsg1-7.dsc 9dd5e9763d88805723fc1bb440c5023c274c097075a79c43376acafabd1e4bf4 26221 ogre_1.7.4+dfsg1-7.debian.tar.gz bc1a055900355d2a800daa720cf92452f7e226d81a7f431c65bee08e11a13e90 1205676 libogre-dev_1.7.4+dfsg1-7_amd64.deb bd337be87cf315a92b1d0a06e4de6d26f69bb4e5664aca5ac8efef19f41a1d5e 3386442 libogre-1.7.4_1.7.4+dfsg1-7_amd64.deb f07c90159724970d3f38309172e7236efd1fa816c8a332af2a34165beb2796a4 51508088 libogre-1.7.4-dbg_1.7.4+dfsg1-7_amd64.deb 4909a6ce4e99406549d8fba9f35c77f93bcd62e9e396e1d3f4dca46cb0038b79 16151204 ogre-doc_1.7.4+dfsg1-7_all.deb
Bug#692397: marked as done (libogre-1.7.4: Segmentation fault when using a skeleton)
Your message dated Wed, 14 Nov 2012 00:02:47 + with message-id e1tyqrl-0003ka...@franck.debian.org and subject line Bug#692397: fixed in ogre 1.7.4+dfsg1-7 has caused the Debian Bug report #692397, regarding libogre-1.7.4: Segmentation fault when using a skeleton 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 692397: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692397 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libogre-1.7.4 Version: 1.7.4+dfsg1-6 Severity: important Tags: upstream patch Any program using a skeleton along a mesh will segfault (at least on amd64). This is the same bug as #687013 which affected ogre-1.8. It is easily fixed by applying the same patch (updated for 1.7.4). Although it is not an RC bug, please consider requesting a freeze exception for this fix: it affects anyone who use skeleton with a mesh (at least on amd64) which is a use case extremely well spread. cheers, Nicolas Bourdaud -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=fr_FR.utf8, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libogre-1.7.4 depends on: ii dpkg 1.16.9 ii libboost-thread1.49.0 1.49.0-3.1 ii libc6 2.13-35 ii libfreeimage3 3.15.1-1+b1 ii libfreetype6 2.4.9-1 ii libgcc1 1:4.7.1-7 ii libgl1-mesa-glx [libgl1] 8.0.4-2 ii libglu1-mesa [libglu1]8.0.4-2 ii libstdc++64.7.1-7 ii libx11-6 2:1.5.0-1 ii libxaw7 2:1.0.10-2 ii libxrandr22:1.3.2-2 ii libxt61:1.1.3-1 ii libzzip-0-13 0.13.56-1.1 ii multiarch-support 2.13-35 libogre-1.7.4 recommends no packages. libogre-1.7.4 suggests no packages. -- no debconf information Description: drop stack alignment hack that breaks with gcc-4.7 Bug: http://www.ogre3d.org/mantis/view.php?id=553 Bug-Debian: http://bugs.debian.org/687013 Origin: upstream, http://hg.libsdl.org/SDL/rev/62ff1c0a103f Applied-Upstream: 1.8.1 # HG changeset patch # User Holger Frydrych h.frydr...@gmx.de # Date 1343895642 -7200 # Branch v1-8 # Node ID 9db0902fcff8772b5f9f6c3459430bb8a75bbe09 # Parent 5bcdaa1cf83322d5a281d1fd6752228a94d51620 Replace an ugly hack for GCC that was trying to force 16-byte stack alignment in OgreOptimisedUtilSSE, but causes trouble with recent GCC versions --- a/OgreMain/src/OgreOptimisedUtilSSE.cpp +++ b/OgreMain/src/OgreOptimisedUtilSSE.cpp @@ -84,7 +84,7 @@ OptimisedUtilSSE(void); /// @copydoc OptimisedUtil::softwareVertexSkinning -virtual void softwareVertexSkinning( +virtual void __OGRE_SIMD_ALIGN_ATTRIBUTE softwareVertexSkinning( const float *srcPosPtr, float *destPosPtr, const float *srcNormPtr, float *destNormPtr, const float *blendWeightPtr, const unsigned char* blendIndexPtr, @@ -96,35 +96,35 @@ size_t numVertices); /// @copydoc OptimisedUtil::softwareVertexMorph -virtual void softwareVertexMorph( +virtual void __OGRE_SIMD_ALIGN_ATTRIBUTE softwareVertexMorph( Real t, const float *srcPos1, const float *srcPos2, float *dstPos, size_t numVertices); /// @copydoc OptimisedUtil::concatenateAffineMatrices -virtual void concatenateAffineMatrices( +virtual void __OGRE_SIMD_ALIGN_ATTRIBUTE concatenateAffineMatrices( const Matrix4 baseMatrix, const Matrix4* srcMatrices, Matrix4* dstMatrices, size_t numMatrices); /// @copydoc OptimisedUtil::calculateFaceNormals -virtual void calculateFaceNormals( +virtual void __OGRE_SIMD_ALIGN_ATTRIBUTE calculateFaceNormals( const float *positions, const EdgeData::Triangle *triangles, Vector4 *faceNormals, size_t numTriangles); /// @copydoc OptimisedUtil::calculateLightFacing -virtual void calculateLightFacing( +virtual void __OGRE_SIMD_ALIGN_ATTRIBUTE calculateLightFacing( const Vector4 lightPos, const Vector4* faceNormals, char* lightFacings, size_t numFaces); /// @copydoc OptimisedUtil::extrudeVertices -virtual void extrudeVertices( +virtual void __OGRE_SIMD_ALIGN_ATTRIBUTE
Bug#684852: [Python-modules-team] Bug#684852: nmu
On Tue, Nov 13, 2012 at 3:49 AM, Jonathan Wiltshire wrote: I don't understand your version number. Please see devref [1] and consider that this does not appear to be a native package. 1: http://www.debian.org/doc/manuals/developers-reference/pkgs.html#nmu-changelog Devref is not an inflexible set of restrictions. It is a set of helpful guidelines. +debXuY for stable updates makes +nmuN a useful alternative to .N for nmus: http://bugs.debian.org/542288 Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693176: imagemagick: ftbfs on sparc
package: imagemagick version: 8:6.7.7.10-5 severity: serious imagemagick fails to build on sparc. convert fails: # make xpm /usr/bin/convert /build/buildd-imagemagick_6.7.7.10-5-sparc-QgV24K/imagemagick-6.7.7.10/debian/display.im6.svg -resize 32x32 \ /build/buildd-imagemagick_6.7.7.10-5-sparc-QgV24K/imagemagick-6.7.7.10/debian/display.im6.xpm *** glibc detected *** convert: free(): invalid pointer: 0x7127c008 *** -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#660671: libdispatch: Fails to build (link dispatch_starfish) on armel
control: tag -1 -patch Looks like more work needs to be done here. Removing patch tag. Best wishes, Mike -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: re: libdispatch: Fails to build (link dispatch_starfish) on armel
Processing control commands: tag -1 -patch Bug #660671 [src:libdispatch] libdispatch: Fails to build (link dispatch_starfish) on armel Removed tag(s) patch. -- 660671: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=660671 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692534: Fails to build sqldeveloper package with chmod: missing operand after `755'
On Tue, Nov 13, 2012 at 9:15 PM, Salvatore Bonaccorso car...@debian.org wrote: Hi Lazarus On Tue, Nov 13, 2012 at 07:37:11PM +, Lazarus Long wrote: On Mon, Nov 12, 2012 at 5:09 PM, Salvatore Bonaccorso car...@debian.org wrote: Hi Steven On Wed, Nov 07, 2012 at 10:48:15AM +0100, Steven Post wrote: Package: sqldeveloper-package Version: 0.2.3+nmu1 Severity: grave Dear maintainer, The command make-sql-developer fails to build the sqldeveloper package with a rather unhelpful message. Terminal output: $ make-sqldeveloper-package -b sqldeveloper sqldeveloper-3.2.20.09.87-no-jre.zip chmod: missing operand after `755' Try `chmod --help' for more information. Omitting the -b parameter has no effect on the output. As you migth have seen, I uploaded a NMU to a delayed queue. You can test the package in [1] if you like. [1]: http://ftp-master.debian.org/deferred/ Hi: I've uploaded to mentors.debian.net https://mentors.debian.net/package/sqldeveloper-package version 0.3.0, that addresses this issue (along all other bugs reported both on Debian and on Ubuntu). I'm not quite sure how will the package be moved to ftp-master (last time one of the Developers offered to move it). Thank you for all the feedback and regards, Thanks for your reply! Should I cancel my NMU from the delayed queue? But please note, the debdiff between 0.2.3+nmu1 and 0.3.0 looks quite big. If you plan an upload (and need sponsoring) could you have a look at [1] for the wheezy freeze_policy? At this stage of the freeze only some important issues, and clearly RC bugs should be addressed to have the package in wheezy; so it might be to late for some of the addressed issues. [1]: http://release.debian.org/wheezy/freeze_policy.html Please let me know if you have some questions. Ciao, Salvatore: I wasn't aware of the Wheezy freeze in progress. The 0.3.0 version I've uploaded to Mentors is my current running script, that I've been testing and modifying since my last upload in 2009, Beside the obvious need to address the RCs, the changes it contains are required since otherwise: - unaware users wouldn't be able to:find the package to download due to dead links; - an old deprecated license agreement would be accompanying the package instead of a current valid one; - old and unavailable methods to get a compatible JDK would be tried and failed; These seem not so important for users that are already using the package, and know what the changes Oracle introduced in the last two years, but for new users it would be stressing and an incentive to not using it, supposing it is flawed (and in it's current state it is). Beside the above changes all others are related to addressing lintian and QA warnings or errors and compliance to standards, not in the script itself. The large difference between this version and the previous is due to the peculiar fact that the script is also a generator of a debianized package, so in order to the generated package to be standard compliant and error free the script has to be edited and the above mentioned changes (mainly the license, which is about a third of the size of the script), placed inside it. I hope I explained my idea, if you feel it's not applicable, please let me know so we can try to find a way to do it right. Thank you and regards, -- Lazarus -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#661471: NMU v2 (was: Re: Bug#661471: bug 661471 gnome-accessibility-themes)
On Tue, Nov 13, 2012 at 9:48 AM, Theppitak Karoonboonyanan t...@debian.org wrote: It's being reviewed. And it's likely that some of the changes may be rejected. Re-uploaded with multiarch change dropped. Now in NEW again. Regards, -- Theppitak Karoonboonyanan http://linux.thai.net/~thep/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690574: oss4-base: depends on linux-sound-base
control: tag -1 patch Hi, I've uploaded an nmu fixing this issue to delayed/5. Let me know if I should delay longer or rework it somehow. Please see attached patch. Best wishes, Mike oss4.patch Description: Binary data
Processed: re: oss4-base: depends on linux-sound-base
Processing control commands: tag -1 patch Bug #690574 [oss4-base] oss4-base: depends on linux-sound-base Added tag(s) patch. -- 690574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=690574 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693188: opendkim-tools: Missing depends on openssl renders opendkim-genkey unusable
Package: opendkim-tools Version: 2.6.8-1 Severity: grave Justification: renders package unusable After installing opendkim-tools in a mimial chroot and runnging opendkim-genkey, there are errors: opendkim-genkey grep: default.public: No such file or directory As indicated in the upstream provided man page, openssl is needed for this script to work correctly, but opendkim-tools does not depend on it. Marking this grave since this is the most commonly used script in the package. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: tagging 693188
Processing commands for cont...@bugs.debian.org: tags 693188 + pending Bug #693188 [opendkim-tools] opendkim-tools: Missing depends on openssl renders opendkim-genkey unusable Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 693188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693188: marked as done (opendkim-tools: Missing depends on openssl renders opendkim-genkey unusable)
Your message dated Wed, 14 Nov 2012 05:32:31 + with message-id e1tyvar-0004ig...@franck.debian.org and subject line Bug#693188: fixed in opendkim 2.6.8-3 has caused the Debian Bug report #693188, regarding opendkim-tools: Missing depends on openssl renders opendkim-genkey unusable 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 693188: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=693188 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: opendkim-tools Version: 2.6.8-1 Severity: grave Justification: renders package unusable After installing opendkim-tools in a mimial chroot and runnging opendkim-genkey, there are errors: opendkim-genkey grep: default.public: No such file or directory As indicated in the upstream provided man page, openssl is needed for this script to work correctly, but opendkim-tools does not depend on it. Marking this grave since this is the most commonly used script in the package. ---End Message--- ---BeginMessage--- Source: opendkim Source-Version: 2.6.8-3 We believe that the bug you reported is fixed in the latest version of opendkim, which is due to be installed in the Debian FTP archive. 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 693...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Scott Kitterman sc...@kitterman.com (supplier of updated opendkim 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 ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Wed, 14 Nov 2012 00:07:48 -0500 Source: opendkim Binary: opendkim opendkim-tools libopendkim7 libopendkim-dev libvbr2 libvbr-dev Architecture: source i386 Version: 2.6.8-3 Distribution: unstable Urgency: medium Maintainer: Mike Markley m...@markley.org Changed-By: Scott Kitterman sc...@kitterman.com Description: libopendkim-dev - Headers and development libraries for the OpenDKIM library libopendkim7 - Library for signing and verifying DomainKeys Identified Mail sign libvbr-dev - Headers and development libraries for the OpenDKIM VBR library libvbr2- Library for RFC 5518 Vouch By Reference (VBR) opendkim - Milter implementation of DomainKeys Identified Mail opendkim-tools - Set of command line tools for OpenDKIM Closes: 693188 Changes: opendkim (2.6.8-3) unstable; urgency=medium . * Urgency medium for low risk RC bug fix * Add missing depends on openssl to opendkim-tools so opendkim-genkey will work (Closes: #693188) Checksums-Sha1: 159ebae12f589b9dd1a3e17835b2665de040bc48 1397 opendkim_2.6.8-3.dsc 2f8e15d3c58a2cb2110864054523ef0c2b8df9ba 13219 opendkim_2.6.8-3.diff.gz e000b47aeefa145e14fe3009837329206757 178034 opendkim_2.6.8-3_i386.deb 5a4c46cb99bf2bbff9ab82b8c21015bc8b5ea203 167140 opendkim-tools_2.6.8-3_i386.deb 159dbf3a7ce1913d6ccfdc69c7e583e22cc7f212 86986 libopendkim7_2.6.8-3_i386.deb 80eabd70754044e9308175b90d95cf0de811392d 175180 libopendkim-dev_2.6.8-3_i386.deb 2ade564fe69ed40b9c8b94b6844d7c4faa5fe1c0 35388 libvbr2_2.6.8-3_i386.deb e65c0193cc117acde8aad92fda0aa8a858335308 39118 libvbr-dev_2.6.8-3_i386.deb Checksums-Sha256: 90f2e8c97b8811bbf3e7bae7d5206ab0fe0e75a13f7381d02e76f3e66c6bc640 1397 opendkim_2.6.8-3.dsc 5daead1d408cea8915072afa86346bbc1e4a1553b0126265c0374ea9e485dff5 13219 opendkim_2.6.8-3.diff.gz 6520c5677e11fbed6d3aa62c72be2b48c4a39530dcadc1cd581d994fb5a93eb2 178034 opendkim_2.6.8-3_i386.deb 052aafe94a77ca380ec35e485b817ae55bf59301422eb22e8ef39a8221c9f2d5 167140 opendkim-tools_2.6.8-3_i386.deb 0631d84df10daec743d9a14d5c8536dd4e9a0b42821e6b97a3465889c4822248 86986 libopendkim7_2.6.8-3_i386.deb 38e0ad4aec120720037ab8c826a14f457b6e5344c6cdc480a6eef4e971172c3e 175180 libopendkim-dev_2.6.8-3_i386.deb 7f0746ce2f2471eccef28914ed1870c53ca65a52cea9361cde532ecf41167a3a 35388 libvbr2_2.6.8-3_i386.deb 36b77796d61e93e3cca76cdcf5e55681f8f6b5b279206ea3c25d6f470f8fad60 39118 libvbr-dev_2.6.8-3_i386.deb Files: 45d98cc509c86265bc60857c6b879d99 1397 mail extra opendkim_2.6.8-3.dsc 0f2f1147b8194dd177ce8514b0c68a62 13219 mail extra opendkim_2.6.8-3.diff.gz 716e6e7718e5568f5c939687e81e0eab 178034 mail extra opendkim_2.6.8-3_i386.deb 3a7298d5bfa6ca44b56f32f53e9b6dd6 167140 mail extra opendkim-tools_2.6.8-3_i386.deb 33264bfb60e5e939efa6207cf728b38b 86986 libs
Processed: Re: Bug#692534: Fails to build sqldeveloper package with chmod: missing operand after `755'
Processing control commands: tags -1 - pending Bug #692534 [sqldeveloper-package] Fails to build sqldeveloper package with chmod: missing operand after `755' Removed tag(s) pending. -- 692534: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=692534 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692534: Fails to build sqldeveloper package with chmod: missing operand after `755'
Control: tags -1 - pending Ciao Lazarus On Wed, Nov 14, 2012 at 02:23:06AM +, Lazarus Long wrote: On Tue, Nov 13, 2012 at 9:15 PM, Salvatore Bonaccorso car...@debian.org wrote: Hi Lazarus On Tue, Nov 13, 2012 at 07:37:11PM +, Lazarus Long wrote: On Mon, Nov 12, 2012 at 5:09 PM, Salvatore Bonaccorso car...@debian.org wrote: Hi Steven On Wed, Nov 07, 2012 at 10:48:15AM +0100, Steven Post wrote: Package: sqldeveloper-package Version: 0.2.3+nmu1 Severity: grave Dear maintainer, The command make-sql-developer fails to build the sqldeveloper package with a rather unhelpful message. Terminal output: $ make-sqldeveloper-package -b sqldeveloper sqldeveloper-3.2.20.09.87-no-jre.zip chmod: missing operand after `755' Try `chmod --help' for more information. Omitting the -b parameter has no effect on the output. As you migth have seen, I uploaded a NMU to a delayed queue. You can test the package in [1] if you like. [1]: http://ftp-master.debian.org/deferred/ Hi: I've uploaded to mentors.debian.net https://mentors.debian.net/package/sqldeveloper-package version 0.3.0, that addresses this issue (along all other bugs reported both on Debian and on Ubuntu). I'm not quite sure how will the package be moved to ftp-master (last time one of the Developers offered to move it). Thank you for all the feedback and regards, Thanks for your reply! Should I cancel my NMU from the delayed queue? But please note, the debdiff between 0.2.3+nmu1 and 0.3.0 looks quite big. If you plan an upload (and need sponsoring) could you have a look at [1] for the wheezy freeze_policy? At this stage of the freeze only some important issues, and clearly RC bugs should be addressed to have the package in wheezy; so it might be to late for some of the addressed issues. [1]: http://release.debian.org/wheezy/freeze_policy.html Please let me know if you have some questions. Ciao, Salvatore: I wasn't aware of the Wheezy freeze in progress. Okay! The 0.3.0 version I've uploaded to Mentors is my current running script, that I've been testing and modifying since my last upload in 2009, Beside the obvious need to address the RCs, the changes it contains are required since otherwise: - unaware users wouldn't be able to:find the package to download due to dead links; - an old deprecated license agreement would be accompanying the package instead of a current valid one; - old and unavailable methods to get a compatible JDK would be tried and failed; These seem not so important for users that are already using the package, and know what the changes Oracle introduced in the last two years, but for new users it would be stressing and an incentive to not using it, supposing it is flawed (and in it's current state it is). Beside the above changes all others are related to addressing lintian and QA warnings or errors and compliance to standards, not in the script itself. The large difference between this version and the previous is due to the peculiar fact that the script is also a generator of a debianized package, so in order to the generated package to be standard compliant and error free the script has to be edited and the above mentioned changes (mainly the license, which is about a third of the size of the script), placed inside it. I hope I explained my idea, if you feel it's not applicable, please let me know so we can try to find a way to do it right. Yes I understand. Honestly I'm not using sqldeveloper-package but only helping out on current RC bugs for wheezy. I have now cancelled my NMU upload. I would now suggest to try the following: Have a look at the freeze policy and try to adapt the required changes you think are necessary for the package to have it in wheezy. As next step, create a debdiff against current version in testing and then via an unblock request first ask for a (pre-)approval of the package. You can keep me in CC, so that if the Release-Team gives their ACK to it, I can sponsor your upload to the archive. Does this helps? Regards, Salvatore signature.asc Description: Digital signature
Bug#689831: gconf-cleaner: Impossible to backup configuration
Andrew, gconf-cleaner has been abandoned by upstream for a while now and I do not believe it in a shape suitable for a stable release, so I am going to ask removal from Debian. Thanks for reporting the issue, Cheers, Ludovico On Wed, Oct 24, 2012 at 1:31 PM, Andrew Starr-Bochicchio a.star...@gmail.com wrote: This was reported upstream at: http://code.google.com/p/gconf-cleaner/issues/detail?id=18 It was also reported in Ubuntu at: https://bugs.launchpad.net/debian/+source/gconf-cleaner/+bug/764041 The issue seems to be that gconf-cleaner does not support the Schema value: http://developer.gnome.org/gconf/2.32/gconf-gconf-schema.html#GConfSchema -- Andrew Starr-Bochicchio Ubuntu Developer https://launchpad.net/~andrewsomething Debian Maintainer http://qa.debian.org/developer.php?login=a.starr.b%40gmail.com PGP/GPG Key ID: D53FDCB1 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#690409: closed by Michal ÃÂÃÂihaÃÂ ÃÂ ni...@debian.org (Bug#690409: fixed in xcache 2.0.0-3)
Hi Dne Sun, 11 Nov 2012 19:34:57 +0100 intrigeri intrig...@debian.org napsal(a): My modification change is still in xcache.ini, the absolute extension path is there too, and no .dpkg-* files waiting for me to merge stuff. Okay, it looks like I need to use same (ugly) hack as xdebug is using, will do another upload. -- Michal Čihař | http://cihar.com | http://blog.cihar.com signature.asc Description: PGP signature