Hi,
> llvm: libfuzzer
Any movement on this? I was shown a cool demo yesterday by the upstream author
and its a bit of a pain to get going in Debian. This feels a shame as all the
sources are there, we just need to do something like:
$ clang++ -c -g -O2 -std=c++11 Fuzzer/*.cpp -IFuzzer
$ ar
control: owner -1 !
control: tags -1 moreinfo
>I am looking for a sponsor for my package "cdist"
>
>* Package name: cdist
> Version : 4.2.2-1
EALREADYINUNSTABLE.
G.
Source: grap
Version: 1.44-1
Severity: wishlist
Tags: patch
Usertags: hardening-wrapper
The hardening-wrapper package is considered obsolete these days, since
it is possible to achieve the same goal with dpkg-buildflags. See the
attached patch.
-- System Information:
Debian Release:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
package: wnpp
Owner: Paul Sladen
Severity: Wishlist
* Package Name: python-gavovotable
* Version: 0.9.6
* Upstream Author: Markus Demleitner
* URL:
Hi Guiseppe,
Thanks, and well done on the debugging! I will prepare a patch for the
upstream g2clib developers.
Regards
Alastair
On 27/07/2016 20:34, Giuseppe Bilotta wrote:
> Hello Alastair,
>
> I've managed to pinpoint the issue: in 1.6.0, the original Makefile
> defines a -D__64BIT__
Package: src:imagemagick
Version: 8:6.7.7.10-5
Severity: grave
Tags: patch security
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org
An out of bounds memory read in the VerticalFilter() function can be
triggered by a malformed DDS file.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
package: wnpp
Owner: Paul Sladen
Severity: Wishlist
* Package Name: tapsh
* Version: 0.7.1
* Upstream Author: Markus Demleitner
* URL:
notfound 832880 4.2.10
tags 832880 +unreproducible
thanks
On Fri, Jul 29, 2016 at 10:54:17AM +0200, Louis van Belle wrote:
> Package: samba
> Version: 4.2.10
> Severity: normal
4.2.10 is a no non-existant version of Samba in Debian.
> -- System Information:
> Debian Release: 8.4
> APT prefers
Package: ntp
Version: 1:4.2.8p8+dfsg-1
Hi,
it is great to see that Debian enables PPS in NTP as well now.
That meant I could drop some delta that Ubuntu carried - thank you.
We also have added a few bits on documentation and examples that I'd think
would serve a Debian user just as well.
So I
Control: tag -1 confirmed
On Mon, Jul 25, 2016 at 23:28:14 +0200, Kurt Roeckx wrote:
> Package: release.debian.org
> Tags: jessie
> User: release.debian@packages.debian.org
> Usertags: pu
>
> Hi,
>
> I would like to fix #800446 in stable. It was caused by the
> uploader not using the
Control: tag -1 confirmed
On Sat, Jul 23, 2016 at 23:01:16 +0100, Jonathan Wiltshire wrote:
> backintime in Jessie misses an important dependency on python-dbus.
> If you have one of the front ends installed the chances are it is
> pulled in by something else, but that's not a guarantee.
>
>
Control: tag -1 moreinfo
On Sat, Jul 16, 2016 at 11:20:57 +, Gianfranco Costamagna wrote:
> Package: release.debian.org
> Severity: normal
> Tags: jessie
> User: release.debian@packages.debian.org
> Usertags: pu
>
>
> Forwarding the email from security team.
>
> the debdiff is the new
Hi,
in the meantime avr-libc-2.0.0 has been released upstream. I don't know if
this helps with the issues you mentioned but maybe it's worth having a look.
Thanks,
Maxi
signature.asc
Description: This is a digitally signed message part.
Am 29.07.2016 um 14:08 schrieb Marc Haber:
> systemd 231-1 on Banana Pi fails with a bunch of "Failed at step
> SECCOMP spawning systemd-food: Invalid Argument". This at least
> applies to logind and networkd. Here is the output of trying to restart
> systemd-networkd:
>
> [ 113.060755]
Package: nvidia-driver-bin
Version: 355.11-7
Severity: grave
Justification: renders package unusable
(Not sure which nvidia package is the culprit.)
I've upgraded the system with aptitude (mainly nvidia packages
were upgraded), and X no longer works. I've attached the log.
-- Package-specific
Package: irqbalance
Version: 1.1.0-2
Hi,
Somehow the directory autom4te.cache, which is not part of the upstream
tarball, made its way to the orig.tar.xz provided by Debian.
This disturbs the gbp build process, as these files are deleted during
the clean phase and dpkg-source emits "ignoring
Control: forwarded -1 http://marc.info/?l=postfix-users=145686783109440=2
On 2016-07-27 09:36 +0200, Francois Mescam wrote:
> When I do "systemctl restart postfix" in the logs I have :
> Jul 27 09:27:08 eiffel6 postfix/postfix-script[9559]: stopping the Postfix
> mail system
> Jul 27 09:27:08
Package: imagemagick
Version: 8:6.7.7.10-5
Severity: grave
Tags: patch security
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org
The DrawDashPolygon function in MagickCore/draw.c in ImageMagick
before 6.9.4-0 and 7.x before 7.0.1-2 mishandles calculations of
certain vertices integer
Package: imagemagick
Version: 8:6.7.7.10-5
Severity: grave
Tags: patch security
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org
The DrawImage function in MagickCore/draw.c in ImageMagick before
6.9.4-0 and 7.x before 7.0.1-2 makes an incorrect function call in
attempting to locate the
Package: imagemagick
Version: 8:6.7.7.10-5
Severity: grave
Tags: patch security
X-Debbugs-CC: secure-testing-t...@lists.alioth.debian.org
control: fixed -1 8:6.7.7.10-5+deb7u7
The TraceStrokePolygon function in MagickCore/draw.c in ImageMagick
before 6.9.4-0 and 7.x before 7.0.1-2 mishandles the
Hello Wei,
we tried with kernel 4.6 now, the crashed happened again, though.
next we want to try the Xen debug build, but we couldn't find any
information on how to enable debug for the build, perhaps you could give
us a hint.
- Andreas
Original-Nachricht
Betreff: Re:
On Fri, Jul 29, 2016 at 10:19:29AM +0100, Sascha Steinbiss wrote:
> >> dpkg-gencontrol: error: error occurred while parsing Depends field:
> >> ,
> >> default-jre | java5-runtime | java6-runtime | java7-runtime |
> >> java8-runtime , jarwrapper (>=0.5), , $, {source, :Version, }, ), , (,
> >>
On Fri, Jul 29, 2016 at 01:52:24PM +0200, louis van belle wrote:
> Package: samba
> Followup-For: Bug #832880
>
>
>
> -- System Information:
> Debian Release: 8.5
> APT prefers stable-updates
> APT policy: (500, 'stable-updates'), (500, 'stable')
> Architecture: amd64 (x86_64)
>
> Kernel:
Hai Jelmer,
I see what you mean but im really not crazy. ;-)
I dont want to be annoying... but please read on. (and sorry but im right in
this case.)
You can check it out yourself.
This is a clean server. Used for testing only.
Its a clean virtual machine jessie only ssh
Package: vnc4server
Version: 4.1.1+X4.3.0-39
Severity: wishlist
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Tried to start regular X session via ~/.vnc/xstartup
* What exactly did you do (or not
Package: apt-cacher-ng
Version: 0.9.3.2-1
Severity: minor
Dear Maintainer,
/etc/logrotate.d/apt-cacher-ng currently contains the following
instructions on when to rotate logs:
/var/log/apt-cacher-ng/apt-cache*.log {
...
size 10M
...
}
/var/log/apt-cacher-ng/apt-cache*.err {
..
daily
On Thu, Jul 28, 2016 at 04:43:41PM +0200, Michael Biebl wrote:
> Am 28.07.2016 um 16:39 schrieb Michael Biebl:
> > Maybe Felipe's helper could be generalized and added to gbp pq, like
> > gbp pq cherry-pick
>
> Or more generally gbp pq cherry-pick --before|after
>
> This will cherry-pick a
Hi,
On Fri, 20 May 2016 10:55:58 +0200 Jonas Smedegaard wrote:
> The correct way to have CDBS not auto-include any docs/changelog files
> is to set the variables to the empty value:
>
> DEB_INSTALL_DOCS_telepathy-ring-dbg =
> DEB_INSTALL_CHANGELOGS_telepathy-ring-dbg =
for the
On Wed, 27 Jul 2016 22:48:40 +0200 Geert Stappers wrote:
On Tue, Jul 26, 2016 at 12:47:33AM +0200, Rob van der Putten wrote:
> On Tue, 26 Jul 2016, Geert Stappers wrote:
> >And that is with which graphical desktop environment?
>
> Xfxe
Most likely XFCE
> >What happens
Hi,
as many users reported here already I think it is fair to enable debugging.
It doesn't really hurt anywhere and I can say that Ubuntu has enabled it as
delta for quite a while without related issues.
As a little helper here the change that would enable it:
Hi Greg,
Regarding your issue, can you please clarify if you are observing the '-'
character in the version string for an FCS build? It has to be noted that the
Oracle policy only prohibits the '-' character in an FCS build.
In case you reported this against an FCS build, can you please
On 29.07.2016 12:48, Emmanuel Bourg wrote:
> Le 29/07/2016 à 11:20, Markus Koschany a écrit :
>
>> If we keep root:tomcat8 then I think 640 is sensible and appropriate.
>
> There is a downside though, our package will become unusable with the
> IDEs since local users will no longer be able to
Hi Chris!
* Chris Lamb , 2016-07-28, 20:48:
lintian: c/systemd: Warn about .service files with a missing WantedBy
target
Updated patch attached, dropping "Certainty: certain".
It certainly shouldn't have been "certain", but you can't just drop
Certainty; it's an obligatory
This failure is probably due to the catalyst package with a regression:
Get:185 http://127.0.0.1:/debian unstable/main amd64 libcatalyst-perl all
5.90111-1 [401 kB]
5.90112 should fix that.
--
Marco
On Sun, Jul 24, 2016 at 18:59:04 +0200, Michael Biebl wrote:
> Am 24.07.2016 um 14:12 schrieb Michael Biebl:
> > for the upcoming jessie stable release, I'd like to update the systemd
> > package with the following fixes:
>
> [..]
>
> > The complete debdiff is attached as well.
>
> I would
This breaks domain name resolution in Ubuntu 16.04, as seen in
(https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1003842).
Consider raising the severity of this bug.
smime.p7s
Description: S/MIME Cryptographic Signature
Control: tag -1 moreinfo
On Mon, Jul 4, 2016 at 18:22:46 +0200, Simon Kainz wrote:
> Package: release.debian.org
> Severity: normal
> Tags: jessie
> User: release.debian@packages.debian.org
> Usertags: pu
>
> Paul Wise found out that duck rund untrusted code from the current directory
>
Package: x11vnc
Version: 0.9.13-1.2+b4
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Connecting to x11vnc with vinagre
* What exactly did you do (or not do) that was effective (or
Le 29/07/2016 à 11:20, Markus Koschany a écrit :
> If we keep root:tomcat8 then I think 640 is sensible and appropriate.
There is a downside though, our package will become unusable with the
IDEs since local users will no longer be able to read the configuration.
I don't think we can satisfy
Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the ruby-semantic-puppet package:
>
> #832529: ruby-semantic-puppet: r10k fails with new version of
> ruby-semantic-puppet
>
> It has been closed by
Control: tag -1 moreinfo
On Fri, Jul 15, 2016 at 22:14:53 +0200, Joel Rosdahl wrote:
> @@ -1745,8 +1747,17 @@
> goto out;
> }
>
> - /* Rewrite to relative to increase hit rate. */
> - input_file =
Package: irqbalance
Version: 1.1.0-2
Severity: wishlist
Tags: patch
Hi,
Since version 1.0.4, upstream provides a local subset of the glib
function it needs (namely glist.h) and thus a build-dependency against
the full-fledged glib2.0 is not needed anymore.
Please remove the build-dependency
Attached is a kernel stack trace that accompanies the x11vnc crash.
The above information is from a different x11vnc crash.
Each stack trace accompanies a different x11vnc crash. All that
is required to recreate the bug is to start x11vnc and login
to the remote desktop, then disconnect.
Jul 28
Control: tags -1 pending
Hi Lucas,
Thanks again for your work on archive rebuilds.
The maven.rules for osmosis have been updated for the recent changes in
libspring-java to fix this build failure.
The fixed package has been uploaded to unstable.
Kind Regards,
Bas
--
GPG Key ID:
Manokwari Now Release
https://github.com/BlankOn/manokwari/releases
and debianized
http://dev.blankonlinux.or.id/browser/tambora/manokwari
Control: tag -1 - moreinfo
Control: tag -1 + confirmed
On Thu, Jul 28, 2016 at 16:49:02 +0200, Ludovic Drolez wrote:
> Hi !
>
> Here is the debdiff!
>
> diff -u backuppc-3.3.0/debian/changelog backuppc-3.3.0/debian/changelog
> --- backuppc-3.3.0/debian/changelog
> +++
Control: tag -1 confirmed
On Tue, Jul 26, 2016 at 14:14:41 +0300, Sergei Golovan wrote:
> Package: release.debian.org
> Severity: normal
> Tags: jessie
> User: release.debian@packages.debian.org
> Usertags: pu
>
> Hi release team!
>
> I'd like to upload stable update for the YAWS web
Florian Weimer skribis:
> We still need the time-based approach if the build ID is not
> available, but I expect most distributions will have something like
> it.
FWIW in Guix we solve it by filling the ‘compilation’ array with a
substring of the installation prefix¹.
Since
Package: samba
Followup-For: Bug #832880
-- System Information:
Debian Release: 8.5
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8
Hi James,
Would you please share the more info / reproducer steps and Warning logs what
you noticed?
Thanks.
> The prerm is looking for /var/lib/binfmts/@basename@ (e.g., openjdk-8) but the
> files under /var/lib/binfmts are named after the binfmt being registered, not
> the package.
> This
Am 29.07.2016 um 09:17 schrieb Michael Biebl:
> That's not a bug in systemd but in your service file.
> If you want to run in early boot, you'll need to use
> DefaultDependencies=yes and specify your dependencies/orderings carefully.
I've filed an upstream RFE bug at [1]. Maybe they have an idea
Source: ghostscript
Version: 9.19~dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> gcc
Source: texworks-manual
Version: 20150506-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
>
Source: jakarta-jmeter
Version: 2.13-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
>
Le 29/07/2016 à 08:17, Chris Lamb a écrit :
> Hi,
>
>> llvm: libfuzzer
> Any movement on this? I was shown a cool demo yesterday by the upstream
> author and its a bit of a pain to get going in Debian. This feels a shame as
> all the sources are there, we just need to do something like:
>
> $
Source: 0ad
Version: 0.0.20-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> checking for
Source: mina2
Version: 2.0.13-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> make[1]:
severity 789839 serious
thanks
On 25/06/15 at 00:04 +0100, Dominic Hargreaves wrote:
> Control: severity -1 important
> Control: retitle -1 xemacs21-packages: FTBFS with timeout in sbuild /
> unwriteable home?
>
>
> On Wed, Jun 24, 2015 at 10:35:10PM +0100, Mark Brown wrote:
> > On Wed, Jun
Source: osmosis
Version: 0.45-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> make[1]:
Source: aiocoap
Version: 0.1+9ae36f4-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
>
Source: telepathy-python
Version: 0.15.19-2.1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
>
Source: libclass-c3-xs-perl
Version: 0.13-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> ok
Source: xpra
Version: 0.17.4+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
>
Hi,
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
[...]
>>dh_gencontrol
>> dpkg-gencontrol: warning: can't parse dependency $
>> dpkg-gencontrol: error: error occurred while parsing Depends field:
>> ,
>> default-jre | java5-runtime | java6-runtime |
Hi there
I'm not going to upload this package as its no longer needed for
asciinema.
The git repo where I did the packaging is
https://anonscm.debian.org/cgit/pkg-go/packages/golang-github-creack-termios.git
Feel free to take over or contact me if any doubt arises.
cheers
--
1AE0 322E B8F7
Package: wnpp
Severity: wishlist
Owner: "Stéphane Glondu"
* Package name: ppx-deriving
Version : 3.3
Upstream Author : Peter Zotov
* URL : https://github.com/whitequark/ppx_deriving
* License : MIT
Programming
On 29/07/16 03:10, Jeff Breidenbach wrote:
> Package: release.debian.org
> Severity: normal
> User: release.debian@packages.debian.org
> Usertags: transition
>
> This is a new upstream release and includes a soname bump on all three
> shared libraries. I've only expressed the primary one in
Source: artemis
Version: 16.0.0+dfsg-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
>
Source: salliere
Version: 0.10-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> make[1]:
Source: eclipse-xsd
Version: 2.9.0-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> make[1]:
Source: refcard
Version: 5.0.9
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> make[1]:
Source: berkshelf-api
Version: 2.1.3-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
>
Source: golang-github-boltdb-bolt
Version: 1.2.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part
Source: perlbrew
Version: 0.76-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> ok 18
> ok 19
Source: ask
Version: 1.0.1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
>
> -- created:
Source: request-tracker4
Version: 4.2.12-6
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
>
Source: python-django-pyscss
Version: 2.0.2-5
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
>
Source: libtest-valgrind-perl
Version: 1.18-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
>
Source: libbio-das-lite-perl
Version: 2.11-4
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
>
On Fri, 29 Jul 2016, Santiago Vila wrote:
> tags 822004 + patch
> thanks
>
> I also recommend switching to dh, but in the meantime, the attached
> patch should work.
We probably will remove nagios3 from debian soon, as it is a dead end.
Thanks
Alex
On Fri, Jul 29, 2016 at 10:12:49AM +0200, Lucas Nussbaum wrote:
> Package: libtool
> Version: 2.4.6-1
> Severity: serious
>
> Hi,
>
> Until libtool 2.4.6-0.1, the first line of output of libtoolize --version was:
> libtoolize (GNU libtool) 2.4.6
> With 2.4.6-1, it became:
> libtoolize (GNU
Source: snapd
Version: 2.0.8+1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
>
Source: mathcomp
Version: 1.5-4
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
>
Control: tags -1 patch
On 27.07.2016 23:39, Emmanuel Bourg wrote:
> Le 27/07/2016 à 13:21, Markus Koschany a écrit :
>
>> So the question is
>>
>> does Tomcat 7/8 need write access to the conf directory at runtime and
>> if yes why?
>
> Yes it does: Tomcat extracts the META-INF/context.xml
Package: src:libgnatcoll
Followup-For: Bug #760004
Control: reopen -1
Hello.
GNATColl supports Python3 with a small patch, but GPS, the main
consumer for this library, is not at all ready. Therefore I am
reverting GNATColl to Python2 until a better solution is found.
Please read
Source: haskell-src-exts
Version: 1.17.1-1
Severity: serious
Your package has been failing to build on mips64el for a while now:
https://buildd.debian.org/status/logs.php?pkg=haskell-src-exts=mips64el
>From the last two logs:
[22 of 24] Compiling Language.Haskell.Exts.Parser (
Hello Elías,
Am Donnerstag, den 28.07.2016, 17:10 -0500 schrieb Elías Alejandro:
> Hello Jörg,
> I can't be able to reproduce this bug and my python version is: 2.7.9
> Could you please send me your python version?
$ apt-cache policy python
python:
Installiert: 2.7.11-2
Source: hyde
Version: 0.8.5a1-4
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> fakeroot
Hi,
I'm unable to reproduce the issue. Could you please confirm that
the error persists under the cricumstances you tried the build?
Kind regards
Andreas.
--
http://fam-tille.de
Hello
The major problem seems the absence of home directory and not dying if
TEMPYASATDIR does not exists.
I will try to solve it by a fallback to /tmp/
Strange that it fails only on amd64 in that case.
Regards
I just posted at
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1606103
that the problem seems to be in
hw/xfree86/drivers/modesetting/drmmode_display.c#add_gtf_modes(),
which is forcing a maximum vertical refresh of 60 (plus 1%), even
though my monitor can actually do up to 120, and
Package: archivemount
Version: 0.8.5-1
There is a new upstream version (0.8.7)
http://www.cybernoia.de/software/archivemount/archivemount-0.8.7.tar.gz
Package: gccintro
Version: 1.0-3
Severity: minor
The debian-packaged version of gccintro is based on upstream version
1.1 (it has the 1.0-1.1 patch applied), yet the upstream version part of the
debian package version number is 1.0.
Source: yasat
Version: 839-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> ./common: line
Source: license-reconcile
Version: 0.11
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
>
Source: findbugs
Version: 3.0.1-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
> make[1]:
Source: ros-rviz
Version: 1.11.10+dfsg-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
>
Source: python-argh
Version: 0.26.1-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
>
Source: docker-swarm
Version: 1.0.1+dfsg-1
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
>
Source: gnome-keyring
Version: 3.20.0-2
Severity: serious
Tags: stretch sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20160728 qa-ftbfs
Justification: FTBFS on amd64
Hi,
During a rebuild of all packages in sid, your package failed to build on
amd64.
Relevant part (hopefully):
>
1 - 100 of 298 matches
Mail list logo