On 2019-03-28 02:14, Camm Maguire wrote:
> Greetings! Didn't look significant to me, but happy to revert if
> needed. How/when do I get the official word here?
You need to file an unblock request for lam
Andreas
Greetings! Didn't look significant to me, but happy to revert if
needed. How/when do I get the official word here?
Take care,
Andreas Beckmann writes:
> On 2019-03-24 16:51, Debian Bug Tracking System wrote:
>>* debhelper compat level 9
>>* standard debian build flags
>
> These are ba
Greetings! Yes, thanks! Did you see the upload? One more
forthcoming
Take care,
Andreas Beckmann writes:
> Hi Camm,
>
> On 2019-03-13 22:44, Camm Maguire wrote:
>> Greetings! I should have some time to look at this this week. If you
>> happen to develop a patch, that would of course sp
Your message dated Wed, 27 Mar 2019 23:06:06 +
with message-id
and subject line Bug#909865: fixed in openexr 2.2.1-4.1
has caused the Debian Bug report #909865,
regarding openexr FTBFS on i386 with gcc 8
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Processing commands for cont...@bugs.debian.org:
> retitle 924891 glibc: misc/tst-pkey fails due to cleared PKRU register after
> signal in amd64 32-bit compat mode
Bug #924891 [src:glibc] glibc: FTBFS: tst-pkey fails for 32-bit processes on
Xeon SP
Changed Bug title to 'glibc: misc/tst-pkey fai
retitle 924891 glibc: misc/tst-pkey fails due to cleared PKRU register after
signal in amd64 32-bit compat mode
thanks
* Lucas Nussbaum:
> On 27/03/19 at 08:48 +0100, Florian Weimer wrote:
>> > If that's useful, I can easily provide access to an AWS VM to debug this
>> > issue.
>>
>> Oh, that
Processing commands for cont...@bugs.debian.org:
> forcemerge 921688 923595
Bug #921688 [electrum] Electrum vulnerable to malware
Bug #923595 [electrum] electrum: Electrum branch containing critical
vulnerability should be updated
Severity set to 'serious' from 'important'
Merged 921688 923595
>
The log contains:
/usr/include/x86_64-linux-gnu/mpich/mpicxx.h:22:4: error: #error 'Please use
the same version of GCC and g++ for compiling MPICH and user MPI programs'
so this bugs seems to be another instance of #807666 and should be fixed
once the fix for that reaches testing.
Bernha
Your message dated Wed, 27 Mar 2019 21:34:30 +
with message-id
and subject line Bug#911993: fixed in structure-synth 1.5.0-5
has caused the Debian Bug report #911993,
regarding structure-synth FTBFS on armel/armhf: error: glVertex3f was not
declared in this scope
to be marked as done.
This m
Processing control commands:
> severity -1 serious
Bug #900573 [qreator] qreator: won't start complaining no module named Image
Severity set to 'serious' from 'normal'
> tags -1 + patch
Bug #900573 [qreator] qreator: won't start complaining no module named Image
Added tag(s) patch.
--
900573: ht
On 27/03/19 at 22:00 +0100, Lucas Nussbaum wrote:
> On 27/03/19 at 08:48 +0100, Florian Weimer wrote:
> > > If that's useful, I can easily provide access to an AWS VM to debug this
> > > issue.
> >
> > Oh, that would be quite helpful indeed.
>
> Can you send your SSH key? (I thought there was a w
Your message dated Wed, 27 Mar 2019 21:09:12 +
with message-id
and subject line Bug#916334: fixed in r-cran-lwgeom 0.1-5+repack-1
has caused the Debian Bug report #916334,
regarding r-cran-lwgeom: autopkgtest regression
to be marked as done.
This means that you claim that the problem has been
retitle 924802 madness: FTBFS: failure checking for working mpicxx
block 924802 807666
thanks
Just some quick fly-by observations:
While the are errors about pow in the log, those seem to be harmless and
properly ignored capability checking.
The actual error causing the failure in the log is:
-
Processing commands for cont...@bugs.debian.org:
> block 924802 by 807666
Bug #924802 [src:madness] madness: FTBFS: failure checking for working mpicxx
924802 was not blocked by any bugs.
924802 was not blocking any bugs.
Added blocking bug(s) of 924802: 807666
> block 924813 by 807666
Bug #924813
On 27/03/19 at 08:48 +0100, Florian Weimer wrote:
> > If that's useful, I can easily provide access to an AWS VM to debug this
> > issue.
>
> Oh, that would be quite helpful indeed.
Can you send your SSH key? (I thought there was a way to get the SSH key
for a DD, but I cannot find it anymore)
T
Processing commands for cont...@bugs.debian.org:
> retitle 924802 madness: FTBFS: failure checking for working mpicxx
Bug #924802 [src:madness] madness: FTBFS: CheckFunctionExists.c:17: undefined
reference to `pow'
Changed Bug title to 'madness: FTBFS: failure checking for working mpicxx' from
'
Processing commands for cont...@bugs.debian.org:
> retitle 924891 glibc: FTBFS: tst-pkey fails for 32-bit processes on Xeon SP
Bug #924891 [src:glibc] glibc: FTBFS:
/<>/build-tree/amd64-libc/conform/UNIX98/ndbm.h/scratch/ndbm.h-test.c:1:10:
fatal error: ndbm.h: No such file or directory
Changed
Processing commands for cont...@bugs.debian.org:
> forcemerge 924328 925617
Bug #924328 [javahelper] javahelper: jh_build regressed for -doc packages
Bug #924339 [javahelper] javahelper: jh_build regressed for -doc packages
Unable to merge bugs because:
package of #925617 is 'src:javatools' not 'j
Your message dated Wed, 27 Mar 2019 19:58:00 +
with message-id <051e9bca-acfc-01c9-c30c-da9926faf...@thykier.net>
and subject line Re: Squeeze->Wheezy: dist-upgrade fails, /usr/bin/python
unable to load libssl.so.1.0.0
has caused the Debian Bug report #680626,
regarding Squeeze->Wheezy: dist-u
> I will upload the upstream version 1.19 to stretch-backports by now.
This command should work:
$ aptitude -t stretch-backports install rtv
But the backports version is still 1.14.1.
Your message dated Wed, 27 Mar 2019 19:54:00 +
with message-id <1150e9d1-dfd9-c76b-b823-c470957a6...@thykier.net>
and subject line Re: HTTP 500 error after logging in to alioth SSO
has caused the Debian Bug report #822989,
regarding sso.debian.org: Can't login using Alioth account
to be marked
Processing commands for cont...@bugs.debian.org:
> package rtv
Limiting to bugs with field 'package' containing at least one of 'rtv'
Limit currently set to 'package':'rtv'
> severity 884632 grave
Bug #884632 [rtv] rtv crashes when viewing submission
Severity set to 'grave' from 'serious'
> found
Source: octave-fits
Version: 1.0.7-2
Severity: serious
X-Debbugs-Cc: mcop...@straitcity.com
Le mercredi 27 mars 2019 à 10:04 -0500, Mark Copper a écrit :
> On the off chance of asking twice, what is this about libcfitsio?
> libcfitsio-dev is already installed with ffghps defined in fitsio.h
>
> o
Package: src:javatools
Version: 0.72.6
Severity: serious
Tags: sid buster patch
jh_build initializes javac_opts with javadoc_opts, discard javac options,
apparently a typo.
patch at
http://launchpadlibrarian.net/416705136/javatools_0.72.6_0.72.6ubuntu1.diff.gz
Le 27/03/2019 à 12:41, Andrej Shadura a écrit :
> I’m not entirely sure it is possible. But maybe someone else is going to
> have better luck removing openhft dependencies.
I'll get a look during the Paris BSP on sunday.
Emmanuel Bourg
Adam D. Barratt (2019-03-26):
> As I mentioned on IRC, we can't "push it into stretch" without a point
> release, and the whole point of this exercise was to avoid having to
> schedule another short-notice point release.
FTAOD: That's exactly in line with what I think I tried to convey over
the l
Your message dated Wed, 27 Mar 2019 14:57:03 +
with message-id
and subject line Bug#925328: fixed in onionshare 2.0-2
has caused the Debian Bug report #925328,
regarding onionshare: Missing dependency on python3-crypto and python3-socks
to be marked as done.
This means that you claim that the
Processing control commands:
> severity -1 serious
Bug #922343 [src:python-sievelib] python-sievelib: autopkgtest regression: No
module named 'pkg_resources'
Severity set to 'serious' from 'normal'
> tags -1 + sid buster
Bug #922343 [src:python-sievelib] python-sievelib: autopkgtest regression: N
Hi,
as far as I understood the Debian Java team agreed that droping the
documentation is an appropriate way to deal with errors like this:
Creating destination directory: "debian/_jh_build.javadoc/api/"
javadoc: error - The code being documented uses packages in the unnamed module,
but the packa
Your message dated Wed, 27 Mar 2019 12:02:08 +
with message-id
and subject line Bug#922031: fixed in python-certbot 0.28.0-1~deb9u2
has caused the Debian Bug report #922031,
regarding certbot: Debian 9 systemd timer inactive after upgrade to
0.28.0-1~deb9u1
to be marked as done.
This means t
Your message dated Wed, 27 Mar 2019 12:02:08 +
with message-id
and subject line Bug#922543: fixed in python-certbot 0.28.0-1~deb9u2
has caused the Debian Bug report #922543,
regarding python-certbot: FTBFS in stretch when built with sbuild (unmet
build-depends)
to be marked as done.
This mea
On Wed, Mar 27, 2019 at 12:37:17PM +0100, Andrej Shadura wrote:
> > (srly? Using dh -N instead of removing the packages from d/control?!…).
>
> Yes, so that it’s easier to bring them back when they’re unbroken.
But that doesn't help anything.
You removed two packages because a dependency of the
Processing control commands:
> forcemerge 925509 925510
Bug #925509 [netbeans] netbeans: Netbeans not usable with java in Buster
Bug #925510 [netbeans] netbeans: Netbeans not usable with java in Buster
Merged 925509 925510
> severity -1 serious
Bug #925509 [netbeans] netbeans: Netbeans not usable
On Tue, 26 Mar 2019 15:27:38 +0100 Emmanuel Bourg
wrote:> I think this was done to remove the openhft packages that are
> incompatible with Java 11. But maybe the affected Spring modules could
> be salvaged by disabling the code using openhft (if it's optional).
I’m not entirely sure it is possib
On Tue, 26 Mar 2019 16:35:41 -0700 tony mancill wrote:
> Regarding the OpenHFT, I tried to help the overall situation by
> uploading new versions to experimental several months back but as was
> discussed on the list (I'd have to find the link), was requested to
> hold-off on transitioning them in
On Wed, 27 Mar 2019 12:01:40 +0100 Mattia Rizzolo wrote:
> On Tue, Mar 26, 2019 at 04:35:41PM -0700, tony mancill wrote:
> > Are you sure about the upload of 4.3.22-2 changing the number of binary
> > packages built? If that is the case, it was completely unintentional.
>
> Meh, apparently nope,
Package: irssi-plugin-xmpp
Version: 0.54-2.1
Severity: grave
Justification: renders package unusable
I get the following warnings from irssi when trying to use it with
irssi-plugin-xmpp:
10:49 -!- Irssi: xmpp/core is ABI version 13 but Irssi is version 20,
cannot
load
10:4
Your message dated Wed, 27 Mar 2019 11:04:25 +
with message-id
and subject line Bug#925592: fixed in org-mode 9.2.2+dfsg-2
has caused the Debian Bug report #925592,
regarding elpa-org: Fails to install, due to byte compile error
to be marked as done.
This means that you claim that the problem
On Tue, Mar 26, 2019 at 04:35:41PM -0700, tony mancill wrote:
> Are you sure about the upload of 4.3.22-2 changing the number of binary
> packages built? If that is the case, it was completely unintentional.
Meh, apparently nope, I was tricked by that dpkg change in the Binary
field... I had only
Control: reassign -1 ftp.debian.org
Re: Ansgar Burchardt 2019-03-20
<751a89074fcaa393f2cc26ff676e9e3434ecd706.ca...@43-1.org>
> the OpenSSL ./. GPL problem (if one sees it as a problem) is larger
> than just libpq5: just looking at a small sample of the direct rdeps of
> libssl1.1, one can find t
Processing control commands:
> reassign -1 ftp.debian.org
Bug #924937 [libpq5] libpq5: OpenSSL license contamination of GPL
reverse-dependencies
Bug reassigned from package 'libpq5' to 'ftp.debian.org'.
No longer marked as found in versions postgresql-11/11.2-2.
Ignoring request to alter fixed ve
On Wed, Mar 27, 2019 at 09:38:12AM +0100, Andreas Tille wrote:
> On Wed, Mar 27, 2019 at 09:10:39AM +0100, Olivier Sallou wrote:
> > As we are in freeze, should we ask release team to unblock transition
> > and then push to unstable?
>
> Yes, please do so.
You can first push to unstable and then
Package: elpa-org
Version: 9.2.2+dfsg-1
Severity: grave
Dear Maintainer,
when upgrading org-mode from unstable today, it failed in postinst in
compiling the .el files. The full of a subsequent "dpkg --configure
--all" run is attached. It seems to me that the message...
,
| In toplevel form:
On Fri, Dec 28, 2018 at 11:49:01AM +0100, Niels Thykier wrote:
> We need a new release signing key for buster so we can include it in a
> debian-archive-keyring upload before the buster release.
Release key exists, but no point adding it to d-a-k until we have an
archive key as well.
--
Jonath
Your message dated Wed, 27 Mar 2019 08:48:33 +
with message-id
and subject line Bug#867682: fixed in squid-deb-proxy 0.8.14+nmu2
has caused the Debian Bug report #867682,
regarding squid-deb-proxy-client: breaks apt operation if removed and system
upgraded to stretch
to be marked as done.
Th
On Wed, Mar 27, 2019 at 09:10:39AM +0100, Olivier Sallou wrote:
>
> > During a rebuild of all packages in buster (in a buster chroot, not a
> > sid chroot), your package failed to build on amd64.
>
> I just did a try on buster.
>
> It succeeded first time, not on a second rebuild (with same erro
On 3/26/19 9:46 PM, Lucas Nussbaum wrote:
> 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 bus
Package: android-sdk-helper
Version: 0.1
Severity: serious
Tags: patch ftbfs
Justification: fails to build from source
Hi,
android-sdk-helper FTBFS on sid/amd64.
Adding the 'libjaxp1.3' to Build-Depends makes build successfully. I did
make a simple patch, but I'm not sure the target:
1. Bui
* Lucas Nussbaum:
> On 26/03/19 at 23:10 +0100, Aurelien Jarno wrote:
>> 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 wa
On 26/03/19 at 23:10 +0100, Aurelien Jarno wrote:
> 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 elimina
Your message dated Wed, 27 Mar 2019 07:35:33 +
with message-id
and subject line Bug#925377: fixed in ukui-biometric-auth 1.0.3-2
has caused the Debian Bug report #925377,
regarding libpam-biometric: missing Breaks+Replaces: ukui-polkit (<< 1.0.3)
to be marked as done.
This means that you clai
Your message dated Wed, 27 Mar 2019 08:28:06 +0100
with message-id <4dc0756958e3975c6b445d8bc538d73973190249.ca...@collabora.com>
and subject line Re: gdcm: FTBFS in buster/sid
has caused the Debian Bug report #923750,
regarding gdcm: FTBFS in buster/sid
to be marked as done.
This means that you c
52 matches
Mail list logo
