Bug#762417: vinagre: cannot connect - libgrypt error?

Package: vinagre Version: 3.12.2-2 Severity: grave Justification: renders package unusable Hi, till recently I was a happy user of vinagre, but today I wanted to check something on a server and vinagre died on me ... repeatatly: The end is always with: Fatal: failed to create the RNG lock: Inva

Bug#762413: taskcoach: Please relax dependency on python-wxgtk3.0

Source: taskcoach Version: 1.4.1-1 Severity: serious Justification: blocks an on-going transition Tags: sid jessie User: freewx-ma...@lists.alioth.debian.org Usertags: wxpy3.0 Control: block 755757 by -1 Thanks for updating taskcoach to use wxpython3.0. However, the versioned dependencies you've

Processed: taskcoach: Please relax dependency on python-wxgtk3.0

Processing control commands: > block 755757 by -1 Bug #755757 [release.debian.org] transition: wxpython3.0 755757 was blocked by: 757755 757431 759076 759048 758954 759075 758947 759047 758941 759045 758948 758953 759083 758950 758944 758942 759043 758943 759044 757886 758957 757299 759049 75905

Bug#762295: live-boot: live image failed to boot. can not mount /dev/loop0 on //filesystem.squashfs

severity 762295 normal tag 762295 unreproducible thanks the images work for me on a multitude of different machines. -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/

Processed: Re: Bug#762295: live-boot: live image failed to boot. can not mount /dev/loop0 on //filesystem.squashfs

Processing commands for cont...@bugs.debian.org: > severity 762295 normal Bug #762295 [live-boot] live-boot: live image failed to boot. can not mount /dev/loop0 on //filesystem.squashfs Severity set to 'normal' from 'grave' > tag 762295 unreproducible Bug #762295 [live-boot] live-boot: live image

Bug#759226: icedtea-netx fails to install (missing dependency on OpenJDK 8?)

Package: icedtea-netx Version: 1.5.1-1 Followup-For: Bug #759226 Hi, The cause of the bug seems to be icedtea-netx.postinst.in file. If you look into it carefully, it will try to install all alternatives unconditionally, see below trimmed version for brevity. There also seems to be a typo on the

Bug#758954: drpython: Patch for wxPython 3.0

Control: tags 758954 + patch Dear maintainer, I've updated drpython to the latest upstream release, and added a patch to rename some uses of deprecated wx constant names (this isn't vital for wxPython 3.0, but improves compatibility with future release, while still working with wxPython 2.8). Th

Processed: drpython: Patch for wxPython 3.0

Processing control commands: > tags 758954 + patch Bug #758954 [src:drpython] drpython: Please update to use wxpython3.0 Added tag(s) patch. -- 758954: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=758954 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRI

Bug#762411: f2fs-tools: FTBFS on big-endian architectures

Source: f2fs-tools Version: 1.4.0-1 Severity: serious Tags: help Justification: fails to build from source (but built successfully in the past) f2fs-tools 1.4.0 currently FTBFS on big-endian archs supported in Debian, i.e. mips, powerpc, s390x, and sparc; tail of build log as follows: /bin/bash .

Processed: Re: Bug#760688: geoip-database-update script coding errors

Processing commands for cont...@bugs.debian.org: > package geoip-database-contrib Limiting to bugs with field 'package' containing at least one of 'geoip-database-contrib' Limit currently set to 'package':'geoip-database-contrib' > severity 760688 normal Bug #760688 [geoip-database-contrib] geoi

Bug#760688: geoip-database-update script coding errors

package geoip-database-update severity 760688 normal thanks On Sun, Sep 21, 2014 at 4:25 PM, Ludovico Cavedon wrote: >> 2. file update has race conditions: >>- file is removed and later downloaded >>- file decompresion is in place, this exposes partial file to user >> >> 3. file download-

Bug#761559: marked as done (openchange: FTBFS: Tests failures)

Your message dated Sun, 21 Sep 2014 23:50:09 + with message-id and subject line Bug#761559: fixed in openchange 1:2.2-5 has caused the Debian Bug report #761559, regarding openchange: FTBFS: Tests failures to be marked as done. This means that you claim that the problem has been dealt with. I

Bug#759407: marked as done (gnat-4.9: gnat1 not found on kfreebsd-i386)

Your message dated Sun, 21 Sep 2014 23:49:26 + with message-id and subject line Bug#759407: fixed in gnat-4.9 4.9.1-3 has caused the Debian Bug report #759407, regarding gnat-4.9: gnat1 not found on kfreebsd-i386 to be marked as done. This means that you claim that the problem has been dealt

Bug#756786: marked as done (ntp: FTBFS on kfreebsd-*)

Your message dated Sun, 21 Sep 2014 23:33:32 + with message-id and subject line Bug#756786: fixed in kfreebsd-kernel-headers 10.1~3 has caused the Debian Bug report #756786, regarding ntp: FTBFS on kfreebsd-* to be marked as done. This means that you claim that the problem has been dealt with

Bug#762372: marked as done (kfreebsd-kernel-headers: regressions make libgtop2 FTBFS)

Your message dated Sun, 21 Sep 2014 23:33:32 + with message-id and subject line Bug#762372: fixed in kfreebsd-kernel-headers 10.1~3 has caused the Debian Bug report #762372, regarding kfreebsd-kernel-headers: regressions make libgtop2 FTBFS to be marked as done. This means that you claim that

Bug#760688: geoip-database-update script coding errors

Hi, first of all for the bug report and the suggestions. I am working in including them. On Sat, Sep 6, 2014 at 3:22 PM, roma1390 wrote: > 1. general naming must be followed, and script named like other update-* > scripts > >update-geoip-database-contrib I am not sure it is a *must* (I coul

Bug#762404: glibc: FTBFS[kfreebsd] tst-execstack fails; expected behaviour

Package: glibc Version: 2.19.11 Severity: serious User: debian-...@lists.debian.org Usertags: kfreebsd Hi, During a test rebuild for kfreebsd 10.1 transition, I noticed that glibc fails to build from source already on kfreebsd 10.0: Encountered regressions that don't match expected failures (de

Bug#762403: gtk+3.0: FTBFS on several archs

Source: gtk+3.0 Version: 3.13.9-2 Severity: serious Justification: FTBFS Hi, sorry I'm a bit lazy so I won't be investigating the reasons for each architecture. Anyway, just to let you know: your package FTBFS on arm64, armel, mips*. Build log summary: https://buildd.debian.org/status/package.

Bug#740509: ifconfig: ioctl(SIOCGIFINFO_IN6): No such device or address

I think I've found a *different* bug while looking for this. A sysctl { CTL_NET, PF_ROUTE, 0, 0, NET_RT_IFLIST, 0 } from kfreebsd-i386 userland on kfreebsd-amd64 9.0 or 10.0 kernel, never seems to fail with ENOMEM! Regardless of given buffer size: Calling sysctl with buffer of size 1024

Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron

ether will walk you through what was being done with screenshots in case that is useful information. I put the current document snapshot up for this bug. You can download the 35 MB tarball from http://dlc.casita.net/~dlc/762146/vp9cb-20140921.tar or just click through the HTML by going to http://dl

Bug#721421: libdevel-bt-perl: FTBFS on armel, hurd-i386, kfreebsd-amd64

On Sun, 21 Sep 2014 23:55:45 +0200, Leon Timmermans wrote: > > Here are some log extracts from recent builds: > > armhf: > > https://buildd.debian.org/status/fetch.php?pkg=libdevel-bt-perl&arch=armhf&ver=0.06-2&stamp=1409851075 > > That suggests the issue is missing symbols in the gdb output. Wha

Bug#758619: reportbug fails with Attempt to unlock mutex that was not locked

This grave bug is still present in reportbug 6.5.1 on fully patched sid, preventing all bug reporting: $ reportbug Attempt to unlock mutex that was not locked Aborted Kind regards, -- Ben Caradoc-Davies -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "u

Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron

Am 21.09.2014 um 23:28 schrieb David L. Craig: > On 14Sep21:2011+0200, Michael Biebl wrote: > >> What were the exact error messages you got? >> Please provide the dpkg log and the output from journalctl -alb > > dpkg.log, kern.log, apt/term.log, and apt/history.log compressed > files are hopefull

Bug#721421: libdevel-bt-perl: FTBFS on armel, hurd-i386, kfreebsd-amd64

On Sun, Sep 21, 2014 at 7:37 PM, Dominic Hargreaves wrote: > On Thu, Sep 04, 2014 at 02:25:44PM +0200, gregor herrmann wrote: > > On Mon, 01 Sep 2014 19:24:18 +0200, Leon Timmermans wrote: > > > > > The attached patch might fix the issue on Hurd, I can't really say much > > > about the issue on a

Bug#758619: more complete backtrace

Hello Simon, On Thu, Aug 21, 2014 at 10:38 AM, Simon McVittie wrote: > --- gtk2_ui.py.orig 2014-08-21 09:28:45.375375786 + > +++ gtk2_ui.py 2014-08-21 09:29:02.843495121 + > @@ -35,6 +35,7 @@ > except: > has_spell = False > > +gtk.set_interactive (0) > gtk.gdk.threads_init ()

Bug#754182: marked as done (chromium-browser: FTBFS on amd64)

Your message dated Sun, 21 Sep 2014 21:24:34 + with message-id and subject line Bug#754182: fixed in chromium-browser 37.0.2062.120-1 has caused the Debian Bug report #754182, regarding chromium-browser: FTBFS on amd64 to be marked as done. This means that you claim that the problem has been

Bug#753761: marked as done ([chromium-broowser] Non free files under GFDL with invariant or front-cover or back-cover texts)

Your message dated Sun, 21 Sep 2014 21:24:33 + with message-id and subject line Bug#753761: fixed in chromium-browser 37.0.2062.120-1 has caused the Debian Bug report #753761, regarding [chromium-broowser] Non free files under GFDL with invariant or front-cover or back-cover texts to be marke

Bug#759407: gnat-4.9: gnat1 not found on kfreebsd-i386

Hi, Ludovic Brenta wrote: > >> Since this is a policy violation (official packages must be built on > >> real hardware, not on virtual machines) I intend to upload -3 to have it > >> rebuilt on kfreebsd-i386 with -2. > > > > Which part of policy is that? > > Heh, I can't find it back. I thought

Bug#752544: Fixed also in experimental

Hi, according to #50, this bug is fixed from upstream for versions greater than 2.41.3. Since the bug wasn't automatically been marked as fixed for the experimental branch (now uploaded in unstable), I'm marking it as such, letting the package (hopefully) reach testing. thanks, Gianfranco Se

Bug#746005: guile-2.0 migration

Don Armstrong writes: > What are your thoughts about supporting guile 1.8 for another release? I'd likely prefer that to dropping lilypond, so no worries. Let's see where we end up. If you can, keep an eye on any critical deadlines and ping me if needed (i.e. if I need to do something to keep

Bug#759407: gnat-4.9: gnat1 not found on kfreebsd-i386

Emilio Pozuelo Monfort writes: > On 21/09/14 02:31, Ludovic Brenta wrote: >> Nicolas Boulenguez writes: >>> A bootstrap issue will remain: building a new gnat-4.9 package >>> installing these symlinks requires a working compiler. >> >> I am now uploading gnat-4.9 4.9.1-2 which solves this proble

Processed: your mail

Processing commands for cont...@bugs.debian.org: > fixed 752544 2.41.4-1 Bug #752544 {Done: Iain Lane } [src:glib2.0] glib2.0: build gobject with -Wl,nodelete to prevent unloading Marked as fixed in versions glib2.0/2.41.4-1. > thanks Stopping processing here. Please contact me if you need assis

Bug#761650: closed by Sylvestre Ledru (Bug#761650: fixed in llvm-toolchain-3.5 1:3.5-2~exp1)

On 21/09/2014 22:11, Andreas Barth wrote: > Hi, > > * Debian Bug Tracking System (ow...@bugs.debian.org) [140921 20:09]: >> Source: llvm-toolchain-3.5 >> Source-Version: 1:3.5-2~exp1 >> >> We believe that the bug you reported is fixed in the latest version of >> llvm-toolchain-3.5, which is due to

Bug#761650: closed by Sylvestre Ledru (Bug#761650: fixed in llvm-toolchain-3.5 1:3.5-2~exp1)

Hi, * Debian Bug Tracking System (ow...@bugs.debian.org) [140921 20:09]: > Source: llvm-toolchain-3.5 > Source-Version: 1:3.5-2~exp1 > > We believe that the bug you reported is fixed in the latest version of > llvm-toolchain-3.5, which is due to be installed in the Debian FTP archive. would it b

Bug#740509: ifconfig: ioctl(SIOCGIFINFO_IN6): No such device or address

On 13:10, Robert Millan wrote: > $ sudo ifconfig -a > : flags=8802 > ifconfig: ioctl(SIOCGIFINFO_IN6): No such device or address > : flags=0<> > ifconfig: ioctl(SIOCGIFINFO_IN6): No such device or address > : flags=0<> > ifconfig: ioctl(SIOCGIFINFO_IN6): No such device or address > : flags=8008 > i

Bug#756334: marked as done (Configure script downloads files from the Internet)

Your message dated Sun, 21 Sep 2014 19:35:21 + with message-id and subject line Bug#756334: fixed in haskell-hoogle 4.2.33-2 has caused the Debian Bug report #756334, regarding Configure script downloads files from the Internet to be marked as done. This means that you claim that the problem

Bug#740509: ifconfig: ioctl(SIOCGIFINFO_IN6): No such device or address

Actually that workaround referred to *if_msghdr* but recent changes have been to *ifa_msghdr*: https://alioth.debian.org/scm/viewvc.php/trunk/glibc-ports/kfreebsd/if_index.c?root=glibc-bsd&r1=1716&r2=2484 so the problem is not quite what I thought. I think I've been seeing two bugs at once. This

Bug#746005: guile-2.0 migration

On Fri, 12 Sep 2014, Rob Browning wrote: > Don Armstrong writes: > > > Should have guessed as much. Upstream probably just doesn't use it. Thanks! > > Certainly -- shout if I can help with anything else. I finally got back into trying to make guile 2.0 work, and apparently there are a whole hos

Bug#762391: dpkg-dev: Unable to sign, weird message from pinentry-curses

Note: The same problem happens in a virtual console. In this case it is not even required to ssh to another host. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Bug#759952: marked as done (freedict: FTBFS: hun-eng.tei:69: parser error : Premature end of data in tag body line 67)

Your message dated Sun, 21 Sep 2014 19:05:21 + with message-id and subject line Bug#759952: fixed in freedict 2014.09.20-2 has caused the Debian Bug report #759952, regarding freedict: FTBFS: hun-eng.tei:69: parser error : Premature end of data in tag body line 67 to be marked as done. This

Bug#762391: dpkg-dev: Unable to sign, weird message from pinentry-curses

Package: dpkg-dev Version: 1.17.13 Severity: serious When trying to build a trivial package on another machine via ssh, I get this: You need a passphrase to unlock the secret [...] [...] [...] pinentry-curses: no LC_CTYPE known - assuming UTF-8

Bug#759407: gnat-4.9: gnat1 not found on kfreebsd-i386

On 21/09/14 02:31, Ludovic Brenta wrote: > Nicolas Boulenguez writes: >> A bootstrap issue will remain: building a new gnat-4.9 package >> installing these symlinks requires a working compiler. > > I am now uploading gnat-4.9 4.9.1-2 which solves this problem. I > bootstrapped it on a kfreebsd-i

Bug#740509: ifconfig: ioctl(SIOCGIFINFO_IN6): No such device or address

reassign 740509 libc0.1 found 740509 glibc/2.19-11 tags 740509 + jessie sid affects 740509 freebsd-net-tools user debian-...@lists.debian.org usertags 740509 + kfreebsd thanks On 13:10, Robert Millan wrote: > $ sudo ifconfig -a > : flags=8802 > ifconfig: ioctl(SIOCGIFINFO_IN6): No such device or a

Bug#731481: marked as done (zvbi: FTBFS on kfreebsd-*/hurd-i386 due to missing symbols)

Your message dated Sun, 21 Sep 2014 18:19:15 + with message-id and subject line Bug#731481: fixed in zvbi 0.2.35-3 has caused the Debian Bug report #731481, regarding zvbi: FTBFS on kfreebsd-*/hurd-i386 due to missing symbols to be marked as done. This means that you claim that the problem ha

Bug#762275: error while upgrading

Control: tags -1 moreinfo Am 20.09.2014 um 22:46 schrieb Michael Biebl: > Am 20.09.2014 um 15:44 schrieb Joseph Nahmias: >> Package: systemd >> Version: 215-4 >> Severity: grave >> >> >> Hello, >> >> While attempting to upgrade systemd this morning, dpkg errored out with the >> following message:

Processed: Re: Bug#762275: error while upgrading

Processing control commands: > tags -1 moreinfo Bug #762275 [systemd] error while upgrading Added tag(s) moreinfo. -- 762275: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762275 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To UNSUBSCRIBE, email to debian-bugs-r

Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron

Control: tags -1 + moreinfo Am 19.09.2014 um 00:08 schrieb David L. Craig: > Installed Beta 1 D-I amd64 netinst without mirror or > standard utils in preparation for dist-upgrade to Sid > using aptitude with sources.list: > > deb ftp://debian.csail.mit.edu/debian/ sid main > > udev and aptitude

Processed: Re: Bug#762146: Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron

Processing control commands: > tags -1 + moreinfo Bug #762146 [udev] Upgrade To Sid From Beta D-I Breaks systemd, udev, and cron Added tag(s) moreinfo. -- 762146: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=762146 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- T

Bug#762211: [Pkg-xfce-devel] Bug#762211: lightdm crashes on startup, system falls back to console

control: severity -1 important control: tag -1 moreinfo unreproducible On ven., 2014-09-19 at 16:37 +0200, Fabio Rosciano wrote: > Package: lightdm > Version: 1.10.2-1 > Severity: critical > Justification: breaks the whole system > > Hello, > > I cannot start lightdm on my system with Intel grap

Processed: Re: [Pkg-xfce-devel] Bug#762211: lightdm crashes on startup, system falls back to console

Processing control commands: > severity -1 important Bug #762211 [lightdm] lightdm crashes on startup, system falls back to console Severity set to 'important' from 'critical' > tag -1 moreinfo unreproducible Bug #762211 [lightdm] lightdm crashes on startup, system falls back to console Added tag(

Bug#756827: marked as done (urjtag: FTBFS on arm*)

Your message dated Sun, 21 Sep 2014 17:49:40 + with message-id and subject line Bug#756827: fixed in urjtag 0.10+r2007-1.2 has caused the Debian Bug report #756827, regarding urjtag: FTBFS on arm* to be marked as done. This means that you claim that the problem has been dealt with. If this is

Bug#759981: marked as done (stdeb: FTBFS: help2man: can't get `--help' info from /«PKGBUILDDIR»/debian/python-stdeb/usr/bin/pypi-install)

Your message dated Sun, 21 Sep 2014 17:49:32 + with message-id and subject line Bug#759981: fixed in stdeb 0.8.2-3 has caused the Debian Bug report #759981, regarding stdeb: FTBFS: help2man: can't get `--help' info from /«PKGBUILDDIR»/debian/python-stdeb/usr/bin/pypi-install to be marked as d

Bug#721421: [rt.cpan.org #93585] Test failures on armel, kfreebsd-amd64, mips

[Adding mips and armhf porters; please see for context. On Fri, Aug 29, 2014 at 03:53:52PM -0400, Karen Etheridge via RT wrote: > 11:49 did you see this? > https://rt.cpan.org/Ticket/Display.html?id=93585 > 12:32 i did just now for the

Processed: retitle 721421 to libdevel-bt-perl: FTBFS on armhfs, mips (and hurd-i386, kfreebsd-i386, arm64)

Processing commands for cont...@bugs.debian.org: > retitle 721421 libdevel-bt-perl: FTBFS on armhfs, mips (and hurd-i386, > kfreebsd-i386, arm64) Bug #721421 [src:libdevel-bt-perl] libdevel-bt-perl: FTBFS on armel, hurd-i386, kfreebsd-amd64 Changed Bug title to 'libdevel-bt-perl: FTBFS on armhfs

Bug#721421: libdevel-bt-perl: FTBFS on armel, hurd-i386, kfreebsd-amd64

On Thu, Sep 04, 2014 at 02:25:44PM +0200, gregor herrmann wrote: > On Mon, 01 Sep 2014 19:24:18 +0200, Leon Timmermans wrote: > > > The attached patch might fix the issue on Hurd, I can't really say much > > about the issue on armel or kfreebsd-amd64 without having some build/test > > output from

Bug#759324: [libdbd-oracle-perl] conflicts with perl-5.20

On Tue, Aug 26, 2014 at 11:07:35AM +0200, Michał Mirosław wrote: > Please rebuild DBD::Oracle package with perl 5.20 from sid. Right now it > can't > be installed, because it depends on perlapi-5.18.1. Please consider using > latest version. Hi Julián, We discussed this a bit on IRC, and it se

Bug#761413: vtk6: Patch for wxPython 3.0

Hi Olly, thanks for the patch! I am planning to do a new vtk6 upload next week, so I will include your patch as well. Best regards Anton 2014-09-20 1:11 GMT+02:00 Olly Betts : > Control: tags 761413 + patch > Control: severity -1 serious > # Justification: blocks the on-going wxpython3.0 trans

Bug#760657: marked as done ([cmtk]Non free files under GFDL with invariant or front-cover or back-cover texts)

Your message dated Sun, 21 Sep 2014 16:33:45 + with message-id and subject line Bug#760657: fixed in cmtk 3.2.2-1 has caused the Debian Bug report #760657, regarding [cmtk]Non free files under GFDL with invariant or front-cover or back-cover texts to be marked as done. This means that you cl

Bug#749659: audacity + wxWidgets 3.0 — Proposing patch

On 09/14/2014 10:14 PM, Reinhard Tartler wrote: Please remind me, what was the autoreconf problem, and how has it been fixed upstream? I'm really not comfortable with uploading an about 500kb diff. I agree, having that patch in the actual package is not an option, it's huge, opaque and will b

Bug#762372: kfreebsd-kernel-headers: regressions make libgtop2 FTBFS

Package: kfreebsd-kernel-headers Version: 10.0~1 Severity: serious Tags: pending Hi, During a test rebuild for the kfreebsd 10.1 transition, it was noticed that libgtop2 currently FTBFS, due to past regressions in kfreebsd-kernel-headers 10.0 in sid not noticed yet: * __FreeBSD_kernel_version wa

Bug#762283: Acknowledgement (redmine: not starting)

I tracked problem down to "ruby-awesome-nested-set" 3.0.0-1 -- downgrading it to 2.1.6-1 fixed the problem (thanks, snapshot.debian.org). -- Best wishes, Dmitry Smirnov. signature.asc Description: This is a digitally signed message part.

Processed: reassign 762283 to redmine

Processing commands for cont...@bugs.debian.org: > reassign 762283 redmine 2.5.2-1 Bug #762283 [ruby-awesome-nested-set] redmine is not starting Bug reassigned from package 'ruby-awesome-nested-set' to 'redmine'. No longer marked as found in versions ruby-awesome-nested-set/3.0.0-1. Ignoring reque

Processed: retitle 762283 to redmine is not compatible with ruby-awesome-nested-set/3.0.0-1

Processing commands for cont...@bugs.debian.org: > retitle 762283 redmine is not compatible with ruby-awesome-nested-set/3.0.0-1 Bug #762283 [redmine] redmine is not starting Changed Bug title to 'redmine is not compatible with ruby-awesome-nested-set/3.0.0-1' from 'redmine is not starting' > tha

Processed: reassign 762283 to ruby-awesome-nested-set

Processing commands for cont...@bugs.debian.org: > reassign 762283 ruby-awesome-nested-set 3.0.0-1 Bug #762283 [redmine] redmine: not starting Bug reassigned from package 'redmine' to 'ruby-awesome-nested-set'. No longer marked as found in versions redmine/2.5.2-1. Ignoring request to alter fixed

Processed: retitle 762283 to redmine is not starting

Processing commands for cont...@bugs.debian.org: > retitle 762283 redmine is not starting Bug #762283 [ruby-awesome-nested-set] redmine: not starting Changed Bug title to 'redmine is not starting' from 'redmine: not starting' > thanks Stopping processing here. Please contact me if you need assist

Bug#762300: marked as done (libuv: Versioned provides not supported during upgrades)

Your message dated Sun, 21 Sep 2014 13:48:42 + with message-id and subject line Bug#762300: fixed in libuv 0.10.28-5 has caused the Debian Bug report #762300, regarding libuv: Versioned provides not supported during upgrades to be marked as done. This means that you claim that the problem has

Bug#759701: marked as done (libstxxl: FTBFS on 32-bit architectures)

Your message dated Sun, 21 Sep 2014 15:37:08 +0200 with message-id and subject line Close the bug has caused the Debian Bug report #759701, regarding libstxxl: FTBFS on 32-bit architectures to be marked as done. This means that you claim that the problem has been dealt with. If this is not the c

Processed: Close the bug

Processing commands for cont...@bugs.debian.org: > fixed 759701 1.4.0-3 Bug #759701 [src:libstxxl] libstxxl: FTBFS on 32-bit architectures Marked as fixed in versions libstxxl/1.4.0-3. > thanks Stopping processing here. Please contact me if you need assistance. -- 759701: http://bugs.debian.org/

Bug#759701: Close the bug

fixed 759701 1.4.0-3 thanks

Bug#762329: marked as done (libjson-any-perl: breaks libcgi-application-plugin-ajaxupload-perl test suite)

Your message dated Sun, 21 Sep 2014 15:49:53 +0300 with message-id <20140921124953.GA3364@estella.local.invalid> and subject line Re: Bug#762329: libjson-any-perl: breaks libcgi-application-plugin-ajaxupload-perl test suite has caused the Debian Bug report #762329, regarding libjson-any-perl: brea

Bug#761550: Imagemagick transition

On Mon, Sep 15, 2014 at 11:39:03PM +0200, Gabriele Giacone wrote: > Bastien, > > On Mon, Sep 15, 2014 at 10:21 PM, Bastien ROUCARIES > wrote: > > the debdiff > > - default-jdk, libmagickcore-extra, python (>= 2.6.6-3~) > + default-jdk, python (>= 2.6.6-3~), > + libmagickcore-6.q16-2-extra > > F

Bug#760476: cups - crashes after reading tls stuff

On 2014-09-16 Didier 'OdyX' Raboud wrote: [...] > Le jeudi, 4 septembre 2014, 13.30:19 Bastian Blank a écrit : >> cups aborts at random times after reading certificates and keys: >> (…) >> As cups disables generation of core files, no additional information > > is available. > Would it be imagin

Bug#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory

On 09/21/2014 12:14 PM, Michael Prokop wrote: * Jerome Martin [Sat Sep 20, 2014 at 07:57:47PM +0200]: I could use (read "desperately require" :-) ) tests and reports myself, so please guys, I will be working on the upstream code next week, now is a good time to fill my inbox with reports :-)

Bug#762272: doxygen: segfaults when building efl (on ix86 amd amd64)

On 2014-09-20 Helmut Grohne wrote: [...] > Andreas, could you add a debian/rules target to efl that allows just > building the documentation? I'd like to add efl as a autopkgtest case to > doxygen to spot this kind of issue earlier. Hello, I have not commit access for efl, however doesn't debi

Bug#468929: Processed: jessie

Control: retitle -1 libmail-cclient-perl: Fails to open any mailbox Hi Holger, Holger Levsen wrote: > On Sonntag, 21. September 2014, Axel Beckert wrote: > > why do you think that this bug report does not apply to Wheezy? > > I didnt mean to imply this. I tagged it "+ sid jessie" to indicate the

Processed: Re: Processed: jessie

Processing control commands: > retitle -1 libmail-cclient-perl: Fails to open any mailbox Bug #468929 [libmail-cclient-perl] libmail-cclient-perl: test failures Changed Bug title to 'libmail-cclient-perl: Fails to open any mailbox' from 'libmail-cclient-perl: test failures' -- 468929: http://bu

Bug#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory

Hi, * Jerome Martin [Sat Sep 20, 2014 at 07:57:47PM +0200]: > On 09/20/2014 01:24 PM, Ritesh Raj Sarraf wrote: > >On Saturday 20 September 2014 02:58 PM, Ritesh Raj Sarraf wrote: > >>I just pushed configshel 1.5 into experimental. > >>Next in line is rtslib and targetcli (both from git tip). Once

Bug#468929: Processed: jessie

Hi Axel, thanks for cleaning up my mistakes! Much appreciated! :) On Sonntag, 21. September 2014, Axel Beckert wrote: > why do you think that this bug report does not apply to Wheezy? I didnt mean to imply this. I tagged it "+ sid jessie" to indicate the RC severity doesnt apply to wheezy. As t

Bug#762186: [Python-modules-team] Bug#762186: python-pypdf: Unexpectedly breaks existing programs on update

On Sun, Sep 21, 2014 at 2:54 AM, Vincent Cheng wrote: > Dear maintainer, > > On Thu, 18 Sep 2014 22:42:50 +0200 Elena Grandi > wrote: >> Package: python-pypdf >> Version: 1.23-1 >> Severity: grave >> Justification: renders package unusable >> >> Dear Maintainer, >> >> updating python-pypdf from 1

Bug#762186: python-pypdf: Unexpectedly breaks existing programs on update

Dear maintainer, On Thu, 18 Sep 2014 22:42:50 +0200 Elena Grandi wrote: > Package: python-pypdf > Version: 1.23-1 > Severity: grave > Justification: renders package unusable > > Dear Maintainer, > > updating python-pypdf from 1.13 to 1.23 breaks every existing script > that use this module with a

Bug#468929: Processed: jessie

Control: tag 468929 - sid jessie Hi Holger, Debian Bug Tracking System wrote: > Processing commands for cont...@bugs.debian.org: > > tag 468929 + sid jessie > Bug #468929 [libmail-cclient-perl] libmail-cclient-perl: test failures > Added tag(s) sid and jessie. why do you think that this bug repo

Processed: Re: Processed: jessie

Processing control commands: > tag 468929 - sid jessie Bug #468929 [libmail-cclient-perl] libmail-cclient-perl: test failures Removed tag(s) sid and jessie. -- 468929: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=468929 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#762283: redmine: not starting

This is related to ruby-awesome-nested-set which was upgraded from 2.1.6-1~bpo70+1 to 3.0.0-1 and broke redmine. You can download the package from https://packages.debian.org/wheezy-backports/all/ruby-awesome-nested-set/download and downgrade it. And at some point, redmine will probably support t

Bug#759093: marked as done (winpdb: Please update to use wxpython3.0)

Your message dated Sun, 21 Sep 2014 09:21:14 + with message-id and subject line Bug#759093: fixed in winpdb 1.4.8-2.1 has caused the Debian Bug report #759093, regarding winpdb: Please update to use wxpython3.0 to be marked as done. This means that you claim that the problem has been dealt wi

Processed: jessie

Processing commands for cont...@bugs.debian.org: > tag 468929 + sid jessie Bug #468929 [libmail-cclient-perl] libmail-cclient-perl: test failures Added tag(s) sid and jessie. > tag 762325 + sid jessie Bug #762325 [src:libgd2] libgd2: not binNMU safe Added tag(s) sid and jessie. > tag 762227 + sid

Bug#759093: winpdb: Patch for wxPython 3.0

I spotted the "About" and "Licence" windows weren't sizing correctly, so I fixed that, and also dropped the BD on lsb-release which there was a bug filed about. There's one difference with wx 3.0 still - I noticed the initial positions of the sashes in the splitter windows isn't quite the same as

Processed: block 762329 with 762334

Processing commands for cont...@bugs.debian.org: > # almost there > block 762329 with 762334 Bug #762329 [libjson-any-perl] libjson-any-perl: breaks libcgi-application-plugin-ajaxupload-perl test suite 762329 was not blocked by any bugs. 762329 was not blocking any bugs. Added blocking bug(s) of

Processed (with 1 errors): Re: Bug#762329: libjson-any-perl: breaks libcgi-application-plugin-ajaxupload-perl test suite

Processing commands for cont...@bugs.debian.org: > # > (we'll see how that goes :) > # didn't go well because of one newline too much; retrying > clone 762329 -2 -3 Bug #762329 [libjson-any-perl] libjson-any-perl: breaks libcgi-application-plugin-ajaxupload-perl test suite Bug 762329 cloned as bu

Bug#762329: libjson-any-perl: breaks libcgi-application-plugin-ajaxupload-perl test suite

Package: libjson-any-perl Version: 1.36-1 Severity: serious Control: clone -1 -2 -3 Control: retitle -2 libcgi-application-plugin-ajaxupload-perl: FTBFS with libjson-any-perl 1.36-1: test failures Control: tags -2 sid Control: reassign -2 libcgi-application-plugin-ajaxupload-perl 0.0.3-6 Control:

Bug#759031: marked as done (init-select: Offers not installed inits, confusing error messages, unhelpfull description)

Your message dated Sun, 21 Sep 2014 07:48:34 + with message-id and subject line Bug#759031: fixed in init-select 1.20140921 has caused the Debian Bug report #759031, regarding init-select: Offers not installed inits, confusing error messages, unhelpfull description to be marked as done. This

Bug#750255: lio-utils: FTBFS: chmod: cannot access '/«BUILDDIR»/lio-utils-3.1+git2.fd0b34fd/debian/lio-utils/usr/share/pyshared/*.py': No such file or directory

On Saturday 20 September 2014 03:23 PM, Jerome Martin wrote: Yes, the problem is that the kernel side uses this path unfortunately. We could relocate policy and fabric to /var/lib/target, but that would mean keeping both /lib/target and /var/target around for now, as the kernel will use that fo

Bug#759252: gjay: diff for NMU version 0.3.2-1.1

On Sun, Sep 14, 2014 at 08:47:17PM -0500, Julián Moreno Patiño wrote: > I'm sorry for the NMU, I see the email too late, so I can't > cancel it. No problem at all, you were fine to go ahead with it. - Craig -- Craig Small (@smallsees) http://enc.com.au/ csmall at : enc.com.au Debian GNU/