Control: found 1068134 7.3-1
Control: notfound 1068134 7.3-2
The bug reported here is already fixed in the version for which the bug
was reported.
This bug was present in the previous version. The current version was
uploaded precisely to fix the problem reported.
Previous version (7.3-1) had
Control: found 1068133 5.1-2
Control: notfound 1068133 5.1-3
The bug reported here is already fixed in the version for which the bug
was reported.
This bug was present in the previous version. The current version was
uploaded precisely to fix the problem reported.
Previous version (5.1-2) had
source: lcmaps-plugins-verify-proxy
version: 1.5.10-2
severity: serious
During the 64 bit time_t transition the package name liblcmaps0 was
changed to liblcmaps0t64. The old name is still provided by the new
package for architectures where this transition did not cause an ABI
break, but not for
source: lcmaps-plugins-basic
version: 1.7.1-1
severity: serious
During the 64 bit time_t transition the package name liblcmaps0 was
changed to liblcmaps0t64. The old name is still provided by the new
package for architectures where this transition did not cause an ABI
break, but not for
source: lcmaps-plugins-jobrep
version: 1.5.6-1.1
severity: serious
During the 64 bit time_t transition the package name liblcmaps0 was
changed to liblcmaps0t64. The old name is still provided by the new
package for architectures where this transition did not cause an ABI
break, but not for
source: lcmaps-plugins-voms
version: 1.7.1-1
severity: serious
During the 64 bit time_t transition the package name liblcmaps0 was
changed to liblcmaps0t64. The old name is still provided by the new
package for architectures where this transition did not cause an ABI
break, but not for
arcresume arcsync
arcclean arcls arcrename arcrm arctest
arccp arched arcmkdir arcrenew arcstat
arcctl arcinfoarcplugin arcresub arcsub
Mattias Ellert
signature.asc
Description: This is a digitally signed message part
Hi!
The proposed change is incomplete, and the build failed on some
architectures.
You need to update debian/rules due to the changes package names:
Line 31 must change from
N = -Nlibxrdec1
to
N = -Nlibxrdec1t64
Regards,
Mattias (package maintainer)
signature.asc
Description:
Source: onnx
Version: 1.13.1-1
Severity: serious
Control: affects -1 +src:pytorch
Control: affects -1 +src:pytorch-cuda
Control: affects -1 +src:open3d
Control: affects -1 +src:pytorch-vision
Control: affects -1 +src:baler
Control: affects -1 +src:pytorch-scatter
Control: affects -1
Control: tag 1051258 +fixed-upstream +patch
Applying the change from the upstream commit:
https://github.com/pytorch/pytorch/commit/0c4fa0229625ccc6fcb9ae2867e98ce285e78946
fixes the FTBFS on ppc64el. This was verified using a schroot build on
the platti.debian.org porterbox.
Link to patch:
Package: python3-torch
Version: 1.13.1+dfsg-4
Severity: serious
Importing torch results in failure due to missing symbols:
$ python3
Python 3.11.4 (main, Jun 7 2023, 10:13:09) [GCC 12.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import torch
Traceback
nst gcc-12 package.
Mattias Ellert
signature.asc
Description: This is a digitally signed message part
bullseye-pu: package voms-api-java_3.3.2-1+deb11u1
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028546
signature.asc
Description: This is a digitally signed message part
Here is a possible patch.
With this patch it builds both on testing (googletest 1.11.0) and
unstable (googletest 1.12.1).
The patch need some tweaks to be upstreamable since it used the Debian
path to the googletest source.
Mattias
diff -ur
Source: seqan3
Version: 3.2.0+ds-1
Severity: serious
The package fails to build in unstable due to a failing test.
The failure is due to a change in googletest 1.12
7451/8534 Test #7451: test/pretty_printing_test::pretty_printing.std_output
Control: forwarded 1012467 https://github.com/cern-fts/davix/issues/97
Control: tag 1012467 +fixed-upstream
The issue was addressed upstream in this commit:
https://github.com/cern-fts/davix/commit/5d15956648c0984094d6147cd2b67c195c5c335f
Mattias
signature.asc
Description: This is a
Hi.
My currently installed version of libjs-jquery is
$ dpkg-query --show libjs-jquery
libjs-jquery3.5.1+dfsg+~3.5.5-4
which is currently the latest version.
I have a symlink as follows:
$ ls -l /usr/share/javascript/jquery
lrwxrwxrwx 1 root root 29 12 May 2020
reassign 952622 src:procps 2:3.3.16-2
fixed 952622 procps/2:3.3.16-3
retitle 952622 procps does not provide /bin/kill - violates FHS specification
affects 952622 myproxy
stop
Section 3.4 of the Filesystem Hierarchy Standard (FHS) says:
mån 2019-01-07 klockan 09:20 +0100 skrev Lucas Nussbaum:
> Hi,
>
> On 07/01/19 at 08:28 +0100, Mattias Ellert wrote:
> > Hi!
> >
> > The globus-gass-copy package and dependent packaged have now been
> > tagged for autoremoval due to this RC bug. So I need to r
Hi Lucas.
I have a question regarding your report.
Is it really a requirement that the package build should succeed even
if the user account doing the package build is disabled for logins?
Not accepting remote logins during the build is very reasonable. But a
test that starts a server on the
mån 2016-08-22 klockan 10:21 +0200 skrev Santiago Vila:
> On Mon, 22 Aug 2016, Mattias Ellert wrote:
>
> >
> > I can not reproduce the problem locally on my machine.
>
> Please try building on a virtual machine having only 1 CPU.
>
> Apparently the test suit
In the two logs attached the failing tests say
Linear duration: 7089ms, 282.1272393849626ops
Parallel duration: 5528ms, 361.794500723589ops
and
Linear duration: 6150ms, 325.2032520325203ops
Parallel duration: 4639ms, 431.1273981461522ops
respectively. I.e. the ratios are
7089/5528 = 1.282
reassign 830299 src:cglib
affects 830299 src:voms-api-java
forcemerge 830204 830299
thanks
I can not reproduce this failure.
Looking at the difference between my successful build log from pbuilder
and the attached log I see that the version of libcglib-java used
changed from 3.2.3-2 to 3.2.3-3.
tis 2015-11-10 klockan 15:50 +0100 skrev Aurelien Jarno:
>
> Bug submitted upstream as PR68273.
Hi!
How should I handle this? Will there be a solution to the gcc bug
within a not too distant future, or is this likely to remain broken for
many months? Not an easy question to answer I imagine.
the optimization from -O2 to -O1,
the build succeeds. This therefore looks like a regression in
mips/mipsel optimization.
Mattias Ellert
signature.asc
Description: This is a digitally signed message part
Control: block 769266 by 768747
ons 2014-11-12 klockan 11:44 +0100 skrev Lucas Nussbaum:
Hi,
During a rebuild of all packages in jessie (in a jessie chroot, not a
sid chroot), your package failed to build on i386.
As I already explained in the previous bug you reported for the same
issue
Control: reassign -1 openjdk-7/7u71-2.5.3-1
sön 2014-11-09 klockan 08:28 +0100 skrev Lucas Nussbaum:
Source: canl-java
Version: 2.1.1-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141108 qa-ftbfs
Justification: FTBFS in jessie on amd64
Hi,
mån 2014-10-13 klockan 19:27 +0200 skrev David Suárez:
Source: globus-simple-ca
Version: 4.14-1
Severity: serious
Tags: jessie sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20141012 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your
Package: glibc
Version: 2.19-11
Severity: serious
The return value from the select function on Hurd is sometimes too high.
I.e. the value returned is greater than the total number of bits set in
the fd_set variables.
This causes problems for code that expect the value to be accurate, and
causes
ons 2014-07-16 klockan 22:41 +0200 skrev Emilio Pozuelo Monfort:
Source: gfal2
Version: 2.3.0-4
Severity: serious
Doing rebuilds for the libgsoap5 transition, your package failed to build
everywhere except on amd64, i386 and hurd-i386. That seems to be because
in those builds, the version
sön 2014-07-06 klockan 19:14 + skrev bastien ROUCARIES:
Package: gsoap
Version: 2.8.16-3
user: lintian-ma...@debian.org
usertags: source-is-missing
severity: serious
X-Debbugs-CC: ftpmas...@debian.org
Hi,
Your package seems to include some files that lack sources
in prefered forms
ons 2014-06-04 klockan 10:11 +0900 skrev Norbert Preining:
Hi Mattias,
\begin{figure}[H] fails with:
LaTeX Error: Unknown float option `H'
Yes, which is correct, the document is simply wrong. H is not
a proper float option.
This is incorrect. The default float command does bot provide
Package: doxygen
Version: 1.8.7-1
Severity: serious
Generation documentation from the doxygen generated latex source fails
with:
\begin{figure}[H] fails with:
LaTeX Error: Unknown float option `H'
See e.g.:
http://aws-logs.debian.net/ftbfs-logs/2014/06/01/globus-common_14.10-2_unstable.log
Package: texlive
Version: 2014.20140528-3
Severity: serious
\begin{figure}[H] fails with:
LaTeX Error: Unknown float option `H'
This causes build failures for packages that generate documentation
using Doxygen. See e.g.:
Hi!
Is there an estimate from the maintainers when this might be fixed? I
know that there is some ongoing work to update condor to version 8, and
that this issue might get fixed in the process. Will that happen soon?
If such an update is still some time away, are there plans to provide a
minor
tis 2013-12-03 klockan 19:04 +0100 skrev Michael Hanke:
PS. At the moment the condor build also fails due to a broken latex2html
that goes into an endless loop during generation of the documentation
files. (See BTS #723913)
Ah, thanks for the pointer! This is the issue that is currently
block 728179 by 723913
thanks
The condor binnmu due to the gsoap update failed during documentation
generation due to a recent problem with latex2html.
If \captions are removed from all \tables and \figures in the
documentation the build succeeds, but that is clearly not the right
thing to do...
Source: condor
Version: 7.8.8~dfsg.1-2
Severity: serious
With the recent update of Globus Toolkit to version 5.2.5, the debian
packages implements Multi-Arch support. For this reason the install
location for the architecture dependent header files had to be changed.
For packages that depend on
severity 728636 important
thanks
Since no changes are needed to the source package to fix this issue the
severity of this bug is reduced.
The issue should be fixed by binmnus of the broken dependencies.
Mattias
signature.asc
Description: This is a digitally signed message part
Source: globus-core
Version: 8.16-1
Severity: serious
The full Globus Toolkit 5.2.5 should migrate to testing together.
However many of the updated packages got diverted to the new queue due
to package splits/renames done in order to support Multi-Arch.
This bug is filed to prevent the migration
block 728636 by 728179
thanks
sön 2013-11-03 klockan 18:00 +0100 skrev David Suárez:
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
cc -D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4
-Wformat
Isn't it time to close this now?
Mattias
signature.asc
Description: This is a digitally signed message part
Package: src:openldap
Version: 2.4.31-1
Severity: serious
Openldap fails to build on hurd-i386. The build has been tried in buildd
three times and failed.
The compilation itself completes and the build then fails during make
check.
Running ../../../tests/scripts/all for bdb...
Executing all
block 687409 by 684963
thanks
Hi!
The reason why this source package does not build in wheezy is that bug
#632183 (missing maven repo info in the bouncycastle package) is not
fixed in wheezy.
Wheezy has bouncycastle 1.44+dfsg-2 and the bug was fixed in
bouncycastle 1.44+dfsg-3 already in July
notfound 677856 dcap/2.47.6-2
reassign 677856 gcc-4.7
found 677856 gcc-4.7/4.7.0-11
fixed 677856 gcc-4.7/4.7.0-12
forcemerge 672411 677856
thanks
This is not a bug in dcap
This is a bug in gcc
This bug is already fixed
Please update the gcc version in your buildd build environments.
mån 2012-05-14 klockan 14:29 +0200 skrev Mathieu Malaterre:
tags 667575 moreinfo
thanks
Mattias, any comments ? I have been using dccp for a while now. dccp
is already known since squeeze. You only introduced dccp recently.
Would it be possible to rename it to something else ?
I do not
mån 2012-04-16 klockan 10:41 -0700 skrev Quanah Gibson-Mount:
--On Monday, April 16, 2012 10:17 AM -0700 Quanah Gibson-Mount
qua...@zimbra.com wrote:
Hi Mattias,
I've filed a bug with upstream
(http://www.openldap.org/its/index.cgi/?findid=7247) on this issue.
That would be the
Hi!
No other suggestion put forward. I will do a bin NMU in a few days
unless there are other solutions proposed.
Mattias
signature.asc
Description: This is a digitally signed message part
Hi!
Is any of the maintainers of the package looking into fixing this?
The cause of the problem is that a function declared in a header file in
the heimdal package has changed its signature.
The old header said:
krb5_error_code
hdb_generate_key_set_password (
krb5_context /*context*/,
mån 2012-02-13 klockan 15:33 +0100 skrev Christoph Egger:
Package: src:lcgdm
Version: 1.8.2-1
Severity: serious
Tags: sid wheezy
Justification: fails to build from source (but built successfully in the past)
Hi!
I think the source package is good, it is just that the bin-nmu of lcgdm
has to
Sat, 9 Jul 2011 06:52:05 +0200 Thomas Krichel kric...@openlib.org wrote:
| Setting up slapd (2.4.25-1+b1) ...
| Creating initial configuration... mkdir: cannot create directory
`/etc/ldap/slapd.d': File exists
| dpkg: error processing slapd (--configure):
| subprocess installed
forwarded 621719 http://bugzilla.globus.org/globus/show_bug.cgi?id=7159
thanks
fre 2011-04-08 klockan 14:02 +0900 skrev Nobuhiro Iwamatsu:
Source: globus-gssapi-gsi
Version: 7.6-1
Severity: serious
Justification: FTBFS
Hi,
globus-gssapi-gsi FTBFS with the following error,presumably for
tags 618433 patch
thanks
Hi!
I here attach a corrected version of the broken patch that fixes the
issue.
Mattias
diff -ur doxygen-1.7.3.orig/src/dot.cpp doxygen-1.7.3/src/dot.cpp
--- doxygen-1.7.3.orig/src/dot.cpp 2010-12-15 23:09:16.0 +0100
+++ doxygen-1.7.3/src/dot.cpp
If I recompile the doxygen package, but without applying the
doxygen_direct_dot_run.diff patch from the source package the problem
goes away. So this bug is an unwanted side effect of that patch.
Mattias
signature.asc
Description: This is a digitally signed message part
Package: doxygen
Version: 1.7.3-1
Severity: serious
Version 1.7.3-1 of doxygen leaves the .dot files behind.
Running doxygen a second time removes them, but it seems to be stupid
that I would have to change all instances of
doxygen Doxyfile
to
doxygen Doxyfile
doxygen Doxyfile
in the
tis 2011-03-15 klockan 05:24 +0100 skrev Matthias Klose:
Afaik not succeeding to build a package twice in a row doesn't rectify a RC
report. Please correct me if I'm wrong.
I do not understand what you are trying to say with the above sentence.
Please elaborate.
Mattias
tis 2011-03-15 klockan 05:24 +0100 skrev Matthias Klose:
It seems to be stupid to rely on a tool not completely cleaning things.
From the above statement I get the impression that you have
misunderstood the issue reported. This is not make clean that is
broken so that building a second time
tis 2010-07-20 klockan 13:49 +0200 skrev Helmut Grohne:
Hi Mattias,
On Tue, Jul 20, 2010 at 01:14:11PM +0200, Mattias Ellert wrote:
The developers considers this to be an error rather than a warning. Do
you not consider this to be a valid error message? Would you rather see
it fail
sön 2010-07-18 klockan 18:43 +0200 skrev Helmut Grohne:
Package: fetch-crl
Version: 2.8.5-1
Are you sure about the version. I know this bug was present in the
2.8.4-1 package, but as far as I know it is fixed in 2.8.5-1.
This is the post install script in 2.8.5-1. Note the period at the end
of
sön 2010-07-18 klockan 18:46 +0200 skrev Helmut Grohne:
Package: fetch-crl
Version: 2.8.5-1
Severity: grave
Justification: renders package unusable
# cat /etc/cron.d/fetch-crl
# Cron job running by default every 6 hours.
# The lock file can be enabled or disabled via a
# service
tis 2010-07-20 klockan 13:52 +0200 skrev Helmut Grohne:
Hi Mattias,
Offending line is this one:
update-rc.d fetch-crl-boot start 20 . stop 20 0 1 2 3 4 5 6 . /dev/null
Notice that *no* runlevels are given for start. It looks like
update-rc.d cannot handle this situation.
Would this
Package: graphviz
Version: 2.26.3-4
Severity: serious
User: debian-h...@lists.debian.org
Usertags: hurd
Packages that use doxygen to generate documentation FTBFS on hurd-i386
due to the dot binary bailing out due to a pthread asertion:
dot:
tor 2010-04-08 klockan 15:43 +0200 skrev Petr Salinger:
Hi,
I am unable to reproduce neither voms neither brltty FBTBF
with gcj 4.4.3-6 and up-to-date sid.
Petr
After receiving your message, I asked for a give-back of the two
packages. This resulted in brltty building fine, but voms
Package: gcj-4.4-jdk
Version: 4.4.3-5
Severity: serious
/usr/lib/jvm/default-java/bin/javadoc exits due to a bus error causing
FTBFS failures on freebsd-amd64.
The default javadoc on freebsd-amd64 is /usr/bin/gjdoc-4.4.
Here are two examples of FTBFS javadoc generation on freebsd-amd64:
severity 571353 important
thanks
This package only FTBFS using the version of
libglobus-gridftp-server-control-dev in unstable (0.40) because that
package has a dependency on a package in the NEW queue.
This package builds fine with the version of
libglobus-gridftp-server-control-dev in testing
This bug has been fixed in upstream's svn tag Release_1_6_2_20100208:
http://doxygen.svn.sourceforge.net/svnroot/doxygen/tags/Release_1_6_2_20100208
Can we please have an update based on this tag in unstable so that it
will be possible to submit updates to packages that use doxygen during
the
Package: doxygen
Version: 1.6.2-1
Severity: serious
block 564408 by -1
block 564409 by -1
block 564370 by -1
thanks
There is a bug in doxygen version 1.6.2 where
#if !defined(X)
is not equivalent to
#ifndef X
I managed to build one of my FTBFS packages with doxygen 1.6.2 if I
changed all the
Package: doxygen
Version: 1.6.0-1
Found: 1.6.1-1
Severity: serious
Forwarded: http://bugzilla.gnome.org/show_bug.cgi?id=593759
See the upstream bug report:
http://bugzilla.gnome.org/show_bug.cgi?id=593759
signature.asc
Description: Detta är en digitalt signerad meddelandedel
Your changelog says ... for hppa and mipsel, however it was hppa and
mips that had FTBFS, not hppa and mipsel.
The new package does build on hppa, but it still fails on mips with the
same error.
signature.asc
Description: Detta är en digitalt signerad meddelandedel
Package: ghostscript
Version: 8.64~dfsg-6
Severity: serious
There is an internal version mismatch in ghostscript 8.64~dfsg-6. The
gs_init.ps file in the package claims that it requires version 8.65, but
the ghostscript interpreter in the package says it is 8.64.
When used the error gs:
70 matches
Mail list logo
