Bug#676635: libwine-bin: faulty dependency AND "No file name for libbz2-1.0"
bug still remains on amd64 -- Sergio Fernández -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#677400: marked as done (nova-common: prompting due to modified conffiles which were not modified by the user)
Your message dated Tue, 19 Jun 2012 07:33:28 + with message-id and subject line Bug#677400: fixed in nova 2012.1-7 has caused the Debian Bug report #677400, regarding nova-common: prompting due to modified conffiles which were not modified by the user 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.) -- 677400: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677400 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: nova-common Version: 2012.1-6 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed the piuparts upgrade test because dpkg detected a conffile as being modified and then prompted the user for an action. As there is no user input, this fails. But this is not the real problem, the real problem is that this prompt shows up in the first place, as there was nobody modifying this conffile at all, the package has just been installed and upgraded... This is a violation of policy 10.7.3, see http://www.debian.org/doc/debian-policy/ch-files.html#s10.7.3, which says "[These scripts handling conffiles] must not ask unnecessary questions (particularly during upgrades), and must otherwise be good citizens." http://wiki.debian.org/DpkgConffileHandling should help with figuring out how to do this properly. In http://lists.debian.org/debian-devel/2009/08/msg00675.html and followups it has been agreed that these bugs are to be filed with severity serious. >From the attached log (scroll to the bottom...): Setting up nova-common (2012.1-6) ... Configuration file `/etc/nova/nova.conf' ==> Modified (by you or by a script) since installation. ==> Package distributor has shipped an updated version. What would you like to do about it ? Your options are: Y or I : install the package maintainer's version N or O : keep your currently-installed version D : show the differences between the versions Z : start a shell to examine the situation The default action is to keep your current version. *** nova.conf (Y/I/N/O/D/Z) [default=N] ? dpkg: error processing nova-common (--configure): EOF on stdin at conffile prompt This problem was observed on a distupgrade from wheezy to sid. cheers, Andreas nova-common_2012.1-6.log.gz Description: GNU Zip compressed data --- End Message --- --- Begin Message --- Source: nova Source-Version: 2012.1-7 We believe that the bug you reported is fixed in the latest version of nova, which is due to be installed in the Debian FTP archive: nova-api-ec2_2012.1-7_all.deb to main/n/nova/nova-api-ec2_2012.1-7_all.deb nova-api-metadata_2012.1-7_all.deb to main/n/nova/nova-api-metadata_2012.1-7_all.deb nova-api-os-compute_2012.1-7_all.deb to main/n/nova/nova-api-os-compute_2012.1-7_all.deb nova-api-os-volume_2012.1-7_all.deb to main/n/nova/nova-api-os-volume_2012.1-7_all.deb nova-api_2012.1-7_all.deb to main/n/nova/nova-api_2012.1-7_all.deb nova-cert_2012.1-7_all.deb to main/n/nova/nova-cert_2012.1-7_all.deb nova-common_2012.1-7_all.deb to main/n/nova/nova-common_2012.1-7_all.deb nova-compute-kvm_2012.1-7_all.deb to main/n/nova/nova-compute-kvm_2012.1-7_all.deb nova-compute-lxc_2012.1-7_all.deb to main/n/nova/nova-compute-lxc_2012.1-7_all.deb nova-compute-qemu_2012.1-7_all.deb to main/n/nova/nova-compute-qemu_2012.1-7_all.deb nova-compute-uml_2012.1-7_all.deb to main/n/nova/nova-compute-uml_2012.1-7_all.deb nova-compute-xen_2012.1-7_all.deb to main/n/nova/nova-compute-xen_2012.1-7_all.deb nova-compute_2012.1-7_all.deb to main/n/nova/nova-compute_2012.1-7_all.deb nova-console_2012.1-7_all.deb to main/n/nova/nova-console_2012.1-7_all.deb nova-doc_2012.1-7_all.deb to main/n/nova/nova-doc_2012.1-7_all.deb nova-network_2012.1-7_all.deb to main/n/nova/nova-network_2012.1-7_all.deb nova-objectstore_2012.1-7_all.deb to main/n/nova/nova-objectstore_2012.1-7_all.deb nova-scheduler_2012.1-7_all.deb to main/n/nova/nova-scheduler_2012.1-7_all.deb nova-volume_2012.1-7_all.deb to main/n/nova/nova-volume_2012.1-7_all.deb nova-xcp-network_2012.1-7_all.deb to main/n/nova/nova-xcp-network_2012.1-7_all.deb nova-xcp-plugins_2012.1-7_all.deb to main/n/nova/nova-xcp-plugins_2012.1-7_all.deb nova-xvpvncproxy_2012.1-7_all.deb to main/n/nova/nova-xvpvncproxy_2012.1-7_all.deb nova_2012.1-7.debian.tar.gz to main/n/nova/nova_2012.1-7.debian.tar.gz nova_2012.1-7.dsc to main/n/nova/nova_2012.1-7.dsc python-nova_2012.1-7_all.deb to main/n/nova/python-nova_2012.1-7_all.deb A summary of the changes betw
Bug#674338: marked as done (germinate: FTBFS: test failed)
Your message dated Tue, 19 Jun 2012 10:56:09 +0200 with message-id <20120619105458.ga10...@debian.org> and subject line Re: Bug#674338: germinate: FTBFS: test failed has caused the Debian Bug report #674338, regarding germinate: FTBFS: test 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.) -- 674338: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: germinate Version: 2.8 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120524 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > make[1]: Entering directory `/«PKGBUILDDIR»' > set -e; for python in $(pyversions -r) $(py3versions -r); do \ > $python setup.py test; \ > done > running test > ./run-pychecker > pychecker not installed, so not running it > running build_py > running egg_info > creating /«PKGBUILDDIR»/build/lib.linux-x86_64-2.7/germinate.egg-info > writing /«PKGBUILDDIR»/build/lib.linux-x86_64-2.7/germinate.egg-info/PKG-INFO > writing top-level names to > /«PKGBUILDDIR»/build/lib.linux-x86_64-2.7/germinate.egg-info/top_level.txt > writing dependency_links to > /«PKGBUILDDIR»/build/lib.linux-x86_64-2.7/germinate.egg-info/dependency_links.txt > writing manifest file > '/«PKGBUILDDIR»/build/lib.linux-x86_64-2.7/germinate.egg-info/SOURCES.txt' > reading manifest file > '/«PKGBUILDDIR»/build/lib.linux-x86_64-2.7/germinate.egg-info/SOURCES.txt' > writing manifest file > '/«PKGBUILDDIR»/build/lib.linux-x86_64-2.7/germinate.egg-info/SOURCES.txt' > running build_ext > test_creates_file (germinate.tests.test_seeds.TestAtomicFile) > AtomicFile creates the named file with the requested contents. ... ok > test_removes_dot_new (germinate.tests.test_seeds.TestAtomicFile) > AtomicFile does not leave .new files lying around. ... ok > test_behaves_as_file (germinate.tests.test_seeds.TestSeed) > A Seed context can be read from as a file object. ... ok > test_equal_if_same_contents (germinate.tests.test_seeds.TestSeed) > Two Seed objects with the same text contents are equal. ... ok > test_init_no_bzr (germinate.tests.test_seeds.TestSeed) > __init__ can open a seed from a collection without bzr. ... ok > test_not_equal_if_different_contents (germinate.tests.test_seeds.TestSeed) > Two Seed objects with different text contents are not equal. ... ok > test_add (germinate.tests.test_seeds.TestSeedStructure) > SeedStructure.add adds a custom seed. ... ok > test_basic (germinate.tests.test_seeds.TestSeedStructure) > A SeedStructure object has the correct basic properties. ... ok > test_dict (germinate.tests.test_seeds.TestSeedStructure) > A SeedStructure can be treated as a dictionary of seeds. ... ok > test_later_branches_override_earlier_branches > (germinate.tests.test_seeds.TestSeedStructure) > Seeds from later branches override seeds from earlier branches. ... ok > test_limit (germinate.tests.test_seeds.TestSeedStructure) > SeedStructure.limit restricts the set of seed names. ... ok > test_multiple (germinate.tests.test_seeds.TestSeedStructure) > SeedStructure follows "include" links to other seed collections. ... ok > test_write (germinate.tests.test_seeds.TestSeedStructure) > SeedStructure.write writes the text of STRUCTURE. ... ok > test_write_dot (germinate.tests.test_seeds.TestSeedStructure) > SeedStructure.write_dot writes an appropriate dot file. ... ok > test_write_seed_text (germinate.tests.test_seeds.TestSeedStructure) > SeedStructure.write_seed_text writes the text of a seed. ... ok > test_write_seed_text_utf8 (germinate.tests.test_seeds.TestSeedStructure) > SeedStructure.write_seed_text handles UTF-8 text in seeds. ... ok > test_basic (germinate.tests.test_seeds.TestSingleSeedStructure) > A SingleSeedStructure object has the correct basic properties. ... ok > test_feature (germinate.tests.test_seeds.TestSingleSeedStructure) > SingleSeedStructure parses the "feature" directive correctly. ... ok > test_include (germinate.tests.test_seeds.TestSingleSeedStructure) > SingleSeedStructure parses the "include" directive correctly. ... ok > test_init_lists (germinate.tests.test_archive.TestTagFile) > TagFile may be constructed with list parameters. ... ok > test_init_strings (germinate.tests.test_archive.TestTagFile) > TagFile may be constructed with string parameters. ... ok > test_sections (germinate.tests.test_archive.TestTagFile) > Test fetching sections from a basic TagFile archive. ... ok > test_str (germinate.tests.test_ge
Bug#675971: what should we be doing?
Hi micah, On Mon, Jun 18, 2012 at 10:59:40PM -0400, micah anderson wrote: > > Is the situation that all users that are at 1.2.3-348 and older can > speak to each other and all users that are at 1.2.3-349 and greater can > speak to each other, but >=349 cannot speak to <=348 users? > > If so, is the intended plan for everyone to bump up to >=349? > > If that is true, at the very least this warrants a NEWS entry. If only it were actually that simple ... The situation looks something like this: - Prior to the squeeze freeze, and after lots of discussion, mumble picked celt 0.7.1 to be the baseline codec for its internal protocol. It still had speex support then, but would prefer to use celt. - For squeeze we provided a system library of that, so that anything else which wanted to experiment with celt would have a version to do that with too. Thorvald was going to encourage other distros to ship this version of celt so there would be interoperability with a broad range of users - but that never happened and they all shipped some other incompatible version of it instead :( Mumble already embeds it's own celt for those. - For squeeze+1, we were fairly sure celt would be obsolete and we'd have Opus by now, and the plan was to drop the system lib when that happened, with mumble making celt a private library of its own (given that it's really the only thing that actually depends on 0.7.1). Eventually all of its users would have Opus and celt could be dropped there too. - We now have Opus, and all versions of celt outside of it are no longer being maintained by anybody. - Out best laid schemes then, true to form, gang aft agley when I learned of reasonable suspicion that 0.7.1 may be carrying a remote crasher among other unfixed issues. These things were fixed in later releases of celt, but given it's an experimental codec, those versions are neither bitstream compatible with 0.7.1, nor are those fixes directly backportable since much of the code has been entirely rewritten numerous times now. - Nobody is committing to maintaining and taking responsibility for celt 0.7.1, or has sufficient 'spare' time and/or the requisite knowledge to fully investigate this further. - Upstream has completely dropped the speex support from clients in recent changes to the code. So at the time of the -349 upload, this was supposed to be temporary, while people investigated the celt issues further. But since then, it's mostly become fairly clear that isn't going to happen in any particularly reassuring way, and people have in fact just reaffirmed that nobody actually wants to be responsible for maintaining celt 0.7.1. So I can't really in good faith sign off on pushing that to the distro for the life of a stable release at this point. Which means the mumble client that we currently have will only interoperate with clients that have opus support. Calling that an "intended plan" seems like an overstatement then ... For the moment, at best, it is Present Day Reality and full of very unintended elements. Given the cloud over celt 0.7.1, encouraging anyone you care about to update to a version using Opus instead seems independently prudent. Given the general state of things, including the zeroc-ice snafu of breaking ABI to "fix the build with gcc 4.7", and the time we have remaining before the freeze, I'm having a very hard time seeing how this might possibly be a viable release candidate for Wheezy anyway at this stage. The only thing that seems to be clear, is that if mumble has a future, it's going to be with opus, not celt. So anybody who wants to help resolve this as quickly as possible, should definitely be focussing on that migration. This is largely out of my power to plan or control, so how long this will take pretty much entirely depends on how long it takes people to tell their friends "it's time to update again". All I can really hope is that it will happen before the blackhats tell them that instead. All I can really do is not make that something Debian's -security team will need to deal with over the life of Wheezy. Sorry, Ron -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678106: base-files: dummy bug, please ignore
Package: base-files Version: 6.11 Severity: serious If this release reaches testing before initscripts 2.88dsf-27, the following will happen to anybody installing a new system from scratch: base-files creates /etc/motd as a real file. initscripts in testing removes the first line of /etc/motd to create /etc/motd.tail Then, when you upgrade to initscripts in unstable, the file /etc/motd.tail is moved back to /etc/motd. The problem with this is that the /etc/motd which is created by base-files 6.11 already has the first line trimmed (i.e. it is already in "motd.tail format"). I could have avoided this by using a Breaks: but such relation is too strong. It is ok to have base-files 6.11 and initscripts 2.88dsf-22.1 in the system as far as you bootstrapped the system with base-files 6.9 or earlier. So, this is a dummy bug to prevent base-files 6.11 to enter testing. Should be closed as soon as initscripts 2.88dsf-27 or later reaches testing. If they enter testing at the same time, even better. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678108: httpcomponents-core: FTBFS twice in a row - broken clean rule
Package: httpcomponents-core Version: 4.1.4 Severity: serious Tags: patch Hi, Your package FTBFS twice in a row because the clean rule does not call mh_clean to clean up after the maven helpers used in d/rules. ~Niels -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: found 673972 in 6.1.11~dfsg-4, found 677085 in kword/1:2.4.2+1, user debian...@lists.debian.org ...
Processing commands for cont...@bugs.debian.org: > found 673972 6.1.11~dfsg-4 Bug #673972 [sympa] sympa: unowned directories after purge Marked as found in versions sympa/6.1.11~dfsg-4. > found 677085 kword/1:2.4.2+1 Bug #677085 [src:calligra] fix conflict/replaces with old koffice names The source kword and version 1:2.4.2+1 do not appear to match any binary packages Marked as found in versions kword/1:2.4.2+1. > user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was deb...@abeckmann.de). > usertags 677759 piuparts Bug#677759: postinst: line 58: /etc/selinux/default/setrans.conf: No such file or directory There were no usertags set. Usertags are now: piuparts. > found 646837 3.6.2.0-4.5 Bug #646837 [bugzilla3] Without liburl-perl bugzilla3 cant be installed Marked as found in versions bugzilla/3.6.2.0-4.5. > usertags 646837 piuparts Bug#646837: Without liburl-perl bugzilla3 cant be installed There were no usertags set. Usertags are now: piuparts. > usertags 676463 piuparts Bug#676463: sysv-rc: complains incorrectly(?) about obsolete init.d scripts for fuse and others There were no usertags set. Usertags are now: piuparts. > thanks Stopping processing here. Please contact me if you need assistance. -- 646837: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646837 673972: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=673972 676463: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676463 677085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677085 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#669522: coinor-cbc: FTBFS: make[3]: *** No rule to make target `/usr/lib/libCgl.la', needed by `cbc'. Stop.
* Vincent Legout [120619 09:25]: > tags 669522 patch > thanks > > Lucas Nussbaum writes: > > > During a rebuild of all packages in sid, your package failed to build on > > amd64. > > It should build fine with the attached patch. It was caused by libCgl.la > no longer being shipped by coinor-libcgl-dev (see #633173). > > Vincent Hello, Thanks for providing a patch for this bug. I'm in the process of adopting this package (ITA: #645087), so please don't NMU this too soon, I will integrate it in a few days in a maintainer upload. Have a nice day ! -- Etienne Millon -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#670292: xemacs ... fails to upgrade from squeeze
Hi, why is this bug flagged as affecting tuareg-mode? If the reason is the dependency on xemacs21|emacsen : this has been changed to emacs23|emacsen in version 1:2.0.6-2, uploaded this morning. -Ralf. -- Ralf Treinen Laboratoire Preuves, Programmes et Systèmes Université Paris Diderot, Paris, France. http://www.pps.univ-paris-diderot.fr/~treinen/ => New email address: trei...@pps.univ-paris-diderot.fr <= -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676109: marked as done (zonecheck: FTBFS: installer.rb:183:in `gsub!': invalid byte sequence in US-ASCII (ArgumentError))
Your message dated Tue, 19 Jun 2012 09:49:45 + with message-id and subject line Bug#676109: fixed in zonecheck 3.0.3-2 has caused the Debian Bug report #676109, regarding zonecheck: FTBFS: installer.rb:183:in `gsub!': invalid byte sequence in US-ASCII (ArgumentError) 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.) -- 676109: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676109 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: zonecheck Version: 3.0.3-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120604 qa-ftbfs User: debian-r...@lists.debian.org Usertags: default19 Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > fakeroot debian/rules binary > dh_testdir > dh_testroot > dh_clean -k > dh_clean: dh_clean -k is deprecated; use dh_prep instead > dh_installdirs > # Add here commands to install the package into debian/zonecheck. > /usr/bin/ruby installer.rb -DCHROOT=/«PKGBUILDDIR»/debian/zonecheck \ > -DPREFIX=/usr -DETCDIR=/etc -DETCDIST= \ > -DLIBEXEC=/usr/share -DMANDIR=/usr/share/man > -DRUBY=/usr/bin/ruby \ > common cli doc > mkdir -p /«PKGBUILDDIR»/debian/zonecheck/usr/share/zonecheck > cp -r zc /«PKGBUILDDIR»/debian/zonecheck/usr/share/zonecheck > chmod 755 /«PKGBUILDDIR»/debian/zonecheck/usr/share/zonecheck/zc/zc.rb > cp -r lib /«PKGBUILDDIR»/debian/zonecheck/usr/share/zonecheck > cp -r test /«PKGBUILDDIR»/debian/zonecheck/usr/share/zonecheck > cp -r locale /«PKGBUILDDIR»/debian/zonecheck/usr/share/zonecheck > mkdir -p /«PKGBUILDDIR»/debian/zonecheck/etc/zonecheck > cp etc/zonecheck/zc.conf /«PKGBUILDDIR»/debian/zonecheck/etc/zonecheck > cp etc/zonecheck/rootservers /«PKGBUILDDIR»/debian/zonecheck/etc/zonecheck > cp etc/zonecheck/default.profile etc/zonecheck/afnic.profile > etc/zonecheck/reverse.profile etc/zonecheck/de.profile > /«PKGBUILDDIR»/debian/zonecheck/etc/zonecheck > chmod 755 /«PKGBUILDDIR»/debian/zonecheck/usr/share/zonecheck/zc/zc.rb > mkdir -p /«PKGBUILDDIR»/debian/zonecheck/usr/bin > ln -sf /usr/share/zonecheck/zc/zc.rb > /«PKGBUILDDIR»/debian/zonecheck/usr/bin/zonecheck > mkdir -p /«PKGBUILDDIR»/debian/zonecheck/usr/share/man/man1 > install -c -m 0644 man/zonecheck.1 > /«PKGBUILDDIR»/debian/zonecheck/usr/share/man/man1/zonecheck.1 > mkdir -p /«PKGBUILDDIR»/debian/zonecheck/usr/share/doc/zonecheck > install -c -m 0644 README TODO BUGS HISTORY CREDITS > /«PKGBUILDDIR»/debian/zonecheck/usr/share/doc/zonecheck > ==> Installing core components > > ==> Installing libraries > > ==> Installing tests > > ==> Installing locale > > ==> Installing default configuration file > > ==> Patching core components > > ==> Installing CLI > > ==> Installing documentation > > ==> Info > > !!! Before using ZoneCheck, please edit the file: zc.conf > > # Patch the configuration file for Linux netkit ping > /usr/bin/ruby -p -i \ > -e > "\$_.gsub"\!"(/()/, > '\1ping -n -q -w 5 -c 5 %s > /dev/null\2')" \ > -e > "\$_.gsub"\!"(/()/, > '\1ping6 -n -q -w 5 -c 5 %s > /dev/null\2')" \ > /«PKGBUILDDIR»/debian/zonecheck/etc/zonecheck/zc.conf > # Add here commands to install the package into debian/zonecheck-cgi. > /usr/bin/ruby installer.rb -DCHROOT=/«PKGBUILDDIR»/debian/zonecheck-cgi \ >-DPREFIX=/usr -DETCDIR=/etc -DETCDIST= \ > -DCGIDIR=/usr/lib/cgi-bin/ -DLIBEXEC=/usr/share \ > -DMANDIR=/usr/share/man -DWWWDIR=/usr/share/zonecheck-cgi \ >-DWWWCGIDIR=/cgi-bin -DRUBY=/usr/bin/ruby \ > cgi > mkdir -p /«PKGBUILDDIR»/debian/zonecheck-cgi/usr/share/zonecheck-cgi > cp -r www/zonecheck.conf.in > /«PKGBUILDDIR»/debian/zonecheck-cgi/usr/share/zonecheck-cgi > cp -r www/img /«PKGBUILDDIR»/debian/zonecheck-cgi/usr/share/zonecheck-cgi > cp -r www/style /«PKGBUILDDIR»/debian/zonecheck-cgi/usr/share/zonecheck-cgi > cp -r www/html /«PKGBUILDDIR»/debian/zonecheck-cgi/usr/share/zonecheck-cgi > cp -r www/js /«PKGBUILDDIR»/debian/zonecheck-cgi/usr/share/zonecheck-cgi > mkdir -p /«PKGBUILDDIR»/debian/zonecheck-cgi/usr/lib/cgi-bin/ > ln -sf /usr/share/zonecheck/zc/zc.rb > /«PKGBUILDDIR»/debian/zonecheck-cgi/usr/lib/cgi-bin//zc.cgi > installer.rb:183:in `gsub!': invalid byte sequence in US-ASCII (ArgumentError) > from installer.rb:183:in `block (2 levels) in patch_cgi' > from installer.rb:182:in `each' > from installer.rb:182:in `block in patch_cgi' > from installer.rb:180:in `each' >
Bug#676173: marked as done (zonecheck: broken with Ruby 1.9: ERROR: uninitialized constant Psych::ParseError)
Your message dated Tue, 19 Jun 2012 09:49:45 + with message-id and subject line Bug#676173: fixed in zonecheck 3.0.3-2 has caused the Debian Bug report #676173, regarding zonecheck: broken with Ruby 1.9: ERROR: uninitialized constant Psych::ParseError 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.) -- 676173: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676173 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: zonecheck Version: 3.0.3-1 Severity: grave User: debian-r...@lists.debian.org Usertags: default19 zonecheck in sid doesn't work at all, it just says: % zonecheck debian.org /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in `require': iconv will be deprecated in the future, use String#encode instead. ERROR: uninitialized constant Psych::ParseError zsh: exit 4 zonecheck debian.org % This is probably related to the switch to Ruby 1.9. There's a similar bug in the upstream bug tracker: https://savannah.nongnu.org/bugs/?35190 Thanks, -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (900, 'unstable'), (850, 'testing'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.4.1-ore (SMP w/8 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 zonecheck depends on: ii iputils-ping3:20101006-1+b1 ii libdns-ruby 1.53-1 ii ruby4.9 ii ruby-dnsruby [libdns-ruby] 1.53-1 ii ruby1.8 [ruby] 1.8.7.358-4 Versions of packages zonecheck recommends: pn libopenssl-ruby zonecheck suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- Source: zonecheck Source-Version: 3.0.3-2 We believe that the bug you reported is fixed in the latest version of zonecheck, which is due to be installed in the Debian FTP archive: zonecheck-cgi_3.0.3-2_all.deb to main/z/zonecheck/zonecheck-cgi_3.0.3-2_all.deb zonecheck_3.0.3-2.debian.tar.gz to main/z/zonecheck/zonecheck_3.0.3-2.debian.tar.gz zonecheck_3.0.3-2.dsc to main/z/zonecheck/zonecheck_3.0.3-2.dsc zonecheck_3.0.3-2_all.deb to main/z/zonecheck/zonecheck_3.0.3-2_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 676...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Sebastien Delafond (supplier of updated zonecheck package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Mon, 18 Jun 2012 15:44:33 +0200 Source: zonecheck Binary: zonecheck zonecheck-cgi Architecture: source all Version: 3.0.3-2 Distribution: unstable Urgency: low Maintainer: Sebastien Delafond Changed-By: Sebastien Delafond Description: zonecheck - DNS configuration checker zonecheck-cgi - DNS configuration checker (web interface) Closes: 676109 676173 Changes: zonecheck (3.0.3-2) unstable; urgency=low . * Fix problems related to ruby 1.9, thanks to patches from Antonio Terceiro (Closes: #676109, #676173) * Bump-up Standards revision. Checksums-Sha1: a5146690b7024897f653ac66943ce22752dc 1152 zonecheck_3.0.3-2.dsc 04c8c16968654fb5fcc9fcaeda4b99c643d888f1 12163 zonecheck_3.0.3-2.debian.tar.gz ea073f02b5fcb6e5fe231606f881637ce29a3825 192398 zonecheck_3.0.3-2_all.deb 14479b263bf423ab8edb733358f8a2e0ade949bd 37690 zonecheck-cgi_3.0.3-2_all.deb Checksums-Sha256: 54bd424d8194a409c0a0e39bcf4e41dba33cf06e46ab0cd0b198b4b6ef76 1152 zonecheck_3.0.3-2.dsc 69df261372f712cb9aad51602bd34df5164a5e13556858083e3c8152622ea421 12163 zonecheck_3.0.3-2.debian.tar.gz ef22ec30398c6a370823e4eabf81ab84ad99cfff5ab80e2ec9f0b09c63a8716f 192398 zonecheck_3.0.3-2_all.deb 4b2dec34465d6445a161c19a50b3421d4e1a142f4d11f3131d460c3cb072743a 37690 zonecheck-cgi_3.0.3-2_all.deb Files: a8caa6232edab00faa5f92508c726e04 1152 net optional zonecheck_3.0.3-2.dsc 9673380aff0cdb1ac20267e57bff3d31 12163 net optional zonecheck_3.0.3-2.debian.tar.gz 8b4b417a3f752ec798fb5246ef092cd4 192398 net optional zonecheck_3.0.3-2_all.deb 90dba7125522654ff8cee10f5b0481f9 37690 net optional zonecheck-cgi_3.0.3-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.11 (GNU/Linux) iEYEARECAAYFAk/fMpAACgkQiZgNKc
Processed: tagging 668662
Processing commands for cont...@bugs.debian.org: > tags 668662 + pending Bug #668662 [cups] cups needs a more strict dependency on libcups Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 668662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668662 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: forcibly merging 668662 677180
Processing commands for cont...@bugs.debian.org: > forcemerge 668662 677180 Bug #668662 [cups] cups needs a more strict dependency on libcups Bug #668662 [cups] cups needs a more strict dependency on libcups Marked as found in versions cups/1.5.3-1. Bug #677180 [cups] cups crash with "undefined symbol: _ppdCacheGetFinishingOptions" Marked as found in versions cups/1.5.2-10. Added tag(s) pending. Merged 668662 677180 > thanks Stopping processing here. Please contact me if you need assistance. -- 668662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668662 677180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677180 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#676800: [Pkg-octave-devel] Bug#676800: octave-java: completely breaks octave
Sébastien Villemot writes: > Package: octave-java > Version: 1.2.8-4 > Severity: grave > > This version of octave-java completely breaks octave. Note that this does not appear to be a GCC 4.7 bug. I tried with gcc 4.6.3-1 (in testing as of today) and with gcc 4.7.1-1 (in unstable as of today), and the bug is present in all cases. -- Sébastien Villemot Researcher in Economics & Debian Maintainer http://www.dynare.org/sebastien Phone: +33-1-40-77-84-04 - GPG Key: 4096R/381A7594 pgpIKO50q866U.pgp Description: PGP signature
Bug#669522: coinor-cbc: FTBFS: make[3]: *** No rule to make target `/usr/lib/libCgl.la', needed by `cbc'. Stop.
Salut Etienne, Etienne Millon writes: > Thanks for providing a patch for this bug. I'm in the process of > adopting this package (ITA: #645087), so please don't NMU this too > soon, I will integrate it in a few days in a maintainer upload. Thanks for taking care of this package. I should be able to sponsor the upload if needed. Vincent -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#677565: msva-perl: Insecure dependency in socket while running with -T switch at /usr/lib/perl/5.14/IO/Socket.pm line 80
Hello, On Thu, Jun 14, 2012 at 11:48:49PM +0200, intrig...@debian.org wrote: > Package: msva-perl > Version: 0.8-2 > Severity: grave > > $ cat $HOME/.monkeysphere/monkeysphere.conf > USE_VALIDATION_AGENT=true > KEYSERVER=keys.indymedia.org > $ . $HOME/.monkeysphere/monkeysphere.conf > $ msva-perl > Use of uninitialized value $loglevel in lc at > /usr/share/perl5/Crypt/Monkeysphere/MSVA/Logger.pm line 91. > Insecure dependency in socket while running with -T switch at > /usr/lib/perl/5.14/IO/Socket.pm line 80. > zsh: exit 255 msva-perl > > This might be related to upgrading libnet-server-perl to 2.005-1. This broke my X login in a way that was perplexing to untangle. It seems as if monkeysphere inserts itself into the X session startup by way of a file in /etc/X11/Xsession.d. monkeysphere-validation-agent failing then made the whole Xsession execution fail, which is really unfriendly. Downgrading libnet-server-perl to 0.99-4 fixes it. Perhaps you should consider blocking that from migrating if it is exposing bugs like this. Cheers, -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] PhD student [ i...@cs.nott.ac.uk ] signature.asc Description: Digital signature
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 674350 pending Bug #674350 [src:vxl] vxl: FTBFS: dimosct.h:124:17: error: 'scaleData' was not declared in this scope, and no declarations were found by argument-dependent lookup at the point of instantiation [-fpermissive] Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 674350: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674350 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: bug 676800 is forwarded to http://sourceforge.net/mailarchive/message.php?msg_id=29427257
Processing commands for cont...@bugs.debian.org: > forwarded 676800 > http://sourceforge.net/mailarchive/message.php?msg_id=29427257 Bug #676800 [octave-java] octave-java: completely breaks octave Set Bug forwarded-to-address to 'http://sourceforge.net/mailarchive/message.php?msg_id=29427257'. > thanks Stopping processing here. Please contact me if you need assistance. -- 676800: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676800 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: bug 678026 is forwarded to https://bugzilla.gnome.org/show_bug.cgi?id=678348
Processing commands for cont...@bugs.debian.org: > forwarded 678026 https://bugzilla.gnome.org/show_bug.cgi?id=678348 Bug #678026 [libatk-adaptor] libatk-adaptor: insecure tempdir handling Ignoring request to change the forwarded-to-address of bug#678026 to the same value > thanks Stopping processing here. Please contact me if you need assistance. -- 678026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678026 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#668662: marked as done (cups needs a more strict dependency on libcups)
Your message dated Tue, 19 Jun 2012 10:47:27 + with message-id and subject line Bug#668662: fixed in cups 1.5.3-2 has caused the Debian Bug report #668662, regarding cups needs a more strict dependency on libcups 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.) -- 668662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668662 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cups Version: 1.5.2-10 Severity: important /usr/lib/cups/backend/ipp fails with: $ sudo /usr/lib/cups/backend/ipp /usr/lib/cups/backend/ipp: symbol lookup error: /usr/lib/cups/backend/ipp: undefined symbol: _ppdCacheGetFinishingValues I did a quick rebuild with the hardening flag changes from #662821 reverted and that fixes the symbol lookup error. So I guess these flags should be reconsidered. I did not test if other parts of cups than the ipp backend are affected as well. Gaudenz -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (800, 'testing'), (700, 'unstable'), (50, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages cups depends on: ii adduser3.113+nmu1 ii bc 1.06.95-2+b1 ii cups-client1.5.2-10 ii cups-common1.5.2-5 ii cups-filters 1.0.2-1 ii cups-ppdc 1.5.2-5 ii debconf [debconf-2.0] 1.5.42 ii dpkg 1.16.2 ii ghostscript9.05~dfsg-4 ii libavahi-client3 0.6.31-1 ii libavahi-common3 0.6.31-1 ii libc6 2.13-27 ii libcups2 1.5.2-5 ii libcupscgi11.5.2-5 ii libcupsimage2 1.5.2-5 ii libcupsmime1 1.5.2-5 ii libcupsppdc1 1.5.2-5 ii libdbus-1-31.5.12-1 ii libgcc11:4.7.0-1 ii libgnutls262.12.18-1 ii libgssapi-krb5-2 1.10+dfsg~beta1-2 ii libkrb5-3 1.10+dfsg~beta1-2 ii libldap-2.4-2 2.4.28-1.1 ii libpam0g 1.1.3-7 ii libpaper1 1.1.24+nmu1 ii libslp11.2.1-9 ii libstdc++6 4.7.0-1 ii libusb-1.0-0 2:1.0.9~rc3-3 ii lsb-base 4.1+Debian0 ii poppler-utils 0.16.7-3 ii procps 1:3.3.2-3 ii ssl-cert 1.0.28 Versions of packages cups recommends: ii avahi-daemon 0.6.31-1 ii colord 0.1.18-1 ii foomatic-filters 4.0.15-1 ii ghostscript-cups 9.05~dfsg-4 ii printer-driver-gutenprint 5.2.7-5 Versions of packages cups suggests: ii cups-bsd 1.5.2-10 ii cups-pdf 2.6.1-6 ii foomatic-db20120322-1 ii hplip 3.12.2-1 ii printer-driver-hpcups 3.12.2-1 ii smbclient 2:3.6.3-2 ii udev 175-3.1 -- Configuration Files: /etc/cups/cupsd.conf changed [not included] -- debconf information: cupsys/raw-print: true cupsys/backend: ipp, lpd, socket, usb, snmp, dnssd --- End Message --- --- Begin Message --- Source: cups Source-Version: 1.5.3-2 We believe that the bug you reported is fixed in the latest version of cups, which is due to be installed in the Debian FTP archive: cups-bsd_1.5.3-2_amd64.deb to main/c/cups/cups-bsd_1.5.3-2_amd64.deb cups-client_1.5.3-2_amd64.deb to main/c/cups/cups-client_1.5.3-2_amd64.deb cups-common_1.5.3-2_all.deb to main/c/cups/cups-common_1.5.3-2_all.deb cups-dbg_1.5.3-2_amd64.deb to main/c/cups/cups-dbg_1.5.3-2_amd64.deb cups-ppdc_1.5.3-2_amd64.deb to main/c/cups/cups-ppdc_1.5.3-2_amd64.deb cups_1.5.3-2.debian.tar.gz to main/c/cups/cups_1.5.3-2.debian.tar.gz cups_1.5.3-2.dsc to main/c/cups/cups_1.5.3-2.dsc cups_1.5.3-2_amd64.deb to main/c/cups/cups_1.5.3-2_amd64.deb cupsddk_1.5.3-2_all.deb to main/c/cups/cupsddk_1.5.3-2_all.deb libcups2-dev_1.5.3-2_amd64.deb to main/c/cups/libcups2-dev_1.5.3-2_amd64.deb libcups2_1.5.3-2_amd64.deb to main/c/cups/libcups2_1.5.3-2_amd64.deb libcupscgi1-dev_1.5.3-2_amd64.deb to main/c/cups/libcupscgi1-dev_1.5.3-2_amd64.deb libcupscgi1_1.5.3-2_amd64.deb to main/c/cups/libcupscgi1_1.5.3-2_amd64.deb libcupsdriver1-dev_1.5.3-2_amd64.deb to main/c/cups/libcupsdriver1-dev_1.5.3-2_amd64.deb libcupsdriver1_1.5.3-2_amd64.deb to main/c/cups/libcupsdriver1_1.5.3-2_amd64.deb libcupsimage2-dev_1.5.3-2_amd64.deb to main/c/cups/libcupsimage2-dev_1.5.3-2_amd64.deb libcupsimage2_1.5.3-2_amd64.deb to main/c/cu
Bug#677180: marked as done (cups crash with "undefined symbol: _ppdCacheGetFinishingOptions")
Your message dated Tue, 19 Jun 2012 10:47:27 + with message-id and subject line Bug#668662: fixed in cups 1.5.3-2 has caused the Debian Bug report #668662, regarding cups crash with "undefined symbol: _ppdCacheGetFinishingOptions" 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.) -- 668662: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=668662 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cups Version: 1.5.3-1 Severity: serious Justification: required Dear Maintainer, After a recent upgrade, cups does not work anymore. # service cups restart [] Restarting Common Unix Printing System: cupsd/usr/sbin/cupsd: symbol lookup error: /usr/sbin/cupsd: undefined symbol: _ppdCacheGetFinishingOptions failed! Moreover, HPlip does not find the PPD file where it should find it, but it’s not a cups bug. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.38-2-686-bigmem (SMP w/3 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages cups depends on: ii adduser3.113+nmu3 ii bc 1.06.95-2 ii cups-client1.5.3-1 ii cups-common1.5.3-1 ii cups-filters 1.0.18-2+b1 ii cups-ppdc 1.5.3-1 ii debconf [debconf-2.0] 1.5.43 ii dpkg 1.16.3 ii ghostscript9.05~dfsg-6 ii libavahi-client3 0.6.31-1 ii libavahi-common3 0.6.31-1 ii libc6 2.13-33 ii libcups2 1.5.0-8 ii libcupscgi11.5.3-1 ii libcupsimage2 1.5.3-1 ii libcupsmime1 1.5.3-1 ii libcupsppdc1 1.5.3-1 ii libdbus-1-31.5.12-1 ii libgcc11:4.7.0-8 ii libgnutls262.12.19-1 ii libgssapi-krb5-2 1.10.1+dfsg-1 ii libkrb5-3 1.10.1+dfsg-1 ii libldap-2.4-2 2.4.28-1.1 ii libpam0g 1.1.3-7.1 ii libpaper1 1.1.24+nmu2 ii libslp11.2.1-9 ii libstdc++6 4.7.0-8 ii libusb-1.0-0 2:1.0.9-1 ii lsb-base 4.1+Debian6 ii poppler-utils 0.18.4-2 ii procps 1:3.3.2-3 ii ssl-cert 1.0.28 Versions of packages cups recommends: ii avahi-daemon 0.6.31-1 ii colord 0.1.21-1 ii foomatic-filters 4.0.15-1 ii ghostscript-cups 9.05~dfsg-6 ii printer-driver-gutenprint 5.2.7-5 Versions of packages cups suggests: ii cups-bsd 1.5.3-1 ii cups-pdf 2.6.1-6 ii foomatic-db20120523-1 ii hplip 3.12.2-1 ii printer-driver-hpcups 3.12.2-1 ii smbclient 2:3.6.5-3 ii udev 175-3.1 -- Configuration Files: /etc/cups/cupsd.conf changed: LogLevel warn MaxLogSize 0 SystemGroup lpadmin Listen localhost:631 Listen /var/run/cups/cups.sock Browsing On BrowseOrder allow,deny BrowseAllow all BrowseRemoteProtocols CUPS BrowseLocalProtocols DefaultAuthType Basic # Restrict access to the server... Order allow,deny # Restrict access to the admin pages... Order allow,deny AuthType Default Require user @SYSTEM # Restrict access to the configuration files... Order allow,deny Require user @OWNER @SYSTEM Order deny,allow AuthType Default Require user @SYSTEM Order deny,allow AuthType Default Require user @SYSTEM Order deny,allow Require user @OWNER @SYSTEM Order deny,allow Order deny,allow AuthType Default Order deny,allow AuthType Default Require user @OWNER @SYSTEM Order deny,allow AuthType Default Require user @SYSTEM Order deny,allow AuthType Default Require user @SYSTEM Order deny,allow AuthType Default Require user @OWNER @SYSTEM Order deny,allow Order deny,allow -- debconf information: cupsys/backend: ipp, lpd, socket, usb, snmp, dnssd cupsys/raw-print: true --- End Message --- --- Begin Message --- Source: cups Source-Version: 1.5.3-2 We believe that the bug you reported is fixed in the latest version of cups, which is due to be installed in the Debian FTP archive: cups-bsd_1.5.3-2_amd64.deb to main/c/cups/cups-bsd_1.5.3-2_amd64.deb cups-client_1.5.3-2_amd64.deb to main/c/cups/cups-client_1.5.3-2_amd64.deb cups-common_1.5.3-2_all.deb to main/c/cups/cups-common_1.5.3-2_all.
Bug#677180: marked as done (cups crash with "undefined symbol: _ppdCacheGetFinishingOptions")
Your message dated Tue, 19 Jun 2012 10:47:27 + with message-id and subject line Bug#677180: fixed in cups 1.5.3-2 has caused the Debian Bug report #677180, regarding cups crash with "undefined symbol: _ppdCacheGetFinishingOptions" 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.) -- 677180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677180 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cups Version: 1.5.3-1 Severity: serious Justification: required Dear Maintainer, After a recent upgrade, cups does not work anymore. # service cups restart [] Restarting Common Unix Printing System: cupsd/usr/sbin/cupsd: symbol lookup error: /usr/sbin/cupsd: undefined symbol: _ppdCacheGetFinishingOptions failed! Moreover, HPlip does not find the PPD file where it should find it, but it’s not a cups bug. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.38-2-686-bigmem (SMP w/3 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages cups depends on: ii adduser3.113+nmu3 ii bc 1.06.95-2 ii cups-client1.5.3-1 ii cups-common1.5.3-1 ii cups-filters 1.0.18-2+b1 ii cups-ppdc 1.5.3-1 ii debconf [debconf-2.0] 1.5.43 ii dpkg 1.16.3 ii ghostscript9.05~dfsg-6 ii libavahi-client3 0.6.31-1 ii libavahi-common3 0.6.31-1 ii libc6 2.13-33 ii libcups2 1.5.0-8 ii libcupscgi11.5.3-1 ii libcupsimage2 1.5.3-1 ii libcupsmime1 1.5.3-1 ii libcupsppdc1 1.5.3-1 ii libdbus-1-31.5.12-1 ii libgcc11:4.7.0-8 ii libgnutls262.12.19-1 ii libgssapi-krb5-2 1.10.1+dfsg-1 ii libkrb5-3 1.10.1+dfsg-1 ii libldap-2.4-2 2.4.28-1.1 ii libpam0g 1.1.3-7.1 ii libpaper1 1.1.24+nmu2 ii libslp11.2.1-9 ii libstdc++6 4.7.0-8 ii libusb-1.0-0 2:1.0.9-1 ii lsb-base 4.1+Debian6 ii poppler-utils 0.18.4-2 ii procps 1:3.3.2-3 ii ssl-cert 1.0.28 Versions of packages cups recommends: ii avahi-daemon 0.6.31-1 ii colord 0.1.21-1 ii foomatic-filters 4.0.15-1 ii ghostscript-cups 9.05~dfsg-6 ii printer-driver-gutenprint 5.2.7-5 Versions of packages cups suggests: ii cups-bsd 1.5.3-1 ii cups-pdf 2.6.1-6 ii foomatic-db20120523-1 ii hplip 3.12.2-1 ii printer-driver-hpcups 3.12.2-1 ii smbclient 2:3.6.5-3 ii udev 175-3.1 -- Configuration Files: /etc/cups/cupsd.conf changed: LogLevel warn MaxLogSize 0 SystemGroup lpadmin Listen localhost:631 Listen /var/run/cups/cups.sock Browsing On BrowseOrder allow,deny BrowseAllow all BrowseRemoteProtocols CUPS BrowseLocalProtocols DefaultAuthType Basic # Restrict access to the server... Order allow,deny # Restrict access to the admin pages... Order allow,deny AuthType Default Require user @SYSTEM # Restrict access to the configuration files... Order allow,deny Require user @OWNER @SYSTEM Order deny,allow AuthType Default Require user @SYSTEM Order deny,allow AuthType Default Require user @SYSTEM Order deny,allow Require user @OWNER @SYSTEM Order deny,allow Order deny,allow AuthType Default Order deny,allow AuthType Default Require user @OWNER @SYSTEM Order deny,allow AuthType Default Require user @SYSTEM Order deny,allow AuthType Default Require user @SYSTEM Order deny,allow AuthType Default Require user @OWNER @SYSTEM Order deny,allow Order deny,allow -- debconf information: cupsys/backend: ipp, lpd, socket, usb, snmp, dnssd cupsys/raw-print: true --- End Message --- --- Begin Message --- Source: cups Source-Version: 1.5.3-2 We believe that the bug you reported is fixed in the latest version of cups, which is due to be installed in the Debian FTP archive: cups-bsd_1.5.3-2_amd64.deb to main/c/cups/cups-bsd_1.5.3-2_amd64.deb cups-client_1.5.3-2_amd64.deb to main/c/cups/cups-client_1.5.3-2_amd64.deb cups-common_1.5.3-2_all.deb to main/c/cups/cups-common_1.5.3-2_all.
Bug#668662: marked as done (cups needs a more strict dependency on libcups)
Your message dated Tue, 19 Jun 2012 10:47:27 + with message-id and subject line Bug#677180: fixed in cups 1.5.3-2 has caused the Debian Bug report #677180, regarding cups needs a more strict dependency on libcups 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.) -- 677180: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677180 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: cups Version: 1.5.2-10 Severity: important /usr/lib/cups/backend/ipp fails with: $ sudo /usr/lib/cups/backend/ipp /usr/lib/cups/backend/ipp: symbol lookup error: /usr/lib/cups/backend/ipp: undefined symbol: _ppdCacheGetFinishingValues I did a quick rebuild with the hardening flag changes from #662821 reverted and that fixes the symbol lookup error. So I guess these flags should be reconsidered. I did not test if other parts of cups than the ipp backend are affected as well. Gaudenz -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (800, 'testing'), (700, 'unstable'), (50, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=de_CH.UTF-8, LC_CTYPE=de_CH.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages cups depends on: ii adduser3.113+nmu1 ii bc 1.06.95-2+b1 ii cups-client1.5.2-10 ii cups-common1.5.2-5 ii cups-filters 1.0.2-1 ii cups-ppdc 1.5.2-5 ii debconf [debconf-2.0] 1.5.42 ii dpkg 1.16.2 ii ghostscript9.05~dfsg-4 ii libavahi-client3 0.6.31-1 ii libavahi-common3 0.6.31-1 ii libc6 2.13-27 ii libcups2 1.5.2-5 ii libcupscgi11.5.2-5 ii libcupsimage2 1.5.2-5 ii libcupsmime1 1.5.2-5 ii libcupsppdc1 1.5.2-5 ii libdbus-1-31.5.12-1 ii libgcc11:4.7.0-1 ii libgnutls262.12.18-1 ii libgssapi-krb5-2 1.10+dfsg~beta1-2 ii libkrb5-3 1.10+dfsg~beta1-2 ii libldap-2.4-2 2.4.28-1.1 ii libpam0g 1.1.3-7 ii libpaper1 1.1.24+nmu1 ii libslp11.2.1-9 ii libstdc++6 4.7.0-1 ii libusb-1.0-0 2:1.0.9~rc3-3 ii lsb-base 4.1+Debian0 ii poppler-utils 0.16.7-3 ii procps 1:3.3.2-3 ii ssl-cert 1.0.28 Versions of packages cups recommends: ii avahi-daemon 0.6.31-1 ii colord 0.1.18-1 ii foomatic-filters 4.0.15-1 ii ghostscript-cups 9.05~dfsg-4 ii printer-driver-gutenprint 5.2.7-5 Versions of packages cups suggests: ii cups-bsd 1.5.2-10 ii cups-pdf 2.6.1-6 ii foomatic-db20120322-1 ii hplip 3.12.2-1 ii printer-driver-hpcups 3.12.2-1 ii smbclient 2:3.6.3-2 ii udev 175-3.1 -- Configuration Files: /etc/cups/cupsd.conf changed [not included] -- debconf information: cupsys/raw-print: true cupsys/backend: ipp, lpd, socket, usb, snmp, dnssd --- End Message --- --- Begin Message --- Source: cups Source-Version: 1.5.3-2 We believe that the bug you reported is fixed in the latest version of cups, which is due to be installed in the Debian FTP archive: cups-bsd_1.5.3-2_amd64.deb to main/c/cups/cups-bsd_1.5.3-2_amd64.deb cups-client_1.5.3-2_amd64.deb to main/c/cups/cups-client_1.5.3-2_amd64.deb cups-common_1.5.3-2_all.deb to main/c/cups/cups-common_1.5.3-2_all.deb cups-dbg_1.5.3-2_amd64.deb to main/c/cups/cups-dbg_1.5.3-2_amd64.deb cups-ppdc_1.5.3-2_amd64.deb to main/c/cups/cups-ppdc_1.5.3-2_amd64.deb cups_1.5.3-2.debian.tar.gz to main/c/cups/cups_1.5.3-2.debian.tar.gz cups_1.5.3-2.dsc to main/c/cups/cups_1.5.3-2.dsc cups_1.5.3-2_amd64.deb to main/c/cups/cups_1.5.3-2_amd64.deb cupsddk_1.5.3-2_all.deb to main/c/cups/cupsddk_1.5.3-2_all.deb libcups2-dev_1.5.3-2_amd64.deb to main/c/cups/libcups2-dev_1.5.3-2_amd64.deb libcups2_1.5.3-2_amd64.deb to main/c/cups/libcups2_1.5.3-2_amd64.deb libcupscgi1-dev_1.5.3-2_amd64.deb to main/c/cups/libcupscgi1-dev_1.5.3-2_amd64.deb libcupscgi1_1.5.3-2_amd64.deb to main/c/cups/libcupscgi1_1.5.3-2_amd64.deb libcupsdriver1-dev_1.5.3-2_amd64.deb to main/c/cups/libcupsdriver1-dev_1.5.3-2_amd64.deb libcupsdriver1_1.5.3-2_amd64.deb to main/c/cups/libcupsdriver1_1.5.3-2_amd64.deb libcupsimage2-dev_1.5.3-2_amd64.deb to main/c/cups/libcupsimage2-dev_1.5.3-2_amd64.deb libcupsimage2_1.5.3-2_amd64.deb to main/c/cu
Bug#640939: [Pkg-cups-devel] Bug#640939: Raising severity of 640939
tag 640939 moreinfo unreproducible thanks Hello all, I discussed this with Till, and we both have no real idea how to get to a situation where lpadmin as root asks for a password. It is already called with -h /var/run/cups/cups.sock to ensure it's not talking to a remote server. It seems you need a particular cups configuration to achieve this. Can you please attach your /etc/cups/cupsd.conf, /etc/cups/client.conf, and ~/.cups/client.conf ? (You might not have the latter two) Thanks, Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) signature.asc Description: Digital signature
Processed: Re: [Pkg-cups-devel] Bug#640939: Raising severity of 640939
Processing commands for cont...@bugs.debian.org: > tag 640939 moreinfo unreproducible Bug #640939 [cups] hplip-cups: asks for root password when cups updates PPDs Bug #662915 [cups] cups: Asking for root password on localhost during an update of ppd files. Added tag(s) unreproducible and moreinfo. Added tag(s) unreproducible and moreinfo. > thanks Stopping processing here. Please contact me if you need assistance. -- 640939: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640939 662915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=662915 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#593607: PCmanfm file deletion ver 0.9.10-3
I can confirm this bug on pcmanfm ver 0.9.10-3 (debian testing). For some reason target device was unmounted, though not copied the source files were removed! Very not cool! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: found 678085 in 0.1-1
Processing commands for cont...@bugs.debian.org: > found 678085 0.1-1 Bug #678085 [python-lua] python-lua: unsuitable for testing Marked as found in versions python-lua/0.1-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 678085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678085 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: found 678085 in 0.1-1
Processing commands for cont...@bugs.debian.org: > found 678085 0.1-1 Bug #678085 [python-lua] python-lua: unsuitable for testing Ignoring request to alter found versions of bug #678085 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 678085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678085 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: found 678085 in 0.1-1
Processing commands for cont...@bugs.debian.org: > found 678085 0.1-1 Bug #678085 [python-lua] python-lua: unsuitable for testing Ignoring request to alter found versions of bug #678085 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 678085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678085 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: found 678085 in 0.1-1
Processing commands for cont...@bugs.debian.org: > found 678085 0.1-1 Bug #678085 [python-lua] python-lua: unsuitable for testing Ignoring request to alter found versions of bug #678085 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 678085: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678085 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: found 678026 in
Processing commands for cont...@bugs.debian.org: > found 678026 Bug #678026 [libatk-adaptor] libatk-adaptor: insecure tempdir handling Ignoring request to alter fixed versions of bug #678026 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 678026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678026 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: found 678026 in 1.91.90
Processing commands for cont...@bugs.debian.org: > found 678026 1.91.90 Bug #678026 [libatk-adaptor] libatk-adaptor: insecure tempdir handling There is no source info for the package 'libatk-adaptor' at version '1.91.90' with architecture '' Unable to make a source version for version '1.91.90' Marked as found in versions 1.91.90. > thanks Stopping processing here. Please contact me if you need assistance. -- 678026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678026 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: found 678026 in 2.0.2-1
Processing commands for cont...@bugs.debian.org: > found 678026 2.0.2-1 Bug #678026 [libatk-adaptor] libatk-adaptor: insecure tempdir handling Marked as found in versions at-spi2-atk/2.0.2-1. > thanks Stopping processing here. Please contact me if you need assistance. -- 678026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678026 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#676984: gnome-keyring:: couldn't connect to: .../.cache/keyring-N8Zux6/pkcs11: Permission denied
Processing commands for cont...@bugs.debian.org: > severity 676984 serious Bug #676984 [gnome-keyring] gnome-keyring:: couldn't connect to: .../.cache/keyring-N8Zux6/pkcs11: Permission denied Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 676984: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676984 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#604579: marked as done (Preparations for the removal of the KDE3 and Qt3 libraries)
Your message dated Tue, 19 Jun 2012 12:03:45 + with message-id and subject line Bug#677901: Removed package(s) from unstable has caused the Debian Bug report #604579, regarding Preparations for the removal of the KDE3 and Qt3 libraries 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.) -- 604579: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=604579 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: k3dsurf Severity: wishlist User: debian-qt-...@lists.debian.org Usertags: qt3libs-removal Dear maintainer, The Debian Qt/KDE team is planning to remove the KDE3 and Qt3 libraries from Debian shortly after the Squeeze release. The transition phase to KDE4 and Qt4 will finish since both KDE and Nokia upstream don't maintain the old versions of those libraries anymore. In order to make this move, all packages directly or indirectly depending on the KDE3/Qt3 libraries have to either get ported to KDE4/Qt4 or eventually get removed from the Debian repositories. Therefore, please take the time and: - contact your upstream (if existing) and ask about the state of a KDE4/Qt4 port of your application - if there are no activities regarding porting, investigate whether there are suitable alternatives for your users - if there is a KDE4/Qt4 port that is not yet packaged, consider packaging it - if both the KDE3/Qt3 and the KDE4/Qt4 version already coexist in the Debian archives, consider removing the KDE3/Qt3 version Documentation on how to port to KDE4 can be found at: http://techbase.kde.org/index.php?title=Development/Tutorials/KDE4_Porting_Guide Documentation on how to port to Qt4 can be found at: http://doc.qt.nokia.com/4.7/porting4.html For any questions and issues, do not hesitate to contact the Debian Qt/KDE team at debian-qt-...@lists.debian.org Eckhart --- End Message --- --- Begin Message --- Version: 0.6.2.4-1+rm Dear submitter, as the package k3dsurf has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/677901 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Alexander Reichle-Schmehl (the ftpmaster behind the curtain) --- End Message ---
Bug#661991: marked as done (libtrash does nothing but causes segmentation fault)
Your message dated Tue, 19 Jun 2012 12:10:03 + with message-id and subject line Bug#678094: Removed package(s) from unstable has caused the Debian Bug report #661991, regarding libtrash does nothing but causes segmentation fault 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.) -- 661991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661991 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libtrash Version: 2.4-2 Severity: critical Justification: breaks unrelated software libtrash does not work here, it simply does nothing. Setting "DEBUG = YES" in /etc/libtrash.conf has no effect. But vim segfaults after setting LD_PRELOAD. Details: $ export LD_PRELOAD=/usr/lib/libtrash/libtrash.so.2.4 $ echo "foo" > foo $ ls -l foo -rw--- 1 user user 4 Mar 3 10:58 foo $ rm foo $ ls Trash ls: cannot access Trash: No such file or directory $ vim foo Vim: Caught deadly signal SEGV Segmentation fault $ export LD_PRELOAD= $ vim foo ## vim works again -- System Information: Debian Release: 6.0.4 APT prefers stable APT policy: (500, 'stable'), (160, 'testing'), (150, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core) 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 libtrash depends on: ii libc6 2.11.3-2 Embedded GNU C Library: Shared lib libtrash recommends no packages. libtrash suggests no packages. -- Configuration Files: /etc/libtrash.conf changed [not included] -- no debconf information --- End Message --- --- Begin Message --- Version: 2.4-2+rm Dear submitter, as the package libtrash has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/678094 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Alexander Reichle-Schmehl (the ftpmaster behind the curtain) --- End Message ---
Bug#676031: marked as done (alogg: FTBFS: ld: cannot find -lSM)
Your message dated Tue, 19 Jun 2012 12:11:32 + with message-id and subject line Bug#671378: Removed package(s) from unstable has caused the Debian Bug report #676031, regarding alogg: FTBFS: ld: cannot find -lSM 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.) -- 676031: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676031 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: alogg Version: 1.3.7-1.1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120604 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > gcc -L. -o _alst _alst.o -lvorbisfile -lvorbisenc -lvorbis -logg -lm > -lpthread `allegro-config --libs --static` > /usr/bin/ld: cannot find -lSM > /usr/bin/ld: cannot find -lICE > /usr/bin/ld: cannot find -lasound > /usr/bin/ld: cannot find -lXxf86dga > /usr/bin/ld: cannot find -lSM > /usr/bin/ld: cannot find -lICE > collect2: error: ld returned 1 exit status The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/04/alogg_1.3.7-1.1_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on about 50 AMD64 nodes of the Grid'5000 platform, using a clean chroot. Internet was not accessible from the build systems. --- End Message --- --- Begin Message --- Version: 1.3.7-1.1+rm Dear submitter, as the package alogg has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/671378 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@debian.org. Debian distribution maintenance software pp. Alexander Reichle-Schmehl (the ftpmaster behind the curtain) --- End Message ---
Bug#676800: [Pkg-octave-devel] Bug#676800: Bug#676800: octave-java: completely breaks octave
And setting -O0 (tested with both GCC 4.6 and 4.7) does not help either. -- Sébastien Villemot Researcher in Economics & Debian Maintainer http://www.dynare.org/sebastien Phone: +33-1-40-77-84-04 - GPG Key: 4096R/381A7594 pgpr6vKLWbxHv.pgp Description: PGP signature
Bug#673038: [Pkg-openldap-devel] Bug#673038: slapd: slapcat output truncated every now and then
Hi Steve, Steve Langasek wrote: > > According to the slapcat man page it should be "always safe to run > > slapcat with the slapd-bdb(5) ... backends" even if slapd runs. We do > > use a BDB backend. > > Note that the HDB backend is the one recommended upstream and the Debian > default. Well, yeah, that system has been dist-upgraded from at least Etch. IIRC it started at some time when BDB was still the default. I wrote that -- according to our backups -- this happened already with Lenny's slapd. But with Lenny it seemed to have happened less often (which is why we noticed it only recently). OTOH we have far more objects in the LDAP for a while now, so it's not clear if that increase was caused by the dist-upgrade or by going from approximately 5000 objects to approximately 1 objects. > Is this issue reproducible with HDB, or only with BDB? We will check that in a VM. > Can you reproduce this issue with the slapd 2.4.28 package in wheezy? We will check that, too. > Are there any noteworthy commonalities in the entries that are being > dropped? It looks as if always all entries created after some time are dropped, i.e. more recently created user were affected more often than old accounts. > Or perhaps commonalities in the last entries that are being > printed? We noticed no commonalities besides the fact that recently created users are affected more often (the slapcat output seems to be order by creation time). The place where it stops to output stuff seems to be random. > (Assumes that there is some consistent ordering to the output, > which of course may not be the case) >From what I have in my mind it looked quite consistently ordered. > Would you be able to provide a minimal test configuration (/etc/ldap/slapd.d > and LDIF of a directory, plus BDB DB_CONFIG file) that could be used to > reproduce this? Unfortunately not (yet) because so far the only place where we encountered this were our live user database. But we will try to generate some similar artifical data and check if we can reproduce this issue with that, too. Regards, Axel -- ,''`. | Axel Beckert , http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 -- 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#678072: puppet-lint: fails to run
Processing commands for cont...@bugs.debian.org: > severity 678072 serious Bug #678072 [puppet-lint] puppet-lint: fails to run Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 678072: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678072 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#678085: sorry
I'm sorry for extra commands, exim4 or gnome-keyring has a bug (#676984) that made me think that bts command failed -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: found 678026 in 1.91.90
Processing commands for cont...@bugs.debian.org: > found 678026 1.91.90 Bug #678026 [libatk-adaptor] libatk-adaptor: insecure tempdir handling There is no source info for the package 'libatk-adaptor' at version '1.91.90' with architecture '' Unable to make a source version for version '1.91.90' Ignoring request to alter found versions of bug #678026 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 678026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678026 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: found 678026 in 2.0.2-1
Processing commands for cont...@bugs.debian.org: > found 678026 2.0.2-1 Bug #678026 [libatk-adaptor] libatk-adaptor: insecure tempdir handling Ignoring request to alter found versions of bug #678026 to the same values previously set > thanks Stopping processing here. Please contact me if you need assistance. -- 678026: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678026 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: severity of 503861 is serious
Processing commands for cont...@bugs.debian.org: > #apertium is unusable without a fix for this > severity 503861 serious Bug #503861 [apertium] echo apple|apertium en-es: Error: Unknown error matching regexp (code -16) Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 503861: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503861 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 (with 1 errors): your mail
Processing commands for cont...@bugs.debian.org:
> merge 633088 678132
Bug #633088 {Done: Stefan Völkel } [revelation] revelation:
silently truncates passphrase
Unable to merge bugs because:
severity of #678132 is 'important' not 'grave'
done of #678132 is '' not 'Stefan Völkel '
Failed to merge 633088: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x3429a00)',
'requester', 'Luciano Bello ', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid',
'<201206191501.36576.luci...@debian.org>', 'request_subject', ...) called at
/usr/lib/debbugs/service line 872
eval {...} called at /usr/lib/debbugs/service line 871
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
633088: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633088
678132: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678132
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#678136: zfsutils: FTBFS with libbsd-dev >= 0.4.0
Package: zfsutils Version: 9.0-2 Severity: serious Tags: wheezy sid 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, Due to libbsd-dev 0.4.0 moving libutil.h into /bsd/, zfsutils can no longer build. Attached patch would be a way to fix that but I wasn't sure if there could be a better way. Then there are other issues during build which I don't have time to look into just yet: > cc -Wall -Wno-unknown-pragmas -g -pipe -fPIC -I. -D_GNU_SOURCE > -DNEED_SOLARIS_BOOLEAN -isystem /usr/include/freebsd > -D__va_list=__builtin_va_list -O2 -DZFS_NO_ACL -I/h[10/1964] > n/zfsutils-9.0/cddl/lib/libzfs/../../../sbin/mount > -I/home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../cddl/lib/libumem > -I/home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../sys > /cddl/compat/opensolaris > -I/home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../cddl/compat/opensolaris/include > -I/home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../cddl/compat/op > ensolaris/lib/libumem > -I/home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzpool/common > -I/home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../sys/ > cddl/contrib/opensolaris/common/zfs > -I/home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../sys/cddl/contrib/opensolaris/uts/common/fs/zfs > -I/home/steven/zfsutils-9.0/cddl/lib/libz > fs/../../../sys/cddl/contrib/opensolaris/uts/common/sys > -I/home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/head > -I/home/steven/zfsutils-9.0/cddl/lib/l > ibzfs/../../../sys/cddl/contrib/opensolaris/uts/common > -I/home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libnvpair > -I/home/steven/zfsutils-9.0/cd > dl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libuutil/common > -I/home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../cddl/contrib/opensolaris/lib/libzfs/common > -I/home/steve > n/zfsutils-9.0/cddl/lib/libzfs/../../../lib/libmd -std=iso9899:1999 > -fstack-protector -Wno-pointer-sign -c > /home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../cddl/compat/opensol > aris/misc/deviceid.c > In file included from /usr/include/sys/kern/types.h:48:0, > from /usr/include/sys/kern/param.h:67, > from /usr/include/osreldate.h:1, > from /usr/include/i386-kfreebsd-gnu/sys/param.h:39, > from /usr/include/freebsd/sys/param.h:1, > from > /home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../sys/cddl/compat/opensolaris/sys/param.h:33, > from > /home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../cddl/compat/opensolaris/misc/deviceid.c:30: > /home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../sys/cddl/compat/opensolaris/sys/types.h:49:1: > error: unknown type name ‘u_int’ > /home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../sys/cddl/compat/opensolaris/sys/types.h:50:1: > error: unknown type name ‘u_char’ > /home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../sys/cddl/compat/opensolaris/sys/types.h:51:1: > error: unknown type name ‘u_short’ > /home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../sys/cddl/compat/opensolaris/sys/types.h:52:1: > error: unknown type name ‘u_long’ > /home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../sys/cddl/compat/opensolaris/sys/types.h:55:1: > error: unknown type name ‘off_t’ > /home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../sys/cddl/compat/opensolaris/sys/types.h:56:1: > error: unknown type name ‘id_t’ > /home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../sys/cddl/compat/opensolaris/sys/types.h:57:1: > error: unknown type name ‘id_t’ > /home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../sys/cddl/compat/opensolaris/sys/types.h:58:1: > error: unknown type name ‘id_t’ > /home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../sys/cddl/compat/opensolaris/sys/types.h:59:1: > error: unknown type name ‘id_t’ > /home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../sys/cddl/compat/opensolaris/sys/types.h:60:1: > error: unknown type name ‘id_t’ > /home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../sys/cddl/compat/opensolaris/sys/types.h:61:1: > error: unknown type name ‘mode_t’ > /home/steven/zfsutils-9.0/cddl/lib/libzfs/../../../sys/cddl/compat/opensolaris/sys/types.h:63:1: > error: unknown type name ‘u_int’ Regards, -- Steven Chamberlain ste...@pyro.eu.org Index: debian/control === --- debian/control (revision 4319) +++ debian/control (working copy) @@ -6,7 +6,7 @@ Dm-Upload-Allowed: yes Build-Depends: debhelper (>= 7.0.50~), freebsd-buildutils (>= 9.0-5~), - libbsd-dev (>= 0.1.4), + libbsd-dev (>= 0.3.0), libc0.1-dev (>= 2.10), kfreebsd-kernel-headers (>= 0.51), libgeom-dev, zlib1g-dev Index: debian/patches/08_libbsd.diff === --- debian/patches/08_libbsd.diff (revision 4319) +++ d
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 676423 confirmed Bug #676423 [doxygen] doxygen: new segmentation faults in version 1.8.1-1 Added tag(s) confirmed. > found 676423 doxygen/1.8.1.1-1 Bug #676423 [doxygen] doxygen: new segmentation faults in version 1.8.1-1 Marked as found in versions doxygen/1.8.1.1-1. > severity 676423 grave Bug #676423 [doxygen] doxygen: new segmentation faults in version 1.8.1-1 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 676423: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676423 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#678137: git-svn: filenames with spaces trip svn 1.7 assertion (svn_uri_is_canonical)
Package: git-svn Version: 1:1.7.2.5-3 Severity: serious Tags: wheezy sid experimental upstream Justification: ftbfs with Subversion >= 1.7 Forwarded: http://thread.gmane.org/gmane.comp.version-control.git/184644 Hi Gerrit, Gerrit Pape wrote[1]: > ok 1 - initialize git svn > > expecting success: git svn fetch > svn: E235000: In file > '/tmp/buildd/subversion-1.7.5/subversion/libsvn_subr/dirent_uri.c' line 2291: > assertion failed (svn_uri_is_canonical(url, pool)) Good catch. Subversion 1.7.5 was just uploaded to the archive, and it is stricter than 1.6.y about pathnames containing spaces. Regards, Jonathan [1] http://thread.gmane.org/gmane.comp.version-control.git.debian/164/focus=165 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678139: CVE-2012-2762
Package: serendipity Severity: grave Tags: security Please see http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2012-2762 for details and a patch. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674746: Additional info
On Mon, Jun 18, 2012 at 05:17:50PM +0200, Arno Wagner wrote: > libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0xb7408000) Just as expected. You should investigate where this file comes from and why /usr/X11R6/lib/ is enabled in /etc/ld.so.conf* As this is clearly a local misconfiguration, I'm closing the bug. -- WBR, wRAR signature.asc Description: Digital signature
Bug#674746: marked as done (libcairo2: undefined symbol: XRenderCreateSolidFill)
Your message dated Tue, 19 Jun 2012 19:53:03 +0600 with message-id <20120619135303.ga17...@belkar.wrar.name> and subject line Re: Bug#674746: Additional info has caused the Debian Bug report #674746, regarding libcairo2: undefined symbol: XRenderCreateSolidFill 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.) -- 674746: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674746 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: libcairo2 Version: 1.12.2-1 Severity: grave Justification: renders package unusable Dear Maintainer, I am running wheezy and yesterday upgraded packages, only to find that a number of x-applications does not start anymore. The errors are all of the following form: wagner ~>iceweasel /usr/lib/iceweasel/firefox-bin: symbol lookup error: \ /usr/lib/i386-linux-gnu/libcairo.so.2: undefined symbol: \ XRenderCreateSolidFill I tried reinstalling all dependencies of libcairo2 without effect. The only thing that finally helped was a downgrade to libcairo2 1.8.10-6 from stable. Goolegling for the problem did not turn up anything useful. I did note however that from stable to testing the number of available architectures changed dramatically, and that the package is not available at all in unstable or experimental. This seems to indicate that there are changes in progress. The versio info below ios after the downgrade to libcairo2 (1.8.10-6). I did not downgrade any other package. Regards, Arno Wagner a...@wagner.name -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 3.3.6-990fxa-ud3 (SMP w/4 CPU cores; PREEMPT) Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) Shell: /bin/sh linked to /bin/bash Versions of packages libcairo2 depends on: ii libc62.13-32 ii libfontconfig1 2.9.0-5 ii libfreetype6 2.4.9-1 ii libpixman-1-00.24.4-1 ii libpng12-0 1.2.49-1 ii libx11-6 2:1.4.99.901-2 ii libxcb-render-util0 0.3.8-1 ii libxcb-render0 1.8.1-1 ii libxcb1 1.8.1-1 ii libxrender1 1:0.9.7-1 ii zlib1g 1:1.2.7.dfsg-1 libcairo2 recommends no packages. libcairo2 suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- On Mon, Jun 18, 2012 at 05:17:50PM +0200, Arno Wagner wrote: > libXrender.so.1 => /usr/X11R6/lib/libXrender.so.1 (0xb7408000) Just as expected. You should investigate where this file comes from and why /usr/X11R6/lib/ is enabled in /etc/ld.so.conf* As this is clearly a local misconfiguration, I'm closing the bug. -- WBR, wRAR signature.asc Description: Digital signature --- End Message ---
Bug#678140: Two tiff issues: CVE-2012-2113 / CVE-2012-2088
Package: tiff Severity: grave Tags: security Two new tiff issues have been repored to Red Hat bugzilla, please see these bugs for details: https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2012-2088 https://bugzilla.redhat.com/show_bug.cgi?id=810551 (CVE-2012-2113) Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#676717: dh_installcatalogs transition and w3c-dtd-xhtml removal bugs
clone 676717 -1
severity -1 important
title -1 Broken {post|pre}rm script of w3c-dtd-xhtml
severity 676717 normal
title 676717 dh_installcatalogs transition with removed package
thanks
Hi,
Nobert, I thought I explained background info enough and I thought those
pointer info made your situation settled. For remaining issues, I was
expecting you to submit new cleaner bug report to appropriate places.
(Clearly this is not a bug of my package.) Since you insist, I will go
out of my way to help you solve your problem and make reassignment of
bug report. But quite frankly, second guessing where are the breakages
in your system is a quite difficult task for me. It is very confusing.
The bug report by Nobert http://bugs.debian.org/477751 raised several
issues. I summarize remaining bugs as:
* dh_installcatalogs transition with removed package
* Broken {post|pre}rm script of w3c-dtd-xhtml
These bugs cause his system to break even now. He still have problem
using debiandoc-sgml package even after bug #675474 ("debiandoc-sgml:
please rebuild to fix your copy of #477751", fixed in 1.2.27.)
I cloned this bug as -1 to address w3c-dtd-xhtml issue (For this bug -1
on w3c-dtd-xhtml, please skip to the half way in this long bug report by
searching "bug -1". Excuse us for this complication.)
=== bug 477751 : dh_installcatalogs transition with removed package ==
Helmut, The closure of dh_installcatalogs bug initiated by the
http://bugs.debian.org/477751 needed a bit more coordination than what
has been done so far. I think what Helmut did was great job but
sometimes we need a final touch. What needs attention is packages which
are removed between squeeze/wheezy.
I see Nobert having multiple issues. Some are because of broken other
packages. But as I see his traumatic experience, I am wondering if there
are some fundamental issues associated with Helmut's dh_installcatalogs
transition plan with removed package. Helmut suggested us to make
re-upload using new dh_installcatalogs. What does Helmut anticipated for
packages such as xml-resume-library which is removed. Their postinst
script is old. So I assume package removal may not function as expected
and may create broken catalog. See http://bugs.debian.org/676717 for
the entire story.
It seems removed xml-resume-library package is one of the cause of
broken SGML catalog. Since it is not uploaded, I assume it is expected
to have problem for wheezy if someone upgrade system with such package
installed.
Reassigning this 676717 bug to debhelper or dpkg is wrong since their
bugs have been fixed (I understand it was a good ones). I did not assign
to xml-resume-library since all bugs for removed package are
automatically closed (or by now, it may not be accepted).
Unless you propose simple technical solution, this is something we
mention in release note. I initially thought this was unfortunate
transitional problem in sid only and closed bug but this may affect next
release. Helmut, please tell me what is the way to handle this bug.
=== Some analysis on Nobert's system ==
I will comment on the last report by Nobert as below.
(Please bare with me.)
On Tue, Jun 19, 2012 at 07:55:02AM +0900, Norbert Preining wrote:
> reopen 676717
> thanks
>
> Hi Osamu,
>
> Funny game, but please stay with me ... if you want to make it short,
> just read the cowbuilder run down there ...
>
> On Mo, 18 Jun 2012, Osamu Aoki wrote:
> > Please remove or update such broken packages. I guess those may be
>
> These packages are removed.
>
> > * xml-resume-library (package removed)
>
> seems to be a bug in xml-resume-library package or dpkg or whatever,
> that this package wasn't removed. Furthermore, I checked all my
> aptitude log files and there is no mentioning of this file, so
> I am a bit surprised that this file is still here.
>
> Anyway, I removed /etc/sgml/xml-resume-library.cat.
Just removing file may not be sufficient. Considering this package
still using old {post/pre}{inst/rm} scripts, purging may not have been
done properly considering transition.
> Still no success ... we are left with w3c-dtd-xhtml.cat:
>
> > * w3c-dtd-xhtml (package RC bug fixed Date: Thu, 14 Jun 2012)
>
> Ok:
> rc w3c-dtd-xhtml 1.1-5
1.1-5??? That is from the stable release. I thought you were running
sid.
oldstable 1.1-5
stable 1.1-5
testing 1.2-3 (uploaded 2012-05-08)
unstable 1.2-4 (uploaded 2012-06-14)
> Well, then
> $ aptitude purge w3c-dtd-xhtml
> ...
>
> THat makes it already a bit better, now I get only one error:
> $ debiandoc2text test.sgml
> nsgmls:/etc/sgml/catalog:12:8:E: cannot open "/etc/sgml/w3c-dtd-xhtml.cat"
> (No such file or directory)
> $
>
> Could it be that there is no update running...
> $ update-catalog --update-super
> Updating the super catalog...
> Ahhh and now it is good.
This is something release note needs to mention for upgrading from
squeeze to wheezy.
> Ok, let us consider this bug closed, but allow me som
Processed (with 2 errors): dh_installcatalogs transition and w3c-dtd-xhtml removal bugs
Processing commands for cont...@bugs.debian.org:
> clone 676717 -1
Bug #676717 [debiandoc-sgml] debiandoc-sgml: does not work at all with minimal
document
Bug 676717 cloned as bug 678143
> severity -1 important
Bug #678143 [debiandoc-sgml] debiandoc-sgml: does not work at all with minimal
document
Severity set to 'important' from 'grave'
> title -1 Broken {post|pre}rm script of w3c-dtd-xhtml
Unknown command or malformed arguments to command.
> severity 676717 normal
Bug #676717 [debiandoc-sgml] debiandoc-sgml: does not work at all with minimal
document
Severity set to 'normal' from 'grave'
> title 676717 dh_installcatalogs transition with removed package
Unknown command or malformed arguments to command.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
676717: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676717
678143: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678143
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: git-svn: filenames with spaces trip svn 1.7 assertion (svn_uri_is_canonical)
Processing commands for cont...@bugs.debian.org: > found 678137 git/1:1.7.10.4-1 Bug #678137 [git-svn] git-svn: filenames with spaces trip svn 1.7 assertion (svn_uri_is_canonical) Marked as found in versions git/1:1.7.10.4-1. > End of message, stopping processing here. Please contact me if you need assistance. -- 678137: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678137 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#666351: marked as done (openr2: FTBFS: dh_install: libopenr2-bin missing files (etc/openr2/*.conf), aborting)
Your message dated Tue, 19 Jun 2012 14:50:42 +
with message-id
and subject line Bug#666351: fixed in openr2 1.3.2-1.1
has caused the Debian Bug report #666351,
regarding openr2: FTBFS: dh_install: libopenr2-bin missing files
(etc/openr2/*.conf), aborting
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.)
--
666351: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: openr2
Version: 1.3.2-1
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
This rebuild was done by building only architecture:any binary packages
(binary-arch target of debian/rules), and using a recent dpkg that uses the
build-arch target if available.
Also, only the Build-Depends were installed, not the Build-Depends-Indep.
Relevant part:
> make[3]: Entering directory `/«PKGBUILDDIR»'
> test -z "/etc" || mkdir -p -- "/«PKGBUILDDIR»/debian/tmp/etc"
> /usr/bin/install -c -m 644 'doc/r2proto.conf'
> '/«PKGBUILDDIR»/debian/tmp/etc/r2proto.conf'
> /usr/bin/install -c -m 644 'doc/r2test.conf'
> '/«PKGBUILDDIR»/debian/tmp/etc/r2test.conf'
> test -z "/usr/share/man/man5" || mkdir -p --
> "/«PKGBUILDDIR»/debian/tmp/usr/share/man/man5"
> /usr/bin/install -c -m 644 './r2test.conf.5'
> '/«PKGBUILDDIR»/debian/tmp/usr/share/man/man5/r2test.conf.5'
> test -z "/usr/share/man/man8" || mkdir -p --
> "/«PKGBUILDDIR»/debian/tmp/usr/share/man/man8"
> /usr/bin/install -c -m 644 './r2test.8'
> '/«PKGBUILDDIR»/debian/tmp/usr/share/man/man8/r2test.8'
> make[3]: Leaving directory `/«PKGBUILDDIR»'
> make[2]: Leaving directory `/«PKGBUILDDIR»'
> make[1]: Leaving directory `/«PKGBUILDDIR»'
>dh_install -a
> dh_install: libopenr2-bin missing files (etc/openr2/*.conf), aborting
> make: *** [binary-arch] Error 2
The full build log is available from:
http://people.debian.org/~lucas/logs/2012/03/30/openr2_1.3.2-1_unstable.log
A list of current common problems and possible solutions is available at
http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
of the Grid'5000 platform, using a clean chroot. Internet was not
accessible from the build systems.
--- End Message ---
--- Begin Message ---
Source: openr2
Source-Version: 1.3.2-1.1
We believe that the bug you reported is fixed in the latest version of
openr2, which is due to be installed in the Debian FTP archive:
libopenr2-3_1.3.2-1.1_amd64.deb
to main/o/openr2/libopenr2-3_1.3.2-1.1_amd64.deb
libopenr2-bin_1.3.2-1.1_amd64.deb
to main/o/openr2/libopenr2-bin_1.3.2-1.1_amd64.deb
libopenr2-dev_1.3.2-1.1_amd64.deb
to main/o/openr2/libopenr2-dev_1.3.2-1.1_amd64.deb
openr2_1.3.2-1.1.debian.tar.gz
to main/o/openr2/openr2_1.3.2-1.1.debian.tar.gz
openr2_1.3.2-1.1.dsc
to main/o/openr2/openr2_1.3.2-1.1.dsc
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 666...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
gregor herrmann (supplier of updated openr2 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: Sat, 16 Jun 2012 15:40:43 +0200
Source: openr2
Binary: libopenr2-dev libopenr2-bin libopenr2-3
Architecture: source amd64
Version: 1.3.2-1.1
Distribution: unstable
Urgency: low
Maintainer: Debian VoIP Team
Changed-By: gregor herrmann
Description:
libopenr2-3 - MFC/R2 (telephony) call setup library
libopenr2-bin - MFC/R2 (telephony) call setup library - test programs
libopenr2-dev - MFC/R2 (telephony) call setup library - development headers
Closes: 666351
Changes:
openr2 (1.3.2-1.1) unstable; urgency=low
.
* Non-maintainer upload.
* Fix "FTBFS: dh_install: libopenr2-bin missing files
(etc/openr2/*.conf), aborting":
update build{,-arch,-indep} target in debian/rules.
(Closes: #666351)
Checksums-Sha1:
f05ca17aa5efda6bc2ec7bf4d2f5062d318c762d 2020 openr2_1.3.2-1.1.dsc
c96722f6e950fed4d71e3e0eca56791ea0e30539 3695 openr2_1.3.2-1.1.debian.tar.gz
8bb298dfd9fbdecf8e5b7ec0a679d715faa8848a 64436
Bug#677974: eclipse-egit: FTBFS with eclipse 3.8.0 (git version)
Hi Niels, in your build log I see: dpkg-buildpackage: source package eclipse-egit dpkg-buildpackage: source version 1.1.0-1 dpkg-buildpackage: source changed by Jakub Adam Why are you using such an old version? Current eclipse-egit in sid is 1.3.0-1, I tried to compile it with eclipse 3.8.0 and it builds without problems. Obviously your build failure is because in sid there is libjgit-java 1.3.0-2, but eclipse-egit 1.1.0-1 requires also 1.1.0 jgit. Regards, Jakub -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: notfound 678075 in 1.7.5-1
Processing commands for cont...@bugs.debian.org:
> notfound 678075 1.7.5-1
Bug #678075 {Done: Peter Samuelson } [subversion] subversion:
incorrect Last Changed Rev after upgrade from 1.6.17 to 1.7.5
No longer marked as found in versions subversion/1.7.5-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
678075: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678075
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#676984: same probleme, important problem
Pierre Crescenzo writes: > Hello, > > I have the same bug with version 4.80-3 of exim4 since my update this > morning. This is now impossible to send mails with GNUS on Emacs nor with > "mail" command line. :-( Only local mails works. using gnus, too at the moment i use a small wrapper script as workaround: ~/develop/scripts/my-sendmail: #!/bin/bash unset GNOME_KEYRING_CONTROL unset GNOME_KEYRING_PID exec /usr/sbin/sendmail "$@" in emacs: M-x customize-variable sendmail-program and set it to the script greetings -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#674515: marked as done (/bin/htpasswd exists in apache2-utils and mini-httpd)
Your message dated Tue, 19 Jun 2012 15:33:37 + with message-id and subject line Bug#674515: fixed in mini-httpd 1.19-9.3 has caused the Debian Bug report #674515, regarding /bin/htpasswd exists in apache2-utils and mini-httpd 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.) -- 674515: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=674515 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: mini-httpd,apache2-utils Severity: normal Dear Maintainers, two different binaries with the same name /bin/htpasswd are provided by apache2 and mini-httpd. If you install mini-httpd after apache2 the htpasswd from mini-httpd will override the file from apache2. The file from apache2 is downward-compatible to the from mini-httpd. This means it provides all the options like mini-httpd, but mini-httpd does not provide all options from apache2. So it doesn't make any sense the the htpasswd from mini-httpd overrides that from apache2. I think thats a bug. It could be resolved by let the packages conflict or let mini-httpd provide something like mini-htpasswd (which could get linked to htpasswd as long as apache2 does not exists) kind regards, Michael Stummvoll --- End Message --- --- Begin Message --- Source: mini-httpd Source-Version: 1.19-9.3 We believe that the bug you reported is fixed in the latest version of mini-httpd, which is due to be installed in the Debian FTP archive: mini-httpd_1.19-9.3.diff.gz to main/m/mini-httpd/mini-httpd_1.19-9.3.diff.gz mini-httpd_1.19-9.3.dsc to main/m/mini-httpd/mini-httpd_1.19-9.3.dsc mini-httpd_1.19-9.3_amd64.deb to main/m/mini-httpd/mini-httpd_1.19-9.3_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 674...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Bernd Zeimetz (supplier of updated mini-httpd 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: Sat, 16 Jun 2012 01:31:28 +0200 Source: mini-httpd Binary: mini-httpd Architecture: source amd64 Version: 1.19-9.3 Distribution: unstable Urgency: low Maintainer: Marvin Stark Changed-By: Bernd Zeimetz Description: mini-httpd - a small HTTP server Closes: 674515 Changes: mini-httpd (1.19-9.3) unstable; urgency=low . * Non-maintainer upload. * Do not install htpasswd, recommend apache2-utils instead. (Closes: #674515). * Add missing dependencies on $remote_fs to fix a lintian error. Checksums-Sha1: a113fc8beb4a39f1edfa906d76852d6011d00430 1716 mini-httpd_1.19-9.3.dsc 501001d24c5f3183feab0b54794084c5d61dd66c 7993 mini-httpd_1.19-9.3.diff.gz 523a720a36e366b6b36fd710fcd212920af991e5 38018 mini-httpd_1.19-9.3_amd64.deb Checksums-Sha256: 6d8bed834a6e46ef80677f5e094175fd55565e261421599884b04235e5472bc8 1716 mini-httpd_1.19-9.3.dsc 5e6e7f98e1d15ea513aad01d5324d97bf4a298cd164f1b6939b18781f43d7eb0 7993 mini-httpd_1.19-9.3.diff.gz d5834f7cca0f00ff2703a2f57fe3414f643a4c22bcd393a7507d03d65e32f6d3 38018 mini-httpd_1.19-9.3_amd64.deb Files: c6280181240457b3738ba7a6d893fbc9 1716 web optional mini-httpd_1.19-9.3.dsc 36afdcd7edfab68b919c06a4b351479c 7993 web optional mini-httpd_1.19-9.3.diff.gz 246e955912fe92f116336709f8d5c4b2 38018 web optional mini-httpd_1.19-9.3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCAAGBQJP3fKjAAoJEOs2Fxpv+UNfuJAP/R7sPqE/F6Eq+ffT3ucr5HFB FLkkcJgiudgzmz2Sx34hM3kD0FwIePzpIe+EV5ollBqPIXOmKlcizAbs7XWs+dzp MRDG6vFOsZNvmHE+il/k1He9dAa466h2gl2/fcP1dlkhrI+PFQIAJScuQBRJy29V eQ2XlJWYdDBOcJ/4jWhbnFPY5snmP2oN0vZtFik8yJUjur/emyjzv8yajUVqrbFa OKvWBD0JohcCVHLrOq8tuMhrK9eeQnT/2v5rAVbX6jatRIn7M2KmuKFvtam7ebgj nTgWoJ4FvH6pZsBX0hNM6wFhD4IlnKkM4/VeKISq8zxQO3lmsPY8+raAS0TDzGzM P7soB5cbITY8qSgA6C+r5zbOmvk3Mg4vs6P7ov7z5mmu4VKqbU7//VFgAciHD+EU TeFDwauhu/ETTEcL6EqY22el1J7sayIOm5xr7dtVxMPwU3Ub8m29h4gKoAZQdUpm VcM4VKHnIkx8/YG2AR14azpmRuNvQ/VKUeYNHkXDP8hj3FvPwXVe0v2alXBZ1Wy4 tnjQe1fnXFAeX7vWe4nqrcCSjPAz/Lbhy0CsuILuUOoN0AbJ6zgJZZjbzvoTBKG6 ipOVyUyCmgwUx+qMLdMZyw6LG7/PL/M5ccNUcAbekNL3uMYg5SyfDgjjKnmQWyhL edXE2cDezeCFKoYreQ3C =4TCL -END PGP SIGNATURE- --- End Message ---
Bug#678072: [Pkg-puppet-devel] Bug#678072: puppet-lint: fails to run
Holger Levsen writes: > severity 678072 serious > thanks > > On Dienstag, 19. Juni 2012, John Eikenberry wrote: >> Running puppet-lint fails every time, with or without any arguments. This >> coincided with a recent change of ruby to default to 1.9.1 instead of 1.8. >> The puppet-common package, which puppet-lint depends on, doesn't include >> support for 1.9.1. > > as ruby will default to 1.9 in wheezy this will make the package completly > unusable, thus raising the severity. > According to: https://github.com/rodjek/puppet-lint/issues/103 - this should work with 1.9.2, this patch doesn't appear in the debian package, and looks pretty trivial. The reported issue seems to be pretty different from what was reported in the upstream github though. micah -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#678152: crashes at start
Package: freediams Version: 0.7.4-2 Severity: grave Hello people, today I started experimenting with the FreeMedForms suite. FreeMedForms starts ok, but FreeDiams and FreeAccount do not (I won't file/clone the bug to FreeAccount, since it seems to be the same exact issue). Both, in fact, crash at start, with similar backtraces. I'm attaching them, hoping that someone is able to fix them :) Kindly, David -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 3.2.0-2-686-pae (SMP w/1 CPU core) Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages freediams depends on: ii freemedforms-common-resources 0.7.4-2 ii freemedforms-freedata 0.7.4-2 ii freemedforms-libs 0.7.4-2 ii libc6 2.13-33 ii libgcc11:4.7.0-13 ii libqt4-network 4:4.8.2-1 ii libqt4-script 4:4.8.2-1 ii libqt4-sql 4:4.8.2-1 ii libqt4-svg 4:4.8.2-1 ii libqt4-xml 4:4.8.2-1 ii libqtcore4 4:4.8.2-1 ii libqtgui4 4:4.8.2-1 ii libstdc++6 4.7.0-13 ii libx11-6 2:1.4.99.901-2 ii libxext6 2:1.3.1-2 freediams recommends no packages. Versions of packages freediams suggests: pn freediams-doc ii ttf-mscorefonts-installer 3.4+nmu1 -- no debconf information -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 | http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 freeaccount.log.bz2 Description: application/bzip freediams.log.bz2 Description: application/bzip signature.asc Description: PGP signature
Bug#673038: [Pkg-openldap-devel] Bug#673038: Bug#673038: slapd: slapcat output truncated every now and then
--On Tuesday, June 19, 2012 2:25 PM +0200 Axel Beckert wrote: Hi Steve, Steve Langasek wrote: > According to the slapcat man page it should be "always safe to run > slapcat with the slapd-bdb(5) ... backends" even if slapd runs. We do > use a BDB backend. Note that the HDB backend is the one recommended upstream and the Debian default. Well, yeah, that system has been dist-upgraded from at least Etch. IIRC it started at some time when BDB was still the default. I wrote that -- according to our backups -- this happened already with Lenny's slapd. But with Lenny it seemed to have happened less often (which is why we noticed it only recently). Personally, I would advise you to ask a question about this on openldap-techni...@openldap.org. I asked Howard about it, and he had a ready answer as to why you were seeing this, but I forget what it is. In any case, this is not a debian specific openldap bug. --Quanah -- Quanah Gibson-Mount Sr. Member of Technical Staff Zimbra, Inc A Division of VMware, Inc. Zimbra :: the leader in open source messaging and collaboration -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#677801: AttributeError: 'module' object has no attribute 'uses_fragment'
Package: python-pip Version: 1.1-2 Followup-For: Bug #677801 Here is a patch with the proposed fixes found in the upstream bug report. It tests if urlparse has the now gone attribute (with latest python 2 & 3 versions) uses_fragment before using it. -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-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 python-pip depends on: ii python2.7.3~rc2-1 ii python-pkg-resources 0.6.24-1 ii python-setuptools 0.6.24-1 ii python2.6 2.6.7-4 Versions of packages python-pip recommends: ii build-essential 11.5 pn python-dev-all python-pip suggests no packages. -- no debconf information Description: fix the improper use of urllib.parse.uses_fragment Since Python >= 2.7.3, 3.2.3 the module urlparse/urllib.parse (python3) do not have a uses_fragment attribute. This patch tests if it exists before using it. Origin: upstream Bug: https://github.com/pypa/pip/issues/552 Bug-Debian: http://bugs.debian.org/677801 Last-Update: 2012-06-19 --- python-pip-1.1.orig/pip/vcs/__init__.py +++ python-pip-1.1/pip/vcs/__init__.py @@ -19,7 +19,9 @@ class VcsSupport(object): def __init__(self): # Register more schemes with urlparse for various version control systems urlparse.uses_netloc.extend(self.schemes) -urlparse.uses_fragment.extend(self.schemes) +# Python >= 2.7.4, 3.3 doesn't have uses_fragment +if getattr(urlparse, 'uses_fragment', None): +urlparse.uses_fragment.extend(self.schemes) super(VcsSupport, self).__init__() def __iter__(self): --- python-pip-1.1.orig/pip/vcs/bazaar.py +++ python-pip-1.1/pip/vcs/bazaar.py @@ -20,8 +20,10 @@ class Bazaar(VersionControl): def __init__(self, url=None, *args, **kwargs): super(Bazaar, self).__init__(url, *args, **kwargs) -urlparse.non_hierarchical.extend(['lp']) -urlparse.uses_fragment.extend(['lp']) +# Python >= 2.7.4, 3.3 doesn't have uses_fragment or non_hierarchical +if getattr(urlparse, 'uses_fragment', None): +urlparse.uses_fragment.extend(self.schemes) +urlparse.non_hierarchical.extend(['lp']) def parse_vcs_bundle_file(self, content): url = rev = None
Bug#673773: Working on it
Hi, I am working on it. So far I have not found out what went wrong in the post-installation script. I need more time to play with piuparts. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#669434: gzip: FTBFS: ../../lib/fchdir.c:149:15: error: storage size of 'statbuf' isn't known
On Thu, Apr 19, 2012 at 09:13:14PM +0200, Lucas Nussbaum wrote: > > CC fchdir.o > > In file included from ./sys/stat.h:48:0, > > from ./fcntl.h:41, > > from ./unistd.h:50, > > from ../../lib/fchdir.c:20: > > /usr/lib/gcc/i686-w64-mingw32/4.6/../../../../i686-w64-mingw32/include/sys/stat.h: > > In function '_gl_register_fd': > > ../../lib/fchdir.c:149:15: error: storage size of 'statbuf' isn't known > > ../../lib/fchdir.c: At top level: > > ../../lib/fchdir.c:222:1: error: conflicting types for 'rpl_fstat' > > ./sys/stat.h:355:12: note: previous declaration of 'rpl_fstat' was here > > ../../lib/fchdir.c: In function 'rpl_fstat': > > ../../lib/fchdir.c:225:5: warning: passing argument 2 of 'rpl_stat' from > > incompatible pointer type [enabled by default] > > ./sys/stat.h:571:12: note: expected 'struct _stat32i64 *' but argument is > > of type 'struct _stat32i64 *' > > ../../lib/fchdir.c:226:3: warning: passing argument 2 of 'fstat' from > > incompatible pointer type [enabled by default] > > /usr/lib/gcc/i686-w64-mingw32/4.6/../../../../i686-w64-mingw32/include/sys/stat.h:171:2: > > note: expected 'struct stat *' but argument is of type 'struct _stat32i64 > > *' > > make[4]: *** [fchdir.o] Error 1 This too (as #653960) preferably should be fixed by upgrading gnulib, but the fix itself is apparently in the gnulib commit 3f3d9b41 (it can't be easily backported to the gzip 1.4 package gnulib though). Also note that 1.5 was released two days ago which contains the updated gnulib. -- WBR, wRAR signature.asc Description: Digital signature
Processed: tagging 665476
Processing commands for cont...@bugs.debian.org: > tags 665476 + upstream fixed-upstream Bug #665476 [libsasl2-2] libsasl2-2 - ABI change without changing ABI name Added tag(s) upstream and fixed-upstream. > thanks Stopping processing here. Please contact me if you need assistance. -- 665476: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=665476 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#676007: marked as done (dovecot-antispam: FTBFS: antispam-storage.c:3:26: fatal error: antispam-storage-2.1.c: No such file or directory)
Your message dated Tue, 19 Jun 2012 17:32:42 + with message-id and subject line Bug#676007: fixed in dovecot-antispam 2.0+20120225-3 has caused the Debian Bug report #676007, regarding dovecot-antispam: FTBFS: antispam-storage.c:3:26: fatal error: antispam-storage-2.1.c: No such file or 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.) -- 676007: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676007 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: dovecot-antispam Version: 2.0+20120225-2 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120604 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: > cc -DHAVE_CONFIG_H -I/usr/include/dovecot/ -I/usr/include/dovecot/src/ > -I/usr/include/dovecot/src/lib/ -I/usr/include/dovecot/src/lib-storage/ > -I/usr/include/dovecot/src/lib-mail/ -I/usr/include/dovecot/src/lib-imap/ > -I/usr/include/dovecot/src/lib-dict/ -I/usr/include/dovecot/src/lib-index/ > -I/usr/include/dovecot/src/imap/ -o dovecot-version dovecot-version.c > ./dovecot-version > dovecot-version.h > CC antispam-storage.o > antispam-storage.c:3:26: fatal error: antispam-storage-2.1.c: No such file or > directory > compilation terminated. > make[1]: *** [antispam-storage.o] Error 1 The full build log is available from: http://people.debian.org/~lucas/logs/2012/06/04/dovecot-antispam_2.0+20120225-2_unstable.log A list of current common problems and possible solutions is available at http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute! About the archive rebuild: The rebuild was done on EC2 VM instances from Amazon Web Services, using a clean, minimal and up-to-date chroot. Every failed build was retried once to eliminate random failures. --- End Message --- --- Begin Message --- Source: dovecot-antispam Source-Version: 2.0+20120225-3 We believe that the bug you reported is fixed in the latest version of dovecot-antispam, which is due to be installed in the Debian FTP archive: dovecot-antispam_2.0+20120225-3.diff.gz to main/d/dovecot-antispam/dovecot-antispam_2.0+20120225-3.diff.gz dovecot-antispam_2.0+20120225-3.dsc to main/d/dovecot-antispam/dovecot-antispam_2.0+20120225-3.dsc dovecot-antispam_2.0+20120225-3_amd64.deb to main/d/dovecot-antispam/dovecot-antispam_2.0+20120225-3_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 676...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Ron Lee (supplier of updated dovecot-antispam 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, 20 Jun 2012 01:55:54 +0930 Source: dovecot-antispam Binary: dovecot-antispam Architecture: source amd64 Version: 2.0+20120225-3 Distribution: unstable Urgency: low Maintainer: Ron Lee Changed-By: Ron Lee Description: dovecot-antispam - Dovecot plugins for training spam filters Closes: 676007 Changes: dovecot-antispam (2.0+20120225-3) unstable; urgency=low . * Apply patch from Johannes for dovecot 2.1 Closes: #676007 Checksums-Sha1: 2d3ccfc7e246a1e168b501c687ae0adfd2b52040 1318 dovecot-antispam_2.0+20120225-3.dsc f3c27895ac20493092e20155bb60e59226187112 3775 dovecot-antispam_2.0+20120225-3.diff.gz 71eb264f0c3721367caa4a076f90495f75702260 23510 dovecot-antispam_2.0+20120225-3_amd64.deb Checksums-Sha256: 9c016616e7d2f08d478399484820a4fa2233def8830c83ba374be34cf1c8a898 1318 dovecot-antispam_2.0+20120225-3.dsc c43be5281513c3893bf004bc3d494c72b391512a321b56946d263bfd81ac80b8 3775 dovecot-antispam_2.0+20120225-3.diff.gz 6f69a3cf5960f404223f52701701f22bcfb3b441bc461436a84b0fd79d5db4e3 23510 dovecot-antispam_2.0+20120225-3_amd64.deb Files: a87bc4f6e316e743d5c0277ccd547bad 1318 mail optional dovecot-antispam_2.0+20120225-3.dsc 37a8e761e0152d1dc6892d1d7e75be5f 3775 mail optional dovecot-antispam_2.0+20120225-3.diff.gz 40fa391a9bc823401c09bf68d0feb4e9 23510 mail optional dovecot-antispam_2.0+20120225-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) iD8DBQFP4LUMp4BCHGgCHOQRAmPCAJ9Ax6p/rjpggVi8bysGolKVOWFS5QCfXjPw 9WZ2NKfCfBLDbWRDbYXhoYo=
Processed: tagging 678060
Processing commands for cont...@bugs.debian.org: > tags 678060 + pending Bug #678060 [nginx] Configuration should be purged in nginx-common Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 678060: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678060 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#678152: [Debian-med-packaging] Bug#678152: crashes at start
Hi, Thanks for your report. I'm working on this issue. Eric, freemedforms.com PGP.sig Description: Ceci est une signature électronique PGP
Bug#677995: gjiten: Doesn't show kana/kanji, displays garbage in kanjidic
Hi, This issue is caused most likely because you are trying to use euc-jp encoded dictionary files. Gjiten needs utf-8 encoded files. Regards, Botond On Mon, 18 Jun 2012 17:27:46 +0400 Serge Shpikin wrote: > Package: gjiten > Version: 2.6-2.2 > Severity: grave > Justification: renders package unusable > >* What led up to the situation? > Just installed gjiten. >* What exactly did you do (or not do) that was effective (or > ineffective)? > Launched, tried to search some words in dictionaries, launched Kanjidic > and tried search by strokes number. >* What was the outcome of this action? > No kana/kanji displayed in the main window, just English translation. > Console output contains lots of this: > (gjiten:11011): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: assertion > `g_utf8_validate (text, len, NULL)' failed > When looking up a kanji in kanjidic buttons contain garbage (seems like > a UTF-8 encoding issue): http://ompldr.org/vZWR1ZA (screenshot). Console > contains many lines like this: > (gjiten:11011): Pango-WARNING **: Invalid UTF-8 string passed to > pango_layout_set_text() >* What outcome did you expect instead? > Kanji displayed in both gjiten and kanjidic because without them it's > unusable at all. > > -- System Information: > Debian Release: wheezy/sid > APT prefers testing > APT policy: (700, 'testing'), (600, 'stable'), (500, 'unstable'), (400, > 'experimental') > Architecture: i386 (i686) > > Kernel: Linux 3.3.0-trunk-686-pae (SMP w/2 CPU cores) > Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/dash > > Versions of packages gjiten depends on: > ii edict 2012.05.09-1 > ii gconf2 3.2.5-1 > ii kanjidic2012.05.09-1 > ii libart-2.0-22.3.21-1 > ii libatk1.0-0 2.4.0-2 > ii libbonobo2-02.24.3-1 > ii libbonoboui2-0 2.24.3-1 > ii libc6 2.13-33 > ii libcairo2 1.12.2-1 > ii libfontconfig1 2.9.0-6 > ii libfreetype62.4.9-1 > ii libgconf2-4 3.2.5-1 > ii libgdk-pixbuf2.0-0 2.26.1-1 > ii libglade2-0 1:2.6.4-1 > ii libglib2.0-02.32.3-1 > ii libgnome2-0 2.32.1-2 > ii libgnomecanvas2-0 2.30.3-1 > ii libgnomeui-02.24.5-2 > ii libgnomevfs2-0 1:2.24.4-1 > ii libgtk2.0-0 2.24.10-1 > ii libice6 2:1.0.8-2 > ii liborbit2 1:2.14.19-0.1 > ii libpango1.0-0 1.30.0-1 > ii libpopt01.16-7 > ii libsm6 2:1.2.1-2 > ii libxml2 2.8.0+dfsg1-3 > > Versions of packages gjiten recommends: > ii fonts-ipaexfont-mincho [fonts-japanese-mincho] 00103-9 > ii fonts-ipafont-mincho [fonts-japanese-mincho]00303-6 > > Versions of packages gjiten suggests: > pn enamdict > > -- 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#677714: marked as done (wine-unstable: Incomplete upload of 1.5 for amd64)
Your message dated Tue, 19 Jun 2012 23:39:24 +0600 with message-id <20120619173924.ga9...@belkar.wrar.name> and subject line Re: Bug#677714: wine-unstable: Incomplete upload of 1.5 for amd64 has caused the Debian Bug report #677714, regarding wine-unstable: Incomplete upload of 1.5 for amd64 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.) -- 677714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677714 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: wine-unstable Version: 1.1.36-1 Severity: grave Justification: renders package unusable The original upload of wine-unstable for amd64 seems to be missing all packages. The original acceptance mail [1] does not list them neither in the list of build packages nor in the accepted packages. Therefore the only package available in amd64 is "wine-unstable" itself, making wine-unstable uninstallable. The other arches seem have been build just fine by the buildds. [1] http://packages.qa.debian.org/w/wine-unstable/news/20120611T193410Z.html -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.37-2-686 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages wine-unstable depends on: ii libwine-alsa-unstable 1.1.36-1 Windows API implementation - ALSA ii libwine-cms-unstable 1.1.36-1 Windows API implementation - color ii libwine-gl-unstable 1.1.36-1 Windows API implementation - OpenG ii libwine-gphoto2-unstable 1.1.36-1 Windows API implementation - camer ii libwine-ldap-unstable 1.1.36-1 Windows API implementation - LDAP ii libwine-openal-unstable 1.1.36-1 Windows API implementation - OpenA ii libwine-print-unstable1.1.36-1 Windows API implementation - print ii libwine-sane-unstable 1.1.36-1 Windows API implementation - scann ii wine-bin-unstable 1.1.36-1 Windows API implementation - binar Versions of packages wine-unstable recommends: ii ttf-liberation 1.06.0.20100721-1 Fonts with the same metrics as Tim Versions of packages wine-unstable suggests: pn avscan | klamav | clamav (no description available) ii binfmt-support2.0.8 Support for extra binary formats ii ttf-mscorefonts-installer 3.3Installer for Microsoft TrueType c pn winbind(no description available) pn wine-doc (no description available) Versions of packages libwine-unstable depends on: ii libc6 2.13-16 Embedded GNU C Library: Shared lib ii libfreetype62.4.4-1 FreeType 2 font engine, shared lib ii libhal1 0.5.14-5 Hardware Abstraction Layer - share ii libice6 2:1.0.7-1X11 Inter-Client Exchange library ii libjpeg88c-1 The Independent JPEG Group's JPEG ii libmpg123-0 1.12.1-3 MPEG layer 1/2/3 audio decoder -- ii libpng12-0 1.2.44-2 PNG library - runtime ii libsm6 2:1.2.0-1X11 Session Management library ii libssl1.0.0 1.0.0d-3 SSL shared libraries ii libx11-62:1.4.3-1X11 client-side library ii libxcursor1 1:1.1.11-1 X cursor management library ii libxext62:1.2.0-2X11 miscellaneous extension librar ii libxi6 2:1.4.1-1X11 Input extension library ii libxinerama12:1.1.1-1X11 Xinerama extension library ii libxml2 2.7.8.dfsg-2 GNOME XML library ii libxrandr2 2:1.3.1-1X11 RandR extension library ii libxrender1 1:0.9.6-1X Rendering Extension client libra ii zlib1g 1:1.2.3.4.dfsg-3 compression library - runtime -- no debconf information --- End Message --- --- Begin Message --- On Sat, Jun 16, 2012 at 12:41:40PM +0200, Heiko Stuebner wrote: > The original upload of wine-unstable for amd64 seems to be missing all > packages. > > The original acceptance mail [1] does not list them neither in the list of > build > packages nor in the accepted packages. > > Therefore the only package available in amd64 is "wine-unstable" itself, > making wine-unstable uninstallable. That's because it's i386-only and wine-unstable:amd64 should install wine-bin-unstable:i386 (well,
Bug#678060: Configuration should be purged in nginx-common
On 06/18/2012 10:35 PM, Jeroen Dekkers wrote: > Package: nginx > Version: 1.2.0-1 > Severity: serious > Tags: patch > > The nginx-light, nginx-full and nginx-naxsi packages delete the > /etc/nginx and /var/log directory when they are purged, but the > configuration files are owned by nginx-common. This can give all sort > of problems, for example if you do "apt-get install nginx-light", then > "apt-get install nginx-full" and "dpkg --purge nginx-light" you end up > with a sytem that doesn't have an /etc/nginx or /var/log/nginx. > > Attached patch moves the purging to the nginx-common package where it > belongs. > > -- System Information: > Debian Release: wheezy/sid > APT prefers precise-updates > APT policy: (500, 'precise-updates'), (500, 'precise-security'), (500, > 'precise'), (100, 'precise-backports') > Architecture: amd64 (x86_64) > > Kernel: Linux 3.2.0-25-generic (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 Hello Jeroen. Thanks for reporting us this issue. We applied your patch in the git repository. It will be fixed in the next upload. Thanks. -- Cyril "Davromaniak" Lavier KeyID 59E9A881 http://www.davromaniak.eu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: affects 670292
Processing commands for cont...@bugs.debian.org:
> affects 670292 - tuareg-mode
Bug #670292
[xemacs21-gnome-mule,xemacs21-gnome-nomule,xemacs21-gnome-mule-canna-wnn]
xemacs21-gnome-{, no-}mule{, -canna-wnn}: fails to upgrade from squeeze:
apt-get dist-upgrade hangs forever
Removed indication that 670292 affects tuareg-mode
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
670292: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=670292
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#677995: gjiten: Doesn't show kana/kanji, displays garbage in kanjidic
Yes, that could be the cause. But Debian provides only these dictionaries, I mean from edict. I also installed enamdict as gjiten suggests it and it contains some Japanese words but they aren't common words just proper names; place-names, surnames and so on. Kanjidic shows no kanjis when I select this dictionary as the source. I guess those dictionaries from edict package should be converted to UTF-8 then but I don't know if this will break something. Without dictionaries gjiten and kanjidic are useless anyway. 2012/6/19 Botond Botyanszki > Hi, > > This issue is caused most likely because you are trying to use euc-jp > encoded dictionary files. Gjiten needs utf-8 encoded files. > > Regards, > Botond > > On Mon, 18 Jun 2012 17:27:46 +0400 > Serge Shpikin wrote: > > > Package: gjiten > > Version: 2.6-2.2 > > Severity: grave > > Justification: renders package unusable > > > >* What led up to the situation? > > Just installed gjiten. > >* What exactly did you do (or not do) that was effective (or > > ineffective)? > > Launched, tried to search some words in dictionaries, launched > Kanjidic and tried search by strokes number. > >* What was the outcome of this action? > > No kana/kanji displayed in the main window, just English > translation. Console output contains lots of this: > > (gjiten:11011): Gtk-CRITICAL **: gtk_text_buffer_emit_insert: > assertion `g_utf8_validate (text, len, NULL)' failed > > When looking up a kanji in kanjidic buttons contain garbage (seems > like a UTF-8 encoding issue): http://ompldr.org/vZWR1ZA (screenshot). > Console contains many lines like this: > > (gjiten:11011): Pango-WARNING **: Invalid UTF-8 string passed to > pango_layout_set_text() > >* What outcome did you expect instead? > > Kanji displayed in both gjiten and kanjidic because without them > it's unusable at all. > > > > -- System Information: > > Debian Release: wheezy/sid > > APT prefers testing > > APT policy: (700, 'testing'), (600, 'stable'), (500, 'unstable'), > (400, 'experimental') > > Architecture: i386 (i686) > > > > Kernel: Linux 3.3.0-trunk-686-pae (SMP w/2 CPU cores) > > Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8) > > Shell: /bin/sh linked to /bin/dash > > > > Versions of packages gjiten depends on: > > ii edict 2012.05.09-1 > > ii gconf2 3.2.5-1 > > ii kanjidic2012.05.09-1 > > ii libart-2.0-22.3.21-1 > > ii libatk1.0-0 2.4.0-2 > > ii libbonobo2-02.24.3-1 > > ii libbonoboui2-0 2.24.3-1 > > ii libc6 2.13-33 > > ii libcairo2 1.12.2-1 > > ii libfontconfig1 2.9.0-6 > > ii libfreetype62.4.9-1 > > ii libgconf2-4 3.2.5-1 > > ii libgdk-pixbuf2.0-0 2.26.1-1 > > ii libglade2-0 1:2.6.4-1 > > ii libglib2.0-02.32.3-1 > > ii libgnome2-0 2.32.1-2 > > ii libgnomecanvas2-0 2.30.3-1 > > ii libgnomeui-02.24.5-2 > > ii libgnomevfs2-0 1:2.24.4-1 > > ii libgtk2.0-0 2.24.10-1 > > ii libice6 2:1.0.8-2 > > ii liborbit2 1:2.14.19-0.1 > > ii libpango1.0-0 1.30.0-1 > > ii libpopt01.16-7 > > ii libsm6 2:1.2.1-2 > > ii libxml2 2.8.0+dfsg1-3 > > > > Versions of packages gjiten recommends: > > ii fonts-ipaexfont-mincho [fonts-japanese-mincho] 00103-9 > > ii fonts-ipafont-mincho [fonts-japanese-mincho]00303-6 > > > > Versions of packages gjiten suggests: > > pn enamdict > > > > -- no debconf information > > > > > > >
Bug#676065: unadf: FTBFS: dpkg-buildpackage: error: dpkg-source -b unadf-0.7.11a
owner 676065 ! thanks I am working on this. Updated package will be soon. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: Fwd: unadf: FTBFS: dpkg-buildpackage: error: dpkg-source -b unadf-0.7.11a
Processing commands for cont...@bugs.debian.org: > owner 676065 ! Bug #676065 [src:unadf] unadf: FTBFS: dpkg-buildpackage: error: dpkg-source -b unadf-0.7.11a gave error exit status 2 Owner recorded as Boris Pek . > thanks Stopping processing here. Please contact me if you need assistance. -- 676065: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=676065 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#646540: marked as done (phpgacl: uninstallable in sid, needs to transition to smarty3)
Your message dated Tue, 19 Jun 2012 18:19:28 + with message-id and subject line Bug#646540: fixed in phpgacl 3.3.7-7.2 has caused the Debian Bug report #646540, regarding phpgacl: uninstallable in sid, needs to transition to smarty3 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.) -- 646540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: phpgacl Severity: minor Dear Maintainer, Smarty and Smarty3 will be merged soon, please consider to test your package with the 3.x series. Thank you. Cheers, --- End Message --- --- Begin Message --- Source: phpgacl Source-Version: 3.3.7-7.2 We believe that the bug you reported is fixed in the latest version of phpgacl, which is due to be installed in the Debian FTP archive: phpgacl_3.3.7-7.2.diff.gz to main/p/phpgacl/phpgacl_3.3.7-7.2.diff.gz phpgacl_3.3.7-7.2.dsc to main/p/phpgacl/phpgacl_3.3.7-7.2.dsc phpgacl_3.3.7-7.2_all.deb to main/p/phpgacl/phpgacl_3.3.7-7.2_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 646...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luk Claes (supplier of updated phpgacl 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: Sun, 17 Jun 2012 19:39:45 +0200 Source: phpgacl Binary: phpgacl Architecture: source all Version: 3.3.7-7.2 Distribution: unstable Urgency: high Maintainer: David Gil Changed-By: Luk Claes Description: phpgacl- PHP Generic Access Control Lists Closes: 646540 Changes: phpgacl (3.3.7-7.2) unstable; urgency=high . * Non-maintainer upload. * Switch to smarty3 (Closes: #646540). * Fix lintian warnings regarding build targets. Checksums-Sha1: 6ee4248f8d34a9de349b77840cdaf322b885e696 1228 phpgacl_3.3.7-7.2.dsc 3893cfa304fa5113c4f0e1cf7153969c489ec7e4 15546 phpgacl_3.3.7-7.2.diff.gz 9e96f8d5490337433fac3864b3f08adf981a1871 1791426 phpgacl_3.3.7-7.2_all.deb Checksums-Sha256: b95a43d31a49bb7ec3bf3241fb6fe6800f47d94f9cd419080371e5f0a3c90a8a 1228 phpgacl_3.3.7-7.2.dsc 67415ecbe3a6208f481593503aac7f036d82e65438dc62c2f79e1e8e75e417d0 15546 phpgacl_3.3.7-7.2.diff.gz 649d05ea73da48037cbebf3c141db99c778af635f1aa3f7da4ea1bb498561f58 1791426 phpgacl_3.3.7-7.2_all.deb Files: 32b9c002fb5ffc2b39537d2c910adfde 1228 web optional phpgacl_3.3.7-7.2.dsc fdabcacaeb33733beff397cc08123d70 15546 web optional phpgacl_3.3.7-7.2.diff.gz 41403a4837bb98191ced3878848123f6 1791426 web optional phpgacl_3.3.7-7.2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAk/eGXsACgkQ5UTeB5t8Mo1qUwCfZef1VDqTD8TkmhlllKgBgGzD btMAoMrFox5czidZvxMR3yJ5AmjGKEi5 =7Lmy -END PGP SIGNATURE- --- End Message ---
Bug#677421: More info
Here is a backtrace: #0 0x7fffd823987d in wxEvtHandler::SearchDynamicEventTable(wxEvent&) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0 #1 0x7fffd8239952 in wxEvtHandler::ProcessEvent(wxEvent&) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0 #2 0x7fffd8239910 in wxEvtHandler::ProcessEvent(wxEvent&) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0 #3 0x7fffd8bedb25 in wxScrollHelperEvtHandler::ProcessEvent(wxEvent&) () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0 #4 0x7fffd8239910 in wxEvtHandler::ProcessEvent(wxEvent&) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0 #5 0x7fffd8239910 in wxEvtHandler::ProcessEvent(wxEvent&) () from /usr/lib/x86_64-linux-gnu/libwx_baseu-2.8.so.0 #6 0x7fffd8afccbb in ?? () from /usr/lib/x86_64-linux-gnu/libwx_gtk2u_core-2.8.so.0 #7 0x7fffd7c4d538 in _gtk_marshal_BOOLEAN__BOXED (closure=0x5c3d530, return_value=0x7fffc760, n_param_values=, param_values=0x7fffc810, invocation_hint=, marshal_data=) at /tmp/buildd/gtk+2.0-2.24.10/gtk/gtkmarshalers.c:86 #8 0x7fffe4432724 in g_closure_invoke (closure=0x5c3d530, return_value=0x7fffc760, n_param_values=2, param_values=0x7fffc810, invocation_hint=0x7fffc7b0) at /tmp/buildd/glib2.0-2.32.3/./gobject/gclosure.c:777 #9 0x7fffe44437b0 in signal_emit_unlocked_R (node=node@entry=0x1e9aee0, detail=detail@entry=0, instance=instance@entry=0x4e8eb40, emission_return=emission_return@entry=0x7fffc8e0, instance_and_params=instance_and_params@entry= 0x7fffc810) at /tmp/buildd/glib2.0-2.32.3/./gobject/gsignal.c:3547 #10 0x7fffe444b34b in g_signal_emit_valist (instance=0x4e8eb40, signal_id=, detail=0, var_args=var_args@entry=0x7fffca68) at /tmp/buildd/glib2.0-2.32.3/./gobject/gsignal.c:3306 #11 0x7fffe444b8c2 in g_signal_emit (instance=, signal_id=, detail=) at /tmp/buildd/glib2.0-2.32.3/./gobject/gsignal.c:3352 #12 0x7fffd7d66451 in gtk_widget_event_internal (widget=0x4e8eb40, event=0x4c98a30) at /tmp/buildd/gtk+2.0-2.24.10/gtk/gtkwidget.c:4984 #13 0x7fffd7c4b6c3 in IA__gtk_propagate_event (widget=0x4e8eb40, event=0x4c98a30) at /tmp/buildd/gtk+2.0-2.24.10/gtk/gtkmain.c:2489 #14 0x7fffd7c4ba23 in IA__gtk_main_do_event (event=0x4c98a30) at /tmp/buildd/gtk+2.0-2.24.10/gtk/gtkmain.c:1684 #15 0x7fffd78b71ec in gdk_event_dispatch (source=, source@entry=0x16bec10, callback=, user_data=) at /tmp/buildd/gtk+2.0-2.24.10/gdk/x11/gdkevents-x11.c:2377 #16 0x7fffe46bb205 in g_main_dispatch (context=0x1e31d40) at /tmp/buildd/glib2.0-2.32.3/./glib/gmain.c:2539 #17 g_main_context_dispatch (context=context@entry=0x1e31d40) at /tmp/buildd/glib2.0-2.32.3/./glib/gmain.c:3075 #18 0x7fffe46bb538 in g_main_context_iterate (context=0x1e31d40, block=block@entry=1, dispatch=dispatch@entry=1, self=) at /tmp/buildd/glib2.0-2.32.3/./glib/gmain.c:3146 #19 0x7fffe46bb932 in g_main_loop_run (loop=0x1403690) at /tmp/buildd/glib2.0-2.32.3/./glib/gmain.c:3340 It is not very useful because running mayavi2 is impossible because of #645042 in python-vtk and I don't think I can build python-vtk properly. -- WBR, wRAR signature.asc Description: Digital signature
Bug#671633: marked as done (tortoisehg: TypeError on launch (Sid))
Your message dated Wed, 20 Jun 2012 00:34:42 +0600 with message-id <20120619183442.gn5...@belkar.wrar.name> and subject line Works now has caused the Debian Bug report #671633, regarding tortoisehg: TypeError on launch (Sid) 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.) -- 671633: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=671633 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: tortoisehg Version: 2.3-1 Severity: grave Justification: renders package unusable Dear Maintainer, Since my last updates, tortoisehg isn't working anymore. Due to bug 671473, I downgraded mercurial to testing, but when I launch tortoisehg I have this error : #!python ** Mercurial version (2.1.2). TortoiseHg version (2.3) ** Command: ** CWD: /home/ustilago ** Encoding: UTF-8 ** Extensions loaded: ** Python version: 2.7.3rc2 (default, Apr 22 2012, 22:30:17) [GCC 4.6.3] ** Qt-4.8.1 PyQt-4.9.1 Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/tortoisehg/hgqt/run.py", line 548, in __call__ dlg = dlgfunc(ui, *args, **opts) File "/usr/lib/python2.7/dist-packages/tortoisehg/hgqt/workbench.py", line 951, in run w = Workbench() File "/usr/lib/python2.7/dist-packages/tortoisehg/hgqt/workbench.py", line 62, in __init__ self.log = LogDockWidget(self) File "/usr/lib/python2.7/dist-packages/tortoisehg/hgqt/docklog.py", line 27, in __init__ self.logte = cmdui.ConsoleWidget() File "/usr/lib/python2.7/dist-packages/tortoisehg/hgqt/cmdui.py", line 511, in __init__ self._initlogwidget() File "/usr/lib/python2.7/dist-packages/tortoisehg/hgqt/cmdui.py", line 518, in _initlogwidget self._logwidget = _LogWidgetForConsole(self) File "/usr/lib/python2.7/dist-packages/tortoisehg/hgqt/cmdui.py", line 387, in __init__ super(_LogWidgetForConsole, self).__init__(parent) File "/usr/lib/python2.7/dist-packages/tortoisehg/hgqt/cmdui.py", line 334, in __init__ super(LogWidget, self).__init__(parent) TypeError: QsciScintilla(QWidget parent=None): argument 1 has unexpected type 'ConsoleWidget' The upgraded dependant packages are : libqscintilla2-8:amd64 (2.6.1-1, 2.6.1-5) python-qscintilla2:amd64 (2.6.1-1, 2.6.1-5) python-qt4:amd64 (4.9.1-1, 4.9.1-3) Downgrading this 3 packages to testing version resolves this problem. Regards, Sebastien KALT -- System Information: Debian Release: wheezy/sid APT prefers unstable APT policy: (900, 'unstable'), (800, 'testing'), (700, 'stable-updates'), (700, 'stable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Shell: /bin/sh linked to /bin/dash Versions of packages tortoisehg depends on: ii mercurial 2.1.2-2 ii python 2.7.2-10 ii python-gobject 3.2.0-3 ii python-qscintilla2 2.6.1-1 ii python-qt4 4.9.1-3 ii python2.6 2.6.7-4 ii python2.7 2.7.3~rc2-2.1 Versions of packages tortoisehg recommends: ii libjs-jquery 1.7.2-1 ii libjs-underscore 1.3.3-1 ii python-iniparse 0.4-2.1 ii python-pygments 1.5+dfsg-1 tortoisehg suggests no packages. -- no debconf information --- End Message --- --- Begin Message --- With python-qscintilla2 2.6.1-5+b1 on current sid I do not see any problems. -- WBR, wRAR signature.asc Description: Digital signature --- End Message ---
Bug#629027: Only supports 2.6.32
On Fri, Jun 03, 2011 at 05:34:00AM +0200, Moritz Muehlenhoff wrote: > Package: linux-patch-tuxonice > Severity: serious > > This package only provides a patch against 2.6.32 and doesn't apply against > current kernels. For the reference: most recent code available at https://github.com/NigelCunningham/tuxonice-kernel -- WBR, wRAR signature.asc Description: Digital signature
Processed: tagging 677801
Processing commands for cont...@bugs.debian.org: > tags 677801 + patch Bug #677801 [python-pip] AttributeError: 'module' object has no attribute 'uses_fragment' Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 677801: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677801 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#555168: Unclear license situation for (e)glibc locales provided by you
Hello, you are listed as contact person/author of the following locale: mn_MN This locale comes with a statement % Distribution and use is free, also % for commercial purposes. Thus it does not allow modification; it is unclear, however, if this statement was meant as a license. As discussed in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555168 this locale could strictly speaking not be part of Debian which would be a great loss. (Currently it is allowed pending investigation). To properly resolve this, I would like to ask you the following question: Would you be willing to relicense this locale to a proper license, e.g. (L)GPL v2 or higher or another free software license of your choice? If you have any questions regarding this issue, do not hesitate to contact me (via the reply-to address set). Thanks for helping to resolve this! Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software libre: http://www.ffii.de/ signature.asc Description: Digital signature
Bug#555168: Unclear license situation for (e)glibc locales provided by you
Hello, you are listed as contact person/author of the following locale: mi_NZ This locale comes with a statement % Distribution and use is free, also % for commercial purposes. Thus it does not allow modification; it is unclear, however, if this statement was meant as a license. As discussed in http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555168 this locale could strictly speaking not be part of Debian which would be a great loss. (Currently it is allowed pending investigation). To properly resolve this, I would like to ask you the following question: Would you be willing to relicense this locale to a proper license, e.g. (L)GPL v2 or higher or another free software license of your choice? If you have any questions regarding this issue, do not hesitate to contact me (via the reply-to address set). Thanks for helping to resolve this! Helge -- Dr. Helge Kreutzmann deb...@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software libre: http://www.ffii.de/ signature.asc Description: Digital signature
Bug#677974: marked as done (eclipse-egit: FTBFS OSGi dependency issues)
Your message dated Tue, 19 Jun 2012 21:13:35 +0200 with message-id <4fe0cf5f.8030...@thykier.net> and subject line Re: Bug#677974: eclipse-egit: FTBFS with eclipse 3.8.0 (git version) has caused the Debian Bug report #677974, regarding eclipse-egit: FTBFS OSGi dependency issues 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.) -- 677974: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=677974 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: eclipse-egit Severity: important Hi, Snippet from the log included below - I haven't tested if it is reproducible with eclipse from sid; if it is I will bump the severity to serious. """ allElements: init: generateScript: [eclipse.buildScript] Some inter-plug-in dependencies have not been satisfied. [eclipse.buildScript] Bundle org.eclipse.egit.core.test: [eclipse.buildScript] Host plug-in org.eclipse.egit.core_0.0.0 has not been found. [eclipse.buildScript] Missing required plug-in org.mockito_[1.8.0,1.9.0). [eclipse.buildScript] Missing required plug-in org.hamcrest_[1.1.0,2.0.0). [eclipse.buildScript] Unsatisfied import package org.mockito_[1.8.0,1.9.0). [eclipse.buildScript] Unsatisfied import package org.mockito.stubbing_[1.8.0,1.9.0). [eclipse.buildScript] Unsatisfied import package org.eclipse.egit.core_[1.1.0,1.2.0). [eclipse.buildScript] Unsatisfied import package org.eclipse.egit.core.op_[1.1.0,1.2.0). [eclipse.buildScript] Unsatisfied import package org.eclipse.egit.core.project_[1.1.0,1.2.0). [eclipse.buildScript] Unsatisfied import package org.eclipse.jgit.api.errors_[1.1.0,1.2.0). [eclipse.buildScript] Unsatisfied import package org.eclipse.jgit.junit_[1.1.0,1.2.0). [eclipse.buildScript] Unsatisfied import package org.eclipse.jgit.lib_[1.1.0,1.2.0). [eclipse.buildScript] Unsatisfied import package org.eclipse.jgit.treewalk_[1.1.0,1.2.0). [eclipse.buildScript] Unsatisfied import package org.eclipse.jgit.treewalk.filter_[1.1.0,1.2.0). [eclipse.buildScript] Unsatisfied import package org.eclipse.jgit.util_[1.1.0,1.2.0). [eclipse.buildScript] Bundle org.eclipse.egit.core: [eclipse.buildScript] Unsatisfied import package org.eclipse.jgit.api_[1.1.0,1.2.0). [eclipse.buildScript] Unsatisfied import package org.eclipse.jgit.api.errors_[1.1.0,1.2.0). [eclipse.buildScript] Unsatisfied import package org.eclipse.jgit.diff_[1.1.0,1.2.0). [eclipse.buildScript] Unsatisfied import package org.eclipse.jgit.dircache_[1.1.0,1.2.0). [eclipse.buildScript] Unsatisfied import package org.eclipse.jgit.errors_[1.1.0,1.2.0). [eclipse.buildScript] Unsatisfied import package org.eclipse.jgit.lib_[1.1.0,1.2.0). [eclipse.buildScript] Unsatisfied import package org.eclipse.jgit.merge_[1.1.0,1.2.0). [eclipse.buildScript] Unsatisfied import package org.eclipse.jgit.patch_[1.1.0,1.2.0). [eclipse.buildScript] Unsatisfied import package org.eclipse.jgit.revwalk_[1.1.0,1.2.0). [eclipse.buildScript] Unsatisfied import package org.eclipse.jgit.revwalk.filter_[1.1.0,1.2.0). [eclipse.buildScript] Unsatisfied import package org.eclipse.jgit.storage.file_[1.1.0,1.2.0). [eclipse.buildScript] Unsatisfied import package org.eclipse.jgit.transport_[1.1.0,1.2.0). [eclipse.buildScript] Unsatisfied import package org.eclipse.jgit.treewalk_[1.1.0,1.2.0). [eclipse.buildScript] Unsatisfied import package org.eclipse.jgit.treewalk.filter_[1.1.0,1.2.0). [eclipse.buildScript] Unsatisfied import package org.eclipse.jgit.util_[1.1.0,1.2.0). [eclipse.buildScript] Bundle org.eclipse.egit.mylyn.ui.test: [eclipse.buildScript] Host plug-in org.eclipse.egit.mylyn.ui_1.1.0 has not been found. [eclipse.buildScript] Missing required plug-in org.apache.log4j_[1.0.0,2.0.0). [eclipse.buildScript] Missing required plug-in org.hamcrest_[1.1.0,2.0.0). [eclipse.buildScript] Bundle org.eclipse.egit.mylyn.ui: [eclipse.buildScript] Missing required plug-in org.eclipse.mylyn.monitor.core_[3.0.0,4.0.0). [eclipse.buildScript] Missing required plug-in org.eclipse.mylyn.tasks.core_[3.0.0,4.0.0). [eclipse.buildScript] Missing required plug-in org.eclipse.mylyn.tasks.ui_[3.0.0,4.0.0). [eclipse.buildScript] Missing required plug-in org.eclipse.mylyn.team.ui_[3.0.0,4.0.0). [eclipse.buildScript] Missing required plug-in org.eclipse.mylyn.resources.ui_[3.0.0,4.0.0). [eclipse.buildScript] Missing required plug-in org.eclipse.mylyn.context.core_[3.0.0,4.0.0). [eclipse.buildScript] Unsatisfied import package org.eclipse.egit.core_[1.1.0,1.2.0). [eclipse.buildScript] Unsatisfied import package org.ecli
Bug#676984: exim 4 upgrade breaks Python smtplib
I upgraded exim4 in wheezy this morning and I am getting the same gnome-keyring error as in this bug report. I am getting the error in a Python program that uses smtplib to send email. I used the snapshot directory to downgrade the exim4 packages in wheezy before today and the problem went away. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#661991: should libtrash be removed?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 clone 661991 -1 reopen -1 retitle -1 RM: libtrash/2.4-2 severity -1 normal reassign -1 release.debian.org user -1 release.debian@packages.debian.org usertag -1 rm thanks libtrash has been removed from unstable (#678094) because it was RC-buggy and is unmaintained upstream. The very same version is in squeeze and the RC bug (which boils down to: does not work at all except partially producing segfaults) is also reproducible - see bug log for details. The maintainer agrees that libtrash should be removed, so please remove libtrash from squeeze. Best Regards Willi -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCAAGBQJP4M+KAAoJEIy+IZx0V22BZZMP/1dmCtgtLZRoI+XTjn4a69lY Lo5ItNFw2Mo6NZf+hhpg+mEx2S3tV7+MJBZgs5DlMrY35qOSA9mIiFPspNKO6pCa ieJT7BSnQliOMWtmXqJ4fT7U0ksyeNSWEQL63mfNAZXp5NDrPRSMZrtTK4qETbiY jKm/KuHrzGHf0+EqHdCK47O7C6PRJZSlzxNSDSdUvBv5OrSF/ai+2hJdzYVD3mQy +HjgAmA8sQn2ZV8+viVGvYfkN0RLuDzTTYwnslFCDagMS9xPIixWTTOT7yI6BHS/ HpqCWEaSD/n20zILbV99K05qZlX0NZbQh+goqfzvzqwBrfar4hXz/EsggmpEmbj4 +icb1E02HnhAhXLaO5gfhLuC0eBZ/YRE4i4oXqPLB1Q7G4XkMgFAZCFhb7hYo9YB kfNna6nzfmKasUvD9sLs8bOcQjkLwybS/Hf93dUT1fTXfqHUFq3NakTJSnE8XnGv EfIMx55zcutvAjlp3jPWjRY29RiJGalxKjEPrj13OgyA3D0lvXwCBkuQ7uwGyRxG w9HzgZNqO7pDKzKzT4fcOdzcWZLZKVCq5srOWwOMfBJkcj/MVdina+tgf7HsdjyC zXd3Z7ZoUvKp94iUoFXMwciKAHEFefNzeIw6CVcHluEFp/uK4qMco0N/XPeFaC6L obGGSiMB/Q25Hx+wp3Cc =z0Vy -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed (with 1 errors): Re: Bug#661991: should libtrash be removed?
Processing commands for cont...@bugs.debian.org:
> clone 661991 -1
Bug #661991 {Done: Debian FTP Masters }
[libtrash] libtrash does nothing but causes segmentation fault
Bug 661991 cloned as bug 678178
> reopen -1
Bug #678178 {Done: Debian FTP Masters }
[libtrash] libtrash does nothing but causes segmentation fault
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 2.4-2+rm.
> retitle -1 RM: libtrash/2.4-2
Bug #678178 [libtrash] libtrash does nothing but causes segmentation fault
Changed Bug title to 'RM: libtrash/2.4-2' from 'libtrash does nothing but
causes segmentation fault'
> severity -1 normal
Bug #678178 [libtrash] RM: libtrash/2.4-2
Severity set to 'normal' from 'critical'
> reassign -1 release.debian.org
Bug #678178 [libtrash] RM: libtrash/2.4-2
Bug reassigned from package 'libtrash' to 'release.debian.org'.
No longer marked as found in versions libtrash/2.4-2.
Ignoring request to alter fixed versions of bug #678178 to the same values
previously set
> user -1 release.debian@packages.debian.org
Unknown command or malformed arguments to command.
> usertag -1 rm
Bug#678178: RM: libtrash/2.4-2
User is wi...@wm1.at
There were no usertags set.
Usertags are now: rm.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
661991: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=661991
678178: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678178
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#669469: (no subject)
tags 669469 patch thanks -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tags 669469 patch Bug #669469 [src:zeitgeist-sharp] zeitgeist-sharp: FTBFS: configure:3038: error: Package requirements (zeitgeist-daemon >= 0.7.1) were not met Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 669469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669469 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#673679: alsa-base: rmdir: failed to remove `/etc/apm/suspend.d': No such file or directory
Package: alsa-base Followup-For: Bug #673679 Any status on this bug? Current unstable still only has 1.0.25+2, uninstallable due to this bug. - 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#675951: marked as done (ruby-ncurses: FTBFS: -Werror=format-security)
Your message dated Tue, 19 Jun 2012 19:40:00 + with message-id and subject line Bug#675951: fixed in ruby-ncurses 1.3.1-2 has caused the Debian Bug report #675951, regarding ruby-ncurses: FTBFS: -Werror=format-security 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.) -- 675951: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=675951 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Package: src:ruby-ncurses Version: 1.3.1-1 Severity: serious Tags: sid wheezy X-Debbugs-Cc: debian-r...@lists.debian.org Justification: fails to build from source (but built successfully in the past) Hi, Built against libruby1.9.1 1.9.3.194-1, ruby-ncurses now FTBFS due to failing a build-hardening check: > compiling form_wrap.c > form_wrap.c: In function 'rbncurs_c_set_field_type': > form_wrap.c:629:15: warning: initialization makes pointer from integer > without a cast [enabled by default] > form_wrap.c:629:5: warning: passing argument 1 of 'rb_string_value_ptr' from > incompatible pointer type [enabled by default] > In file included from /usr/include/ruby-1.9.1/ruby.h:32:0, > from form_wrap.h:34, > from form_wrap.c:32: > /usr/include/ruby-1.9.1/ruby/ruby.h:463:7: note: expected 'volatile VALUE *' > but argument is of type 'VALUE **' > form_wrap.c:657:10: warning: initialization makes pointer from integer > without a cast [enabled by default] > form_wrap.c:657:10: warning: (near initialization for 'int2num_v') [enabled > by default] > form_wrap.c:657:3: warning: passing argument 1 of 'rb_string_value_ptr' from > incompatible pointer type [enabled by default] > In file included from /usr/include/ruby-1.9.1/ruby.h:32:0, > from form_wrap.h:34, > from form_wrap.c:32: > /usr/include/ruby-1.9.1/ruby/ruby.h:463:7: note: expected 'volatile VALUE *' > but argument is of type 'VALUE **' > form_wrap.c: In function 'rbncurs_c_set_field_buffer': > form_wrap.c:746:10: warning: initialization makes pointer from integer > without a cast [enabled by default] > form_wrap.c:746:10: warning: (near initialization for 'int2num_v') [enabled > by default] > form_wrap.c:746:3: warning: passing argument 1 of 'rb_string_value_ptr' from > incompatible pointer type [enabled by default] > In file included from /usr/include/ruby-1.9.1/ruby.h:32:0, > from form_wrap.h:34, > from form_wrap.c:32: > /usr/include/ruby-1.9.1/ruby/ruby.h:463:7: note: expected 'volatile VALUE *' > but argument is of type 'VALUE **' > form_wrap.c: In function 'rbncurs_c_form_request_by_name': > form_wrap.c:1056:10: warning: initialization makes pointer from integer > without a cast [enabled by default] > form_wrap.c:1056:10: warning: (near initialization for 'int2num_v') [enabled > by default] > form_wrap.c:1056:3: warning: passing argument 1 of 'rb_string_value_ptr' from > incompatible pointer type [enabled by default] > In file included from /usr/include/ruby-1.9.1/ruby.h:32:0, > from form_wrap.h:34, > from form_wrap.c:32: > /usr/include/ruby-1.9.1/ruby/ruby.h:463:7: note: expected 'volatile VALUE *' > but argument is of type 'VALUE **' > form_wrap.c: In function 'make_arg': > form_wrap.c:1135:5: error: format not a string literal and no format > arguments [-Werror=format-security] > cc1: some warnings being treated as errors > make[1]: *** [form_wrap.o] Error 1 Regards, -- Steven Chamberlain ste...@pyro.eu.org --- End Message --- --- Begin Message --- Source: ruby-ncurses Source-Version: 1.3.1-2 We believe that the bug you reported is fixed in the latest version of ruby-ncurses, which is due to be installed in the Debian FTP archive: libncurses-ruby1.8_1.3.1-2_all.deb to main/r/ruby-ncurses/libncurses-ruby1.8_1.3.1-2_all.deb libncurses-ruby1.9.1_1.3.1-2_all.deb to main/r/ruby-ncurses/libncurses-ruby1.9.1_1.3.1-2_all.deb libncurses-ruby1.9_1.3.1-2_all.deb to main/r/ruby-ncurses/libncurses-ruby1.9_1.3.1-2_all.deb libncurses-ruby_1.3.1-2_all.deb to main/r/ruby-ncurses/libncurses-ruby_1.3.1-2_all.deb ruby-ncurses_1.3.1-2.debian.tar.gz to main/r/ruby-ncurses/ruby-ncurses_1.3.1-2.debian.tar.gz ruby-ncurses_1.3.1-2.dsc to main/r/ruby-ncurses/ruby-ncurses_1.3.1-2.dsc ruby-ncurses_1.3.1-2_amd64.deb to main/r/ruby-ncurses/ruby-ncurses_1.3.1-2_amd64.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 675...@bugs.debian.org, and the maintainer will reopen
Bug#677565: msva-perl: Insecure dependency in socket while running with -T switch at /usr/lib/perl/5.14/IO/Socket.pm line 80
Hi, Iain Lane wrote (19 Jun 2012 10:58:58 GMT) : > Downgrading libnet-server-perl to 0.99-4 fixes it. Thanks a lot for confirming this. > Perhaps you should consider blocking that from migrating if it is > exposing bugs like this. I agree this bug is annoying, but even knowing that, I doubt Net-Server-2.005 is any worse than our previous Net::Server 0.99 series, that is seriously buggy itself, and carries a handful of Debian specific patches that were merged upstream since then. However, given Net::Server pretends to be taint clean, it does looks like there's a serious bug in there, that shall be reported and fixed. I'll try to isolate a minimal testcase and will report it in Debian and upstream. Cheers, -- intrigeri | GnuPG key @ https://gaffer.ptitcanardnoir.org/intrigeri/intrigeri.asc | OTR fingerprint @ https://gaffer.ptitcanardnoir.org/intrigeri/otr.asc -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: > tag 678036 + pending Bug #678036 [python-networkx] 1.7~rc1 causes FTBFS in nipype 0.5.3-1 Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 678036: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=678036 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#673679: [Pkg-alsa-devel] Bug#673679: alsa-base: rmdir: failed to remove `/etc/apm/suspend.d': No such file or directory
Hey Josh, On Tue, Jun 19, 2012 at 12:43:24PM -0700, Josh Triplett wrote: > Any status on this bug? Current unstable still only has 1.0.25+2, > uninstallable due to this bug. I'm in the middle of exams, so NMUs are very welcome. Else, expect an update next week. Jordi -- Jordi Mallach Pérez -- Debian developer http://www.debian.org/ jo...@sindominio.net jo...@debian.org http://www.sindominio.net/ GnuPG public key information available at http://oskuro.net/ signature.asc Description: Digital signature
Bug#669434: gzip: FTBFS: ../../lib/fchdir.c:149:15: error: storage size of 'statbuf' isn't known
Andrey Rahmatullin writes: > Also note that 1.5 was released two days ago which contains the > updated gnulib. Thanks for mentioning this, as I hadn't noticed yet! Bdale pgpukqEdsVJxF.pgp Description: PGP signature
Bug#666331: marked as done (libdbi-drivers: FTBFS: configure: error: Invalid SQLite3 directory - libraries not found.)
Your message dated Wed, 20 Jun 2012 03:56:23 +0800 with message-id <4fe0d967.6060...@goirand.fr> and subject line This was fixed has caused the Debian Bug report #666331, regarding libdbi-drivers: FTBFS: configure: error: Invalid SQLite3 directory - libraries not found. 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.) -- 666331: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666331 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems --- Begin Message --- Source: libdbi-drivers Version: 0.8.3-1+s-2.1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120330 qa-ftbfs qa-ftbfs-buildarch Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. This rebuild was done by building only architecture:any binary packages (binary-arch target of debian/rules), and using a recent dpkg that uses the build-arch target if available. Also, only the Build-Depends were installed, not the Build-Depends-Indep. Relevant part: > debian/rules build > test -d debian/patched || install -d debian/patched > dpatch apply-all > applying patch 001_test_dbi.c to ./ ... ok. > dpatch cat-all >>patch-stampT > mv -f patch-stampT patch-stamp > dh_testdir > dh_autoreconf > configure.in:98: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected > in body > ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... > ../../lib/autoconf/general.m4:2591: _AC_COMPILE_IFELSE is expanded from... > ../../lib/autoconf/general.m4:2607: AC_COMPILE_IFELSE is expanded from... > acinclude.m4:420: AC_CHECK_FIREBIRD_INTERBASE is expanded from... > configure.in:98: the top level > configure.in:98: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected > in body > ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... > ../../lib/autoconf/general.m4:2591: _AC_COMPILE_IFELSE is expanded from... > ../../lib/autoconf/general.m4:2607: AC_COMPILE_IFELSE is expanded from... > acinclude.m4:420: AC_CHECK_FIREBIRD_INTERBASE is expanded from... > configure.in:98: the top level > libtoolize: putting auxiliary files in `.'. > libtoolize: copying file `./ltmain.sh' > libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.in and > libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree. > libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. > configure.in:98: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected > in body > ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... > ../../lib/autoconf/general.m4:2591: _AC_COMPILE_IFELSE is expanded from... > ../../lib/autoconf/general.m4:2607: AC_COMPILE_IFELSE is expanded from... > acinclude.m4:420: AC_CHECK_FIREBIRD_INTERBASE is expanded from... > configure.in:98: the top level > configure.in:98: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected > in body > ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... > ../../lib/autoconf/general.m4:2591: _AC_COMPILE_IFELSE is expanded from... > ../../lib/autoconf/general.m4:2607: AC_COMPILE_IFELSE is expanded from... > acinclude.m4:420: AC_CHECK_FIREBIRD_INTERBASE is expanded from... > configure.in:98: the top level > configure.in:98: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected > in body > ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... > ../../lib/autoconf/general.m4:2591: _AC_COMPILE_IFELSE is expanded from... > ../../lib/autoconf/general.m4:2607: AC_COMPILE_IFELSE is expanded from... > acinclude.m4:420: AC_CHECK_FIREBIRD_INTERBASE is expanded from... > configure.in:98: the top level > configure.in:98: warning: AC_LANG_CONFTEST: no AC_LANG_SOURCE call detected > in body > ../../lib/autoconf/lang.m4:194: AC_LANG_CONFTEST is expanded from... > ../../lib/autoconf/general.m4:2591: _AC_COMPILE_IFELSE is expanded from... > ../../lib/autoconf/general.m4:2607: AC_COMPILE_IFELSE is expanded from... > acinclude.m4:420: AC_CHECK_FIREBIRD_INTERBASE is expanded from... > configure.in:98: the top level > configure.in:7: installing `./config.guess' > configure.in:7: installing `./config.sub' > drivers/firebird/Makefile.am:10: docdir was already defined in condition > TRUE, which includes condition BUILDDOCS and HAVE_FIREBIRD_INTERBASE ... > configure.in:2: ... `docdir' previously defined here > drivers/firebird/Makefile.am:11: htmldir was already defined in condition > TRUE, which includes condition BUILDDOCS and HAVE_FIREBIRD_INTERBASE ... > configure.in:2: ... `htmldir' previously defined here > drivers/firebird/Makefile.am:15:
Bug#678189: packagekit-backend-aptcc: insecure tempfile use
Package: packagekit-backend-aptcc Version: 0.7.4-4 Severity: grave Tags: security Justification: user security hole /usr/share/PackageKit/helpers/aptcc/pkconffile uses a tempfile with a fixed name in /tmp, which means anyone could create a /tmp/pkconffile.templates symlink and have root trash the contents of the linked file. You need to use mktemp (or File::Temp or however it's called in perl). Cheers, Julien -- System Information: Debian Release: wheezy/sid APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'proposed-updates'), (500, 'unstable'), (500, 'testing'), (500, 'stable'), (101, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages packagekit-backend-aptcc depends on: ii app-install-data2010.11.17 ii libapt-inst1.5 0.9.6 ii libapt-pkg4.12 0.9.6 ii libc6 2.13-33 ii libgcc1 1:4.7.1-1 ii libglib2.0-02.32.3-1 ii libgstreamer0.10-0 0.10.36-1 ii libstdc++6 4.7.1-1 ii libxml2 2.8.0+dfsg1-4 ii python 2.7.3~rc2-1 ii python-packagekit 0.7.4-4 Versions of packages packagekit-backend-aptcc recommends: ii apt-xapian-index 0.45 ii packagekit0.7.4-4 Versions of packages packagekit-backend-aptcc suggests: ii gdebi-core 0.8.5 -- 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
Processed: tagging 669469
Processing commands for cont...@bugs.debian.org: > tags 669469 + pending Bug #669469 [src:zeitgeist-sharp] zeitgeist-sharp: FTBFS: configure:3038: error: Package requirements (zeitgeist-daemon >= 0.7.1) were not met Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. -- 669469: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=669469 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#677421: More info
#0 0x7fffd7f9e9bd in wxEvtHandler::ProcessEvent (this=0x5686c60,
event=...) at ../src/common/event.cpp:1301
#1 0x7fffd7f9ea1f in wxEvtHandler::ProcessEvent (this=0x75c4a10,
event=...) at ../src/common/event.cpp:1308
#2 0x7fffd8a5e07c in wxScrollHelperEvtHandler::ProcessEvent
(this=0x75c4a10, event=...) at ../src/generic/scrlwing.cpp:208
#3 0x7fffd7f9ea1f in wxEvtHandler::ProcessEvent (this=0x5bf5a80,
event=...) at ../src/common/event.cpp:1308
#4 0x7fffd7f9ea1f in wxEvtHandler::ProcessEvent (this=0x772f4b0,
event=...) at ../src/common/event.cpp:1308
#5 0x7fffd8915c58 in wxWindow::GTKProcessEvent (this=0x5686c60, event=...)
at ../src/gtk/window.cpp:1435
#6 0x7fffd8916203 in gtk_window_button_press_callback (widget=0x6603340,
gdk_event=0x63f7080, win=0x5686c60) at ../src/gtk/window.cpp:1634
#7 0x7fffd7953538 in _gtk_marshal_BOOLEAN__BOXED (closure=0x567c3c0,
return_value=0x7fffb720, n_param_values=,
param_values=0x7fffb7d0, invocation_hint=,
marshal_data=)
at /tmp/buildd/gtk+2.0-2.24.10/gtk/gtkmarshalers.c:86
#8 0x7fffe44bf724 in g_closure_invoke (closure=0x567c3c0,
return_value=0x7fffb720, n_param_values=2, param_values=0x7fffb7d0,
invocation_hint=0x7fffb770) at
/tmp/buildd/glib2.0-2.32.3/./gobject/gclosure.c:777
#9 0x7fffe44d07b0 in signal_emit_unlocked_R (node=node@entry=0x1b733c0,
detail=detail@entry=0, instance=instance@entry=0x6603340,
emission_return=emission_return@entry=0x7fffb8a0,
instance_and_params=instance_and_params@entry=
0x7fffb7d0) at /tmp/buildd/glib2.0-2.32.3/./gobject/gsignal.c:3547
#10 0x7fffe44d834b in g_signal_emit_valist (instance=0x6603340,
signal_id=, detail=0, var_args=var_args@entry=0x7fffba28) at
/tmp/buildd/glib2.0-2.32.3/./gobject/gsignal.c:3306
#11 0x7fffe44d88c2 in g_signal_emit (instance=,
signal_id=, detail=) at
/tmp/buildd/glib2.0-2.32.3/./gobject/gsignal.c:3352
#12 0x7fffd7a6c451 in gtk_widget_event_internal (widget=0x6603340,
event=0x63f7080) at /tmp/buildd/gtk+2.0-2.24.10/gtk/gtkwidget.c:4984
#13 0x7fffd79516c3 in IA__gtk_propagate_event (widget=0x6603340,
event=0x63f7080) at /tmp/buildd/gtk+2.0-2.24.10/gtk/gtkmain.c:2489
#14 0x7fffd7951a23 in IA__gtk_main_do_event (event=0x63f7080) at
/tmp/buildd/gtk+2.0-2.24.10/gtk/gtkmain.c:1684
#15 0x7fffd75bd1ec in gdk_event_dispatch (source=,
source@entry=0x1cacbf0, callback=, user_data=) at
/tmp/buildd/gtk+2.0-2.24.10/gdk/x11/gdkevents-x11.c:2377
#16 0x7fffe4748205 in g_main_dispatch (context=0x2389610) at
/tmp/buildd/glib2.0-2.32.3/./glib/gmain.c:2539
#17 g_main_context_dispatch (context=context@entry=0x2389610) at
/tmp/buildd/glib2.0-2.32.3/./glib/gmain.c:3075
#18 0x7fffe4748538 in g_main_context_iterate (context=0x2389610,
block=block@entry=1, dispatch=dispatch@entry=1, self=)
at /tmp/buildd/glib2.0-2.32.3/./glib/gmain.c:3146
#19 0x7fffe4748932 in g_main_loop_run (loop=0x3a097a0) at
/tmp/buildd/glib2.0-2.32.3/./glib/gmain.c:3340
(gdb) list
1296// Handle per-instance dynamic event tables first
1297if ( m_dynamicEvents && SearchDynamicEventTable(event) )
1298return true;
1299
1300// Then static per-class event tables
1301if ( GetEventHashTable().HandleEvent(event, this) )
1302return true;
1303}
1304
1305// Try going down the event handler chain
(gdb) p GetEventHashTable()
Cannot access memory at address 0x30050
(gdb) p this->'_vptr.wxObject'
$5 = (int (**)(void)) 0x3
(gdb) fr 5
#5 0x7fffd8915c58 in wxWindow::GTKProcessEvent (this=0x5686c60, event=...)
at ../src/gtk/window.cpp:1435
1435return GetEventHandler()->ProcessEvent(event);
(gdb) list
1430//
1431
1432bool wxWindowGTK::GTKProcessEvent(wxEvent& event) const
1433{
1434// nothing special at this level
1435return GetEventHandler()->ProcessEvent(event);
1436}
1437
1438int wxWindowGTK::GTKCallbackCommonPrologue(GdkEventAny *event) const
1439{
(gdb) p GetEventHandler()
$6 = (wxEvtHandler *) 0x0
(gdb) p this->m_eventHandler
$14 = (wxEvtHandler *) 0x0
Though as 'this' in deeper methods is not NULL I must assume that m_eventHandler
was cleared after calling the method. I do not know WX and python-wx and I
don't see anything interesting in gdb so I cannot help with this.
Also, to get this output I was forced to rebuild python-vtk, python-traits and
mayavi2 with crude hacks so I must wish the maintainer good luck with fixing
this bug.
--
WBR, wRAR
signature.asc
Description: Digital signature
