Processed: Re: Bug#748827: torque: CVE-2014-0749

Processing control commands: > tags -1 + patch Bug #748827 [src:torque] torque: CVE-2014-0749 Added tag(s) patch. -- 748827: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748827 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-rc

Bug#748827: torque: CVE-2014-0749

Control: tags -1 + patch Hi, I have prepared packages for squeeze and wheezy based on attached debdiff for the older versions. Attached debdiff is for unstable. Regards, Salvatore diff -Nru torque-2.4.16+dfsg/debian/changelog torque-2.4.16+dfsg/debian/changelog --- torque-2.4.16+dfsg/debian/cha

Bug#718004: marked as done (paramiko-doc: fails to upgrade from 'wheezy' - trying to overwrite /usr/share/doc-base/python-paramiko)

Your message dated Thu, 22 May 2014 04:03:59 + with message-id and subject line Bug#718004: fixed in paramiko 1.14.0-1 has caused the Debian Bug report #718004, regarding paramiko-doc: fails to upgrade from 'wheezy' - trying to overwrite /usr/share/doc-base/python-paramiko to be marked as don

Processed: Re: Bug#747805: duo-unix: FTBFS: error: OpenSSL not found

Processing control commands: > tags -1 patch Bug #747805 [src:duo-unix] duo-unix: FTBFS: error: OpenSSL not found Added tag(s) patch. -- 747805: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=747805 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, ema

Bug#747805: duo-unix: FTBFS: error: OpenSSL not found

Control: tags -1 patch Looks like the package is just missing a Build-Depends on libssl-dev. Presumably previously libcurl4-openssl-dev depended on libssl-dev, and this package was (incorrectly) relying on that continuing. Once I add libssl-dev to Build-Depends, the package builds fine for me. L

Bug#740064: marked as done (dhelp: Weekly cron job always fails.)

Your message dated Wed, 21 May 2014 22:34:00 + with message-id and subject line Bug#734523: fixed in dhelp 0.6.21+nmu4 has caused the Debian Bug report #734523, regarding dhelp: Weekly cron job always fails. to be marked as done. This means that you claim that the problem has been dealt with.

Bug#734523: marked as done (dhelp: Error while building the HTML tree)

Your message dated Wed, 21 May 2014 22:34:00 + with message-id and subject line Bug#734523: fixed in dhelp 0.6.21+nmu4 has caused the Debian Bug report #734523, regarding dhelp: Error while building the HTML tree to be marked as done. This means that you claim that the problem has been dealt

Bug#732916: marked as done (Depends on obsolete package: ruby1.8)

Your message dated Wed, 21 May 2014 22:33:59 + with message-id and subject line Bug#732916: fixed in dhelp 0.6.21+nmu4 has caused the Debian Bug report #732916, regarding Depends on obsolete package: ruby1.8 to be marked as done. This means that you claim that the problem has been dealt with.

Bug#712621: marked as done (dhelp_parse is performance killer)

Your message dated Wed, 21 May 2014 22:33:59 + with message-id and subject line Bug#712621: fixed in dhelp 0.6.21+nmu4 has caused the Debian Bug report #712621, regarding dhelp_parse is performance killer to be marked as done. This means that you claim that the problem has been dealt with. If

Processed: Re: Bug#748848: byzanz: does not work at all: Error during recording: no element "appsrc"

Processing control commands: > tags -1 confirmed Bug #748848 [byzanz] byzanz: does not work at all: Error during recording: no element "appsrc" Added tag(s) confirmed. > severity -1 serious Bug #748848 [byzanz] byzanz: does not work at all: Error during recording: no element "appsrc" Severity se

Bug#748848: byzanz: does not work at all: Error during recording: no element "appsrc"

Control: tags -1 confirmed Control: severity -1 serious On 21.05.2014 14:05, Thorsten Glaser wrote: > Package: byzanz > Version: 0.3.0+git20140123-1 > Severity: grave > Justification: renders package unusable > > -BEGIN SCREEN PASTE- > tglase@tglase:~ $ byzanz-record -c -e xterm -v --dela

Bug#748889: paraview: FTBFS on kfreebsd

Source: paraview Version: 4.1.0+dfsg-1 Severity: serious Justification: fails to build from source (but built successfully in the past) paraview failed to build on kfreebsd buildds: | cd /«BUILDDIR»/paraview-4.1.0+dfsg/obj-x86_64-kfreebsd-gnu/VTK/Utilities/KWSys/vtksys && /usr/bin/c++ -DKWSYS_

Bug#748850: marked as done (ruby-descendants-tracker: uninstallable due to dependency typo)

Your message dated Wed, 21 May 2014 21:36:08 + with message-id and subject line Bug#748850: fixed in ruby-descendants-tracker 0.0.4-2 has caused the Debian Bug report #748850, regarding ruby-descendants-tracker: uninstallable due to dependency typo to be marked as done. This means that you cl

Bug#748574: 3.14.1 does not boot on Dell server

Le 21/05/2014 22:20, Ben Hutchings a écrit : > Control: tag -1 - moreinfo > > On Wed, 2014-05-21 at 22:08 +0200, Erwan David wrote: >> Le 20/05/2014 21:45, Erwan David a écrit : >>> Le 20/05/2014 21:16, Erwan David a écrit : I do not see how to apply the patch you provided once I got the sourc

Bug#748574: 3.14.1 does not boot on Dell server

On 05/21/2014 04:16 PM, Ben Hutchings wrote: I'm not sure, but that looks like it's failing to mount the root, as if the boot loader was not loading an initrd. Anyway, from your later message on debian-user it seems that the problem

Bug#748574: 3.14.1 does not boot on Dell server

Le 21/05/2014 22:20, Ben Hutchings a écrit : > Control: tag -1 - moreinfo > > On Wed, 2014-05-21 at 22:08 +0200, Erwan David wrote: >> Le 20/05/2014 21:45, Erwan David a écrit : >>> Le 20/05/2014 21:16, Erwan David a écrit : I do not see how to apply the patch you provided once I got the sourc

Processed: Re: Bug#748574: 3.14.1 does not boot on Dell server

Processing control commands: > tag -1 - moreinfo Bug #748574 [src:linux] 3.14.1 does not boot on Dell server Removed tag(s) moreinfo. -- 748574: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=748574 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, ema

Bug#748574: 3.14.1 does not boot on Dell server

Control: tag -1 - moreinfo On Wed, 2014-05-21 at 22:08 +0200, Erwan David wrote: > Le 20/05/2014 21:45, Erwan David a écrit : > > Le 20/05/2014 21:16, Erwan David a écrit : > >> I do not see how to apply the patch you provided once I got the source > >> of the package. > >> > >> patch < 00*.patch

Bug#748574: 3.14.1 does not boot on Dell server

On Mon, 2014-05-19 at 10:52 -0400, John Bleichert wrote: > On 05/18/2014 09:25 PM, Ben Hutchings wrote: > > >> The page faults are ominous… > > > > Please test whether the attached patch fixes this, following the > > instructions at > >

Bug#748574: 3.14.1 does not boot on Dell server

Le 20/05/2014 21:45, Erwan David a écrit : > Le 20/05/2014 21:16, Erwan David a écrit : >> I do not see how to apply the patch you provided once I got the source >> of the package. >> >> patch < 00*.patch does nit find the file to patch whether I use it in >> the directory where I got the source pa

Processed: bug 748849 is forwarded to https://rt.cpan.org/Public/Bug/Display.html?id=86843

Processing commands for cont...@bugs.debian.org: > # sort of ... the ticket also mentions that Email::Send is deprecated and > should be replaced with Email::Sender > forwarded 748849 https://rt.cpan.org/Public/Bug/Display.html?id=86843 Bug #748849 [libcatalyst-plugin-email-perl] libcatalyst-plug

Processed: severity of 745531 is serious

Processing commands for cont...@bugs.debian.org: > severity 745531 serious Bug #745531 [f-spot] Please migrate to lcms2 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 745531: http://bugs.debian.org/cgi-bin/bugreport.cgi?

Processed: severity of 745516 is serious

Processing commands for cont...@bugs.debian.org: > severity 745516 serious Bug #745516 [photoprint] Please migrate to lcms2 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 745516: http://bugs.debian.org/cgi-bin/bugreport.

Processed: severity of 745534 is serious

Processing commands for cont...@bugs.debian.org: > severity 745534 serious Bug #745534 [netsurf-common] Please migrate to lcms2 Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 745534: http://bugs.debian.org/cgi-bin/bugrep

Bug#748495: closed by Daniel Baumann (reply to daniel.baum...@progress-technologies.net) (Re: Missing required dependencies)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Daniel, Am 21.05.2014 12:55, schrieb Daniel Baumann: > On 05/19/2014 09:40 AM, Benny Baumann wrote: >> Even then you should make sure you are recommending the correct >> version (python3 >= 3.3) which currently is not the case. > > there is no s

Bug#745672: its building fine for me

locally as well as in pbuilder. avtobiff, can you try to build it once again? -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Processed: severity of 747673 is serious

Processing commands for cont...@bugs.debian.org: > severity 747673 serious Bug #747673 [ejabberd] Horrid default cipher settings without option to adjust them to sane values Severity set to 'serious' from 'grave' > thanks Stopping processing here. Please contact me if you need assistance. -- 74

Bug#747803: libmrss: FTBFS: configure: line 12750: syntax error near unexpected token `NXML,'

Hi David, I wasn't able to reproduce it yet, but as the package is running dh_reconfigure, could you send me the generated configure file so I could check what is wrong and have a better idea about how to fix it please? Thanks in advance, Joseph -- To UNSUBSCRIBE, email to debian-bugs-rc-requ.

Bug#746076: marked as done (threadscope: FTBFS: Ambiguous occurrence `Region')

Your message dated Wed, 21 May 2014 16:34:12 + with message-id and subject line Bug#746076: fixed in threadscope 0.2.3-1 has caused the Debian Bug report #746076, regarding threadscope: FTBFS: Ambiguous occurrence `Region' to be marked as done. This means that you claim that the problem has b

Bug#748472: marked as done (python3-wsme: Uninstallable due to dropping of python3-ipaddr)

Your message dated Wed, 21 May 2014 16:04:57 + with message-id and subject line Bug#748472: fixed in python-wsme 0.6-3 has caused the Debian Bug report #748472, regarding python3-wsme: Uninstallable due to dropping of python3-ipaddr to be marked as done. This means that you claim that the pro

Bug#748865: xbmc-pvr-addons: fails to build with xmbc 13

Source: xbmc-pvr-addons Version: 12.0+79+ge1c3fb1+dfsg1-5 Severity: serious Justification: fails to build from source Dear maintainer, xbmc-pvr-addons currently fails to build in sid: src/client.cpp: In function 'PVR_ERROR CallMenuHook(const PVR_MENUHOOK&)': src/client.cpp:292:52: error: declara

Bug#748761: printer-driver-gutenprint: Cups doesn't print because rastertogutenprint.5.2 is missing

Control: tags -1 +pending +confirmed Le mardi, 20 mai 2014, 15.59:23 rollopack a écrit : > installing printer-driver-gutenprint (5.2.10~pre2-1) break cups. > The error reported is: > file "/usr/lib/cups/filter/rastertogutenprint.5.2" not available: No > such file or directory > > No problem with

Processed: Re: Bug#748761: printer-driver-gutenprint: Cups doesn't print because rastertogutenprint.5.2 is missing

Processing control commands: > tags -1 +pending +confirmed Bug #748761 [printer-driver-gutenprint] printer-driver-gutenprint: Cups doesn't print because rastertogutenprint.5.2 is missing Added tag(s) pending. Bug #748761 [printer-driver-gutenprint] printer-driver-gutenprint: Cups doesn't print b

Bug#747673: Horrid default cipher settings without option to adjust them to sane values

Hi, ejabberd 2.1.11-1 is pretty much useless by now, look at the RC bugs #746029 and #746073. Nevertheless I would like to know how you retrieved this information and if it still applies to 14.05. If so I will forward it to upstream, although you're welcome to do it yourself at https://support.p

Bug#748862: kernel-common: missing dependency on dpkg-dev

Control: reassign -1 kernel-common 13.0.11 Reassigning to the right package, since there is no kernel-common source package. On 2014-05-21 17:22 +0200, Sven Joachim wrote: > Control: severity -1 serious > > On 2014-05-21 17:08 +0200, Adam Borowski wrote: > >> Source: kernel-common >> Version: 13

Processed: Re: Bug#748862: kernel-common: missing dependency on dpkg-dev

Processing control commands: > reassign -1 kernel-common 13.0.11 Bug #748862 [src:kernel-common] kernel-common: missing dependency on dpkg-dev Warning: Unknown package 'src:kernel-common' Bug reassigned from package 'src:kernel-common' to 'kernel-common'. No longer marked as found in versions kern

Bug#748776: libprelude: FTBFS on arm64 as well as armel and armhf

Package: libprelude Version: 1.0.0-11.1 Followup-For: Bug #748776 libprelude FTBFS on arm64 just as it does on armel and armhf: make[5]: Entering directory '/home/buildd/packages/modified/libprelude-1.0.0/tests' ../test-driver: line 107: 32328 Segmentation fault "$@" > $log_file 2>&1 FAIL:

Processed: Re: Bug#748862: kernel-common: missing dependency on dpkg-dev

Processing control commands: > severity -1 serious Bug #748862 [src:kernel-common] kernel-common: missing dependency on dpkg-dev Warning: Unknown package 'src:kernel-common' Severity set to 'serious' from 'important' Warning: Unknown package 'src:kernel-common' -- 748862: http://bugs.debian.org/

Bug#748861: miro: FTBFS due to Libav 10

Package: miro Version: 4.0.4-1.1 Severity: serious Justification: fails to build from source Tags: patch Dear Maintainer, miro currently fails to build in sid: cc -I/usr/include/ffmpeg -c /tmp/buildd/miro-4.0.4/linux/miro-segmenter.c -o /tmp/buildd/miro-4.0.4/./build/miro-segmenter/tmp/buildd/

Bug#743748: Folders are not listed, blank folder pane

Hello Mordur, On Sat, Apr 05, 2014 at 06:17:55PM -0400, Mordur Ingolfsson wrote: > The software seems to be working (filters, calendars etc.) except for > the folder pane and the folder list in the subscriptions control panel > are completely blank. The folder pane is gray like the background of >

Bug#748850: ruby-descendants-tracker: uninstallable due to dependency typo

Package: ruby-descendants-tracker Version: 0.0.4-1 Severity: grave # apt-get install ruby-descendants-tracker Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossib

Bug#748849: libcatalyst-plugin-email-perl: FTBFS due to removal of libemail-send-perl

Package: libcatalyst-plugin-email-perl Version: 0.08-1 Severity: serious libcatalyst-plugin-email-perl fails to build in unstable with this error when installing build-dependencies: The following packages have unmet dependencies: sbuild-build-depends-libcatalyst-plugin-email-perl-dummy : Dep

Bug#748848: byzanz: does not work at all: Error during recording: no element "appsrc"

Package: byzanz Version: 0.3.0+git20140123-1 Severity: grave Justification: renders package unusable -BEGIN SCREEN PASTE- tglase@tglase:~ $ byzanz-record -c -e xterm -v --delay=2 ggl.flv ** (byzanz-record:25119): WARNING **: Error retrievin

Bug#748846: ruby-compass-rails: uninstallable due to new ruby-sprockets

Package: ruby-compass-rails Version: 1.1.7-1 Severity: grave # apt-get install ruby-compass-rails Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation

Bug#748750: marked as done (src:mhc: Build-Depends on ruby2.0, which will not be shipped in jessie)

Your message dated Wed, 21 May 2014 11:50:23 + with message-id and subject line Bug#748750: fixed in mhc 0.25.1+20130926-3 has caused the Debian Bug report #748750, regarding src:mhc: Build-Depends on ruby2.0, which will not be shipped in jessie to be marked as done. This means that you claim

Bug#748495: closed by Daniel Baumann (reply to daniel.baum...@progress-technologies.net) (Re: Missing required dependencies)

On 05/19/2014 09:40 AM, Benny Baumann wrote: > Even then you should make sure you are recommending the correct > version (python3 >= 3.3) which currently is not the case. there is no such thing as versioned recommends. > Furthermore when running basic commands (and starting a container > really I

Bug#721621: [Pkg-nagios-devel] Bug#721621: dependency change s/libradiusclient-ng2/libfreeradius-client2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Daniel, Am 26.02.14 08:46, schrieb Jan Wagner: > Am 02.02.14 22:18, schrieb Daniel Pocock: >> Looks like argument 1 and 6 are new. They may or may not be >> needed, if we are lucky you can just insert 0 for missing >> arguments and it will emul

Bug#748742: liferea: Crashes some seconds after launch even without user interaction (segfault in libpthread)

On Tue, 20 May 2014 18:22:20 -0500 David Smith wrote: > Please install the liferea-dbg package and then start liferea as > follows: gdb liferea > ... > ... > [crash] > bt full i had to run the "run" command to gdb or it would stay blocked indefinitely, hope that does not mess up the backtrace. Y

Bug#747934: marked as done (FTBFS: type dict/0 is deprecated)

Your message dated Wed, 21 May 2014 07:33:48 + with message-id and subject line Bug#747934: fixed in erlang-meck 0.8.2+dfsg-1 has caused the Debian Bug report #747934, regarding FTBFS: type dict/0 is deprecated to be marked as done. This means that you claim that the problem has been dealt wi

Bug#747765: marked as done (ykclient: FTBFS: error: The pkg-config script could not be found or is too old)

Your message dated Wed, 21 May 2014 07:34:16 + with message-id and subject line Bug#747765: fixed in ykclient 2.12-3 has caused the Debian Bug report #747765, regarding ykclient: FTBFS: error: The pkg-config script could not be found or is too old to be marked as done. This means that you cl

Bug#746080: marked as done (erlang-cherly: FTBFS: ERROR: OTP release 17 does not match required regex R14B04|R15B02|R15B03|R16B)

Your message dated Wed, 21 May 2014 07:18:45 + with message-id and subject line Bug#746080: fixed in erlang-cherly 0.12.8+dfsg-4 has caused the Debian Bug report #746080, regarding erlang-cherly: FTBFS: ERROR: OTP release 17 does not match required regex R14B04|R15B02|R15B03|R16B to be marked