Your message dated Sat, 24 May 2014 07:03:42 +
with message-id e1wo5za-0005td...@franck.debian.org
and subject line Bug#748953: fixed in blktap-dkms 2.0.93-0.3
has caused the Debian Bug report #748953,
regarding blktap-dkms: Struct bio was changed in 3.14 breaking build
to be marked as done.
Package: git-buildpackage
Version: 0.6.14
Severity: grave
When building with 0.6.14, I get:
# git-buildpackage
Traceback (most recent call last):
File /usr/bin/git-buildpackage, line 5, in module
sys.exit(main(sys.argv))
File /usr/lib/python2.7/dist-packages/gbp/scripts/buildpackage.py,
Processing control commands:
severity #747105 normal
Bug #747105 {Done: Michael Biebl em...@michaelbiebl.de} [policykit-1]
policykit-1: depends on systemd
Bug #747397 {Done: Michael Biebl em...@michaelbiebl.de} [policykit-1]
policykit-1 forces using systemd and may break systems with sysvinit
Package: policykit-1
Version: 0.105-5
Followup-For: Bug #747105
Control: severity #747105 normal
Control: reopen #747105
Hi,
I want to add a little bit on this bug here.
IMHO the bug is valid in the sense that policykit unnecessarily pulls
in systemd. Chosing systemd-shim, as described in bug
Package: libnfs1
Version: 1.9.3-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
I have two machines a client and a server. The server has a couple of NFS
shares. Working perfectly with libnfs1 1.3 and xbmc 12.3 in the client machine.
Package: libgcal
Version: 0.9.6-3.1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
-- Could NOT find PkgConfig (missing: PKG_CONFIG_EXECUTABLE)
-- checking for
Hi folks,
I wanted to note that I tried out the latest upstream version 1.4.3 from
the website on Debian jessie (amd64), and I got a SIGSERV error as well
(see attachment).
This got away after removing or replacing both of the following icons in
the menu folder:
/Data/Menu/icon_folder.png
Package: courier-mta-ssl
Version: 0.73.1-1.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.
Processing commands for cont...@bugs.debian.org:
tags 749058 + sid jessie
Bug #749058 [liboping] liboping: Regression: new version (1.6.2-5) FTBFS
Added tag(s) sid and jessie.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
749058:
Processing commands for cont...@bugs.debian.org:
found 734865 2.4.9-1
Bug #734865 [apache2,libapache2-mpm-itk] libapache2-mpm-itk: fails to install:
subprocess installed post-installation script returned error exit status 1
Bug #741253 [apache2,libapache2-mpm-itk] E: Sub-process /usr/bin/dpkg
On 2014-05-23 22:37, Matthias Schmitz wrote:
any progress here? I'am afraid pisa and therewith trac-wikiprint is
gone today...
I looked into this, but forgot to reply: There has been some
upstream changes, that should be reflected in the package.
Mainly the name pisa is not used anymore, it
severity 749087 important
thanks
On Fri, May 23, 2014 at 06:06:16PM -0400, Guo Yixuan wrote:
Package: libc6
Version: 2.18-7
Severity: serious
Tags: upstream patch
Justification: causes ftbfs for src:kyotocabinet on sparc
Even if it prevents another package to build, it is not a
Processing commands for cont...@bugs.debian.org:
severity 749087 important
Bug #749087 [libc6] libc6: Patch for pthread_spin_lock on sparc32/sparc64
Severity set to 'important' from 'serious'
thanks
Stopping processing here.
Please contact me if you need assistance.
--
749087:
Package: docker.io
Version: 0.11.1~dfsg1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
When I try to run any container (eg. docker.io run busybox echo 'Hello world')
I get the message
... Error: Cannot start container ... mkdir /sys/fs/devices: operation not
Package: src:ucl
Severity: grave
Justification: renders package unusable
Hello!
ucl currently fails to build from source on all architectures except
i386 and kfreebsd-i386 due to missing symbols in the symbols file
for the libary shipped.
Please update the symbols file according to the diffs
On 05/24/2014 03:57 PM, Sergio Villar wrote:
12:07:21 T:140323922204416 DEBUG: NFS: Context for 192.168.1.10/export/media
not open - get a new context.
12:07:21 T:140323922204416 DEBUG: NFS: Connected to server 192.168.1.10 and
export /export/media
12:07:21 T:140323922204416 DEBUG: NFS:
Your message dated Sat, 24 May 2014 17:37:03 +0200
with message-id 20140524153702.GD30724@greenwood
and subject line Closing
has caused the Debian Bug report #709406,
regarding libsigrokdecode0: Missing depends on python3
to be marked as done.
This means that you claim that the problem has been
Package: libaws
Version: 2.10.2-4
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
- Attempting to parse the build-deps
- Considering build-dep debhelper (= 8.1.3)
tags 749143 + moreinfo unreproducible
severity 749143 normal
thanks
On Sat, May 24, 2014 at 05:13:39PM +0300, Famelis George wrote:
Dear Maintainer,
When I try to run any container (eg. docker.io run busybox echo 'Hello world')
I get the message
... Error: Cannot start container ... mkdir
Source: libmpich2-3
Severity: serious
Tags: jessie sid
libmpich2-3 is replaced by libmpich12, built from the mpich source
package. It shouldn't be released in jessie.
Cheers,
Julien
signature.asc
Description: Digital signature
Processing commands for cont...@bugs.debian.org:
tags 749143 + moreinfo unreproducible
Bug #749143 [docker.io] docker.io: Cannot start container ... mkdir
/sys/fs/devices: operation not permitted
Added tag(s) unreproducible and moreinfo.
severity 749143 normal
Bug #749143 [docker.io]
Processing control commands:
reassign -1 src:mpich2
Bug #749162 [src:libmpich2-3] libmpich2-3: don't release with jessie
Warning: Unknown package 'src:libmpich2-3'
Bug reassigned from package 'src:libmpich2-3' to 'src:mpich2'.
Ignoring request to alter found versions of bug #749162 to the same
Control: reassign -1 src:mpich2
On Sb, 24 mai 14, 18:03:02, Julien Cristau wrote:
Source: libmpich2-3
I'm guessing you meant source of ..., see #352104, #721793.
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
Package: libgksu
Version: 2.0.13~pre1-7
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
make[1]: Entering directory
Processing commands for cont...@bugs.debian.org:
close 659861
Bug #659861 [cvs] cvs contains /usr/share/info/dir.gz
Bug #664872 [cvs] cvs: Excess dir.gz file in /usr/share/info
Marked Bug as done
Marked Bug as done
thanks
Stopping processing here.
Please contact me if you need assistance.
--
Your message dated Sat, 24 May 2014 17:19:29 +
with message-id e1wofbv-8a...@franck.debian.org
and subject line Bug#749104: fixed in git-buildpackage 0.6.15
has caused the Debian Bug report #749104,
regarding git-buildpackage 0.6.14 crashes
to be marked as done.
This means that you claim
On Sat, May 24, 2014 at 19:58:43 +0300, Andrei POPESCU wrote:
Control: reassign -1 src:mpich2
On Sb, 24 mai 14, 18:03:02, Julien Cristau wrote:
Source: libmpich2-3
I'm guessing you meant source of ..., see #352104, #721793.
Sigh, no, I meant Package: libmpich2-3, no idea how this
Control: severity -1 important
On 05/24/2014 03:57 PM, Sergio Villar wrote:
Package: libnfs1
Version: 1.9.3-1
Severity: grave
Justification: renders package unusable
And I'm going to lower down the severity to important because there is
no definite conclusion yet that libnfs is core culprit
Processing control commands:
severity -1 important
Bug #749123 [libnfs1] libnfs1: Unable to mount NFS shares with xbmc 13 and
libnfs1 1.9.3
Severity set to 'important' from 'grave'
--
749123: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749123
Debian Bug Tracking System
Contact
Control: tag -1 + patch
Hi,
I made patch for this bug, without reverting the b2549fac commit.
This patch moves the code that generates build_dir into a function, that takes
all that is needed into account. I also removed the local variable export_dir,
and changed all its uses to build_dir.
Processing control commands:
tag -1 + patch
Bug #749104 {Done: Guido Günther a...@sigxcpu.org} [git-buildpackage]
git-buildpackage 0.6.14 crashes
Added tag(s) patch.
--
749104: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=749104
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Hi,
I forgot to attach the patch. :)
--
UNIX is basically a simple operating system, but you have to be a genius to
understand the simplicity.
-- Dennis Ritchie
Saludos /\/\ /\ `/
commit 79a0436d8c80d90f3844e4267b7f6187de3bd445
Author: Maximiliano Curia m...@gnuservers.com.ar
Date: Sat May
Your message dated Sat, 24 May 2014 21:19:52 +
with message-id e1wojm8-0004ts...@franck.debian.org
and subject line Bug#748920: fixed in jssc 2.6.0-3
has caused the Debian Bug report #748920,
regarding libjSSC-java: Undefined symbol: _Znwm
to be marked as done.
This means that you claim that
Processing commands for cont...@bugs.debian.org:
# the next upstream breaks the API so it will keep making depending packages
FTBFS anyway, and the API is explicitly declared as unstable anyway
severity 746122 important
Bug #746122 [libdpkg-dev] libdpkg-dev: Has stopped providing MD5
Package: ldap-git-backup
Version: 1.0.6-2
Severity: serious
Usertags: goto-cc
During a rebuild of all packages in a clean sid chroot (and cowbuilder+pbuilder)
the build failed with the following error.
[...]
make check-local
make[2]: Entering directory
Your message dated Sun, 25 May 2014 01:18:57 +
with message-id e1won5v-0007cf...@franck.debian.org
and subject line Bug#738934: fixed in isc-dhcp 4.3.0+dfsg-1
has caused the Debian Bug report #738934,
regarding isc-dhcp-client: missing Depends on freebsd-net-tools
to be marked as done.
This
Package: src:mojarra
Version: 2.0.3-3
Severity: serious
Justification: fails to build from source (but built successfully in the past)
This package FTBFS in a clean sid chroot with this error:
The following packages have unmet dependencies:
libtomcat7-java : Conflicts: libtomcat6-java but
Processing commands for cont...@bugs.debian.org:
severity 748742 serious
Bug #748742 [libgnutls28] liferea: Crashes some seconds after launch even
without user interaction (segfault in libpthread)
Severity set to 'serious' from 'important'
thanks
Stopping processing here.
Please contact me if
38 matches
Mail list logo
