Bug#1070077: [Pkg-privacy-maintainers] Bug#1070077: ships files directly in /usr/onionprobe
Hi, Thanks for the report. On 24-04-29 16:19:21, Antoine Beaupre wrote: > Package: onionprobe > Version: 1.0.0+ds-2.1+deb12u1 > Severity: serious > > The Debian package shipped in bookworm right now changed the path to > the examples/ directory. It used to be: > > /usr/lib/python3/dist-packages/onionprobe/examples/tpo.py > > and now seems to be: > > /usr/onionprobe/examples/tpo.py > > Apart from the gratuitous change, this seems to be a violation of the > FHS policy, packages shouldn't ship their own stuff directly under > /usr like this... Indeed -- I wasn't aware, or probably forgot, that bookworm is affected. Given the severity, this might warrant a bookworm-pu, I guess? > I haven't checked in unstable to see if this is fixed. This was reported via #1025508 and fixed in unstable via 1.1.2+ds-1. Cheers, Georg
Bug#1056594: [Pkg-privacy-maintainers] Bug#1056594: mat2: test failure
Hi Paul, On 24-01-01 10:24:46, Paul Gevers wrote: > On 01-01-2024 09:50, Paul Gevers wrote: > > I'm going to NMU with this patch shortly. @gregor, any reason why > > you didn't the upload to DELAYED after you built it already? > > I have uploaded the attached changes. Thanks for the upload, although I would have appreciated communication about this upfront. Could you please push the relevant changes to git? Thanks & all the best, Georg
Bug#1038935: [DRE-maint] Bug#1038935: schleuder: fails to upgrade buster -> bullseye -> bookworm: NoMethodError: undefined method `preparable='
Hi, On 23-06-27 09:05:43, Georg Faerber wrote: > Regarding the test: I'll seek comments of the Ruby team before filling > the -pu; I believe the risk of regressions should be fairly low, as > arel, as described, has been part of activerecord since quite some > time. I'll test this especially in combination with schleuder, which > exposed this issue; to ease future maintenance and increase the > chances of spotting these issues earlier, ideally before release, I > added a "piuparts multi distro upgrade" test job to the Salsa CI [1]. I was on the road the last weeks, therefore I was only able to mail the team by now. Cheers, Georg
Bug#1040257: schleuder-cli does not work with Ruby >= 3.0.0
Hi, Thanks for your report. On 23-07-03 23:50:03, s3lph wrote: > [...] > > Upstream has fixed the issue on the main branch, but has not yet > created a new release containing the fix. The fix is quite small, > only two lines diff: > > https://0xacab.org/schleuder/schleuder-cli/-/commit/68754cf94cc2d9b2a400ff19d2e48a7ffa2ec1f2 > > With this patch applied manually, schleuder-cli works as expected: > > [...] Indeed, I forgot to pull this into Debian, apologies for that. That's fixed now via 0.1.0-5. bookworm-pu is tracked via #1040791. Cheers, Georg
Bug#1038935: schleuder: fails to upgrade buster -> bullseye -> bookworm: NoMethodError: undefined method `preparable='
Hi, On 23-06-26 10:27:37, Antoine Beaupré wrote: > Just to make sure, someone still is working on this to make sure it's > fixed in bookworm? I'll take care of it. > I guess the first step is to wait for the package to transition to > trixie and then do the -pu? I suspect it will be hard to test this in > trixie since you'd need to upgrade from buster to trixie, right? Right, it needs some more days. CI reported regressions, which I believe are unrelated to the issue and hand the fix. As of now it should migrate within five days. Regarding the test: I'll seek comments of the Ruby team before filling the -pu; I believe the risk of regressions should be fairly low, as arel, as described, has been part of activerecord since quite some time. I'll test this especially in combination with schleuder, which exposed this issue; to ease future maintenance and increase the chances of spotting these issues earlier, ideally before release, I added a "piuparts multi distro upgrade" test job to the Salsa CI [1]. I'll keep this bug updated. Cheers, Georg [1] https://salsa.debian.org/ruby-team/schleuder/-/commit/08fd9a91a938346f5cad3cf216f8225b6f6cdd0e
Bug#1036950: schleuder: fails to upgrade from 'buster': insufficient dependency on ruby-activerecord (>= 2:6)
Hi, On 23-06-23 20:14:59, Georg Faerber wrote: > Unfortunately, up until now, there wasn't a proposed update targeting > bullseye. > > Andreas, how do you want to proceed? Do you have any spare cycles to > handle this? This would be great -- but please don't hesitate to tell me > if that's not the case, if so, I'll take over. The pu targeting bullseye is now tracked via #1039020. Cheers, Georg
Bug#1038935: schleuder: fails to upgrade buster -> bullseye -> bookworm: NoMethodError: undefined method `preparable='
Hi, On 23-06-24 14:58:21, Andreas Beckmann wrote: > Shouldn't these conflicts rather be in ruby-activerecord? Yes, I agree, that's the correct place. > As I understand the history, arel has been merged into activerecord (5 years > ago, probably version 6.0.x) and the "old" arel 9 is no longer compatible > with current activerecord 6.1.x. This is probably unrelated to schleuder > (which only exposes the bug). That's my understanding as well. > Interestingly this didn't happen on buster->bullseye upgrades, but perhaps > arel 9 was still compatible with activerecord 6.0.x. Yeah, I wondered about this also, but I'm unsure why is that, so far. > Should ruby-arel be RM:ed? > Note: one reverse build dependency > # Broken Build-Depends: > ruby-premailer-rails: ruby-arel Yes -- I sent a mail about this to the Ruby team, see [1] for details. > I'll give it a try... yes, the conflict against ruby-arel fixes the > upgrade path. Great, thanks. So, given the above, I believe this bug should be reassigned to ruby-activerecord, and schleuder should be marked as affected? Also, I guess, as this issue is not specific to schleuder, probably more packages which rely on ruby-activerecord are affected. I'll prepare a ruby-activerecord proposed-update targeting bookworm. Cheers, Georg [1] https://lists.debian.org/debian-ruby/2023/06/msg4.html
Bug#1038935: schleuder: fails to upgrade buster -> bullseye -> bookworm: NoMethodError: undefined method `preparable='
Control: tag -1 + patch Hi, Thanks for the report! On 23-06-23 11:20:28, Andreas Beckmann wrote: > Package: schleuder > > during a test with piuparts I noticed your package fails to upgrade > from 'buster' to 'bullseye' to 'bookworm'. > It installed fine in 'buster', and upgraded to 'bullseye' > successfully, but then the upgrade to 'bookworm' failed. I believe that's caused by ruby-arel, the attached patches fix the issue in my tests. Andreas, are you able to test these in your environment? All the best, Georg >From 45bc5cfff9adbacef1174d6bb9cd49ba8a90d860 Mon Sep 17 00:00:00 2001 From: Georg Faerber Date: Sat, 24 Jun 2023 00:14:47 + Subject: [PATCH 1/2] debian/control: add Conflicts: ruby-arel --- debian/control | 1 + 1 file changed, 1 insertion(+) diff --git a/debian/control b/debian/control index 0f08e89..80a6f0c 100644 --- a/debian/control +++ b/debian/control @@ -32,6 +32,7 @@ Rules-Requires-Root: no Package: schleuder Architecture: all +Conflicts: ruby-arel, Depends: adduser, cron | cron-daemon, default-mta | postfix | mail-transport-agent, -- 2.30.2 >From 009d8af740408deccafd477bbbeaf8eaa6d54ec1 Mon Sep 17 00:00:00 2001 From: Georg Faerber Date: Sat, 24 Jun 2023 00:15:10 + Subject: [PATCH 2/2] debian/changelog: Debian release 4.0.3-8 --- debian/changelog | 9 + 1 file changed, 9 insertions(+) diff --git a/debian/changelog b/debian/changelog index edb2aa8..9bda664 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,12 @@ +schleuder (4.0.3-8) unstable; urgency=medium + + * debian/control: +- Declare that schleuder conflicts with ruby-arel. Before, database + migration failed during an upgrade, if ruby-arel was installed. + (Closes: #1038935) + + -- Georg Faerber Sat, 24 Jun 2023 00:05:14 + + schleuder (4.0.3-7) unstable; urgency=medium * Team upload -- 2.30.2
Bug#1036950: schleuder: fails to upgrade from 'buster': insufficient dependency on ruby-activerecord (>= 2:6)
Control: tag -1 + confirmed bullseye Control: X-Debbugs-CC: gitcom...@henk.geekmail.org Hi, Thanks for reporting this, and sorry for my delay in answering: On 23-06-23 09:34:13, Andreas Beckmann wrote: > Followup-For: Bug #1036950 > Control: tag -1 patch > Control: retitle -1 schleuder: fails to upgrade from 'buster': insufficient > dependency on ruby-activerecord (>= 2:6) > > I'm currently testing the attached patch ... This makes sense -- thanks a lot. Actually, Hendrik Jäger (Cc:ed) reported this issue and provided a patch [1], which was uploaded to unstable on 2022/12/26 via 4.0.3-7. After a review of the patch, I also noticed this only targeted Build-Depends, but not Depends. Unfortunately, up until now, there wasn't a proposed update targeting bullseye. Andreas, how do you want to proceed? Do you have any spare cycles to handle this? This would be great -- but please don't hesitate to tell me if that's not the case, if so, I'll take over. Also, another, related question, looking at #1038935, which will require an update targeting bookworm: I assume, as Debian, qua definition, only supports upgrades from one release to the next, fixing the ruby-activerecord issue in bullseye is sufficient? All the best, Georg [1] https://salsa.debian.org/ruby-team/schleuder/-/commit/307f8f5e4125dec9d3a9b2bce5a721394c9657fa
Bug#1021732: [Pkg-privacy-maintainers] Bug#1021732: Bug#1021732: libimage-exiftool-perl breaks mat2 autopkgtest: 'ColorProfiles' not found in ...
Hi nodens, On 22-10-25 09:16:29, Clément Hermann wrote: > Do you mind if I cherry-pick the upstream fix and upload today ? > This is blocking the perl 5.36 transition. I do not, please do, and thanks in advance. Please push your changes, including the tag. Cheers, Georg
Bug#1019682: [DRE-maint] Bug#1019682: Bug#1019682: schleuder: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect(error).to be_empty
Hi, After further debugging, I've now got the following backtrace: a bounce message is received :85:in `require': cannot load such file -- charlock_holmes (LoadError) from :85:in `require' from /<>/lib/schleuder/cli.rb:4:in `' from :85:in `require' from :85:in `require' from bin/schleuder:12:in `' from bounce example However, the following works as expected # ruby -v -e "require 'charlock_holmes'; puts CharlockHolmes::VERSION" ruby 3.1.2p20 (2022-04-12 revision 4491bb740a) [x86_64-linux-gnu] 0.7.7 so I'm still at loss. Cheers, Georg
Bug#1019682: [DRE-maint] Bug#1019682: schleuder: FTBFS with ruby3.1: ERROR: Test "ruby3.1" failed: Failure/Error: expect(error).to be_empty
Control: tags -1 + help Hi Antonio, all, Thanks for your report. I had a look, and I'm able to reproduce locally if building the package, although so far I haven't been able to find out what is causing this. I would be happy if someone is able to support me in debugging this. Looking at [1], which fails in the same way, I noticed: Ignoring bcrypt-3.1.17 because its extensions are not built. Try: gem pristine bcrypt --version 3.1.17 Ignoring charlock_holmes-0.7.7 because its extensions are not built. Try: gem pristine charlock_holmes --version 0.7.7 Ignoring debug-1.4.0 because its extensions are not built. Try: gem pristine debug --version 1.4.0 Ignoring rbs-2.1.0 because its extensions are not built. Try: gem pristine rbs --version 2.1.0 Ignoring sdbm-1.0.0 because its extensions are not built. Try: gem pristine sdbm --version 1.0.0 Ignoring thin-1.8.0 because its extensions are not built. Try: gem pristine thin --version 1.8.0 Ignoring bcrypt-3.1.17 because its extensions are not built. Try: gem pristine bcrypt --version 3.1.17 Ignoring charlock_holmes-0.7.7 because its extensions are not built. Try: gem pristine charlock_holmes --version 0.7.7 Ignoring debug-1.4.0 because its extensions are not built. Try: gem pristine debug --version 1.4.0 Ignoring rbs-2.1.0 because its extensions are not built. Try: gem pristine rbs --version 2.1.0 Ignoring sdbm-1.0.0 because its extensions are not built. Try: gem pristine sdbm --version 1.0.0 Ignoring thin-1.8.0 because its extensions are not built. Try: gem pristine thin --version 1.8.0 Some of these are direct dependencies of Schleuder. I'm mentioning this, because some days ago, [2] reported different errors: Failure/Error: require 'thin' LoadError: cannot load such file -- thin To make all of this even more interesting: [3] reports no errors. I'm wondering if different build environments are of relevance here. Any clue, anyone? Thanks in advance, all the best, Georg [1] https://buildd.debian.org/status/fetch.php?pkg=schleuder=all=4.0.3-4.1=1666457954=0 [2] https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/schleuder.html [3] https://ci.debian.net/data/autopkgtest/unstable/amd64/s/schleuder/27432900/log.gz
Bug#1021732: [Pkg-privacy-maintainers] Bug#1021732: libimage-exiftool-perl breaks mat2 autopkgtest: 'ColorProfiles' not found in ...
Control: forwarded -1 https://0xacab.org/jvoisin/mat2/-/issues/178 Control: tags -1 + fixed-upstream upstream Hi Paul, On 22-10-13 19:52:35, Paul Gevers wrote: > With a recent upload of libimage-exiftool-perl the autopkgtest of mat2 > fails in testing when that autopkgtest is run with the binary packages > of libimage-exiftool-perl from unstable. Thanks for your report. Cheers, Georg
Bug#993350: xsane: Scanimage detects scanner but Xsane won't start it
Hi, after updating libsane1 yesterday xsane works as expected. Georg
Bug#1002418: [Pkg-privacy-maintainers] Bug#1002418: marked as done (mat2: FTBFS: AssertionError: 'TransparentColor' not found in {})
Hi Utkarsh, Thanks for your upload. Could you please push the changes you did to the git repo? Thanks, cheers, Georg
Bug#1002418: [Pkg-privacy-maintainers] Bug#1002418: marked as done (mat2: FTBFS: AssertionError: 'TransparentColor' not found in {})
Hi Utkarsh, Thanks for your upload. Could you please push the changes you did to the git repo? Thanks, cheers, Georg
Bug#1002622: schleuder: ActiveRecord >= 6.0 changes boolean serialization, makes existing mailing lists fail
Package: schleuder Version: 3.6.0-3 Severity: grave Justification: renders package unusable Forwarded: https://0xacab.org/schleuder/schleuder/-/issues/505 Tags: fixed-upstream Since ActiveRecord >= 6.0, the SQLite3 connection adapter relies on boolean serialization to use 1 and 0, but does not natively recognize 't' and 'f' as booleans were previously serialized. This change made existing mailing lists fail, after people upgraded buster to bullseye, due to the involved ActiveRecord version bump, as Schleuder isn't able anymore to fetch correct values from the database. Unfortunately, we missed this breaking change when bumping ActiveRecord to >= 6.0 recently. This caused quite some work upstream, but also in downstream environments and, last but not least, at the side of users. We should extend our CI to explicitly test, and ensure things work as expected, if running a Schleuder setup in real world. As of now, we don't ensure data provided by a user in Schleuder version x still works after upgrading to version y.
Bug#1002418: [Pkg-privacy-maintainers] Bug#1002418: mat2: FTBFS: AssertionError: 'TransparentColor' not found in {}
Control: affects -1 libimage-exiftool-perl Control: forwarded -1 https://0xacab.org/jvoisin/mat2/-/issues/162 -- Hi Lucas, On 21-12-22 09:13:25, Lucas Nussbaum wrote: > During a rebuild of all packages in sid, your package failed to build > on amd64. Thanks for reporting, the error is caused by libimage-exiftool-perl >= 12.37+dfsg-1. I've forwarded this upstream. Cheers, Georg
Bug#993350: xsane: Scanimage detects scanner but Xsane won't start it
Scanimage fails starting the scan, too. The result of "scanimage -d epson2:libusb:002:005 --format png -o /home/georg/unsinn.png" is "scanimage: sane_start: Operation not supported". Georg
Bug#980194: [Pkg-privacy-maintainers] Bug#980194: Bug#980194: mat2: autopkgtest regression in testing: AssertionError: ValueError not raised
Hi Paul, On 21-01-15 22:57:54, Georg Faerber wrote: > I'm wondering if this is related to the recent upload of media-types > [1]. > > This test [2], which installed media-types 1.0.1, was successful, > whereas the test [3], which installed media-types 1.1.0, wasn't. I've requested a test [1] in testing with media-types from unstable, which was successful. The problem seems a regression in media-types, which is fixed in media-types >= 3.0.0. Given this, is there anything else required from my side? Cheers, Georg [1] https://ci.debian.net/data/autopkgtest/testing/amd64/m/mat2/9735398/log.gz
Bug#980194: [Pkg-privacy-maintainers] Bug#980194: mat2: autopkgtest regression in testing: AssertionError: ValueError not raised
Hi Paul, Thanks for telling! On 21-01-15 22:09:18, Paul Gevers wrote: > With a very recent change in testing the autopkgtest of your package > started to fail. I copied some of the output at the bottom of this > report. Can you please investigate the situation and fix it? I'm wondering if this is related to the recent upload of media-types [1]. This test [2], which installed media-types 1.0.1, was successful, whereas the test [3], which installed media-types 1.1.0, wasn't. Cheers, Georg [1] https://tracker.debian.org/news/1208854/accepted-media-types-110-source-into-unstable/ [2] https://ci.debian.net/data/autopkgtest/testing/amd64/m/mat2/9452897/log.gz [3] https://ci.debian.net/data/autopkgtest/testing/amd64/m/mat2/9663226/log.gz
Bug#976270: [Pkg-puppet-devel] Bug#976270: Bug#976270: ruby-puppet-forge: autopkgtest/ftbfs with ruby-faraday-middleware 1.x
Hi, On 20-12-03 14:19:00, Pirate Praveen wrote: > Added Breaks, but we may need to request removal from testing to allow > ruby-faraday to migrate. I would like to keep it in testing, as it's a dependency of r10k. Cheers, Georg
Bug#975533: [Pkg-privacy-maintainers] Bug#975533: mat2's autopkg tests fail with Python 3.9
Hi nicoo, On 20-12-14 15:57:10, nicoo wrote: > There doesn't seem to be anyone else handling the mat2 RC bug (FTBFS & > autopkgtest failure) so I will do it. I'm well aware and will handle this accordingly once there is a new upstream release, which should happen soon. Cheers, Georg
Bug#961088: bug confirmed
Hi, I have the same problem with an HP Officejet 7310 AIO: sane-find-scanner reports: "found USB scanner (vendor=0x03f0 [HP], product=0x4211 [Officejet 7300 series]) at libusb:002:012" but "scanimage -L" fails: "No scanners were identified." Unfortunately, I wasn't able to downgrade to 3.20.3+dfsg0-2. There are (too) many dependencies, and I couldn't find the 3.20.3 packages on the Debian servers). A fix or a workaround would be very much appreciated. Regards and thanks for your efforts, HG
Bug#951225: marked as pending in schleuder
Control: tag -1 pending Hello, Bug #951225 in schleuder reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/schleuder/commit/033760b58aa9d2e8f6121fa5609a393e308c5aa4 debian/patches: Relax dependency on sqlite3 in gemspec Closes: #951225 (this message was generated automatically) -- Greetings https://bugs.debian.org/951225
Bug#949824: [DRE-maint] Bug#949824: schleuder: tests fail with ruby-sqlite 1.4.2-1
Control: Tags -1 + confirmed upstream Control: Forwarded -1 https://0xacab.org/schleuder/schleuder/issues/453 Hi, On 20-01-25 09:58:22, Antonio Terceiro wrote: > I'm about upload ruby-sqlite3 1.4.2-1, and schleuder now fails its > tests on the dependency resolution step. > > [...] > > I tried hacking it locally, and just changing ~> to >= makes it work, > and all the tests pass. Please consider making the dependency check > less strict. Thanks for reporting -- confirmed, will be fixed upstream. Cheers, Georg
Bug#949252: [Pkg-privacy-maintainers] Bug#949252: mat2: autopkgtest needs update for new version of libimage-exiftool-perl
Control: tags -1 + confirmed upstream Control: Forwarded -1 https://0xacab.org/jvoisin/mat2/issues/136 Hi Paul, On 20-01-18 22:09:54, Paul Gevers wrote: > With a recent upload of libimage-exiftool-perl the autopkgtest of mat2 > fails in testing when that autopkgtest is run with the binary packages > of libimage-exiftool-perl from unstable. > > [...] Thanks for reporting, confirmed. We'll fix this upstream. Cheers, Georg
Bug#939630: [DRE-maint] Bug#939630: schleuder: breaks testbed?
control: tags -1 confirmed pending Hi Gianfranco, Thanks for your report. On 19-09-07 08:16:22, Gianfranco Costamagna wrote: > looks like you are playing with /dev/random removing and symlinking it > again. > > This might break the test environment, so I would say we should > > 1) declare the test as breaks-testbed [1] > > or > > 2) stop doing that. > > I tried to remove that if statement in Ubuntu, and the testsuite ran > successfully everywhere, including armhf. > > I discovered that issue, because in armhf the rm was failing because > of "dev/random" busy issues. > > you can see my "ubuntu3" upload, and the various test results if you > want more information > http://autopkgtest.ubuntu.com/packages/s/schleuder/eoan/armhf Agreed -- I've just uploaded 3.4.0-4 which drops this workaround. Lets see how this goes, I'll update this bug soonish once there are some tests made. Cheers, Georg
Bug#921637: [DRE-maint] Bug#921637: FTBFS: /usr/lib/ruby/vendor_ruby/ronn/roff.rb:165:in `block_filter': undefined method
Control: tags + confirmed pending On 19-02-23 20:24:15, brian m. carlson wrote: > It would be great if we could get this patch into buster. [...] Upload, including the patch, upcoming in the next days. Cheers, Georg signature.asc Description: Digital signature
Bug#919072: schleuder: FTBFS in both buster and sid
Control: reopen -1 Control: found -1 3.3.0-7 Hi, I've just uploaded 3.3.0-7, which, three times in a row, built fine on my local machine prior to the upload. On 19-01-12 13:26:16, Santiago Vila wrote: > Failures: > > 1) user sends a plain text message from thunderbird being signed-inline > Failure/Error: expect(error).to be_empty >expected `"Error: A serious, unhandleable error happened. Please > contact the administrators of this system or service and provide them with > the following information:\n\ninvalid byte sequence in US-ASCII\n".empty?` to > return true, got false > # ./spec/schleuder/integration/send_plain_spec.rb:18:in `block (3 > levels) in ' > # ./spec/spec_helper.rb:47:in `block (3 levels) in ' > # ./spec/spec_helper.rb:46:in `block (2 levels) in ' > > [...] However, it seems, this error still happens (sometimes?) [1]. In any case: two done, one more to go.. :) Cheers, Georg [1] https://salsa.debian.org/ruby-team/schleuder/pipelines/35065 signature.asc Description: Digital signature
Bug#918569: Could not find 'activerecord' (~> 4.2) - did find: [activerecord-5.2.0]
Hi Pirate, On 19-01-07 19:13:39, Pirate Praveen wrote: > Currently rails 5.2 is in unstable and schleuder autopkgtest is > failing (it is causing a delay in rails 5 migration to buster). Please > fix it so we can get rails 5 into buster. I'm back from traveling, and just uploaded 3.3.0-7 containing a fix. Sorry that this took so long.. :( Cheers, Georg signature.asc Description: Digital signature
Bug#917303: Request for help with MariaDB 10.3 / libdbd-mysql-perl packaging
Hi Otto, it doesn't make sense to zero a pointer, if the container (or speaking of C: structure) is freed afterwards. The documentation clearly states, that a handle (which was previously freed by mysql_close() ) needs to be initialized again. The pull request fixes the perl test case, but it didn't fix perl itself, which still abuses internal members of the connector, which are considered to be opaque. (And being opaque is the goal for next major release). /Georg On Mon, Jan 7, 2019 at 8:40 PM Otto Kekäläinen wrote: > Hello! > > gregor herrmann kirjoitti pe 4. tammikuuta 2019 klo > 1.23: > >> On Thu, 03 Jan 2019 22:04:48 +0200, Otto Kekäläinen wrote: >> >> > Just checking: are you Georg or Gregor currently working on this >> > issue, and do you have any estimate when we could expect either a >> > patch to MariaDB Connector C or a new upload of DBD-mysql so this >> > issue would be resolved? >> >> I had a look at DBD::mysql and DBD::MariaDB but without any success. >> I hope that someone with a better understanding than me from the >> Debian perl Group can try and find a solution. >> >> I've now pinged the upstream issue at: >> https://github.com/perl5-dbi/DBD-mysql/issues/275 > > > Thanks Gregor for working with upstreams to fix this. Nice Eric Herman was > also involved ;) > > Georg Richter, I hope you can review > https://github.com/MariaDB/mariadb-connector-c/pull/95 shortly, thanks! > > >> -- Georg Richter, Senior Software Engineer MariaDB Corporation Ab
Bug#917303: Request for help with MariaDB 10.3 / libdbd-mysql-perl packaging
About the reconnect bug: Latest code is setting the reconnect flag correctly via mysql_options (instead of accessing internal member), so I need to debug why it's failing. /Georg On Fri, Dec 28, 2018 at 1:31 PM gregor herrmann wrote: > On Fri, 28 Dec 2018 11:27:04 +0200, Otto Kekäläinen wrote: > > > pe 28. jouluk. 2018 klo 11.09 Georg Richter (ge...@mariadb.com) > kirjoitti: > > > no clue about dbd-mysql - we reported several bugs (and sent > > > fixes), but didn't get feedback since more than a year. Why don't > > > you ship DBD-mariadb instead? > > Gregor Hermann, do you want to switch to DBD-mariadb instead? > > DBD-mariadb is in the archive since a couple of months: > https://tracker.debian.org/libdbd-mariadb-perl > > Unfortunately, it's not a 1:1 replacement for DBD-mysql and many user > will want to continue using the latter in their existing codebase. > > Georg, maybe you can give us pointers to the bugs and fixes you > mentioned above? > > > Cheers, > gregor > > -- > .''`. https://info.comodo.priv.at -- Debian Developer > https://www.debian.org > : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 > AA06 > `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation > Europe >`- NP: Penelope Swales: Turning Point > -- Georg Richter, Senior Software Engineer MariaDB Corporation Ab
Bug#917303: Request for help with MariaDB 10.3 / libdbd-mysql-perl packaging
Hi, the zerofill test fails, since dbd-mysql binds a buffer with buffer_length=1, so MariaDB Connector/C can't add leading zeros and just returns 1. Perl seems to retrieve the information from metadata after mysql_stmt_store_result() call. According to the documentation ( https://dev.mysql.com/doc/refman/8.0/en/mysql-stmt-attr-set.html) you have to call mysql_stmt_attr_set(stmt, STMT_ATTR_UPDATE_MAX_LENGTH, ) to force mysql_stmt_store_result to update the max_length value in metadata - however its not set and therefore Connector/C doesn't return expected value. The correct behavior would be to check the metadata after mysql_stmt_prepare() and calculate the buffer_size or to force Connector/C to calculate the size via STMT_ATTR_UPDATE_MAX_LENGTH. I would prefer the latter one, since in some cases metadata after prepare can't be calculated correctly, e.g. for a "SELECT ? FROM DUAL" /Georg On Fri, Dec 28, 2018 at 1:31 PM gregor herrmann wrote: > On Fri, 28 Dec 2018 11:27:04 +0200, Otto Kekäläinen wrote: > > > pe 28. jouluk. 2018 klo 11.09 Georg Richter (ge...@mariadb.com) > kirjoitti: > > > no clue about dbd-mysql - we reported several bugs (and sent > > > fixes), but didn't get feedback since more than a year. Why don't > > > you ship DBD-mariadb instead? > > Gregor Hermann, do you want to switch to DBD-mariadb instead? > > DBD-mariadb is in the archive since a couple of months: > https://tracker.debian.org/libdbd-mariadb-perl > > Unfortunately, it's not a 1:1 replacement for DBD-mysql and many user > will want to continue using the latter in their existing codebase. > > Georg, maybe you can give us pointers to the bugs and fixes you > mentioned above? > > > Cheers, > gregor > > -- > .''`. https://info.comodo.priv.at -- Debian Developer > https://www.debian.org > : :' : OpenPGP fingerprint D1E1 316E 93A7 60A8 104D 85FA BB3A 6801 8649 > AA06 > `. `' Member VIBE!AT & SPI Inc. -- Supporter Free Software Foundation > Europe >`- NP: Penelope Swales: Turning Point > -- Georg Richter, Senior Software Engineer MariaDB Corporation Ab
Bug#913843: [DRE-maint] Bug#913843: ruby-mail-gpg FTBFS with gpgme 1.12.0
Control: severity -1 important Will take care of this (non-critical) bug at the end of January; I'm currently on travel. Up until then, downgrading the severity to prevent autoremoval. Cheers, Georg signature.asc Description: Digital signature
Bug#916375: apache2: Segmentation fault when mod_perl.so is loaded
Thanks Niko, it seems that you where right regarding libmariadbclient18 ... downgrading libmariadbclient18 fixed the issue :-) dpkg -i libmariadbclient18_10.1.26-0+deb9u1_amd64.deb Niko Tyni wrote: On Thu, Dec 13, 2018 at 06:44:32PM +0100, h.thien wrote: Package: apache2 Version: 2.4.25-3+deb9u6 Severity: grave Tags: patch Justification: renders package unusable gdb> Thread 1 "/opt/otrs/bin/cgi-bi" received signal SIGSEGV, Segmentation fault. gdb> bt #0 0x7fffdcd290c7 in free_defaults () from /usr/lib/x86_64-linux-gnu/libmariadbclient.so.18 We are using unattended upgrades (security only), and we suspect that an automatic system update has installed a new Perl version that now causes these problems. Have you ruled out the MariaDB update? That one seems the most likely to have triggered this regression. https://www.debian.org/security/2018/dsa-4341 (Not sure how reliably you got the list of loaded shared libraries; you seem to be running the prefork mpm so presumably only some of your apache processes will have the libraries loaded by the actual Perl application.) -- Hans-Georg Thien | Software Engineer callas software GmbH | Schoenhauser Allee 6/7 | 10119 Berlin | Germany Tel +49.30.4439031-0 | Fax +49.30.4416402 | www.callassoftware.com Amtsgericht Charlottenburg, HRB 59615 Geschäftsführung: Olaf Drümmer, Ulrich Frotscher, Dietrich von Seggern
Bug#916375: question about your solution
Hi, we have already tried that too. But (to my surprise) no change regarding the SEGV problem. - Hans cyri...@bollu.be wrote: Hi, If you suspect perl 'security update, you might want to try reverting to the previous version: apt-get install libperl5.24=5.24.1-3+deb9u4 Br, Cyrille -- Hans-Georg Thien | Software Engineer callas software GmbH | Schoenhauser Allee 6/7 | 10119 Berlin | Germany Tel +49.30.4439031-0 | Fax +49.30.4416402 | www.callassoftware.com Amtsgericht Charlottenburg, HRB 59615 Geschäftsführung: Olaf Drümmer, Ulrich Frotscher, Dietrich von Seggern
Bug#910376: mat2: Incomplete debian/copyright?
Hi all, On 18-10-07 16:00:06, intrigeri wrote: > Georg Faerber: > > Currently, we don't ship the logo, but I'm unsure if this matters? > > We do ship the logo in the source package so it does matter :) Alright -- I'll fix this once the current state is clarified upstream, see the corresponding issue over there. Cheers, Georg signature.asc Description: Digital signature
Bug#910376: mat2: Incomplete debian/copyright?
Hi Chris, Thanks for reporting. On 18-10-05 17:31:50, Chris Lamb wrote: > I just ACCEPTed mat2 from NEW but noticed it was missing attribution > in debian/copyright for at least a certain "Marie Rose". > > This is in no way exhaustive so please check over the entire package > carefully and address these on your next upload. Currently, we don't ship the logo, but I'm unsure if this matters? Cheers, Georg signature.asc Description: Digital signature
Bug#890751: Bug #890751 in rake marked as pending
Control: tag -1 pending Hello, Bug #890751 in rake reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/rake/commit/ea933f4e55577f043d38bce87ffb02d31ca8fab4 debian/ruby-tests.rb: Ensure tests are working with ruby 2.5 This commit removes the call to the dropped option '-rubygems' in ruby 2.5, makes the run of the testsuite verbose, and, drops the fixed seed, again. This was introduced in 213d8513e32320b84584066069d0d78bc47f713f, but now fixed upstream. Closes: #890751 (this message was generated automatically) -- Greetings https://bugs.debian.org/890751
Bug#890751: Bug #890751 in rake marked as pending
Control: tag -1 pending Hello, Bug #890751 in rake reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below, and you can check the diff of the fix at: https://salsa.debian.org/ruby-team/rake/commit/ea933f4e55577f043d38bce87ffb02d31ca8fab4 debian/ruby-tests.rb: Ensure tests are working with ruby 2.5 This commit removes the call to the dropped option '-rubygems' in ruby 2.5, makes the run of the testsuite verbose, and, drops the fixed seed, again. This was introduced in 213d8513e32320b84584066069d0d78bc47f713f, but now fixed upstream. Closes: #890751 (this message was generated automatically) -- Greetings https://bugs.debian.org/890751
Bug#890751: rake FTBFS with Ruby 2.5: cannot load such file -- ubygems (LoadError)
I'll work on this today. Cheers, Georg signature.asc Description: Digital signature
Bug#892507: [DRE-maint] Bug#892507: ruby-sequel FTBFS with Ruby 2.5
On 18-03-09 23:13:27, Adrian Bunk wrote: > Source: ruby-sequel > Version: 4.37.0-1 > Severity: serious > Tags: buster sid I'll work on this today. Cheers, Georg signature.asc Description: Digital signature
Bug#888189: [DRE-maint] Bug#888189: ruby-innertube: FTBFS on ruby2.5: undefined method mock
On 18-01-23 20:31:56, Chris West (Faux) wrote: > This package fails to build against ruby2.5. Soon, there will be a > transition to ruby2.5, and this package will FTBFS in sid. Upstream seems rather dead, popcon lists 11 installations. @Héctor: You've tagged this help: Are you using it personally, or DSA? Cheers, Georg signature.asc Description: Digital signature
Bug#890954: closed by Michael Gilbert <mgilb...@debian.org> (Bug#890954: fixed in chromium-browser 65.0.3325.146-2)
Hi, I can confirm this works now. Thanks for the work, Michael! Cheers, Georg signature.asc Description: Digital signature
Bug#881041: gzip/gunzip: fails to preserve filename
Package: gzip Version: 1.6-5+b1 Severity: serious Tags: Security Dear Maintainer, say I will gzip a file named sample_name. As result I get a new packed file sample_name.gz. When gunzipping this file the result is a file named sample_name. That is the expected result and in no way surprising or objectionable. But when I rename sample_name.gz to disguised_name.gz and than gunzip it, the result is a file withe the new name disguised_name. The original filename will not be preserved. Even if I look into the file with gunzip -l, I will not see the original filename. This might be intentional behaviour, but it is somewhat surprising - and it might lead to dangerous results! In fact, this behaviour is currently actively exploited to bypass content checks on MTA's and deliver trojans via mail to their intended victims. The problem is, that other (un)zipping tools, e.g. file-roller or nearly each and every unzipping tool under Windows don't show the same behaviour as gunzip, but unzip the file to it's original filename. The scenario is as follows: a trojan horse named trojan.exe will be gzipped. The resulting file will be renamed trojan.pdf.gz and will then be sent via mail to some target address. The MTA uses e.g. Amavis to look into the attachment with gunzip -l, sees an obviously harmless filename trojan.pdf and let it pass. The recipient unzips the file, expects a pdf, but gets an executable, doubleclick... This scenario will not work with any other zipping tool than gzip! As said before, this behaviour might be intentional; even more, there might be scripts in the wild, which count on this behaviour and would be broken, if it is changed. But at least the list command gzip -l resp. gunzip -l should show the real content of the zipped file and not just the filename with the .gz stripped.
Bug#861744: torbrowser-launcher: Should not be part of Stretch
Hi Roger, Not the maintainer here, but: On 17-08-31 20:10:35, Roger Shimizu wrote: > Is it time to upload backports of 0.2.7-3 to stretch? No: Packages need to be first in testing, before going into -backports. > I'm also wondering why it didn't hit testing yet. Read this bug report for some reasons. Cheers, Georg signature.asc Description: Digital signature
Bug#867031: marked as pending
tag 867031 pending thanks Hello, Bug #867031 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: https://anonscm.debian.org/cgit/pkg-ruby-extras/schleuder.git/commit/?id=08774fe --- commit 08774fe9924e4f8d5339702adfbd424231fef10a Author: Georg Faerber <ge...@riseup.net> Date: Thu Jul 13 13:45:49 2017 +0200 debian/changelog: Debian release 3.1.2-1 diff --git a/debian/changelog b/debian/changelog index 2c7708e..1513498 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,21 @@ +schleuder (3.1.2-1) unstable; urgency=medium + + * New upstream release. + * debian/copyright: +- Bump years to include 2017. +- Fix upstream source location. + * debian/control: Bump required rake version to >= 12~. + * debian/schleuder.preinst: +- Check for existing schleuder < 3.0 data first, before doing the backup. +(Closes: #867031) +- Don't use 'echo' to inform the user about the data migration process, +but instead via a proper NEWS file. + * debian/NEWS: Add said file with notes on how to migrate schleuder < 3.0 +data. + * debian/patches/0003-bin-fix-require.patch: Refresh for 3.1.2-1. + + -- Georg Faerber <ge...@riseup.net> Thu, 13 Jul 2017 13:40:47 +0200 + schleuder (3.1.1-1) unstable; urgency=medium * New upstream release.
Bug#849308: wireguard: Wireguard should not transition to stable yet
Hi, I would like to see wireguard right now in buster. Even if the on-wire format should change in the future, it would be still worth it, IMHO. Buster is the 'testing' suite - so let's just do that: let's test and get this into testing. Sometimes testing breaks, which is expected, but most of the time it works. I doubt that there would be a major difference in this case. Thanks for consideration and your work, cheers, Georg signature.asc Description: Digital signature
Bug#867643: [DRE-maint] Bug#867643: schleuder: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect(output).to include("98769E8A1091F36BD88403ECF71A3F8412D83889 was fetched (new key)")
On 17-07-08 21:05:36, Lucas Nussbaum wrote: > On 08/07/17 at 19:37 +0200, Georg Faerber wrote: > > Unfortunately, I can't reproduce this locally. Besides the sbuild > > options used which are shown in the log file, is there a .sbuildrc in > > place, with non-default options? If so, could you share it? > > Have you tried diffing your log with mine? Not yet, but all the tests work for me. I strongly suspect gnupg2 / dirmngr to cause trouble, I'm however unsure, how to reproduce that. > > Additionally, I've got a question regarding the network configuration of > > the VM on which the build was run: At the moment of the build, were the > > only configured network interfaces localhost and / or loopback? > > no. Hm, alright. I've suspected [1] to apply here as well, but it seems there has to be a different problem. > Also, I've just tried on another machine (that has Internet access). In > that case the test suite hangs at: > > user sends a plain text message > from thunderbird > > Schleuder::ListBuilder That sounds like low entropy: Ensure that haveged is running or that the entropy pool is filled via some other technique / method. Cheers, Georg [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856152 signature.asc Description: Digital signature
Bug#867643: [DRE-maint] Bug#867643: schleuder: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect(output).to include("98769E8A1091F36BD88403ECF71A3F8412D83889 was fetched (new key)")
Hi, Unfortunately, I can't reproduce this locally. Besides the sbuild options used which are shown in the log file, is there a .sbuildrc in place, with non-default options? If so, could you share it? Additionally, I've got a question regarding the network configuration of the VM on which the build was run: At the moment of the build, were the only configured network interfaces localhost and / or loopback? Thanks, Georg signature.asc Description: Digital signature
Bug#867643: [DRE-maint] Bug#867643: schleuder: FTBFS: ERROR: Test "ruby2.3" failed: Failure/Error: expect(output).to include("98769E8A1091F36BD88403ECF71A3F8412D83889 was fetched (new key)")
Hi Lucas, Thanks for the report: On 17-07-08 08:28:30, Lucas Nussbaum wrote: > > [...] > > 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. Was a wrapper used, like pbuilder or sbuild? Thanks, Georg signature.asc Description: Digital signature
Bug#753993: lyx: SIGSEGV when saving a new LyX file resulting in data loss
The development of the 2.0.x series of LyX was closed with the release of 2.0.8.1. There will be no further bug fixes upstream, and I don't think it makese sense to try debian specific fixes. Unfortunately LyX 2.1.0 suffers from a more serious crash which is extremely difficult to reproduce, but has been seen by several people, see http://www.lyx.org/trac/ticket/9049. I doubt it has anything to do with this report, but I mention it for completeness. Thanks, Georg -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#663016: [synaptic] Segmentation fault after upgrade to 0.75.5
Hi, On 03/08/2012 09:16 AM, Michael Vogt wrote: syslog shows: Mar 8 01:31:18 linprofs-hgb kernel: [ 8440.806485] synaptic[7794]: segfault at 0 ip 0047ec41 sp 7fffab0cd3d0 error 4 in synaptic[40+b7000] Thanks for looking at it. Could you please run synpatic under gdb ? To do that, you need to install it first and then run: $ sudo gdb synaptic (gdb) run [wait for crash] (gdb) backtrace full and send me the output? here you are: GNU gdb (GDB) 7.4-debian Copyright (C) 2012 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type show copying and show warranty for details. This GDB was configured as x86_64-linux-gnu. For bug reporting instructions, please see: http://www.gnu.org/software/gdb/bugs/... Reading symbols from /usr/sbin/synaptic...(no debugging symbols found)...done. (gdb) run Starting program: /usr/sbin/synaptic [Thread debugging using libthread_db enabled] Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1. Program received signal SIGSEGV, Segmentation fault. 0x0047ec41 in ?? () (gdb) backtrace full #0 0x0047ec41 in ?? () No symbol table info available. #1 0x0047a7da in ?? () No symbol table info available. #2 0x0046c362 in ?? () No symbol table info available. #3 0x00417499 in ?? () No symbol table info available. #4 0x73323ead in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 No symbol table info available. #5 0x00419ef1 in ?? () No symbol table info available. #6 0x7fffe6f8 in ?? () No symbol table info available. #7 0x001c in ?? () No symbol table info available. #8 0x0001 in ?? () No symbol table info available. #9 0x7fffe925 in ?? () No symbol table info available. #10 0x in ?? () No symbol table info available. (gdb) -- hgb -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#663016: [synaptic] Segmentation fault after upgrade to 0.75.5
Hi Michael,
On 03/08/2012 09:43 AM, Michael Vogt wrote:
Thanks, unfortunately this is very little information :/
Would it be possible for you to do a debug build? It goes like this:
$ sudo apt-get build-dep synaptic
$ sudo apt-get source synaptic
$ cd synaptic-0.75.5
$ DEB_BUILD_OPTIONS=nostrip noopt dpkg-buildpackage
This should give you a deb package that contains more debug
information to help finding the crash with gdb.
I hope this helps (wrong quoting, I know *sigh*):
(gdb) run
Starting program: /usr/sbin/synaptic
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
Program received signal SIGSEGV, Segmentation fault.
0x0047ec41 in RPackageViewOrigin::addPackage (this=0x776e80,
package=0xeaffc0) at rpackageview.cc:614
614 if(strcmp(VF.File().Archive(), now) == 0)
(gdb) backtrace full
#0 0x0047ec41 in RPackageViewOrigin::addPackage (this=0x776e80,
package=0xeaffc0) at rpackageview.cc:614
VF = {pkgCache::IteratorpkgCache::VerFile,
pkgCache::VerFileIterator = {std::iteratorstd::forward_iterator_tag,
pkgCache::VerFile, long, pkgCache::VerFile*, pkgCache::VerFile = {No data
fields}, _vptr.Iterator = 0x49ed90, S = 0x7fffed8514f8,
Owner = 0x943c00}, No data fields}
prefix = {static npos = optimized out,
_M_dataplus = {std::allocatorchar =
{__gnu_cxx::new_allocatorchar = {No data fields}, No data fields},
_M_p = 0x186b9c8 Not automatic: }}
origin_url = {static npos = optimized out,
_M_dataplus = {std::allocatorchar =
{__gnu_cxx::new_allocatorchar = {No data fields}, No data fields},
_M_p = 0x1866298 ftp.debian.nl}}
subview = {static npos = optimized out,
_M_dataplus = {std::allocatorchar =
{__gnu_cxx::new_allocatorchar = {No data fields}, No data fields},
_M_p = 0x187e6e8 Not automatic: unstable(ftp.debian.nl)}}
suite = {static npos = optimized out,
_M_dataplus = {std::allocatorchar =
{__gnu_cxx::new_allocatorchar = {No data fields}, No data fields},
_M_p = 0x1867378 unstable}}
Ver = {pkgCache::IteratorpkgCache::Version, pkgCache::VerIterator
= {std::iteratorstd::forward_iterator_tag, pkgCache::Version, long,
pkgCache::Version*, pkgCache::Version = {No data fields}, _vptr.Iterator
= 0x49edd0, S = 0x7fffed8462f0,
Owner = 0x943c00}, No data fields}
subview = {static npos = optimized out,
_M_dataplus = {std::allocatorchar =
{__gnu_cxx::new_allocatorchar = {No data fields}, No data fields},
_M_p = 0x18766c8 stable/main (ftp.debian.nl)}}
component = {static npos = optimized out,
_M_dataplus = {std::allocatorchar =
{__gnu_cxx::new_allocatorchar = {No data fields}, No data fields},
_M_p = 0x187eb68 main}}
origin_url = {static npos = optimized out,
_M_dataplus = {std::allocatorchar =
{__gnu_cxx::new_allocatorchar = {No data fields}, No data fields},
_M_p = 0x1864e78 ftp.debian.nl}}
origin_str = {static npos = optimized out,
_M_dataplus = {std::allocatorchar =
{__gnu_cxx::new_allocatorchar = {No data fields}, No data fields},
_M_p = 0x186c018 Debian}}
suite = {static npos = optimized out,
_M_dataplus = {std::allocatorchar =
{__gnu_cxx::new_allocatorchar = {No data fields}, No data fields},
_M_p = 0x1866028 stable}}
#1 0x0047a7da in RPackageView::refresh (this=0x776e80) at
rpackageview.cc:90
i = optimized out
#2 0x0046c362 in RPackageLister::openCache (this=0x776a00) at
rpackagelister.cc:421
---Type return to continue, or q return to quit---
i = optimized out
lock = optimized out
deps = 0x942400
pkgName = {static npos = optimized out,
_M_dataplus = {std::allocatorchar =
{__gnu_cxx::new_allocatorchar = {No data fields}, No data fields},
_M_p = 0x18636c8 libpng12-dev}}
count = 40613
firstRun = true
packageCount = optimized out
showAllMultiArch = false
pkgmap = {_M_t = {
_M_impl =
{std::allocatorstd::_Rb_tree_nodestd::pairstd::basic_stringchar,
std::char_traitschar, std::allocatorchar const, RPackage* =
{__gnu_cxx::new_allocatorstd::_Rb_tree_nodestd::pairstd::basic_stringchar,
std::char_traitschar, std::allocatorchar const, RPackage* = {No
data fields}, No data fields},
_M_key_compare = {std::binary_functionstd::basic_stringchar,
std::char_traitschar, std::allocatorchar , std::basic_stringchar,
std::char_traitschar, std::allocatorchar , bool = {No data fields},
No data fields}, _M_header = {
_M_color = std::_S_red, _M_parent = 0xb948b0, _M_left =
0xebe690, _M_right = 0xc5b430}, _M_node_count = 40613}}}
Bug#643310: mpqc cannot be started
Package: mpqc Version: 2.3.1-7 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, Whenever I try to start mpqc, whatever parameters I submit, mpqc 2.3.1-7 crashes with the same output to std.err: [cohg:03330] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file .../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 357 [cohg:03330] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file .../../../../../../orte/mca/ess/singleton/ess_singleton_module.c at line 230 [cohg:03330] [[INVALID],INVALID] ORTE_ERROR_LOG: A system-required executable either could not be found or was not executable by this user in file .../../../orte/runtime/orte_init.c at line 132 -- Sorry! You were supposed to get help about: orte_init:startup:internal-failure But I couldn't open the help file: /usr/share/openmpi/help-orte-runtime: No such file or directory. Sorry! -- -- Sorry! You were supposed to get help about: mpi_init:startup:internal-failure But I couldn't open the help file: /usr/share/openmpi/help-mpi-runtime: No such file or directory. Sorry! -- *** The MPI_Init_thread() function was called before MPI_INIT was invoked. *** This is disallowed by the MPI standard. *** Your MPI job will now abort. [cohg:3330] Abort before MPI_INIT completed successfully; not able to guarantee that all other processes were killed! I tried it on this amd64/testing-system, on an amd64/sid-system, and on an i386 /testing-system. Greetings, Georg -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.0.0-1-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages mpqc depends on: ii libblas3gf [libblas.so.3gf] 1.2.20110419-2 ii libc62.13-21 ii libgcc1 1:4.6.1-4 ii libgfortran3 4.6.1-4 ii liblapack3gf [liblapack.so.3gf] 3.3.1-1 ii libopenmpi1.31.4.3-2.1 ii libquadmath0 4.6.1-4 ii libsc-data 2.3.1-7 ii libsc7 2.3.1-7 ii libstdc++6 4.6.1-4 mpqc recommends no packages. Versions of packages mpqc suggests: ii mpqc-support 2.3.1-7 -- 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#643310: [Debichem-devel] Bug#643310: Bug#643310: mpqc cannot be started
Am Dienstag, den 27.09.2011, 11:17 +0200 schrieb Michael Banck: retitle 64331 mpqc: Missing Depends on mpi-default-bin thanks On Tue, Sep 27, 2011 at 11:09:16AM +0200, Michael Banck wrote: Erm, can you try installing openmpi-bin, if you have that one not installed, and let me know if that fixes it? Yeah, that seems to be the problem, sorry about that. Thanks for your report, Michael After installing openmpi-bin, mpqc works! Georg
Bug#634680: debian-installer: Installing base system stops with error message The bzcat ist not available on the system
Package: debian-installer Severity: critical Tags: d-i Justification: breaks the whole system Installing of the base system stops with the error message: Debootstrap-Fehler Es ist der folgende Fehler aufgetreten: The bzcat is not available on the System - Schauen Sie in /var/log/syslog oder auf die vierte Konsole bezüglich detaillierter Informationen The 4th console tells me: failed to execute '/lib/udev/edd_id' 'edd_id --export /dev/sda': No such file or directory 'edd_id --export /dev/sdb': No such file or directory After that, the installation process has to be exited. The system ist left unbootable from the hard disk. I tried //cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd on 2011-07-17 and //cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/amd64/iso-cd on 2011-07-17 and on 2011-07-19 This bug seems related to bugs #633678 and #633782. -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 2.6.39-2-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.utf8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#634680: Installing base system stops with error message The bzcat ist not available on the system
Hi, if you want a quick workaround, you can install LMDE = Linux Mint Debian Edition from www.linuxmint.com/download_lmde.php . You get a complete Debian testing system with a nice gnome (still 2) gui. Greetings, Georg
Bug#610210: plymouth 0.8.3-18 package does not include several files in /usr/lib/plymouth/
Package: plymouth Version: 0.8.3-18 Severity: grave Justification: renders package unusable Probably a minor packaging error: The plymouth 0.8.3-18 package does not include several files in /usr/lib/plymouth/ that were still included in version 0.8.3-9.1 (compare http://packages.debian.org/squeeze/i386/plymouth/filelist and http://packages.debian.org/sid/i386/plymouth/filelist). Depending on the selected theme, this results in modules not being available, which causes /usr/share/initramfs-tools/hooks/plymouth to fail. Please re-add all *.so module files to the curren package. Further, for a more robust solution, /usr/share/initramfs-tools/hooks/plymouth should gratiously handle the case of missing on incorrent module names (which afterall are supplied by non-core theme configuration files). Thansk! -- System Information: Debian Release: 6.0 APT prefers testing APT policy: (900, 'testing'), (300, 'unstable'), (200, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.36-trunk-686 (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/bash Versions of packages plymouth depends on: pn initramfs-tools none (no description available) ii libc6 2.11.2-7 Embedded GNU C Library: Shared lib plymouth recommends no packages. plymouth suggests no packages. -- Configuration Files: /etc/plymouth/plymouthd.conf changed: [Daemon] Theme=spacefun -- 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#600578: More descriptions about this problem
Hi, more reports about this problem can be seen within bug #601084 Regards -- hgb -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#586273: Fix for current flashplayer workaround package script on squeeze amd64
Hi all, on http://wiki.debian.org/FlashPlayer is desribed how to make an workaround package with the script provided by Bart Martens. The file libnss3-1d_3.12.6-2_i386.deb is no longer hosted on h ttp://ftp.debian.org/debian/pool/main/n/nss/ If you change the line 55 in file http://people.debian.org/~bartm/flashplugin-nonfree/ia32-libs-workaround-499043-squeeze.sh to libnss3-1d_3.12.6-3_i386.deb it works as requested. I attached a patchfile Best Regards Georg 55c55 http://$mirror/debian/pool/main/n/nss/libnss3-1d_3.12.6-2_i386.deb \ --- http://$mirror/debian/pool/main/n/nss/libnss3-1d_3.12.6-3_i386.deb \
Bug#588545: memtest86+: Update failed even when grub package exists
Package: memtest86+ Severity: normal I recently had this same problem, too (now solved by forcing the sid packages as mentioned in #586815 #550704 etc) In my system the dummy transitional package grub still exists, but even then memtest86+ (now?) suggests grub-pc | grub-legacy Since this is just a suggestion there should be no problem with it even in your config (suggestion there, too). I'd say this is a bug just triggered by memtest86+ since there were not that many kernel-updates recently and belongs to grub2. That's the joy of testing. Every year or so debian wants to show that testing != stable, it seems ;-) @maintainer: please reassign and merge with #586815 or so. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages memtest86+ depends on: ii debconf [debconf-2.0] 1.5.32 Debian configuration management sy memtest86+ recommends no packages. Versions of packages memtest86+ suggests: ii grub-pc 1.98+20100710-1 GRand Unified Bootloader, version pn hwtools none (no description available) pn kernel-patch-badram none (no description available) pn memtest86none (no description available) ii memtester4.1.3-1 A utility for testing the memory s ii mtools 4.0.12-1Tools for manipulating MSDOS files -- debconf information: shared/memtest86-run-lilo: false -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#550296: clamav .04 disabled
clamaav 0.94 is disabled now and therefore useless it should be updated or removed from stable distribution. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#535238: [usbmount] Partitions of USB-disk mounted to same mountpoint
Hi, On Fri, 2009-07-31 at 15:26 -0300, Rogério Brito wrote: [...] My USB-disk (not flash) has two partitions: 1. vfat 2. ext3. Both partitions are recognized and have no errors. Right. It is strange, but I had a problem quite similar to this one with some udev versions, but I can't reproduce the problem anymore (I'm using sid here, with, perhaps, some updated udev). Can you still reproduce things with udev + usbmount from sid? I am using sid already and there're no new versions of udev available other than 0.141-1 ... When the disk is connected, it is recognized and usbmount mounts them with correct FS types, but both partitions on the exact same location (/media/usb0): excerpt from /var/log/syslog Jul 1 00:55:06 sokrates usbmount[21916]: mountpoint /media/usb0 is available for /dev/sdb2 Jul 1 00:55:06 sokrates usbmount[21920]: mountpoint /media/usb0 is available for /dev/sdb1 end excerpt from /var/log/syslog It seems that usbmount is in a race when checking the available mountpoint and find it both times available ... it's just a matter of luck which partition is mounted first. This might lead to data loss, since a standard user might not recognize that there is such problem. Yes, it seems that there is some race condition somewhere and I will try to check with lockfile-progs what can be done. There're also no new version of lockfile-progs other than 0.1.13 ... I tried with usbmount 0.0.14-1 which I found in svn and the disk is mounted fine: excerpt from /var/log/syslog Aug 5 16:12:51 sokrates kernel: [1807358.676659] sdb: sdb1 sdb2 Aug 5 16:12:51 sokrates kernel: [1807358.723532] sd 16:0:0:0: [sdb] Attached SCSI disk Aug 5 16:12:51 sokrates kernel: [1807358.724131] sd 16:0:0:0: Attached scsi generic sg1 type 0 Aug 5 16:12:52 sokrates usbmount[5130]: executing command: mount -tvfat -osync,noexec,nodev,noatime /dev/sdb1 /media/usb0 Aug 5 16:12:52 sokrates usbmount[5130]: executing command: run-parts /etc/usbmount/mount.d Aug 5 16:12:57 sokrates usbmount[5129]: executing command: mount -text3 -osync,noexec,nodev,noatime /dev/sdb2 /media/usb1 Aug 5 16:12:57 sokrates kernel: [1807365.256657] kjournald starting. Commit interval 5 seconds Aug 5 16:12:57 sokrates kernel: [1807365.256657] EXT3 FS on sdb2, internal journal Aug 5 16:12:57 sokrates kernel: [1807365.256657] EXT3-fs: mounted filesystem with ordered data mode. Aug 5 16:12:57 sokrates usbmount[5129]: executing command: run-parts /etc/usbmount/mount.d end excerpt from /var/log/syslog I believe that 0.0.14-1 seem to work fine, since it doesn't try to lock (or doesn't show it); with this there is a difference of +/- 5 seconds between the two mounts, while 0.0.17 does it at the same second. Unfortunately I don't have enough time left (yet) to go deeper in this and check it; for now I'll pin usbmount to 0.0.14-1 ... Thanks for your bugreport, Rogério Brito. P.S.: Just out of curiosity, which program do you use to report bugs? I see it is different from what my reportbug program uses to list the packages dependencies... reportbug-ng 1.5 from sid. Regards -- hgb signature.asc Description: This is a digitally signed message part
Bug#535238: [usbmount] Partitions of USB-disk mounted to same mountpoint
Package: usbmount Version: 0.0.17 Severity: serious Hi there, I didn't use my USB-disk for two or three months now, but I know that I never had any trouble ... in the meantime usbmount 0.0.17 came out and I believe there is where the trouble starts. Unfortunately usbmount 0.0.16 isn't available anymore in debian repositories, so I cannot doublecheck if it works with that. My USB-disk (not flash) has two partitions: 1. vfat 2. ext3. Both partitions are recognized and have no errors. When the disk is connected, it is recognized and usbmount mounts them with correct FS types, but both partitions on the exact same location (/media/usb0): excerpt from /var/log/syslog Jul 1 00:55:05 sokrates kernel: [440465.213768] sdb: sdb1 sdb2 Jul 1 00:55:05 sokrates kernel: [440465.265885] sd 6:0:0:0: [sdb] Attached SCSI disk Jul 1 00:55:05 sokrates kernel: [440465.266074] sd 6:0:0:0: Attached scsi generic sg1 type 0 Jul 1 00:55:05 sokrates usbmount[21891]: trying to acquire lock /var/run/usbmount/.mount-dev-sdb.lock Jul 1 00:55:05 sokrates usbmount[21891]: acquired lock /var/run/usbmount/.mount-dev-sdb.lock Jul 1 00:55:05 sokrates usbmount[21891]: testing whether /dev/sdb is readable Jul 1 00:55:05 sokrates usbmount[21891]: /dev/sdb does not contain a filesystem or disklabel Jul 1 00:55:06 sokrates usbmount[21916]: trying to acquire lock /var/run/usbmount/.mount-dev-sdb2.lock Jul 1 00:55:06 sokrates usbmount[21920]: trying to acquire lock /var/run/usbmount/.mount-dev-sdb1.lock Jul 1 00:55:06 sokrates usbmount[21916]: acquired lock /var/run/usbmount/.mount-dev-sdb2.lock Jul 1 00:55:06 sokrates usbmount[21916]: testing whether /dev/sdb2 is readable Jul 1 00:55:06 sokrates usbmount[21920]: acquired lock /var/run/usbmount/.mount-dev-sdb1.lock Jul 1 00:55:06 sokrates usbmount[21920]: testing whether /dev/sdb1 is readable Jul 1 00:55:06 sokrates usbmount[21916]: /dev/sdb2 contains a filesystem or disklabel Jul 1 00:55:06 sokrates usbmount[21920]: /dev/sdb1 contains a filesystem or disklabel Jul 1 00:55:06 sokrates usbmount[21916]: /dev/sdb2 contains filesystem type ext3 Jul 1 00:55:06 sokrates usbmount[21916]: mountpoint /media/usb0 is available for /dev/sdb2 Jul 1 00:55:06 sokrates usbmount[21916]: executing command: mount -text3 -onoexec,nodev,noatime /dev/sdb2 /media/usb0 Jul 1 00:55:06 sokrates usbmount[21920]: /dev/sdb1 contains filesystem type vfat Jul 1 00:55:06 sokrates usbmount[21920]: mountpoint /media/usb0 is available for /dev/sdb1 Jul 1 00:55:06 sokrates usbmount[21920]: executing command: mount -tvfat -onoexec,nodev,noatime /dev/sdb1 /media/usb0 Jul 1 00:55:06 sokrates kernel: [440466.513924] kjournald starting. Commit interval 5 seconds Jul 1 00:55:06 sokrates kernel: [440466.519001] EXT3 FS on sdb2, internal journal Jul 1 00:55:06 sokrates kernel: [440466.519044] EXT3-fs: recovery complete. Jul 1 00:55:06 sokrates kernel: [440466.519260] EXT3-fs: mounted filesystem with ordered data mode. Jul 1 00:55:06 sokrates usbmount[21916]: executing command: run-parts /etc/usbmount/mount.d Jul 1 00:55:06 sokrates usbmount[21920]: executing command: run-parts /etc/usbmount/mount.d end excerpt from /var/log/syslog some commands $ mount | grep usb none on /proc/bus/usb type usbfs (rw,nosuid,nodev,devgid=1004,devmode=664) /dev/sdb1 on /media/usb0 type vfat (rw,noexec,nodev,noatime) /dev/sdb2 on /media/usb0 type ext3 (rw,noexec,nodev,noatime) # umount /dev/sdb1 umount: cannot umount /dev/sdb1 -- /dev/sdb2 is mounted over it on the same point. some commands It seems that usbmount is in a race when checking the available mountpoint and find it both times available ... it's just a matter of luck which partition is mounted first. This might lead to data loss, since a standard user might not recognize that there is such problem. Regards Hans-Georg Bork PS: It might be possible that the bug lies within udev which starts usbmount simultaneous. If this is true, please forward to them. --- System information. --- Architecture: i386 Kernel: Linux 2.6.26-3-sokrates.home Debian Release: squeeze/sid 500 unstablewww.debian-multimedia.org 500 unstableftp.de.debian.org 500 testing ftp.be.debian.org --- Package information. --- Depends (Version) | Installed =-+-=== udev | 0.141-1 lockfile-progs| 0.1.13 Package's Recommends field is empty. Package's Suggests field is empty. signature.asc Description: This is a digitally signed message part
Bug#527909: acx100-source: compilation stops on errors: too few arguments to function 'iwe_stream_add_event'
Package: acx100-source Version: 20070101-3 Severity: grave Justification: renders package unusable -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.29-2-amd64 (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 acx100-source depends on: ii debhelper 7.2.9 helper programs for debian/rules ii dpatch2.0.31 patch maintenance system for Debia ii module-assistant 0.11.1 tool to make module package creati acx100-source recommends no packages. acx100-source suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#524523: [eog] Latest version for i386 not installable
Package: eog Version: 2.24.3.1-1+b1 Severity: critical --- Please enter the report below this line. --- Hi, the latest version of eog is not installable since the package libgnome-desktop-2-7 does not exist ... the dependency should probably be changed into libgnome-desktop-2-11 or back to the previous libgnome-desktop-2. Thx HG --- System information. --- Architecture: i386 Kernel: Linux 2.6.26-3-sokrates.home Debian Release: squeeze/sid 500 unstablewww.debian-multimedia.org 500 unstableftp.nl.debian.org 500 unstableftp.de.debian.org 500 testing ftp.nl.debian.org --- Package information. --- Depends (Version) == libart-2.0-2 (= 2.3.18) libc6 (= 2.3.6-6~) libcairo2 (= 1.2.4) libdbus-glib-1-2 (= 0.78) libexempi3 (= 2.1.0) libexif12 libgconf2-4 (= 2.23.2) libglade2-0 (= 1:2.6.1) libglib2.0-0 (= 2.16.0) libgnome-desktop-2-7 libgnome2-0 (= 2.17.3) libgnomeui-0 (= 2.22.0) libgtk2.0-0 (= 2.14.0) libjpeg62 liblcms1 (= 1.15-1) libx11-6 libxml2 (= 2.6.27) python2.5 (= 2.5) zlib1g (= 1:1.2.2) gconf2 (= 2.10.1-2) gnome-icon-theme (= 2.19.1) shared-mime-info (= 0.20) signature.asc Description: This is a digitally signed message part
Bug#524314: Backtrace
+ '[' -z 0 ']' + STEPS_DIR=/lib/init/rw/splashy + SPL_UPD=/sbin/splashy_update + '[' -r /etc/default/splashy ']' + . /etc/default/splashy ++ CHVT_TTY=auto ++ ENABLE_INITRAMFS=1 ++ DEBUG=0 + log_use_splashy + '[' n = y ']' + pidof splashy + log_to_console log_end_msg 0 + '[' n '!=' y ']' + '[' no '!=' yes ']' ++ readlink /proc/self/fd/0 + stdin=/dev/pts/2 + '[' /dev/pts/2 '!=' /dev/pts/2 ']' + return 0 + '[' 73 ']' + '[' -x /usr/bin/tput ']' + printf '\r' + /usr/bin/tput hpa 73 + '[' 0 -eq 0 ']' + echo '[ OK ]' [ OK ] + '[' -x /sbin/splashy_update ']' + '[' '!' -d /lib/init/rw/splashy ']' + SPL_PRG=/lib/init/rw/splashy/2-progress + '[' -f /lib/init/rw/splashy/2-progress ']' + return 1 It seems as if the error is in line 341 of /etc/lsb-base-logging.sh. Splashy is looking for the file /lib/init/rw/splashy/2-progress which doesn't exist and returns 1, i.e. error, for the entire configuration process. Regards, Georg -- Georg Wittenburg http://page.mi.fu-berlin.de/~wittenbu/ signature.asc Description: This is a digitally signed message part.
Bug#485734: Unable to install synce-sync-engine
Subject: Unable to install synce-sync-engine
Package: synce-sync-engine
Version: 0.11-1
Severity: grave
Justification: renders package unusable
*** Please type your report below this line ***
# apt-get install synce-sync-engine
Paketlisten werden gelesen... Fertig
Abhängigkeitsbaum wird aufgebaut
Lese Status-Informationen ein... Fertig
Die folgenden NEUEN Pakete werden installiert:
synce-sync-engine
0 aktualisiert, 1 neu installiert, 0 zu entfernen und 0 nicht aktualisiert.
Es mÃŒssen noch 0B von 122kB an Archiven heruntergeladen werden.
Nach dieser Operation werden 700kB Plattenplatz zusÀtzlich benutzt.
Wähle vormals abgewähltes Paket synce-sync-engine.
(Lese Datenbank ... 217226 Dateien und Verzeichnisse sind derzeit
installiert.)
Entpacke synce-sync-engine (aus .../synce-sync-engine_0.11-1_all.deb) ...
INFO: using old version '/usr/bin/python2.3'
Richte synce-sync-engine ein (0.11-1) ...
INFO: using old version '/usr/bin/python2.3'
/usr/lib/python3.3/site-packages/SyncEngine/dtptserver.py:26: FutureWarning:
hex/oct constants sys.maxint will return positive values in Python 2.4 and
up
DUMMY_PTR = 0xDEADBEEF
/usr/lib/python2.3/site-packages/SyncEngine/dtptserver.py:258: FutureWarning:
hex/oct constants sys.maxint will return positive values in Python 2.4 and
up
self._send_reply(10, 0, 0xDEADBEEF, 0)
Compiling
/usr/lib/python2.3/site-packages/SyncEngine/formats/tzutils/recurrence.py ...
File
/usr/lib/python2.3/site-packages/SyncEngine/formats/tzutils/recurrence.py,
line 84
self.byMonth += list(int(x) for x in val.split(','))
^
SyntaxError: invalid syntax
Compiling
/usr/lib/python2.3/site-packages/SyncEngine/formats30/tzutils/recurrence.py ...
File
/usr/lib/python2.3/site-packages/SyncEngine/formats30/tzutils/recurrence.py,
line 122
self.byMonth += list(int(x) for x in rule.split(','))
^
SyntaxError: invalid syntax
Compiling /usr/lib/python2.3/site-packages/SyncEngine/kernel.py ...
File /usr/lib/python2.3/site-packages/SyncEngine/kernel.py, line 507
@dbus.service.method(DBUS_SYNCENGINE_IFACE, in_signature='',
out_signature='')
^
SyntaxError: invalid syntax
/usr/lib/python2.3/site-packages/SyncEngine/syncdb.py:72: FutureWarning:
hex/oct constants sys.maxint will return positive values in Python 2.4 and
up
return pas-id-%08X%08X % (random.randint(0, 0x),
/usr/lib/python2.3/site-packages/SyncEngine/syncdb.py:72: FutureWarning:
hex/oct constants sys.maxint will return positive values in Python 2.4 and
up
return pas-id-%08X%08X % (random.randint(0, 0x),
/usr/lib/python2.3/site-packages/SyncEngine/util.py:30: FutureWarning: hex/oct
constants sys.maxint will return positive values in Python 2.4 and up
d1 = random.randint(0, 0x)
pycentral: pycentral pkginstall: error byte-compiling files (58)
pycentral pkginstall: error byte-compiling files (58)
dpkg: Fehler beim Bearbeiten von synce-sync-engine (--configure):
Unterprozess post-installation script gab den Fehlerwert 1 zurÃŒck
Fehler traten auf beim Bearbeiten von:
synce-sync-engine
E: Sub-process /usr/bin/dpkg returned an error code (1)
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Kernel: Linux 2.6.24-1-686-bigmem (SMP w/1 CPU core)
Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored:
LC_ALL set to [EMAIL PROTECTED])
Shell: /bin/sh linked to /bin/bash
Versions of packages synce-sync-engine depends on:
ii odccm 0.11-4Daemon to keep a connection to Win
ii python2.5.2-1 An interactive high-level object-o
ii python-central0.6.7 register and build utility for Pyt
ii python-dateutil 1.4-1 powerful extensions to the standar
ii python-dbus 0.82.4-2 simple interprocess messaging syst
ii python-gobject2.14.1-6 Python bindings for the GObject li
ii python-libxml22.6.32.dfsg-2 Python bindings for the GNOME XML
ii python-libxslt1 1.1.24-1 Python bindings for libxslt1
ii python-rapi2 0.11.1-1 Make RAPI calls to a Windows Mobil
ii python-rra0.11.1-1 Library for syncing with Windows M
ii python-rtfcomp1.1-2 Library to read compressed RTF fil
ii python-tz 2008b-3 Python version of the Olson timezo
ii python-wbxml 0.1-1 WBXML parsing and encoding library
synce-sync-engine recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484503: tightvncserver: could not open default font 'fixed'
Package: tightvncserver Version: 1.3.9-4 Severity: grave Justification: renders package unusable The system does not start up, this bug exists for months now and I did *not* find a solution. I am no X guru, my other machine has exactly the same problem. I did not change x configuration etc., XWindows on the PC is o.k., I just cannot use vncserver. This also concerns other vnc packages (vnc4server) -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core) Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages tightvncserver depends on: ii libc6 2.7-12GNU C Library: Shared libraries ii libjpeg62 6b-14 The Independent JPEG Group's JPEG ii libx11-6 2:1.0.3-7 X11 client-side library ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii perl 5.10.0-10 Larry Wall's Practical Extraction ii x11-common 1:7.3+11 X Window System (X.Org) infrastruc ii xbase-clients 1:7.3+11 miscellaneous X clients - metapack ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime Versions of packages tightvncserver recommends: ii xfonts-base 1:1.0.0-5 standard fonts for X -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#484504: vnc4server: could not open default font fixed
Package: vnc4server Version: 4.1.1+X4.3.0-26 Severity: grave Justification: renders package unusable The system does not start up, this bug exists for months now and I did *not* find a solution. I am no X guru, my other machine has exactly the same problem. I did not change x configuration etc., XWindows on the PC is o.k., I just cannot use vncserver. This also concerns other vnc packages (vnc4server) Xvnc Free Edition 4.1.1 - built Apr 22 2008 08:22:52 Copyright (C) 2002-2005 RealVNC Ltd. See http://www.realvnc.com for information on VNC. Underlying X server release 4030, The XFree86 Project, Inc Wed Jun 4 14:52:59 2008 vncext: VNC extension running! vncext: Listening for VNC connections on port 5901 vncext: Listening for HTTP connections on port 5801 vncext: created VNC server for screen 0 Could not init font path element /usr/X11R6/lib/X11/fonts/Speedo/, removing from list! Could not init font path element /usr/X11R6/lib/X11/fonts/misc/, removing from list! Could not init font path element /usr/share/fonts/X11/misc/, removing from list! Fatal server error: could not open default font 'fixed' xsetroot: unable to open display 'voltaire:1' vncconfig: unable to open display voltaire:1 x-window-manager: cannot connect to X server voltaire:1 x-terminal-emulator: cannot connect to X server voltaire:1 -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.22-3-686 (SMP w/1 CPU core) Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) Shell: /bin/sh linked to /bin/bash Versions of packages vnc4server depends on: ii libc6 2.7-12GNU C Library: Shared libraries ii libgcc11:4.3.0-2 GCC support library ii libice62:1.0.4-1 X11 Inter-Client Exchange library ii libsm6 2:1.0.3-1+b1 X11 Session Management library ii libstdc++6 4.3.0-2 The GNU Standard C++ Library v3 ii libx11-6 2:1.0.3-7 X11 client-side library ii libxext6 2:1.0.4-1 X11 miscellaneous extension librar ii libxtst6 2:1.0.3-1 X11 Testing -- Resource extension ii x11-common 1:7.3+11 X Window System (X.Org) infrastruc ii xbase-clients 1:7.3+11 miscellaneous X clients - metapack ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime Versions of packages vnc4server recommends: ii xfonts-base 1:1.0.0-5 standard fonts for X -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#471609: libaunit-dev: possible impact of gnatgcc in debian/rules
Package: libaunit-dev Version: 1.03-2 Followup-For: Bug #471609 (Using gnat-4.3.) While forcing a dpkg-buildpackage -b of libaunit-1.03-2 I stumbled on /usr/bin/gnatgcc, which is not installed with gnat-4.3 (as ^gnat$ not installed). However, gnatgcc is used verbatim as a command in the rules file of libaunit-1.03, for making a shared library. As a workaround: if the link gnatgcc - /usr/bin/gcc-4.3 is present, aunit can be built. Still, installation isn't possible (presumably because of the conflicting dependences). -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.24-1-486 Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages libaunit-dev depends on: pn gnat-4.1 none (no description available) pn libaunit1.03 none (no description available) libaunit-dev recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#480426: [gosa] not useable on sid
Package: gosa Version: 2.5.15-2 Severity: serious --- Please enter the report below this line. --- After installation the setup wizard started normally, but at the installation check I get (among other warnings) this message: -- SAMBA password hash generation Error In order to use SAMBA 2/3 you've to install additional perl libraries. Take a look at mkntpasswd. GOsa will NOT run without fixing this. -- Checked mkntpasswd, perl needs Crypt::SmbHash (.deb package unknown to me) and cpan shows Crypt::SmbHash is up to date (0.12) There's nowhere any description which additional libraries are needed here. BTW: php5-snmp 5.2.5-3 is installed, but setup shows that it's not there. Regards -- hgb --- System information. --- Architecture: i386 Kernel: Linux 2.6.22.sokrates.home Debian Release: lenny/sid 500 unstablewww.debian-multimedia.org 500 unstableftp.de.debian.org --- Package information. --- Depends(Version) | Installed -+- php5 | 5.2.5-3 apache2 | exim4| OR mail-transport-agent | php5-gd | 5.2.5-3 php5-imap| 5.2.5-3 php5-ldap| 5.2.5-3 php5-mhash | 5.2.5-3 php5-mysql | 5.2.5-3 php5-imagick | OR imagemagick (= 5.4.4.5-1) | 7:6.3.7.9.dfsg1-2+b2 OR graphicsmagick-im-compat | fping| 2.4b2-to-ipv6-15 libcrypt-smbhash-perl| 0.12-2 smarty | 2.6.19-1 php5-recode | 5.2.5-3 wwwconfig-common | 0.1.1 smarty-gettext | 1.0b1-2 signature.asc Description: This is a digitally signed message part
Bug#455872: splashy: Fails to initialize, messes up loading other modules
On Tuesday 18 December 2007 16:31:09 Luis Mondesi wrote: If you have libdirectfb-0.9.25-x installed, can you please remove it? It seems that even though Splashy links against libdirectfb-1.0.x (from Sid), the binary tries to access the older version of the lib causing the -3 errors. Please report back ASAP as we are getting ready to do a bug fix release. Removing libdirectfb-0.9.25 definately helped. Splashy now generally works, although not perfectly: 1) After about 5% progress while booting, the boot process stalls (with Splashy visible) until F2 is pressed, at which point booting continues (Splashy still being displayed). 2) After logging into X, there are some small black spots near the top of the screen. This is X.org 1:7.3+8 with NVidia drivers 100.14.19-1 compiled from source. Regards, Georg -- Georg Wittenburg http://page.mi.fu-berlin.de/~wittenbu/ signature.asc Description: This is a digitally signed message part.
Bug#455872: splashy: Fails to initialize, messes up loading other modules
On Tuesday 18 December 2007 04:47:11 Luis Mondesi wrote: On Dec 12, 2007 3:13 AM, Georg Wittenburg [EMAIL PROTECTED] wrote: Package: splashy Version: 0.3.7-1 Severity: critical Justification: breaks the whole system Hi! After upgrading to splashy 0.3.7, splashy fails to start with error code -3 from splashy_start_splashy(). What is worse, several unrelated other modules fail to load afterwards, e.g. all sound drivers (snd_*) and the WLAN driver iwl4965. This effectively breaks sound and networking on my system. I haven't seen any suspicios messages in dmesg or syslog that would point to what exactly the problem is, but I could provide the output if necessary. As a workaround I removed splash from the kernel command line and the system works fine. Regards, Georg This looks like udev is not starting properly. Can you move /usr/share/initramfs-tools/scripts/init-top/splashy to /usr/share/initramfs-tools/scripts/init-bottom/z_splashy and redo your initrd? update-initramfs -u That should allow udev to start first and it should fix your problem. We will do a minor (bug fix) release shortly. If you can send us the result of this test it will be greatly appreciated. Regards, Unfortunately, even with the new initrd, the problem remains unchanged. In fact, on shutdown splashy segfaults (I assume it did that, too, prior to the changes). If the problem had to do with hardware initialization, I find it strange that splashy should crash when the system is going down. The exact message (as captured with `splashy test`) is segfault at 000c eip b7efb27d esp bfcab720 error 4 Two more bits of information: On boot, just before I get error code -3 from splashy_start_splashy(), it complains that it can't open /dev/fb0. Further, NetworkManager also gives me errors on shutdown, if splashy is enabled. It's quite a bit of text and I'm unsure how to capture that. Regards, Georg -- Georg Wittenburg http://page.mi.fu-berlin.de/~wittenbu/ signature.asc Description: This is a digitally signed message part.
Bug#455872: splashy: Fails to initialize, messes up loading other modules
Package: splashy Version: 0.3.7-1 Severity: critical Justification: breaks the whole system Hi! After upgrading to splashy 0.3.7, splashy fails to start with error code -3 from splashy_start_splashy(). What is worse, several unrelated other modules fail to load afterwards, e.g. all sound drivers (snd_*) and the WLAN driver iwl4965. This effectively breaks sound and networking on my system. I haven't seen any suspicios messages in dmesg or syslog that would point to what exactly the problem is, but I could provide the output if necessary. As a workaround I removed splash from the kernel command line and the system works fine. Regards, Georg -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (900, 'testing'), (300, 'unstable'), (200, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.23-1-686 (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/bash Versions of packages splashy depends on: ii initramfs-tools 0.90atools for generating an initramfs ii libc6 2.7-3GNU C Library: Shared libraries ii libdirectfb-1.0-0 1.0.1-5 direct frame buffer graphics - sha ii libgcc1 1:4.2.2-4GCC support library ii libglib2.0-02.14.3-1 The GLib library of C routines ii libmagic1 4.21-3 File type determination library us ii libsplashy1 0.3.7-1 Library to draw splash screen on b ii lsb-base3.1-24 Linux Standard Base 3.1 init scrip ii zlib1g 1:1.2.3.3.dfsg-6 compression library - runtime splashy recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#444428: libwnck-common replaces libwnck1, but does not provide it
Package: libwnck-common Version: 2.20.0-1 Severity: critical --- Please enter the report below this line. --- Package conflicts and replaces libwnck1 (= 0.10-1), but does not provide it, so that all packages depending on it are going to be deinstalled ore are broken. # apt-get install libwnck-common Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be REMOVED anjuta devhelp gnome-applets gnome-system-monitor libdevhelp-1-0 libwnck18 notification-daemon The following packages will be upgraded: libwnck-common 1 upgraded, 0 newly installed, 7 to remove and 1 not upgraded. Need to get 254kB of archives. After unpacking 11.5MB disk space will be freed. Do you want to continue [Y/n]? n Abort. Kind regards -- hgb --- System information. --- Architecture: i386 Kernel: Linux 2.6.22.sokrates.home Debian Release: lenny/sid 500 unstablewww.debian-multimedia.org 500 unstableftp.nl.debian.org --- Package information. --- Depends (Version) | Installed ===-+-=== | signature.asc Description: This is a digitally signed message part
Bug#442165: apt-spy: Destroys sources.list file
Hi Jeff, I believe that there is still a file called /etc/apt/sources.list.bak created by apt-spy; at least I have it on my system (sid with apt-spy 3.1-16). Fort the remainder I think you're by suggesting something like a tempfile in which all new source lines are written and only copied over (or appended) to sources.list (after a backup) if apt-spy was successful. Kind regards -- hgb -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#428967: [Pkg-lyx-devel] Bug#428967: Bug#428967: lyx: main window does not repaint with Qt 4.3
Am Freitag, 15. Juni 2007 12:06 schrieb Per Olofsson: Hi, On 2007-06-15 Laurent Bonnaud wrote: since I upgraded this system with Qt 4.3 from experimental, lyx does not work any longer. It opens its main window but is not able to draw it: $ lyx QWidget::repaint: Recursive repaint detected QWidget::repaint: Recursive repaint detected [...] This problem has been reported some time ago on the Mac (and fixed), search the LyX devel mailing list archives. Thank you for reporting this. We are going to upload LyX 1.5.0rc1 soon, I will check if the bug is still present in that version. I don't think that using rc1 it will make a difference. Maybe Qt 4.3 is not as binary compatible to 4.2 as supposed and recompiling against Qt 4.3 helps? Georg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#415636: Fixed upstream
Fixed upstream: http://www.lyx.org/trac/changeset/17506 Georg -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#405240: Similar error while upgrading to splashy 0.3
Hi! Not sure whether this is related, but during the upgrade to splashy 0.3 the same error is triggered and after the upgrade /lib/splashy still contains the some files as mentioned in this bug report. Regards, Georg -- Georg Wittenburg http://page.mi.fu-berlin.de/~wittenbu/ pgpkGnTF8aIuS.pgp Description: PGP signature
Bug#402148: Fwd: Re: Source for latex-xft-fonts?
Forgot to CC the bug tracker. -- Weitergeleitete Nachricht -- Subject: Re: Source for latex-xft-fonts? Date: Dienstag, 16. Januar 2007 20:59 From: Georg Baum [EMAIL PROTECTED] To: lyx-devel@lists.lyx.org Am Dienstag, 16. Januar 2007 20:36 schrieb John Levon: On Tue, Jan 16, 2007 at 08:11:22PM +0100, Per Olofsson wrote: There is a bug filed against the latex-xft-fonts Debian package about the lack of source code for it (http://bugs.debian.org/402148). This prevents the package from entering etch (the upcoming stable release of Debian). Apparently the fonts have been converted from the corresponding LaTeX .pfb fonts. Does anyone know how this was done? Is it possible to automate? I've entirely forgotten how I did it, but it definitely involved some manual fixing of the fonts. I used some popular open-source font editor, which I've also forgotten, and I had to fix some stuff up if I remember rightly. You probably used fontforge (formerly called PFAEdit IIRC). I have no idea what sources they're looking for. It's like complaining a .jpg doesn't have sources when it's a scanned in photo. No, it is rather like looking for the source of a jpeg that somebody created by manually modifying another one. This cannot be automated either. To me the ttf fonts look like a derived work of the original pfb versions. So, these could be considered as source, but the normal way of automated building from source would not work, so it would be pointless. AFAIK the original pfb fonts are under the LPPL, so I think the following would work: - The ttf files are considered as source technically. - The README documents that they were converted from the .pfb files and polished manually after that. - The README documents where to get the .pfb files (required by the LPPL). IANAL, but I see no reason why this would not work. Georg --- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390270: amaya: Amaya corrupts files when saving
Ok,
{1} Create a html file beginning with an xml statement, such as
?xml version=1.0 encoding=utf-8?
!DOCTYPE html PUBLIC -//W3C//DTD XHTML 1.1//EN
http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd;
html xmlns=http://www.w3.org/1999/xhtml;
head
title/title
meta http-equiv=Content-Type content=text/html; charset=utf-8 /
/head
body/body
/html
{2}
Open it with Amaya and change it, e. g. by inserting a blank character.
Save it.
{3}
Open the saved file with a text editor and you will see what I mean.
Greetings,
Georg
Am Samstag, den 02.12.2006, 18:53 + schrieb Regis Boudin:
Hi,
Sorry for the delay in replying. The bug arrived at the wrong time and
found itself sort of lost...
Anyway, I don't really understand what the problem is, or how to trigger
it. Do you have a way to reproduce the problem, so that I can either try
to fix the problem or check with upstream ?
Regards,
Regis
On Sat, 2006-09-30 at 08:40 +0200, Georg Colle wrote:
Package: amaya
Version: 9.51-2.1
Severity: grave
Justification: renders package unusable
In the doctype tag 'PUBLIC xyz \n ' is inserted (xyz means arbitrary
charcters and \n
stands for the line feed charcter). At the end of the document, after a
line containing
'', the html-tag and the whole part of the document included within it is
repeated.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-amd64
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Versions of packages amaya depends on:
ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries
ii libexpat1 1.95.8-3.3XML parsing C library -
runtime li
ii libfreetype6 2.2.1-5 FreeType 2 font engine, shared
lib
ii libgcc11:4.1.1-14GCC support library
ii libgl1-mesa-glx [libgl1] 6.5.1-0.1 A free implementation of the
OpenG
ii libglu1-mesa [libglu1] 6.5.1-0.1 The OpenGL utility library
(GLU)
ii libjpeg62 6b-13 The Independent JPEG Group's
JPEG
ii libpng12-0 1.2.8rel-5.2 PNG library - runtime
ii libraptor1 1.4.12-1 Raptor RDF parser and
serializer l
ii librdf01.0.4-1 Redland Resource Description
Frame
ii libstdc++6 4.1.1-14 The GNU Standard C++ Library v3
ii libwww-ssl05.4.0-11 The W3C-WWW library (SSL
support)
ii libwxbase2.6-0 2.6.3.2.1.5 wxBase library (runtime) -
non-GUI
ii libwxgtk2.6-0 2.6.3.2.1.5 wxWidgets Cross-platform C++
GUI t
ii ttf-freefont 20060501cvs-9 Freefont Serif, Sans and Mono
True
ii zlib1g 1:1.2.3-13compression library - runtime
amaya recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#390270: amaya: Amaya corrupts files when saving
Package: amaya Version: 9.51-2.1 Severity: grave Justification: renders package unusable In the doctype tag 'PUBLIC xyz \n ' is inserted (xyz means arbitrary charcters and \n stands for the line feed charcter). At the end of the document, after a line containing '', the html-tag and the whole part of the document included within it is repeated. -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing') Architecture: amd64 (x86_64) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-amd64 Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Versions of packages amaya depends on: ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries ii libexpat1 1.95.8-3.3XML parsing C library - runtime li ii libfreetype6 2.2.1-5 FreeType 2 font engine, shared lib ii libgcc11:4.1.1-14GCC support library ii libgl1-mesa-glx [libgl1] 6.5.1-0.1 A free implementation of the OpenG ii libglu1-mesa [libglu1] 6.5.1-0.1 The OpenGL utility library (GLU) ii libjpeg62 6b-13 The Independent JPEG Group's JPEG ii libpng12-0 1.2.8rel-5.2 PNG library - runtime ii libraptor1 1.4.12-1 Raptor RDF parser and serializer l ii librdf01.0.4-1 Redland Resource Description Frame ii libstdc++6 4.1.1-14 The GNU Standard C++ Library v3 ii libwww-ssl05.4.0-11 The W3C-WWW library (SSL support) ii libwxbase2.6-0 2.6.3.2.1.5 wxBase library (runtime) - non-GUI ii libwxgtk2.6-0 2.6.3.2.1.5 wxWidgets Cross-platform C++ GUI t ii ttf-freefont 20060501cvs-9 Freefont Serif, Sans and Mono True ii zlib1g 1:1.2.3-13compression library - runtime amaya recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#353583: kontact: libXft.so.2: undefined symbol: FT_GlyphSlot_Embolden
Hi! This bug was resolved after libfreetype6 2.1.10-1 entered testing and thus was updated on my system. Thanks again! Georg -- Georg Wittenburg http://page.mi.fu-berlin.de/~wittenbu/ pgpScbwOq3mdP.pgp Description: PGP signature
Bug#353572: Crash: libXft.so.2: undefined symbol: FT_GlyphSlot_Embolden
Hi! This bug was resolved after libfreetype6 2.1.10-1 entered testing and thus was updated on my system. Thanks again! Georg -- Georg Wittenburg http://page.mi.fu-berlin.de/~wittenbu/ pgp0gzYOP2Opg.pgp Description: PGP signature
Bug#353572: Crash: libXft.so.2: undefined symbol: FT_GlyphSlot_Embolden
Package: k3b Version: 0.12.12-1 Severity: grave Justification: renders package unusable Hi! When starting k3b I get this: [EMAIL PROTECTED]:~$ k3b [EMAIL PROTECTED]:~$ find: /dev/.static: Permission denied k3b: symbol lookup error: /usr/lib/libXft.so.2: undefined symbol: FT_GlyphSlot_Embolden This is possibly related to bug #316031. Thanks for looking into this. Georg -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900, 'testing'), (300, 'unstable'), (200, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages k3b depends on: ii cdparanoia3a9.8-11 An audio extraction tool for sampl ii cdrecord 4:2.01+01a03-5 command line CD writing tool ii kcontrol 4:3.5.1-1 control center for KDE ii kdebase-bin 4:3.5.1-1 core binaries for the KDE base mod ii kdelibs-data 4:3.5.1-2 core shared data for all KDE appli ii kdelibs4c2a 4:3.5.1-2 core libraries for all KDE applica ii libacl1 2.2.34-1 Access control list shared library ii libart-2.0-2 2.3.17-1 Library of functions for 2D graphi ii libattr1 2.4.25-1 Extended attribute shared library ii libaudio2 1.7-3 The Network Audio System (NAS). (s ii libc6 2.3.5-13 GNU C Library: Shared libraries an ii libdbus-1-2 0.60-5 simple interprocess messaging syst ii libdbus-qt-1-1c2 0.60-5 simple interprocess messaging syst ii libexpat1 1.95.8-3 XML parsing C library - runtime li ii libfam0 2.7.0-9Client library to control the FAM ii libfontconfig12.3.2-1.1 generic font configuration library ii libfreetype6 2.1.7-2.4 FreeType 2 font engine, shared lib ii libgcc1 1:4.0.2-8 GCC support library ii libhal1 0.5.6-4Hardware Abstraction Layer - share ii libice6 6.9.0.dfsg.1-4 Inter-Client Exchange library ii libidn11 0.5.18-1 GNU libidn library, implementation ii libjpeg62 6b-11 The Independent JPEG Group's JPEG ii libk3b2 0.12.12-1 The KDE cd burning application lib ii libmusicbrainz4c2a2.1.2-2Second generation incarnation of t ii libpng12-01.2.8rel-5 PNG library - runtime ii libqt3-mt 3:3.3.5-3 Qt GUI Library (Threaded runtime v ii libresmgr11.0-3 resource manager library ii libsm66.9.0.dfsg.1-4 X Window System Session Management ii libstdc++64.0.2-8The GNU Standard C++ Library v3 ii libx11-6 6.9.0.dfsg.1-4 X Window System protocol client li ii libxcursor1 1.1.3-1X cursor management library ii libxext6 6.9.0.dfsg.1-4 X Window System miscellaneous exte ii libxft2 2.1.8.2-3 FreeType-based font drawing librar ii libxi66.9.0.dfsg.1-4 X Window System Input extension li ii libxinerama1 6.9.0.dfsg.1-4 X Window System multi-head display ii libxrandr26.9.0.dfsg.1-4 X Window System Resize, Rotate and ii libxrender1 1:0.9.0.2-1X Rendering Extension client libra ii libxt66.9.0.dfsg.1-4 X Toolkit Intrinsics ii mkisofs 4:2.01+01a03-5 Creates ISO-9660 CD-ROM filesystem ii zlib1g1:1.2.3-9 compression library - runtime Versions of packages k3b recommends: ii cdrdao1:1.2.1-4 records CDs in Disk-At-Once (DAO) ii dvd+rw-tools 6.1-1 DVD+-RW/R tools ii kdebase-kio-plugins 4:3.5.1-1 core I/O slaves for KDE ii vcdimager 0.7.23-1 A VideoCD (VCD) image mastering an -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#353583: kontact: libXft.so.2: undefined symbol: FT_GlyphSlot_Embolden
Package: kontact Version: 4:3.5.1-1 Severity: grave Justification: renders package unusable Hi! When using the organizer part of Kontact, the application frequently crashes with this error in .xsession-errors: kontact: ERROR: Can't decrement change count. It already is 0. kontact: symbol lookup error: /usr/lib/libXft.so.2: undefined symbol: FT_GlyphSlot_Embolden This is possibly related to bug #316031 and similar to #353572. Thanks for looking into this. Georg -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (900, 'testing'), (300, 'unstable'), (200, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.15-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages kontact depends on: ii kdelibs4c2a 4:3.5.1-2 core libraries for all KDE applica ii libc6 2.3.5-13 GNU C Library: Shared libraries an ii libgcc1 1:4.0.2-8 GCC support library ii libkcal2b 4:3.5.1-1 KDE calendaring library ii libkdepim1a 4:3.5.1-1 KDE PIM library ii libkpimidentities14:3.5.1-1 KDE PIM user identity information ii libqt3-mt 3:3.3.5-3 Qt GUI Library (Threaded runtime v ii libstdc++64.0.2-8The GNU Standard C++ Library v3 Versions of packages kontact recommends: ii kaddressbook 4:3.5.1-1 KDE NG addressbook application ii kitchensync 4:3.5.1-1 Synchronization framework ii kmail 4:3.5.1-1 KDE Email client ii knode 4:3.5.1-1 KDE news reader ii knotes4:3.5.1-1 KDE sticky notes ii korganizer4:3.5.1-1 KDE personal organizer -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#353092: alicq: res variable not found
Package: alicq Severity: grave Justification: renders package unusable Apparently since ICQ protocol change last week, the tcl-icq library used in alicq does not work any more. It shows an error message like: can't read res: no such variable apparently on receiving a message. -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.8-wap Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages alicq depends on: pn bwidget Not found. ii tk8.4 8.4.9-1Tk toolkit for Tcl and X11, v8.4 - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#349316: Confirmed in kaddressbook-3.5.1-1
Hi! I'm seeing the same bug in kaddressbook-3.5.1-1. It occurs about every time I close Kontact. I don't have initng installed, so it's probably unrelated. Regards, Georg -- Georg Wittenburg http://page.mi.fu-berlin.de/~wittenbu/ pgp9ULZwDAVzj.pgp Description: PGP signature
Bug#324371: sam: symbol errno, version GLIBC_2.0 not defined ...
Package: sam Version: 4.3-18 Severity: grave Justification: renders package unusable When trying to start sam I get the following error: % sam /usr/bin/sam: relocation error: /usr/bin/sam: symbol errno, version GLIBC_2.0 not defined in file libc.so.6 with link time reference -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-1-k7 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages sam depends on: ii libc6 2.3.5-4GNU C Library: Shared libraries an ii xlibs 6.8.2.dfsg.1-5 X Window System client libraries m sam recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#317098: kmail: Same problem for me - segfault without any information
Package: kmail Version: 4:3.3.2-3 Followup-For: Bug #317098 -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (990, 'unstable'), (500, 'proposed-updates'), (500, 'testing'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.4.26 Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages kmail depends on: ii kdelibs4 4:3.3.2-7 KDE core libraries ii libc6 2.3.2.ds1-22 GNU C Library: Shared libraries an ii libgcc1 1:4.0.1-2 GCC support library ii libice6 6.8.2.dfsg.1-3 Inter-Client Exchange library ii libkcal2a 4:3.3.2-3 KDE calendaring library ii libkdenetwork24:3.3.2-3 KDE Network library ii libkdepim14:3.3.2-3 KDE PIM library ii libkleopatra0a4:3.3.2-3 KDE GnuPG interface libraries ii libkpimidentities14:3.3.2-3 KDE PIM user identity information ii libksieve04:3.3.2-3 KDE mail/news message filtering li ii libmimelib1a 4:3.3.2-3 KDE mime library ii libpng12-01.2.8rel-1 PNG library - runtime ii libqt3c102-mt 3:3.3.4-3 Qt GUI Library (Threaded runtime v ii libsm66.8.2.dfsg.1-3 X Window System Session Management ii libstdc++51:3.3.6-7 The GNU Standard C++ Library v3 ii libx11-6 6.8.2.dfsg.1-3 X Window System protocol client li ii libxext6 6.8.2.dfsg.1-3 X Window System miscellaneous exte ii perl 5.8.7-4Larry Wall's Practical Extraction ii xlibs 6.8.2.dfsg.1-3 X Window System client libraries m ii zlib1g1:1.2.2-9 compression library - runtime Versions of packages kmail recommends: ii kdebase-kio-plugins 4:3.3.2-1 KDE I/O Slaves ii kdepim-kio-plugins4:3.3.2-3 KDE pim I/O Slaves ii procmail 3.22-11Versatile e-mail processor -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#298723: gimp segfaults
Package: gimp
Version: 2.2.4-1
Severity: grave
Justification: renders package unusable
16:30:07 [EMAIL PROTECTED]:~$ rm -rf .gimp*
16:30:15 [EMAIL PROTECTED]:~$ gimp
Segmentation fault
16:30:35 [EMAIL PROTECTED]:~$ strace gimp
execve(/usr/bin/gimp, [gimp], [/* 33 vars */]) = 0
uname({sys=Linux, node=fgk, ...}) = 0
brk(0) = 0x8376000
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0 xb7fe9000
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/etc/ld.so.preload, O_RDONLY)= -1 ENOENT (No such file or directory)
open(/etc/ld.so.cache, O_RDONLY) = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=82089, ...}) = 0
old_mmap(NULL, 82089, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb7fd4000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/usr/lib/libgimpwidgets-2.0.so.0, O_RDONLY) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\340\354..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=909256, ...}) = 0
old_mmap(NULL, 908788, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0xb7ef6000
old_mmap(0xb7fd1000, 12288, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3,
0xdb 000) = 0xb7fd1000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/usr/lib/libgimpmodule-2.0.so.0, O_RDONLY) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\360\24..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=14564, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0 xb7ef5000
old_mmap(NULL, 17656, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0xb7ef
old_mmap(0xb7ef4000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3,
0x300 0) = 0xb7ef4000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/usr/lib/libgimpcolor-2.0.so.0, O_RDONLY) = 3
read(3, [EMAIL PROTECTED]..., 512) = 5 12
fstat64(3, {st_mode=S_IFREG|0644, st_size=35404, ...}) = 0
old_mmap(NULL, 34372, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0xb7ee7000
old_mmap(0xb7eef000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3,
0x800 0) = 0xb7eef000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/usr/lib/libgimpthumb-2.0.so.0, O_RDONLY) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\360!\0..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=28720, ...}) = 0
old_mmap(NULL, 31888, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0xb7edf000
old_mmap(0xb7ee6000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3,
0x600 0) = 0xb7ee6000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/usr/lib/libgimpmath-2.0.so.0, O_RDONLY) = 3
read(3, [EMAIL PROTECTED]..., 512) = 5 12
fstat64(3, {st_mode=S_IFREG|0644, st_size=16232, ...}) = 0
old_mmap(NULL, 19292, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0xb7eda000
old_mmap(0xb7ede000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3,
0x300 0) = 0xb7ede000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/usr/lib/libgimpbase-2.0.so.0, O_RDONLY) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\3208\0..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=53104, ...}) = 0
old_mmap(NULL, 56356, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0xb7ecc000
old_mmap(0xb7ed9000, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3,
0xc00 0) = 0xb7ed9000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/usr/lib/libgtk-x11-2.0.so.0, O_RDONLY) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0Pa\4\000..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=2993256, ...}) = 0
old_mmap(NULL, 3005184, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0xb7bee000
old_mmap(0xb7ec1000, 32768, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3,
0x2d 3000) = 0xb7ec1000
old_mmap(0xb7ec9000, 11008, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANON YMOUS, -1, 0) = 0xb7ec9000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or directory)
open(/usr/lib/libgdk-x11-2.0.so.0, O_RDONLY) = 3
read(3, \177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\240=\1..., 512) = 512
fstat64(3, {st_mode=S_IFREG|0644, st_size=453064, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0 xb7bed000
old_mmap(NULL, 456628, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0xb7b7d000
old_mmap(0xb7be8000, 20480, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED, 3,
0x6a 000) = 0xb7be8000
close(3)= 0
access(/etc/ld.so.nohwcap, F_OK) = -1 ENOENT (No such file or
Bug#290876: alsa-base still uninstallable on powerpc
Package: alsa-base Version: 1.0.7-2 Followup-For: Bug #290876 hi, unfortunately, alsa-base is still uninstallable on powerpc because the new alsa-utils ppc package is not in sid even tough the x86 one is (and alsa-base as well as alsa-utils in fact is installable on x86). Trying to install alsa-base on ppc fails with: The following packages have unmet dependencies: alsa-base: Depends: alsa-utils (= 1.0.8-1) but 1.0.7-2 is to be installed regards, Georg Kaindl -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: powerpc (ppc) Kernel: Linux 2.6.10-gck-apple-powerbook-g4-12-1333-gcc3.4.4-noprempt Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Versions of packages alsa-base depends on: ii alsa-utils1.0.7-2ALSA utilities ii debconf 1.4.42 Debian configuration management sy ii debianutils 2.11.2 Miscellaneous utilities specific t ii lsof 4.73-1 List open files. ii module-init-tools 3.2-pre1-2 tools for managing Linux kernel mo ii modutils 2.4.26-1.2 Linux module utilities -- debconf information: alsa-base/alsactl_store_on_shutdown: always autosave -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#292757: openoffice.org: uninstallable on powerpc
Package: openoffice.org Version: 1.1.2dfsg1-2 Severity: grave Justification: renders package unusable hi, openoffice.org has been kept back and is uninstallable on powerpc for quite some time now. Trying to install openoffice.org on ppc yields: The following packages have unmet dependencies: openoffice.org: Depends: openoffice.org-debian-files ( 1.1.2+1.1.3) but 1.1.2-5+1 is to be installed Depends: openoffice.org-bin ( 1.1.2+1.1.3) but 1.1.2dfsg1-3 is to be installed regards, Georg Kaindl -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: powerpc (ppc) Kernel: Linux 2.6.10-gck-apple-powerbook-g4-12-1333-gcc3.4.4-noprempt Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C) Versions of packages openoffice.org depends on: ii dictionaries-common [openof 0.24.5 Common utilities for spelling dict ii openoffice.org-bin 1.1.2dfsg1-3 OpenOffice.org office suite binary ii openoffice.org-debian-files 1.1.2-5+1Debian specific parts of OpenOffic ii openoffice.org-l10n-en [ope 1.1.2dfsg1-2 English (US) language package for ii ttf-opensymbol 1.1.3-4 The OpenSymbol TrueType font -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
