Bug#749363: marked as done (FIXME in debian/copyright)

Your message dated Tue, 21 Oct 2014 06:48:46 + with message-id and subject line Bug#749363: fixed in ardour 1:2.8.16+git20131003-4 has caused the Debian Bug report #749363, regarding FIXME in debian/copyright to be marked as done. This means that you claim that the problem has been dealt with

Bug#766134: coinutils: lapack and blas support is not really enabled

Package: src:coinutils Version: 2.9.15-1 Severity: serious Tag: patched liblapack and libblas are in the building depends list while in build log, there are lines: checking whether -lblas has BLAS... no checking for COIN-OR package Blas... skipped check via pkg-config, redirect to fallback checki

Bug#765852: marked as done (s3ql: FTBFS - pkg_resources.VersionConflict: (py 1.4.24 (/usr/lib/python3/dist-packages), Requirement.parse('py>=1.4.25')))

Your message dated Tue, 21 Oct 2014 04:36:26 + with message-id and subject line Bug#765844: fixed in pytest 2.6.3-2 has caused the Debian Bug report #765844, regarding s3ql: FTBFS - pkg_resources.VersionConflict: (py 1.4.24 (/usr/lib/python3/dist-packages), Requirement.parse('py>=1.4.25')) to

Bug#765844: marked as done (python-pytest: needs to depend on python-py (>= 1.4.25))

Your message dated Tue, 21 Oct 2014 04:36:26 + with message-id and subject line Bug#765844: fixed in pytest 2.6.3-2 has caused the Debian Bug report #765844, regarding python-pytest: needs to depend on python-py (>= 1.4.25) to be marked as done. This means that you claim that the problem has

Processed: your mail

Processing commands for cont...@bugs.debian.org: > tag 765844 + pending Bug #765844 [python-pytest] python-pytest: needs to depend on python-py (>= 1.4.25) Bug #765852 [python-pytest] s3ql: FTBFS - pkg_resources.VersionConflict: (py 1.4.24 (/usr/lib/python3/dist-packages), Requirement.parse('py>

Processed: Re: Bug#765107: librest: FTBFS - segmentation fault in test custom-serialize

Processing control commands: > reassign -1 src:librest 0.7.92-1 Bug #765107 [librest] librest: FTBFS - segmentation fault in test custom-serialize Bug reassigned from package 'librest' to 'src:librest'. No longer marked as found in versions 0.7.92-1. Ignoring request to alter fixed versions of bu

Bug#765107: librest: FTBFS - segmentation fault in test custom-serialize

Control: reassign -1 src:librest 0.7.92-1 Control: forcemerge 765141 -1 On 2014-10-13 17:54:03, Michael Tautschnig wrote: > Package: librest > Version: 0.7.92-1 > Severity: serious > Usertags: goto-cc > > During a rebuild of all Debian packages in a clean sid chroot (using > cowbuilder > and pbu

Bug#763237: marked as done (gav: FTBFS: ld: final link failed: Bad value)

Your message dated Tue, 21 Oct 2014 05:42:52 +0200 with message-id <20141021034252.gd8...@ramacher.at> and subject line Re: Bug#763237: ld problem tracked in #764573 has caused the Debian Bug report #763237, regarding gav: FTBFS: ld: final link failed: Bad value to be marked as done. This means th

Bug#765131: shogun: diff for NMU version 3.2.0-7.3

Control: tags 765131 + patch Control: tags 765131 + pending Dear maintainer, I've prepared an NMU for shogun (versioned as 3.2.0-7.3) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru shogun-3.2.0/debian/changelog shogu

Bug#765290: marked as done (mruby: FTBFS on armel: Segmentation fault)

Your message dated Tue, 21 Oct 2014 12:42:38 +0900 with message-id and subject line Re: Bug#765290: mruby: FTBFS on armel: Segmentation fault has caused the Debian Bug report #765290, regarding mruby: FTBFS on armel: Segmentation fault to be marked as done. This means that you claim that the pro

Processed: shogun: diff for NMU version 3.2.0-7.3

Processing control commands: > tags 765131 + patch Bug #765131 [src:shogun] shogun: FTBFS: make[2]: python: Command not found Added tag(s) patch. > tags 765131 + pending Bug #765131 [src:shogun] shogun: FTBFS: make[2]: python: Command not found Added tag(s) pending. -- 765131: http://bugs.debian

Processed: Re: Bug#751498 closed by Laszlo Boszormenyi (GCS) (Bug#751498: fixed in python-greenlet 0.4.5-1)

Processing control commands: > reopen -1 Bug #751498 {Done: Laszlo Boszormenyi (GCS) } [src:python-greenlet] python-greenlet: FTBFS on arm* due to test failures 'reopen' may be inappropriate when a bug has been closed with a version; all fixed versions will be cleared, and you may need to re-add

Bug#751498: closed by Laszlo Boszormenyi (GCS) (Bug#751498: fixed in python-greenlet 0.4.5-1)

Control: reopen -1 On 2014-10-18 17:21:10, Debian Bug Tracking System wrote: > python-greenlet (0.4.5-1) unstable; urgency=medium > . >* New upstream release, fixes crashes on ARM and MIPS (closes: 751498). Unfortunately that doesn't seem to be enough. It still crashes on mips and also fail

Bug#751062: marked as done (python-greenlet: FTBFS - FAIL: test_threaded_adv_leak (tests.test_leaks.ArgRefcountTests))

Your message dated Tue, 21 Oct 2014 05:18:49 +0200 with message-id <20141021031849.ga8...@ramacher.at> and subject line Re: Bug#751062: python-greenlet: FTBFS - FAIL: test_threaded_adv_leak (tests.test_leaks.ArgRefcountTests) has caused the Debian Bug report #751062, regarding python-greenlet: FTB

Processed: rurple-ng: diff for NMU version 0.5+16-1.2

Processing control commands: > tags 764989 + patch Bug #764989 [src:rurple-ng] rurple-ng: FTBFS: "xsltproc" ... returned exit status 5 Added tag(s) patch. > tags 764989 + pending Bug #764989 [src:rurple-ng] rurple-ng: FTBFS: "xsltproc" ... returned exit status 5 Added tag(s) pending. -- 764989

Bug#764989: rurple-ng: diff for NMU version 0.5+16-1.2

Control: tags 764989 + patch Control: tags 764989 + pending Dear maintainer, I've prepared an NMU for rurple-ng (versioned as 0.5+16-1.2) and uploaded it to DELAYED/2. Please feel free to tell me if I should delay it longer. Cheers -- Sebastian Ramacher diff -Nru rurple-ng-0.5+16/debian/changel

Bug#766092: systemd: Boot hangs indefinitely

Am 21.10.2014 um 02:19 schrieb Marcelo Laia: > On 21/10/14 at 01:07am, Michael Biebl wrote: >> How long did you wait? > > no limit! Indefinitely > Could you check your /tmp (and /var/tmp) directory if it contains a large amount of symlinks (created by cups) or files. IIRC there is a bug report t

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

Hi! The attached patch is my best guess at how to fix this bug. I'm still testing it myself, but I'm sharing it now in case anyone else is able to build glibc on kfreebsd-i386 and also help test. (It can take many hours to build glibc). getifaddrs() uses a NET_RT_IFLIST sysctl to get back a str

Bug#766092: systemd: Boot hangs indefinitely

On 21/10/14 at 02:29am, Michael Biebl wrote: Hi, > Btw, is there anything special about your setup, e.g. how does your > partition layout look like? :~$ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:00 111,8G 0 disk ├─sda1 8:10 23,3G 0 part / ├─sda2 8:20 1K

Bug#766092: systemd: Boot hangs indefinitely

On 21/10/14 at 02:27am, Michael Biebl wrote: > Can you tar those files and send attach them to the bug report, please. > Here you are! -- Laia, ML http://ppgcf.ufvjm.edu.br/~ppgcf/marcelolaia output.tar Description: Unix tar archive

Bug#766092: systemd: Boot hangs indefinitely

Am 21.10.2014 um 02:27 schrieb Michael Biebl: > Hi, > > Am 21.10.2014 um 02:19 schrieb Marcelo Laia: >> # ls -l /usr/lib/tmpfiles.d.old/ >> total 48 >> -rw-r--r-- 1 root root 480 Set 28 16:05 debian.conf >> -rw-r--r-- 1 root root 595 Set 22 14:43 gvfsd-fuse-tmpfiles.conf >> -rw-r--r-- 1 root roo

Bug#766092: systemd: Boot hangs indefinitely

Hi, Am 21.10.2014 um 02:19 schrieb Marcelo Laia: > # ls -l /usr/lib/tmpfiles.d.old/ > total 48 > -rw-r--r-- 1 root root 480 Set 28 16:05 debian.conf > -rw-r--r-- 1 root root 595 Set 22 14:43 gvfsd-fuse-tmpfiles.conf > -rw-r--r-- 1 root root 1181 Set 28 16:05 legacy.conf > -rw-r--r-- 1 root root

Bug#766092: systemd: Boot hangs indefinitely

On 21/10/14 at 01:07am, Michael Biebl wrote: > How long did you wait? no limit! Indefinitely > Which kernel version is it exactly? :~$ uname -a Linux marcelo 3.16-2-686-pae #1 SMP Debian 3.16.3-2 (2014-09-20) i686 GNU/Linux :~$ I found a workaround [1] and can boot after I did it: # mv /usr/l

Bug#759079: marked as done (pyhoca-gui: Please update to use wxpython3.0)

Your message dated Mon, 20 Oct 2014 23:49:51 + with message-id and subject line Bug#759079: fixed in pyhoca-gui 0.5.0.2-1 has caused the Debian Bug report #759079, regarding pyhoca-gui: Please update to use wxpython3.0 to be marked as done. This means that you claim that the problem has been

Bug#766092: systemd: Boot hangs indefinitely

Am 20.10.2014 um 23:55 schrieb Marcelo Laia: > The same here! Breaks the whole system! Isn't possible to boot! O hit > Ctrl+Alt+Del and system reboot and hang again! The message is: > > "a start job is running for Create Volatile files and directories (xx > minutes / no limit)" > > My kernels are

Bug#766114: fso-deviced: uninstallable in i386/amd64/armhf

Package: fso-deviced Version: 0.12.0-2 Severity: grave Justification: renders package unusable Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I suspect fso-deviced isn't fit/wasn't properly ported to systemd sin

Bug#766068: RFS: robocode 1.6.2+dfsg2-1 [ITA] [RC]

On Mon, Oct 20, 2014 at 11:58:06PM +0200, Markus Koschany wrote: > Hi all, > > I have recently adopted Robocode, a Java programming game, and I think > [...] Hi Markus, I'll take care of it. Cheers, -- Miguel Landaeta, nomadium at debian.org secure email with PGP 0x6E608B637D8967E9 available

Bug#761001:

Hi, i'm on Jessie with GDM 3.14.0-1, after update and reboot I also cannot login. gdm3 asks for username and password, and then tries to load gnome but restarts itself and ask again for username and password. I can only login, if a change from gdm3 to ligthdm for example. -- To UNSUBSCRIBE, e

Bug#766092: systemd: Boot hangs indefinitely

The same here! Breaks the whole system! Isn't possible to boot! O hit Ctrl+Alt+Del and system reboot and hang again! The message is: "a start job is running for Create Volatile files and directories (xx minutes / no limit)" My kernels are the Debian default linux-images. I don't compile it. --

Bug#766068: RFS: robocode 1.6.2+dfsg2-1 [ITA] [RC]

Hi all, I have recently adopted Robocode, a Java programming game, and I think it fits best into the Java team. It is currently affected by RC bug #766068 that prevents users from starting the game. This is a rather old version. Unfortunately it's too late now to package the latest release since i

Bug#764817: marked as done (sudo: fails if kernel auditing disabled)

Your message dated Mon, 20 Oct 2014 21:29:57 + with message-id and subject line Bug#764817: fixed in sudo 1.8.11p1-2 has caused the Debian Bug report #764817, regarding sudo: fails if kernel auditing disabled to be marked as done. This means that you claim that the problem has been dealt with

Bug#764818: marked as done (sudo: Silently fails to execute any commands if kernel compiled with !AUDIT)

Your message dated Mon, 20 Oct 2014 21:29:57 + with message-id and subject line Bug#764817: fixed in sudo 1.8.11p1-2 has caused the Debian Bug report #764817, regarding sudo: Silently fails to execute any commands if kernel compiled with !AUDIT to be marked as done. This means that you claim

Bug#765939: marked as done (src:vtk: FTBFS with error: 'GLintptr' has not beed declared)

Your message dated Mon, 20 Oct 2014 21:28:35 + with message-id and subject line Bug#765939: fixed in paraview 4.1.0+dfsg+1-1 has caused the Debian Bug report #765939, regarding src:vtk: FTBFS with error: 'GLintptr' has not beed declared to be marked as done. This means that you claim that the

Processed: severity of 764762 is serious

Processing commands for cont...@bugs.debian.org: > severity 764762 serious Bug #764762 [src:valabind] Upcoming vala 0.24 removal Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 764762: http://bugs.debian.org/cgi-bin/bugre

Bug#754678: marked as done (openocd: FTBFS on kfreebsd-*: configure: error: libusb-1.x is required for the MPSSE mode of FTDI based devices)

Your message dated Mon, 20 Oct 2014 21:27:02 + with message-id and subject line Bug#754678: fixed in openocd 0.8.0-4 has caused the Debian Bug report #754678, regarding openocd: FTBFS on kfreebsd-*: configure: error: libusb-1.x is required for the MPSSE mode of FTDI based devices to be marked

Bug#753182: marked as done (avian: FTBFS: lto1: internal compiler error: Segmentation fault)

Your message dated Mon, 20 Oct 2014 21:19:57 + with message-id and subject line Bug#753182: fixed in avian 1.1.0-1 has caused the Debian Bug report #753182, regarding avian: FTBFS: lto1: internal compiler error: Segmentation fault to be marked as done. This means that you claim that the probl

Bug#759834: marked as done (avian: FTBFS: src/avian/common.h:115:0: error: "UNUSED" redefined [-Werror])

Your message dated Mon, 20 Oct 2014 21:19:57 + with message-id and subject line Bug#759834: fixed in avian 1.1.0-1 has caused the Debian Bug report #759834, regarding avian: FTBFS: src/avian/common.h:115:0: error: "UNUSED" redefined [-Werror] to be marked as done. This means that you claim t

Bug#763248: valabind: FTBFS: swigwriter.vala:88.34-88.45: error: Argument 1: Cannot convert from `Vala.Expression?' to `int'

Control: tags -1 patch Control: tags -1 fixed-upstream Upstream seems to have a couple of fixes to make valabind build against vala 0.26: https://github.com/radare/valabind/commit/dc16a77fb93183558ff38298ed4eaf7e3ac15e03 https://github.com/radare/valabind/commit/776ff5a33649dfc3cb48d83f9485d3963

Processed: Re: valabind: FTBFS: swigwriter.vala:88.34-88.45: error: Argument 1: Cannot convert from `Vala.Expression?' to `int'

Processing control commands: > tags -1 patch Bug #763248 [src:valabind] valabind: FTBFS: swigwriter.vala:88.34-88.45: error: Argument 1: Cannot convert from `Vala.Expression?' to `int' Added tag(s) patch. > tags -1 fixed-upstream Bug #763248 [src:valabind] valabind: FTBFS: swigwriter.vala:88.34-8

Bug#766101: Should not be released with jessie

Source: vala-0.24 Version: 0.24.0-6 Severity: serious This is a blocker bug to make sure we don't release jessie with vala-0.24. The default vala version for jessie will be 0.26. All reverse dependencies but one (valabind) have been updated to build against vala 0.26. -- System Information: Debi

Bug#765725: Crash with "terminate called after throwing an instance of 'Gio::Error'"

Package: pavucontrol Version: 2.0-2 Followup-For: Bug #765725 I'm experiencing the same error, consistently, when Chromium is running and on a WebRTC-enabled page. For example, start Chromium, enable WebRTC support, go to http://appear.in/linux and accept to share webcam and microphone. Then start

Bug#766092: systemd: Boot hangs indefinitely

On Lu, 20 oct 14, 22:22:28, Thomas Zoschke wrote: > > I just installed my first systemd, previously had sysv-initcore, well-working. > The boot after the installation hung forever after a timed out job for the > boot drive. > I would have expected the system to boot. > I cannot even get to a sulog

Bug#766092: systemd: Boot hangs indefinitely

Package: systemd Version: 215-5+b1 Severity: critical Justification: breaks the whole system Dear Maintainer, I just installed my first systemd, previously had sysv-initcore, well-working. The boot after the installation hung forever after a timed out job for the boot drive. I would have expected

Bug#765968: marked as done (building openssl without sslv3 support breaks tor)

Your message dated Mon, 20 Oct 2014 19:49:15 + with message-id and subject line Bug#765968: fixed in tor 0.2.5.9-rc-1 has caused the Debian Bug report #765968, regarding building openssl without sslv3 support breaks tor to be marked as done. This means that you claim that the problem has been

Bug#754678: openocd: FTBFS on kfreebsd-*: configure: error: libusb-1.x is required for the MPSSE mode of FTDI based devices

> On Mon, Oct 20, 2014 at 03:43:43PM +0200, Luca Bruno wrote: >> On Monday 20 October 2014 17:31:48 Paul Fertser wrote: >> I see. So in the end, let's keep: >> * libusb autodetection for kfreebsd >> * --enable-usb_blaster_libftdi for linux That sounds great, and I think is exactly what we get us

Bug#766030: wine: error: unable to find wine executable. this shouldn't happen.

I confirm the bug and also confirm that the following downgrade: [DOWNGRADE] libwine:i386 1.6.2-13 -> 1.6.2-8 [DOWNGRADE] libwine-print:i386 1.6.2-13 -> 1.6.2-8 [DOWNGRADE] wine:i386 1.6.2-13 -> 1.6.2-8 [DOWNGRADE] wine32:i386 1.6.2-13 -> 1.6.2-8 solves the problem. Sincerely G. On Mon, 20 O

Bug#764897: kfreebsd-kernel-headers: net/route.h fails to compile in userland, squid3 FTBFS

Hi! On 20/10/14 19:41, Christoph Egger wrote: > "Adam D. Barratt" writes: >> On Fri, 2014-10-17 at 13:16 +0100, Steven Chamberlain wrote: >>> On 12/10/14 02:00, Steven Chamberlain wrote: kfreebsd-kernel-headers >= 10.1~ adds a sys/counter.h, used in various places including net/route.h.

Bug#750329: nsscache: FTBFS: Tests failures

Package: nsscache Version: 0.27-2 Followup-For: Bug #750329 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu utopic ubuntu-patch In Ubuntu, the attached patch was applied to achieve the following: * Build-depend on libnss-db to fix tests. Thanks for considering the patch. Logan Ros

Bug#766088: debian-edu-artwork: Unable to upgrade from version 0.49-1 to 0.50-1

Package: debian-edu-artwork Version: 0.50-1 Severity: serious When trying to upgrade my freshly installed Debian Edy Jessie installation to unable, the upgrade fail like this when upgrading debian-edu-artwork from version 0.49-1: Preparing to unpack .../debian-edu-artwork_0.50-1_all.deb ... Leav

Bug#764897: kfreebsd-kernel-headers: net/route.h fails to compile in userland, squid3 FTBFS

"Adam D. Barratt" writes: > On Fri, 2014-10-17 at 13:16 +0100, Steven Chamberlain wrote: >> On 12/10/14 02:00, Steven Chamberlain wrote: >> > kfreebsd-kernel-headers >= 10.1~ adds a sys/counter.h, used in various >> > places including net/route.h. It requires a kernel type uint64_t >> > (from sys

Processed: found 751121 in 2.1.2-2

Processing commands for cont...@bugs.debian.org: > found 751121 2.1.2-2 Bug #751121 [src:netatalk] Please fix "FIXME" statements in copyright file Marked as found in versions netatalk/2.1.2-2. > thanks Stopping processing here. Please contact me if you need assistance. -- 751121: http://bugs.deb

Bug#728452: opal: FTBFS if $HOME does not exist

On 19/10/14 16:37, Balint Reczey wrote: Since May there have ben several stable releases starting with 3.14.0. It would be nice if the package could be updated before the freeze. The package cannot be updated, because it breaks API in major ways with each version (even minor one!), and most im

Processed: Re: Bug#761245: icedove: tagging pending upload

Processing commands for cont...@bugs.debian.org: > tags 761245 + pending Bug #761245 [icedove] icedove: STARTTLS regression: "connection to SMTP server was lost in the middle of the transaction" Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistance. --

Bug#754119: marked as done (libmagic1: arch-specific symlink in /usr/share)

Your message dated Mon, 20 Oct 2014 19:58:47 +0200 with message-id <20141020175847.gb13...@ulrik.uio.no> and subject line Re: libmagic1: arch-specific symlink in /usr/share has caused the Debian Bug report #754119, regarding libmagic1: arch-specific symlink in /usr/share to be marked as done. This

Processed (with 1 errors): Re: Bug#751121: Please fix "FIXME" statements in copyright file

Processing commands for cont...@bugs.debian.org: > tags 751121 -jessie -sid Bug #751121 [src:netatalk] Please fix "FIXME" statements in copyright file Removed tag(s) jessie. Bug #751121 [src:netatalk] Please fix "FIXME" statements in copyright file Removed tag(s) sid. > seen 751121 2.1.2-2 Unknown

Bug#751121: Please fix "FIXME" statements in copyright file

tags 751121 -jessie -sid seen 751121 2.1.2-2 thanks Quoting Luca Falavigna (2014-06-10 16:40:39) > Source: netatalk > Version 2.2.2-1 > Severity: serious > Tags: jessie sid > > > Your debian/copyright file contains lots of FIXMEs. > > For example there is an entry for > distrib/initscripts/rc

Bug#764897: kfreebsd-kernel-headers: net/route.h fails to compile in userland, squid3 FTBFS

On Fri, 2014-10-17 at 13:16 +0100, Steven Chamberlain wrote: > On 12/10/14 02:00, Steven Chamberlain wrote: > > kfreebsd-kernel-headers >= 10.1~ adds a sys/counter.h, used in various > > places including net/route.h. It requires a kernel type uint64_t > > (from sys/kglue/sys/types.h) without which

Bug#765319: missing license in debian/copyright

Hi Roland, On Sat, 18 Oct 2014, Roland Clobus wrote: I learned from https://wiki.debian.org/DFSGLicenses that CC-BY-SA 3.0 can be used. yes, that license would be fine. What do you propose? - Replace the image parts from images that are CC-BY-SA 3.0 and license the derived work as CC-BY-SA 3

Bug#738927: marked as done (mcelog: fails to install when CPU unsupported)

Your message dated Mon, 20 Oct 2014 17:19:28 + with message-id and subject line Bug#738927: fixed in mcelog 104-1 has caused the Debian Bug report #738927, regarding mcelog: fails to install when CPU unsupported to be marked as done. This means that you claim that the problem has been dealt w

Bug#766041: marked as done (missing license in debian/coypright)

Your message dated Mon, 20 Oct 2014 15:39:08 + with message-id and subject line Bug#766041: fixed in pythondialog 3.2.0-2 has caused the Debian Bug report #766041, regarding missing license in debian/coypright to be marked as done. This means that you claim that the problem has been dealt wit

Bug#764885: php-htmlpurifier ready for tests (Security flaws in the current Debian version)

David Prévot, 2014-10-17 21:30:05 -0400 : [...] > The package ready for test and upload is online: [...] > Thanks in advance for your feedback. If I don’t get negative feedback > by Monday, I intend to upload the package as is (it will already be > late: two weeks before the freeze). I would mu

Bug#765814: marked as done (node-dryice incompatible with uglifyjs version 1.x)

Your message dated Mon, 20 Oct 2014 16:04:09 + with message-id and subject line Bug#765814: fixed in node-dryice 0.4.10-2 has caused the Debian Bug report #765814, regarding node-dryice incompatible with uglifyjs version 1.x to be marked as done. This means that you claim that the problem has

Processed: Bug#765789 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 765789 pending Bug #765789 [dpkg] dpkg: cycle found while processing triggers Bug #765434 [dpkg] dpkg: bogus triggers cycle detection Bug #765668 [dpkg] dpkg: bogus triggers cycle detection Bug #765734 [dpkg] dpkg: bogus triggers cycle detecti

Processed: Bug#765434 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 765434 pending Bug #765434 [dpkg] dpkg: bogus triggers cycle detection Bug #765668 [dpkg] dpkg: bogus triggers cycle detection Bug #765734 [dpkg] dpkg: bogus triggers cycle detection Bug #765781 [dpkg] man-db: failed upgrade: trigger loop with

Processed: Bug#765781 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 765781 pending Bug #765781 [dpkg] man-db: failed upgrade: trigger loop with install-info Bug #765434 [dpkg] dpkg: bogus triggers cycle detection Bug #765668 [dpkg] dpkg: bogus triggers cycle detection Bug #765734 [dpkg] dpkg: bogus triggers cy

Bug#765115: marked as done (ruby-yaml-db: FTBFS: build-dependency not installable: ruby-rails-3.2)

Your message dated Mon, 20 Oct 2014 16:05:16 + with message-id and subject line Bug#765115: fixed in ruby-yaml-db 0.2.3-2 has caused the Debian Bug report #765115, regarding ruby-yaml-db: FTBFS: build-dependency not installable: ruby-rails-3.2 to be marked as done. This means that you claim t

Bug#765734: marked as pending

tag 765734 pending thanks Hello, Bug #765734 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=dpkg/dpkg.git;a=commitdiff;h=e121d88 --- commit e121d882c92099d1f1aa9eedd0c0e90806a44efa Aut

Bug#765668: marked as pending

tag 765668 pending thanks Hello, Bug #765668 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=dpkg/dpkg.git;a=commitdiff;h=e121d88 --- commit e121d882c92099d1f1aa9eedd0c0e90806a44efa Aut

Bug#766011: marked as done (racket-common: trying to overwrite '/usr/share/doc/racket/release/stamp.sxref')

Your message dated Mon, 20 Oct 2014 15:40:15 + with message-id and subject line Bug#766011: fixed in racket 6.1-2 has caused the Debian Bug report #766011, regarding racket-common: trying to overwrite '/usr/share/doc/racket/release/stamp.sxref' to be marked as done. This means that you claim

Bug#759226: icedtea-netx.postinst.in

I've attached a modified version of the postist script for icedtea-netx_1.5.1 This new version loops through the list of tools and checks if it exist for each version, adding it to update-alternatives if if does. This script allows the package to be installed on my machine and seems to set the cor

Processed: Bug#765952 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 765952 pending Bug #765952 [dpkg] apt, dpkg: cycle during trigger processing Bug #765434 [dpkg] dpkg: bogus triggers cycle detection Bug #765668 [dpkg] dpkg: bogus triggers cycle detection Bug #765734 [dpkg] dpkg: bogus triggers cycle detectio

Processed: Bug#765668 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 765668 pending Bug #765668 [dpkg] dpkg: bogus triggers cycle detection Bug #765434 [dpkg] dpkg: bogus triggers cycle detection Bug #765734 [dpkg] dpkg: bogus triggers cycle detection Bug #765781 [dpkg] man-db: failed upgrade: trigger loop with

Bug#754678: openocd: FTBFS on kfreebsd-*: configure: error: libusb-1.x is required for the MPSSE mode of FTDI based devices

On Monday 20 October 2014 17:31:48 Paul Fertser wrote: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?msg=22;filename=openocd.log. > > gz;att=1;bug=754678> > > | Altera USB-Blaster II Compatibleyes (auto) > > I see the source of the confusion now. There're two versions of USB > Blaste

Bug#760476: gnutls28 3.3.8-3

On 2014-10-20 Christophe Ségui wrote: > I got this issue and tried 3.3.8-3 of gnutls but bug is still present. Hello, can you perhaps provide the info Nikos was asking for: | Given that the size read 16 is sufficient to the stack var

Bug#762195: libc6: libpthread: hardware-assisted lock elision hazardous on x86

On Thu, 16 Oct 2014, Carlos O'Donell wrote: > I disagree. IMO the most flexible approach is for glibc to stop using cpuid > for RTM detection and rely on the kernel to tell it if RTM is usable. Then > we have a single hardware blacklist in the kernel. We need to talk to > kernel people about this.

Bug#765434: marked as pending

tag 765434 pending thanks Hello, Bug #765434 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=dpkg/dpkg.git;a=commitdiff;h=e121d88 --- commit e121d882c92099d1f1aa9eedd0c0e90806a44efa Aut

Bug#765781: marked as pending

tag 765781 pending thanks Hello, Bug #765781 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=dpkg/dpkg.git;a=commitdiff;h=e121d88 --- commit e121d882c92099d1f1aa9eedd0c0e90806a44efa Aut

Bug#765789: marked as pending

tag 765789 pending thanks Hello, Bug #765789 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=dpkg/dpkg.git;a=commitdiff;h=e121d88 --- commit e121d882c92099d1f1aa9eedd0c0e90806a44efa Aut

Bug#765952: marked as pending

tag 765952 pending thanks Hello, Bug #765952 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=dpkg/dpkg.git;a=commitdiff;h=e121d88 --- commit e121d882c92099d1f1aa9eedd0c0e90806a44efa Aut

Processed: Bug#765734 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 765734 pending Bug #765734 [dpkg] dpkg: bogus triggers cycle detection Bug #765434 [dpkg] dpkg: bogus triggers cycle detection Bug #765668 [dpkg] dpkg: bogus triggers cycle detection Bug #765781 [dpkg] man-db: failed upgrade: trigger loop with

Bug#764885: marked as done (Security flaws in the current Debian version)

Your message dated Mon, 20 Oct 2014 16:35:50 + with message-id and subject line Bug#764885: fixed in php-htmlpurifier 4.6.0-1 has caused the Debian Bug report #764885, regarding Security flaws in the current Debian version to be marked as done. This means that you claim that the problem has b

Bug#766011: marked as pending

tag 766011 pending thanks Hello, Bug #766011 reported by you has been fixed in the Git repository. You can see the changelog below, and you can check the diff of the fix at: http://git.debian.org/?p=collab-maint/racket.git;a=commitdiff;h=a061851 --- commit a0618519b4143a78ab858c3f41c7f9a998

Processed: Bug#766011 marked as pending

Processing commands for cont...@bugs.debian.org: > tag 766011 pending Bug #766011 {Done: David Bremner } [racket-common] racket-common: trying to overwrite '/usr/share/doc/racket/release/stamp.sxref' Added tag(s) pending. > thanks Stopping processing here. Please contact me if you need assistanc

Bug#764327: thinfan: Startup Fails On PostInstall

control: severity -1 normal Hi Stephen, On 10/07/2014 11:41 AM, Stephen Allen wrote: >>From the applicaiton log: > > # journalctl -xn > -- Logs begin at Mon 2014-10-06 22:36:18 EDT, end at Tue 2014-10-07 05:35:40 > EDT. -- > Oct 07 05:35:40 Jessie systemd[1]: Starting simple and lightweight fa

Processed: Re: Bug#764327: thinfan: Startup Fails On PostInstall

Processing control commands: > severity -1 normal Bug #764327 [thinkfan] thinfan: Startup Fails On PostInstall Severity set to 'normal' from 'grave' -- 764327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=764327 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- To U

Bug#766068: robocode: fails to start because of obsolete Java environment detection

Package: robocode Version: 1.6.2+dfsg-4 Severity: serious Robocode fails to start when OpenJDK 7 or a newer version is installed on the system. Since OpenJDK7 is the default Java runtime environment for Jessie and OpenJDK6 is going to be removed, this issue is release critical. The error message

Bug#754678: openocd: FTBFS on kfreebsd-*: configure: error: libusb-1.x is required for the MPSSE mode of FTDI based devices

On Mon, Oct 20, 2014 at 03:43:43PM +0200, Luca Bruno wrote: > On Monday 20 October 2014 17:31:48 Paul Fertser wrote: > I see. So in the end, let's keep: > * libusb autodetection for kfreebsd > * --enable-usb_blaster_libftdi for linux My proposal is to have libusb autodetection and usb_blaster_li

Bug#765789: marked as done (dpkg: cycle found while processing triggers)

Your message dated Mon, 20 Oct 2014 15:34:50 + with message-id and subject line Bug#765952: fixed in dpkg 1.17.19 has caused the Debian Bug report #765952, regarding dpkg: cycle found while processing triggers to be marked as done. This means that you claim that the problem has been dealt wit

Bug#765973: marked as done (hicolor-icon-theme: cycle errors while processing triggers)

Your message dated Mon, 20 Oct 2014 15:34:50 + with message-id and subject line Bug#765789: fixed in dpkg 1.17.19 has caused the Debian Bug report #765789, regarding hicolor-icon-theme: cycle errors while processing triggers to be marked as done. This means that you claim that the problem has

Bug#765734: marked as done (dpkg: bogus triggers cycle detection)

Your message dated Mon, 20 Oct 2014 15:34:50 + with message-id and subject line Bug#765952: fixed in dpkg 1.17.19 has caused the Debian Bug report #765952, regarding dpkg: bogus triggers cycle detection to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#765973: marked as done (hicolor-icon-theme: cycle errors while processing triggers)

Your message dated Mon, 20 Oct 2014 15:34:50 + with message-id and subject line Bug#765952: fixed in dpkg 1.17.19 has caused the Debian Bug report #765952, regarding hicolor-icon-theme: cycle errors while processing triggers to be marked as done. This means that you claim that the problem has

Bug#765668: marked as done (dpkg: bogus triggers cycle detection)

Your message dated Mon, 20 Oct 2014 15:34:50 + with message-id and subject line Bug#765952: fixed in dpkg 1.17.19 has caused the Debian Bug report #765952, regarding dpkg: bogus triggers cycle detection to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#765952: marked as done (apt, dpkg: cycle during trigger processing)

Your message dated Mon, 20 Oct 2014 15:34:50 + with message-id and subject line Bug#765952: fixed in dpkg 1.17.19 has caused the Debian Bug report #765952, regarding apt, dpkg: cycle during trigger processing to be marked as done. This means that you claim that the problem has been dealt with

Bug#765781: marked as done (man-db: failed upgrade: trigger loop with install-info)

Your message dated Mon, 20 Oct 2014 15:34:50 + with message-id and subject line Bug#765952: fixed in dpkg 1.17.19 has caused the Debian Bug report #765952, regarding man-db: failed upgrade: trigger loop with install-info to be marked as done. This means that you claim that the problem has bee

Bug#765434: marked as done (dpkg: bogus triggers cycle detection)

Your message dated Mon, 20 Oct 2014 15:34:50 + with message-id and subject line Bug#765952: fixed in dpkg 1.17.19 has caused the Debian Bug report #765952, regarding dpkg: bogus triggers cycle detection to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#765781: marked as done (man-db: failed upgrade: trigger loop with install-info)

Your message dated Mon, 20 Oct 2014 15:34:50 + with message-id and subject line Bug#765781: fixed in dpkg 1.17.19 has caused the Debian Bug report #765781, regarding man-db: failed upgrade: trigger loop with install-info to be marked as done. This means that you claim that the problem has bee

Bug#765434: marked as done (dpkg: bogus triggers cycle detection)

Your message dated Mon, 20 Oct 2014 15:34:50 + with message-id and subject line Bug#765789: fixed in dpkg 1.17.19 has caused the Debian Bug report #765789, regarding dpkg: bogus triggers cycle detection to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#765789: marked as done (dpkg: cycle found while processing triggers)

Your message dated Mon, 20 Oct 2014 15:34:50 + with message-id and subject line Bug#765789: fixed in dpkg 1.17.19 has caused the Debian Bug report #765789, regarding dpkg: cycle found while processing triggers to be marked as done. This means that you claim that the problem has been dealt wit

Bug#765668: marked as done (dpkg: bogus triggers cycle detection)

Your message dated Mon, 20 Oct 2014 15:34:50 + with message-id and subject line Bug#765789: fixed in dpkg 1.17.19 has caused the Debian Bug report #765789, regarding dpkg: bogus triggers cycle detection to be marked as done. This means that you claim that the problem has been dealt with. If t

Bug#765781: marked as done (man-db: failed upgrade: trigger loop with install-info)

Your message dated Mon, 20 Oct 2014 15:34:50 + with message-id and subject line Bug#765789: fixed in dpkg 1.17.19 has caused the Debian Bug report #765789, regarding man-db: failed upgrade: trigger loop with install-info to be marked as done. This means that you claim that the problem has bee

  1   2   3   >