-1.8 has:
Warning: -L../../snmplib/.libs changed to
-L/build/net-snmp-5.7.3+dfsg/perl/default_store/../../snmplib/.libs
Warning: -L../../snmplib/ changed to
-L/build/net-snmp-5.7.3+dfsg/perl/default_store/../../snmplib/
Writing MYMETA.yml and MYMETA.json
But -2 has:
Warning: -L../../snmplib/.libs
Source: ros-rosinstall
Version: 0.7.7-6
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/ros-rosinstall.html
...
==
ERROR: test_info_only (test.local.test_rosws.RosWsTest)
Your message dated Tue, 03 Apr 2018 10:49:51 +
with message-id
and subject line Bug#881375: fixed in sen 0.6.0-0.1
has caused the Debian Bug report #881375,
regarding sen FTBFS with python-docker 2.5.1-1
to be marked as done.
This means that you claim
Processing control commands:
> tags 881375 + patch
Bug #881375 [src:sen] sen FTBFS with python-docker 2.5.1-1
Added tag(s) patch.
> tags 881375 + pending
Bug #881375 [src:sen] sen FTBFS with python-docker 2.5.1-1
Added tag(s) pending.
--
881375:
Control: tags 881375 + patch
Control: tags 881375 + pending
Dear maintainer,
I've prepared an NMU for sen (versioned as 0.6.0-0.1) and
uploaded it.
Regards.
diff -Nru sen-0.5.1/debian/changelog sen-0.6.0/debian/changelog
--- sen-0.5.1/debian/changelog 2017-11-18 04:11:21.0 +0100
+++
Processing control commands:
> retitle -1 FTBFS: Failed to register: The connection is closed;
> gio/tests/gapplication.c:572:test_quit: assertion failed: (activated)
Bug #894677 [src:glib2.0] glib2.0: gio/tests/gapplication.c:572:test_quit:
assertion failed: (activated)
Changed Bug title to
Control: retitle -1 FTBFS: Failed to register: The connection is closed;
gio/tests/gapplication.c:572:test_quit: assertion failed: (activated)
Control: forwarded -1 https://bugzilla.gnome.org/show_bug.cgi?id=768996
Control: found -1 2.49.3-1
On Tue, 03 Apr 2018 at 11:00:23 +0100, Simon McVittie
The odd thing about this is nothing changed in that part of the packaging
at all.
- Craig
On Tue, 3 Apr 2018 at 18:21 Niko Tyni wrote:
> Control: reassign -1 libsnmp-perl 5.7.3+dfsg-2
> Control: retitle -1 libsnmp-perl: undefined symbol:
> netsnmp_ds_toggle_boolean
>
Processing control commands:
> retitle -1 glib2.0: gio/tests/gapplication.c:572:test_quit: assertion failed:
> (activated)
Bug #894677 [src:glib2.0] glib2.0: FTBFS on i386: test error occurred
Changed Bug title to 'glib2.0: gio/tests/gapplication.c:572:test_quit:
assertion failed: (activated)'
Control: retitle -1 glib2.0: gio/tests/gapplication.c:572:test_quit: assertion
failed: (activated)
On Tue, 03 Apr 2018 at 15:31:34 +0800, Boyuan Yang wrote:
> Justification: fails to build from source on release architecture (but
> built successfully in the past)
This looks like a transient
Hi Andreas,
I finally managed to find a Debian Developer !
He signed my gpg key yesterday so now I think I can request the
permissions to log in the sparc64 portexbox and process that bug.
The gpg key is the one used to sign this email. Please tell me if that's
ok now.
Cheers,
Le 09/01/2018
Processing commands for cont...@bugs.debian.org:
> affects 894371 src:gdcm
Bug #894371 [src:openjdk-9] gdcm FTBFS with openjdk-9
Added indication that 894371 affects src:gdcm
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
894371:
Your message dated Tue, 03 Apr 2018 09:15:07 +
with message-id
and subject line Bug#893975: fixed in xorgproto 2018.4-4
has caused the Debian Bug report #893975,
regarding x11proto-dev: trying to overwrite
'/usr/include/X11/extensions/xf86misc.h'
to be
On 04/03/2018 08:19 AM, Adrian Bunk wrote:
> Source: gf-complete
> Version: 1.0.2+2017.04.10.git.ea75cdf-1
> Severity: serious
>
> https://buildd.debian.org/status/package.php?p=gf-complete=sid
>
> A note regarding
> * drop not use sse patch, gf-complete supports runtime simd detection now.
>
Source: weechat
Version: 2.1-1
Severity: serious
Hi,
In 1.9.1-1, you disabled the javascript plugin as libv8 is not in testing.
In 2.1-1, you (silently) enabled it again. Since libv8 is not in testing and
is not going to migrate unless someone fixes the security problems it has,
this is
Processing commands for cont...@bugs.debian.org:
> affects 882308 http-parser src:http-parser
Bug #882308 [ruby-http-parser.rb] http-parser 2.7 breaks ruby-em-http-request's
tests
Added indication that 882308 affects http-parser and src:http-parser
> thanks
Stopping processing here.
Please
wf...@niif.hu (Ferenc Wágner) writes:
> Nobody objected, so let's hold out until libcurl breaks us for good or
> OpenSSL 1.1 support emerges...
According to the latest comment on
https://issues.shibboleth.net/jira/browse/CPPXT-110
upstream support is getting there.
Scott, have you perhaps got a
Processing control commands:
> reassign -1 src:openjdk-9
Bug #894371 [src:gdcm] gdcm FTBFS with openjdk-9
Bug reassigned from package 'src:gdcm' to 'src:openjdk-9'.
No longer marked as found in versions gdcm/2.8.4-1.
Ignoring request to alter fixed versions of bug #894371 to the same values
Control: reassign -1 src:openjdk-9
Control: affects -1 gdcm
Control: tags -1 upstream
The error message states:
An exception has occurred in the compiler (9.0.4). Please file a bug
against the Java compiler ...
Hence, I reported the bug upstream and will update this report here
when I
Control: reassign -1 ruby-http-parser.rb
Hi,
it seems ruby-em-http-request uses a fork of http_parser.rb that has not
been updated for a while. However, upstream seems to have fixed some
issues with more recents http-parser developments:
Source: glib2.0
Version: 2.56.0-5
Severity: serious
Justification: fails to build from source on release architecture (but
built successfully in the past)
According to https://buildd.debian.org/status/package.php?p=glib2.0 ,
glib2.0 FTBFS on i386.
>From
Processing control commands:
> reassign -1 ruby-http-parser.rb
Bug #882308 [src:http-parser] http-parser 2.7 breaks ruby-em-http-request's
tests
Bug reassigned from package 'src:http-parser' to 'ruby-http-parser.rb'.
No longer marked as found in versions http-parser/2.7.1-2.
Ignoring request to
Source: libsmali-java
Version: 2.2.2-1
Severity: serious
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libsmali-java.html
...
Processing with ANTLR 3
/build/1st/libsmali-java-2.2.2/util/src/main/java/org/jf/util/jcommander/HelpFormatter.java:34:
error: package
Package: gdebi
Version: 0.9.5.7+nmu1
Severity: grave
Package structure interface appears and it's usable; if user tries
button [Install Package], gksu asks for authorisation and nothing more:
package is not installed and gdebi-gtk disappears.
$ gdebi-gtk AnyPackage.deb
/home/user/.gtkrc-2.0:38:
On Sun, 25 Mar 2018 17:24:57 -0400 Jeremy Bicha wrote:
> I am now raising the severity of this bug.
I've pinged upstream about creating a new release.
--
bye,
pabs
https://wiki.debian.org/PaulWise
signature.asc
Description: This is a digitally signed message part
Source: gf-complete
Version: 1.0.2+2017.04.10.git.ea75cdf-1
Severity: serious
https://buildd.debian.org/status/package.php?p=gf-complete=sid
A note regarding
* drop not use sse patch, gf-complete supports runtime simd detection now.
You cannot pass -mfpu or -msse functions to gcc when
Your message dated Tue, 03 Apr 2018 06:04:36 +
with message-id
and subject line Bug#894648: fixed in botan 2.4.0-5
has caused the Debian Bug report #894648,
regarding CVE-2018-9127
to be marked as done.
This means that you claim that the problem has been
101 - 127 of 127 matches
Mail list logo