Package: src:apache-mime4j
Version: 0.7.2-4
Severity: important
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:
[...]
debian/rules build-indep
dh build-indep
Package: src:projectreactor
Version: 2.0.8-1
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:
[...]
debian/rules build-indep
dh build-indep
Package: src:kryo-serializers
Version: 0.22-3
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:
[...]
debian/rules build-indep
dh build-indep
Package: src:openjpa
Version: 2.4.0-3
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
but it failed:
[...]
debian/rules build-indep
dh build-indep --parallel
On Fri, Jan 13, 2017 at 10:12:06AM +0100, Emmanuel Bourg wrote:
> Le 13/01/2017 à 09:55, Santiago Vila a écrit :
>
> > My autobuilders do not work that way (with arbitrary build-dependencies).
> >
> > Please tell me if those versions are in testing, in unstable, or
&g
On Fri, Jan 13, 2017 at 09:52:36AM +0100, Emmanuel Bourg wrote:
> Could you please try again with the latest version of gradle (3.2.1-1
> instead of 3.1-2) and gradle-debian-helper (1.5.1 instead of 1.4.4) ?
My autobuilders do not work that way (with arbitrary build-dependencies).
Please tell
On Tue, Jan 10, 2017 at 10:02:12AM +0100, Emmanuel Bourg wrote:
> I'm unable to reproduce this issue. The pom file
> build/debian/easybind.pom should be generated automatically, this
> feature was added to gradle-debian-helper 1.4.
>
> Santiago could you post the full build log please?
Sure.
I said:
> I have at least one *successful* build
> containing an error like that (see attach)
Well, I forgot the attach.
I'll report that in a separate bug.
Thanks.
__
This is the maintainer address of Debian's Java team
On Fri, Jan 06, 2017 at 12:22:36PM +0100, Emmanuel Bourg wrote:
> Le 5/01/2017 à 11:05, Santiago Vila a écrit :
> > Running org.apache.directory.mavibot.btree.MultiThreadedBtreeTest
> > Time to create 1M entries : 4 seconds
> > Written 0 elements
> > Written 10
Package: src:mavibot
Version: 1.0.0~M1-2
Severity: important
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
Package: src:java-gnome
Version: 4.1.3-4
Severity: important
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
severity 846116 important
severity 680038 important
severity 828929 important
severity 834686 important
severity 834962 important
severity 842836 important
severity 844083 important
severity 844088 important
severity 844571 important
severity 845164 important
severity 846021 important
severity
Package: src:jackson-module-afterburner
Version: 2.7.1-1
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
Package: src:easybind
Version: 1.0.3-1
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
On Fri, Dec 30, 2016 at 01:46:57AM +, Miguel Landaeta wrote:
> Can you provide the full log of the failed build attempt?
>
> I can't reproduce this issue, although I don't use sbuild to build my
> packages but cowbuilder.
>
> Since I couldn't reproduce the issue with my builder tool of
Package: src:conversant-disruptor
Version: 1.2.8-1
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
Package: src:openhft-lang
Version: 6.7.6-1
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
Package: src:freeplane
Version: 1.5.16-1
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
Package: src:jayway-jsonpath
Version: 2.0.0-2
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
retitle 840827 lucene-solr: Network tests are performed using public IP instead
of 127.0.0.1
severity 840827 normal
thanks
On Mon, Oct 24, 2016 at 05:08:39PM +0200, Emmanuel Bourg wrote:
> I got a look at this issue and it seems the failing tests are setting up
> a local RMI server but the
On Wed, Oct 19, 2016 at 10:50:33PM +0200, Emmanuel Bourg wrote:
> Le 19/10/2016 à 22:31, Santiago Vila a écrit :
>
> > I have already reported a bug like this in other packages.
> > See Bug #841197 for a likely fix.
>
> ...and you'll get the same issue with all reverse
Package: src:junit4
Version: 4.12-4
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
Package: src:activemq-protobuf
Version: 1.1-4
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
Package: src:openjpa
Version: 2.4.0-3
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
Package: src:libhibernate3-java
Version: 3.6.10.Final-5
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
I forgot to tell that I can reproduce this only on some machines but
not in others. The machines on which it fails (there are more than one)
seem to be the ones having some corporate firewall rules I can't
disable. This is probably not just a coincidence.
However, since packages are not supposed
Package: src:lucene-solr
Version: 3.6.2+dfsg-8
Severity: serious
Dear maintainer:
I tried to build this package in stretch with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
On Fri, 26 Aug 2016, Markus Koschany wrote:
> Control: severity -1 normal
Markus, this package fails to build from source:
* In my 5 autobuilders.
* In one of the three tests made by Gregor.
* In several autobuilders from the reproducible builds effort:
On Thu, 8 Sep 2016, gregor herrmann wrote:
> Logs attached. Unfortunately I don't have any idea on how to fix the
> problem, but if you want me to do something else just shout.
Well, if you don't mind burning a bunch of additional CPU cycles,
I would continue to build it several times until it
On Wed, 7 Sep 2016, Markus Koschany wrote:
> I am attaching two build logs (cowbuilder and sbuild) that show no
> issues at all. The build succeeds.
Thanks a lot for trying to reproduce this.
There are still a lot of differences, we should better remove them all,
until our building environments
On Wed, Sep 07, 2016 at 02:05:45PM +0200, Markus Koschany wrote:
> I have just filed
>
> http://bugs.debian.org/836940
>
> against cowbuilder and sbuild and asked both maintainers for a
> clarification. Apparently apt moved the dependency on gnupg from Depends
> to Recommends in version 1.3~exp1
On Wed, 7 Sep 2016, Emmanuel Bourg wrote:
> I haven't been able to reproduce this issue either with a clean pbuilder
> environment. For some reason gnupg was installed by default in the
> environment, but maybe this changed recently?
I don't know if this changed recently with pbuilder, but
On Wed, Sep 07, 2016 at 04:47:15AM +0200, Markus Koschany wrote:
> I disagree with your bug severity. The build does not fail in a clean
> cowbuilder environment. I'm attaching my build log as proof.
The build log is just a proof that the build succeeded, but *not* a proof
that the environment
On Wed, Sep 07, 2016 at 04:47:15AM +0200, Markus Koschany wrote:
> You should rather work towards defining a common build environment
> standard in Debian [...]
You must be joking. There is already a "common build environment standard",
and it's called the set of build essential packages, of
severity 834744 serious
tags 834744 - unreproducible
thanks
Sorry, but missing build-dependencies are RC, and they have always been.
On Mon, 22 Aug 2016, Markus Koschany wrote:
> This package builds fine in a clean cowbuilder chroot environment
No, it does not. If the chroot environment
On Mon, 25 Jan 2016, Michael Tautschnig wrote:
> java.text.ParseException: Unparseable date: "Wed Oct 4 15:42:47 2006"
This happened to me today while checking for "dpkg-buildpackage -A" bugs.
I attach my build log.
> The full build log is attached; please do let me know if the problem is
>
On Tue, Aug 23, 2016 at 10:27:07AM +, Debian Bug Tracking System wrote:
> Files:
> 70c1a6ff3530b04e6ad62d33ff99592a 1969 java optional cup_0.11a+20060608-8.dsc
> a17d8727b785eed718e448c9dca0b13c 6148 java optional
> cup_0.11a+20060608-8.debian.tar.xz
> 6be68ae5d67dfc667d3582757e6a3612
Package: airlift-slice
Version: 0.10-1
Severity: serious
Dear maintainer: This package FTBFS in testing.
-
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X
Package: src:libslf4j-java
Version: 1.7.21-1
Severity: serious
Dear maintainer:
I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
Package: src:commons-math
Version: 2.2-5
Severity: serious
Dear maintainer:
I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
Package: javassist
Version: 3.20.0-1
Severity: serious
Dear maintainer:
I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed several times.
A diff between a successful build and a failed build shows this:
Package: src:xmlgraphics-commons
Version: 2.1-1
Severity: serious
Tags: patch
Dear maintainer:
I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
Package: src:mina2
Version: 2.0.13-1
Severity: serious
Dear maintainer:
I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
Package: src:surefire
Version: 2.17-2
Severity: serious
Dear maintainer:
I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
Package: src:tomcat7
Version: 7.0.70-2
Severity: serious
Dear maintainer:
I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
Package: src:libxalan2-java
Version: 2.7.1-9
Severity: serious
Dear maintainer:
I tried to build this package with "dpkg-buildpackage -A"
(which is what the "Arch: all" autobuilder would do to build it)
but it failed:
On Sat, 16 Jul 2016, tony mancill wrote:
> The first two packages I tried, src:pegdown and src:libjbcrypt-java,
> both appear in the "successfully built reproducibly" set here [1], and
> neither has any bugs assigned to it. Maybe I'm looking in the wrong place?
If those packages generate only
On Sat, 16 Jul 2016, tony mancill wrote:
> > https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=binary-indep;users=sanv...@debian.org
>
> Hi Santiago,
>
> Thanks for the list. For 806640, the only bug that appears in this list
> related to mh_install 805228, I will mark it as blocked by 805228,
On Sat, 16 Jul 2016, Markus Koschany wrote:
> On 16.07.2016 18:22, tony mancill wrote:
> [...]
> > I'd like to discuss options with the Java Team. For example, we could
> > change mh_install to ignore '-i' when not passed in conjunction with a
> > maven.ignoreRules file, or change the DH
On Sat, 16 Jul 2016, tony mancill wrote:
> There are 320-odd packages that build-depend on maven-repo-helper,
> although only a subset of them will use the DH sequencer. Still, I
> think the bug belongs there as a problem in the tool chain and not
> against all of the packages that depend on it.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
__
This is the maintainer address of Debian's Java team
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
__
This is the maintainer address of Debian's Java team
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
__
This is the maintainer address of Debian's Java team
On Thu, 14 Jul 2016, Emmanuel Bourg wrote:
> openjfx builds fine with "dpkg-buildpackage"
But there is not a way to tell the official autobuilders that they
do "dpkg-buildpackage" alone. They always do either -A or -B, so no,
it does not build fine as far as the official autobuilders is
On Thu, 14 Jul 2016, Emmanuel Bourg wrote:
> > Or even better: Consider a source package which only builds "Arch: all"
> > binary packages. Suppose your package has a missing build-depends but
> > it builds ok in your computer because you have installed the
> > build-dependency in your chroot.
On Thu, 14 Jul 2016, Emmanuel Bourg wrote:
> Le 14/07/2016 à 14:08, Santiago Vila a écrit :
>
> > Would you apply the same reasoning to a package which fails to
> > build from source in every arch-dependent autobuilder but still builds
> > fine without the -B flag?
>
On Thu, 14 Jul 2016, Emmanuel Bourg wrote:
> Le 14/07/2016 à 12:23, Santiago Vila a écrit :
>
> > So there should not be a problem with this bug being serious and no
> > upload happening immediately, because you have just shown that you are
> > not MIA.
>
> Actu
On Thu, 14 Jul 2016, Emmanuel Bourg wrote:
> Le 13/07/2016 à 22:45, Santiago Vila a écrit :
>
> > I have the ok from the Release Managers to consider this issue
> > as RC for stretch.
> >
> > I'm going to wait a week before raising severities, but since this bu
Greetings.
I have the ok from the Release Managers to consider this issue
as RC for stretch.
I'm going to wait a week before raising severities, but since this bug
is in pending state, I'd appreciate if you could make an upload
before that.
Thanks.
__
This is the maintainer address of Debian's
Package: src:jpathwatch
Version: 0.95-4
Severity: serious
Dear maintainer:
I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed.
But the failure is build-depends related, so it has nothing to do
with the fact that I was doing
Package: src:eclipse
Version: 3.8.1-8
User: sanv...@debian.org
Usertags: binary-indep
Severity: important
Dear maintainer:
I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:
Package: src:libnative-platform-java
Version: 0.10+dfsg-1
User: sanv...@debian.org
Usertags: binary-indep
Severity: important
Dear maintainer:
I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:
Package: src:ecj
Version: 3.10.1-2
User: sanv...@debian.org
Usertags: binary-indep
Severity: important
Dear maintainer:
I tried to build this package with "dpkg-buildpackage -A"
(i.e. only architecture-independent packages), and it failed:
63 matches
Mail list logo
