Bug#722307: [picard] Uninstallable because it depends on python2 (not in sid)
Package: picard Version: 1.2-2 Severity: serious The new version of picard in sid depends on python2 which is not available in sid. This was tested on amd64 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722283: [Pkg-javascript-devel] Bug#722283: libuv: FTBFS with test suite errors
On Mon, 09 Sep 2013 15:47:40 -0400 Aaron M. Ucko u...@debian.org wrote: Source: libuv Version: 0.10.8-0~exp2 Severity: serious Justification: fails to build from source Automated builds of libuv on Linux failed with test suite errors. (Builds for other platforms didn't even compile; I'll report that separately.) To wit: Thanks for the reports, both issues are already addressed in git (but I didn't know script(1), so I'll try to use it to pass test-tty). What I didn't notice is that I mistakenly uploaded ~exp2 to unstable, while it was intended for experimental. Libuv packaging is not yet mature and !linux still have to be tested, I'm going to fill the removal from unstable soon. Cheers, Luca -- .''`. | ~[ Luca BRUNO ~ (kaeso) ]~ : :' : | Email: lucab (AT) debian.org ~ Debian Developer `. `'` | GPG Key ID: 0x3BFB9FB3 ~ Free Software supporter `-| HAM-radio callsign: IZ1WGT ~ Networking sorcerer -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#713208: petsc: FTBFS: cp: cannot stat '/usr/share/automake-1.11/config.*': No such file or directory
On Mon, Sep 09, 2013 at 02:21:05PM +0200, Julien Cristau wrote: On Mon, Sep 9, 2013 at 14:09:17 +0200, Thomas Weber wrote: @@ -89,7 +93,7 @@ build-indep: build-arch: dh_quilt_patch echo Using MPI implementation $(PETSC_MPI) in directory $(PETSC_MPI_DIR) - cp -fp /usr/share/automake-1.13/config.* config/BuildSystem/config/packages/ + cp -fp $(AUTOMAKE_LIB_DIR)/config.* config/BuildSystem/config/packages/ You could just copy them from /usr/share/misc, which doesn't change. Okay, new patch attached. Thomas From 9af0f6fe749bcbd18c97f0e0a3407387d8e278f8 Mon Sep 17 00:00:00 2001 From: Thomas Weber twe...@debian.org Date: Mon, 9 Sep 2013 09:38:01 +0200 Subject: [PATCH] Make copying config.guess and config.sub independent of automake version Replace automake by autotools-dev for that. --- debian/control | 2 +- debian/rules | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/debian/control b/debian/control index da5096a..04e9838 100644 --- a/debian/control +++ b/debian/control @@ -4,7 +4,7 @@ Priority: extra Maintainer: Debian Science Maintainers debian-science-maintain...@lists.alioth.debian.org Uploaders: Adam C. Powell, IV hazel...@debian.org Standards-Version: 3.9.2 -Build-Depends: debhelper (= 7.0.50), quilt, python (= 2.2), gfortran, automake, +Build-Depends: debhelper (= 7.0.50), quilt, python (= 2.2), gfortran, autotools-dev, libx11-dev, mpi-default-dev, libblas-dev, liblapack-dev, libsuitesparse-dev (= 3.1.0-2), diff --git a/debian/rules b/debian/rules index 6046d46..908d150 100755 --- a/debian/rules +++ b/debian/rules @@ -89,7 +89,7 @@ build-indep: build-arch: dh_quilt_patch echo Using MPI implementation $(PETSC_MPI) in directory $(PETSC_MPI_DIR) - cp -fp /usr/share/automake-1.13/config.* config/BuildSystem/config/packages/ + cp -fp /usr/share/misc/config.* config/BuildSystem/config/packages/ if [ ! -f TAGS.backup ]; then cp -a TAGS TAGS.backup; fi PETSC_DIR=$(CURDIR) PETSC_ARCH=$(PETSC_ARCH)-c-debug \ ./config/configure.py --with-shared-libraries --with-debugging=1 \ -- 1.8.4.rc3
Bug#719665: Fwd: Re: Why does libgeotiff-dev depend on libtiff5-dev ?
Relevant discussion. It appears all packages need to transition to B-D on libtiff5-dev. Original Message Subject:Re: Why does libgeotiff-dev depend on libtiff5-dev ? Date: Sat, 15 Jun 2013 16:35:55 -0600 From: Gordon Haverland ghave...@materialisations.com Reply-To: ghave...@materialisations.com Organisation: Matter Realisations To: Alastair McKinstry mckins...@debian.org On June 15, 2013, you wrote: Hi, I'm investigating http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=711789 and wondering whats going on: Grads fails to build due to a B-D conflict, grads (= 2:2.0.1-1) build-depends on one of: - libgeotiff-dev (= 1.3.0+dfsg-3) libgeotiff-dev (= 1.3.0+dfsg-3) depends on one of: - libtiff5-dev (= 4.0.2-6) libtiff4-dev (= 3.9.6-11) and libtiff5-dev (= 4.0.2-6) conflict libgd-dev (= 2.1.0~rc2-1) depends on one of: - libtiff4-dev (= 3.9.6-11) libgd2-xpm-dev (= 2.1.0~rc2-1) depends on one of: - libgd-dev (= 2.1.0~rc2-1) grads (= 2:2.0.1-1) build-depends on one of: - libgd2-xpm-dev (= 2.1.0~rc2-1) - libgd-dev (= 2.1.0~rc2-1) I'm unfamiliar with the history of libtiff4 / tiff5, but libgd-dev depends on libtiff-dev ; can anyone answer: (1) why does libgeotiff-dev depend on libtiff5-dev? (2) why libtiff5-dev not provide the virtual libtiff-dev? Best regards Alastair Greetings. I am not a developer or a Debian maintainer. I have built stuff before. A little while ago (weeks), there was a problem with TeXLive that if people ran into a problem with a package not installing (I think the package was tex-common) in unstable, that a user could either downgrade libkapthsea by one version, or upgrade to all of the 2013 TeXLive. In the discussion of that bug, was a reference to this libtiff-4/5 dichotomy. I believe the tie in to TeX is involving ghostscript. As near as I can tell, the cause for the libtiff-4/5 dichotomy, is libjpeg related. Aparently libjpeg is not being developed by Independent JPEG group any more. Maybe. Debian was using JPEG-8. Some person has apparently taken over the title of Independent JPEG Group, and has started development on a JPEG-9. Somebody forked JPEG-8, and produced a faster library that is supposed more useful. Some distirbutions of Linux are following the faster fork, and some are following this IJG thing which may or may not be a continuation of JPEG-8. And someone asked questions about OpenJPEG. It kinds of sounds like the Debian maintainer wants to go JPEG-9 from IJG, and apparently Fedora is following the faster fork. One branch is tied to libtiff-4, and the other to libtiff-5. And that is as far as I got in investigating. And I may be completely wrong. Gord
Bug#710650: Bug#718767: transition: ocaml 4.00.1
Le 06/09/2013 10:14, Thomas Goirand a écrit : I wrote it many time to many people. Please don't just read 1.6 as new upstream release for XCP. That's unfortunately not the way it works. Upstream version for Debian and the one they do for CentOS are different, and just using upstream 1.6 doesn't cut it. It needs to be ported to Debian, and that's far from a trivial work (as Michael Tokarev wrote, it's not just replacing /usr/libexec/ into /usr/lib/ and the like). That is not the way it should work. Upstream version should not be specific to either Debian or CentOS. There should be only one version, and it is the job of each distribution (yours, here) to do the specialization work. If you can't, then arrange for its removal from testing. However, as I wrote it, it's going to happen, so please be patient about it. IMO, this shouldn't block any transition though. If the release team is reading: just let everything transition to testing, and remove the old version of XCP 1.3.2 in testing if that helps, plus add some blocking bugs so that the rest of Debian isn't affected by the (not finished) work on XCP 1.6 for Debian. There are reverse-dependencies so it cannot be easily removed from testing. And this situation IS blocking other people's work. And has been for (at least) one month. No, the package isn't neglected. It's simply more complicated than it seems. I'm currently dealing with upstream about it. While doing so, please make sure future versions are trivial to port to Debian. It should have been done during the initial packaging. I by the way don't mind if 1.3.2 is removed from testing, as we will need to package the next version anyway. Then, could you give the list of packages that should be removed from testing? Remember, testing should be self-contained, so it means remove all reverse dependencies as well. There are a few reverse-dependencies, but they all look somehow connected: nova, guest-templates, xcp-*... My take would be to remove (from testing) all of them. The problem for Nova is different. It's depending on sqlalchemy-migrate (python-migrate in Debian), which is blocked by Alembic, AFAIK. As for guest-templates, I don't see why it is affected. guest-templates build-depends on libxenapi-ocaml-dev, which is built by xen-api. I hope the above helps, And nothing has changed since... Cheers, -- Stéphane -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702705: vlock: sometimes does not exit therefore xautolock does not lock screen again after idle time
Hi Rodolfo, debian developers, * Gregor Zattler telegr...@gmx.net [2013-07-27; 10:47]: * Gregor Zattler telegr...@gmx.net [12. Jul. 2013]: * Rodolfo García Peñas k...@kix.es [12. Jul. 2013]: Probably the bug could be here: module new.c: 173 /* Work around stupid X11 bug: When switching immediately after the command 174* is entered, the enter button may get stuck. */ 175 if (getenv(DISPLAY) != NULL) 176 sleep(1); Probably the problem is not only related to the enter key. Can you reproduce the bug yet? Then, the best idea could be run vlock without the module new. Then we can see if the bug is in that module and work on it. Because we are in X11, run vlock -sa is not possible and we need the new module. Perhaps, one idea is increase the sleep time, for testing, something like: 176 sleep(5); [... 13 lines deleted ...] I used vlock -san since this last E-Mail with sleep (9): I realized only two hangs when the laptop was suspended and I woke it up. This is something I do often and it hanged only twice. Otherwise vlock functioned perfect -- with the exeption of having to wait for 9 secs. Which is still a security problem since I have to call vlock -san *after* the laptop wakes up from suspend (doesn't suspend while vlocked). Therefore the laptop is not protected for this waiting time after wakeup (by an attacker). Now I changed the sleeping time to 5 secs as you suggested and will proceede bisecting. I'll report back when I know how long the waiting time should be in order to function correctly. It worked perfectly with 2 seconds sleep time. Since September first I test it with 1.5 seconds sleep time and today it hanged for the first time. HTH, Gregor -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#702705: Info received (vlock: sometimes does not exit therefore xautolock does not lock screen again after idle time)
Hi Rodolfo, * Rodolfo García Peñas k...@kix.es [2013-07-12; 20:39]: could you try it without X11 (running the vlock -san in console) and see if the problem continues? If it continues, then probably we can run vlock -sa (without the n module) and try to see if the bug is in that module. Sorry, I missed this email of yours. I'll would try to do this but since the laptop is locked in most cases through xautolock, meaning I simply did not use it for a few minutes, it will take a while to have an encounter with a hanged vlock. But: Since we now know that vlock does not hang with at least 2 secs of sleeping but hangs with 1 second and even one time with 1.5 secs, isn't it safe to say that the problem is in the new module? Anyway I can try to do it from the console. Thanks for your patience and sorry again for missing your last email in this issue, Gregor -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: [package-stash] Name Package::Stash::qualify used only once (#8)
Processing commands for cont...@bugs.debian.org: Fixed 707528 0.36-1 Bug #707528 [libpackage-stash-perl] libpackage-stash-perl: Package::Stash::* used only once; causes FTBFS in other packages Marked as fixed in versions libpackage-stash-perl/0.36-1. thanks Stopping processing here. Please contact me if you need assistance. -- 707528: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707528 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707528: marked as done (libpackage-stash-perl: Package::Stash::* used only once; causes FTBFS in other packages)
Your message dated Tue, 10 Sep 2013 09:54:33 +0200 with message-id 20130910075433.ge144...@zedat.fu-berlin.de and subject line Re: [package-stash] Name Package::Stash::qualify used only once (#8) has caused the Debian Bug report #707528, regarding libpackage-stash-perl: Package::Stash::* used only once; causes FTBFS in other packages to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 707528: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707528 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libvideo-fourcc-info-perl Version: 1.005-1 Severity: serious Tags: jessie sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20130509 qa-ftbfs Justification: FTBFS on amd64 Hi, During a rebuild of all packages in sid, your package failed to build on amd64. Relevant part: make[1]: Entering directory `/«PKGBUILDDIR»' AUTOMATED_TESTING=1 dh_auto_test t/00signature.t . skipped: Set HAS_INTERNET to enable tests requiring Internet t/01manifest.t .. ok # Failed test 'no warnings' # at /usr/share/perl5/Test/NoWarnings.pm line 45. # There were 24 warning(s) # Previous test 1 'use Video::FourCC::Info;' # Name Package::Stash::qualify used only once: possible typo at /usr/share/perl5/Package/Stash/PP.pm line 198. # at /usr/share/perl5/Package/Stash/PP.pm line 198 # # -- # Previous test 1 'use Video::FourCC::Info;' # Name Package::Stash::has_symbol used only once: possible typo at /usr/share/perl5/Package/Stash/PP.pm line 198. # at /usr/share/perl5/Package/Stash/PP.pm line 198 # # -- # Previous test 1 'use Video::FourCC::Info;' # Name Package::Stash::BROKEN_ISA_ASSIGNMENT used only once: possible typo at /usr/share/perl5/Package/Stash/PP.pm line 198. # at /usr/share/perl5/Package/Stash/PP.pm line 198 # # -- # Previous test 1 'use Video::FourCC::Info;' # Name Package::Stash::BROKEN_GLOB_ASSIGNMENT used only once: possible typo at /usr/share/perl5/Package/Stash/PP.pm line 198. # at /usr/share/perl5/Package/Stash/PP.pm line 198 # # -- # Previous test 1 'use Video::FourCC::Info;' # Name Package::Stash::list_all_symbols used only once: possible typo at /usr/share/perl5/Package/Stash/PP.pm line 198. # at /usr/share/perl5/Package/Stash/PP.pm line 198 # # -- # Previous test 1 'use Video::FourCC::Info;' # Name Package::Stash::new used only once: possible typo at /usr/share/perl5/Package/Stash/PP.pm line 198. # at /usr/share/perl5/Package/Stash/PP.pm line 198 # # -- # Previous test 1 'use Video::FourCC::Info;' # Name Package::Stash::get_symbol used only once: possible typo at /usr/share/perl5/Package/Stash/PP.pm line 198. # at /usr/share/perl5/Package/Stash/PP.pm line 198 # # -- # Previous test 1 'use Video::FourCC::Info;' # Name Package::Stash::name used only once: possible typo at /usr/share/perl5/Package/Stash/PP.pm line 198. # at /usr/share/perl5/Package/Stash/PP.pm line 198 # # -- # Previous test 1 'use Video::FourCC::Info;' # Name Package::Stash::ungensym used only once: possible typo at /usr/share/perl5/Package/Stash/PP.pm line 198. # at /usr/share/perl5/Package/Stash/PP.pm line 198 # # -- # Previous test 1 'use Video::FourCC::Info;' # Name Package::Stash::confess used only once: possible typo at /usr/share/perl5/Package/Stash/PP.pm line 198. # at /usr/share/perl5/Package/Stash/PP.pm line 198 # # -- # Previous test 1 'use Video::FourCC::Info;' # Name Package::Stash::qualify_to_ref used only once: possible typo at /usr/share/perl5/Package/Stash/PP.pm line 198. # at /usr/share/perl5/Package/Stash/PP.pm line 198 # # -- # Previous test 1 'use Video::FourCC::Info;' # Name Package::Stash::BROKEN_SCALAR_INITIALIZATION used only once: possible typo at /usr/share/perl5/Package/Stash/PP.pm line 198. # at /usr/share/perl5/Package/Stash/PP.pm line 198 # # -- # Previous test 1 'use Video::FourCC::Info;' # Name Package::Stash::get_or_add_symbol used only once: possible typo at /usr/share/perl5/Package/Stash/PP.pm line 198. # at /usr/share/perl5/Package/Stash/PP.pm line 198 # # -- # Previous test 1 'use Video::FourCC::Info;' # Name Package::Stash::remove_symbol used only once: possible typo at /usr/share/perl5/Package/Stash/PP.pm line 198. # at /usr/share/perl5/Package/Stash/PP.pm line 198 # # -- # Previous test 1 'use Video::FourCC::Info;' #
Bug#704785: OGRE's FTBFS #713640 affects other packages
On Mon, 2013-09-09 at 18:24 +0100, Manuel A. Fernandez Montecelo wrote: I uploaded 1.8.0+dfsg1-6 today, modifying the pkg-config files to emit -lboost_system, can you please give it a try when available? That works as a work-around, the proper fix would be to boost though so I would appreciate if you could get it fixed there and then revert the workaround in ogre-1.8. I'm uploading funguloids now, thanks. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#719665: Fwd: Re: Why does libgeotiff-dev depend on libtiff5-dev ?
On Tue, Sep 10, 2013 at 08:06:54 +0100, Alastair McKinstry wrote: Relevant discussion. It appears all packages need to transition to B-D on libtiff5-dev. No, all packages need to b-d on libtiff-dev. Please don't encourage more libtiff5-dev usage. Cheers, Julien -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721903: Dependency problem
I think this might be because libgpgme11 v1.2 depended on gnupg whereas libgpgme11 v1.4 depends on gnupg2. mandos-client depends on gnupg. In initrd only gnupg files are included whereas at console both gnupg and gnupg2 files are available. Needs to be proved! Dick -- Dick Middleton d...@lingbrae.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: your mail
Processing commands for cont...@bugs.debian.org: forwarded 720794 https://rt.cpan.org/Ticket/Display.html?id=88537 Bug #720794 [src:prophet] prophet: FTBFS: test failures Set Bug forwarded-to-address to 'https://rt.cpan.org/Ticket/Display.html?id=88537'. -- Stopping processing here. Please contact me if you need assistance. -- 720794: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720794 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 3 errors): wesnoth bug triaging
Processing commands for cont...@bugs.debian.org:
# Known bug upstream; fixed in 1.10.7
forcemerge 722168 721616
Bug #722168 [wesnoth] Segfaults on startup
Unable to merge bugs because:
package of #721616 is 'wesnoth-1.10-core' not 'wesnoth'
Failed to forcibly merge 722168: Did not alter merged bugs
Debbugs::Control::set_merged('transcript', 'GLOB(0x1f8ab08)',
'requester', 'Vincent Cheng vincentc1...@gmail.com', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid',
'CACZd_tAA=pxsxw6oq2tjuh2z3b6-frphqazp4dxu0srta_n...@mail.gma...',
'request_subject', ...) called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 552
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 551
Debbugs::Control::Service::control_line('line', undef, 'clonebugs',
'HASH(0x1f0eab8)', 'limit', 'HASH(0x1f0e4a0)', 'common_control_options',
'ARRAY(0x1f0e4e8)', 'errors', ...) called at /usr/lib/debbugs/service line 474
tag 722168 + fixed-upstream
Failed to alter tags of Bug 722168: failed to get lock on
/org/bugs.debian.org/spool/lock/722168 -- Unable to lock
/org/bugs.debian.org/spool/lock/722168 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/722168 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 582.
Unable to lock /org/bugs.debian.org/spool/lock/722168 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 582.
Unable to lock /org/bugs.debian.org/spool/lock/722168 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 582.
Unable to lock /org/bugs.debian.org/spool/lock/722168 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 582.
Unable to lock /org/bugs.debian.org/spool/lock/722168 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 582.
Unable to lock /org/bugs.debian.org/spool/lock/722168 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 582.
Unable to lock /org/bugs.debian.org/spool/lock/722168 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 582.
Unable to lock /org/bugs.debian.org/spool/lock/722168 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 582.
Unable to lock /org/bugs.debian.org/spool/lock/722168 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 582. at
/usr/local/lib/site_perl/Debbugs/Common.pm line 600
Debbugs::Common::filelock('/org/bugs.debian.org/spool/lock/722168')
called at /usr/local/lib/site_perl/Debbugs/Status.pm line 213
Debbugs::Status::read_bug('bug', 722168, 'lock', 1) called at
/usr/local/lib/site_perl/Debbugs/Status.pm line 465
Debbugs::Status::lock_read_all_merged_bugs('bug', 722168) called at
/usr/local/lib/site_perl/Debbugs/Control.pm line 3671
Debbugs::Control::__begin_control('remove', 0, 'add', 1,
'request_replyto', 'Vincent Cheng vincentc1...@gmail.com', 'transcript',
'GLOB(0x1f8ab08)', 'bug', ...) called at
/usr/local/lib/site_perl/Debbugs/Control.pm line 627
Debbugs::Control::set_tag('transcript', 'GLOB(0x1f8ab08)', 'requester',
'Vincent Cheng vincentc1...@gmail.com', 'request_addr',
'cont...@bugs.debian.org', 'request_msgid',
'CACZd_tAA=pxsxw6oq2tjuh2z3b6-frphqazp4dxu0srta_n...@mail.gma...',
'request_subject', ...) called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 485
eval {...} called at
/usr/local/lib/site_perl/Debbugs/Control/Service.pm line 478
Debbugs::Control::Service::control_line('line', 'tag 722168 +
fixed-upstream', 'clonebugs', 'HASH(0x1f0eab8)', 'limit', 'HASH(0x1f0e4a0)',
'common_control_options', 'ARRAY(0x1f0e4e8)', 'errors', ...) called at
/usr/lib/debbugs/service line 474
forwarded 722168 https://gna.org/bugs/?20742
Failed to set the forwarded-to-address of 722168: failed to get lock on
/org/bugs.debian.org/spool/lock/722168 -- Unable to lock
/org/bugs.debian.org/spool/lock/722168 Resource temporarily unavailable.
Unable to lock /org/bugs.debian.org/spool/lock/722168 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 582.
Unable to lock /org/bugs.debian.org/spool/lock/722168 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 582.
Unable to lock /org/bugs.debian.org/spool/lock/722168 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 582.
Unable to lock /org/bugs.debian.org/spool/lock/722168 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 582.
Unable to lock /org/bugs.debian.org/spool/lock/722168 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 582.
Unable to lock /org/bugs.debian.org/spool/lock/722168 Resource temporarily
unavailable at /usr/local/lib/site_perl/Debbugs/Common.pm line 582.
Unable to lock
Bug#694143: [php-maint] Bug#694143: FTBFS against libav 9
Hi, On 9 September 2013 16:43, Moritz Mühlenhoff j...@inutil.org wrote: On Sat, Nov 24, 2012 at 11:46:02AM +0100, Ondřej Surý wrote: severity 694143 wishlist thank you We are in freeze, and the libav9 is not even in unstable, it's by no means an important bug. You might raise the severity once we have released and the transition is planned with release team. In the mean time libav9 was uploaded, could you please look into a fix? I had completely forgotten about this bug *sigh* Will try to give it a shot this week unless somebody beats me to it. Cheers, -- Raphael Geissert - Debian Developer www.debian.org - get.debian.net -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: wesnoth bug triaging, round 2
Processing commands for cont...@bugs.debian.org: # Known bug upstream; fixed in 1.10.7 reassign 722168 wesnoth-1.10-core 1:1.10.6-2+b1 Bug #722168 [wesnoth] Segfaults on startup Bug reassigned from package 'wesnoth' to 'wesnoth-1.10-core'. No longer marked as found in versions wesnoth-1.10/1:1.10.6-2. Ignoring request to alter fixed versions of bug #722168 to the same values previously set Bug #722168 [wesnoth-1.10-core] Segfaults on startup Marked as found in versions wesnoth-1.10/1:1.10.6-2. forcemerge 722168 721616 Bug #722168 [wesnoth-1.10-core] Segfaults on startup Bug #721616 [wesnoth-1.10-core] wesnoth: segmentation fault wesnoth when my first turn on a map starts Severity set to 'normal' from 'grave' Merged 721616 722168 tag 722168 + fixed-upstream Bug #722168 [wesnoth-1.10-core] Segfaults on startup Bug #721616 [wesnoth-1.10-core] wesnoth: segmentation fault wesnoth when my first turn on a map starts Added tag(s) fixed-upstream. Added tag(s) fixed-upstream. forwarded 722168 https://gna.org/bugs/?20742 Bug #722168 [wesnoth-1.10-core] Segfaults on startup Bug #721616 [wesnoth-1.10-core] wesnoth: segmentation fault wesnoth when my first turn on a map starts Set Bug forwarded-to-address to 'https://gna.org/bugs/?20742'. Set Bug forwarded-to-address to 'https://gna.org/bugs/?20742'. thanks Stopping processing here. Please contact me if you need assistance. -- 721616: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721616 722168: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722168 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704785: marked as done (funguloids: Please upgrade OGRE dependency to 1.8 or greater)
Your message dated Tue, 10 Sep 2013 09:18:59 + with message-id e1vjk67-0005ox...@franck.debian.org and subject line Bug#704785: fixed in funguloids 1.06-11 has caused the Debian Bug report #704785, regarding funguloids: Please upgrade OGRE dependency to 1.8 or greater to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 704785: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704785 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: funguloids Severity: wishlist Hello, After the freeze is over, please consider to upload a new version of funguloids depending on OGRE v1.8 (or v1.9, if available by then). Your package currently depends on v1.7 series, which is discontinued and unsupported (as far as I know), and so it should not be present in future releases of Debian. This also affects the transition of boost-defaults to 1.53 that they plan after the freeze. Cheers. ---End Message--- ---BeginMessage--- Source: funguloids Source-Version: 1.06-11 We believe that the bug you reported is fixed in the latest version of funguloids, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 704...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Fabian Greffrath fabian+deb...@greffrath.com (supplier of updated funguloids package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Fri, 07 Jun 2013 10:44:45 +0200 Source: funguloids Binary: funguloids funguloids-data Architecture: source amd64 all Version: 1.06-11 Distribution: unstable Urgency: low Maintainer: Debian Games Team pkg-games-de...@lists.alioth.debian.org Changed-By: Fabian Greffrath fabian+deb...@greffrath.com Description: funguloids - space-flying-mushroom-picking-simulator game funguloids-data - space-flying-mushroom-picking-simulator game (data files) Closes: 704785 Changes: funguloids (1.06-11) unstable; urgency=low . [ Evgeni Golov ] * Correct Vcs-* URLs to point to anonscm.debian.org . [ Fabian Greffrath ] * Build against Ogre-1.8 with a little help from another patch courtesy of openSUSE Build Service (Closes: #704785). * Add a Build-Conflicts: libboost-date-time1.49-dev ( 1.49.0-4~) to avoid the notorious TIME_UTC bug. Checksums-Sha1: 0118222369ee43ed8180ea8bfcedf202dc37e70d 2225 funguloids_1.06-11.dsc ebabdcd80b36165f0861c3568a2a9afbb1860a72 15008 funguloids_1.06-11.debian.tar.gz 3a56c6e1b4fbecbedd10b3e83584556c75252a5d 98180 funguloids_1.06-11_amd64.deb db517630da6598c615f5340d3df05934e75990f8 12559782 funguloids-data_1.06-11_all.deb Checksums-Sha256: f99a9a4181d95e7f9ceac803405bb1a65f8e5115658b0d0d03c3a76555feafb0 2225 funguloids_1.06-11.dsc 178ec921e3a144b35708a66d22ac5d6d94bd5e63cc42888e2ae86e67af38f132 15008 funguloids_1.06-11.debian.tar.gz 9355c1be210ca0786d6c408d4f9925ace85b08eacea448d8b3ec2f603e3d7ca6 98180 funguloids_1.06-11_amd64.deb cf8c5a8cf44b486bf96f44724ea13a333a6e12c391cb06ce470bf44f70f6847b 12559782 funguloids-data_1.06-11_all.deb Files: cc391d3eb3a54ef170e6f50eeeb9c803 2225 games extra funguloids_1.06-11.dsc c1e096395d2c18111574c6a1f9a5134c 15008 games extra funguloids_1.06-11.debian.tar.gz e8872d44e8253670c1f58d416d8b363d 98180 games extra funguloids_1.06-11_amd64.deb 4614c4edea49a07e63759e35b3c5711e 12559782 games extra funguloids-data_1.06-11_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) iQIcBAEBCgAGBQJSLs7oAAoJEDEWul6f+mmj3pUP/0QGjxeXlwkEGHuhqf9ezl+7 sVgUdclrEmQJ30CbtdBJ8b0kOvI/fysJeDwsatCgwQ1tzpapaWa/Dz4Wxv/3OZkG uojCJmUCNttMitIDXExGEVSEOikZKAC+zK5c3uIE4Ko5wVCelWh5y4amyRyv3fR9 yTqvdDuu+P3vBPXc/ml/kFkOZl1wqgiEmp/riAdQM+pPNaO5KLxxo/aFXEWIX6tI mDsPNbTysS+IrZjR9SOPO6R/89HgSTrvuSI+4D98zWh8/Xu0QhL0zVZhh19/NdvN y50JsZMRAXPWM0r6c2FJV1yloYR2kH5YN1n+V8Jcph/2hxq32uGR0F1h65taWssq y6ZVNseO7+Vj7YUrilGQvd1Jnj/9u7bwtxEeA19Ef7X4ECXH22pj+/qqKBJ8Xp+R eb1jk2yiUJwDvxBm/Fe7b2kyUFdHYsqnf1E/JpSH0u4ft0sp21yYkzvIZi1GHN60 NZgk5qTe0036gk3p2eDtFh2YCJhuo84ZZWQmw094uGdRJzaosyHP6TZUOqYYrgL3 tbvY0AH4/jadA/YIPUDs1g5axMp2QAkRdHFF0H6QvxNWyDwv7SVEnwbDZ/epKk8s Qhih1Hyeb0LIl0s1yeUAcWL5jfeoPBIatkcaOKZVFSBFd1Dssh2PwYpzX/tKnKaU mNcq9nKZOnT3wdyN4PmK =EqDA -END PGP
Bug#721388: gdm3: anyone can change the user's next session
severity 721388 normal thanks Le Mon, 9 Sep 2013 19:22:29 +0200, Vincent Lefevre vinc...@vinc17.net a écrit : On 2013-09-09 17:26:30 +0200, Laurent Bigonville wrote: So if I understood correctly: 1) A rogue user has selected your user in the list and then changed your session to something else. 2) When you arrived in front of the screen you saw that your user was already selected and then you just typed your password 3) You were logged in using the wrong session. Is that correct? I think that I cancelled first by typing Enter (i.e. an incorrect password). But, FYI, my user is selected by default as this is the only user of the machine. I tried to reproduce this on a machine running GDM 3.8 and I definitely cannot reproduce this. To save the default session of a user you really need to enter the password of this user, and as soon as you are hitting escape or enter with a wrong password, the session of the user is reset to the saved one. I guess that adding a timeout to un-select the user (return from the screen where you need to enter the password to the one (main) were you select the user) could mitigate this issue. I'll open an upstream bug for this. Cheers Laurent Bigonville -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#721388: gdm3: anyone can change the user's next session
Processing commands for cont...@bugs.debian.org: severity 721388 normal Bug #721388 [gdm3] gdm3: anyone can change the user's next session in a more-or-less hidden way Severity set to 'normal' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 721388: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721388 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721092: [Pkg-mozext-maintainers] Bug#721092: xul-ext-pentadactyl is incompatible with iceweasel
Hey David, On Mon, Sep 09, 2013 at 04:30:06PM -0400, David Prévot wrote: -BEGIN PGP SIGNED MESSAGE- Le 09/09/2013 06:25, Michael Schutte a écrit : Meanwhile, updating dactyl through stable-security is also not a possibility It may not be welcome, but it already happened for at least enigmail and adblockplus. In the mean time, the release team already accepted a bunch of minimal patches that allow some extensions to work in both stable-security and the current stable (at least a more invasive one has been proposed for firetray, and has not yet been rejected). Ah, I didn't know there was a precendent even for non-essential extensions. I'm afraid that Pentadactyl is a much trickier case; there is no release supporting 17.*, I'm not comfortable with uploading a revision from the upstream VCS to stable, and even a minimal patch would be an invasive mess. As 24.0 ESR is scheduled to be released next week it would be silly not to keep it in mind as well, and that situation is even worse. If there are no objections I'm therefore going to downgrade the severity of #721092, tag it wontfix and leave it for posterity. I would strongly disagree (SC#3 We will not hide problems), if dactyl happen to be broken in stable and no fix can address that, the package should be removed from stable. You're right, and I'm afraid a removal does seem like the only feasible option to me. Michael -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722057: libdspam7-drv-hash: dspam segfaults [libhash_drv on _hash_drv_seek()]
Le samedi 7 septembre 2013 23:46:14 Thomas Preud'homme a écrit : By the way, could you send me that css file so that I can run some test on it? It's better to not send it to the bug log as it might contain some private information. I don't know exactly what is stored in those files so better be safe than sorry. Alright, I managed to reproduce the issue with the file you sent me. From what I could gather quickly in gdb the file is corrupted. Cssclean assume the file respect some constraint but since they are not respected it reads too far in memory which causes the segfault. The bug didn't happened for me when I was running as simple user because it could not read the configuration. I'll forward the problem upstream but given how silent is the development since one year (not a single commit, almost no message on mailing list), I doubt they will fix it. This means I'll probably do the fix myself but I don't have much time right now. Best regards, Thomas signature.asc Description: This is a digitally signed message part.
Bug#722332: libcommon-sense-perl: common::sense runs into trouble with Perl 5.18, eg. no say().
Package: libcommon-sense-perl Version: 3.72-1 Severity: grave Justification: renders package unusable Dear maintainer, I just noticed that, upon upgrading to Perl 5.18.1-3 (Debian testing), common::sense stopped having some: $ perl -Mcommon::sense -e 'say hi;' syntax error at -e line 1, near say hi Execution of -e aborted due to compilation errors. On another machine with Perl 5.14 still installed and the same version of libcommon-sense-perl (3.72-1) it's still the same friendly response: $ perl -Mcommon::sense -e 'say hi;' hi So, *something* happened upon upgrading, although I'm currently at a loss (of time, mainly) to specify what exactly. Surely I messed something up and everything's working fine for everybody else? Thank you! Regards, Hagen -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722336: kfreebsd-9: CVE-2013-5666: sendfile kernel memory disclosure
Package: src:kfreebsd-9 Version: 9.2~svn253912-1 Severity: grave Tags: security upstream http://security.FreeBSD.org/advisories/FreeBSD-SA-13:11.sendfile.asc This affects 9.2 only. The advisory says this is fixed in r255444 but I'm not sure if that's correct. SA-13:12 and SA-13:13 are fixed in that commit. -- System Information: Debian Release: 7.1 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-2-amd64-xenhvm Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kfreebsd-image-9.0-2-amd64-xenhvm depends on: ii devd 9.0-10+deb70.3 ii freebsd-utils 9.0-10+deb70.3 ii kbdcontrol 9.0-10+deb70.3 ii kldutils 9.0-10+deb70.3 kfreebsd-image-9.0-2-amd64-xenhvm recommends no packages. kfreebsd-image-9.0-2-amd64-xenhvm 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#722337: kfreebsd-9: CVE-2013-5710: nullfs hardlinks across mounts
Package: src:kfreebsd-9 Version: 9.0-10+deb70.3 Severity: grave Tags: security upstream Control: found -1 kfreebsd-9/9.0~svn223109-0.1 http://security.FreeBSD.org/advisories/FreeBSD-SA-13:13.nullfs.asc nullfs wrongly allows creating hard links between separate instances, as long as they're based on the same underlying filesystem. That undermines security of chroot/jails depending on it for isolation. kfreebsd-8 and kfreebsd-9 in wheezy will need the patch from r255443 kfreebsd-9 in jessie/sid will need updating to r255444 or later kfreebsd-10 in experimental will need updating to r255442 or later -- System Information: Debian Release: 7.1 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-2-amd64-xenhvm Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kfreebsd-image-9.0-2-amd64-xenhvm depends on: ii devd 9.0-10+deb70.3 ii freebsd-utils 9.0-10+deb70.3 ii kbdcontrol 9.0-10+deb70.3 ii kldutils 9.0-10+deb70.3 kfreebsd-image-9.0-2-amd64-xenhvm recommends no packages. kfreebsd-image-9.0-2-amd64-xenhvm 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
Processed: kfreebsd-9: CVE-2013-5710: nullfs hardlinks across mounts
Processing control commands: found -1 kfreebsd-9/9.0~svn223109-0.1 Bug #722337 [src:kfreebsd-9] kfreebsd-9: CVE-2013-5710: nullfs hardlinks across mounts Marked as found in versions kfreebsd-9/9.0~svn223109-0.1. -- 722337: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722337 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: kfreebsd-9: CVE-2013-5691: ifioctl credential checks missing
Processing control commands: found -1 kfreebsd-9/9.0~svn223109-0.1 Bug #722338 [src:kfreebsd-9] kfreebsd-9: CVE-2013-5691: ifioctl credential checks missing Marked as found in versions kfreebsd-9/9.0~svn223109-0.1. -- 722338: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722338: kfreebsd-9: CVE-2013-5691: ifioctl credential checks missing
Package: src:kfreebsd-9 Version: 9.0-10+deb70.3 Severity: grave Tags: security upstream Control: found -1 kfreebsd-9/9.0~svn223109-0.1 http://security.FreeBSD.org/advisories/FreeBSD-SA-13:12.ifioctl.asc User privileges for certain ioctls are not checked by the IPv6 or ATM layer. This allows to modify a network interface, trigger a panic, or maybe escalate privileges. kfreebsd-8 and kfreebsd-9 in wheezy will need the patch from r255443 kfreebsd-9 in jessie/sid will need updating to r255444 or later kfreebsd-10 in experimental will need updating to r255442 or later -- System Information: Debian Release: 7.1 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-2-amd64-xenhvm Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kfreebsd-image-9.0-2-amd64-xenhvm depends on: ii devd 9.0-10+deb70.3 ii freebsd-utils 9.0-10+deb70.3 ii kbdcontrol 9.0-10+deb70.3 ii kldutils 9.0-10+deb70.3 kfreebsd-image-9.0-2-amd64-xenhvm recommends no packages. kfreebsd-image-9.0-2-amd64-xenhvm 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#714540: closing 714540
close 714540 3.8.4-1 thanks Hi, This is fixed in 3.8.4-1 Upgrade from unstable to experimental is working fine now. Cheers Laurent Bigonville -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: closing 714540
Processing commands for cont...@bugs.debian.org: close 714540 3.8.4-1 Bug #714540 [libgdm] libgdm: fails to upgrade from 'sid' - trying to overwrite /usr/bin/gdmflexiserver There is no source info for the package 'libgdm' at version '3.8.4-1' with architecture '' Unable to make a source version for version '3.8.4-1' Marked as fixed in versions 3.8.4-1. Bug #714540 [libgdm] libgdm: fails to upgrade from 'sid' - trying to overwrite /usr/bin/gdmflexiserver Marked Bug as done thanks Stopping processing here. Please contact me if you need assistance. -- 714540: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714540 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed (with 5 errors): Pending wheezy-security upload
Processing commands for cont...@bugs.debian.org: tags 722338 + pending Bug #722338 [src:kfreebsd-9] kfreebsd-9: CVE-2013-5691: ifioctl credential checks missing Added tag(s) pending. tags 722337 + pending Bug #722337 [src:kfreebsd-9] kfreebsd-9: CVE-2013-5710: nullfs hardlinks across mounts Added tag(s) pending. branches/wheezy/kfreebsd-9/ r4939 is ready in SVN for anyone to test. Unknown command or malformed arguments to command. I'm building it for kfreebsd-amd64 currently. Testing for working IPv6 Unknown command or malformed arguments to command. and nullfs seems like a good idea. Unknown command or malformed arguments to command. Attached is a debdiff against unpacked source of 9.0-10+deb70.3 Unknown command or malformed arguments to command. Regards, Unknown command or malformed arguments to command. Too many unknown commands, stopping here. Please contact me if you need assistance. -- 722337: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722337 722338: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722338 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: [Python-apps-team] Bug#722307: [picard] Uninstallable because it depends on python2 (not in sid)
Processing control commands: reassign -1 dh-python 1.20130901-1 Bug #722307 [picard] [picard] Uninstallable because it depends on python2 (not in sid) Bug reassigned from package 'picard' to 'dh-python'. No longer marked as found in versions picard/1.2-2. Ignoring request to alter fixed versions of bug #722307 to the same values previously set Bug #722307 [dh-python] [picard] Uninstallable because it depends on python2 (not in sid) Marked as found in versions dh-python/1.20130901-1. retitle -1 dh-python: dh_python2 creates dependencies on non-existing python2 Bug #722307 [dh-python] [picard] Uninstallable because it depends on python2 (not in sid) Changed Bug title to 'dh-python: dh_python2 creates dependencies on non-existing python2' from '[picard] Uninstallable because it depends on python2 (not in sid)' affects -1 + picard Bug #722307 [dh-python] dh-python: dh_python2 creates dependencies on non-existing python2 Added indication that 722307 affects picard -- 722307: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722307 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722307: [Python-apps-team] Bug#722307: [picard] Uninstallable because it depends on python2 (not in sid)
Control: reassign -1 dh-python 1.20130901-1 Control: retitle -1 dh-python: dh_python2 creates dependencies on non-existing python2 Control: affects -1 + picard On 2013-09-10 08:13:26, Schrober wrote: Package: picard Version: 1.2-2 Severity: serious The new version of picard in sid depends on python2 which is not available in sid. This was tested on amd64 This looks like a dh-python issue to me. Looking through the build logs of picard 1.2-1 on mips and kfreebsd-i386, this bug was introduced in 1.20130901-1. 1.2-1 on these two architectures had a dependency on python2 (both built with dh-python 1.20130901-1), but 1.2-1 on the other architectures (built with dh-python 1.20130819-1) don't have a depdency on python2. Reassigning to dh-python. Regards -- Sebastian Ramacher signature.asc Description: Digital signature
Processed: Re: Bug#714409: This bug still bites
Processing control commands: severity -1 grave Bug #714409 [libgtk-3-0] libgtk-3-0: triggers ci file contains unknown directive `interest-noawait' on install (needs newer dpkg) Severity set to 'grave' from 'important' -- 714409: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#714409: This bug still bites
severity 714409 thanks Am 10.09.2013 14:52, schrieb Greg Alexander: Control: severity -1 grave You are wrong. Debian is very good about supporting an indefinite Sorry to disappoint you, but you are. If you re-raise the severity again, I'll ask the BTS admins to ban your email address. Regards, Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Processed: severity of 714409 is important
Processing commands for cont...@bugs.debian.org: severity 714409 important Bug #714409 [libgtk-3-0] libgtk-3-0: triggers ci file contains unknown directive `interest-noawait' on install (needs newer dpkg) Severity set to 'important' from 'grave' thanks Stopping processing here. Please contact me if you need assistance. -- 714409: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=714409 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710650: Bug#718767: transition: ocaml 4.00.1
On 09/10/2013 03:17 PM, Stéphane Glondu wrote: Le 06/09/2013 10:14, Thomas Goirand a écrit : I wrote it many time to many people. Please don't just read 1.6 as new upstream release for XCP. That's unfortunately not the way it works. Upstream version for Debian and the one they do for CentOS are different, and just using upstream 1.6 doesn't cut it. It needs to be ported to Debian, and that's far from a trivial work (as Michael Tokarev wrote, it's not just replacing /usr/libexec/ into /usr/lib/ and the like). That is not the way it should work. Upstream version should not be specific to either Debian or CentOS. There should be only one version, and it is the job of each distribution (yours, here) to do the specialization work. Well, I agree, and upstream agrees as well. There's an ongoing work to have this happen. If you can't, then arrange for its removal from testing. However, as I wrote it, it's going to happen, so please be patient about it. IMO, this shouldn't block any transition though. If the release team is reading: just let everything transition to testing, and remove the old version of XCP 1.3.2 in testing if that helps, plus add some blocking bugs so that the rest of Debian isn't affected by the (not finished) work on XCP 1.6 for Debian. There are reverse-dependencies so it cannot be easily removed from testing. And this situation IS blocking other people's work. And has been for (at least) one month. Right. Though the month of August isn't the best time for things to move on, as people go in holidays, go in Debconf, and so on... :) No, the package isn't neglected. It's simply more complicated than it seems. I'm currently dealing with upstream about it. While doing so, please make sure future versions are trivial to port to Debian. It should have been done during the initial packaging. Yes, it should have. Though it's not as easy as it sounds in your wording, and this work was done by upstream. I have no time for doing the work myself. I by the way don't mind if 1.3.2 is removed from testing, as we will need to package the next version anyway. Then, could you give the list of packages that should be removed from testing? Remember, testing should be self-contained, so it means remove all reverse dependencies as well. I'm currently removing the xcp-plugins from Nova. As for the list of packages, it's rather easy, they are all listed here: http://qa.debian.org/developer.php?login=pkg-xen-de...@lists.alioth.debian.org (of course, that doesn't include the xen package which is the hypervisor which is also listed) Cheers, Thomas Goirand (zigo) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721777: marked as done (postgres-xc: fails to install: initializing pg_authid ... FATAL: wrong number of index expressions)
Your message dated Tue, 10 Sep 2013 13:18:22 + with message-id e1vjnpm-00065q...@franck.debian.org and subject line Bug#721777: fixed in postgres-xc 1.1-1 has caused the Debian Bug report #721777, regarding postgres-xc: fails to install: initializing pg_authid ... FATAL: wrong number of index expressions to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 721777: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721777 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: postgres-xc Version: 1.0.3-1 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package postgres-xc. (Reading database ... 7420 files and directories currently installed.) Unpacking postgres-xc (from .../postgres-xc_1.0.3-1+b1_amd64.deb) ... Setting up postgres-xc (1.0.3-1+b1) ... Adding user postgres-xc to group ssl-cert The files belonging to this GTM system will be owned by user postgres-xc. This user must also own the server process. creating directory GTM ... ok creating configuration files ... ok Success. You can now start the GTM server using: gtm -D GTM or gtm_ctl -Z gtm -D GTM -l logfile start The files belonging to this database system will be owned by user postgres-xc. This user must also own the server process. The database cluster will be initialized with locale C. The default database encoding has accordingly been set to SQL_ASCII. The default text search configuration will be set to english. creating directory CN ... ok creating subdirectories ... ok selecting default max_connections ... 100 selecting default shared_buffers ... 24MB creating configuration files ... ok creating template1 database in CN/base/1 ... ok initializing pg_authid ... FATAL: wrong number of index expressions STATEMENT: REVOKE ALL on pg_authid FROM public; child process exited with exit code 1 initdb: removing data directory CN dpkg: error processing postgres-xc (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: postgres-xc cheers, Andreas postgres-xc_1.0.3-1+b1.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: postgres-xc Source-Version: 1.1-1 We believe that the bug you reported is fixed in the latest version of postgres-xc, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 721...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Michael Meskes mes...@debian.org (supplier of updated postgres-xc package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 10 Sep 2013 14:15:21 +0200 Source: postgres-xc Binary: postgres-xc postgres-xc-dbg postgres-xc-doc postgres-xc-client postgres-xc-server-dev postgres-xc-plperl postgres-xc-plpython postgres-xc-pltcl postgres-xc-contrib ecpg-xc Architecture: source amd64 all Version: 1.1-1 Distribution: unstable Urgency: low Maintainer: Debian PostgreSQL Maintainers pkg-postgresql-pub...@lists.alioth.debian.org Changed-By: Michael Meskes mes...@debian.org Description: ecpg-xc- Postgres-XC version of ECPG (Embedded PostgreSQL for C) postgres-xc - write-scalable, synchronous multi-master, transparent PostgreSQL postgres-xc-client - front-end programs for Postgres-XC postgres-xc-contrib - additional facilities for Postgres-XC postgres-xc-dbg - debug symbols for postgres-xc postgres-xc-doc - documentation for the Postgres-XC cluster postgres-xc-plperl - PL/Perl procedural language for Postgres-XC postgres-xc-plpython - PL/Python procedural language for Postgres-XC postgres-xc-pltcl - PL/Tcl procedural language for Postgres-XC postgres-xc-server-dev - development files for Postgres-XC server-side programming Closes: 721777 Changes: postgres-xc (1.1-1) unstable; urgency=low . * Imported
Bug#722336: kfreebsd-9: CVE-2013-5666: sendfile kernel memory disclosure
This is fixed in stable/9 in r255443. The offending commit was already reverted from the 9.2 branch prior to 9.2-RC3 for other reasons. On 10 September 2013 07:31, Steven Chamberlain ste...@pyro.eu.org wrote: Package: src:kfreebsd-9 Version: 9.2~svn253912-1 Severity: grave Tags: security upstream http://security.FreeBSD.org/advisories/FreeBSD-SA-13:11.sendfile.asc This affects 9.2 only. The advisory says this is fixed in r255444 but I'm not sure if that's correct. SA-13:12 and SA-13:13 are fixed in that commit. -- System Information: Debian Release: 7.1 APT prefers proposed-updates APT policy: (500, 'proposed-updates'), (500, 'stable') Architecture: kfreebsd-amd64 (x86_64) Kernel: kFreeBSD 9.0-2-amd64-xenhvm Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages kfreebsd-image-9.0-2-amd64-xenhvm depends on: ii devd 9.0-10+deb70.3 ii freebsd-utils 9.0-10+deb70.3 ii kbdcontrol 9.0-10+deb70.3 ii kldutils 9.0-10+deb70.3 kfreebsd-image-9.0-2-amd64-xenhvm recommends no packages. kfreebsd-image-9.0-2-amd64-xenhvm suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bsd-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/522f02f9.1060...@pyro.eu.org
Bug#722336: kfreebsd-9: CVE-2013-5666: sendfile kernel memory disclosure
On 10/09/13 14:20, Ed Maste wrote: This is fixed in stable/9 in r255443. The offending commit was already reverted from the 9.2 branch prior to 9.2-RC3 for other reasons. I suspected that might be the case but didn't have time to look into it yet. Thanks very much for saying so! Please could one of the DDs on the team upload (urgency=medium or high?) a new upstream snapshot of r255444 to unstable , which includes fixes for: - sendfile kernel memory disclosure [SA-13:11] (CVE-2013-5666) (Closes #722336) - ifioctl credential checks missing [SA-13:12] (CVE-2013-5691) (Closes: #722338) - nullfs hardlinks across mounts [SA-13:13] (CVE-2013-5710) (Closes: #722337) Thanks, Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#719138: marked as done (nova-common: fails to install: /var/lib/dpkg/info/nova-common.config: ip: not found)
Your message dated Tue, 10 Sep 2013 13:34:26 + with message-id e1vjo5k-0001bl...@franck.debian.org and subject line Bug#719138: fixed in nova 2013.1.3-1 has caused the Debian Bug report #719138, regarding nova-common: fails to install: /var/lib/dpkg/info/nova-common.config: ip: not found to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 719138: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719138 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nova-common Version: 2013.1.2-3 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, during a test with piuparts I noticed your package failed to install. As per definition of the release team this makes the package too buggy for a release, thus the severity. From the attached log (scroll to the bottom...): Selecting previously unselected package nova-common. (Reading database ... 21851 files and directories currently installed.) Unpacking nova-common (from .../nova-common_2013.1.2-3_all.deb) ... Setting up nova-common (2013.1.2-3) ... /var/lib/dpkg/info/nova-common.config: 1: /var/lib/dpkg/info/nova-common.config: ip: not found dpkg: error processing nova-common (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: nova-common cheers, Andreas nova-common_2013.1.2-3.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: nova Source-Version: 2013.1.3-1 We believe that the bug you reported is fixed in the latest version of nova, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 719...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand z...@debian.org (supplier of updated nova package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 22 Aug 2013 12:10:46 +0200 Source: nova Binary: python-nova nova-common nova-compute nova-compute-lxc nova-compute-uml nova-compute-xen nova-compute-qemu nova-compute-kvm nova-xcp-plugins nova-conductor nova-cert nova-scheduler nova-volume nova-api nova-network nova-console nova-consoleauth nova-doc nova-cells nova-baremetal nova-consoleproxy Architecture: source all Version: 2013.1.3-1 Distribution: unstable Urgency: low Maintainer: PKG OpenStack openstack-de...@lists.alioth.debian.org Changed-By: Thomas Goirand z...@debian.org Description: nova-api - OpenStack Compute - compute API frontend nova-baremetal - Openstack Compute - baremetal virt nova-cells - Openstack Compute - cells nova-cert - OpenStack Compute - certificate manager nova-common - OpenStack Compute - common files nova-compute - OpenStack Compute - compute node nova-compute-kvm - OpenStack Compute - compute node (KVM) nova-compute-lxc - OpenStack Compute - compute node (LXC) nova-compute-qemu - OpenStack Compute - compute node (QEmu) nova-compute-uml - OpenStack Compute - compute node (UserModeLinux) nova-compute-xen - OpenStack Compute - compute node (Xen) nova-conductor - OpenStack Compute - conductor service nova-console - OpenStack Compute - console nova-consoleauth - OpenStack Compute - Console Authenticator nova-consoleproxy - OpenStack Compute - NoVNC proxy nova-doc - OpenStack Compute - documentation nova-network - OpenStack Compute - network manager nova-scheduler - OpenStack Compute - virtual machine scheduler nova-volume - OpenStack Compute - storage metapackage nova-xcp-plugins - OpenStack Compute plugin for the Xen Cloud Platform python-nova - OpenStack Compute - libraries Closes: 718710 718924 719138 720005 720315 720602 721039 721259 Changes: nova (2013.1.3-1) unstable; urgency=low . * New upstream point release. * Fixed wrong chown in upstart script (sed s/Root/root/). * Adds new debconf template translations: - Brazilian Portuguese, thanks to Adriano Rafael Gomes (Closes: #718710). - Japanese, thanks to victory (Closes: #718924). * Debconf translation updates: - Danish, thanks to Joe Dalton (Closes: #720005). - Portuguese, thanks to the Traduz team (Closes: #720315). - Czech, thanks to Michal
Bug#720602: marked as done (nova: CVE-2013-4278: Incomplete fix for CVE-2013-2256)
Your message dated Tue, 10 Sep 2013 13:34:27 + with message-id e1vjo5l-0001bi...@franck.debian.org and subject line Bug#720602: fixed in nova 2013.1.3-1 has caused the Debian Bug report #720602, regarding nova: CVE-2013-4278: Incomplete fix for CVE-2013-2256 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 720602: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720602 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: nova Version: 2013.1.2-3 Severity: grave Tags: security upstream patch *** /tmp/nova.reportbug Package: nova Severity: FILLINSEVERITY Tags: security Hi, the following vulnerability was published for nova. CVE-2013-4278[0]: Nova private flavors resource limit circumvention This is the CVE for the incomplete fix for previous CVE-2013-2256, see bug #718905[1]. See furthermore [2] and patch for grizzly[3]. If you fix the vulnerability please also make sure to include the CVE (Common Vulnerabilities Exposures) id in your changelog entry. For further information see: [0] http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2013-4278 http://security-tracker.debian.org/tracker/CVE-2013-4278 [1] http://bugs.debian.org/718905 [2] https://bugs.launchpad.net/ossa/+bug/1212179 [3] https://review.openstack.org/#/c/43281/ Regards, Salvatore ---End Message--- ---BeginMessage--- Source: nova Source-Version: 2013.1.3-1 We believe that the bug you reported is fixed in the latest version of nova, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 720...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Thomas Goirand z...@debian.org (supplier of updated nova package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 22 Aug 2013 12:10:46 +0200 Source: nova Binary: python-nova nova-common nova-compute nova-compute-lxc nova-compute-uml nova-compute-xen nova-compute-qemu nova-compute-kvm nova-xcp-plugins nova-conductor nova-cert nova-scheduler nova-volume nova-api nova-network nova-console nova-consoleauth nova-doc nova-cells nova-baremetal nova-consoleproxy Architecture: source all Version: 2013.1.3-1 Distribution: unstable Urgency: low Maintainer: PKG OpenStack openstack-de...@lists.alioth.debian.org Changed-By: Thomas Goirand z...@debian.org Description: nova-api - OpenStack Compute - compute API frontend nova-baremetal - Openstack Compute - baremetal virt nova-cells - Openstack Compute - cells nova-cert - OpenStack Compute - certificate manager nova-common - OpenStack Compute - common files nova-compute - OpenStack Compute - compute node nova-compute-kvm - OpenStack Compute - compute node (KVM) nova-compute-lxc - OpenStack Compute - compute node (LXC) nova-compute-qemu - OpenStack Compute - compute node (QEmu) nova-compute-uml - OpenStack Compute - compute node (UserModeLinux) nova-compute-xen - OpenStack Compute - compute node (Xen) nova-conductor - OpenStack Compute - conductor service nova-console - OpenStack Compute - console nova-consoleauth - OpenStack Compute - Console Authenticator nova-consoleproxy - OpenStack Compute - NoVNC proxy nova-doc - OpenStack Compute - documentation nova-network - OpenStack Compute - network manager nova-scheduler - OpenStack Compute - virtual machine scheduler nova-volume - OpenStack Compute - storage metapackage nova-xcp-plugins - OpenStack Compute plugin for the Xen Cloud Platform python-nova - OpenStack Compute - libraries Closes: 718710 718924 719138 720005 720315 720602 721039 721259 Changes: nova (2013.1.3-1) unstable; urgency=low . * New upstream point release. * Fixed wrong chown in upstart script (sed s/Root/root/). * Adds new debconf template translations: - Brazilian Portuguese, thanks to Adriano Rafael Gomes (Closes: #718710). - Japanese, thanks to victory (Closes: #718924). * Debconf translation updates: - Danish, thanks to Joe Dalton (Closes: #720005). - Portuguese, thanks to the Traduz team (Closes: #720315). - Czech, thanks to Michal Šimůnek (Closes: #721039). - Russian, thanks to Yuri Kozlov (Closes: #721259). * Adds iproute to nova-common depends (Closes:
Bug#722057: marked as done (libdspam7-drv-hash: dspam segfaults [libhash_drv on _hash_drv_seek()])
Your message dated Tue, 10 Sep 2013 13:33:20 + with message-id e1vjo4g-0008dv...@franck.debian.org and subject line Bug#722057: fixed in dspam 3.10.2+dfsg-9 has caused the Debian Bug report #722057, regarding libdspam7-drv-hash: dspam segfaults [libhash_drv on _hash_drv_seek()] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 722057: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722057 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libdspam7-drv-hash Version: 3.10.1+dfsg-11 Severity: grave Justification: causes non-serious data loss Sample of dmesg: [1701173.909095] dspam[15582]: segfault at 7f8c2197acf8 ip 7f8c1ea8f69a sp 7f8c1cbe9048 error 4 in libhash_drv.so.7.0.0[7f8c1ea8b000+6000] [1775508.341567] cssclean[25298]: segfault at 7f9b7086a000 ip 00403b5b sp 7fff7d456130 error 7 in cssclean[40+c000] [1785820.256253] dspam[8177]: segfault at 7ff586ffe2f8 ip 7ff58dd4169a sp 7ff58cd35048 error 4 in libhash_drv.so.7.0.0[7ff58dd3d000+6000] [1785862.479249] dspam[8243]: segfault at 7fa456fa62f8 ip 7fa457fac69a sp 7fa4577a1048 error 4 in libhash_drv.so.7.0.0[7fa457fa8000+6000] [1785888.517082] dspam[8281]: segfault at 7fef8160c2f8 ip 7fef8261269a sp 7fef81e07048 error 4 in libhash_drv.so.7.0.0[7fef8260e000+6000] [1786011.902307] dspam[8760]: segfault at 7f8a051752f8 ip 7f8a0617b69a sp 7f8a06171048 error 4 in libhash_drv.so.7.0.0[7f8a06177000+6000] I happened to be in a situation where I can't even fully flush the postfix queue without having Dspam to segfault. I end up installing dspam-dbg and gdb and attach to the process [I wasn't able to run the process without the init-script]. Here is a stack trace, but sadly libdspam7-drv-hash does not provide debug symbols. (gdb) bt #0 0x7ff5afdc369a in _hash_drv_seek () from /usr/lib/x86_64-linux-gnu/dspam/libhash_drv.so #1 0x7ff5afdc3a19 in _hash_drv_get_spamrecord () from /usr/lib/x86_64-linux-gnu/dspam/libhash_drv.so #2 0x7ff5afdc3a90 in _ds_get_spamrecord () from /usr/lib/x86_64-linux-gnu/dspam/libhash_drv.so #3 0x7ff5afdc3cfd in _ds_getall_spamrecords () from /usr/lib/x86_64-linux-gnu/dspam/libhash_drv.so #4 0x7ff5b28422f6 in _ds_operate () from /usr/lib/x86_64-linux-gnu/libdspam.so.7 #5 0x7ff5b2842e90 in dspam_process () from /usr/lib/x86_64-linux-gnu/libdspam.so.7 #6 0x0040bad7 in process_message (ATX=ATX@entry=0xd58e90, message=message@entry=0xd5aa10, username=username@entry=0xd584e0 testabcd...@orange.fr, result_string=result_string@entry=0x7ff5afdbc348) at dspam.c:540 #7 0x0040ce4d in process_users (ATX=ATX@entry=0xd58e90, message=message@entry=0xd5af10) at dspam.c:1882 #8 0x0040faa0 in process_connection (ptr=0xd56f80) at daemon.c:738 #9 0x7ff5b2621b50 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #10 0x7ff5b236ba7d in clone () from /lib/x86_64-linux-gnu/libc.so.6 #11 0x in ?? () (gdb) bt full #0 0x7ff5afdc369a in _hash_drv_seek () from /usr/lib/x86_64-linux-gnu/dspam/libhash_drv.so No symbol table info available. #1 0x7ff5afdc3a19 in _hash_drv_get_spamrecord () from /usr/lib/x86_64-linux-gnu/dspam/libhash_drv.so No symbol table info available. #2 0x7ff5afdc3a90 in _ds_get_spamrecord () from /usr/lib/x86_64-linux-gnu/dspam/libhash_drv.so No symbol table info available. #3 0x7ff5afdc3cfd in _ds_getall_spamrecords () from /usr/lib/x86_64-linux-gnu/dspam/libhash_drv.so No symbol table info available. #4 0x7ff5b28422f6 in _ds_operate () from /usr/lib/x86_64-linux-gnu/libdspam.so.7 No symbol table info available. #5 0x7ff5b2842e90 in dspam_process () from /usr/lib/x86_64-linux-gnu/libdspam.so.7 No symbol table info available. #6 0x0040bad7 in process_message (ATX=ATX@entry=0xd58e90, message=message@entry=0xd5aa10, username=username@entry=0xd584e0 testabcd...@orange.fr, result_string=result_string@entry=0x7ff5afdbc348) at dspam.c:540 CTX = 0xd96700 components = optimized out copyback = optimized out have_signature = optimized out result = optimized out i = optimized out internally_canned = 0 -- System Information: Debian Release: 7.1 APT prefers stable APT policy: (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libdspam7-drv-hash depends on: ii libc6 2.13-38 ii
Processed: Re: Bug#722323: qtiplot: Qtiplot does not start and produces a symbol lookup error in /usr/lib/liborigin2.so.1
Processing commands for cont...@bugs.debian.org: severity 722323 grave Bug #722323 [qtiplot] qtiplot: Qtiplot does not start and produces a symbol lookup error in /usr/lib/liborigin2.so.1 Severity set to 'grave' from 'important' tags 722323 +pending Bug #722323 [qtiplot] qtiplot: Qtiplot does not start and produces a symbol lookup error in /usr/lib/liborigin2.so.1 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 722323: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721166: ffdiaporama: depends on ffmpeg which is going away
Hi Fabrice, what's the status of 1.5-2? Is it just waiting to be uploaded? Regards -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#704809: marked as done (dvb-apps and scalasca: error when trying to install together)
Your message dated Tue, 10 Sep 2013 13:48:25 + with message-id e1vjoir-0003ib...@franck.debian.org and subject line Bug#704809: fixed in scalasca 2.0-1 has caused the Debian Bug report #704809, regarding dvb-apps and scalasca: error when trying to install together to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 704809: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704809 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: scalasca,dvb-apps Version: scalasca/1.4.2-1 Version: dvb-apps/1.1.1+rev1483-2 Severity: serious User: trei...@debian.org Usertags: edos-file-overwrite Date: 2013-04-06 Architecture: amd64 Distribution: sid Hi, automatic installation tests of packages that share a file and at the same time do not conflict by their package dependency relationships has detected the following problem: WARNING: The following packages cannot be authenticated! libquadmath0 libgfortran3 libgomp1 libpng12-0 libxau6 libxdmcp6 libxcb1 libx11-data libx11-6 libzvbi-common libzvbi0 libnuma1 libtorque2 dvb-apps libibverbs1 libopenmpi1.3 scalasca Authentication warning overridden. Can not write log, openpty() failed (/dev/pts not mounted?) Selecting previously unselected package libquadmath0:amd64. (Reading database ... 10775 files and directories currently installed.) Unpacking libquadmath0:amd64 (from .../libquadmath0_4.7.2-5_amd64.deb) ... Selecting previously unselected package libgfortran3:amd64. Unpacking libgfortran3:amd64 (from .../libgfortran3_4.7.2-5_amd64.deb) ... Selecting previously unselected package libgomp1:amd64. Unpacking libgomp1:amd64 (from .../libgomp1_4.7.2-5_amd64.deb) ... Selecting previously unselected package libpng12-0:amd64. Unpacking libpng12-0:amd64 (from .../libpng12-0_1.2.49-3_amd64.deb) ... Selecting previously unselected package libxau6:amd64. Unpacking libxau6:amd64 (from .../libxau6_1%3a1.0.7-1_amd64.deb) ... Selecting previously unselected package libxdmcp6:amd64. Unpacking libxdmcp6:amd64 (from .../libxdmcp6_1%3a1.1.1-1_amd64.deb) ... Selecting previously unselected package libxcb1:amd64. Unpacking libxcb1:amd64 (from .../libxcb1_1.8.1-2_amd64.deb) ... Selecting previously unselected package libx11-data. Unpacking libx11-data (from .../libx11-data_2%3a1.5.0-1_all.deb) ... Selecting previously unselected package libx11-6:amd64. Unpacking libx11-6:amd64 (from .../libx11-6_2%3a1.5.0-1_amd64.deb) ... Selecting previously unselected package libzvbi-common. Unpacking libzvbi-common (from .../libzvbi-common_0.2.33-7_all.deb) ... Selecting previously unselected package libzvbi0:amd64. Unpacking libzvbi0:amd64 (from .../libzvbi0_0.2.33-7_amd64.deb) ... Selecting previously unselected package libnuma1. Unpacking libnuma1 (from .../libnuma1_2.0.8-1_amd64.deb) ... Selecting previously unselected package libtorque2. Unpacking libtorque2 (from .../libtorque2_2.4.16+dfsg-1_amd64.deb) ... Selecting previously unselected package dvb-apps. Unpacking dvb-apps (from .../dvb-apps_1.1.1+rev1483-2_amd64.deb) ... Selecting previously unselected package libibverbs1. Unpacking libibverbs1 (from .../libibverbs1_1.1.6-1_amd64.deb) ... Selecting previously unselected package libopenmpi1.3. Unpacking libopenmpi1.3 (from .../libopenmpi1.3_1.4.5-1_amd64.deb) ... Selecting previously unselected package scalasca. Unpacking scalasca (from .../scalasca_1.4.2-1_amd64.deb) ... dpkg: error processing /var/cache/apt/archives/scalasca_1.4.2-1_amd64.deb (--unpack): trying to overwrite '/usr/bin/scan', which is also in package dvb-apps 1.1.1+rev1483-2 dpkg-deb: error: subprocess paste was killed by signal (Broken pipe) Processing triggers for man-db ... Errors were encountered while processing: /var/cache/apt/archives/scalasca_1.4.2-1_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) This is a serious bug as it makes installation fail, and violates sections 7.6.1 and 10.1 of the policy. An optimal solution would consist in only one of the packages installing that file, and renaming or removing the file in the other package. Depending on the circumstances you might also consider Replace relations or file diversions. If the conflicting situation cannot be resolved then, as a last resort, the two packages have to declare a mutual Conflict. Please take into account that Replaces, Conflicts and diversions should only be used when packages provide different implementations for the same functionality. Here is a list of files that are known to be shared by both packages (according to the Contents file for sid/amd64, which may be slightly out of sync): /usr/bin/scan
Bug#710650: Bug#718767: transition: ocaml 4.00.1
On 10/09/13 14:09, Thomas Goirand wrote: On 09/10/2013 03:17 PM, Stéphane Glondu wrote: Le 06/09/2013 10:14, Thomas Goirand a écrit : I wrote it many time to many people. Please don't just read 1.6 as new upstream release for XCP. That's unfortunately not the way it works. Upstream version for Debian and the one they do for CentOS are different, and just using upstream 1.6 doesn't cut it. It needs to be ported to Debian, and that's far from a trivial work (as Michael Tokarev wrote, it's not just replacing /usr/libexec/ into /usr/lib/ and the like). That is not the way it should work. Upstream version should not be specific to either Debian or CentOS. There should be only one version, and it is the job of each distribution (yours, here) to do the specialization work. Well, I agree, and upstream agrees as well. There's an ongoing work to have this happen. Certainly we do :-) There is indeed ongoing work, but it's not yet in a state to be able to be uploaded. However, fixing the xenguest compile problem looks fairly straightforward - I can try and provide a patch for that today. Would that help? As for becoming more upstream-friendly, there are now several of us working to make that happen. Euan Harris is working hard on actually creating packages from this work, though the shape of these packages is quite different from that of the old-style 1.3.2 packages. We should start a conversation on pkg-xen-devel to make sure what he's doing is acceptable to you guys. Jon -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710650: Bug#718767: transition: ocaml 4.00.1
Hmm, I'm not having much success in replicating the build environment for this - however, I did notice two patches in the ubuntu xen-api package that look relevant. The build failure appears to be related to xenguest, and there is a patch 'xenguest-4.2.patch' which looks worth a test. Also, I noticed another patch 'fix-xen-4.2-paths.patch' that might be relevant. Thomas, could you try these patches? If they don't work, perhaps you could (off list) advise me on how to set up the environment for building. Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722354: intel-vaapi-driver: FTBFS on kfreebsd-*: error: unknown type name 'uint64_t'
Source: intel-vaapi-driver Version: 1.0.20-2 Severity: serious Justification: FTBFS but built successfully in the past intel-vaapi-driver fails to build on kfreebsd-*: | libtool: compile: gcc -DHAVE_CONFIG_H -I. -DPTHREADS -I/usr/include/libdrm -D_FORTIFY_SOURCE=2 -Wall -fvisibility=hidden -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c intel_memman.c -fPIC -DPIC -o .libs/i965_drv_video_la-intel_memman.o | In file included from intel_driver.h:8:0, | from intel_memman.c:32: | /usr/include/libdrm/drm.h:50:1: error: unknown type name 'uint8_t' | /usr/include/libdrm/drm.h:52:1: error: unknown type name 'uint16_t' | /usr/include/libdrm/drm.h:54:1: error: unknown type name 'uint32_t' | /usr/include/libdrm/drm.h:56:1: error: unknown type name 'uint64_t' | make[5]: *** [i965_drv_video_la-intel_memman.lo] Error 1 The version in experimental fails similarly: | libtool: compile: gcc -DHAVE_CONFIG_H -I. -DPTHREADS -I/usr/include/libdrm -D_FORTIFY_SOURCE=2 -Wall -fvisibility=hidden -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c intel_memman.c -fPIC -DPIC -o .libs/i965_drv_video_la-intel_memman.o | In file included from intel_driver.h:9:0, | from intel_memman.c:32: | /usr/include/libdrm/drm.h:50:1: error: unknown type name 'uint8_t' | typedef uint8_t __u8; | ^ | /usr/include/libdrm/drm.h:52:1: error: unknown type name 'uint16_t' | typedef uint16_t __u16; | ^ | /usr/include/libdrm/drm.h:54:1: error: unknown type name 'uint32_t' | typedef uint32_t __u32; | ^ | /usr/include/libdrm/drm.h:56:1: error: unknown type name 'uint64_t' | typedef uint64_t __u64; | ^ | In file included from /usr/include/va/va_backend.h:33:0, | from intel_driver.h:13, | from intel_memman.c:32: | /usr/include/linux/videodev2.h:67:18: error: conflicting types for '__u64' | typedef uint64_t __u64; | ^ | In file included from intel_driver.h:9:0, | from intel_memman.c:32: | /usr/include/libdrm/drm.h:56:18: note: previous declaration of '__u64' was here | typedef uint64_t __u64; | ^ | In file included from /usr/include/va/va_backend.h:33:0, | from intel_driver.h:13, | from intel_memman.c:32: | /usr/include/linux/videodev2.h:70:18: error: conflicting types for '__u32' | typedef uint32_t __u32; | ^ | In file included from intel_driver.h:9:0, | from intel_memman.c:32: | /usr/include/libdrm/drm.h:54:18: note: previous declaration of '__u32' was here | typedef uint32_t __u32; | ^ | In file included from /usr/include/va/va_backend.h:33:0, | from intel_driver.h:13, | from intel_memman.c:32: | /usr/include/linux/videodev2.h:73:18: error: conflicting types for '__u16' | typedef uint16_t __u16; | ^ | In file included from intel_driver.h:9:0, | from intel_memman.c:32: | /usr/include/libdrm/drm.h:52:18: note: previous declaration of '__u16' was here | typedef uint16_t __u16; | ^ | In file included from /usr/include/va/va_backend.h:33:0, | from intel_driver.h:13, | from intel_memman.c:32: | /usr/include/linux/videodev2.h:76:17: error: conflicting types for '__u8' | typedef uint8_t __u8; | ^ | In file included from intel_driver.h:9:0, | from intel_memman.c:32: | /usr/include/libdrm/drm.h:50:18: note: previous declaration of '__u8' was here | typedef uint8_t __u8; | ^ Build logs: https://buildd.debian.org/status/fetch.php?pkg=intel-vaapi-driverarch=kfreebsd-i386ver=1.0.20-2stamp=1369333965 https://buildd.debian.org/status/fetch.php?pkg=intel-vaapi-driverarch=kfreebsd-amd64ver=1.2.0-1stamp=1378600135 Regards -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#706330: A set of themes for reference
For reference, you can use the Ambiance Crunchy set of themes. [1] Recently, it's been updated for GTK+ 3.8, and it still uses Unico. It looks fine in the current beta of Ubuntu Saucy (so, please, no theming is totally broken arguments) which uses the latest build of gtk3-engines-unico. I suggest updating gtk3-engines-unico to the same version (revision 150). It's not that hard. [1] http://box-look.org/content/show.php/?content=136162 -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722121: installing `gir1.2-gtk-3.0` doesn't fix this bug here
Hi, On Mon, Sep 09, 2013 at 08:44:48PM +0200, Ivan Sergio Borgonovo wrote: I can confirm the problem and having installed gir1.2-gtk-3.0 doesn't seem to work here. Question is what ibus modules are you using. If you are using ibus-* packages listed as bad in http://release.debian.org/transitions/html/ibus1.5.html This is expected situation under sid during transition. Please let me know what packages you use. Also, python dependency needs to be installed as Jeremy pointed out. * python-ibus for some ibus modules (ibus-setup) or * python-gi + gir1.2-ibus-1.0 for some ibus modules Osamu -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710650: Bug#718767: transition: ocaml 4.00.1
On 10.09.2013 16:07, Jon Ludlam wrote: Hmm, I'm not having much success in replicating the build environment for this - however, I did notice two patches in the ubuntu xen-api package that look relevant. The build failure appears to be related to xenguest, and there is a patch 'xenguest-4.2.patch' which looks worth a test. Also, I noticed another patch 'fix-xen-4.2-paths.patch' that might be relevant. Thomas, could you try these patches? If they don't work, perhaps you could (off list) advise me on how to set up the environment for building. We got the xen-api-libs re-uploaded with an ocaml fix (the type-conv change I think I sent Thomas, or could be extracted quite easy from the ubuntu package). With xen-api-libs rebuild, xen-api will also rebuild without change (for xen-4.2). For the xen-4.3 work I did add a patch that updates the paths again. Unfortunately that isn't uploaded yet as xen itself needed to go first and that needed an expection now). I am still waiting to get that sponsored in ubuntu. -Stefan signature.asc Description: OpenPGP digital signature
Bug#722332: libcommon-sense-perl: common::sense runs into trouble with Perl 5.18, eg. no say().
On Tue, 10 Sep 2013 12:35:16 +0200, Hagen Fuchs wrote:
Package: libcommon-sense-perl
Version: 3.72-1
Severity: grave
Justification: renders package unusable
I just noticed that, upon upgrading to Perl 5.18.1-3 (Debian testing),
common::sense stopped having some:
$ perl -Mcommon::sense -e 'say hi;'
syntax error at -e line 1, near say hi
Execution of -e aborted due to compilation errors.
I can confirm this behaviour.
On another machine with Perl 5.14 still installed and the same version
of libcommon-sense-perl (3.72-1) it's still the same friendly response:
$ perl -Mcommon::sense -e 'say hi;'
hi
Confirmed (on a stable machine with common-sense 3.6-1 and perl
5.14.2.)
So, *something* happened upon upgrading, although I'm currently at a
loss (of time, mainly) to specify what exactly. Surely I messed
something up and everything's working fine for everybody else?
I rebuilt common-sense now in unstable; as expected, the contents of
the resulting /usr/lib/perl5/common/sense.pm changes:
Before (as: in the package, built with 5.14 in August):
#v+
package common::sense;
our $VERSION = 3.72;
# overload should be included
sub import {
local $^W; # work around perl 5.16 spewing out warnings for next statement
# use warnings
${^WARNING_BITS} ^= ${^WARNING_BITS} ^
\x3c\x3f\x33\x00\x0f\xf0\x0f\xc0\xf0\xfc\x33\x00\x00;
# use strict, use utf8; use feature;
$^H |= 0x820f00;
@^H{qw(feature_unicode feature_say feature_state feature_switch)} = (1) x 4;
}
1
#v-
After:
#v+
package common::sense;
our $VERSION = 3.72;
# overload should be included
sub import {
local $^W; # work around perl 5.16 spewing out warnings for next statement
# use warnings
${^WARNING_BITS} ^= ${^WARNING_BITS} ^
\x3c\x3f\x33\x00\x0f\xf0\x0f\xc0\xf0\xfc\x33\x00\x00\x00;
# use strict, use utf8; use feature;
$^H |= 0x1c820fc0;
@^H{qw(feature_state feature_fc feature___SUB__ feature_switch feature_say
feature_evalbytes feature_unicode)} = (1) x 7;
}
1
#v-
But feature_say is, also as expected, there in both cases. Hm.
If I install the rebuilt package:
% perl -Mcommon::sense -e 'say hi;'
hi
Oh.
Seems we
- need to set lower and upper bounds of the perl version in Depends (not
only the lower, as it's now)
- hope that all buildds have perl 5.18 when we upload the fixed
package by now or request binNMUs with a dep-wait on perl 5.18.1-x
- add it to our mental list of packages that needs rebuilds on new
perl releases
I've committed the changes for the first point; reviews welcome!
Cheers,
gregor
--
.''`. Homepage: http://info.comodo.priv.at/ - OpenPGP key 0xBB3A68018649AA06
: :' : Debian GNU/Linux user, admin, and developer - http://www.debian.org/
`. `' Member of VIBE!AT SPI, fellow of the Free Software Foundation Europe
`- NP: Bettina Wegner: Ikarus
signature.asc
Description: Digital signature
Processed: your mail
Processing commands for cont...@bugs.debian.org: reassign 720259 gtk3-engines-unico Bug #720259 [libgtk-3-0] libgtk-3-0: Gnome Apps receive SEGFAULT after libgtk-3-0 Upgrade Bug reassigned from package 'libgtk-3-0' to 'gtk3-engines-unico'. No longer marked as found in versions gtk+3.0/3.8.2-3. Ignoring request to alter fixed versions of bug #720259 to the same values previously set forcemerge 706330 720259 Bug #706330 [gtk3-engines-unico] Some applications segfaults after upgrade to 3.8.0-1 Bug #709548 [gtk3-engines-unico] libgtk-3-0: most recent gtk upload breaks (nearly) everything (in GNOME) Bug #709946 [gtk3-engines-unico] gnome-settings-daemon: Segmentation fault during startup Bug #716714 [gtk3-engines-unico] dwb: Segmentation fault on startup Bug #716771 [gtk3-engines-unico] libgtk-3-0: Segmentation fault in gtk_style_context_get_valist Bug #717081 [gtk3-engines-unico] network-manager: Segementation fault when 'nm-applet' and 'nm-connection-editor' as non-root Bug #720259 [gtk3-engines-unico] libgtk-3-0: Gnome Apps receive SEGFAULT after libgtk-3-0 Upgrade Severity set to 'critical' from 'important' Marked as found in versions gtk3-engines-unico/1.0.2-1. Added tag(s) moreinfo, patch, and wheezy-ignore. Bug #709548 [gtk3-engines-unico] libgtk-3-0: most recent gtk upload breaks (nearly) everything (in GNOME) Bug #709946 [gtk3-engines-unico] gnome-settings-daemon: Segmentation fault during startup Bug #716714 [gtk3-engines-unico] dwb: Segmentation fault on startup Bug #716771 [gtk3-engines-unico] libgtk-3-0: Segmentation fault in gtk_style_context_get_valist Bug #717081 [gtk3-engines-unico] network-manager: Segementation fault when 'nm-applet' and 'nm-connection-editor' as non-root Merged 706330 709548 709946 716714 716771 717081 720259 End of message, stopping processing here. Please contact me if you need assistance. -- 706330: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706330 709548: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709548 709946: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=709946 716714: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716714 716771: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=716771 717081: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=717081 720259: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722323: marked as done (qtiplot: Qtiplot does not start and produces a symbol lookup error in /usr/lib/liborigin2.so.1)
Your message dated Tue, 10 Sep 2013 15:23:49 + with message-id e1vjpnb-0007g4...@franck.debian.org and subject line Bug#722323: fixed in qtiplot 0.9.8.9-7 has caused the Debian Bug report #722323, regarding qtiplot: Qtiplot does not start and produces a symbol lookup error in /usr/lib/liborigin2.so.1 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 722323: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722323 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: qtiplot Version: 0.9.8.9-6 Severity: important Dear Maintainer, When starting qtiplot 0.9.8.9-6 0 in debian/testing, it does not actually start. The following error is produced : qtiplot: symbol lookup error: /usr/lib/liborigin2.so.1: undefined symbol: _ZN5boost6system16generic_categoryEv I tried to reinstall qtiplot, no success. Sincerly, -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (700, 'testing'), (500, 'stable-updates'), (500, 'stable') Architecture: i386 (i686) Kernel: Linux 3.10-2-686-pae (SMP w/2 CPU cores) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages qtiplot depends on: ii libalglib3.7 3.7.0-7 ii libc6 2.17-92+b1 ii libgcc1 1:4.8.1-2 ii libgl1-mesa-glx [libgl1] 9.1.6-2 ii libgl2ps0 1.3.8-1 ii libglu1-mesa [libglu1]9.0.0-1 ii libgsl0ldbl 1.16+dfsg-1 ii libmuparser2 2.2.3-2 ii liborigin2-1 2:20110117-1+b3 ii libpng12-01.2.49-4 ii libpython2.7 2.7.5-5 ii libqt4-network4:4.8.5+dfsg-3 ii libqt4-opengl 4:4.8.5+dfsg-3 ii libqt4-qt3support 4:4.8.5+dfsg-3 ii libqt4-svg4:4.8.5+dfsg-3 ii libqt4-xml4:4.8.5+dfsg-3 ii libqtassistantclient4 4.6.3-6 ii libqtcore44:4.8.5+dfsg-3 ii libqtexengine10.3-3 ii libqtgui4 4:4.8.5+dfsg-3 ii libstdc++64.8.1-2 ii libtamuanova-0.2 0.2-3 ii python2.7.5-4 ii python-qt44.10.2-2 ii python-sip4.14.7-4 ii zlib1g1:1.2.8.dfsg-1 Versions of packages qtiplot recommends: ii qt-assistant-compat 4.6.3-6 ii qtiplot-doc 0.9.8.9-6 qtiplot suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: qtiplot Source-Version: 0.9.8.9-7 We believe that the bug you reported is fixed in the latest version of qtiplot, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 722...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Anton Gladky gl...@debian.org (supplier of updated qtiplot package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 10 Sep 2013 16:14:00 +0200 Source: qtiplot Binary: qtiplot qtiplot-doc Architecture: source amd64 all Version: 0.9.8.9-7 Distribution: unstable Urgency: high Maintainer: Debian Science Team debian-science-maintain...@lists.alioth.debian.org Changed-By: Anton Gladky gl...@debian.org Description: qtiplot- data analysis and scientific plotting qtiplot-doc - data analysis and scientific plotting (documentation) Closes: 722323 Changes: qtiplot (0.9.8.9-7) unstable; urgency=high . * Team upload. * [f4c910d] Link boost_system explicitly. (Closes: #722323) * [90606d7] Add texlive-lang-european to BD. Fix documentation generation. * [b3f2561] Update Standards-Version to 3.9.4. No changes. * [9530d73] Use canonical VCS. Checksums-Sha1: f0237bf71f4425fc2253d40e2f263dfc902623f2 2526 qtiplot_0.9.8.9-7.dsc 2867d399ac3717323181197d3cd4d92a6bb3b2fa 20891 qtiplot_0.9.8.9-7.debian.tar.gz 9d78c3a0877852cf803950751ece014d8b786e7e 2565152 qtiplot_0.9.8.9-7_amd64.deb 3b66a3f7c01f0135ae775ff0a3d121f04c504330 28630668 qtiplot-doc_0.9.8.9-7_all.deb Checksums-Sha256: 30929e588b2d730650b0971d7cb057122dc2d110b7651790c69d543cffd88c3f 2526 qtiplot_0.9.8.9-7.dsc ca143bc57cf0eabf557486b3c530def12c5afadbc065911d6ddd34be54c707d2 20891
Bug#721718: marked as done (gimp: failure to resolve symbols gegl ff-load.so: undefined symbol: av_open_input_file)
Your message dated Tue, 10 Sep 2013 16:03:26 + with message-id e1vjqpw-0004kg...@franck.debian.org and subject line Bug#721533: fixed in gegl 0.2.0-4 has caused the Debian Bug report #721533, regarding gimp: failure to resolve symbols gegl ff-load.so: undefined symbol: av_open_input_file to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 721533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: gimp Version: 2.8.6-1 Severity: grave Tags: d-i Justification: renders package unusable Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? attempting to load gimp failes with the message GEGL-geglmodule.c-Message: Module '/usr/lib/x86_64-linux-gnu/gegl-0.2/ff-load.so' load error: /usr/lib/x86_64-linux-gnu/gegl-0.2/ff-load.so: undefined symbol: av_open_input_file $ldd gimp linux-vdso.so.1 (0x7fff7dbde000) libgimpwidgets-2.0.so.0 = /usr/lib/libgimpwidgets-2.0.so.0 (0x7f9620cda000) libgtk-x11-2.0.so.0 = /usr/lib/x86_64-linux-gnu/libgtk-x11-2.0.so.0 (0x7f96206a2000) libgdk-x11-2.0.so.0 = /usr/lib/x86_64-linux-gnu/libgdk-x11-2.0.so.0 (0x7f96203ef000) libatk-1.0.so.0 = /usr/lib/x86_64-linux-gnu/libatk-1.0.so.0 (0x7f96201cc000) libdbus-glib-1.so.2 = /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2 (0x7f961ffa5000) libdbus-1.so.3 = /lib/x86_64-linux-gnu/libdbus-1.so.3 (0x7f961fd5f000) libgimpconfig-2.0.so.0 = /usr/lib/libgimpconfig-2.0.so.0 (0x7f961fb4e000) libgimpmath-2.0.so.0 = /usr/lib/libgimpmath-2.0.so.0 (0x7f961f948000) libgimpthumb-2.0.so.0 = /usr/lib/libgimpthumb-2.0.so.0 (0x7f961f73d000) libgimpcolor-2.0.so.0 = /usr/lib/libgimpcolor-2.0.so.0 (0x7f961f52f000) libgimpmodule-2.0.so.0 = /usr/lib/libgimpmodule-2.0.so.0 (0x7f961f32a000) libgimpbase-2.0.so.0 = /usr/lib/libgimpbase-2.0.so.0 (0x7f961f11) libgdk_pixbuf-2.0.so.0 = /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x7f961eef) libz.so.1 = /lib/x86_64-linux-gnu/libz.so.1 (0x7f961ecd8000) libpangocairo-1.0.so.0 = /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x7f961eaca000) libpangoft2-1.0.so.0 = /usr/lib/x86_64-linux-gnu/libpangoft2-1.0.so.0 (0x7f961e8b4000) libpango-1.0.so.0 = /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 (0x7f961e666000) libfreetype.so.6 = /usr/lib/x86_64-linux-gnu/libfreetype.so.6 (0x7f961e3c6000) libfontconfig.so.1 = /usr/lib/x86_64-linux-gnu/libfontconfig.so.1 (0x7f961e18b000) libcairo.so.2 = /usr/lib/x86_64-linux-gnu/libcairo.so.2 (0x7f961de72000) libgegl-0.2.so.0 = /usr/lib/x86_64-linux-gnu/libgegl-0.2.so.0 (0x7f961dc03000) libgmodule-2.0.so.0 = /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0 (0x7f961d9ff000) libgio-2.0.so.0 = /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x7f961d6a4000) libbabl-0.1.so.0 = /usr/lib/x86_64-linux-gnu/libbabl-0.1.so.0 (0x7f961d465000) libm.so.6 = /lib/x86_64-linux-gnu/libm.so.6 (0x7f961d167000) libgobject-2.0.so.0 = /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x7f961cf17000) libgthread-2.0.so.0 = /usr/lib/x86_64-linux-gnu/libgthread-2.0.so.0 (0x7f961cd14000) libglib-2.0.so.0 = /lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x7f961ca15000) libpthread.so.0 = /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f961c7f9000) libc.so.6 = /lib/x86_64-linux-gnu/libc.so.6 (0x7f961c44c000) libX11.so.6 = /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x7f961c111000) libXcomposite.so.1 = /usr/lib/x86_64-linux-gnu/libXcomposite.so.1 (0x7f961bf0e000) libXdamage.so.1 = /usr/lib/x86_64-linux-gnu/libXdamage.so.1 (0x7f961bd0a000) libXfixes.so.3 = /usr/lib/x86_64-linux-gnu/libXfixes.so.3 (0x7f961bb04000) libXrender.so.1 = /usr/lib/x86_64-linux-gnu/libXrender.so.1 (0x7f961b8f9000) libXinerama.so.1 = /usr/lib/x86_64-linux-gnu/libXinerama.so.1 (0x7f961b6f6000) libXi.so.6 = /usr/lib/x86_64-linux-gnu/libXi.so.6 (0x7f961b4e6000) libXrandr.so.2 = /usr/lib/x86_64-linux-gnu/libXrandr.so.2 (0x7f961b2db000) libXcursor.so.1 = /usr/lib/x86_64-linux-gnu/libXcursor.so.1 (0x7f961b0d) libXext.so.6 = /usr/lib/x86_64-linux-gnu/libXext.so.6 (0x7f961aebe000) librt.so.1 =
Processed: fixes commited
Processing commands for cont...@bugs.debian.org: tags 722045 +pending Bug #722045 [dh-python] Please support python:any dependencies for multiarch compatibility Added tag(s) pending. tags 722214 +pending Bug #722214 [dh-python] dh-python: ASCII conversion error in pybuild autotest Added tag(s) pending. tags 722307 +pending Bug #722307 [dh-python] dh-python: dh_python2 creates dependencies on non-existing python2 Added tag(s) pending. thanks Stopping processing here. Please contact me if you need assistance. -- 722045: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722045 722214: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722214 722307: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722307 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707346: edbrowse: FTBFS: jsdom.c:174:55: error: 'JS_FinalizeStub' undeclared here (not in a function)
Control: tag -1 - jessie sid As Iceweasel 17 is currently pending in proposed-updates-NEW[1] and should ideally be integrated into the next point release, this also affects stable. Could you look into preparing an update? I noticed that the fix for unstable switches to libmozjs185-dev. As far as I heard sandboxing shouldn't be regarded as secure in this version so it shouldn't be used for untrusted JS (like in web browsers). [1] http://release.debian.org/proposed-updates/stable.html Ansgar -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: edbrowse: FTBFS: jsdom.c:174:55: error: 'JS_FinalizeStub' undeclared here (not in a function)
Processing control commands:
tag -1 - jessie sid
Bug #707346 {Done: Samuel Thibault sthiba...@debian.org} [src:edbrowse]
edbrowse: FTBFS: jsdom.c:174:55: error: 'JS_FinalizeStub' undeclared here (not
in a function)
Removed tag(s) sid and jessie.
--
707346: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707346
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: chmsee: requires update in stable for xulrunner-17.0
Processing control commands: fixed -1 2.0.1-1 Bug #722401 [src:chmsee] chmsee: requires update in stable for xulrunner-17.0 Marked as fixed in versions chmsee/2.0.1-1. -- 722401: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722401: chmsee: requires update in stable for xulrunner-17.0
Source: chmsee Version: 1.99.10-1 Severity: serious Control: fixed -1 2.0.1-1 chmsee fails to build in stable against xulrunner-17.0: xpidl.IDLError: error: type 'PRUint32' not found, csIChm.idl line 33:17 readonly attribute PRUint32 lcid; ^ As Iceweasel 17 is currently pending in proposed-updates-NEW[1] and should ideally be integrated into the next point release, this should be fixed. Could you look into preparing an update? I noticed that there will be an additional update needed, also for unstable (2.0.2 fixed issues with xulrunner-22.0) and that upstream stopped maintaining the software[2]: ChmSee is not being developed anymore. So you either have to take over upstream maintenance or the package will likely have to be removed in the near future anyway. [1] http://release.debian.org/proposed-updates/stable.html [2] https://code.google.com/p/chmsee/ Ansgar -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721672: marked as done (libconfig-model-dpkg-perl: cme fix dpkg-copyright may cause data loss if there is a paragraph with File: instead of Files:)
Your message dated Tue, 10 Sep 2013 18:18:10 + with message-id e1vjsvu-00023s...@franck.debian.org and subject line Bug#721672: fixed in libconfig-model-dpkg-perl 2.040 has caused the Debian Bug report #721672, regarding libconfig-model-dpkg-perl: cme fix dpkg-copyright may cause data loss if there is a paragraph with File: instead of Files: to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 721672: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721672 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libconfig-model-dpkg-perl Severity: grave Version: 2.038 Justification: may cause data loss Hi, cme fix dpkg-copyright deleted the following paragraph from debian/copyright completely: File: debian/patches/half_code_pod_errors.patch Copyright: 2010, Frank Wiegand f...@cpan.org License: Artistic or GPL-1+ Reason seems that the author of the paragraph changed Files to File because it affected only one file. Yes, I know, this is incorrect syntax, but I would expect fix to fix such stuff, not to just delete it. (Feel free to downgrade the severity if the tool is really not intended to work which don't abide 100% to the correct syntax (or an older version of the syntax.) Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 ---End Message--- ---BeginMessage--- Source: libconfig-model-dpkg-perl Source-Version: 2.040 We believe that the bug you reported is fixed in the latest version of libconfig-model-dpkg-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 721...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dominique Dumont d...@debian.org (supplier of updated libconfig-model-dpkg-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 08 Sep 2013 21:03:40 +0200 Source: libconfig-model-dpkg-perl Binary: libconfig-model-dpkg-perl Architecture: source all Version: 2.040 Distribution: unstable Urgency: low Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: Dominique Dumont d...@debian.org Description: libconfig-model-dpkg-perl - editor for Dpkg source files with validation Closes: 721663 721670 721672 721832 Changes: libconfig-model-dpkg-perl (2.040) unstable; urgency=low . * All: fix white space and extraneous line issue (Closes: #721832) * dpkg-copyright: * skip empty-ish license * append second occurrence of an entry (Closes: #721670) * convert File section into Files (Closes: #721672) * dpkg-control: + added support for XS-Testsuite (Thanks Stig) (Closes: #721663) * added tests for xs-testsuite (Thanks Stig) * control: BD on libconfig-model-tester = 2.044 to test white space fix Checksums-Sha1: 8c02ef075ad5b709596ae96f359a12387f38d3b0 2315 libconfig-model-dpkg-perl_2.040.dsc 3df93fd5387f58cac747230d7fc7e6c9950f487d 79136 libconfig-model-dpkg-perl_2.040.tar.gz ea446d56917aae3835ebc055f9b1bf00175ddeb6 100700 libconfig-model-dpkg-perl_2.040_all.deb Checksums-Sha256: e41676eb448eefe778c10535cfb8cf6a02721de7867f661ef017ba8e32eda7e6 2315 libconfig-model-dpkg-perl_2.040.dsc 5872b56d9f2c37b62067acf5415a640474e0eea173a321c6264ce3af627ef11d 79136 libconfig-model-dpkg-perl_2.040.tar.gz 93ea5d301b10b38eedb228656a18c4a2ffeb85fe943f897ad154bd3733a9c5f9 100700 libconfig-model-dpkg-perl_2.040_all.deb Files: 8363209a376014e68d5c05a26a140ecc 2315 perl optional libconfig-model-dpkg-perl_2.040.dsc a78e35dbf58094a85232345d0ad46715 79136 perl optional libconfig-model-dpkg-perl_2.040.tar.gz 36cb1ba315684a8ea5499c9b7ac475b5 100700 perl optional libconfig-model-dpkg-perl_2.040_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) iQIcBAEBAgAGBQJSL18xAAoJEMMfT9lJqytsVjMP/3qtR/gVf86fnbpDyUd85qFQ g3UNcxo37Xnju5Y7EpeG71O7m2aL4fP30MGPJbQ/nvnIS3JH0HcdOlTARg2+jY9b 03rcOzp5k4au9S1i65xzUN5x66Rp/aggtFPldURhR5vzI0DO54ZNiG3q8dVjqVBR
Bug#722283: marked as done (libuv: FTBFS with test suite errors)
Your message dated Tue, 10 Sep 2013 18:18:18 + with message-id e1vjsw2-000289...@franck.debian.org and subject line Bug#722283: fixed in libuv 0.10.8-0~exp3 has caused the Debian Bug report #722283, regarding libuv: FTBFS with test suite errors to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 722283: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722283 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: libuv Version: 0.10.8-0~exp2 Severity: serious Justification: fails to build from source Automated builds of libuv on Linux failed with test suite errors. (Builds for other platforms didn't even compile; I'll report that separately.) To wit: * test-tty fails because automated builds don't bother allocating ttys. Please try arranging to run the test suite under script(1): LD_PRELOAD=$(CURDIR)/libuv.so script -q -c ./run-tests /dev/null * Most of the udp tests fail. I'm not sure why, but suspect a quirk of the autobuilders' configuration, which might require disabling those tests altogether. :-/ Could you please take a look? You can find the full logs at https://buildd.debian.org/status/logs.php?pkg=libuvver=0.10.8-0~exp2 Thanks! ---End Message--- ---BeginMessage--- Source: libuv Source-Version: 0.10.8-0~exp3 We believe that the bug you reported is fixed in the latest version of libuv, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 722...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Luca Bruno lu...@debian.org (supplier of updated libuv package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 10 Sep 2013 19:26:24 +0200 Source: libuv Binary: libuv-dev libuv0.10 libuv0.10-dbg Architecture: source amd64 Version: 0.10.8-0~exp3 Distribution: experimental Urgency: low Maintainer: Debian Javascript Maintainers pkg-javascript-de...@lists.alioth.debian.org Changed-By: Luca Bruno lu...@debian.org Description: libuv-dev - asynchronous event notification library - development files libuv0.10 - asynchronous event notification library - runtime library libuv0.10-dbg - asynchronous event notification library - debugging symbols Closes: 722283 Changes: libuv (0.10.8-0~exp3) experimental; urgency=low . * Fix test suite errors (Closes: #722283) + Adjust test runner invocation for missing TTY on buildd + Backport patch: fix setsockopt(SO_REUSEPORT) error handling Checksums-Sha1: a1793a36b0c393d7ee45cd50efc032cbdcfdfa65 1390 libuv_0.10.8-0~exp3.dsc 55b6fbc9e8fe548bfdf72762eded500104f91d2c 6073 libuv_0.10.8-0~exp3.debian.tar.gz fc2fa9995851455f86cf9345e972c7722ebdd875 83508 libuv-dev_0.10.8-0~exp3_amd64.deb 1db40cd28244d2a785d6fdab94042bd82dcf9d5d 52168 libuv0.10_0.10.8-0~exp3_amd64.deb f25bc7ad72335855b5ae4254bc603789df144b2d 157732 libuv0.10-dbg_0.10.8-0~exp3_amd64.deb Checksums-Sha256: a983e2993b4b618076966045d7c1ff1f3eb6d719681d33b2471f6055ce690b61 1390 libuv_0.10.8-0~exp3.dsc 0523489554ef4cfb3a1ce3b25c241da436d97b4e72645d4412386b7cc18be864 6073 libuv_0.10.8-0~exp3.debian.tar.gz 94cf617bdec7811929496d5c8e0ef7d6977afc4ca69116598f6f01656404306f 83508 libuv-dev_0.10.8-0~exp3_amd64.deb ea1617d48db2458bdbf8c8e3d854ee03e08624a1b43ca0583d5f17ed7d630f44 52168 libuv0.10_0.10.8-0~exp3_amd64.deb c68eb0d7fc3ee13ee6b9fbc84e57cd7ec159d8001f9720751a1e2f42daeaf9ba 157732 libuv0.10-dbg_0.10.8-0~exp3_amd64.deb Files: 823b983b53e5c400a7268a2535fe9272 1390 libs optional libuv_0.10.8-0~exp3.dsc 3972a17eaa67dd7ec58fc73f739a36f2 6073 libs optional libuv_0.10.8-0~exp3.debian.tar.gz 802db3564bb53ea53139dfacade3d42c 83508 libdevel optional libuv-dev_0.10.8-0~exp3_amd64.deb 31d7c114caa5759afc5bdc2af9e8e361 52168 libs optional libuv0.10_0.10.8-0~exp3_amd64.deb f41482ae071136ca4705f86caf6141c2 157732 debug extra libuv0.10-dbg_0.10.8-0~exp3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) iEYEARECAAYFAlIvXuQACgkQRqobajv7n7MUDQCdEWRtuMwGVyQRqLZhYCRqL/nQ 9nUAn3Xi22ehNme5is8m7BBmE/znS0LS =/Auk -END PGP SIGNATUREEnd Message---
Bug#721670: marked as done (libconfig-model-dpkg-perl: cme fix dpkg-copyright may cause data loss if there are two Copyright fields in one paragraph)
Your message dated Tue, 10 Sep 2013 18:18:10 + with message-id e1vjsvu-00023m...@franck.debian.org and subject line Bug#721670: fixed in libconfig-model-dpkg-perl 2.040 has caused the Debian Bug report #721670, regarding libconfig-model-dpkg-perl: cme fix dpkg-copyright may cause data loss if there are two Copyright fields in one paragraph to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 721670: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721670 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libconfig-model-dpkg-perl Severity: grave Version: 2.038 Justification: may cause data loss Hi, I had a package (libbenchmark-timer-perl) with the following paragraph in debian/copyright: Files: * Copyright: (c) 2000-2001 Andrew Ho Copyright: (c) 2004 David Coppit The original code (written before April 20, 2001) was written by Andrew Ho and...@zeuscat.com, and is copyright (c) 2000-2001 Andrew Ho. […] cme fix dpkg-copyright modified that paragraph as follows: Files: * -Copyright: (c) 2000-2001 Andrew Ho Copyright: (c) 2004 David Coppit The original code (written before April 20, 2001) was written by Andrew Ho and...@zeuscat.com, and is copyright (c) 2000-2001 Andrew Ho. Versions up to i.e. it removed one of the (errornously) two Copyright fields. IMHO the only sane way to automatically handle such cases is to concatenate, i.e. merge the values of these two fields: Files: * Copyright: (c) 2000-2001 Andrew Ho -Copyright: (c) 2004 David Coppit + (c) 2004 David Coppit The original code (written before April 20, 2001) was written by Andrew Ho and...@zeuscat.com, and is copyright (c) 2000-2001 Andrew Ho. Versions up to 0.5 are distributed under the same terms as Perl. Final and manually fixed and improved commit was http://deb.li/3aP7A Please check if this may also happen for other multiple field occurrences in one paragraph. But in any case, the data loss in the Copyright field is probably the worst which can happen. (And yes, this happened before 2.039 was uploaded.) Regards, Axel -- ,''`. | Axel Beckert a...@debian.org, http://people.debian.org/~abe/ : :' : | Debian Developer, ftp.ch.debian.org Admin `. `' | 1024D: F067 EA27 26B9 C3FC 1486 202E C09E 1D89 9593 0EDE `-| 4096R: 2517 B724 C5F6 CA99 5329 6E61 2FF9 CD59 6126 16B5 ---End Message--- ---BeginMessage--- Source: libconfig-model-dpkg-perl Source-Version: 2.040 We believe that the bug you reported is fixed in the latest version of libconfig-model-dpkg-perl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 721...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Dominique Dumont d...@debian.org (supplier of updated libconfig-model-dpkg-perl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Sun, 08 Sep 2013 21:03:40 +0200 Source: libconfig-model-dpkg-perl Binary: libconfig-model-dpkg-perl Architecture: source all Version: 2.040 Distribution: unstable Urgency: low Maintainer: Debian Perl Group pkg-perl-maintain...@lists.alioth.debian.org Changed-By: Dominique Dumont d...@debian.org Description: libconfig-model-dpkg-perl - editor for Dpkg source files with validation Closes: 721663 721670 721672 721832 Changes: libconfig-model-dpkg-perl (2.040) unstable; urgency=low . * All: fix white space and extraneous line issue (Closes: #721832) * dpkg-copyright: * skip empty-ish license * append second occurrence of an entry (Closes: #721670) * convert File section into Files (Closes: #721672) * dpkg-control: + added support for XS-Testsuite (Thanks Stig) (Closes: #721663) * added tests for xs-testsuite (Thanks Stig) * control: BD on libconfig-model-tester = 2.044 to test white space fix Checksums-Sha1: 8c02ef075ad5b709596ae96f359a12387f38d3b0 2315 libconfig-model-dpkg-perl_2.040.dsc 3df93fd5387f58cac747230d7fc7e6c9950f487d 79136 libconfig-model-dpkg-perl_2.040.tar.gz ea446d56917aae3835ebc055f9b1bf00175ddeb6 100700 libconfig-model-dpkg-perl_2.040_all.deb Checksums-Sha256:
Bug#722002: ampache-common: Unsatisfiable dependency on php-getid3
On Tue, Sep 10, 2013 at 12:20 AM, Adam D. Barratt a...@adam-barratt.org.ukwrote: On Fri, 2013-09-06 at 16:08 -0400, Jeremy Bicha wrote: ampache-common depends on php-getid3 ( 1.9.6.0~), php-getid3 (= 1.9.6), but the version of php-getid3 in unstable is 1.9.6-1. So, in a small case of being unable to see the wood for the trees... that dependency /is/ satisfiable, even if it's not what the maintainer thinks it should be: $ dpkg --compare-versions 1.9.6-1 lt 1.9.6.0~ echo y y $ dpkg --compare-versions 1.9.6-1 gt 1.9.6 echo y y This is indeed good news. Thank you for going the extra mile on this. :) If there are no objections I will close this bug in the next day or so. -- Charlie Smotherman Debian Contributor Ubuntu Developer
Bug#704785: OGRE's FTBFS #713640 affects other packages
On Tue, 2013-09-10 at 19:49 +0100, Manuel A. Fernandez Montecelo wrote: Boost.Thread depends on some non header-only libraries. Boost.System: This dependency is mandatory and you will need to link with the library. Since Boost has no pkg-config or similar mechanism... Don't you agree with this? I don't know what you propose to do instead in Boost, if they don't have this pkg-config-like mechanism. I wasn't aware of this fact, how annoying. Yes in this situation the current solution is the right one. It would be great if boost used pkg-config (and similar on non-Linux platforms) but I don't expect you to work on that :) -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#704785: OGRE's FTBFS #713640 affects other packages
2013/9/10 Paul Wise p...@debian.org: On Mon, 2013-09-09 at 18:24 +0100, Manuel A. Fernandez Montecelo wrote: I uploaded 1.8.0+dfsg1-6 today, modifying the pkg-config files to emit -lboost_system, can you please give it a try when available? That works as a work-around, the proper fix would be to boost though so I would appreciate if you could get it fixed there and then revert the workaround in ogre-1.8. I'm uploading funguloids now, thanks. From http://www.boost.org/doc/libs/1_54_0/doc/html/thread/build.html: Boost.Thread depends on some non header-only libraries. Boost.System: This dependency is mandatory and you will need to link with the library. Since Boost has no pkg-config or similar mechanism (as other programs have, e.g. sdl2-config), as far as I can tell, it's up to the users of the library to link against Boost::System. So for me it seems natural which is OGRE the one which should do what it's doing now (telling users of the library that they should also link agains blah and blah, as it's already done for freeimage library for example), not the users of OGRE (e.g. funguloids) and not Boost (since they don't have the pkg-config-like mechanism). Don't you agree with this? I don't know what you propose to do instead in Boost, if they don't have this pkg-config-like mechanism. Cheers. -- Manuel A. Fernandez Montecelo manuel.montez...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704785: OGRE's FTBFS #713640 affects other packages
2013/9/10 Paul Wise p...@debian.org: On Tue, 2013-09-10 at 19:49 +0100, Manuel A. Fernandez Montecelo wrote: Boost.Thread depends on some non header-only libraries. Boost.System: This dependency is mandatory and you will need to link with the library. Since Boost has no pkg-config or similar mechanism... Don't you agree with this? I don't know what you propose to do instead in Boost, if they don't have this pkg-config-like mechanism. I wasn't aware of this fact, how annoying. Yes in this situation the current solution is the right one. It would be great if boost used pkg-config (and similar on non-Linux platforms) but I don't expect you to work on that :) OK. So thanks for uploading the new version of funguloids, now OGRE 1.7 is almost ready to go. BTW I think that this one can be closed: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689215 Cheers. -- Manuel A. Fernandez Montecelo manuel.montez...@gmail.com -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721166: ffdiaporama: depends on ffmpeg which is going away
On 2013-09-10 21:26:03, Fabrice Coutadeur wrote: Hi Sebastian, yes: the tests I did with that version was successful at that time. The other option is to update to 1.6, but I'm not sure it is compatible with libav 0.9. It may be a 2 step upload: first, 1.5-2, to unblock the transition and then update to 1.6, with more time. What do you think? Getting 1.5-2 in first and waiting with 1.6 until after the libav transition sounds like a good plan. I'll have a look 1.5-2 now. Regards -- Sebastian Ramacher signature.asc Description: Digital signature
Bug#721851: taskcoach: uninstallable in sid: Depends: python-keyring ( 1.6.0~) but 2.1-1 is to be installed
There's still a very narrow dependency on apscheduler which looks like it will cause headaches in the future: python-apscheduler ( 2.1.0.0~), python-apscheduler (= 2.1.0) Jeremy -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721025: spek: FTBFS with spek-fft.cc:31:82: error: 'malloc' was not declared in this scope
Sebastian Ramacher wrote: Source: spek Version: 0.8.2-1 Severity: serious Justification: FTBFS but built successfully in the past Tags: jessie sid Control: block 706798 by -1 spek currently FTBFS: | g++ -DHAVE_CONFIG_H -I. -I.. -include config.h -pthread -I/usr/lib/x86_64-linux-gnu/wx/include/gtk2-unicode-release-2.8 -I/usr/include/wx-2.8 -D_FILE_OFFSET_BITS=64 -D_LARGE_FILES -D__WXGTK__ -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security -std=gnu++11 -Wall -Wextra -c -o libspek_a-spek-fft.o `test -f 'spek-fft.cc' || echo './'`spek-fft.cc | spek-fft.cc: In function 'spek_fft_plan* spek_fft_plan_new(int)': | spek-fft.cc:31:82: error: 'malloc' was not declared in this scope | struct spek_fft_plan *p = (spek_fft_plan*)malloc(sizeof(struct spek_fft_plan)); | ^ | spek-fft.cc: In function 'void spek_fft_delete(spek_fft_plan*)': | spek-fft.cc:67:11: error: 'free' was not declared in this scope | free(p); |^ | make[3]: *** [libspek_a-spek-fft.o] Error 1 The full build log is available from http://people.debian.org/~sramacher/logs/spek_0.8.2-1_amd64-20130826-1853.log This bug is marked pending for a week and it would be good to have a fixed package soon (spek is part of the libav9 transition). Do you need a sponsor? Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721533: FTBFS: unresolved symbols with libav 9
Sebastian Ramacher wrote:
Source: gegl
Version: 0.20-3
Severity: normal
Tags: sid jessie
While being rebuilt for the libav 9 I noticed that ff-load.so now
contains unresolved symbols and is unusable:
| GEGL-geglmodule.c-Message: Module
'../../operations/external/.libs/ff-load.so' load error:
../../operations/external/.libs/ff-load.so: undefined symbol:
av_open_input_file
Using severity normal for now since I don't know how important
ff-load.so is for gegl.
Patch attached. I'm pretty sure this will also fix the build failures
on s390.
Cheers,
Moritz
--- gegl-0.2.0.orig/operations/external/ff-load.c 2012-04-01 13:17:57.0 +0200
+++ gegl-0.2.0/operations/external/ff-load.c 2013-09-06 00:16:39.01200 +0200
@@ -271,7 +271,7 @@
gint err;
ff_cleanup (o);
- err = av_open_input_file (p-ic, o-path, NULL, 0, NULL);
+ err = avformat_open_input (p-ic, o-path, NULL, NULL);
if (err 0)
{
print_error (o-path, err);
Bug#720661: kino: FTBFS: 'URL_WRONLY' was not declared in this scope
On Sat, Aug 24, 2013 at 01:00:43PM +0100, Dominic Hargreaves wrote: Source: kino Version: 1.3.4-1.3 Severity: serious Justification: FTBFS Tags: sid jessie This package FTBGS in a clean sid chroot: frame.cc:1478:60: error: 'URL_WRONLY' was not declared in this scope url_open_buf( avformatEncoder-pb, data, bytesInFrame, URL_WRONLY ); ^ frame.cc:1478:71: error: 'url_open_buf' was not declared in this scope url_open_buf( avformatEncoder-pb, data, bytesInFrame, URL_WRONLY ); ^ frame.cc:1482:38: error: 'av_write_header' was not declared in this scope av_write_header( avformatEncoder ); ^ frame.cc:1487:39: error: 'url_close_buf' was not declared in this scope url_close_buf( avformatEncoder-pb ); Patches attached to fix compilation with libav 9. Cheers, Moritz -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704785: OGRE's FTBFS #713640 affects other packages
On Tue, 2013-09-10 at 20:05 +0100, Manuel A. Fernandez Montecelo wrote: BTW I think that this one can be closed: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=689215 Done. -- bye, pabs http://wiki.debian.org/PaulWise signature.asc Description: This is a digitally signed message part
Bug#700061: No usable local backends
I can attest to this package's usefulness as far as using it for the remote driver to access a selenium grid. In addition, there is a phantomjs package currently in unstable: http://packages.debian.org/unstable/web/phantomjs Phantomjs *can* be used as a local backend as of python-selenium 2.27 (the current version on PiPi is 2.35). So if the package gets and update it might resolve this issue. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710068: marked as done (tiger: postinst uses /usr/share/doc content (Policy 12.3))
Your message dated Tue, 10 Sep 2013 21:21:36 + with message-id e1vjvnq-0006ff...@franck.debian.org and subject line Bug#710068: fixed in tiger 1:3.2.3-11 has caused the Debian Bug report #710068, regarding tiger: postinst uses /usr/share/doc content (Policy 12.3) to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 710068: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710068 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: tiger Version: 1:3.2.3-10 Severity: serious User: debian...@lists.debian.org Usertags: piuparts Hi, a test with piuparts revealed that your package uses files from /usr/share/doc in its maintainer scripts which is a violation of Policy 12.3: Packages must not require the existence of any files in /usr/share/doc/ in order to function. http://www.debian.org/doc/debian-policy/ch-docs.html#s12.3 These files must be moved to /usr/share/$PACKAGE and may be symlinked from /usr/share/doc/$PACKAGE. This piuparts test prevents the installation of (most) files into /usr/share/doc with 'dpkg --path-exclude=...'. From the attached log (scroll to the bottom...): Selecting previously unselected package tiger. (Reading database ... 7084 files and directories currently installed.) Unpacking tiger (from .../tiger_1%3a3.2.3-10_amd64.deb) ... Setting up tiger (1:3.2.3-10) ... ERROR in maintainer script, cannot find package configuration file at /usr/share/doc/tiger/examples/tigerrc.gz dpkg: error processing tiger (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: tiger Cheers, Andreas tiger_1:3.2.3-10.log.gz Description: GNU Zip compressed data ---End Message--- ---BeginMessage--- Source: tiger Source-Version: 1:3.2.3-11 We believe that the bug you reported is fixed in the latest version of tiger, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 710...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Javier Fernández-Sanguino Peña j...@debian.org (supplier of updated tiger package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Thu, 05 Sep 2013 07:11:59 +0200 Source: tiger Binary: tiger tiger-otheros Architecture: source i386 Version: 1:3.2.3-11 Distribution: unstable Urgency: low Maintainer: Javier Fernández-Sanguino Peña j...@debian.org Changed-By: Javier Fernández-Sanguino Peña j...@debian.org Description: tiger - Report system security vulnerabilities tiger-otheros - Scripts to run Tiger in other operating systems Closes: 511970 687937 690644 696510 708360 709065 710068 Changes: tiger (1:3.2.3-11) unstable; urgency=low . * debian/postinst, debian/rules: Do not use example file at /usr/share/doc/tiger for the configuration. Copy the example file to /usr/share/tiger and use it from there instead (Closes: #710068) * debian/rules: - Add the issue and issue.net example files provided into /usr/share/doc/tiger/examples. - Remove auto-generated config files when cleaning just in case Makefile didn't take care of them [ Updated with upstream content in GIT repository. The following is a list of changes relevant to Debian as they close existing bugs. ] * scripts/check_known: Determine properly the kernel version to decide whether to user ifconfig (or not) (Closes: #708360, #709065, #687937) * Make util/mkfilelst a bash script since it uses a sourced script with arguments (Closes: #690644) - Note: We ignore other bashims reported in the bug reported due to the use of HOSTNAME since the Tiger configuration file ensures that the HOSTNAME variable is properly set before using any of these scripts. This variable is defined using the proper binary in the system/OPERATING_SYSTEM/config scripts. * systems/Linux/2/services: Update services definition to prevent false positives report on duplicated service names (Closes: #696510) * scripts/check_issue: Do not require there to be administrative-provided files to compare with. If they are not found, warn instead that we
Bug#722406: liblensfun does not provide correct versioning info (shlibs/symbol)
Package: liblensfun0 Version: 0.2.7-2 Severity: serious liblensfun0 does not provide correct versioning info as described in policy 8.6. -- (sid-AMD64)ametzler@argenau:$ cat /var/lib/dpkg/info/liblensfun0.shlibs liblensfun 0 liblensfun0 -- The shlibs is unversioned, although 0.2.7 exports a lot of additional symbols (e.g. _ZNK6lfLens15InterpolateCropEfR15lfLensCalibCrop or lf_get_crop_desc@Base) compared to 0.2.5. cu Andreas -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721432: awesome: Memory leak (at least) when switching windows
Hi, turns out that this is ultimately a bug in Pango. However, a work-around was just committed to lua-lgi upstream: https://github.com/pavouk/lgi/commit/ec3dfe88ce013e78246b22adce88a2c97a934005 Uli -- Why make things difficult, when it is possible to make them cryptic and totally illogical, with just a little bit more effort? -- A. P. J. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722431: tcl-snack-dev: Unable to install due to dependencies and conflicts
Package: tcl-snack-dev Version: 2.2.10.20090623-dfsg-3 Severity: grave Justification: renders package unusable I just tried to install tcl-snack-dev, but my system reports that: 1) tcl-snack-dev depends on tcl-snack; 2) tcl-snack depends on libsnack-alsa AND provides libsnack2; 3) libsnack-alsa conflicts with libsnack2. This makes the package uninstallable on my system. Am I doing something wrong? Bests, Giulio. -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.9.3geppetto (SMP w/2 CPU cores) Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8) 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#722121: installing `gir1.2-gtk-3.0` doesn't fix this bug here
On Tue, 10 Sep 2013 23:24:25 +0900 Osamu Aoki os...@debian.org wrote: Hi, Hi, On Mon, Sep 09, 2013 at 08:44:48PM +0200, Ivan Sergio Borgonovo wrote: I can confirm the problem and having installed gir1.2-gtk-3.0 doesn't seem to work here. Question is what ibus modules are you using. If you are using ibus-* packages listed as bad in http://release.debian.org/transitions/html/ibus1.5.html Some were in the list. Thanks for pointing me at that table. This is expected situation under sid during transition. Please let me know what packages you use. I had installed some of the package listed. After uninstalling some of the listed ones with the exception of kdeplasma-addons, ibus-setup starts and I can type Chinese (quick and cangjie), but I really don't know what I'm doing. You'll have to wait the rest of my family comes back if you need a more meaningful feedback. I've tested xkbc but I don't know what to expect either. It's just writing latin alphabet and I can't see any composing box. Let me know if I can do more tests. This is the list of ibus related packages I've now installed on my box (just finished to update/safe-upgrade sid). ibus ibus-array ibus-chewing ibus-clutter ibus-googlepinyin ibus-gtk ibus-gtk3 ibus-libpinyin ibus-m17n ibus-pinyin-db-android ibus-qt4 ibus-table ibus-table-array30 ibus-table-cangjie-big ibus-table-cangjie3 ibus-table-cangjie5 ibus-table-cantonese ibus-table-cantonhk ibus-table-cns11643 ibus-table-compose ibus-table-easy ibus-table-easy-big ibus-table-erbi ibus-table-erbi-qs ibus-table-extraphrase ibus-table-ipa-x-sampa ibus-table-jyutping ibus-table-quick ibus-table-quick-classic ibus-table-quick3 ibus-table-quick5 ibus-table-scj6 ibus-table-stroke5 ibus-table-wu ibus-table-wubi ibus-table-yawerty ibus-table-yong ibus-xkbc thanks. -- Ivan Sergio Borgonovo http://www.webthatworks.it -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721533: marked as done (gegl: unresolved symbols with libav 9)
Your message dated Tue, 10 Sep 2013 16:03:26 + with message-id e1vjqpw-0004kg...@franck.debian.org and subject line Bug#721533: fixed in gegl 0.2.0-4 has caused the Debian Bug report #721533, regarding gegl: unresolved symbols with libav 9 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 721533: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721533 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: gegl Version: 0.20-3 Severity: normal Tags: sid jessie While being rebuilt for the libav 9 I noticed that ff-load.so now contains unresolved symbols and is unusable: | GEGL-geglmodule.c-Message: Module '../../operations/external/.libs/ff-load.so' load error: ../../operations/external/.libs/ff-load.so: undefined symbol: av_open_input_file Using severity normal for now since I don't know how important ff-load.so is for gegl. For a full build log see https://buildd.debian.org/status/fetch.php?pkg=geglarch=amd64ver=0.2.0-3+b1stamp=1377707473 Regards -- Sebastian Ramacher signature.asc Description: Digital signature ---End Message--- ---BeginMessage--- Source: gegl Source-Version: 0.2.0-4 We believe that the bug you reported is fixed in the latest version of gegl, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 721...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Matteo F. Vescovi mfv.deb...@gmail.com (supplier of updated gegl package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Mon, 09 Sep 2013 17:40:09 +0200 Source: gegl Binary: gegl libgegl-0.2-0 libgegl-dev libgegl-doc libgegl-0.2-0-dbg Architecture: source all amd64 Version: 0.2.0-4 Distribution: unstable Urgency: low Maintainer: Matteo F. Vescovi mfv.deb...@gmail.com Changed-By: Matteo F. Vescovi mfv.deb...@gmail.com Description: gegl - Generic Graphics Library Test Program libgegl-0.2-0 - Generic Graphics Library libgegl-0.2-0-dbg - Generic Graphics Library (debugging symbols) libgegl-dev - Generic Graphics Library (development files) libgegl-doc - Generic Graphics Library (documentation) Closes: 721533 Changes: gegl (0.2.0-4) unstable; urgency=low . * debian/patches/: patchset updated - debian/patches/cve-2012-4433.patch renamed to 0001-Fix_CVE-2012-4433.patch - 0002-Port_gegl_forward_to_libav54.patch added (Closes: #721533) Checksums-Sha1: ffd63de6cdacf0b6d1451b3d8820fa8301e78bea 2476 gegl_0.2.0-4.dsc f8153a5e94200054df7a135188660ab2a560a697 9892 gegl_0.2.0-4.debian.tar.gz 00af2a825bb5ee0e5d1231bc68b48943d2ba6158 1417856 libgegl-doc_0.2.0-4_all.deb acab84f3cbdfcd0dfd72da5e84a3ca0a2c815fdd 158890 gegl_0.2.0-4_amd64.deb eb91e12c1623ac6b8c804b8ea231e7cd2756c3b8 533106 libgegl-0.2-0_0.2.0-4_amd64.deb 125d78d5f6dcfb2c081e75526c3e5e5fdc1d7d1a 201744 libgegl-dev_0.2.0-4_amd64.deb 6b0d9c9141c69e8f7f52bb217e09df5da589a0d9 2030922 libgegl-0.2-0-dbg_0.2.0-4_amd64.deb Checksums-Sha256: e64308647b4ee2bb0c01caeae03799bbfe33cb5a015aa69be00ec0e84e6008ab 2476 gegl_0.2.0-4.dsc d175ade1f3021bf306205ef4944de214e0c83520127ddc8e205e4b889365b9a8 9892 gegl_0.2.0-4.debian.tar.gz bbd689e2a8eb87f261af3db75587ec0218382a4ed97ef331d0c31b9b92b0dc77 1417856 libgegl-doc_0.2.0-4_all.deb a60d535d302333ac7488f2b3f16710d6ce3d3826a7895e6e2ca6a6fdfe49241c 158890 gegl_0.2.0-4_amd64.deb b5b3a85a21d6aac4300c4eb11fe6fad3b203acc300a7cc1b414714f27dae112f 533106 libgegl-0.2-0_0.2.0-4_amd64.deb db4970e5ab08c146d93f805dc87c5adce732fbdd4bc0737034a5b01890a87def 201744 libgegl-dev_0.2.0-4_amd64.deb 2fed723b1e0c7470afcd43ea506fc790d3f13188d3c04b3fdf6bb4ce6081d550 2030922 libgegl-0.2-0-dbg_0.2.0-4_amd64.deb Files: 55fa0528e0a820a29129465bdf6384d6 2476 libs optional gegl_0.2.0-4.dsc 071fc0f540dc1b10f0fcbd49e1e70de5 9892 libs optional gegl_0.2.0-4.debian.tar.gz d234808588ab9c62784f9ade554ed009 1417856 doc optional libgegl-doc_0.2.0-4_all.deb 790849508fe10a0985e664b4de9a111f 158890 libs optional gegl_0.2.0-4_amd64.deb d7d3384f04a70703e23ec72180698302 533106 libs optional libgegl-0.2-0_0.2.0-4_amd64.deb 287a0dbceb17caee6ac77f377d50962a 201744 libdevel optional libgegl-dev_0.2.0-4_amd64.deb
Processed: reassign 707641 to cryptsetup
Processing commands for cont...@bugs.debian.org: reassign 707641 cryptsetup Bug #707641 [initramfs-tools] overriding root device on TS-419 non-working Bug reassigned from package 'initramfs-tools' to 'cryptsetup'. Ignoring request to alter found versions of bug #707641 to the same values previously set Ignoring request to alter fixed versions of bug #707641 to the same values previously set thanks Stopping processing here. Please contact me if you need assistance. -- 707641: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707641 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721851: taskcoach: strict dependencies caused by dh_linktree
Package: taskcoach Followup-For: Bug #721851 Taskcoach embeds 2.0.3 and patches it. Using the python-apscheduler Debian package (now 2.1.0) would require very intrusive changes, so I use the patched version. The easy way is to completely ignore the packaged python-apscheduler. But code duplication of whole source files in the archive is bad in the long term. Else, I may link at least identical files, and Depend: python-apscheduler with the exact version available during the build. But narrow dependencies are bad in the long term. Any idea to avoid such a dilemna? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: Re: Bug#722332: libcommon-sense-perl: common::sense runs into trouble with Perl 5.18, eg. no say().
Processing commands for cont...@bugs.debian.org: tag 722332 + confirmed Bug #722332 [libcommon-sense-perl] libcommon-sense-perl: common::sense runs into trouble with Perl 5.18, eg. no say(). Added tag(s) confirmed. kthxbye Stopping processing here. Please contact me if you need assistance. -- 722332: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722332 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Processed: block 722349 with 722406
Processing commands for cont...@bugs.debian.org: # after the shlibs is fixed, hugin can be rebuilt to get correct depedencies. block 722349 with 722406 Bug #722349 [hugin] hugin crashes on picture load 722349 was not blocked by any bugs. 722349 was not blocking any bugs. Added blocking bug(s) of 722349: 722406 thanks Stopping processing here. Please contact me if you need assistance. -- 722349: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722349 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#720661: kino: FTBFS: 'URL_WRONLY' was not declared in this scope
On Sat, Aug 24, 2013 at 01:00:43PM +0100, Dominic Hargreaves wrote:
Source: kino
Version: 1.3.4-1.3
Severity: serious
Justification: FTBFS
Tags: sid jessie
This package FTBGS in a clean sid chroot:
frame.cc:1478:60: error: 'URL_WRONLY' was not declared in this scope
url_open_buf( avformatEncoder-pb, data, bytesInFrame, URL_WRONLY );
^
frame.cc:1478:71: error: 'url_open_buf' was not declared in this scope
url_open_buf( avformatEncoder-pb, data, bytesInFrame, URL_WRONLY );
^
frame.cc:1482:38: error: 'av_write_header' was not declared in this scope
av_write_header( avformatEncoder );
^
frame.cc:1487:39: error: 'url_close_buf' was not declared in this scope
url_close_buf( avformatEncoder-pb );
Patches now really attached.
Cheers,
Moritz
diff -aur kino-1.3.4.orig/src/frame.cc kino-1.3.4/src/frame.cc
--- kino-1.3.4.orig/src/frame.cc 2013-09-06 00:14:45.22400 +0200
+++ kino-1.3.4/src/frame.cc 2013-09-06 00:15:26.49200 +0200
@@ -101,8 +101,8 @@
#if defined(HAVE_LIBAVCODEC)
pthread_mutex_lock( avcodec_mutex );
av_register_all();
- libavcodec = avcodec_alloc_context();
- avcodec_open( libavcodec, avcodec_find_decoder( CODEC_ID_DVVIDEO ) );
+ libavcodec = avcodec_alloc_context3(NULL);
+ avcodec_open2( libavcodec, avcodec_find_decoder( CODEC_ID_DVVIDEO ), NULL );
pthread_mutex_unlock( avcodec_mutex );
data = ( unsigned char* ) av_mallocz( 144000 );
#if defined(HAVE_SWSCALE)
@@ -1364,12 +1364,10 @@
vst-sample_aspect_ratio = avcodecEncoder-sample_aspect_ratio;
#endif
avcodecEncoder-thread_count = 2;
- avcodec_thread_init( avcodecEncoder, avcodecEncoder-thread_count );
avcodecEncoder-time_base= isPAL ? ( AVRational ){ 1, 25 } : ( AVRational ){ 1001, 3 };
avcodecEncoder-pix_fmt = isPAL ? PIX_FMT_YUV420P : PIX_FMT_YUV411P;
avcodecEncoder-flags |= CODEC_FLAG_INTERLACED_DCT;
- av_set_parameters( avformatEncoder, NULL );
- avcodec_open( avcodecEncoder, avcodec_find_encoder( CODEC_ID_DVVIDEO ) );
+ avcodec_open2( avcodecEncoder, avcodec_find_encoder( CODEC_ID_DVVIDEO ), NULL );
av_new_packet( avpacketEncoder, 144000 );
tempImage = ( uint8_t* ) av_malloc(
avpicture_get_size( avcodecEncoder-pix_fmt, avcodecEncoder-width, avcodecEncoder-height ) );
@@ -1475,19 +1473,15 @@
// Encode
bytesInFrame = avcodec_encode_video( avcodecEncoder, avpacketEncoder.data, size, output );
- url_open_buf( avformatEncoder-pb, data, bytesInFrame, URL_WRONLY );
+ avformatEncoder-pb = avio_alloc_context(data, bytesInFrame, 0, NULL, NULL, NULL, NULL);
avpacketEncoder.size = bytesInFrame;
if ( !isEncoderHeaderWritten )
{
-av_write_header( avformatEncoder );
+avformat_write_header(avformatEncoder, NULL);
isEncoderHeaderWritten = true;
}
av_write_frame( avformatEncoder, avpacketEncoder );
-#if LIBAVFORMAT_VERSION_INT = ((5216)+(08)+0)
- url_close_buf( avformatEncoder-pb );
-#else
- url_close_buf( avformatEncoder-pb );
-#endif
+ avio_close(avformatEncoder-pb);
// Update this frame's metadata
ExtractHeader();
diff -aur kino-1.3.4.orig/src/frame.cc kino-1.3.4/src/frame.cc
--- kino-1.3.4.orig/src/frame.cc 2013-09-06 01:16:23.35600 +0200
+++ kino-1.3.4/src/frame.cc 2013-09-06 01:21:57.41600 +0200
@@ -1338,7 +1338,7 @@
if ( avformatEncoder )
{
avformatEncoder-oformat = av_guess_format( dv, NULL, NULL );
- AVStream* vst = av_new_stream( avformatEncoder, 0 );
+ AVStream* vst = avformat_new_stream( avformatEncoder, NULL );
vst-codec-codec_type = AVMEDIA_TYPE_VIDEO;
vst-codec-codec_id = CODEC_ID_DVVIDEO;
vst-codec-bit_rate = 2500;
Bug#720003: marked as done (bzr-builddeb: FTBFS: Test failure in bzrlib.plugins.builddeb.tests.test_import_dsc.OneZeroSourceExtractorTests.test_extract_format3_native)
Your message dated Tue, 10 Sep 2013 23:33:02 + with message-id e1vjxqc-0002qc...@franck.debian.org and subject line Bug#720003: fixed in bzr-builddeb 2.8.7 has caused the Debian Bug report #720003, regarding bzr-builddeb: FTBFS: Test failure in bzrlib.plugins.builddeb.tests.test_import_dsc.OneZeroSourceExtractorTests.test_extract_format3_native to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 720003: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=720003 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Source: bzr-builddeb Version: 2.8.6 Severity: serious From my pbuilder build log: ... ...ball.test_repack_tarball_with_target_dir_not_dir(.tar.lzma) OK 10ms ...ckTarball.test_repack_tarball_with_target_dir_not_dir(.zip) OK2ms ...ckTarball.test_repack_tarball_with_target_dir_not_dir(.tar) OK2ms == FAIL: bzrlib.plugins.builddeb.tests.test_import_dsc.OneZeroSourceExtractorTests.test_extract_format3_native -- _StringException: Empty attachments: log Traceback (most recent call last): File /tmp/buildd/bzr-builddeb-2.8.6/tests/test_import_dsc.py, line 1973, in test_extract_format3_native builder.build() File /tmp/buildd/bzr-builddeb-2.8.6/tests/__init__.py, line 442, in build (proc.stdout.read(),) AssertionError: dpkg-source failed, output: dpkg-source: error: can't build with source format '3.0 (native)': native package version may not have a revision -- Ran 530 tests in 66.856s FAILED (failures=1) Missing feature '_LaunchpadConnectionFeature' skipped 1 tests. Missing feature 'bzr-svn plugin' skipped 3 tests. make[1]: *** [override_dh_auto_test] Error 1 make[1]: Leaving directory `/tmp/buildd/bzr-builddeb-2.8.6' make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 -- Daniel Schepler ---End Message--- ---BeginMessage--- Source: bzr-builddeb Source-Version: 2.8.7 We believe that the bug you reported is fixed in the latest version of bzr-builddeb, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 720...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andrew Starr-Bochicchio a...@debian.org (supplier of updated bzr-builddeb package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 10 Sep 2013 19:05:58 -0400 Source: bzr-builddeb Binary: bzr-builddeb Architecture: source all Version: 2.8.7 Distribution: unstable Urgency: low Maintainer: Debian Bazaar Maintainers pkg-bazaar-ma...@lists.alioth.debian.org Changed-By: Andrew Starr-Bochicchio a...@debian.org Description: bzr-builddeb - bzr plugin for Debian package management Closes: 711042 720003 Changes: bzr-builddeb (2.8.7) unstable; urgency=low . * tests/blackbox/test_import_dsc.py: - Explicitly pass '--format=1.0' to dpkg-source inorder to silence no source format specified warnings printed to stderr (Closes: #711042). * tests/test_import_dsc.py: - As of dpkg 1.17.0, source format '3.0 (native)' strictly enforces that native packages do not have a Debian revision. Use 0.1 instead of 0.1-1 for the version number in test_extract_format3_native (Closes: #720003). * debian/control: Add myself to Uploaders. * debian/tests/control: - Remove the depricated no-build-needed Features flag and add Restrictions: allow-stderr. Checksums-Sha1: 2321a1a1a5110056c58fa23ef52369eec058c7c0 2042 bzr-builddeb_2.8.7.dsc cb6e9da9880c958b7b290965c2b51c6df1e7743d 195108 bzr-builddeb_2.8.7.tar.gz d1ff2ee5567971c4fb03fd05df5bf53579fd5785 146776 bzr-builddeb_2.8.7_all.deb Checksums-Sha256: d73039235afa5173839eab57e84364ba3d7ce40a25a4c106fb05ae9ea571d593 2042 bzr-builddeb_2.8.7.dsc b089e30027db7ff1c71df7802ef5b173877f5bc7acba5a29cc7ab469afe3f4c3 195108 bzr-builddeb_2.8.7.tar.gz 9e77c3d9c604735c4230c8cc29719bb1cafde7643aa1233ec308863acaa1bf1e 146776 bzr-builddeb_2.8.7_all.deb Files: dd673468c2cfec6f4a8385066d37bb7e 2042
Bug#721166: ffdiaporama: depends on ffmpeg which is going away
Hi Sebastian, yes: the tests I did with that version was successful at that time. The other option is to update to 1.6, but I'm not sure it is compatible with libav 0.9. It may be a 2 step upload: first, 1.5-2, to unblock the transition and then update to 1.6, with more time. What do you think? thanks, Fabrice 2013/9/10 Sebastian Ramacher sramac...@debian.org Hi Fabrice, what's the status of 1.5-2? Is it just waiting to be uploaded? Regards -- Sebastian Ramacher
Bug#722151: marked as done (depends on python3.2 which is going away)
Your message dated Wed, 11 Sep 2013 00:18:09 + with message-id e1vjy8h-000160...@franck.debian.org and subject line Bug#722151: fixed in pystache 0.5.3-2 has caused the Debian Bug report #722151, regarding depends on python3.2 which is going away to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 722151: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722151 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: python3-pystache Version: 0.5.3-1 Severity: serious python3-pystache depends on python3.2 which is going away. Ansgar ---End Message--- ---BeginMessage--- Source: pystache Source-Version: 0.5.3-2 We believe that the bug you reported is fixed in the latest version of pystache, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 722...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Kouhei Maeda mkou...@palmtb.net (supplier of updated pystache package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Format: 1.8 Date: Tue, 10 Sep 2013 11:52:51 +0900 Source: pystache Binary: python-pystache python3-pystache Architecture: source all Version: 0.5.3-2 Distribution: unstable Urgency: low Maintainer: Kouhei Maeda mkou...@palmtb.net Changed-By: Kouhei Maeda mkou...@palmtb.net Description: python-pystache - Python implementation of Mustache python3-pystache - Python3 implementation of Mustache Closes: 722151 Changes: pystache (0.5.3-2) unstable; urgency=low . * Fixes depends on python3.2 which is going away (Closes: #722151) - debian/control: Change = 3.2 to = 3.3 of X-Python-Version. - debian/rules: Modified to python2.7, python3.2 to the valiable. Checksums-Sha1: 99695177e6c855019dd323ad69d67cf19ebd 1868 pystache_0.5.3-2.dsc 323b229eddbb5ce33b1f986aa9b0da137ade563e 3968 pystache_0.5.3-2.debian.tar.gz 6d833f7c4245f4b39aaa76830f91a5cdc958c0ea 34678 python-pystache_0.5.3-2_all.deb c0df4257f158236903fe2a87894eea13255deab6 26614 python3-pystache_0.5.3-2_all.deb Checksums-Sha256: d16d778483484f2f0dbf6125f5105ce91f1e7138e45d8947a33f4f8513934097 1868 pystache_0.5.3-2.dsc 661ebbdeeaa283a5369f659db3e1f582d24ed9163fc75de9605d39a61656e32a 3968 pystache_0.5.3-2.debian.tar.gz 354ebc11447d383161cefcad97c318a9939c128462bcbc7bf588ae0ee3afe229 34678 python-pystache_0.5.3-2_all.deb 544cafc94f9ae76ad0fae261f272c1a0b779822dc8a3a1f9e7e625f3281563a7 26614 python3-pystache_0.5.3-2_all.deb Files: cd4b99dae4ce9ba2cf522c88b16059f8 1868 python optional pystache_0.5.3-2.dsc 73dc0fe507b791ddc482c6f36908dfc7 3968 python optional pystache_0.5.3-2.debian.tar.gz 24f7c62bc1577db29720add77bc573b6 34678 python optional python-pystache_0.5.3-2_all.deb 2d101f3b5c1a357e4868f026f44fa6be 26614 python optional python3-pystache_0.5.3-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.14 (GNU/Linux) iQIcBAEBCAAGBQJSL7QAAAoJEDIkf7tArR+mengQAIgL88kM+Z2AZ/mfsh5H8o39 qQk5fQLFEFE/XVgO0jf6zuKeOcRdnEIjd7Pn6jhQq4FPL3gQXa7CH0Fkb6XD5KMM RfwUZbG+PpdLyI7NUMUojRqgFER0j8qWSQiy9zimhtKhy6++SN5sH8urhKHHZcMg AdX/hzPgFDkdVygXppo5zYlGaFKRtq3Wq88T6J3cmBEV7ppZui4J8+0WsihG8bVf NqnkPYEzv6919I8nYlq3VBvKSl/WS6mqlF8jRGLf21F55sL7oXIk0liab3+sNb9r rLrmSZU+cGgfJvGFQV68VWwGGBYRWzAPRrD6LVVURppC/zvsz6kbUE++Co9dae4e 3ev6SvS0BIItyZ0fmoFJhsUGN1Rdn9YhuUABLjRSVZZOtEsrdt960UWnwpqrsmW1 Rx9GGMvN2kV7hfhcOu1YCagWJR6XRjrjpKv41dF+ETbJIJLrK7TmeL7NARsyva2x Qd69jLwhhuqSQWYoSu04TtlglP8e04R5BKXbQBde9JIFYxMajXea8uvl+MZJQwYz iiR1hjOStpaRFWQE5l6FKR1aCVHgkMS9IzDuQjyDBcBHHZMmnxngin9WzVzVTBh9 UaboehkzLliRH0RFVw1ntzKgHgVF3jY+IvI9+qwRRpm9I1NkSRSsR1hCu42bqoN1 sdDumfJtoDYleR9zM8zc =N2t4 -END PGP SIGNATUREEnd Message---
Bug#710650: Bug#718767: transition: ocaml 4.00.1
Hi, As for becoming more upstream-friendly, there are now several of us working to make that happen. Euan Harris is working hard on actually creating packages from this work, though the shape of these packages is quite different from that of the old-style 1.3.2 packages. We should start a conversation on pkg-xen-devel to make sure what he's doing is acceptable to you guys. Yes, I've already had some brief discussions with Thomas and Stefan about the packages. We're getting quite close to having working xenserver-core packages for Debian (in addition to the current versions for CentOS). I don't think you will want to use those packages directly in Debian, but as a result of trying to build our own Debian packages we have been removing as many of these distribution-specific quirks in the upstream packages as possible which should make packaging easier in future. Thanks, Euan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722002: marked as done (ampache-common: Unsatisfiable dependency on php-getid3)
Your message dated Tue, 10 Sep 2013 21:05:04 -0500 with message-id cal_xwdcqjyfnkenq4lnpsheiqfdw-uu2pfmh7nlcx6bgnp1...@mail.gmail.com and subject line Unsatisfiable dependency on php-getid3 has caused the Debian Bug report #722002, regarding ampache-common: Unsatisfiable dependency on php-getid3 to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 722002: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722002 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: ampache-common Version: 3.6-rzb2752+dfsg-1 Severity: serious User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu saucy ampache-common depends on php-getid3 ( 1.9.6.0~), php-getid3 (= 1.9.6), but the version of php-getid3 in unstable is 1.9.6-1. Thanks, Jeremy - -- System Information: Debian Release: wheezy/sid APT prefers saucy-updates APT policy: (500, 'saucy-updates'), (500, 'saucy-security'), (500, 'saucy'), (100, 'saucy-backports') ---End Message--- ---BeginMessage--- Package: ampache Version: 3.6-rzb2752+dfsg-1 Closing -- Charlie Smotherman Debian Contributor Ubuntu Developer ---End Message---
Bug#722438: qtscrob: FTBFS - manpage compression race in parallel builds
Source: qtscrob Version: 0.11+git-1 Severity: serious Justification: fails to build from source The builds of qtscrob on i386, mips, and powerpc all failed because man pages they meant to compress weren't actually present: gzip -9 -f /«BUILDDIR»/qtscrob-0.11+git/debian/tmp//usr/share/man/man1/qtscrob.1 gzip: /«BUILDDIR»/qtscrob-0.11+git/debian/tmp//usr/share/man/man1/qtscrob.1: No such file or directory make[3]: *** [install_man-compress] Error 1 make[3]: *** Waiting for unfinished jobs Given that all three builds ran in parallel (with -j6 or -j8), I suspect a race condition. Could you please take a look? Thanks! -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#707961: marked as done (glabels: depends on gnome-desktop-data which is going away)
Your message dated Wed, 11 Sep 2013 03:03:57 + with message-id e1vjaij-00069q...@franck.debian.org and subject line Bug#707961: fixed in glabels 3.0.1-3 has caused the Debian Bug report #707961, regarding glabels: depends on gnome-desktop-data which is going away to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 707961: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707961 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: glabels Version: 3.0.0-3 Severity: serious User: pkg-gnome-maintain...@lists.alioth.debian.org Usertags: oldlibs gnome-desktop Dear maintainer, Your last upload of glabels added a dependency on gnome-desktop-data, which I am about to remove. I am not even sure why you have added that dependency (the changelog mentions some license stuff, but gnome-desktop-data only ships a bunch of pixmaps and some translations). Perhaps you can avoid it entirely or depend on gnome-desktop3-data instead. Regards, Emilio ---End Message--- ---BeginMessage--- Source: glabels Source-Version: 3.0.1-3 We believe that the bug you reported is fixed in the latest version of glabels, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 707...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Jakob Haufe su...@sur5r.net (supplier of updated glabels package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 10 Sep 2013 20:44:01 +0200 Source: glabels Binary: glabels glabels-data glabels-dev Architecture: source all amd64 Version: 3.0.1-3 Distribution: experimental Urgency: low Maintainer: Jakob Haufe su...@sur5r.net Changed-By: Jakob Haufe su...@sur5r.net Description: glabels- label, business card and media cover creation program for GNOME glabels-data - data files for gLabels glabels-dev - development documentation and library files for gLabels Closes: 691089 707961 722033 Changes: glabels (3.0.1-3) experimental; urgency=low . * Refresh debian/patches * Cherry-pick 6b7d7e831e5542b6ea3c15802fa882a42399fc15 from upstream as 0004-unbreak-with-evolution-data-server-3.6.0.patch (Closes: #722033) * Bump Standards-Version (no changes needed) * Change dependency to gnome-desktop3-data (Closes: #707961) * Add patch from Jakub Wilk to fix Polish translation (Closes: #691089) Checksums-Sha1: 34b5a11d6f4ddff2e09a3e819a2822fa4a22231b 2171 glabels_3.0.1-3.dsc 3e0dcc858188fe64d9f2379fa6c93fede0afa241 20238 glabels_3.0.1-3.debian.tar.gz 669b6fa9d01a9265c91150c441be628478a805d9 2768582 glabels-data_3.0.1-3_all.deb 18873d8773c06a5e8c75c3afdef40062a990d763 421296 glabels_3.0.1-3_amd64.deb 061dde535619a79e868b25293f104d72519ece98 234562 glabels-dev_3.0.1-3_amd64.deb Checksums-Sha256: 2361ee9766cc65a911835fce01c5b8612e48e6221ff3855b0d71659547bd0c7f 2171 glabels_3.0.1-3.dsc 5cefe5aeddfd0712c46eba9a135e219ed4038225e5416d949d733e2bfe945f87 20238 glabels_3.0.1-3.debian.tar.gz d56aeff242db1851551b5a107994169ce1509a171862f83887b9d53079a31a40 2768582 glabels-data_3.0.1-3_all.deb 2fafe707e49ebe106dfd6c61311dd83444b5f1e32060c2a646c495e86f9d7623 421296 glabels_3.0.1-3_amd64.deb 0b0f4bea79cca1efceb7a6d6548d7158773ce60d55e6dfb24526eced2a4e63f2 234562 glabels-dev_3.0.1-3_amd64.deb Files: cbb0beb0355d5e5313a0aae52971fcca 2171 gnome optional glabels_3.0.1-3.dsc ae760c57de6f75ee2a88bc476611a3c8 20238 gnome optional glabels_3.0.1-3.debian.tar.gz 42fdcb7c791718aabbe41b066f7569ef 2768582 gnome optional glabels-data_3.0.1-3_all.deb 22541958320c62ad6233f3a6d4e24e47 421296 gnome optional glabels_3.0.1-3_amd64.deb ef3e5b19639c501949102a812bc71e85 234562 devel optional glabels-dev_3.0.1-3_amd64.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iQIcBAEBCgAGBQJSL9VBAAoJEE5xYO1KyO4dhXkQAIIkRYJexI4ubczNoSlE+THM 5Jd3pUx38tr1s6U98GX1sC/QPBttHw9sLm6wZJINIXAbXh/8TdKwwMPe4Y0vOztm QCbQttqjU6uHbSPcWb7HpycL8RF5cxFM5yk1eslSIg7W5pJvB1rKg9vIVkuE8A5c 94LwuKEFb4wAT7yuFONJ6N6YA4oPdxzc/8uVnhl283NsjC6f9qv0oDy5+jjAn7a0 SnmY6r6bQC86f4+QlR28h6EfAk75GOOu7TcvUtYUuK/2DnIHbYoTbRcqH78EAv+w yrL4s+uEgA2lcovJcFtGjxJuudZL7BOz+msb7LPNBJcSvQKnfRS5Z1CPZ8/XJTqy
Bug#722288: marked as done (libgl1-nvidia-legacy-304xx-glx: 304.108-2 fails to install: trying to overwrite libnvidia-tls.so.304.108, which is also in libgl1-nvidia-glx:amd64 304.108-1)
Your message dated Wed, 11 Sep 2013 04:18:35 +
with message-id e1vjbsx-0001bh...@franck.debian.org
and subject line Bug#722288: fixed in nvidia-graphics-drivers 304.108-2
has caused the Debian Bug report #722288,
regarding libgl1-nvidia-legacy-304xx-glx: 304.108-2 fails to install: trying to
overwrite libnvidia-tls.so.304.108, which is also in libgl1-nvidia-glx:amd64
304.108-1
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
722288: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722288
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
---BeginMessage---
Package: libgl1-nvidia-legacy-304xx-glx
Version: 304.108-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I can't update libgl1-nvidia-legacy-304xx-glx from 304.108-1 to 304.108-2,
because
apt-get complains about overwriting a file belonging to the older version:
root@thinkpad:~# apt-get -f install
Reading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
libgl1-nvidia-legacy-304xx-glx
Suggested packages:
nvidia-legacy-304xx-kernel-dkms nvidia-legacy-304xx-kernel-source
The following NEW packages will be installed:
libgl1-nvidia-legacy-304xx-glx
0 upgraded, 1 newly installed, 0 to remove and 19 not upgraded.
11 not fully installed or removed.
Need to get 0 B/6,597 kB of archives.
After this operation, 37.0 MB of additional disk space will be used.
Do you want to continue? [Y/n]
(Reading database ... 158580 files and directories currently installed.)
Unpacking libgl1-nvidia-legacy-304xx-glx:amd64 (from
.../libgl1-nvidia-legacy-304xx-glx_304.108-2_amd64.deb) ...
dpkg: error processing
/var/cache/apt/archives/libgl1-nvidia-legacy-304xx-glx_304.108-2_amd64.deb
(--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/tls/libnvidia-tls.so.304.108',
which is also in package libgl1-nvidia-glx:amd64 304.108-1
dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
Errors were encountered while processing:
/var/cache/apt/archives/libgl1-nvidia-legacy-304xx-glx_304.108-2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@thinkpad:~#
So now I'm stuck, unfortunately.
Kind regards,
Jurriaan
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 3.10-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
---End Message---
---BeginMessage---
Source: nvidia-graphics-drivers
Source-Version: 304.108-2
We believe that the bug you reported is fixed in the latest version of
nvidia-graphics-drivers, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 722...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Andreas Beckmann a...@debian.org (supplier of updated nvidia-graphics-drivers
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Format: 1.8
Date: Wed, 11 Sep 2013 05:37:09 +0200
Source: nvidia-graphics-drivers
Binary: nvidia-driver nvidia-glx xserver-xorg-video-nvidia libgl1-nvidia-glx
nvidia-alternative nvidia-kernel-dkms nvidia-kernel-source nvidia-vdpau-driver
nvidia-smi nvidia-cuda-mps libcuda1 libnvidia-compiler libnvcuvid1
libnvidia-ml1 nvidia-opencl-common nvidia-opencl-icd nvidia-libopencl1
nvidia-detect
Architecture: source amd64
Version: 304.108-2
Distribution: unstable
Urgency: low
Maintainer: Debian NVIDIA Maintainers pkg-nvidia-de...@lists.alioth.debian.org
Changed-By: Andreas Beckmann a...@debian.org
Description:
libcuda1 - NVIDIA CUDA runtime library
libgl1-nvidia-glx - NVIDIA binary OpenGL libraries${nvidia:LegacyDesc}
libnvcuvid1 - NVIDIA CUDA nvcuvid runtime library
libnvidia-compiler - NVIDIA runtime compiler library
libnvidia-ml1 - NVIDIA management library (NVML) runtime library
nvidia-alternative - allows the selection of NVIDIA as GLX provider
nvidia-cuda-mps - NVIDIA CUDA Multi Process Service (MPS)
nvidia-detect - NVIDIA GPU detection utility
Processed: user debian...@lists.debian.org, tagging 646224, tagging 719457, tagging 701009
Processing commands for cont...@bugs.debian.org: user debian...@lists.debian.org Setting user to debian...@lists.debian.org (was a...@debian.org). tags 646224 - sid Bug #646224 [svnmailer] svnmailer: Please upgrade svnmailer, there are new upstream version of it. Removed tag(s) sid. tags 719457 + upstream Bug #719457 [nvidia-driver] nvidia-driver: fails to repaint/refresh windows Added tag(s) upstream. tags 701009 + upstream Bug #701009 [nvidia-glx] Bands at the top of the screen. Added tag(s) upstream. thanks Stopping processing here. Please contact me if you need assistance. -- 646224: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=646224 701009: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701009 719457: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=719457 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#722431: tcl-snack-dev: Unable to install due to dependencies and conflicts
Hi Giulio, On Wed, Sep 11, 2013 at 2:20 AM, Giulio Paci giuliop...@gmail.com wrote: I just tried to install tcl-snack-dev, but my system reports that: 1) tcl-snack-dev depends on tcl-snack; 2) tcl-snack depends on libsnack-alsa AND provides libsnack2; 3) libsnack-alsa conflicts with libsnack2. This makes the package uninstallable on my system. Am I doing something wrong? I think I did something terribly wrong with dependencies. The idea was to allow upgrade from the old packages. I'll fix the dependencies shortly. -- Sergei Golovan -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#721401: marked as done (libspiro-dev: libspiro.so is missing)
Your message dated Wed, 11 Sep 2013 05:18:03 + with message-id e1vjcov-z6...@franck.debian.org and subject line Bug#721401: fixed in libspiro 20071029-7 has caused the Debian Bug report #721401, regarding libspiro-dev: libspiro.so is missing to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 721401: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=721401 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: libspiro-dev Version: 20071029-6 Severity: serious Dear Maintainer, /usr/lib/i386-linux-gnu/libspiro.so is missing from this package and thus other /packages are unable to detect or link against this library. gegl is a nice example. Christian -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 3.10.10 (SMP w/8 CPU cores; PREEMPT) Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libspiro-dev depends on: ii libspiro0 20071029-6 libspiro-dev recommends no packages. libspiro-dev suggests no packages. -- no debconf information ---End Message--- ---BeginMessage--- Source: libspiro Source-Version: 20071029-7 We believe that the bug you reported is fixed in the latest version of libspiro, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 721...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Christian Perrier bubu...@debian.org (supplier of updated libspiro package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.8 Date: Tue, 10 Sep 2013 07:09:06 +0200 Source: libspiro Binary: libspiro0 libspiro-dev libspiro0-dbg Architecture: source i386 Version: 20071029-7 Distribution: unstable Urgency: low Maintainer: Debian Fonts Task Force pkg-fonts-de...@lists.alioth.debian.org Changed-By: Christian Perrier bubu...@debian.org Description: libspiro-dev - library for curve design - development files libspiro0 - library for curve design libspiro0-dbg - library for curve design - debugging symbols Closes: 721401 Changes: libspiro (20071029-7) unstable; urgency=low . [ Vasudev Kamath ] * Team Upload. * Marked the packages multi-arch same, and added pre-depends on multiarch-support. Thanks to Christian Marillat. Closes: bug#721401 * Description field is fixed by removing extra space and article a in the beginning. * Install symlink to libspiro.so as part of libspiro-dev package. * Symbols file is introduced using pkg-kde-tools, appropriate change is done to rules to kde addon with dh and build-depends on pkg-kde-tools is added. * Converted copyright file to copyright-format 1.0. . [ Christian Perrier ] * Rewrite package descriptions to fit the debian-l10n-english standardized writing style. Checksums-Sha1: 30447f5df6345222b776a98d1a22c3306afa022e 1932 libspiro_20071029-7.dsc bbabc12123dd91220096fcb2620e0566c6dad041 274724 libspiro_20071029.orig.tar.gz 38cc41a799051500c9868f09774e7b7f749c20a6 3006 libspiro_20071029-7.debian.tar.gz 9358695d54e40f8c14e3b6640b3ff63db1f2b0b0 12564 libspiro0_20071029-7_i386.deb b7d08bc8c7295ba95f055acb5d9b9195ffddfba0 3938 libspiro-dev_20071029-7_i386.deb f947d7f29c2e94e4ca06bf07122a6cdbd2424464 15882 libspiro0-dbg_20071029-7_i386.deb Checksums-Sha256: b09b496d96d716a4db6c00ba6be3a482dea364157f7e4a4d5d29dcf9391d3e8a 1932 libspiro_20071029-7.dsc 8a593e93301e68614c8ae37d08c07cef90727ac6651cad36c23e59d8bd6abbad 274724 libspiro_20071029.orig.tar.gz b4bd75cbc1dcbe9729ba2a8d9252a8cfef991ccce487f08105ba61f0ed45d850 3006 libspiro_20071029-7.debian.tar.gz d3d32346047f5997c6c4b03e6fdf146f32d9d1579e4390de6c396d95f598ff8d 12564 libspiro0_20071029-7_i386.deb 5af725204392993d99848ded678eb580d539d266261fb23e0388c3dfd62f34d2 3938 libspiro-dev_20071029-7_i386.deb 2949201c427be2dab1e7a962418c32d33bb26ea1960b049e044af8f301c3030d 15882 libspiro0-dbg_20071029-7_i386.deb Files: 620858748f00f0ef02a050c63a96dcd8 1932 libs extra libspiro_20071029-7.dsc d3afc1c159b3c3184e05b8d820416067 274724 libs extra libspiro_20071029.orig.tar.gz
Bug#722209: marked as done (yacy: Admin login failure)
Your message dated Wed, 11 Sep 2013 08:51:06 +0300 with message-id 20130911055106.GK3551@sid.nuvreauspam and subject line Re: Bug#722209: yacy: Admin login failure has caused the Debian Bug report #722209, regarding yacy: Admin login failure to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 722209: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=722209 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: yacy Version: 1.62.9051 Severity: grave Tags: upstream Justification: renders package unusable Dear Maintainer, *** Please consider answering these questions, where appropriate *** * What led up to the situation? After installation yacy, I couldn't login as admin on yacy server. This makes impossible to configure yacy search engine in the beginning. * What exactly did you do (or not do) that was effective (or ineffective)? After stopping yacy daemon, I had to edit the following lines in yacy.conf file. Then restarted yacy daemon. adminAccountForLocalhost=false publicAdministratorPi=false adminAccount= adminAccountBase64MD5=53d27063489ec1082ad8ddc11c1badf5 * What was the outcome of this action? I could login as admin on yacy server. * What outcome did you expect instead? *** End of the template - remove these lines *** -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.4.0-10.dmz.1-liquorix-amd64 (SMP w/6 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages yacy depends on: ii debconf1.5.46 ii openjdk-6-jre [java2-runtime] 6b24-1.11.5-1 ii sudo 1.8.5p2-1 ii sun-java6-jre [java2-runtime] 6.26-0squeeze1 yacy recommends no packages. yacy suggests no packages. -- debconf information: * yacy/network: freeworld yacy/network-url: * yacy/memory-max: 600 * yacy/peername: theblue * yacy/memory-start: 180 ---End Message--- ---BeginMessage--- On Lu, 09 sep 13, 14:16:44, Hughe Chung wrote: Package: yacy Version: 1.62.9051 Severity: grave Tags: upstream Justification: renders package unusable There is currently no such package in Debian and your kernel hints you might not even be running Debian. Please report this issue to where you obtained the yacy package from. [snip] -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (900, 'testing'), (800, 'unstable') Architecture: amd64 (x86_64) Kernel: Linux 3.4.0-10.dmz.1-liquorix-amd64 (SMP w/6 CPU cores; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages yacy depends on: ii debconf1.5.46 ii openjdk-6-jre [java2-runtime] 6b24-1.11.5-1 ii sudo 1.8.5p2-1 ii sun-java6-jre [java2-runtime] 6.26-0squeeze1 yacy recommends no packages. yacy suggests no packages. -- debconf information: * yacy/network: freeworld yacy/network-url: * yacy/memory-max: 600 * yacy/peername: theblue * yacy/memory-start: 180 Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature ---End Message---
Bug#722332: libcommon-sense-perl: common::sense runs into trouble with Perl 5.18, eg. no say().
On Tue, Sep 10, 2013 at 05:12:53PM +0200, gregor herrmann wrote: On Tue, 10 Sep 2013 12:35:16 +0200, Hagen Fuchs wrote: I just noticed that, upon upgrading to Perl 5.18.1-3 (Debian testing), common::sense stopped having some: - need to set lower and upper bounds of the perl version in Depends (not only the lower, as it's now) The new perl-base also needs to Break the old libcommon-sense-perl versions, for partial upgrades from wheezy. Please clone a bug for that when there's a fixed libcommon-sense-perl package in the archive. - add it to our mental list of packages that needs rebuilds on new perl releases The dependencies should make it possible to detect this automatically in the future, but there's also a list at https://wiki.debian.org/PerlMaintenance Feel free to update that. Not sure if all the internals that common::sense fiddles with are under the 'no ABI changes in minor Perl version updates' promise. I suspect they are, but we might still be best off rebuilding it even for minor updates. Last, I note that autopkgtest and a good test suite in common::sense would have caught this :) -- Niko -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
