Your message dated Tue, 06 Oct 2020 06:48:27 +
with message-id
and subject line Bug#965007: fixed in pitivi 2020.09-1
has caused the Debian Bug report #965007,
regarding pitivi: ships a copy of gstreamer libraries
to be marked as done.
This means that you claim that the problem has been dealt
Processing control commands:
> tags -1 upstream
Bug #971681 [r-cran-openmx] r-cran-openmx regression on arm, will not migrate
to testing due to failing autopkgtests
Added tag(s) upstream.
> tags -1 help
Bug #971681 [r-cran-openmx] r-cran-openmx regression on arm, will not migrate
to testing due
Control: tags -1 upstream
Control: tags -1 help
Control: forwarded -1 Joshua N. Pritikin
Hi Joshua,
the version 2.18.1 of the openmx CRAN package that was build for Debian
shows a test suite error on arm64 architecture. Here is an extract of
the full test log[1] (if you want to inspect the full
Hi,
the build on mipsel[1] failed with
g++ -std=gnu++14 -I"/usr/share/R/include" -DNDEBUG -I"../inst/include"
-I"../inst/include/boost_not_in_BH" -I"." -DBOOST_DISABLE_ASSERTS
-DBOOST_PHOENIX_NO_VARIADIC_EXPRESSION -DBOOST_NO_AUTO_PTR -D_REENTRANT
-DSTAN_THREADS -I'/usr/lib/R/site-library/R
It turns out there was already an RM bug filed:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969975
I will merge the duplicate I created into it:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971730
On Mon, Oct 05, 2020 at 06:30:51AM +0200, Sebastiaan Couwenberg wrote:
> On 10/5/20 6:04 AM, tony mancill wrote:
> > On Sun, Oct 04, 2020 at 04:34:17PM +0200, Sebastiaan Couwenberg wrote:
> >> Control: severity -1 serious
> >> Control: affects -1 src:openjfx
> >>
> >> This issue is preventing testi
Package: malcontent-gui
Version: 0.9.0-1
Severity: grave
Tags: patch
Justification: renders package unusable
X-Debbugs-Cc: die...@gnome.org
Hi, it seems that there's a missing .policy file in the .install file
for `malcontent-gui`, specifically:
`usr/share/polkit-1/actions/org.freedesktop.Malcon
Processing control commands:
> tags 956970 + patch
Bug #956970 [src:4g8] 4g8: ftbfs with GCC-10
Added tag(s) patch.
> tags 956970 + pending
Bug #956970 [src:4g8] 4g8: ftbfs with GCC-10
Added tag(s) pending.
--
956970: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=956970
Debian Bug Tracking S
Control: tags 956970 + patch
Control: tags 956970 + pending
Dear maintainer,
I've prepared an NMU for 4g8 (versioned as 1.0-3.3) and
uploaded it to DELAYED/15. Please feel free to tell me if I
should delay it longer.
Regards.
diff -u 4g8-1.0/debian/changelog 4g8-1.0/debian/changelog
--- 4g8-1.
Processing control commands:
> tags 957999 + patch
Bug #957999 [src:xsd] xsd: ftbfs with GCC-10
Added tag(s) patch.
> tags 957999 + pending
Bug #957999 [src:xsd] xsd: ftbfs with GCC-10
Added tag(s) pending.
--
957999: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=957999
Debian Bug Tracking S
Control: tags 957999 + patch
Control: tags 957999 + pending
Dear maintainer,
I've prepared an NMU for xsd (versioned as 4.0.0-8.1) and
uploaded it to DELAYED/15. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru xsd-4.0.0/debian/changelog xsd-4.0.0/debian/changelog
--
Control: tags 958004 + patch
Control: tags 958004 + pending
Dear maintainer,
I've prepared an NMU for xtron (versioned as 1.1a-14.1) and
uploaded it to DELAYED/15. Please feel free to tell me if I
should delay it longer.
Regards.
diff -u xtron-1.1a/debian/changelog xtron-1.1a/debian/changelog
Processing control commands:
> tags 958004 + patch
Bug #958004 [src:xtron] xtron: ftbfs with GCC-10
Ignoring request to alter tags of bug #958004 to the same tags previously set
> tags 958004 + pending
Bug #958004 [src:xtron] xtron: ftbfs with GCC-10
Added tag(s) pending.
--
958004: https://bugs
Processing control commands:
> tags 958012 + patch
Bug #958012 [src:ziproxy] ziproxy: ftbfs with GCC-10
Added tag(s) patch.
> tags 958012 + pending
Bug #958012 [src:ziproxy] ziproxy: ftbfs with GCC-10
Added tag(s) pending.
--
958012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958012
Debia
Control: tags 958012 + patch
Control: tags 958012 + pending
Dear maintainer,
I've prepared an NMU for ziproxy (versioned as 3.3.1-2.2) and
uploaded it to DELAYED/15. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru ziproxy-3.3.1/debian/changelog ziproxy-3.3.1/debian/
Control: tags 958011 + patch
Control: tags 958011 + pending
Dear maintainer,
I've prepared an NMU for yersinia (versioned as 0.8.2-2.1) and
uploaded it to DELAYED/15. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru yersinia-0.8.2/debian/changelog yersinia-0.8.2/debi
Processing control commands:
> tags 958011 + patch
Bug #958011 [src:yersinia] yersinia: ftbfs with GCC-10
Added tag(s) patch.
> tags 958011 + pending
Bug #958011 [src:yersinia] yersinia: ftbfs with GCC-10
Added tag(s) pending.
--
958011: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=958011
D
Your message dated Mon, 05 Oct 2020 23:03:25 +
with message-id
and subject line Bug#957824: fixed in snoopy 2.4.8-1
has caused the Debian Bug report #957824,
regarding snoopy: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is no
On 2020-10-05 15:35:23 +0200, Gianfranco Costamagna wrote:
> In this case, the symbols were private, and incorrectly exposed
> outside, so removing them is "safe" as long as nobody uses them.
I've looked at the repository, and in more details, they were
incorrectly exposed outside via the symbol t
Your message dated Mon, 05 Oct 2020 22:50:36 +
with message-id
and subject line Bug#971234: fixed in ruby-bson 4.10.0-2
has caused the Debian Bug report #971234,
regarding src:ruby-bson: fails to migrate to testing for too long: FTBFS on
s390x
to be marked as done.
This means that you claim
Processing control commands:
> tag -1 pending
Bug #971234 [src:ruby-bson] src:ruby-bson: fails to migrate to testing for too
long: FTBFS on s390x
Added tag(s) pending.
--
971234: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=971234
Debian Bug Tracking System
Contact ow...@bugs.debian.org wi
Control: tag -1 pending
Hello,
Bug #971234 in ruby-bson 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:
https://salsa.debian.org/ruby-team/ruby-bson/-/commit/67106212bc90679d35c25e9e67e
Processing commands for cont...@bugs.debian.org:
> tags 958620 + pending
Bug #958620 [src:sanlock] sanlock: Build-Depends on deprecated dh-systemd which
is going away
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
958620: https://bugs.debia
Dmitry Shachnev writes:
> I would be happy to update the packaging to the latest upstream
> release (1.1) and upload it, if the maintainer (Brian) wants so.
That is good with me.
Thanks.
--
Brian May
On Mon, Oct 05, 2020 at 07:53:05AM +0100, Julian Gilbey wrote:
> On Mon, Oct 05, 2020 at 12:57:59AM +0100, Julian Gilbey wrote:
> > 4) The output of "greylist list" is now somewhat mangled: the "Data"
> > field shows something like:
> > [ ' 1 . 2 . 3 . 4 / 2 4 ' , ' i n f o @ e x a m p l e . c o
Package: mime-support
Version: 3.64
Severity: serious
On Mon, Oct 05, 2020 at 09:09:01AM +0200, Adam Borowski wrote:
> On Mon, Oct 05, 2020 at 01:52:19PM +1000, Jai Flack wrote:
> > Forgive me if this is an ignorant question but isn't mailcap missing
> > dependencies? If I build, then install all
Processing control commands:
> close -1 0.18.0-1
Bug #971717 [src:rust-sequoia-openpgp] src:rust-sequoia-openpgp: fails to
migrate to testing for too long: unsatisfied B-D
The source 'rust-sequoia-openpgp' and version '0.18.0-1' do not appear to match
any binary packages
Marked as fixed in versi
Source: rust-sequoia-openpgp
Version: 0.17.0-5
Severity: serious
Control: close -1 0.18.0-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 971099
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
Source: rust-sequoia-sqv
Version: 0.17.0-1
Severity: serious
Control: close -1 0.18.0-2
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 971103
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are
Processing control commands:
> close -1 0.18.0-2
Bug #971715 [src:rust-sequoia-sqv] src:rust-sequoia-sqv: fails to migrate to
testing for too long: unsatisfied B-D
The source 'rust-sequoia-sqv' and version '0.18.0-2' do not appear to match any
binary packages
Marked as fixed in versions rust-seq
Processing control commands:
> close -1 0.18.0-1
Bug #971716 [src:rust-sequoia-sop] src:rust-sequoia-sop: fails to migrate to
testing for too long: unsatisfied B-D
The source 'rust-sequoia-sop' and version '0.18.0-1' do not appear to match any
binary packages
Marked as fixed in versions rust-seq
Source: rust-sequoia-sop
Version: 0.17.0-2
Severity: serious
Control: close -1 0.18.0-1
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 971105
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are
Processing control commands:
> close -1 1.19.0-2
Bug #971714 [src:libiscsi] src:libiscsi: fails to migrate to testing for too
long: FTBFS
The source 'libiscsi' and version '1.19.0-2' do not appear to match any binary
packages
Marked as fixed in versions libiscsi/1.19.0-2.
Bug #971714 [src:libisc
Source: libiscsi
Version: 1.19.0-1
Severity: serious
Control: close -1 1.19.0-2
Tags: sid bullseye
User: release.debian@packages.debian.org
Usertags: out-of-sync
Control: block -1 by 969074
Dear maintainer(s),
As recently announced [1], the Release Team now considers packages that
are out-of-
Hi,
On Sun, Oct 04, 2020 at 11:56:56AM -0300, Antonio Terceiro wrote:
> Dear Maintainer,
>
> the current version of mkdocs-bootstrap in the archive is broken and
> does not work with the version of mkdocs that we have.
Yes, unfortunately it is probably also broken in stable. Let's fix it at least
On 2020-10-05 11:51:59 +0200, Matthias Klose wrote:
> On 9/30/20 12:38 AM, Sebastian Ramacher wrote:
> > On 2020-09-30 00:01:52 +0200, Ahzo wrote:
> >>
> >> Sep 29, 2020, 07:14 by rguent...@suse.de:
> >>
> >>> I've filed > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97236
> >>>
> >>> Someone needs
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:snoopy
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Sett
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:python-tornado
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.
Processing commands for cont...@bugs.debian.org:
> #
> # bts-link upstream status pull for source package src:otb
> # see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
> # https://bts-link-team.pages.debian.net/bts-link/
> #
> user debian-bts-l...@lists.debian.org
Setting
i checked this in devuan (it lacks of systemd) and does work..but not on debian
root@venenux:~# service courier-imap-ssl status
● courier-imap-ssl.service - LSB: Courier IMAP server (TLS)
Loaded: loaded (/etc/init.d/courier-imap-ssl; generated)
Active: active (exited) since Mon 2020-10-05 15
Processing commands for cont...@bugs.debian.org:
> block 963628 with 887167
Bug #963628 [node-jest] Node-jest fails with: Error: Cannot find module
'import-local'
963628 was not blocked by any bugs.
963628 was not blocking any bugs.
Added blocking bug(s) of 963628: 887167
> thanks
Stopping proces
Your message dated Mon, 05 Oct 2020 15:21:05 +
with message-id
and subject line Bug#920545: fixed in python-intervaltree-bio 1.0.1-4
has caused the Debian Bug report #920545,
regarding python-intervaltree breaks python-intervaltree-bio autopkgtest
to be marked as done.
This means that you cla
Package: uwsgi-emperor
Version: 2.0.19.1-3
Followup-For: Bug #969372
Dear Maintainer,
it seems this bug still exists in 2.0.19.1-3.
I've upgraded from 2.0.19.1-1 this morning and since then the
uwsgi-emperor can't be started using systemd or
/etc/init.d/uwsgi-emperor script. I tried to purge and
Source: golang-github-knadh-koanf
Version: 0.10.0-1
Severity: serious
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu groovy
Dear maintainers,
The golang-github-knadh-koanf package cannot be built in Debian due to
missing build-dependency, golang-github-rhnvrm-simples3-dev:
$ sudo ap
Your message dated Mon, 5 Oct 2020 15:46:16 +0200
with message-id <158b483f-0235-ac8b-6a0c-4f9878e3c...@debian.org>
and subject line Re: Bug#971668: libsane: broke ABI
has caused the Debian Bug report #971668,
regarding libsane: broke ABI
to be marked as done.
This means that you claim that the pr
Processing control commands:
> severity -1 serious
Bug #970589 [tracker-extract] tracker-extract: Crashes due to statx SIGABRT
causes disk full ( need update to 2.3.5 )
Severity set to 'serious' from 'normal'
> tags -1 + fixed-upstream patch bullseye sid
Bug #970589 [tracker-extract] tracker-extr
Hello Joerg,
> We are not back.
to be honest, yes we are :)
>
> Between 1.0.30 and 1.0.31 are the following 7 symbols are not longer
> available:
>
> #MISSING: 1.0.31# testing_append_commands_node@Base 1.0.29
> #MISSING: 1.0.31# testing_known_commands_input_failed@Base 1.0.29
> #MISSING: 1.0.
Hi,
I've attempted to fix: #920545 which is about failing autopkgtests for
python-intervaltree-bio. It seems to pass on my chroot and I've pushed the
corresponding changes to the team repo here[1].
It'd be great if someone could try testing my changes once - and either
sponsor or grant me access to
Processing control commands:
> severity -1 important
Bug #971687 [libsane1] libsane1: broke ABI
Severity set to 'important' from 'grave'
> reassign -1 src:sane-backends
Bug #971687 [libsane1] libsane1: broke ABI
Bug reassigned from package 'libsane1' to 'src:sane-backends'.
No longer marked as fou
control: severity -1 important
control: reassign -1 src:sane-backends
control: retitle -1 sane-backends: dropped unused symbols without changing
SONAME
Hello Vincent and Sebastian
On Mon, 5 Oct 2020 03:48:26 +0200 Vincent Lefevre wrote:
> Control: clone -1 -2
> Control: reassign -2 libsane1 1
Control: tags -1 + patch
On Mon, 05 Oct 2020 at 12:23:19 +0100, Simon McVittie wrote:
> > > | grep:
> > > debian/libgs9-common/usr/share/ghostscript/9.53.3/Resource/Init/cidfmap:
> > > No such file or directory
> > > | rm: cannot remove
> > > 'debian/libgs9-common/usr/share/ghostscript/9.53.3/R
Processing control commands:
> tags -1 + patch
Bug #971678 [src:ghostscript] ghostscript: FTBFS when not building Arch:all:
debian/libgs9-common/usr/share/ghostscript/9.53.3/Resource/Init/cidfmap: No
such file or directory
Added tag(s) patch.
--
971678: https://bugs.debian.org/cgi-bin/bugrepor
Processing control commands:
> tags -1 fixed-upstream
Bug #908137 [src:luajit] luajit: lightuserdata problem with > 47 bit address
space on arm64
Added tag(s) fixed-upstream.
--
908137: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908137
Debian Bug Tracking System
Contact ow...@bugs.debian
Control: tags -1 fixed-upstream
On Thu, 06 Sep 2018 16:54:30 +0300 Adrian Bunk wrote:
> Source: luajit
> Version: 2.0.4+dfsg-1
> Severity: serious
> Forwarded: https://github.com/LuaJIT/LuaJIT/pull/230#issuecomment-260205661
>
> This is an RFC regarding what to do for avoiding runtime
> problems
On Mon, 05 Oct 2020 at 10:56:17 +0100, Simon McVittie wrote:
> Control: retitle 971678 ghostscript: FTBFS when not building Arch:all:
> debian/libgs9-common/usr/share/ghostscript/9.53.3/Resource/Init/cidfmap: No
> such file or directory
>
> On Sun, 04 Oct 2020 at 22:55:24 +0200, Sebastian Ramach
Processing control commands:
> retitle 971678 ghostscript: FTBFS when not building Arch:all:
> debian/libgs9-common/usr/share/ghostscript/9.53.3/Resource/Init/cidfmap: No
> such file or directory
Bug #971678 [src:ghostscript] ghostscript: FTBFS: ERROR: cidfmap not virtually
empty as expected
Ch
Control: retitle 971678 ghostscript: FTBFS when not building Arch:all:
debian/libgs9-common/usr/share/ghostscript/9.53.3/Resource/Init/cidfmap: No
such file or directory
On Sun, 04 Oct 2020 at 22:55:24 +0200, Sebastian Ramacher wrote:
> ghostscript currently FTBFS on the buildds:
> | grep:
> de
On 9/30/20 12:38 AM, Sebastian Ramacher wrote:
> On 2020-09-30 00:01:52 +0200, Ahzo wrote:
>>
>> Sep 29, 2020, 07:14 by rguent...@suse.de:
>>
>>> I've filed > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97236
>>>
>>> Someone needs to create a testcase or provide instructions how to
>>> reproduce t
Your message dated Mon, 05 Oct 2020 08:22:28 +
with message-id
and subject line Bug#957450: fixed in libmygpo-qt 1.1.0-4
has caused the Debian Bug report #957450,
regarding libmygpo-qt: ftbfs with GCC-10
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Your message dated Mon, 05 Oct 2020 08:22:28 +
with message-id
and subject line Bug#964647: fixed in libmygpo-qt 1.1.0-4
has caused the Debian Bug report #964647,
regarding libmygpo-qt: FTBFS: dpkg-gensymbols: error: some symbols or patterns
disappeared in the symbols file: see diff output be
Processing control commands:
> retitle -1 gnome-shell-extension-pixelsaver: Fails to load on Shell 3.38: No
> JS module 'tweener' found in search path
Bug #971689 [gnome-shell-extension-pixelsaver]
gnome-shell-extension-pixelsaver: Fails with "No JS module 'tweener' found in
search path"
Change
Processing commands for cont...@bugs.debian.org:
> severity 971203 important
Bug #971203 [dpkg-dev] gap-atlasrep: FTBFS: dpkg-source: error: pathname
'/<>/debian/gaproot/pkg/AtlasRep' points outside source root (to
'/<>')
Severity set to 'important' from 'serious'
> quit
Stopping processing here
severity 971203 important
quit
> > root (to '/tmp/gap-atlasrep-2.1.0')
> > E: Unpack command 'dpkg-source --no-check -x gap-atlasrep_2.1.0-2.dsc'
> > failed.
> >
> > There is no rationale to reject such a symlink which does not point
> > _outside_ the source root, but _to_ the source root.
> > Th
Your message dated Mon, 05 Oct 2020 07:49:05 +
with message-id
and subject line Bug#969616: fixed in rust-tui 0.8.0-3
has caused the Debian Bug report #969616,
regarding rust-tui builds 5 uninstallable packages
to be marked as done.
This means that you claim that the problem has been dealt wi
64 matches
Mail list logo
