On 2019-03-27 00:48, wf...@niif.hu wrote:
> Yes, I'm on it. It's somewhat bizarre: libcrmcluster1-dev wasn't part
> of jessie or stretch. Similarly, pacemaker-dev was present in wheezy
> only, until I reintroduced it recently, and looks like its ghost came
> back to haunt us. I didn't
Your message dated Wed, 27 Mar 2019 00:21:14 +
with message-id
and subject line Bug#924836: fixed in python-bottle 0.12.15-2
has caused the Debian Bug report #924836,
regarding python-bottle: FTBFS: build-dependency not installable: python-tox
to be marked as done.
This means that you claim
Your message dated Wed, 27 Mar 2019 00:02:35 +
with message-id
and subject line Bug#925566: fixed in python-trustme 0.4.0-2
has caused the Debian Bug report #925566,
regarding python-trustme: FTBFS: dh_auto_test: pybuild --test --test-pytest -i
python{version} -p 3.7 returned exit code 13
to
Valentin Vidic writes:
> On Mon, Mar 25, 2019 at 03:45:58PM +0100, Andreas Beckmann wrote:
>
>> In that case you should probably add Breaks+Replaces against all of the
>> old -dev packages that were merged, just to be on the safe side.
>
> Yes, that is the plan. I think wferi will take care of
On Tue, Mar 26, 2019 at 02:46:35PM +0100, Mattia Rizzolo wrote:
> Source: libspring-java
> Version: 4.3.22-2
> Severity: serious
> X-Debbugs-Cc: tony mancill
> Control: block 925390 924635 924634 by -1
>
> Dear maintainer (and tony, whose upload 4.3.22-2 caused this bug),
>
> your package
Jim Turner pisze:
Hi,
> truetype fonts, and instead use pkg-config. Problem is that the patch
> properly removes it from configure.in, but NOT from configure itself
The configure script is regenerated during the build process, so there
is no need to change it via a patch.
> I simply untacked
On Tue, Mar 26, 2019 at 09:49:00PM +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in buster (in a buster chroot, not a
> sid chroot), your package failed to build on amd64.
Thank you for this report.
It looks like python-trustme (build time) tests uses the idna directly,
so an
Your message dated Tue, 26 Mar 2019 23:36:14 +0100
with message-id <20190326223612.bxaixpezuzv2b...@debian.org>
and subject line Re: Stretch-backports linux-image-cloud-amd64 broken
has caused the Debian Bug report #922184,
regarding Stretch-backports linux-image-cloud-amd64 broken
to be marked as
Package: kernel-package
Version: 13.018+nmu1
Just wanted to let you know I'm a user of kernel-package and it works
fine on my amd64 debian testing machine. Just finished compiling
linux-5.0.4-amd64 kernel for my specific use case. I'm not seeing any
major bugs like what I see on my x86
Your message dated Tue, 26 Mar 2019 21:58:30 +0100
with message-id <20190326205830.5imcnqdus6e4a...@xanadu.blop.info>
and subject line Re: Bug#924858: also can't reproduce
has caused the Debian Bug report #924858,
regarding doxygen: FTBFS: make[4]: ***
Your message dated Tue, 26 Mar 2019 22:00:34 +0100
with message-id <20190326210034.33se6stzmamgp...@xanadu.blop.info>
and subject line Re: Bug#924823: libcaca: FTBFS: mv: cannot stat
'latex/refman.pdf': No such file or directory
has caused the Debian Bug report #924823,
regarding libcaca: FTBFS:
Your message dated Tue, 26 Mar 2019 22:02:15 +0100
with message-id <20190326210215.frm6qrwfuh2uu...@xanadu.blop.info>
and subject line Re: Bug#924808: lua-nvim: FTBFS: E: Build killed with signal
TERM after 150 minutes of inactivity
has caused the Debian Bug report #924808,
regarding lua-nvim:
Source: ruby-voight-kampff
Version: 1.1.3-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20190325 qa-ftbfs
Justification: FTBFS in buster on amd64
Hi,
During a rebuild of all packages in buster (in a buster chroot, not a
sid chroot), your package failed
Source: python-trustme
Version: 0.4.0-1
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20190325 qa-ftbfs
Justification: FTBFS in buster on amd64
Hi,
During a rebuild of all packages in buster (in a buster chroot, not a
sid chroot), your package failed to
Source: gcc-8-cross
Version: 26
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20190325 qa-ftbfs
Justification: FTBFS in buster on amd64
Hi,
During a rebuild of all packages in buster (in a buster chroot, not a
sid chroot), your package failed to build on
On 2019-03-22 17:30, Florian Weimer wrote:
> > About the archive rebuild: The rebuild was done on EC2 VM instances from
> > Amazon Web Services, using a clean, minimal and up-to-date chroot. Every
> > failed build was retried once to eliminate random failures.
>
> I believe the actual test
Source: cnvkit
Version: 0.9.5-2
Severity: serious
Tags: buster sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20190325 qa-ftbfs
Justification: FTBFS in buster on amd64
Hi,
During a rebuild of all packages in buster (in a buster chroot, not a
sid chroot), your package failed to build on
Your message dated Tue, 26 Mar 2019 20:47:49 +
with message-id
and subject line Bug#923759: fixed in netlib-java 0.9.3-5
has caused the Debian Bug report #923759,
regarding mtj: FTBFS in buster/sid
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
On Tue, Mar 26, 2019 at 07:29:12PM +0100, Gert Wollny wrote:
> the problem is I at least don't know the offending package because I
> was not able to reproduce the build failure. Whatever it was, it has
> probably already benn fixed.
My build history for buster:
Status: successful
On Tue, 2019-03-26 at 10:39 -0700, Vagrant Cascadian wrote:
> On 2019-03-26, Adam D. Barratt wrote:
> > On 2019-03-15 06:44, Adam D. Barratt wrote:
> > > The updated images for armhf have been available in p-u for a
> > > couple of
> > > days now.
> > >
> > > Feedback would be appreciated, as we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Gabriel Filion a écrit :
> On 2019-03-26 2:43 p.m., Gabriel Filion wrote:
>> Did you recently upgrade smokeping? if so what version were you
>> using before? (maybe check your dpkg logs for signs of upgrade of
>> the smokeping package)
>
> I just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Gabriel Filion a écrit :
> Hi Bertrand,
Hello,
> e.g. the file is in /run/smokeping and systemd is able to use it
> to restart the servce.
In my case, systemd doesn't create /run/smokeping.
> Did you recently upgrade smokeping?
On 2019-03-26 2:43 p.m., Gabriel Filion wrote:
> Did you recently upgrade smokeping? if so what version were you using
> before? (maybe check your dpkg logs for signs of upgrade of the
> smokeping package)
I just thought of something else: if you were using the 2.7.3-1 package
previously, it's
Hi Bertrand,
On 2019-03-25 2:57 a.m., BERTRAND Joël wrote:
> I have restarted a server last sunday and I have seen that smokeping doesn't
> start anymore.
>
> In systemd config file, smokeping is launched with --pid-dir=/run/smokeping
> and
> systemd complains about non existent pid file.
>
>
Processing commands for cont...@bugs.debian.org:
> severity 92 important
Bug #92 [src:linux] linux-image-4.19.0-4-amd64: Display manager fails to
start or display anything on IvyBridge with linux-image-4.19.0-4-amd64
Severity set to 'important' from 'grave'
> thanks
Stopping processing
Package: src:linux
Version: 4.19.28-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
after upgrading the kernel to 4.19.0-4 or later (5.0.0-trunk), my IvyBridge
laptop fails to start the display manager.
I end up with a black screen and a non blinking _ character in the
Hi,
the problem is I at least don't know the offending package because I
was not able to reproduce the build failure. Whatever it was, it has
probably already benn fixed.
Best,
Gert
Your message dated Tue, 26 Mar 2019 18:18:44 +
with message-id
and subject line Bug#905178: fixed in apt-cacher 1.7.20.1
has caused the Debian Bug report #905178,
regarding apt-cacher: prompting due to modified conffiles which were not
modified by the user: /etc/default/apt-cacher
to be
On 2019-03-26, Adam D. Barratt wrote:
> On 2019-03-15 06:44, Adam D. Barratt wrote:
>> The updated images for armhf have been available in p-u for a couple of
>> days now.
>>
>> Feedback would be appreciated, as we would like to be able to accept
>> the new kernel upload into p-u, which will
Your message dated Tue, 26 Mar 2019 17:35:02 +
with message-id
and subject line Bug#911918: fixed in ruby-openssl 2.1.2-1
has caused the Debian Bug report #911918,
regarding ruby-openssl: CVE-2018-16395: OpenSSL::X509::Name equality check does
not work correctly
to be marked as done.
This
Package: gocode
Version: 20150303-3+b1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
The gocode server only returns "PANIC" autocompletion because of the
following panic:
panic: Can't find the package clause
1(runtime.call32):
Your message dated Tue, 26 Mar 2019 17:21:16 +
with message-id
and subject line Bug#918610: fixed in ruby-model-tokenizer 1.0.1-2
has caused the Debian Bug report #918610,
regarding ruby-model-tokenizer FTBFS with rails 5.2
to be marked as done.
This means that you claim that the problem has
Hi Andreas,
On Sat, Mar 23, 2019 at 05:04:56PM +0100, Andreas Beckmann wrote:
>Package: lava-server
>Version: 2019.01-4
>Severity: serious
>User: debian...@lists.debian.org
>Usertags: piuparts
>Control: found -1 2014.09.1-1+deb8u1
>
>Hi,
>
>during a test with piuparts I noticed your package's
On Tue, 26 Mar 2019 14:46:35 +0100 Mattia Rizzolo wrote:
> Dear maintainer (and tony, whose upload 4.3.22-2 caused this bug),
>
> your package libspring-java suddenly stopped building two binaries that
> were actively used by other packages, like activemq.
>
> What's very worse, the changelog
Processing control commands:
> reassign -1 ca-certificates-java
Bug #925431 [openjdk-12-jre-headless,ca-certificates-java]
openjdk-12-jre-headless,ca-certificates-java: fails to install in sid
Bug reassigned from package 'openjdk-12-jre-headless,ca-certificates-java' to
'ca-certificates-java'.
Control: reassign -1 ca-certificates-java
Control: found -1 20190214
Control: tags -1 + sid buster
the postinst is not ready for OpenJDK >= 12. Please extend the loop for java
versions 12 - 17 (inclusive, the next OpenJDK LTS version).
Your message dated Tue, 26 Mar 2019 13:48:38 +
with message-id
and subject line Bug#924841: fixed in lib3mf 1.8.1+ds-3
has caused the Debian Bug report #924841,
regarding lib3mf: FTBFS: dh_makeshlibs: failing due to earlier errors
to be marked as done.
This means that you claim that the
Source: libspring-java
Version: 4.3.22-2
Severity: serious
X-Debbugs-Cc: tony mancill
Control: block 925390 924635 924634 by -1
Dear maintainer (and tony, whose upload 4.3.22-2 caused this bug),
your package libspring-java suddenly stopped building two binaries that
were actively used by other
Package: src:schema2ldif
Version: 1.3-2
Severity: serious
Justification: Policy 3.3
Policy 3.3 requires a working email address for the maintainer.
Maintainer notifications from ftp-master.debian.org are failing:
This message was created automatically by mail delivery software.
A message that
Processing commands for cont...@bugs.debian.org:
> found 900787 304.137-7
Bug #900787 [src:nvidia-graphics-drivers-legacy-304xx]
nvidia-graphics-drivers-legacy-304xx: does not support Xorg Xserver 1.20
Marked as found in versions nvidia-graphics-drivers-legacy-304xx/304.137-7.
> notfixed 895795
Hi lynxis,
On Mon, Mar 25, 2019 at 11:04 PM Alexander Couzens wrote:
> > I'm playing with the different patched versions for hours now.
> > Indeed, it seems with your latest patch the memory leak is bearable.
>
> Nice to hear. I compressed a 8GB tree of toolchains and rootfs with
> valgrind
Processing commands for cont...@bugs.debian.org:
> tags 925483 + upstream
Bug #925483 [tilda] tilda: does not start (segfault)
Added tag(s) upstream.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
925483:
Source: openhft-chronicle-bytes
Version: 1.16.25-1
Severity: serious
Justification: fails to build from source
Hi,
openhft-chronicle-bytes/experimental recently started to FTBFS:
[ESC[1;31mERRORESC[m] COMPILATION ERROR :
[ESC[1;34mINFOESC[m]
On 2019-03-15 06:44, Adam D. Barratt wrote:
The updated images for armhf have been available in p-u for a couple of
days now.
Feedback would be appreciated, as we would like to be able to accept
the new kernel upload into p-u, which will block a further rebuild here
as it brings an ABI bump.
close 925374 2019031302
thanks
Processing commands for cont...@bugs.debian.org:
> close 925374 2019031302
Bug #925374 [dns-root-data] dns-root-data: ships an obsolete root zone signing
key
Ignoring request to alter fixed versions of bug #925374 to the same values
previously set
Bug #925374 [dns-root-data] dns-root-data:
Hello Nicolas
On Mon, 25 Mar 2019 12:08:18 -0400 Scott Kitterman
wrote:> Package: src:lirc
> Version: 0.10.1-5.1
> Severity: grave
> Justification: renders package unusable
>
> Removal of the obselete packages dropped in the most recent upload is
> blocked by:
>
> - broken Build-Depends:
>
Hello Jakub,
On Mon, Mar 25, 2019 at 11:15:59AM +0100, Jakub Wilk wrote:
> Hi Helge!
>
> * Helge Kreutzmann , 2019-03-23, 20:48:
> >+/* Create a secure private temporary directory */
> >+fifosdir = mkdtemp(FIFODIR "tvtimeXX");
>
> The mkdtemp(2) man page says: "Since it will be
Package: src:python-escript
Vesion: 5.3-1
Severity: serious
Tags: sid buster
python-escript ftbfs on some release architectures (armhf, mips, mips64el,
mipsel), and blocks the python3.6 removal.
Control: tags -1 patch
Hi,
This is caused by using new github.com/ugorji/go/codec.
Please see patch in attachment.
Repo created before still can't be deleted, but new repo can be
deleted after patch.
--
Shengjing Zhu
aptly.debdiff
Description: Binary data
Processing control commands:
> tags -1 patch
Bug #923866 [aptly] aptly: unable to delete local repositories
Added tag(s) patch.
--
923866: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923866
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> reassign 923752 javahelper 0.72.2
Bug #923752 {Done: Leo Singer } [javatools] healpix-java:
FTBFS in buster/sid
Bug reassigned from package 'javatools' to 'javahelper'.
No longer marked as found in versions 0.72.2.
Ignoring request to alter
Control: severity -1 important
Control: tags -1 + unreproducible moreinfo
Thank you for the report.
On Mon, Mar 25, 2019 at 12:18:02PM -0400, PICCORO McKAY Lenz wrote:
> Package: lighttpd
> Version: 1.4.35-4+deb8u1
> Version: 1.4.53-3
You are listing two versions here. Does it really affect
Processing control commands:
> severity -1 important
Bug #925478 [lighttpd] restart action breaks with systemd (Again)
Severity set to 'important' from 'grave'
> tags -1 + unreproducible moreinfo
Bug #925478 [lighttpd] restart action breaks with systemd (Again)
Added tag(s) moreinfo and
Control: reassign -1 javatools 0.72.2
Control: forcemerge 923748 -1
This bug is actually fixed in the javahelper package, so a separate fix
is not required. The healpix-java package currently in testing can be
built with the updated javahelper, except for the problem mentioned in
#925507 (to be
Processing control commands:
> reassign -1 javatools 0.72.2
Bug #923752 {Done: Leo Singer } [src:healpix-java]
healpix-java: FTBFS in buster/sid
Bug reassigned from package 'src:healpix-java' to 'javatools'.
No longer marked as found in versions healpix-java/3.40-1.
No longer marked as fixed in
56 matches
Mail list logo
