Your message dated Sat, 12 Sep 2020 05:48:26 +
with message-id
and subject line Bug#964639: fixed in gitlab-ci-multi-runner 13.3.1+dfsg-1
has caused the Debian Bug report #964639,
regarding gitlab-ci-multi-runner: FTBFS
to be marked as done.
This means that you claim that the problem has
tony mancill:
> Hi Chris!
Hello again Tony :)
> On Sat, Sep 05, 2020 at 05:43:17AM +, Chris Knadle wrote:
>> Chris Knadle:
>>> For what it's worth, I used a clean cowbuilder sid chroot that was fully
>>> upgraded to build openjfx 11.0.7+0-4 and the package built fine. The build
>>> log
>>>
Control: tag -1 pending
Hello,
Bug #964639 in gitlab-ci-multi-runner reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Processing control commands:
> tag -1 pending
Bug #964639 [src:gitlab-ci-multi-runner] gitlab-ci-multi-runner: FTBFS
Added tag(s) pending.
--
964639: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964639
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Sat, 12 Sep 2020 00:18:35 +
with message-id
and subject line Bug#969889: fixed in nvidia-graphics-drivers-legacy-390xx
390.138-3
has caused the Debian Bug report #969889,
regarding linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not
work
to be marked as
Your message dated Sat, 12 Sep 2020 00:18:35 +
with message-id
and subject line Bug#969894: fixed in nvidia-graphics-drivers-legacy-390xx
390.138-3
has caused the Debian Bug report #969894,
regarding nvidia-legacy-390xx-driver: X will not start with
nvidia-legacy-390.xx driver and 5.8
Your message dated Sat, 12 Sep 2020 00:18:35 +
with message-id
and subject line Bug#969889: fixed in nvidia-graphics-drivers-legacy-390xx
390.138-3
has caused the Debian Bug report #969889,
regarding nvidia-legacy-390xx-driver: X will not start with
nvidia-legacy-390.xx driver and 5.8
Your message dated Sat, 12 Sep 2020 00:18:35 +
with message-id
and subject line Bug#969894: fixed in nvidia-graphics-drivers-legacy-390xx
390.138-3
has caused the Debian Bug report #969894,
regarding linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not
work
to be marked as
Your message dated Fri, 11 Sep 2020 23:04:24 +
with message-id
and subject line Bug#969842: fixed in mailcheck 1.91.2-4
has caused the Debian Bug report #969842,
regarding mailcheck: autopkgtest should be marked superficial
to be marked as done.
This means that you claim that the problem has
Your message dated Fri, 11 Sep 2020 21:48:38 +
with message-id
and subject line Bug#957746: fixed in ramond 0.5-4.1
has caused the Debian Bug report #957746,
regarding ramond: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Importing the new upstream version 4.5.0 will need the enclosed changes.
Upstream commit dfee8d03468f25667a95902008933e3c4080d38d introduced an
ABI change that might have to be dealt with: Unifying
wolfSSL_sk_SSL_CIPHER_dup and wolfSSL_sk_X509_dup to wolfSSL_sk_dup.
From: Bastian Germann
Date:
Your message dated Fri, 11 Sep 2020 20:34:19 +
with message-id
and subject line Bug#957144: fixed in dnshistory 1.3-2.1
has caused the Debian Bug report #957144,
regarding dnshistory: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If
On Fri, Sep 11, 2020 at 09:51:24PM +0200, Aigars Mahinovs wrote:
> Agreed. It was packaged as a reverse dependency for other software,
> but other problems eventually prevented the packaging of that.
Ack, I've just filed an RM bug.
Cheers,
Moritz
Hello,
I'm not the original author but the maintainer of the unofficial
https://github.com/speed47/dvdisaster version. I happen to already have
fixed this compilation issue. The patch is trivial and attached to this
message.
Best Regards,
Stéphane.
diff --git a/dvdisaster.c b/dvdisaster.c
Agreed. It was packaged as a reverse dependency for other software,
but other problems eventually prevented the packaging of that.
On Fri, 11 Sep 2020 at 21:42, Moritz Mühlenhoff wrote:
>
> On Fri, Aug 30, 2019 at 07:30:59AM +, Matthias Klose wrote:
> > Package: src:piggyphoto
> > Version:
Package: enigmail
Version: 2:2.1.6+ds1-1
Severity: grave
Justification: renders package unusable
X-Debbugs-Cc: onit...@gmail.com
Dear Maintainer,
Please consider uploading the latest 2.2 version of Enigmail to support the
ongoing Thunderbird upgrade to version 78.
This version includes a
Package: librust-derive-builder+compiletest-rs-dev
Version: 0.9.0-2
Severity: grave
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu groovy
The librust-derive-builder+compiletest-rs-dev package is uninstallable
because it depends on librust-compiletest-rs-0.3+default-dev, which does
On Fri, Aug 30, 2019 at 07:30:59AM +, Matthias Klose wrote:
> Package: src:piggyphoto
> Version: 0.1dev-git20141014
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
>
> Python2 becomes end-of-live upstream, and Debian aims to remove
>
Ximin,
On Tue, Sep 08, 2020 at 09:23:49PM +0100, Ximin Luo wrote:
> You keep filing these same bugs. I have told you this many times before
> already: this is just how rust packaging works, Britney's migration policy
> already prevents these packages from reaching Debian Testing, so there is
>
On Tue, Sep 01, 2020 at 07:11:46PM +1000, Dmitry Smirnov wrote:
> On Tuesday, 1 September 2020 4:57:56 AM AEST Moritz Mühlenhoff wrote:
> > There's radio silence on https://bugs.mysql.com/bug.php?id=98839,
>
> They are not very transparent and their public bug tracker is somewhat
> redundant, I
On Sun, Jul 26, 2020 at 01:31:08PM +0200, Moritz Mühlenhoff wrote:
> Hi Marcos,
>
> I overlooked this in my inbox..
>
> On Tue, Jul 07, 2020 at 11:15:58PM +0200, Marcos Fouces wrote:
> > Hello Moritz
> >
> > I did some work time ago on ganglia [1] but i never get this work
> > published due to
On Thu, Dec 26, 2019 at 03:57:53PM +0100, Sascha Steinbiss wrote:
> Just an update: Python 3 compatibility is indeed introduced in the latest
> upstream version, however, that version also adds some new dependencies that
> would need to be packaged and pass NEW. For example,
Source: rust-gstreamer
Version: 0.14.5-2
Severity: grave
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu groovy
The librust-gstreamer+futures-dev package is uninstallable because it
depends on librust-futures-core-preview-0.3+default-dev, which does not
exist anywhere in Debian,
On Fri, Aug 30, 2019 at 07:29:10AM +, Matthias Klose wrote:
> Package: src:olefile
> Version: 0.46-1
> Severity: normal
> Tags: sid bullseye
> User: debian-pyt...@lists.debian.org
> Usertags: py2removal
>
> Python2 becomes end-of-live upstream, and Debian aims to remove
> Python2 from the
On Sun, Aug 02, 2020 at 06:24:44PM +0300, Ilias Tsitsimpis wrote:
> Control: severity -1 serious
>
> On Sun, Jul 26, 2020 at 01:21PM, Moritz Mühlenhoff wrote:
> > Nine months later there's no progress, let's remove?
>
> Agreed.
>
> Raising the severity to serious to remove from testing, and
Source: barman
Version: 2.10-2
Severity: serious
Control: close -1 2.11-1
Tags: sid bullseye pending
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between testing and
Source: libhinawa
Version: 1.4.5-1
Severity: serious
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 968026
Control: affects -1 src:hinawa-utils
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
Processing control commands:
> block -1 by 968026
Bug #970101 [src:libhinawa] src:libhinawa: fails to migrate to testing for too
long: reverse-dependency not ready yet
970101 was not blocked by any bugs.
970101 was not blocking any bugs.
Added blocking bug(s) of 970101: 968026
> affects -1
Processing control commands:
> close -1 2.11-1
Bug #970102 [src:barman] src:barman: fails to migrate to testing for too long:
maintainer built arch:all binaries
Marked as fixed in versions barman/2.11-1.
Bug #970102 [src:barman] src:barman: fails to migrate to testing for too long:
maintainer
Processing control commands:
> close -1 2.34.0+ds-3.1
Bug #970100 [src:angelscript] src:angelscript: fails to migrate to testing for
too long: FTBFS on mips64el
Marked as fixed in versions angelscript/2.34.0+ds-3.1.
Bug #970100 [src:angelscript] src:angelscript: fails to migrate to testing for
Source: angelscript
Version: 2.34.0+ds-1.1
Severity: serious
Control: close -1 2.34.0+ds-3.1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-sync between
Control: tag -1 pending
Hello,
Bug #969879 in wifite reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Processing control commands:
> tag -1 pending
Bug #969841 [src:mac-robber] mac-robber: autopkgtest should be marked
superficial
Added tag(s) pending.
--
969841: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969841
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tag -1 pending
Bug #969844 [src:memdump] memdump: autopkgtest should be marked superficial
Added tag(s) pending.
--
969844: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tag -1 pending
Bug #969879 [src:wifite] wifite: autopkgtest should be marked superficial
Added tag(s) pending.
--
969879: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969879
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tag -1 pending
Bug #969824 [src:ext3grep] ext3grep: autopkgtest should be marked superficial
Added tag(s) pending.
--
969824: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969824
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing control commands:
> tag -1 pending
Bug #969869 [src:steghide] steghide: autopkgtest should be marked superficial
Added tag(s) pending.
--
969869: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969869
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #969869 in steghide reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #969844 in memdump reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #969824 in ext3grep reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #969841 in mac-robber reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Processing control commands:
> tag -1 pending
Bug #969875 [src:vinetto] vinetto: autopkgtest should be marked superficial
Added tag(s) pending.
--
969875: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969875
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Hi Craig,
On 11-09-2020 12:03, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:nanook package:
>
> #969493: src:nanook: fails to migrate to testing for too long: maintainer
> built arch:all binaries
>
> It has
Control: tag -1 pending
Hello,
Bug #969875 in vinetto reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Control: tag -1 pending
Hello,
Bug #969820 in dnsenum reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Processing control commands:
> tag -1 pending
Bug #969820 [src:dnsenum] dnsenum: autopkgtest should be marked superficial
Added tag(s) pending.
--
969820: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969820
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Dear Maintainer, hello Bruce Momjian,
with the last informations the issue is perfectly reproducible.
It looks like a use after free caused by statically stored
function pointers in libengine-pkcs11-openssl / libp11.
That led to following upstream bug:
Processing commands for cont...@bugs.debian.org:
> forwarded 969559 https://github.com/OpenSC/libp11/issues/328
Bug #969559 [libengine-pkcs11-openssl] curl segmentation fauls on any https URL
Set Bug forwarded-to-address to 'https://github.com/OpenSC/libp11/issues/328'.
> tags 969559 + patch
Processing commands for cont...@bugs.debian.org:
> reassign 969559 libengine-pkcs11-openssl 0.4.9-4
Bug #969559 [curl] curl segmentation fauls on any https URL
Bug reassigned from package 'curl' to 'libengine-pkcs11-openssl'.
No longer marked as found in versions curl/7.64.0-4+deb10u1.
Ignoring
Source: nat-rtsp
Version: 0.7+4.18-0.1
Followup-For: Bug #955488
I've been hit by this bug (trying to use it with the
kernel 5.7.0-0.bpo.2-amd64).
My workaround has been to manually apply the patch from
https://github.com/openwrt/packages/pull/11468
Regards,
Vincent
-- System Information:
Sylvestre Ledru wrote:
> emscripten developers implemented fastcomp, a LLVM backend. This
> requires a patched version of LLVM and this could not go in Debian
> packages.
fastcomb is no longer default backend since emscripten v1.39.0:
> v1.39.0: 10/18/2019
> ---
> - The emsdk
Hello,
I have attempted patching out dependencies in Gemfile, namely, rails and
roadie-rails, to accept later major releases. However, I ran into the
following autopkgtest failures.
First of all, 'service apache2 restart' fails in autopkgtest on schroot.
It tries to execute 'systemctl', which
Hi,
On Sat, 13 Jun 2020 12:13:59 +0200 Xavier Brochard
wrote:
snip
> xfilter_bayes_db_init: opening db: /home/anne/.sylfilter/junk.db
>
> ** (process:21314): WARNING **: 12:04:05.137: Cannot open database:
> /home/anne/.sylfilter/junk.db
> Database initialization error.
I've tried to check
Control: tags -1 + patch
this is the last package preventing migration of python-defaults to testing.
Uploading that fix to the delayed queue.
diff -Nru android-platform-build-8.1.0+r23/debian/changelog android-platform-build-8.1.0+r23/debian/changelog
---
Processing control commands:
> tags -1 + patch
Bug #970086 [src:android-platform-build] Unversioned Python removal in
sid/bullseye
Added tag(s) patch.
--
970086: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=970086
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: src:android-platform-build
Version: 1:8.1.0+r23-4
Severity: serious
Tags: sid bullseye
User: debian-pyt...@lists.debian.org
Usertags: py2unversioned
Python2 becomes end-of-live upstream, and Debian aims to remove
Python2 from the distribution, as discussed in
duplicate
Bug #969889
linux-image-5.8.0-1-amd64: fails to load kernel modules, X does not work
Reverting to:
linux-image-5.7.0-3-amd64 works
http://deb.debian.org/debian/ unstable non-free contrib main
nvidia graphics
Lars
Your message dated Fri, 11 Sep 2020 10:04:20 +
with message-id
and subject line Bug#966521: fixed in gnome-remote-desktop 0.1.9-2
has caused the Debian Bug report #966521,
regarding gnome-remote-desktop: to have g-r-d working with Gnome 3.36, you need
to have g-r-d >= 0.1.8
to be marked as
Your message dated Fri, 11 Sep 2020 10:00:21 +
with message-id
and subject line Bug#959643: fixed in pbbam 1.3.0+dfsg-1
has caused the Debian Bug report #959643,
regarding pbbam: FTBFS: ../tests/src/test_BamWriter.cpp:40:34: error: call of
overloaded ‘CigarData(const char [1])’ is ambiguous
Your message dated Fri, 11 Sep 2020 10:00:21 +
with message-id
and subject line Bug#959643: fixed in pbbam 1.3.0+dfsg-1
has caused the Debian Bug report #959643,
regarding blasr: FTBFS: unsatisfiable build-dependencies: libpbcopper1.3.0 (>=
1.3.0+dfsg), libpbcopper1.3.0 (>= 1.3.0+dfsg)
to be
Your message dated Fri, 11 Sep 2020 10:00:21 +
with message-id
and subject line Bug#959643: fixed in pbbam 1.3.0+dfsg-1
has caused the Debian Bug report #959643,
regarding pbseqlib: FTBFS: libpbcopper1.6.0 : Breaks: libpbcopper1.3.0 (>= 1.6)
but 1.6.0+dfsg-1 is to be installed
to be marked
Your message dated Fri, 11 Sep 2020 10:00:18 +
with message-id
and subject line Bug#969493: fixed in net-snmp 5.9+dfsg-2
has caused the Debian Bug report #969493,
regarding src:nanook: fails to migrate to testing for too long: maintainer
built arch:all binaries
to be marked as done.
This
Your message dated Fri, 11 Sep 2020 09:34:51 +
with message-id
and subject line Bug#969753: fixed in diffoscope 160
has caused the Debian Bug report #969753,
regarding diffoscope: autopkgtest failures
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:
> forwarded 963444 https://github.com/w3c/epubcheck/issues/1185
Bug #963444 [src:epubcheck] epubcheck: FTBFS: [ERROR]
/<>/src/main/java/com/adobe/epubcheck/opf/ValidationContext.java:[267,7]
is not
abstract and does not override abstract method
Hi Pebs,
Thanks for checking this.
On Sat, 5 Sep 2020 23:23:30 +0200 Pierre-Elliott =?utf-8?B?QsOpY3Vl?=
wrote:>
> LXC's devs told me that 4.0.4 should solve it. I'm uploading this
> release now. Please don't hesitate to tell me if it helps.
Run a pipeline removing the pinning of lxc, and the
Processing commands for cont...@bugs.debian.org:
> affects 970036 src:cloudcompare src:paraview
Bug #970036 [libopenmpi-dev] libopenmpi-dev fails to install
Added indication that 970036 affects src:cloudcompare and src:paraview
> thanks
Stopping processing here.
Please contact me if you need
Processing control commands:
> tag -1 pending
Bug #969753 [src:diffoscope] diffoscope: autopkgtest failures
Added tag(s) pending.
--
969753: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969753
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #969753 in diffoscope reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:
Processing commands for cont...@bugs.debian.org:
> reopen 963444
Bug #963444 {Done: Mathieu Malaterre } [src:epubcheck]
epubcheck: FTBFS: [ERROR]
/<>/src/main/java/com/adobe/epubcheck/opf/ValidationContext.java:[267,7]
is not
abstract and does not override abstract method
Package: cfengine3
Followup-For: Bug #963341
Hi,
just a friendly ping that
https://salsa.debian.org/cfengine-team/cfengine3/-/merge_requests/2
fixes this (admittely also includes not strictly needed changes, tho).
Ciao,
Gian Piero.
-- System Information:
Debian Release: bullseye/sid
APT
Package: ppp
Version: 2.4.7-2+4.1+deb10u1+b1
Severity: grave
In https://github.com/paulusmack/ppp/issues/167
> "PM" == Paul Mackerras writes:
PM> It seems like the debian packaging of pppd has not been updated to use
PM> whatever the "correct" way to supply new DNS servers to
PM>
Your message dated Fri, 11 Sep 2020 06:48:25 +
with message-id
and subject line Bug#963444: fixed in epubcheck 4.2.4-1
has caused the Debian Bug report #963444,
regarding epubcheck: FTBFS: [ERROR]
/<>/src/main/java/com/adobe/epubcheck/opf/ValidationContext.java:[267,7]
is not
abstract and
Package: cyrus-common
Version: 3.2.3-1
Followup-For: Bug #969261
Hello,
The file /usr/lib/tmpfile.d/cyrus-imapd.conf isn't installed anymore.
Cyrus can't start without the dirs /run/cyrus and /run/cyrus/socket
created by systemd tmpfile mechanism.
73 matches
Mail list logo
