Processed: severity of 699877 is serious
Processing commands for cont...@bugs.debian.org: > severity 699877 serious Bug #699877 [src:postfix] postfix: maintainer address bounces Severity set to 'serious' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 699877: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699877 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#696386: marked as done (makedumpfile fails with elf_readall error)
Your message dated Tue, 5 Feb 2013 23:08:15 -0800 with message-id <20130206070815.ga15...@callisto.home.lan> and subject line Re: Bug#696386: makedumpfile fails with elf_readall error : more information has caused the Debian Bug report #696386, regarding makedumpfile fails with elf_readall error 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.) -- 696386: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696386 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: makedumpfile Version: 1.5.0-1 Severity: grave Justification: renders package unusable Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? Testing packaging of new 1.5.1 version of makedumpfile. * What exactly did you do (or not do) that was effective (or ineffective)? Ran normal kernel panic test. * What was the outcome of this action? The following output came out when makedumpfile tried to run : Starting kdump-tools: [info] running makedumpfile -c -d 31 -x /usr/lib/debug/boot/vmlinux-3.2.0-4-amd64 /proc/vmcore /var/crash/201212201000/d ump-incomplete. makedumpfile: elf_readall.c:94: __libelf_readall: Unexpected error: Resource deadlock avoided. /usr/sbin/kdump-config: line 387: 2243 Aborted makedumpfile $MAKEDUMP_ARGS $vmcore_file $KDUMP_CORETEMP [FAIL] kdump-tools: makedumpfile failed, falling back to 'cp' ... failed! Since this was while testing makedumpfile 1.5.1 for packaging, I tested the current packaged 1.5.0-1 which tested successfully previously and it also fails. This might be a regression from another package. It is important to note that makedumpfile correctly runs on the dump file once the system is back to multi-user. * What outcome did you expect instead? makedumpfile correctly process the /proc/vmcore file -- System Information: Debian Release: 7.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages makedumpfile depends on: ii libbz2-1.0 1.0.6-4 ii libc6 2.13-37 ii libdw1 0.153-2 ii libelf1 0.153-2 ii perl5.14.2-16 ii zlib1g 1:1.2.7.dfsg-13 Versions of packages makedumpfile recommends: ii crash6.1.0-1 ii kexec-tools 1:2.0.3-1 makedumpfile suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- tag 696386 + unreproducible thanks On Thu, Jan 31, 2013 at 05:46:18PM +0100, Bouchard Louis wrote: > Hello John, > > Well this is what happen when juggling with too many distros. I might > have tested with a .deb package built on Ubuntu instead of my normal > Debian/Sid build VM. > > After rebuilding the package on Sid, the makedumpfile command works as > expected. You can mark this bug as invalid. Tagging it unreproducible and closing. :) -- John Wright --- End Message ---
Processed: Re: Bug#696386: makedumpfile fails with elf_readall error : more information
Processing commands for cont...@bugs.debian.org: > tag 696386 + unreproducible Bug #696386 [makedumpfile] makedumpfile fails with elf_readall error Added tag(s) unreproducible. > thanks Stopping processing here. Please contact me if you need assistance. -- 696386: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696386 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#699208: bug not present in 0.16.7 BFS on wheezy
Because the mpd package is missing from the Wheezy archives, I built 0.16.7 today on a fresh Wheezy amd64 install, using the source package and building with debian/rules binary. This problem is not present in 0.16.7 as packaged for Wheezy, so it's a regression in 0.16.8. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#699835: marked as done (keystone: CVE-2013-0247: Keystone denial of service through invalid token requests)
Your message dated Wed, 06 Feb 2013 02:47:37 + with message-id and subject line Bug#699835: fixed in keystone 2012.1.1-12 has caused the Debian Bug report #699835, regarding keystone: CVE-2013-0247: Keystone denial of service through invalid token requests 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.) -- 699835: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699835 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: keystone Severity: grave Tags: security Justification: user security hole Hi, the following vulnerability was published for keystone. CVE-2013-0247[0]: Keystone denial of service through invalid token requests Patches should be available via [1]. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0247 http://security-tracker.debian.org/tracker/CVE-2013-0247 [1] https://lists.launchpad.net/openstack/msg20689.html Please adjust the affected versions in the BTS as needed. Regards, Salvatore --- End Message --- --- Begin Message --- Source: keystone Source-Version: 2012.1.1-12 We believe that the bug you reported is fixed in the latest version of keystone, 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 699...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand (supplier of updated keystone 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, 06 Feb 2013 09:52:07 +0800 Source: keystone Binary: python-keystone keystone keystone-doc Architecture: source all Version: 2012.1.1-12 Distribution: unstable Urgency: low Maintainer: PKG OpenStack Changed-By: Thomas Goirand Description: keystone - OpenStack identity service keystone-doc - OpenStack identity service - documentation python-keystone - OpenStack identity service - library Closes: 699835 Changes: keystone (2012.1.1-12) unstable; urgency=low . * CVE-2013-0247: Keystone denial of service through invalid token requests (Closes: #699835). Checksums-Sha1: ba2661a72d48f45f124587b39cdeded4f732d355 1902 keystone_2012.1.1-12.dsc 0af6cb8d28c1eb27de93de6f05811ac89ec3cb85 28470 keystone_2012.1.1-12.debian.tar.gz 3eb0bc1365fc5e6b3156c4a645da7629870a5b0a 93240 python-keystone_2012.1.1-12_all.deb 8c4176ff456128f38f0e27ff44a794fa5862ae36 18338 keystone_2012.1.1-12_all.deb ae54d6fef3f4e26ebed9963ea6306d505a7e57c7 240660 keystone-doc_2012.1.1-12_all.deb Checksums-Sha256: 47bba32c1a5277b777e6c73a3d315763c1cdf38362e5b53ccc5499d1050ca48e 1902 keystone_2012.1.1-12.dsc 2d8720e327c3786eeaa5b86123d75b0a3b722e5174ac1595bd517f49f63e0142 28470 keystone_2012.1.1-12.debian.tar.gz 82b86448682e9f0e39050188a211e174bf04d0f2d9642d0619d43881537ac9a9 93240 python-keystone_2012.1.1-12_all.deb 6315d40686c0e5a9f86e644047852545ffce182c1ebcb49ab77d14583020c7a6 18338 keystone_2012.1.1-12_all.deb 8f3a5198079cc32c2b5271dd2b767ec9ebce242f2af36740051a449db48592ac 240660 keystone-doc_2012.1.1-12_all.deb Files: 7491ad50b55b820ef5d2b5286d57940b 1902 net extra keystone_2012.1.1-12.dsc c3070057b6d53ab34046d6e64adae352 28470 net extra keystone_2012.1.1-12.debian.tar.gz c992d48a0b03346b265b0f3834a1a727 93240 python extra python-keystone_2012.1.1-12_all.deb 31a38d32e66abfc5c249a8c923336b74 18338 python extra keystone_2012.1.1-12_all.deb e5a6f2a61b94fd36dc92a425b9ab810d 240660 doc extra keystone-doc_2012.1.1-12_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlERuG0ACgkQl4M9yZjvmkkdAgCg1wKTmombFWVPsjiAwOxge0wJ h8YAoIaGyVYXESI6m6jP966PrfWxyn/c =+ES/ -END PGP SIGNATURE End Message ---
Bug#699866: clang crashes while translating a trivial C++ program
Package: clang
Version: 3.0-6
Severity: grave
Justification: renders package unusable
Dear Maintainer,
compiling this program
---8<---
#include
int main ( int argc, char * argv[] )
{
int * i = new int (100);
int j = (*i) + 4;
delete i;
return j;
}
---8<---
causes clang to crash in the lexer complaining about the execution
of an "Illegal instruction" and suggesting to file a report with
http://llvm.org/bugs/.
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.39-2-powerpc
Locale: LANG=POSIX, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages clang depends on:
ii libc62.13-37
ii libclang-common-dev 3.0-6
ii libffi5 3.0.10-3
ii libgcc1 1:4.7.2-5
ii libllvm3.0 3.0-10
ii libstdc++6 4.7.2-5
ii libstdc++6-4.6-dev 4.6.3-14
Versions of packages clang recommends:
ii llvm-3.0-dev 3.0-10
ii python2.7.3~rc2-1
clang 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#688140: file-rc: File-rc doesn't restore rcX.d dirs at remove, breaks sysv-rc installation.
On Wed, Feb 06, 2013 at 12:49:02AM +0100, Michael Stapelberg wrote: > On Tue, 6 Nov 2012 20:46:25 +0100 > Andreas Beckmann wrote: > > On Wednesday, 19. September 2012 21:05:03 Piotr Borkowski wrote: > > > File-rc doesn't restore rcX.d dirs at remove. This breaks sysv-rc > > > legacy_bootordering postinst function. After sysv-rc installation > > > this leads to empty rcX.d dirs and broken system. Maybe file-rc > > > should call > > > > I can reproduce this problem in piuparts distupgrade tests, e.g. > > setup squeeze (or wheezy) chroot > > switch to file-rc > > distupgrade to wheezy (or sid) > > switch back to sysv-rc > > > > but not within a distro: > > setup a squeeze (or wheezy or sid) chroot > > switch to file-rc > > switch back to sysv-rc > > > > curiously it also happens after a wheezy->sid distuprade, even if the > > versions of sysv-rc and file-rc are the same in both sid and wheezy > I haven’t tried to reproduce this issue yet, but I have figured out > that in file-rc 0.8.13, the call to rcfile2link.sh was removed from > debian/prerm: > > --- file-rc-0.8.12/debian/prerm 2010-04-07 21:30:54.0 +0200 > +++ file-rc-0.8.13/debian/prerm 2012-07-30 07:49:08.0 +0200 > @@ -19,7 +19,6 @@ > > case "$1" in > remove) > - /usr/share/file-rc/rcfile2link.sh > ;; > upgrade|deconfigure) > ;; > > > The changelog mentions: > >* Removed long obsolete logic (prior to oldstable) from maintainer > scripts, which is no longer useful for upgrades. > > Roger: Your name was above the changes in the changelog of file-rc > 0.8.13. Was this change intentional? If so, could you explain how the > conversion from file to links is supposed to work in the current > version so that we can debug further? Hi Michael, I'm afraid I can't remember the specifics off the top of my head; I'd have to review this work again to refresh my memory of the details. The reason for this change is that with file-rc now using insserv to maintain the links in part, it is not really meaningful to "restore" the links. Both file-rc and sysv-rc use insserv, and so when we switch between them, the state should remain identical. That is to say, that the changes effected by insserv (wrapped by update-rc.d/file-rc) are the state which should be preserved, which in practice means not doing anything at all. However... my memory may be bad here--I can't recall the extent to which we use insserv in file-rc for handling the links. I think the question to ask here is, why does the pattern of links make legacy_bootordering true, and why does activate_insserv fail? Is this at the point of running convert_rc_s_to_k or when running insserv? A little more detail about exactly what is failing here would be helpful. Regards, Roger -- .''`. Roger Leigh : :' : Debian GNU/Linuxhttp://people.debian.org/~rleigh/ `. `' schroot and sbuild http://alioth.debian.org/projects/buildd-tools `-GPG Public Key F33D 281D 470A B443 6756 147C 07B3 C8BC 4083 E800 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#699744: nagios3-cgi: prompting due to modified conffiles which were not modified by the user: /etc/nagios3/stylesheets/outages.css
On Tuesday, 5. February 2013 01:01:43 Vagrant Cascadian wrote: > As far as I can tell, /etc/nagios3/stylesheets/* were introduced in the > squeeze nagios3-cgi package. /etc/nagios3/cgi.cfg was a conffile with > nagios3-common in wheezy, and transitioned to nagios3-cgi for wheezy. My > guess is something wrong in the transition from nagios3-common to > nagios3-cgi for cgi.cfg, but I'm not sure what exactly is needed there. Changing the ownership of conffiles is not working really well, especially if the new version ships a conffile with modified content. There were several similar bugs, but luckily I don't remember any package :-) (go looking for fixed (and possibly archived bugs) with piuparts usertag and similar subjects) > Why my installation had no trouble with > /etc/nagios3/stylesheets/outages.css is a mystery to me. I did not use > piuparts, rather just used an schroot with lenny installed. I did do an > "apt-get upgrade" followed by an "apt-get dist-upgrade" in each of my > upgrade cycles, if that somehow matters. Also had etckeeper installed in > order to track the changes in configuration files, which pulled in a few > more package dependencies. piuparts has DEBIAN_FRONTEND=noninteractive set in the environment to not ask any debconf questions and only does apt-get dist-update. OK, I reran the test and kept the chroot to do manual analysis /tmp/piupartss/tmp3WkGdL # ls -la /etc/nagios3/stylesheets/ total 188 drwxr-xr-x 2 root root 720 Feb 5 22:36 . drwxr-xr-x 4 root root 200 Feb 5 22:36 .. -rw-r--r-- 1 root root 5040 Jul 3 2010 avail.css -rw-r--r-- 1 root root 1913 Jun 30 2012 avail.css.dpkg-new -rw-r--r-- 1 root root 2421 Jul 3 2010 checksanity.css -rw-r--r-- 1 root root 1261 Jun 30 2012 checksanity.css.dpkg-new -rw-r--r-- 1 root root 1643 Jul 3 2010 cmd.css -rw-r--r-- 1 root root 959 Jun 30 2012 cmd.css.dpkg-new -rw-r--r-- 1 root root 2961 Jul 3 2010 common.css -rw-r--r-- 1 root root 9562 Jun 30 2012 common.css.dpkg-new -rw-r--r-- 1 root root 1550 Jul 3 2010 config.css -rw-r--r-- 1 root root 586 Jun 30 2012 config.css.dpkg-new -rw-r--r-- 1 root root 8137 Jul 3 2010 extinfo.css -rw-r--r-- 1 root root 5626 Jun 30 2012 extinfo.css.dpkg-new -rw-r--r-- 1 root root 1943 Jul 3 2010 histogram.css -rw-r--r-- 1 root root 560 Jun 30 2012 histogram.css.dpkg-new -rw-r--r-- 1 root root 1601 Jul 3 2010 history.css -rw-r--r-- 1 root root 482 Jun 30 2012 history.css.dpkg-new -rw-r--r-- 1 root root 6634 Jul 3 2010 ministatus.css -rw-r--r-- 1 root root 4422 Jun 30 2012 ministatus.css.dpkg-new -rw-r--r-- 1 root root 2997 Jul 3 2010 notifications.css -rw-r--r-- 1 root root 2081 Jun 30 2012 notifications.css.dpkg-new -rw-r--r-- 1 root root 1792 Jul 3 2010 outages.css -rw-r--r-- 1 root root 743 Jun 30 2012 outages.css.dpkg-new -rw-r--r-- 1 root root 1400 Jul 3 2010 showlog.css -rw-r--r-- 1 root root 482 Jun 30 2012 showlog.css.dpkg-new -rw-r--r-- 1 root root 8638 Jul 3 2010 status.css -rw-r--r-- 1 root root 7283 Jun 30 2012 status.css.dpkg-new -rw-r--r-- 1 root root 1217 Jul 3 2010 statusmap.css -rw-r--r-- 1 root root 710 Jun 30 2012 statusmap.css.dpkg-new -rw-r--r-- 1 root root 3837 Jul 3 2010 summary.css -rw-r--r-- 1 root root 1748 Jun 30 2012 summary.css.dpkg-new -rw-r--r-- 1 root root 9480 Jul 3 2010 tac.css -rw-r--r-- 1 root root 5472 Jun 30 2012 tac.css.dpkg-new -rw-r--r-- 1 root root 1935 Jul 3 2010 trends.css -rw-r--r-- 1 root root 481 Jun 30 2012 trends.css.dpkg-new # md5sum /etc/nagios3/stylesheets/* c28401289fac0e58737e124938df229a /etc/nagios3/stylesheets/avail.css 739028581fac80d594dd83d2e3c3934f /etc/nagios3/stylesheets/avail.css.dpkg-new 04ab2d7edea942d839ed9ce7cd16085b /etc/nagios3/stylesheets/checksanity.css dc10b7e52b89928a81dfd0b267134654 /etc/nagios3/stylesheets/checksanity.css.dpkg-new 86ee04ba8d9272062d72a522df8b86a7 /etc/nagios3/stylesheets/cmd.css 6e9ad4a413ab336e699795cb6e0f084b /etc/nagios3/stylesheets/cmd.css.dpkg-new 30d44e331accf44db53781512b817bb4 /etc/nagios3/stylesheets/common.css b6b38b456a93a502e499f7c9c0c78caa /etc/nagios3/stylesheets/common.css.dpkg-new 30e8f1e9b15221f70f6ac74694fb36fd /etc/nagios3/stylesheets/config.css c31ee7f849f159313b89bb866a304daa /etc/nagios3/stylesheets/config.css.dpkg-new 4c80a8f2e823b95748199d59791235c6 /etc/nagios3/stylesheets/extinfo.css e008c51ee797e54069704104cc3a22a3 /etc/nagios3/stylesheets/extinfo.css.dpkg-new bb727613ecbf68feee6947992c63d97b /etc/nagios3/stylesheets/histogram.css b7eb620ad84f39129c617272fdfda00a /etc/nagios3/stylesheets/histogram.css.dpkg-new f81773311075beb6683ca791454aa144 /etc/nagios3/stylesheets/history.css 634f2c92876bb64eb54fe2f9e9e45b11 /etc/nagios3/stylesheets/history.css.dpkg-new 6326f1e3d18f0dd9bfa2293ecef5895a /etc/nagios3/stylesheets/ministatus.css aee1deb36d41f5fbc514fc09f1c423d4 /etc/nagios3/stylesheets/ministatus.css.dpkg-new 48aca7fd859e7ddca70fc4a449a30d40 /etc/nagios3/stylesheets/notifications.css f5c001e48b0bded60bf35b
Bug#688140: file-rc: File-rc doesn't restore rcX.d dirs at remove, breaks sysv-rc installation.
On Tue, 6 Nov 2012 20:46:25 +0100 Andreas Beckmann wrote: > On Wednesday, 19. September 2012 21:05:03 Piotr Borkowski wrote: > > File-rc doesn't restore rcX.d dirs at remove. This breaks sysv-rc > > legacy_bootordering postinst function. After sysv-rc installation > > this leads to empty rcX.d dirs and broken system. Maybe file-rc > > should call > > I can reproduce this problem in piuparts distupgrade tests, e.g. > setup squeeze (or wheezy) chroot > switch to file-rc > distupgrade to wheezy (or sid) > switch back to sysv-rc > > but not within a distro: > setup a squeeze (or wheezy or sid) chroot > switch to file-rc > switch back to sysv-rc > > curiously it also happens after a wheezy->sid distuprade, even if the > versions of sysv-rc and file-rc are the same in both sid and wheezy I haven’t tried to reproduce this issue yet, but I have figured out that in file-rc 0.8.13, the call to rcfile2link.sh was removed from debian/prerm: --- file-rc-0.8.12/debian/prerm 2010-04-07 21:30:54.0 +0200 +++ file-rc-0.8.13/debian/prerm 2012-07-30 07:49:08.0 +0200 @@ -19,7 +19,6 @@ case "$1" in remove) - /usr/share/file-rc/rcfile2link.sh ;; upgrade|deconfigure) ;; The changelog mentions: * Removed long obsolete logic (prior to oldstable) from maintainer scripts, which is no longer useful for upgrades. Roger: Your name was above the changes in the changelog of file-rc 0.8.13. Was this change intentional? If so, could you explain how the conversion from file to links is supposed to work in the current version so that we can debug further? Thanks! -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#698527: elmer: executable ElmerGUI.real links with both GPL-licensed and GPL-incompatible libraries
Hi, thanks for a huge work on this issue! I will be glad to upload it, if the release team agree to give a freeze exception for this upload. As far as I know, the package will not go to a NEW queue, because the binary package was deleted, not added. Thanks, Anton 2013/2/5 Boris Pek : > Hi, > > > I prepared updated package with changes described above. Diff is quite big > (see attachment) and I am still not sure that such changes are fit for > freeze exception and that such limited package will be useful. > > Also I should note after upload that package should go through NEW queue, > because package elmergui-samples was removed. > > Links: > > http://mentors.debian.net/debian/pool/main/e/elmerfem/elmerfem_6.1.0.svn.5396.dfsg2-2.dsc > > http://anonscm.debian.org/gitweb/?p=debian-science/packages/elmerfem.git;a=shortlog;h=refs/heads/wheezy > > Best regards, > Boris > > PS: diff file was produced using command: > $ debdiff elmerfem_6.1.0.svn.5396.dfsg2-1.dsc > elmerfem_6.1.0.svn.5396.dfsg2-2.dsc | \ > filterdiff -x '*debian/po/*' -x '*debian/patches/*.patch' > > elmerfem_6.1.0.svn.5396.dfsg2-1:6.1.0.svn.5396.dfsg2-2.diff -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#699856: marked as done (incorrectly refuses to authenticate in some circumstances)
Your message dated Tue, 05 Feb 2013 22:47:32 + with message-id and subject line Bug#699856: fixed in dynalogin 0.9.14-2 has caused the Debian Bug report #699856, regarding incorrectly refuses to authenticate in some circumstances 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.) -- 699856: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699856 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libdynalogin-1-0 Version: 0.9.14-1 Severity: serious In some circumstances, the algorithm fails to authenticate a valid user presenting a valid code. This appears to be occurring because the expected behavior of the oath_strcmp function is not identical to regular strcmp, negative return values are being handled as errors. There is no security risk or risk of giving access when a user should not have access. The solution involves testing the strcmp return value and is a minor change (~2 lines) --- End Message --- --- Begin Message --- Source: dynalogin Source-Version: 0.9.14-2 We believe that the bug you reported is fixed in the latest version of dynalogin, 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 699...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Daniel Pocock (supplier of updated dynalogin 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, 05 Feb 2013 23:25:37 +0100 Source: dynalogin Binary: libdynalogin-1-0 dynalogin-server dynalogin-client-php simpleid-store-dynalogin Architecture: source all amd64 Version: 0.9.14-2 Distribution: unstable Urgency: low Maintainer: Debian Authentication Maintainers Changed-By: Daniel Pocock Description: dynalogin-client-php - two-factor HOTP authentication - PHP client dynalogin-server - two-factor HOTP authentication - server daemon libdynalogin-1-0 - two-factor HOTP authentication - implementation libs simpleid-store-dynalogin - two-factor HOTP authentication - OpenID provider Closes: 699856 Changes: dynalogin (0.9.14-2) unstable; urgency=low . * Correct behavior of oath_callback (Closes: #699856) * Tweak title and description text * Update control file for migration from collab-maint to pkg-auth * Remove deprecated DM-Upload-Allowed Checksums-Sha1: 501a921a99bcc54722a71824e6cbc1c5035ac8bc 2184 dynalogin_0.9.14-2.dsc 823758e73da4113f883979958f2f387ec24474dd 4189 dynalogin_0.9.14-2.diff.gz e93a0f25bb3945757c614eb43fb65a91b817f523 2608 dynalogin-client-php_0.9.14-2_all.deb 4c2fd97de60beeec4678074eae46e20d2d0af3ae 9862 simpleid-store-dynalogin_0.9.14-2_all.deb 04c42e62e6053fed753bde0f6dd52d5c5c8a24ec 22828 libdynalogin-1-0_0.9.14-2_amd64.deb 61cc5d0528a06c860d1ac8bbb09bba31471ab6d2 12926 dynalogin-server_0.9.14-2_amd64.deb Checksums-Sha256: 00a574dcbc601d37ac1ed3e5dd46d913da18b3168b35b18a5e70b1825895adbf 2184 dynalogin_0.9.14-2.dsc cd830c50a205062acb27a9aa0982681f4488c6c5e89943aaa73162585c9da09f 4189 dynalogin_0.9.14-2.diff.gz faa623df168e66b43b53e621833179bbc6af11535ee511f2447eebd1962b8be2 2608 dynalogin-client-php_0.9.14-2_all.deb 316f717c2c19238cda921370d320889084afcc4dd7733e0038fb7baf569781ef 9862 simpleid-store-dynalogin_0.9.14-2_all.deb 37c436237074c427787555257767ab6dc426f119f9b32f76579718f7f3e1c445 22828 libdynalogin-1-0_0.9.14-2_amd64.deb ef4cc6a0aa4f68f210a5e624b42aade235972186b5698d0640519a37efab9f38 12926 dynalogin-server_0.9.14-2_amd64.deb Files: 705bee5ef588ce02c7cd4643796684b0 2184 admin optional dynalogin_0.9.14-2.dsc 2eab48218aedecbec532ba6e0f1982e9 4189 admin optional dynalogin_0.9.14-2.diff.gz ea173e5bd73729366a00199302afa586 2608 web optional dynalogin-client-php_0.9.14-2_all.deb bd8a86599e73e0f502e85f4e2585e6c8 9862 web optional simpleid-store-dynalogin_0.9.14-2_all.deb 44bcee723981c80e9df603768ba7f67d 22828 libs optional libdynalogin-1-0_0.9.14-2_amd64.deb 1c1a95d37e30ed36b77ea1103077ec6e 12926 admin optional dynalogin-server_0.9.14-2_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJREYjyAAoJEOm1uwJp1aqD5noQAJNKsdmSJFCf2Nvi8ei/OlZY 5N1vwI4ru5JP8RHs2YlPW/pEB327net3ZBKLQSMcriMVm/K/KM+gLFOtB6CH+Av4 GUbcS5QmEDiJMN/PVfYtZ1jA/9Co+sRMs5fPd
Bug#696187: marked as done (CVE-2012-5643: cachemgr.cgi denial of service)
Your message dated Tue, 05 Feb 2013 22:33:04 + with message-id and subject line Bug#696187: fixed in squid3 3.1.20-2.1 has caused the Debian Bug report #696187, regarding CVE-2012-5643: cachemgr.cgi denial of service 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.) -- 696187: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=696187 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: squid-cgi Version: 3.1.20-2 Severity: important Tags: security http://www.squid-cache.org/Advisories/SQUID-2012_1.txt http://www.openwall.com/lists/oss-security/2012/12/17/3 Problem Description: Due to missing input validation Squid cachemgr.cgi tool is vulnerable to a denial of service attack when processing specially crafted requests. - Henri Salo --- End Message --- --- Begin Message --- Source: squid3 Source-Version: 3.1.20-2.1 We believe that the bug you reported is fixed in the latest version of squid3, 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 696...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Stapelberg (supplier of updated squid3 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: SHA512 Format: 1.8 Date: Tue, 05 Feb 2013 23:16:27 +0100 Source: squid3 Binary: squid3 squid3-dbg squid3-common squidclient squid-cgi Architecture: source all amd64 Version: 3.1.20-2.1 Distribution: unstable Urgency: high Maintainer: Luigi Gangitano Changed-By: Michael Stapelberg Description: squid-cgi - Full featured Web Proxy cache (HTTP proxy) - control CGI squid3 - Full featured Web Proxy cache (HTTP proxy) squid3-common - Full featured Web Proxy cache (HTTP proxy) - common files squid3-dbg - Full featured Web Proxy cache (HTTP proxy) - Debug symbols squidclient - Full featured Web Proxy cache (HTTP proxy) - control utility Closes: 696187 Changes: squid3 (3.1.20-2.1) unstable; urgency=high . * Non-maintainer upload . * Urgency high due to security fixes . * debian/patches/30-CVE-2012-5643-CVE-2013-0189.patch - Added upstream fix for squid-cgi (cachemgr) memory leaks and denial of service vulnerability (Closes: #696187) Checksums-Sha1: a0ca698b161413fee7fe9c01aa28abd95dd9c629 2076 squid3_3.1.20-2.1.dsc ae6b931a399d398eaa37963a26f6ffc5c9f37f75 21881 squid3_3.1.20-2.1.debian.tar.gz a3e1806b1fc5f64f55c55bbd011f481cc477ce3a 200848 squid3-common_3.1.20-2.1_all.deb 3bdc5a1242dd21ab0b2ef9ae456bc5aeffcd4bfa 1638958 squid3_3.1.20-2.1_amd64.deb 87290672bf086fc3243bf31c97f48a763b8fe480 6960658 squid3-dbg_3.1.20-2.1_amd64.deb 73445f2b5e101478ce93ecfaecae058c93f2d3e2 111962 squidclient_3.1.20-2.1_amd64.deb b0dcc1f2701aef5086740f6286b1b2b959fdc494 115278 squid-cgi_3.1.20-2.1_amd64.deb Checksums-Sha256: 24d4937a3342d0cb6d4bcc21736f524974407ac813adff854190bf141b848f04 2076 squid3_3.1.20-2.1.dsc 6747e5c286a3f9735341ecfeee6a12d97cf327bf212029fd9fc0667417e2394b 21881 squid3_3.1.20-2.1.debian.tar.gz 037cd592139835d86014ede0d0af28b0ae95c55fb8ee26d99bed8ca1b9e4dd70 200848 squid3-common_3.1.20-2.1_all.deb b3eb3929183845f5da7490c93b3efc465c0cec4ce1cf504ae47aa2c08ee50e22 1638958 squid3_3.1.20-2.1_amd64.deb 324aee09f4cbbeed2cf6fea6ab98b1c28484a83aad92a77d74531a7b9fa9641d 6960658 squid3-dbg_3.1.20-2.1_amd64.deb 368eea78e5487c49b1fab06983e18deda9b8ae9650623a44ab19abef1468b254 111962 squidclient_3.1.20-2.1_amd64.deb 7e6123e334b79ff974e2a8548065c57630b6f55cf13b38eb5618f149b9d8d95f 115278 squid-cgi_3.1.20-2.1_amd64.deb Files: 8ebbfd2ee551c8480b40676bbe8a89d7 2076 web optional squid3_3.1.20-2.1.dsc 5c6cf0fbc64d59b2e79e056ab2376fa9 21881 web optional squid3_3.1.20-2.1.debian.tar.gz 5bb3503b67f93669181392bcf0e98527 200848 web optional squid3-common_3.1.20-2.1_all.deb 2516daa160e779a5ca87c6e812e9da13 1638958 web optional squid3_3.1.20-2.1_amd64.deb 03384d282ac70a02b704f8498e624621 6960658 debug extra squid3-dbg_3.1.20-2.1_amd64.deb 15167fcb596253441814ccdbd7411e69 111962 web optional squidclient_3.1.20-2.1_amd64.deb f1b0c8be7957d8edcf741a097efb5918 115278 web optional squid-cgi_3.1.20-2.1_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJREYUsAAoJEE5
Bug#699856: incorrectly refuses to authenticate in some circumstances
Package: libdynalogin-1-0 Version: 0.9.14-1 Severity: serious In some circumstances, the algorithm fails to authenticate a valid user presenting a valid code. This appears to be occurring because the expected behavior of the oath_strcmp function is not identical to regular strcmp, negative return values are being handled as errors. There is no security risk or risk of giving access when a user should not have access. The solution involves testing the strcmp return value and is a minor change (~2 lines) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#696187: CVE-2012-5643: cachemgr.cgi denial of service
On Tue, 22 Jan 2013 17:37:10 +0100 Moritz Muehlenhoff wrote: > Note that the initial fix was incorrect: > https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2013-0189 I have integrated this upstream patch (which adresses CVE-2012-5643 and CVE-2013-0189): http://www.squid-cache.org/Versions/v3/3.1/changesets/SQUID-2012_1.patch Because the maintainer has not reacted to this bugreport at all for nearly 2 months, I have directly NMUed the package. -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 697588
Processing commands for cont...@bugs.debian.org:
> tags 697588 + wheezy sid
Bug #697588 {Done: Colin Watson } [pyparted] Breaks
python-parted
Added tag(s) sid and wheezy.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
697588: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=697588
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#699853: icedove-gcontactsync: incompatibility with icedove-10.0.12
Package: icedove-gcontactsync Version: 0.2.8-1 Severity: grave Justification: renders package unusable unable to use this addon after upgrading icedove to 10.0.12 from squeeze- backports. Icedove complains that this version is incompatible. -- System Information: Debian Release: 6.0.6 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-0.bpo.4-amd64 (SMP w/2 CPU cores) Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages icedove-gcontactsync depends on: ii icedove10.0.12-1~bpo60+1 mail/news client with RSS and inte icedove-gcontactsync recommends no packages. icedove-gcontactsync 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#699852: syncevolution-http: sync from nokia e51 to syncevo-http-server not possible "invalid server" "[ERROR] twisted: Unhandled Error"
Package: syncevolution-http Version: 1.2.99.1-1 Severity: grave Justification: renders package unusable Dear Maintainer, * What led up to the situation? 1. set up synceo-http-server according to https://syncevolution.org/wiki/http-server-howto including https. 2. trigger sync from my phone (nokia e51) having the addressbook datasource active * What was the outcome of this action? sync stopped, the phone returns "invalid server" and the server prints out below log. * What outcome did you expect instead? * synchronisation should work. >From the syncevolution-mailinglist I got the remark by Patrick Ohly: = Probably a known and fixed timing issue with registering on D-Bus. You are probably running Debian Testing? Please install 1.3 from syncevolution.org, there's an apt repository. *** End of the template - remove these lines *** Logfile of server: [ERROR] twisted: Unhandled Error Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/twisted/web/http.py", line 1349, in dataReceived finishCallback(data[contentLength:]) File "/usr/lib/python2.7/dist-packages/twisted/web/http.py", line 1563, in _finishRequestBody self.allContentReceived() File "/usr/lib/python2.7/dist-packages/twisted/web/http.py", line 1618, in allContentReceived req.requestReceived(command, path, version) File "/usr/lib/python2.7/dist-packages/twisted/web/http.py", line 773, in requestReceived self.process() --- --- File "/usr/lib/python2.7/dist-packages/twisted/web/server.py", line 132, in process self.render(resrc) File "/usr/lib/python2.7/dist-packages/twisted/web/server.py", line 167, in render body = resrc.render(self) File "/usr/lib/python2.7/dist-packages/twisted/web/resource.py", line 216, in render return m(request) File "/usr/bin/syncevo-http-server", line 302, in render_POST urlparse.urljoin(self.url.geturl(), request.path)) File "/usr/bin/syncevo-http-server", line 218, in start '') File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 70, in __call__ return self._proxy_method(*args, **keywords) File "/usr/lib/python2.7/dist-packages/dbus/proxies.py", line 145, in __call__ **keywords) File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 651, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: No such interface `org.syncevolution.Server' on object at path /org/syncevolution/Server [DEBUG] twisted: 213.211.219.200 - - [05/Feb/2013:20:22:52 +] "POST /sync HTTP/1.1" 500 9391 "-" "Nokia SyncML HTTP Client" [DEBUG] syncevo-http: done with request in session None, error None [DEBUG] sync: /org/syncevolution/Server: http presence signal funambol,no transport,https://kdserv.dyndns.org:8443/funambol/ds [DEBUG] sync: /org/syncevolution/Server: http presence signal target-config,no transport,http://yourserver:port [WARNING] sync: /org/syncevolution/Server: libnotify: Failed to connect to proxy [DEBUG] sync: /org/syncevolution/Server: auto sync: updating info about config christofphon [DEBUG] sync: /org/syncevolution/Server: auto sync: christofphon: auto sync '0', no Bluetooth, no HTTP, 1800 seconds repeat interval, 300 seconds online delay [DEBUG] sync: /org/syncevolution/Server: auto sync: reschedule, initConfig() for christofphon [DEBUG] sync: /org/syncevolution/Server: auto sync: nothing to do [DEBUG] sync: /org/syncevolution/Server: auto sync: updating info about config funambol [DEBUG] sync: /org/syncevolution/Server: auto sync: funambol: auto sync '0', no Bluetooth, no HTTP, 1800 seconds repeat interval, 300 seconds online delay [DEBUG] sync: /org/syncevolution/Server: auto sync: reschedule, initConfig() for funambol [DEBUG] sync: /org/syncevolution/Server: auto sync: nothing to do [DEBUG] sync: /org/syncevolution/Server: auto sync: updating info about config target-config [DEBUG] sync: /org/syncevolution/Server: auto sync: target-config: auto sync '0', no Bluetooth, no HTTP, 1800 seconds repeat interval, 300 seconds online delay [DEBUG] sync: /org/syncevolution/Server: auto sync: reschedule, initConfig() for target-config [DEBUG] sync: /org/syncevolution/Server: auto sync: nothing to do [DEBUG] sync: /org/syncevolution/Server: D-Bus server ready to run, versions: [DEBUG] sync: /org/syncevolution/Server: backends: Loading backend library /usr/lib/syncevolution/backends/platformkde.so Loading backend library /usr/lib/syncevolution/backends/syncxmlrpc.so Loading backend library /usr/lib/syncevolution/backends/syncfile.so Loading backend library /usr/lib/syncevolution/backends/syncebook.so Loading backend library /usr/lib/syncevolution/backends/synckcalextended.so Loading backend library /usr/lib/syncevolution/backends/syncqtcontacts.so Loading backend library /usr/lib/syncevolution/backends/syncactivesync.so Loading backend library /usr/lib/syncevolution/backends/syncsqlite.so Loading
Bug#699379: marked as done (gdcm: remove armhf from mono archs)
Your message dated Tue, 05 Feb 2013 20:47:53 + with message-id and subject line Bug#699379: fixed in gdcm 2.2.1-1.1 has caused the Debian Bug report #699379, regarding gdcm: remove armhf from mono archs 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.) -- 699379: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699379 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gdcm Version: 2.2.0-13 Severity: serious mono packages are being removed on armhf in wheezy, please update gdcm to match. Cheers, Julien signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: gdcm Source-Version: 2.2.1-1.1 We believe that the bug you reported is fixed in the latest version of gdcm, 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 699...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Cristau (supplier of updated gdcm 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, 05 Feb 2013 19:25:05 +0100 Source: gdcm Binary: libgdcm2.2 libgdcm-tools libgdcm2-dev libgdcm2.2-dbg libgdcm-cil php5-gdcm libgdcm-java python-gdcm libvtkgdcm2.2 libvtkgdcm2-dev libvtkgdcm-cil php5-vtkgdcm libvtkgdcm-java python-vtkgdcm libvtkgdcm-tools gdcm-doc Architecture: source amd64 all Version: 2.2.1-1.1 Distribution: sid Urgency: low Maintainer: Debian Med Packaging Team Changed-By: Julien Cristau Description: gdcm-doc - Grassroots DICOM documentation libgdcm-cil - Grassroots DICOM CLI bindings libgdcm-java - Grassroots DICOM Java bindings libgdcm-tools - Grassroots DICOM tools and utilities libgdcm2-dev - Grassroots DICOM development libraries and headers libgdcm2.2 - Grassroots DICOM runtime libraries libgdcm2.2-dbg - Grassroots DICOM runtime libraries, debug version libvtkgdcm-cil - Grassroots DICOM VTK CLI bindings libvtkgdcm-java - Grassroots DICOM VTK Java bindings libvtkgdcm-tools - Grassroots DICOM VTK tools and utilities libvtkgdcm2-dev - Grassroots DICOM VTK development libraries and headers libvtkgdcm2.2 - Grassroots DICOM VTK runtime libraries php5-gdcm - Grassroots DICOM PHP5 bindings php5-vtkgdcm - Grassroots DICOM VTK PHP bindings python-gdcm - Grassroots DICOM Python bindings python-vtkgdcm - Grassroots DICOM VTK/Python bindings Closes: 699379 Changes: gdcm (2.2.1-1.1) sid; urgency=low . * Non-maintainer upload. * Remove armhf from mono architectures (closes: #699379) Checksums-Sha1: 5cb7c1db488c4e1142a7f462c69cda4d5c0f6312 3440 gdcm_2.2.1-1.1.dsc 333ce36c3b21ebb8f18841869f14fe1bc5d1756c 18048 gdcm_2.2.1-1.1.debian.tar.xz 42fa8a7586ed15a251b704eb0d7573cd1614d3f7 2514476 libgdcm2.2_2.2.1-1.1_amd64.deb 24f075b1ea43afb25d9cc70b4bb9aa3426b468f5 328794 libgdcm-tools_2.2.1-1.1_amd64.deb eec621639d01fbc6d8e5096c28fa4968e8fc4d25 377998 libgdcm2-dev_2.2.1-1.1_amd64.deb b4244b889dc60aeb16dd74a31bbeeb91d185f271 25074904 libgdcm2.2-dbg_2.2.1-1.1_amd64.deb 9c4a53df3a0156e71176cf2988d3abb062eb9fe2 360694 libgdcm-cil_2.2.1-1.1_amd64.deb e0b362b8f9c0ae776275a966eb15c99b8cd2 376972 php5-gdcm_2.2.1-1.1_amd64.deb 37c83420ea5d06f16e152608f7c21fedcef5f8d8 514408 libgdcm-java_2.2.1-1.1_amd64.deb ad8b18d7c223c6bcff6cc3aa659a4f213960762c 774954 python-gdcm_2.2.1-1.1_amd64.deb 40c4627a2c7e07fd44af37af8a7458060ac83ba1 284854 libvtkgdcm2.2_2.2.1-1.1_amd64.deb 92e8f18f5969d9f479472099f88644ea6983b698 30034 libvtkgdcm2-dev_2.2.1-1.1_amd64.deb 0a0e5037d6e920b3e4e9a82438cbe2cafbe34e55 48524 libvtkgdcm-cil_2.2.1-1.1_amd64.deb 00e2e3a5678e25597703f416d29883784edf7a2a 202910 php5-vtkgdcm_2.2.1-1.1_amd64.deb 52b4211d80b84329d9fe4075602aabddfff85d51 46910 libvtkgdcm-java_2.2.1-1.1_amd64.deb 5d58125b4737515e748a02b2aaad3505d1a05be2 81886 python-vtkgdcm_2.2.1-1.1_amd64.deb 9bd05513f240cb1021fb93866c4c71870417cb81 52986 libvtkgdcm-tools_2.2.1-1.1_amd64.deb da29cf266b42757a47e40d78b04901c0abad1b5e 11084558 gdcm-doc_2.2.1-1.1_all.deb Checksums-Sha256: c89b74acac229dc9371a3a3055ea686ce6c4e40b47396568e364152af6a18e02 3440 gdcm_2.2.1-1.1.dsc 4af0d254a99b22b83320e151a583021480886d4e051bc82726b947ddfba53cf2 18048 gdcm_2.2.1-1.1.debian.tar.xz 73ccaf65a
Bug#699379: marked as done (gdcm: remove armhf from mono archs)
Your message dated Tue, 05 Feb 2013 20:47:38 + with message-id and subject line Bug#699379: fixed in gdcm 2.2.0-14.1 has caused the Debian Bug report #699379, regarding gdcm: remove armhf from mono archs 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.) -- 699379: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699379 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: gdcm Version: 2.2.0-13 Severity: serious mono packages are being removed on armhf in wheezy, please update gdcm to match. Cheers, Julien signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: gdcm Source-Version: 2.2.0-14.1 We believe that the bug you reported is fixed in the latest version of gdcm, 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 699...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Julien Cristau (supplier of updated gdcm 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, 05 Feb 2013 20:47:03 +0100 Source: gdcm Binary: libgdcm2.2 libgdcm-tools libgdcm2-dev libgdcm2.2-dbg libgdcm-cil php5-gdcm libgdcm-java python-gdcm libvtkgdcm2.2 libvtkgdcm2-dev libvtkgdcm-cil php5-vtkgdcm libvtkgdcm-java python-vtkgdcm libvtkgdcm-tools gdcm-doc Architecture: source amd64 all Version: 2.2.0-14.1 Distribution: wheezy Urgency: low Maintainer: Debian Med Packaging Team Changed-By: Julien Cristau Description: gdcm-doc - Grassroots DICOM documentation libgdcm-cil - Grassroots DICOM CLI bindings libgdcm-java - Grassroots DICOM Java bindings libgdcm-tools - Grassroots DICOM tools and utilities libgdcm2-dev - Grassroots DICOM development libraries and headers libgdcm2.2 - Grassroots DICOM runtime libraries libgdcm2.2-dbg - Grassroots DICOM runtime libraries, debug version libvtkgdcm-cil - Grassroots DICOM VTK CLI bindings libvtkgdcm-java - Grassroots DICOM VTK Java bindings libvtkgdcm-tools - Grassroots DICOM VTK tools and utilities libvtkgdcm2-dev - Grassroots DICOM VTK development libraries and headers libvtkgdcm2.2 - Grassroots DICOM VTK runtime libraries php5-gdcm - Grassroots DICOM PHP5 bindings php5-vtkgdcm - Grassroots DICOM VTK PHP bindings python-gdcm - Grassroots DICOM Python bindings python-vtkgdcm - Grassroots DICOM VTK/Python bindings Closes: 699379 Changes: gdcm (2.2.0-14.1) wheezy; urgency=low . * Non-maintainer upload. * Remove the other half of armhf from mono supported list (closes: #699379) Checksums-Sha1: bf3f683251ae1ae0938384bcd5420e4017433349 3444 gdcm_2.2.0-14.1.dsc 840413cf3525057a36d22d7f7693dd5ed9b467df 34605 gdcm_2.2.0-14.1.debian.tar.gz 74de021b2d5c3c7dad03952faf53628339673a43 2475766 libgdcm2.2_2.2.0-14.1_amd64.deb 654dab20631414832e6bf4decf4e9768fccd6210 326884 libgdcm-tools_2.2.0-14.1_amd64.deb 39040cd045ba6143098472bfd4611cef91ed9c56 374988 libgdcm2-dev_2.2.0-14.1_amd64.deb a9c8492bd3b0db5349f643272e175d14a8450382 23588616 libgdcm2.2-dbg_2.2.0-14.1_amd64.deb 94410704133b7153e501be8bd33a7db7a9adb6c3 301264 libgdcm-cil_2.2.0-14.1_amd64.deb 36b5356d90a7d5c8737b82bf261571b7b67f0672 376080 php5-gdcm_2.2.0-14.1_amd64.deb 41ba28312fe690d90cbdb8b707ac1888d8c04cae 458518 libgdcm-java_2.2.0-14.1_amd64.deb ffc25ab2ce46cf9a84540e5636f51a776177f696 594532 python-gdcm_2.2.0-14.1_amd64.deb 75c4ea8d3b0c684c5dc021c43b586fd7342a8333 282996 libvtkgdcm2.2_2.2.0-14.1_amd64.deb 09233ad24b7faa6592fdb172af1f8ba3f26837ef 29962 libvtkgdcm2-dev_2.2.0-14.1_amd64.deb fdfa35d0a5211a6eebb7038dcc8bf6653538421d 48388 libvtkgdcm-cil_2.2.0-14.1_amd64.deb b542c64eec3b959a9996035b1ee52b9259665ff8 202836 php5-vtkgdcm_2.2.0-14.1_amd64.deb 89ba6125db56265c84d5b46f90ce9240315913f6 46856 libvtkgdcm-java_2.2.0-14.1_amd64.deb 3340c50986ab2a190698df292308357986965f55 81812 python-vtkgdcm_2.2.0-14.1_amd64.deb 590a23b74621e63eaaa1811f02316d4fde71504b 50888 libvtkgdcm-tools_2.2.0-14.1_amd64.deb 7cdced46c50a9539b46f1393daaf175d0e2da732 11006298 gdcm-doc_2.2.0-14.1_all.deb Checksums-Sha256: 15a3df0362ebc131fc17221c29c2b87b94910eb7d1265048d643de5d502da6aa 3444 gdcm_2.2.0-14.1.dsc a0c9226bcb2a16312ab7bff5f0e89a773a21f21a22f9b616e4e3fc34b446
Bug#698527: elmer: executable ElmerGUI.real links with both GPL-licensed and GPL-incompatible libraries
Hi, >> Did you try to send your messages directly to email >> or another? > > No, I didn't. > > I am under the impression that OCE (OpenCASCADE Community Edition) > is a project to enhance Open CASCADE Technology with external > contributions not (yet) accepted by Open CASCADE S.A.S. into the > official OCCT releases. > It is my understanding that OCE is an unofficial project maintained and > coordinated outside Open CASCADE S.A.S. Yes. But you were searching people to help you in persuading of upstream. And you might find few interested persons in this mailing list. Best wishes, Boris -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#698527: elmer: executable ElmerGUI.real links with both GPL-licensed and GPL-incompatible libraries
Hi, > I propose to remove executable ElmerGUI.real from the package. Anyway, > it is better, than to remove the whole package. > > But we need to get a pre-approval permission from release-managers. > Could you, please, provide a patch? I prepared updated package with changes described above. Diff is quite big (see attachment) and I am still not sure that such changes are fit for freeze exception and that such limited package will be useful. Also I should note after upload that package should go through NEW queue, because package elmergui-samples was removed. Links: http://mentors.debian.net/debian/pool/main/e/elmerfem/elmerfem_6.1.0.svn.5396.dfsg2-2.dsc http://anonscm.debian.org/gitweb/?p=debian-science/packages/elmerfem.git;a=shortlog;h=refs/heads/wheezy Best regards, Boris PS: diff file was produced using command: $ debdiff elmerfem_6.1.0.svn.5396.dfsg2-1.dsc elmerfem_6.1.0.svn.5396.dfsg2-2.dsc | \ filterdiff -x '*debian/po/*' -x '*debian/patches/*.patch' > elmerfem_6.1.0.svn.5396.dfsg2-1:6.1.0.svn.5396.dfsg2-2.diff elmerfem_6.1.0.svn.5396.dfsg2-1:6.1.0.svn.5396.dfsg2-2.diff Description: Binary data
Bug#684645: Patch
Hi Jakub, Since you intend to adopt the sendmail package, can you have a look at the patch which Tim posted at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684645#43 please? If you need a sponsor for your upload, I can help you with that. -- Best regards, Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#699379: gdcm: diff for NMU version 2.2.0-14.1
Hi Mathieu,
I've prepared an NMU for gdcm for wheezy (versioned as 2.2.0-14.1) and
will upload shortly (well, once it's finished building anyway). Diff
against the current tpu version attached.
Cheers,
Julien
diff -Nru gdcm-2.2.0/debian/changelog gdcm-2.2.0/debian/changelog
--- gdcm-2.2.0/debian/changelog 2013-02-02 09:31:40.0 +0100
+++ gdcm-2.2.0/debian/changelog 2013-02-05 20:52:03.0 +0100
@@ -1,3 +1,10 @@
+gdcm (2.2.0-14.1) wheezy; urgency=low
+
+ * Non-maintainer upload.
+ * Remove the other half of armhf from mono supported list (closes: #699379)
+
+ -- Julien Cristau Tue, 05 Feb 2013 20:47:03 +0100
+
gdcm (2.2.0-14) testing-proposed-updates; urgency=low
* Remove armhf from mono supported list
diff -Nru gdcm-2.2.0/debian/control gdcm-2.2.0/debian/control
--- gdcm-2.2.0/debian/control 2013-02-02 09:30:36.0 +0100
+++ gdcm-2.2.0/debian/control 2013-02-05 20:46:36.0 +0100
@@ -77,7 +77,7 @@
Package: libgdcm-cil
Section: cli-mono
-Architecture: amd64 armel armhf i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc ppc64 s390x sparc
+Architecture: amd64 armel i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc ppc64 s390x sparc
Depends: ${shlibs:Depends}, ${misc:Depends}, ${cli:Depends}
Description: Grassroots DICOM CLI bindings
Grassroots DiCoM is a C++ library for DICOM medical files. It is
@@ -150,7 +150,7 @@
Package: libvtkgdcm-cil
Section: cli-mono
-Architecture: amd64 armel armhf i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc ppc64 s390x sparc
+Architecture: amd64 armel i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc ppc64 s390x sparc
Depends: ${shlibs:Depends}, ${misc:Depends}, ${cli:Depends}, libgdcm2.2 (= ${binary:Version})
Suggests: libgdcm-cil
Description: Grassroots DICOM VTK CLI bindings
signature.asc
Description: Digital signature
Bug#699564: marked as done ([flush] Starting Flush failed:)
Your message dated Tue, 5 Feb 2013 20:35:00 +0100 with message-id <20130205193500.GA18755@localhost> and subject line Done: [flush] Starting Flush failed: has caused the Debian Bug report #699564, regarding [flush] Starting Flush failed: 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.) -- 699564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699564 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: flush Version: 0.9.12-3 Severity: grave --- Please enter the report below this line. --- Hi, I just installed flush and want to run it, but get the message: Starting Flush failed: Creating Flush session failed. Can't get DBus session bus address. On the console from where I started flush, I get output: $ flush (flush:29648): GLib-WARNING **: /tmp/buildd/glib2.0-2.33.12+really2.32.4/./glib/goption.c:2179: ignoring no-arg, optional-arg or filename flags (8) on option of arg-type 0 in entry main:version (flush:29648): GLib-WARNING **: /tmp/buildd/glib2.0-2.33.12+really2.32.4/./glib/goption.c:2179: ignoring no-arg, optional-arg or filename flags (16) on option of arg-type 4 in entry main:config (flush:29648): GLib-WARNING **: /tmp/buildd/glib2.0-2.33.12+really2.32.4/./glib/goption.c:2179: ignoring no-arg, optional-arg or filename flags (8) on option of arg-type 0 in entry main:only-pass W: Creating Flush session failed. Can't get DBus session bus address. csanyipal@debian-asztal:~$ flush (flush:29824): GLib-WARNING **: /tmp/buildd/glib2.0-2.33.12+really2.32.4/./glib/goption.c:2179: ignoring no-arg, optional-arg or filename flags (8) on option of arg-type 0 in entry main:version (flush:29824): GLib-WARNING **: /tmp/buildd/glib2.0-2.33.12+really2.32.4/./glib/goption.c:2179: ignoring no-arg, optional-arg or filename flags (16) on option of arg-type 4 in entry main:config (flush:29824): GLib-WARNING **: /tmp/buildd/glib2.0-2.33.12+really2.32.4/./glib/goption.c:2179: ignoring no-arg, optional-arg or filename flags (8) on option of arg-type 0 in entry main:only-pass W: Creating Flush session failed. Can't get DBus session bus address. Any hint to solve this problem? --- System information. --- Architecture: amd64 Kernel: Linux 3.2.0-4-amd64 Debian Release: 7.0 500 unstablewww.deb-multimedia.org 500 unstableftp.debian.org 500 unstabledebian.scribus.net 500 testing www.deb-multimedia.org 500 testing http.us.debian.org 500 testing ftp.debian.org 500 stable dl.google.com 1 experimentalftp.debian.org --- Package information. --- Depends (Version) | Installed ===-+-== libatkmm-1.6-1 (>= 2.22.1) | 2.22.6-1 libboost-filesystem1.49.0 (>= 1.49.0-1) | 1.49.0-3.1 libboost-signals1.49.0(>= 1.49.0-1) | 1.49.0-3.1 libboost-system1.49.0 (>= 1.49.0-1) | 1.49.0-3.1 libboost-thread1.49.0 (>= 1.49.0-1) | 1.49.0-3.1 libc6 (>= 2.4) | libconfig++9| libdbus-1-3 (>= 1.1.1) | libgcc1(>= 1:4.1.1) | libglademm-2.4-1c2a (>= 2.6.0) | libglib2.0-0(>= 2.16.0) | libglibmm-2.4-1c2a (>= 2.31.22) | libgtk2.0-0 (>= 2.8.0) | libgtkmm-2.4-1c2a (>= 1:2.24.0) | libnotify4 (>= 0.7.0) | libsigc++-2.0-0c2a (>= 2.0.2) | libssl1.0.0 (>= 1.0.0) | libstdc++6 (>= 4.6) | libtorrent-rasterbar6 (>= 0.15.10) | hicolor-icon-theme | Package's Recommends field is empty. Package's Suggests field is empty. -- Regards from Pal --- End Message --- --- Begin Message --- Package: flush Version: 0.9.12-3 --- Please enter the report below this line. --- Dear Sébastien, After I installed docker and set up ~/.xinitrc: eval `dbus-launch --exit-with-session --sh-syntax` everything works as one can expected. Thanks! -- Regards from Pal--- End Message ---
Processed: Re: Processed: Re: Bug#699785: virtuoso-opensource: may FTBFS depending on time of day
Processing commands for cont...@bugs.debian.org: > # Package is built now; no longer seems RC for wheezy > tags 699785 = sid Bug #699785 [src:virtuoso-opensource] virtuoso-opensource: may FTBFS depending on time of day Added tag(s) sid; removed tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 699785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699785 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: gdcm: diff for NMU version 2.2.1-1.1
Processing commands for cont...@bugs.debian.org: > tags 699379 + patch Bug #699379 [src:gdcm] gdcm: remove armhf from mono archs Added tag(s) patch. > tags 699379 + pending Bug #699379 [src:gdcm] gdcm: remove armhf from mono archs Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 699379: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699379 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: Re: Bug#699785: virtuoso-opensource: may FTBFS depending on time of day
Processing control commands: > tags -1 - wheezy Bug #699785 [src:virtuoso-opensource] virtuoso-opensource: may FTBFS depending on time of day Ignoring request to alter tags of bug #699785 to the same tags previously set -- 699785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699785 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#699785: virtuoso-opensource: may FTBFS depending on time of day
Control: tags -1 - wheezy The package is built on all arches for now. But if there is going to be another upload, please fix this issue to avoid stalling the buildds. It is a recurrence of this problem: http://bugs.debian.org/581267#5 (Shortening the timeouts made it less likely to happen, but now we have found the true cause of it I think). Thanks! Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#699379: gdcm: diff for NMU version 2.2.1-1.1
tags 699379 + patch
tags 699379 + pending
thanks
Hi Mathieu,
I've prepared an NMU for gdcm (versioned as 2.2.1-1.1) and
will upload it shortly.
Cheers,
Julien
diff -Nru gdcm-2.2.1/debian/changelog gdcm-2.2.1/debian/changelog
--- gdcm-2.2.1/debian/changelog 2012-09-20 16:25:49.0 +0200
+++ gdcm-2.2.1/debian/changelog 2013-02-05 19:25:07.0 +0100
@@ -1,3 +1,10 @@
+gdcm (2.2.1-1.1) sid; urgency=low
+
+ * Non-maintainer upload.
+ * Remove armhf from mono architectures (closes: #699379)
+
+ -- Julien Cristau Tue, 05 Feb 2013 19:25:05 +0100
+
gdcm (2.2.1-1) unstable; urgency=low
* New upstream: 2.2.1. Update to lastest DICOM standard (2011)
diff -Nru gdcm-2.2.1/debian/control gdcm-2.2.1/debian/control
--- gdcm-2.2.1/debian/control 2012-06-14 16:44:22.0 +0200
+++ gdcm-2.2.1/debian/control 2013-02-05 19:24:26.0 +0100
@@ -10,10 +10,10 @@
swig (>= 2.0.7), cmake (>= 2.6.2), libvtk5-dev, libcharls-dev, javahelper,
libopenjpeg-dev, graphviz, default-jdk, php5-dev, php5-cli,
libpoppler-private-dev, libssl-dev, python-vtk, gccxml,
- libactiviz.net-cil [amd64 armel armhf i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc ppc64 s390x sparc],
- mummy [amd64 armel armhf i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc ppc64 s390x sparc],
- cli-common-dev (>= 0.8~) [amd64 armel armhf i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc ppc64 s390x sparc],
- mono-devel (>= 2.10.5) [amd64 armel armhf i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc ppc64 s390x sparc]
+ libactiviz.net-cil [amd64 armel i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc ppc64 s390x sparc],
+ mummy [amd64 armel i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc ppc64 s390x sparc],
+ cli-common-dev (>= 0.8~) [amd64 armel i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc ppc64 s390x sparc],
+ mono-devel (>= 2.10.5) [amd64 armel i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc ppc64 s390x sparc]
Build-Depends-Indep: vtk-doc
Standards-Version: 3.9.3
X-Python-Version: 2.7
@@ -77,7 +77,7 @@
Package: libgdcm-cil
Section: cli-mono
-Architecture: amd64 armel armhf i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc ppc64 s390x sparc
+Architecture: amd64 armel i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc ppc64 s390x sparc
Depends: ${shlibs:Depends}, ${misc:Depends}, ${cli:Depends}
Description: Grassroots DICOM CLI bindings
Grassroots DiCoM is a C++ library for DICOM medical files. It is
@@ -150,7 +150,7 @@
Package: libvtkgdcm-cil
Section: cli-mono
-Architecture: amd64 armel armhf i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc ppc64 s390x sparc
+Architecture: amd64 armel i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc ppc64 s390x sparc
Depends: ${shlibs:Depends}, ${misc:Depends}, ${cli:Depends}, libgdcm2.2 (= ${binary:Version})
Suggests: libgdcm-cil
Description: Grassroots DICOM VTK CLI bindings
signature.asc
Description: Digital signature
Bug#699837: scrub[kfreebsd]: error: conflicting types for 'getsize'
Package: src:scrub Version: 2.5.2-1 Severity: serious Tags: sid wheezy User: debian-...@lists.debian.org Usertags: kfreebsd X-Debbugs-Cc: debian-...@lists.debian.org Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the kfreebsd-* buildds: gcc -DHAVE_CONFIG_H -I. -I../config -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c getsize.c getsize.c:235:1: error: conflicting types for 'getsize' In file included from getsize.c:40:0: getsize.h:27:5: note: previous declaration of 'getsize' was here make[2]: *** [getsize.o] Error 1 Full build log at https://buildd.debian.org/status/fetch.php?pkg=scrub&arch=kfreebsd-amd64&ver=2.5.2-1&stamp=1359617916 Regards Christoph If you have further questions please mail debian-...@lists.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#699836: kshutdown[kfreebsd]: error: 'getQDBusInterface' is not a member of 'LockAction'
Package: src:kshutdown Version: 3.0~beta5-2 Severity: serious Tags: sid wheezy User: debian-...@lists.debian.org Usertags: kfreebsd X-Debbugs-Cc: debian-...@lists.debian.org Justification: fails to build from source (but built successfully in the past) Hi! Your package failed to build on the kfreebsd-* buildds: [ 60%] Building CXX object src/CMakeFiles/kshutdown.dir/triggers/idlemonitor.o cd "/build/buildd-kshutdown_3.0~beta5-2-kfreebsd-i386-i1VDIh/kshutdown-3.0~beta5/obj-i486-kfreebsd-gnu/src" && /usr/bin/g++ -D_GNU_SOURCE -DQT_NO_STL -DQT_NO_CAST_TO_ASCII -D_REENTRANT -DKDE_DEPRECATED_WARNINGS -DKDE4_CMAKE_TOPLEVEL_DIR_LENGTH=56 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -Wall -D_FORTIFY_SOURCE=2 -Woverloaded-virtual -fno-threadsafe-statics -fvisibility=hidden -Werror=return-type -fvisibility-inlines-hidden -DNDEBUG -DQT_NO_DEBUG -I/usr/include/KDE -I/usr/include/qt4/phonon -I/usr/include/qt4/QtXmlPatterns -I/usr/include/qt4/QtXml -I/usr/include/qt4/QtUiTools -I/usr/include/qt4/QtTest -I/usr/include/qt4/QtSvg -I/usr/include/qt4/QtSql -I/usr/include/qt4/QtScriptTools -I/usr/include/qt4/QtScript -I/usr/include/qt4/QtNetwork -I/usr/include/qt4/QtHelp -I/usr/include/qt4/QtDesigner -I/usr/include/qt4/QtDeclarative -I/usr/include/qt4/QtDBus -I/usr/include/qt4/Qt3Support -I/usr/include/qt4/QtGui -I/usr/include/qt4/QtCore -I/usr/include/qt4/Qt -I/usr/share/qt4/mkspecs/default -I/usr/include/qt4 -I"/build/buildd-kshutdown_3.0~beta5-2-kfreebsd-i386-i1VDIh/kshutdown-3.0~beta5/obj-i486-kfreebsd-gnu/src" -o CMakeFiles/kshutdown.dir/triggers/idlemonitor.o -c "/build/buildd-kshutdown_3.0~beta5-2-kfreebsd-i386-i1VDIh/kshutdown-3.0~beta5/src/triggers/idlemonitor.cpp" /build/buildd-kshutdown_3.0~beta5-2-kfreebsd-i386-i1VDIh/kshutdown-3.0~beta5/src/triggers/idlemonitor.cpp: In constructor 'IdleMonitor::IdleMonitor()': /build/buildd-kshutdown_3.0~beta5-2-kfreebsd-i386-i1VDIh/kshutdown-3.0~beta5/src/triggers/idlemonitor.cpp:56:16: error: 'getQDBusInterface' is not a member of 'LockAction' /build/buildd-kshutdown_3.0~beta5-2-kfreebsd-i386-i1VDIh/kshutdown-3.0~beta5/src/triggers/idlemonitor.cpp: In member function 'void IdleMonitor::getSessionIdleTime()': /build/buildd-kshutdown_3.0~beta5-2-kfreebsd-i386-i1VDIh/kshutdown-3.0~beta5/src/triggers/idlemonitor.cpp:177:30: error: 'getQDBusInterface' is not a member of 'LockAction' make[3]: *** [src/CMakeFiles/kshutdown.dir/triggers/idlemonitor.o] Error 1 make[3]: Leaving directory `/build/buildd-kshutdown_3.0~beta5-2-kfreebsd-i386-i1VDIh/kshutdown-3.0~beta5/obj-i486-kfreebsd-gnu' make[2]: *** [src/CMakeFiles/kshutdown.dir/all] Error 2 Full build log at https://buildd.debian.org/status/fetch.php?pkg=kshutdown&arch=kfreebsd-i386&ver=3.0%7Ebeta5-2&stamp=1359207833 Regards Christoph If you have further questions please mail debian-...@lists.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#699625: Only apply minimal changes to latd package due to Wheezy freeze
Hi One further follow up: The Security Team marked the issue as no-dsa in the Security-Tracker[1]. So an update for Squeeze might go trough a p-u upload. [1] https://security-tracker.debian.org/tracker/CVE-2013-0251 Thanks for fixing this issue quickly! Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: tagging 699564
Processing commands for cont...@bugs.debian.org: > tags 699564 - moreinfo unreproducible Bug #699564 [flush] [flush] Starting Flush failed: Removed tag(s) unreproducible and moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 699564: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699564 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: notfound 694340 in 3.2.5-0ubuntu4, found 694340 in 3.2.5-1+build1
Processing commands for cont...@bugs.debian.org: > notfound 694340 3.2.5-0ubuntu4 Bug #694340 [libgconf2-4] libgconf2-4: libgconf built with the dbus backend requires dbus-glib to be initialized with threading There is no source info for the package 'libgconf2-4' at version '3.2.5-0ubuntu4' with architecture '' Unable to make a source version for version '3.2.5-0ubuntu4' No longer marked as found in versions 3.2.5-0ubuntu4. > found 694340 3.2.5-1+build1 Bug #694340 [libgconf2-4] libgconf2-4: libgconf built with the dbus backend requires dbus-glib to be initialized with threading Marked as found in versions gconf/3.2.5-1+build1. > thanks Stopping processing here. Please contact me if you need assistance. -- 694340: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=694340 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#699835: keystone: CVE-2013-0247: Keystone denial of service through invalid token requests
Package: keystone Severity: grave Tags: security Justification: user security hole Hi, the following vulnerability was published for keystone. CVE-2013-0247[0]: Keystone denial of service through invalid token requests Patches should be available via [1]. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities & Exposures) id in your changelog entry. For further information see: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-0247 http://security-tracker.debian.org/tracker/CVE-2013-0247 [1] https://lists.launchpad.net/openstack/msg20689.html Please adjust the affected versions in the BTS as needed. Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#699825: marked as done (CVE-2013-0240: fails to verify SSL certificates when creating accounts)
Your message dated Tue, 05 Feb 2013 17:47:39 + with message-id and subject line Bug#699825: fixed in gnome-online-accounts 3.4.2-2 has caused the Debian Bug report #699825, regarding CVE-2013-0240: fails to verify SSL certificates when creating accounts 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.) -- 699825: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699825 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gnome-online-accounts Version: 3.4.2-1 Severity: grave Tags: security pending Justification: user security hole I discovered this vulnerability, which was just made public on oss-security: > it was found that Gnome Online Accounts (GOA) > did not perform SSL certificate validation, when > performing Windows Live and Facebook accounts creation. > A remote attacker could use this flaw to conduct > man-in-the-middle (MiTM) attacks, possibly leading > to their ability to obtain sensitive information. It's fixed in upstream master. I have a backport to 3.4 on the way (it needs testing though). 3.6 in experimental is also affected. I've asked upstream for a backported patch for 3.6, we'll see what happens... S --- End Message --- --- Begin Message --- Source: gnome-online-accounts Source-Version: 3.4.2-2 We believe that the bug you reported is fixed in the latest version of gnome-online-accounts, 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 699...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Simon McVittie (supplier of updated gnome-online-accounts 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, 05 Feb 2013 15:51:24 + Source: gnome-online-accounts Binary: gnome-online-accounts libgoa-1.0-0 libgoa-1.0-dev libgoa-1.0-common libgoa-1.0-doc gir1.2-goa-1.0 Architecture: source all amd64 Version: 3.4.2-2 Distribution: unstable Urgency: medium Maintainer: Debian GNOME Maintainers Changed-By: Simon McVittie Description: gir1.2-goa-1.0 - Introspection data for GNOME Online Accounts gnome-online-accounts - GNOME Online Accounts libgoa-1.0-0 - library for GNOME Online Accounts libgoa-1.0-common - library for GNOME Online Accounts - common files libgoa-1.0-dev - library for GNOME Online Accounts - development files libgoa-1.0-doc - library for GNOME Online Accounts - documentation files Closes: 699825 Changes: gnome-online-accounts (3.4.2-2) unstable; urgency=medium . * Team upload. * CVE-2013-0240: check TLS certificates for web services (Closes: #699825) Checksums-Sha1: bc67b7978dff4ba028131692d6f2c6d2e66b51ed 2723 gnome-online-accounts_3.4.2-2.dsc 416afaf6608d998a1f22e16b0f0e861ac2ac7ff6 6980 gnome-online-accounts_3.4.2-2.debian.tar.gz 222038a84bce14d19d96aaead5a1c23f18c1d39b 57270 libgoa-1.0-common_3.4.2-2_all.deb 7d6d5489f401c1a196427eadffd0540791d950f2 70264 libgoa-1.0-doc_3.4.2-2_all.deb 47e373668f17b84c41a8b1ef269a037ea3b469e9 79538 gnome-online-accounts_3.4.2-2_amd64.deb a62ab6c4dee7cfd4ee19c3ff9d0c19e47ffe15fe 74510 libgoa-1.0-0_3.4.2-2_amd64.deb afb36953e5936175a2bfa53ff09a802d662a7b61 29744 libgoa-1.0-dev_3.4.2-2_amd64.deb d31ca0e228800df7ee04e910f17c7aef0adc94e7 12642 gir1.2-goa-1.0_3.4.2-2_amd64.deb Checksums-Sha256: d7f4f256ad622c0f98f19d00d8f25c769876cfdaf483d68ca4ec13d8998d9889 2723 gnome-online-accounts_3.4.2-2.dsc d2d524ddc32543f754a87b20249f94bd3f561c9168d323f3efbe75711f8f02a5 6980 gnome-online-accounts_3.4.2-2.debian.tar.gz 5b7dafad49b44d659303e1e356f8d0eb93c95d9c61862c699924d18d2b95b0fc 57270 libgoa-1.0-common_3.4.2-2_all.deb f18eb25d0269cfa8904af579d744722e28e5a3f80e7d9c0b1c6d3f4e7c829cbc 70264 libgoa-1.0-doc_3.4.2-2_all.deb 6e613b244aff68fb22534bfef0b313284e0f253b8d2f054dd779c252d5b17232 79538 gnome-online-accounts_3.4.2-2_amd64.deb e1b47ce285dff889bdbd2baddadca349e0975bcbb796977f8a3d26092095d918 74510 libgoa-1.0-0_3.4.2-2_amd64.deb 5d6fdf497e61f63768b0a4d9498acb440e2467327bf6aa618a1923e90fbfa9c4 29744 libgoa-1.0-dev_3.4.2-2_amd64.deb db84a16ae11a238739f7ba423a35c2e74f8af4aaed22fe0fed5d4793325f1906 12642 gir1.2-goa-1.0_3.4.2-2_amd64.deb Files: f45a33b7f835d886b56862d40e70df74 2723 gnome optional gnom
Bug#684889: CVE-2012-3480 - stable update?
Hi! Is there any plan to fix CVE-2012-3480 / #684889 in stable? cu AW -- [...] If you don't want to be restricted, don't agree to it. If you are coerced, comply as much as you must to protect yourself, just don't support it. Noone can free you but yourself. (crag, on Debian Planet) Arne Wichmann (a...@linux.de) signature.asc Description: Digital signature
Bug#699825: CVE-2013-0240: fails to verify SSL certificates when creating accounts
Package: gnome-online-accounts Version: 3.4.2-1 Severity: grave Tags: security pending Justification: user security hole I discovered this vulnerability, which was just made public on oss-security: > it was found that Gnome Online Accounts (GOA) > did not perform SSL certificate validation, when > performing Windows Live and Facebook accounts creation. > A remote attacker could use this flaw to conduct > man-in-the-middle (MiTM) attacks, possibly leading > to their ability to obtain sensitive information. It's fixed in upstream master. I have a backport to 3.4 on the way (it needs testing though). 3.6 in experimental is also affected. I've asked upstream for a backported patch for 3.6, we'll see what happens... S -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#624507: closed by Josselin Mouette (Bug#624507: fixed in gvfs 1.12.3-4)
On Tue, Feb 05, 2013 at 03:06:06PM +, Debian Bug Tracking System wrote: > gvfs (1.12.3-4) unstable; urgency=low > . >* 06_metadata_nfs.patch: new patch. Disable gvfsd-metadata entirely on > remote filesystems. It is better to miss functionality than to > hammer the server. Closes: #624507. Quite possibly a good idea, but note that the my original report occurred with a local filesystem, not a remote filesystem. - Josh Triplett -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#699820: stack smashing when reading ics file
Package: imview Version: 1.1.9c-9 Severity: grave Tags: security imview has stack smashing vulnerability when parsing ics header @ io/readics.cxx:320 /* get the filename from the ICS file */ t = temp1; while (*bp != delim2) *t++ = *bp++; This bug can lead arbitrary code execution. I am attaching a crashing input. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) 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 imview depends on: ii libc6 2.13-37 ii libfontconfig1 2.9.0-7.1 ii libgcc1 1:4.7.2-5 ii libgomp14.7.2-5 ii libjpeg88d-1 ii libmagickcore5 8:6.7.7.10-5 ii libpng12-0 1.2.49-1 ii libstdc++6 4.7.2-5 ii libtiff43.9.6-11 ii libx11-62:1.5.0-1 ii libxext62:1.3.1-2 ii libxft2 2.3.1-1 ii libxinerama12:1.1.2-1 ii libxpm4 1:3.5.10-1 ii zlib1g 1:1.2.7.dfsg-13 imview recommends no packages. Versions of packages imview suggests: pn imview-doc -- no debconf information A:A:
Bug#699396: CVE-2013-0241 - qxl: synchronous io guest DoS
Hi, Luciano, On Thu, Jan 31, 2013 at 12:10:16AM +0100, Luciano Bello wrote: > Package: xserver-xorg-video-qxl > Severity: grave > Tags: security patch > Justification: user security hole > > Hi there, >Take a look to http://seclists.org/oss-sec/2013/q1/204 >Please, use CVE-2013-0241 to refer this issue. >The Debian package in unstable looks affected. Can you check if the stable > or > testings are affected too? I checked the patch, it modified following function: qxl_handle_oom qxl_allocnf setup_slot qxl_surface_cache_create_primary download_box qxl_allocnf exist in qxl 0.0.12, but it have not use ioport_write function, other function don't exist in qxl 0.0.12. Could you please check wheather this bug affect qxl in squeeze ? Thanks and Regards, -- Liang Guo http://bluestone.cublog.cn signature.asc Description: Digital signature
Bug#635457: marked as done (gvfsd-metadata: gvfsd-metadata creates a large amount of NFS network I/O on NFS-mounted user home directory)
Your message dated Tue, 05 Feb 2013 15:02:41 + with message-id and subject line Bug#624507: fixed in gvfs 1.12.3-4 has caused the Debian Bug report #624507, regarding gvfsd-metadata: gvfsd-metadata creates a large amount of NFS network I/O on NFS-mounted user home directory 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.) -- 624507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624507 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: gvfs Version: 1.6.4-3 Severity: normal File: gvfsd-metadata I logged in to my at-work desktop Debian 6 manchine from home today (monday) and found it generating a large amount of traffic to the NFS server. This traffic ceased when I killed "gvfsd-metadata" The NFS server is a Sun/Oracle Unified storage 7410C if that makes any difference. I have seen this error reported elsewhere see: https://bugzilla.redhat.com/show_bug.cgi?id=561904 Here is some of the tcpdump traffic log during the "event": 15:31:45.266224 nfshomedirserver.edu.nfsd > clientbox.edu.895: xid 0x6d34c57 reply ok 116 getattr [|nfs] 15:31:45.266498 clientbox.edu.895 > nfshomedirserver.edu.nfsd: xid 0x7d34c57 (NFSv3) 1428 write [|nfs] (DF) 15:31:45.266502 clientbox.edu.895 > nfshomedirserver.edu.nfsd: xid 0x0 (Unk 15024) 1428 proc-22796 (DF) 15:31:45.266504 clientbox.edu.895 > nfshomedirserver.edu.nfsd: xid 0x1b83 (Unk 9) 1428 null (DF) 15:31:45.266600 nfshomedirserver.edu.nfsd > clientbox.edu.895: . ack 34929 win 32710 15:31:45.266723 nfshomedirserver.edu.nfsd > clientbox.edu.895: xid 0x7d34c57 reply ok 164 write [|nfs] 15:31:45.266874 clientbox.edu.895 > nfshomedirserver.edu.nfsd: xid 0x8d34c57 (NFSv3) 180 commit [|nfs] (DF) 15:31:45.267227 nfshomedirserver.edu.nfsd > clientbox.edu.895: xid 0x8d34c57 reply ok 156 commit [|nfs] 15:31:45.267499 clientbox.edu.895 > nfshomedirserver.edu.nfsd: xid 0x9d34c57 (NFSv3) 200 remove [|nfs] (DF) 15:31:45.267503 clientbox.edu.895 > nfshomedirserver.edu.nfsd: xid 0xad34c57 (NFSv3) 192 remove [|nfs] (DF) 15:31:45.267601 nfshomedirserver.edu.nfsd > clientbox.edu.895: . ack 36929 win 32799 15:31:45.267987 nfshomedirserver.edu.nfsd > clientbox.edu.895: xid 0x9d34c57 reply ok 148 remove [|nfs] 15:31:45.267989 nfshomedirserver.edu.nfsd > clientbox.edu.895: xid 0xad34c57 reply ok 148 remove [|nfs] 15:31:45.268125 clientbox.edu.895 > nfshomedirserver.edu.nfsd: . ack 2484 win 15787 (DF) 15:31:45.271121 clientbox.edu.895 > nfshomedirserver.edu.nfsd: xid 0xbd34c57 (NFSv3) 196 create [|nfs] (DF) 15:31:45.271598 nfshomedirserver.edu.nfsd > clientbox.edu.895: xid 0xbd34c57 reply ok 276 create [|nfs] 15:31:45.271870 clientbox.edu.895 > nfshomedirserver.edu.nfsd: xid 0xcd34c57 (NFSv3) 200 setattr [|nfs] (DF) 15:31:45.272225 nfshomedirserver.edu.nfsd > clientbox.edu.895: xid 0xcd34c57 reply ok 148 setattr [|nfs] 15:31:45.272495 clientbox.edu.895 > nfshomedirserver.edu.nfsd: xid 0xdd34c57 (NFSv3) 1428 write [|nfs] (DF) 15:31:45.272500 clientbox.edu.895 > nfshomedirserver.edu.nfsd: xid 0x0 (Unk 15024) 1428 proc-22796 (DF) 15:31:45.272502 clientbox.edu.895 > nfshomedirserver.edu.nfsd: xid 0x1b83 (Unk 9) 1428 null (DF) 15:31:45.272598 nfshomedirserver.edu.nfsd > clientbox.edu.895: . ack 40181 win 32710 15:31:45.272620 clientbox.edu.895 > nfshomedirserver.edu.nfsd: xid 0x0 (Unk 0) 1428 proc-27772 (DF) 15:31:45.272624 clientbox.edu.895 > nfshomedirserver.edu.nfsd: xid 0x70656420 (Unk 1914725231) 1428 proc-1835884910 (DF) 15:31:45.272626 clientbox.edu.895 > nfshomedirserver.edu.nfsd: xid 0x61746573 (Unk 1937006964) 1428 proc-1970482481 (DF) 15:31:45.272628 clientbox.edu.895 > nfshomedirserver.edu.nfsd: xid 0x73685f4d (Unk 776557391) 1428 proc-779116914 (DF) 15:31:45.272630 clientbox.edu.895 > nfshomedirserver.edu.nfsd: xid 0x66775f75 (Unk 1093563489) 1428 proc-1915646049 (DF) 15:31:45.272632 clientbox.edu.895 > nfshomedirserver.edu.nfsd: xid 0x732e7a69 (Unk 1600286821) 1428 proc-1949643888 (DF) 15:31:45.272635 clientbox.edu.895 > nfshomedirserver.edu.nfsd: xid 0x3433302d (Unk 1952803886) 1428 proc-1684365870 (DF) 15:31:45.272637 clientbox.edu.895 > nfshomedirserver.edu.nfsd: xid 0x0 (Unk 17956) 1428 proc-33808 (DF) 15:31:45.272639 clientbox.edu.895 > nfshomedirserver.edu.nfsd: xid 0x2b598ec (Unk 45455575) 864 proc-15792 (DF) 15:31:45.272641 clientbox.edu.895 > nfshomedirserver.edu.nfsd: xid 0xed34c57 (NFSv3) 1428 write [|nfs] (DF) 15:31:45.272643 clientbox.edu.895 > nfshomedirserver.edu.nfsd: xid 0x52345f65 (Unk 1599616052) 1428 proc-875585368 (DF) 15:31:45.272652 clientbox.edu.895 > nfshomedirserver.edu.n
Bug#624507: marked as done (Started looping and continuously rewriting metadata file)
Your message dated Tue, 05 Feb 2013 15:02:41 +
with message-id
and subject line Bug#624507: fixed in gvfs 1.12.3-4
has caused the Debian Bug report #624507,
regarding Started looping and continuously rewriting metadata file
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.)
--
624507: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=624507
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: gvfs
Version: 1.6.4-3
Severity: important
File: gvfsd-metadata
I just had gvfsd-metadata start looping continuously in the background,
rewriting metadata files. I grabbed a quick strace, then killed it.
Repeating pattern in the strace:
open("/home/josh/.local/share/gvfs-metadata/home-aec04c3b.log.9QPTUV",
O_RDWR|O_CREAT|O_EXCL, 0666) = 11
fcntl(11, F_GETFL) = 0x8002 (flags O_RDWR|O_LARGEFILE)
fstat(11, {st_mode=S_IFREG|0644, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f508e87c000
lseek(11, 0, SEEK_CUR) = 0
write(11,
"\332\32jour\1\0\256\300L;\0\0\200\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
32768) = 32768
fstatfs(11, {f_type="EXT2_SUPER_MAGIC", f_bsize=4096, f_blocks=18022671,
f_bfree=8762318, f_bavail=8579218, f_files=4579328, f_ffree=4085656,
f_fsid={1281784360, -1936016178}, f_name
len=255, f_frsize=4096}) = 0
lstat("/home/josh/.local/share/gvfs-metadata/home-aec04c3b.log",
0x7fff99738a40) = -1 ENOENT (No such file or directory)
close(11) = 0
munmap(0x7f508e87c000, 4096)= 0
rename("/home/josh/.local/share/gvfs-metadata/home-aec04c3b.log.9QPTUV",
"/home/josh/.local/share/gvfs-metadata/home-aec04c3b.log") = 0
open("/home/josh/.local/share/gvfs-metadata/home", O_RDWR) = 11
rename("/home/josh/.local/share/gvfs-metadata/home.L2STUV",
"/home/josh/.local/share/gvfs-metadata/home") = 0
open("/home/josh/.local/share/gvfs-metadata", O_RDONLY) = 12
fsync(12) = 0
close(12) = 0
mmap(NULL, 16, PROT_READ|PROT_WRITE, MAP_SHARED, 11, 0) = 0x7f508e87c000
munmap(0x7f508e87c000, 16) = 0
close(11) = 0
unlink("/home/josh/.local/share/gvfs-metadata/home-2aa65dd1.log") = 0
open("/home/josh/.local/share/gvfs-metadata/home.43PUUV",
O_RDWR|O_CREAT|O_EXCL, 0600) = 11
write(11, "\332\32meta\1\0\0\0\0\0\3\321\307\25\0\0\1d\0\0\0
\0\0\0\0M\267\244\372"..., 1292) = 1292
fsync(11) = 0
close(11) = 0
This pattern seems to repeat infinitely, with only the hashes and mktemp
extensions changing. This resulted in continous disk writes.
- Josh Triplett
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.39-rc4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages gvfs depends on:
ii libc6 2.11.2-13 Embedded GNU C Library: Shared lib
ii libdbus-1-3 1.4.8-3simple interprocess messaging syst
ii libexpat1 2.0.1-7XML parsing C library - runtime li
ii libgconf2-4 2.28.1-6 GNOME configuration database syste
ii libgdu0 2.30.1-2 GObject based Disk Utility Library
ii libglib2.0-0 2.28.6-1 The GLib library of C routines
ii libgnome-keyring0 3.0.0-2GNOME keyring services library
ii libudev0 168-1 libudev shared library
ii x11-utils 7.6+1 X11 utilities
Versions of packages gvfs recommends:
ii dbus 1.4.8-3simple interprocess messaging syst
ii policykit-1-gnome 0.101-2GNOME authentication agent for Pol
Versions of packages gvfs suggests:
ii gvfs-backends 1.6.4-3userspace virtual filesystem - bac
-- no debconf information
--- End Message ---
--- Begin Message ---
Source: gvfs
Source-Version: 1.12.3-4
We believe that the bug you reported is fixed in the latest version of
gvfs, 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 624...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenanc
Bug#699523: sysvinit: postinst fails if several 'init' process are running (LXC)
Roger, After some research, the best way I've found to send a signal to the correct 'init' is: pkill --signal USR1 -P 0 -x init You can check the PID with : pgrep -P 0 -x init It always return the correct process under the main machine and the LXC containers. HIH -- ,''`. : :' : Cyril Bouthors `. `' 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#699523: sysvinit: postinst fails if several 'init' process are running (LXC)
On 3 Feb 2013, rle...@codelibre.net wrote: > Please could you try upgrading with the packages at > http://people.debian.org/~rleigh/sysvinit/ > and let me know if this solves the problem for you. Seems to work: 3:32PM lenovo:/tmp% sudo dpkg -i sysvinit_2.88dsf-40_amd64.deb (Reading database ... 261177 files and directories currently installed.) Preparing to replace sysvinit 2.88dsf-39 (using sysvinit_2.88dsf-40_amd64.deb) ... Unpacking replacement sysvinit ... Setting up sysvinit (2.88dsf-40) ... sysvinit: restarting... done. Processing triggers for man-db ... 3:32PM lenovo:/tmp% -- ,''`. : :' : Cyril Bouthors `. `' 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#698632: rstatd: Patch 03-627217-netio.patch breaks RPC protocol compatibility for rstatd
Hi Anibal On Mon, Jan 21, 2013 at 02:50:43PM +0100, Salvatore Bonaccorso wrote: > Reverting the patch 03-627217-netio.patch let it work in a mixed > squeeze, wheezy environment. If 627217 can be fixed, it should probably > without breaking the "protocol". After reverting the patch the requests > give again correct results. [...] > Could you please revert at least 03-627217-netio.patch (if fixing > #627217 without creating the compatibility issue cannot be fixed)? At this stage of the freeze this option (droping the patch for 627217) looks the best to me, what do you think Anibal? Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: reassign 699795 to libtasn1-6-dbg, found 699795 in 3.0-1
Processing commands for cont...@bugs.debian.org: > reassign 699795 libtasn1-6-dbg Bug #699795 [libtasn1-3-dbg,libtasn1-6-dbg] libtasn1-6-dbg and libtasn1-3-dbg: error when trying to install together Bug reassigned from package 'libtasn1-3-dbg,libtasn1-6-dbg' to 'libtasn1-6-dbg'. Ignoring request to alter found versions of bug #699795 to the same values previously set Ignoring request to alter fixed versions of bug #699795 to the same values previously set > found 699795 3.0-1 Bug #699795 [libtasn1-6-dbg] libtasn1-6-dbg and libtasn1-3-dbg: error when trying to install together Marked as found in versions libtasn1-6/3.0-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 699795: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=699795 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#698846: wiggle: non-DFSG document in source tarball
On 2013-02-05 10:10, NeilBrown wrote: | I've made a 0.9.1 release (both in git://neil.brown.name/wiggle and in | http://neil.brown.name/wiggle) which removes the 'diff.ps' file and replaces | it with a text file which suggests how the postscript file can be found. | | i.e. I've chosen not to distribute the diff.ps file at all any more. It is | easily found on the internet so there is nothing to be gained by me | distributing it. | | Thanks, | NeilBrown That helps a lot on the Debian side of the release management. Thanks Neil, Jari signature.asc Description: Digital signature
Bug#698837: Bug#695774 cloned and reopened to #698837
On Sat, 2 Feb 2013, Jérémy Lal wrote: > So it would be nice to know : > - do you have adater: pgsql in database.yml ? Sorry, I can’t know this any more, the test machine was deleted now. > - was the file modified manually before the upgrade ? No, never. > - are you able to reproduce the bug on another machine ? Sorry, I don’t have the resources to do so any more (this being company stuff and all that). If the steps (install redmine and redmine-pgsql but not postgresql server, say yes to configure the DB, then it fails, then install postgresql and let redmine configure the DB, then upgrade redmine) work for you, I guess the issue is closed. bye, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-314 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Boris Esser, Sebastian Mancke -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#650874: marked as done (empathy: does not start)
Your message dated Tue, 05 Feb 2013 11:18:18 +0100 with message-id <1360059498.8280.21.camel@tomoyo> and subject line Re: The bug is in cogl has caused the Debian Bug report #619636, regarding empathy: does not start 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.) -- 619636: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619636 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: empathy Version: 3.2.1.1-1 Severity: important empathy does not start and does not even show an error message (in gui). when i try to start it from a terminal the output is: failed to create drawable (empathy:4529): Clutter-CRITICAL **: Unable to initialize Clutter: Unable to select the newly created GLX context (empathy:4529): Gdk-WARNING **: The program 'empathy' received an X Window System error. This probably reflects a bug in the program. The error was 'BadGC (invalid GC parameter)'. (Details: serial 159 error_code 13 request_code 60 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) this error makes it completely unusable. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.1.0-1-amd64 (SMP w/4 CPU cores) 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 empathy depends on: ii dbus-x11 1.4.16-1 ii dconf-gsettings-backend [gsettings-backend] 0.7.5-3 ii empathy-common 3.2.1.1-1 ii geoclue 0.12.0-3+b1 ii gnome-icon-theme 3.2.1.2-1 ii gsettings-desktop-schemas3.2.0-2 ii gstreamer0.10-gconf 0.10.30-2 ii libc62.13-21 ii libcanberra-gtk3-0 0.28-3 ii libcanberra0 0.28-3 ii libchamplain-0.12-0 0.12.0-1 ii libchamplain-gtk-0.12-0 0.12.0-1 ii libcheese-gtk20 3.2.2-1 ii libclutter-1.0-0 1.8.2-2 ii libclutter-gtk-1.0-0 1.0.4-1 ii libdbus-glib-1-2 0.98-1 ii libebook1.2-10 3.0.3-2 ii libenchant1c2a 1.6.0-6 ii libfolks-telepathy25 0.6.5-1 ii libfolks25 0.6.5-1 ii libgcr-3-0 3.0.3-2 ii libgdk-pixbuf2.0-0 2.24.0-1 ii libgee2 0.6.1-3 ii libgeoclue0 0.12.0-3+b1 ii libgeocode-glib0 0.99.0-1 ii libglib2.0-0 2.30.2-4 ii libgnome-keyring03.2.2-1 ii libgnutls26 2.12.14-3 ii libgstfarsight0.10-0 0.0.31-1 ii libgstreamer-plugins-base0.10-0 0.10.35-1 ii libgstreamer0.10-0 0.10.35-1 ii libgtk-3-0 3.0.12-2 ii libgudev-1.0-0 175-2 ii libnm-glib4 0.9.2.0-1 ii libnotify4 0.7.4-1 ii libpango1.0-01.29.4-2 ii libpulse-mainloop-glib0 1.0-4 ii libpulse01.0-4 ii libtelepathy-farsight0 0.0.19-1 ii libtelepathy-glib0 0.16.2-1 ii libtelepathy-logger2 0.2.10-2 ii libwebkitgtk-3.0-0 1.6.1-5+b1 ii libx11-6 2:1.4.4-4 ii libxml2 2.7.8.dfsg-5 ii telepathy-logger 0.2.10-2 ii telepathy-mission-control-5 1:5.9.3-3 Versions of packages empathy recommends: ii freedesktop-so
Bug#620908: marked as done (Clutter is not working properly with mesa software rendering)
Your message dated Tue, 05 Feb 2013 11:18:18 +0100
with message-id <1360059498.8280.21.camel@tomoyo>
and subject line Re: The bug is in cogl
has caused the Debian Bug report #619636,
regarding Clutter is not working properly with mesa software rendering
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.)
--
619636: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619636
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libclutter-1.0-0
Version: 1.6.10-3
Severity: normal
My desktop machine does not have hardware 3D acceleration, but it does
have the Mesa software rasterizer (glxinfo output appended). Clutter-
using programs fail to start with an obscure error message, e.g.
$ empathy
failed to create drawable
Unable to select the newly created GLX context
Run 'empathy --help' to see a full list of available command line options.
(empathy:10362): empathy-WARNING **: Error in empathy init: Unable to select
the newly created GLX context
--clutter-debug=ALL does not appear to provide any more clues, but here is the
key part of that anyway:
Clutter-Message: [BACKEND] ./x11/clutter-backend-x11.c:463: X Display
':0.0'[0x211f940] opened (screen:0, root:304, dpi:96.00)
Clutter-Message: [MISC] ./clutter-feature.c:92: checking features
Clutter-Message: [MISC] ./clutter-feature.c:96: allocating features data
Clutter-Message: [BACKEND] ./glx/clutter-backend-glx.c:447: Retrieving GL
fbconfig, dpy: 0x211f940, xscreen; 0x211b890 (0)
Clutter-Message: [BACKEND] ./glx/clutter-backend-glx.c:489: Using the first
available FBConfig
Clutter-Message: [BACKEND] ./glx/clutter-backend-glx.c:583: Creating GLX
Context (display: 0x211f940)
Clutter-Message: [GL] ./glx/clutter-backend-glx.c:602: Setting direct context
failed to create drawable
Clutter-Message: [BACKEND] ./glx/clutter-backend-glx.c:661: Selecting dummy
0x3c4 for the GLX context
Unable to select the newly created GLX context
and here's an X11 protocol trace (just the requests that failed) -- note that
the "failed to create drawable" message happens before this point, and I don't
see any attempt to create a drawable go over the wire before that, just a
bunch of server capability queries. (Lemme know if you want to see the
complete protocol trace, it's huge.)
001:<:0031: 28: GLX-Request(154,24): glXCreateNewContext opcode=0x9a
opcode2=0x18
unparsed-data=0x01,0x00,0xc0,0x03,0xb0,0x00,0x00,0x00,0x00,0x00,0x00,0x00,0x14,0x80,0x00,0x00,0x00,0x00,0x00,0x00,0x01,0x00,0x00,0x00;
001:<:0032: 16: Request(78): CreateColormap alloc=None(0x00) mid=0x03c2
window=0x0130 visual=0x0021
001:<:0033: 44: Request(1): CreateWindow depth=0x18 window=0x03c3
parent=0x0130 x=-100 y=-100 width=1 height=1 border-width=0
class=CopyFromParent(0x) visual=0x0021
value-list={border-pixel=0x override-redirect=true(0x01)
colormap=0x03c2}
001:<:0034: 24: GLX-Request(154,31): glXCreateWindow opcode=0x9a opcode2=0x1f
unparsed-data=0x00,0x00,0x00,0x00,0xb0,0x00,0x00,0x00,0x03,0x00,0xc0,0x03,0x04,0x00,0xc0,0x03,0x00,0x00,0x00,0x00;
001:<:0035: 16: Request(55): CreateGC cid=0x03c5 drawable=0x03c4
values={}
001:<:0036: 16: Request(55): CreateGC cid=0x03c6 drawable=0x03c4
values={}
001:<:0037: 8: Request(14): GetGeometry drawable=0x03c4
001:>:0035:Error 9=Drawable: major=55, minor=0, bad=62914564
001:>:0036:Error 9=Drawable: major=55, minor=0, bad=62914564
001:>:0037:Error 9=Drawable: major=14, minor=0, bad=62914564
If ordinary GNOME programs are going to be growing dependencies on
clutter, IMHO clutter needs to work with software GL.
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable'), (101, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.38-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages libclutter-1.0-0 depends on:
ii libatk1.0-0 1.32.0-3 The ATK accessibility toolkit
ii libc6 2.11.2-13 Embedded GNU C Library: Shared lib
ii libcairo-gobject2 1.10.2-6 The Cairo 2D vector graphics libra
ii libcairo2 1.10.2-6 The Cairo 2D vector graphics libra
ii libdrm2 2.4.23-3 Userspace interface to kernel DRM
ii libgdk-pixbuf2.0-02.23.0-2 GDK Pixbuf library
ii libgl1-mesa-glx [libgl1] 7.10-4 A free implementation of the OpenG
ii libglib2.0-0 2.28.4-1 The GLib library of C routines
ii libjson-
Bug#619636: marked as done (Clutter is not working properly with mesa software rendering)
Your message dated Tue, 05 Feb 2013 11:18:18 +0100 with message-id <1360059498.8280.21.camel@tomoyo> and subject line Re: The bug is in cogl has caused the Debian Bug report #619636, regarding Clutter is not working properly with mesa software rendering 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.) -- 619636: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=619636 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: empathy Version: 2.30.3-1+b2 Severity: important failed to create drawable. Unable to select the newly created GLX context -- System Information: Debian Release: wheezy/sid Architecture: i386 (i686) Kernel: Linux 2.6.38-1-686-bigmem (SMP w/2 CPU cores) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages empathy depends on: ii dbus-x11 1.4.6-1 simple interprocess messaging syst ii empathy-common 2.30.3-1GNOME multi-protocol chat and call ii gconf2 2.32.1-2GNOME configuration database syste ii geoclue 0.12.0-2Geographic information framework ii gnome-icon-theme 2.30.3-2GNOME Desktop icon theme ii libatk1.0-0 1.32.0-1+sid1 The ATK accessibility toolkit ii libc62.11.2-11 Embedded GNU C Library: Shared lib ii libcairo21.10.2-4The Cairo 2D vector graphics libra ii libcamel1.2-19 2.32.2-2The Evolution MIME message handlin ii libcanberra-gtk0 0.24-1 Gtk+ helper for playing widget eve ii libcanberra0 0.24-1 a simple abstract interface for pl ii libchamplain-0.4 0.4.6-3 C library providing ClutterActor t ii libchamplain-gtk 0.4.6-3 A Gtk+ widget to display maps ii libclutter-1.0-0 1.6.10-1Open GL based interactive canvas l ii libclutter-gtk-0 0.10.4-1Open GL based interactive canvas l ii libdbus-1-3 1.4.6-1 simple interprocess messaging syst ii libdbus-glib-1-2 0.92-1 simple interprocess messaging syst ii libebook1.2-10 2.32.2-2Client library for evolution addre ii libedataserver1. 2.32.2-2Utility library for evolution data ii libenchant1c2a 1.6.0-2 a wrapper library for various spel ii libfontconfig1 2.8.0-2.1 generic font configuration library ii libfreetype6 2.4.4-1 FreeType 2 font engine, shared lib ii libgconf2-4 2.32.1-2GNOME configuration database syste ii libgeoclue0 0.12.0-2C API for GeoClue ii libgl1-mesa-glx 7.10-4 A free implementation of the OpenG ii libglib2.0-0 2.28.2-1The GLib library of C routines ii libgnome-keyring 2.32.0-1GNOME keyring services library ii libgstfarsight0. 0.0.26-1Audio/Video communications framewo ii libgstreamer-plu 0.10.32-2 GStreamer libraries from the "base ii libgstreamer0.10 0.10.32-6 Core GStreamer libraries and eleme ii libgtk2.0-0 2.24.3-1~sid1 The GTK+ graphical user interface ii libjson-glib-1.0 0.12.0-3GLib JSON manipulation library ii libnm-glib2 0.8.3.998-1 network management framework (GLib ii libnotify1 [libn 0.5.0-2 sends desktop notifications to a n ii libnspr4-0d 4.8.7-2 NetScape Portable Runtime Library ii libnss3-1d 3.12.9.with.ckbi.1.82-1 Network Security Service libraries ii libpango1.0-01.28.3-2~sid1 Layout and rendering of internatio ii libsoup2.4-1 2.30.2-1an HTTP library implementation in ii libsqlite3-0 3.7.5-1 SQLite 3 shared library ii libtelepathy-far 0.0.16+is.0.0.14-1 Glue library between telepathy and ii libtelepathy-gli 0.11.11-1 Telepathy framework - GLib library ii libunique-1.0-0 1.1.6-2 Library for writing single instanc ii libwebkit-1.0-2 1.2.7-2 Web content engine library for Gtk ii libx11-6 2:1.4.1-5 X11 client-side library ii libxcomposite1 1:0.4.3-1 X11 Composite extension library ii libxdamage1 1:1.1.3-1 X11 damaged region extension libra ii libxext6 2:1.2.0-2 X11 miscellaneous extension librar ii libxfixes3 1:4.0.5-1 X11 miscellaneous 'fixe
Bug#699625: Only apply minimal changes to latd package due to Wheezy freeze
Hi On Tue, Feb 05, 2013 at 08:26:53AM +, Chrissie Caulfield wrote: > On 04/02/13 22:14, Salvatore Bonaccorso wrote: > >Hi Christine > > > >I noticed you already uploaded 1.31 fixing #699625 which is great, > >thanks for working on this issue and fixing it already. > > > >There is however one unfortunate thing: > > > > 91 files changed, 28516 insertions(+), 2085 deletions(-) > > > >This is a problem as the fix needs to go to testing too, but we are in > >Freeze for wheezy now so the freeze policy[1] applies. > > > > [1]: http://release.debian.org/wheezy/freeze_policy.html > > > >Could you isolate the fix needed and only perform a minimal update to > >the package in regard to the version in testing? 1.30. I guess the > >release team would like to see the changes reverted and have only the > >bug fixed at this stage of the freeze. > > Sorry, my mistake. > > I'll do another upload later today with only that patch, then > another one to fix the lintian bugs later in the week. TBH most of > that diff was a sill yautoconf-generated file! Thank you for the quick reply! Btw, could you then also ask for the unblock to the release team? It should appear on their radar anyway as it's RC bug, but I think it's appreciated on their side. Regards, Salvatore -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#699795: libtasn1-6-dbg and libtasn1-3-dbg: error when trying to install together
Package: libtasn1-3-dbg,libtasn1-6-dbg Version: libtasn1-3-dbg/2.13-2 Version: libtasn1-6-dbg/3.2-1 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2013-02-05 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libtasn1-6 libtasn1-3-dbg libtasn1-6-dbg Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libtasn1-6:amd64. (Reading database ... 10762 files and directories currently installed.) Unpacking libtasn1-6:amd64 (from .../libtasn1-6_3.2-1_amd64.deb) ... Selecting previously unselected package libtasn1-3-dbg. Unpacking libtasn1-3-dbg (from .../libtasn1-3-dbg_2.13-2_amd64.deb) ... Selecting previously unselected package libtasn1-6-dbg. Unpacking libtasn1-6-dbg (from .../libtasn1-6-dbg_3.2-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/libtasn1-6-dbg_3.2-1_amd64.deb (--unpack): trying to overwrite '/usr/lib/debug/usr/bin/asn1Decoding', which is also in package libtasn1-3-dbg 2.13-2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/libtasn1-6-dbg_3.2-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) cow-shell unlink .ilist: No such file or directory This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/lib/debug/usr/bin/asn1Coding /usr/lib/debug/usr/bin/asn1Decoding /usr/lib/debug/usr/bin/asn1Parser This bug has been filed against both packages. If you, the maintainers of the two packages in question, have agreed on which of the packages will resolve the problem please reassign the bug to that package. You may then also register in the BTS that the other package is affected by the bug. -Ralf. PS: for more information about the detection of file overwrite errors of this kind see http://edos.debian.net/file-overwrites/. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#699625: Only apply minimal changes to latd package due to Wheezy freeze
On 04/02/13 22:14, Salvatore Bonaccorso wrote: Hi Christine I noticed you already uploaded 1.31 fixing #699625 which is great, thanks for working on this issue and fixing it already. There is however one unfortunate thing: 91 files changed, 28516 insertions(+), 2085 deletions(-) This is a problem as the fix needs to go to testing too, but we are in Freeze for wheezy now so the freeze policy[1] applies. [1]: http://release.debian.org/wheezy/freeze_policy.html Could you isolate the fix needed and only perform a minimal update to the package in regard to the version in testing? 1.30. I guess the release team would like to see the changes reverted and have only the bug fixed at this stage of the freeze. Sorry, my mistake. I'll do another upload later today with only that patch, then another one to fix the lintian bugs later in the week. TBH most of that diff was a sill yautoconf-generated file! Chrissie -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#699625: asdf
Hi,
I browsed the source archives of latd because pkgsrc still has latd 1.18,
and found that all version between and including 1.25 and 1.30 have the
bug. I wonder if that information is useful to others...
Btw, why not change the sprintf to
snprintf(error, sizeof(error),
"llogin version %s does not match latd version " VERSION, cmdbuf);
instead of arbitrarily limiting cmdbuf to 900 characters, which might
be too long if somebody in the future shortened the buffer error or
passed in a much longer VERSION from the Makefile?
Do we want to avoid snprintf()?
Explicit
1024 - sizeof("llogin version does not match latd version " VERSION)
looks complicated, but makes the size requirement openly visible, and
should be optimizable by modern compilers.
Regards,
-is
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
