Control: tag -1 pending
Hello,
Bug #949926 in mlpost 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 #949926 [src:mlpost] FTBFS with bitstring 3.1.1
Added tag(s) pending.
--
949926: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=949926
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Package: src:python-virustotal-api
Version: 1.1.11-2
Severity: serious
Tags: sid bullseye
the autodep8 test fails, because the package is wrongly named. The package name
should be python-virustotal-apis? Or you remove the autodep8 test from
debian/control.
Setting up autopkgtest-satdep (0) ...
Your message dated Thu, 30 Jan 2020 07:04:49 +
with message-id
and subject line Bug#949351: fixed in efl 1.23.3-6
has caused the Debian Bug report #949351,
regarding efl FTBFS: missing dependency on libx11-xcb-dev
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 30 Jan 2020 06:51:05 +
with message-id
and subject line Bug#950158: Removed package(s) from unstable
has caused the Debian Bug report #937023,
regarding mgltools-geomutils: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the
Your message dated Thu, 30 Jan 2020 06:51:26 +
with message-id
and subject line Bug#950157: Removed package(s) from unstable
has caused the Debian Bug report #937019,
regarding mgltools-bhtree: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 30 Jan 2020 06:50:44 +
with message-id
and subject line Bug#950159: Removed package(s) from unstable
has caused the Debian Bug report #937028,
regarding mgltools-opengltk: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
Your message dated Thu, 30 Jan 2020 06:50:06 +
with message-id
and subject line Bug#950191: Removed package(s) from unstable
has caused the Debian Bug report #885505,
regarding yorick-spydr: Depends on unmaintained pygtk
to be marked as done.
This means that you claim that the problem has
Your message dated Thu, 30 Jan 2020 06:49:45 +
with message-id
and subject line Bug#950193: Removed package(s) from unstable
has caused the Debian Bug report #936893,
regarding libmimic: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Thu, 30 Jan 2020 06:50:24 +
with message-id
and subject line Bug#950160: Removed package(s) from unstable
has caused the Debian Bug report #937032,
regarding mgltools-pyglf: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
Package: src:python-crontab
Version: 1.9.3-3
Severity: serious
Tags: sid bullseye patch
autopkg test still depends on python. patch at
http://launchpadlibrarian.net/462714698/python-crontab_1.9.3-3_1.9.3-3ubuntu1.diff.gz
> > koji is keeping createrepo in the archive, which keeps python-lzma in
> > the archive.
>
> there's also mock, yum, rpm, deltarpm and yum-metadata-parser affected by
> this.
yep i came across all of them starting from python-lzma -- do you know
what's the status of the "RedHat infrastructure"
Your message dated Thu, 30 Jan 2020 05:51:16 +
with message-id
and subject line Bug#943389: fixed in node-lodash 4.17.15+dfsg-2
has caused the Debian Bug report #943389,
regarding node-lodash: source package does not contain upstream source
to be marked as done.
This means that you claim
Your message dated Thu, 30 Jan 2020 05:51:16 +
with message-id
and subject line Bug#935845: fixed in node-lodash 4.17.15+dfsg-2
has caused the Debian Bug report #935845,
regarding node-lodash: node-lodash._createRound calls deprecated root object
to be marked as done.
This means that you
Processing control commands:
> tag -1 pending
Bug #935845 [node-lodash] node-lodash: node-lodash._createRound calls
deprecated root object
Added tag(s) pending.
--
935845: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=935845
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Processing control commands:
> tag -1 pending
Bug #943389 [node-lodash] node-lodash: source package does not contain upstream
source
Added tag(s) pending.
--
943389: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=943389
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #943389 in node-lodash 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 #935845 in node-lodash 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:
> forwarded 949237 https://phabricator.kde.org/D25370
Bug #949237 [src:ktp-accounts-kcm] ktp-accounts-kcm: FTBFS on various archs
Set Bug forwarded-to-address to 'https://phabricator.kde.org/D25370'.
> tags 949237 patch fixed-upstream
Bug #949237
Control: forwarded 949237 https://phabricator.kde.org/D25370
Control: tags 949237 patch fixed-upstream
This was caused by the new telepathy-qt and the patch suffices for it to build
on my system. #949239 in ktp-contacts-runner looks to be the same issue, but
its git log is much less
Processing control commands:
> forwarded 949237 https://phabricator.kde.org/D25370
Bug #949237 [src:ktp-accounts-kcm] ktp-accounts-kcm: FTBFS on various archs
Ignoring request to change the forwarded-to-address of bug#949237 to the same
value
> tags 949237 patch fixed-upstream
Bug #949237
Your message dated Thu, 30 Jan 2020 01:37:00 +
with message-id
and subject line Bug#945344: fixed in uim 1:1.8.8-6.1
has caused the Debian Bug report #945344,
regarding libuim-data: registers unusable "tutcode" module
to be marked as done.
This means that you claim that the problem has been
Processing commands for cont...@bugs.debian.org:
> found 943584 1.7.0-2
Bug #943584 {Done: Debian FTP Masters }
[xul-ext-dispmua] xul-ext-dispmua: AddOn does not work with Thunderbird 68.x
Marked as found in versions dispmua/1.7.0-2.
> found 950141 201909.1-1
Bug #950141 {Done: Debian FTP
Your message dated Thu, 30 Jan 2020 00:21:09 +
with message-id
and subject line Bug#937169: fixed in nut 2.7.4-12
has caused the Debian Bug report #937169,
regarding nut: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt with.
If
Il giorno mer 29 gen 2020 alle ore 23:34 Michael Biebl
ha scritto:
> Controls: reassign -1 gvfs-daemons 1.42.2-1
> Control: retitle -1 missing schema files makes udisks monitor crash
> Control: severity -1 serious
>
> Am 29.01.20 um 23:27 schrieb Michael Biebl:
> > Am 29.01.20 um 23:26 schrieb
Processing control commands:
> retitle -1 missing schema files makes udisks monitor crash
Bug #950174 [udisks2] udisks2: when I start some application, like gedit, I
wait 30 seconds, to open.
Bug #950173 [udisks2] udisks2: when I start some application, like gedit, I
wait 30 seconds, to open.
Processing commands for cont...@bugs.debian.org:
> forwarded 947998 https://github.com/theupdateframework/notary/issues/1527
Bug #947998 [src:notary] notary FTBFS in testing/unstable
Set Bug forwarded-to-address to
'https://github.com/theupdateframework/notary/issues/1527'.
> thanks
Stopping
Processing commands for cont...@bugs.debian.org:
> affects 947998 src:docker.io src:gitlab-ci-multi-runner
> src:golang-github-containers-buildah src:golang-github-containers-image
> src:golang-github-fsouza-go-dockerclient src:singularity-container
Bug #947998 [src:notary] notary FTBFS in
Processing commands for cont...@bugs.debian.org:
> tags 947998 + upstream help
Bug #947998 [src:notary] notary FTBFS in testing/unstable
Added tag(s) help and upstream.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
947998:
On Wed, Jan 29, 2020 at 10:16:58AM +0100, Thibaut Paumard wrote:
>
> > Did you hear anything back? Shall we remove it?
> >
>
> Yes, we should remove it. Can you fill the request? I won't have time
> before next week.
Done, I also CCed you.
Cheers,
Moritz
Your message dated Wed, 29 Jan 2020 21:52:09 +
with message-id
and subject line Bug#950087: fixed in statsmodels 0.10.2-2
has caused the Debian Bug report #950087,
regarding statsmodels: FTBFS with new ipython
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 29 Jan 2020 20:53:56 +
with message-id
and subject line Bug#950128: fixed in nvidia-graphics-drivers 440.44-2
has caused the Debian Bug report #950128,
regarding nvidia-graphics-drivers: Error! Bad return status for module build on
kernel: 5.4.0-3-amd64 (x86_64)
to be
Processing commands for cont...@bugs.debian.org:
> found 950176 3.1.9-1
Bug #950176 [src:source-highlight] source-highlight: FTBFS on all architectures
other than amd64
Marked as found in versions source-highlight/3.1.9-1.
> found 950177 3.1.9-1
Bug #950177 [src:source-highlight]
Control: reassign -1 src:source-highlight
X-Debbugs-CC: kartik.koo...@gmail.com
Sorry for reporting the bug against the wrong package name. Re-assigning the
report accordingly.
--
Thanks,
Boyuan Yang
signature.asc
Description: This is a digitally signed message part
Control: reassign -1 src:source-highlight
X-Debbugs-CC: kartik.koo...@gmail.com
Sorry for reporting the bug with a wrong package name. Re-assigning the bug
report accordingly.
--
Thanks,
Boyuan Yang
signature.asc
Description: This is a digitally signed message part
Processing control commands:
> reassign -1 src:source-highlight
Bug #950176 [src:source-hightlight] source-highlight: FTBFS on all
architectures other than amd64
Warning: Unknown package 'src:source-hightlight'
Bug reassigned from package 'src:source-hightlight' to 'src:source-highlight'.
No
Processing control commands:
> reassign -1 src:source-highlight
Bug #950177 [src:source-hightlight] source-highlight: FTBFS: make test fails
Warning: Unknown package 'src:source-hightlight'
Bug reassigned from package 'src:source-hightlight' to 'src:source-highlight'.
No longer marked as found in
Source: source-hightlight
Version: 3.1.9-1
Severity: grave
Dear source-highlight maintainer,
Currently source-highlight would FTBFS due to errors when running "make test"
after build:
https://buildd.debian.org/status/fetch.php?pkg=source-highlight=arm64=3.1.9-1=1579812231=0
There are
Source: source-hightlight
Version: 3.1.9-1
Severity: grave
Tags: patch
Dear source-highlight maintainer,
There is an error currently lying in the debian/rules file that prevents the
package from being built successfully on all architectures other than amd64:
Your message dated Wed, 29 Jan 2020 19:32:33 +
with message-id
and subject line Bug#943584: fixed in dispmua 1.8.4.6-1~deb9u1
has caused the Debian Bug report #943584,
regarding xul-ext-dispmua: AddOn does not work with Thunderbird 68.x
to be marked as done.
This means that you claim that
I think this is fixed by
https://github.com/seebk/GIMP-Lensfun/commit/ca4511c1a4dd8edabe86e4a943861fda07b7e86c
Feel free to 0day NMU, I don't have much time right now.
On January 29, 2020 7:00:30 PM UTC, Paul Gevers wrote:
>Source: gimplensfun
>Version: 0.2.4-1
>Severity: serious
Processing control commands:
> fixed -1 nvidia-graphics-drivers/440.44-1
Bug #950128 [src:nvidia-graphics-drivers] nvidia-graphics-drivers: Error! Bad
return status for module build on kernel: 5.4.0-3-amd64 (x86_64)
Marked as fixed in versions nvidia-graphics-drivers/440.44-1.
--
950128:
Source: libextractor
Version: 1:1.9-2
Severity: serious
Justification: ftbfs
Tags: ftbfs sid bullseye
Dear maintainer,
exiv2 started a transition and I scheduled binNMUs. However, your
package failed. Please investigate.
Paul
Tail of log for libextractor on amd64:
Source: gpscorrelate
Version: 1.6.1-7
Severity: serious
Justification: ftbfs
Tags: ftbfs sid bullseye
Dear maintainer,
exiv2 started a transition and I scheduled binNMUs. However, your
package failed. Please investigate.
Paul
Tail of log for gpscorrelate on amd64:
|
Source: gimplensfun
Version: 0.2.4-1
Severity: serious
Justification: ftbfs
Tags: ftbfs sid bullseye
Dear maintainer,
exiv2 started a transition and I scheduled binNMUs. However, your
package failed. Please investigate.
Paul
Tail of log for gimplensfun on amd64:
Source: gexiv2
Version: 0.12.0-1
Severity: serious
Justification: ftbfs
Tags: ftbfs sid bullseye
Dear maintainer,
exiv2 started a transition and I scheduled binNMUs. However, your
package failed. Please investigate.
Paul
Tail of log for gexiv2 on amd64:
../gexiv2/gexiv2-metadata.cpp:184:14:
Control: fixed -1 nvidia-graphics-drivers/440.44-1
The package in experimental works.
Kind Regards,
Bas
--
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
Package: pstack
Version: 1.3.1-1+b1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I can't get pstack working as expected. Even not as root.
Example:
# pstack 2280
2280: /usr/lib/upower/upowerd
(No symbols found)
0x7fbfe723dd0f: (55babe9e5900, 51, 0, 0, 0,
Processing commands for cont...@bugs.debian.org:
> tags 939847 + ftbfs
Bug #939847 [src:haskell-stack] haskell-stack: FTBFS in sid
Added tag(s) ftbfs.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
939847: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939847
Source: uvloop
Version: 0.14.0+ds1-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/uvloop.html
...
= test session starts ==
platform linux -- Python 3.8.1, pytest-4.6.9, py-1.8.0,
Source: libdbi-drivers
Version: 0.9.0-6
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/libdbi-drivers.html
...
Running "libdbi framework test"...
test_dbi.c:3823: unit test failure: pgsql -> libdbi connection -> Retrieving
fields as
Your message dated Wed, 29 Jan 2020 18:05:08 +
with message-id
and subject line Bug#936853: fixed in libevtx 20181227-1.1
has caused the Debian Bug report #936853,
regarding libevtx: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 29 Jan 2020 18:04:51 +
with message-id
and subject line Bug#936850: fixed in libesedb 20181229-3.1
has caused the Debian Bug report #936850,
regarding libesedb: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 29 Jan 2020 18:05:32 +
with message-id
and subject line Bug#936862: fixed in libfvde 20190104-1.1
has caused the Debian Bug report #936862,
regarding libfvde: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 29 Jan 2020 18:05:47 +
with message-id
and subject line Bug#936864: fixed in libfwsi 20181227-1.1
has caused the Debian Bug report #936864,
regarding libfwsi: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 29 Jan 2020 18:06:10 +
with message-id
and subject line Bug#936897: fixed in libolecf 20181231-1.1
has caused the Debian Bug report #936897,
regarding libolecf: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 29 Jan 2020 18:05:16 +
with message-id
and subject line Bug#936858: fixed in libfsapfs 20190210-1.1
has caused the Debian Bug report #936858,
regarding libfsapfs: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 29 Jan 2020 18:06:32 +
with message-id
and subject line Bug#936915: fixed in libscca 20181227-1.1
has caused the Debian Bug report #936915,
regarding libscca: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 29 Jan 2020 18:06:47 +
with message-id
and subject line Bug#936921: fixed in libsmraw 20181227-1.1
has caused the Debian Bug report #936921,
regarding libsmraw: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 29 Jan 2020 18:07:01 +
with message-id
and subject line Bug#936936: fixed in libvmdk 20181227-1.1
has caused the Debian Bug report #936936,
regarding libvmdk: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 29 Jan 2020 18:07:33 +
with message-id
and subject line Bug#938291: fixed in pytsk 20190507-1.1
has caused the Debian Bug report #938291,
regarding pytsk: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 29 Jan 2020 18:07:11 +
with message-id
and subject line Bug#936937: fixed in libvshadow 20190323-1.1
has caused the Debian Bug report #936937,
regarding libvshadow: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 29 Jan 2020 18:06:02 +
with message-id
and subject line Bug#936895: fixed in libmsiecf 20181227-1.1
has caused the Debian Bug report #936895,
regarding libmsiecf: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 29 Jan 2020 18:05:24 +
with message-id
and subject line Bug#936859: fixed in libfsntfs 20190104-1.1
has caused the Debian Bug report #936859,
regarding libfsntfs: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 29 Jan 2020 18:05:39 +
with message-id
and subject line Bug#936863: fixed in libfwnt 20181227-1.1
has caused the Debian Bug report #936863,
regarding libfwnt: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 29 Jan 2020 18:07:18 +
with message-id
and subject line Bug#936938: fixed in libvslvm 20181227-1.1
has caused the Debian Bug report #936938,
regarding libvslvm: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 29 Jan 2020 18:06:54 +
with message-id
and subject line Bug#936931: fixed in libvhdi 20181227-1.1
has caused the Debian Bug report #936931,
regarding libvhdi: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 29 Jan 2020 18:06:24 +
with message-id
and subject line Bug#936912: fixed in libregf 20190303-1.1
has caused the Debian Bug report #936912,
regarding libregf: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 29 Jan 2020 18:06:17 +
with message-id
and subject line Bug#936909: fixed in libqcow 20181227-1.1
has caused the Debian Bug report #936909,
regarding libqcow: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
Your message dated Wed, 29 Jan 2020 18:05:54 +
with message-id
and subject line Bug#936890: fixed in liblnk 20181227-1.1
has caused the Debian Bug report #936890,
regarding liblnk: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 29 Jan 2020 18:04:59 +
with message-id
and subject line Bug#936852: fixed in libevt 20181227-1.1
has caused the Debian Bug report #936852,
regarding libevt: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Wed, 29 Jan 2020 18:06:39 +
with message-id
and subject line Bug#936919: fixed in libsigscan 20190103-1.1
has caused the Debian Bug report #936919,
regarding libsigscan: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
Hi Boyuan,
On Wed, 22 Jan 2020 16:17:37 -0500 Boyuan Yang wrote:
> No idea why. Looks like we need to have python3-zeitgeist removed eventually.
>
> However before that, I'm going for a workaround: Upload an experimental
> version with higher version string, e.g., 1.0.2+py3-0.
That happened,
Got into this today. apt full-upgrade complain with message about it can'
install package nvidia-kernel-435.21-3 (sorry, it was in the morning, do
not save logs).
For now remove all nvidia libs and install old 430.64-5 version from
snapshot
--
*Сиамская кошка – это сама истина с чумазой
Processing commands for cont...@bugs.debian.org:
> forwarded 950020 https://github.com/mesonbuild/meson/pull/6539
Bug #950020 [src:meson] meson autopkg tests failing on arm64
Set Bug forwarded-to-address to 'https://github.com/mesonbuild/meson/pull/6539'.
>
End of message, stopping processing
Hi there,
I agree that a fix should be done. Personally, I'm not a contributor
but just someone who was affected by the same issue.
I'd be happy to help fix it if someone can point me in the right direction.
Thanks,
Mohammed
Your message dated Wed, 29 Jan 2020 16:49:33 +
with message-id
and subject line Bug#936920: fixed in libsmdev 20190315-1.1
has caused the Debian Bug report #936920,
regarding libsmdev: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has been
On 21/01/2020 17:26, Adrian Bunk wrote:
> Control: tags 936541 + patch
> Control: tags 936541 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for fonts-rit-sundar (versioned as
> 2.0.0+20170909-1.1) and uploaded it to DELAYED/14. Please feel free to
> tell me if I should cancel it.
Your message dated Wed, 29 Jan 2020 16:36:43 +
with message-id
and subject line Bug#950141: fixed in rdkit 201909.1-2
has caused the Debian Bug report #950141,
regarding rdkit downloads additional files during the build
to be marked as done.
This means that you claim that the problem has
Your message dated Wed, 29 Jan 2020 16:19:46 +
with message-id
and subject line Bug#946470: fixed in libreoffice 1:6.4.0-1
has caused the Debian Bug report #946470,
regarding libreoffice-l10n-de: unhandled symlink to directory conversion:
/usr/share/doc/PACKAGE
to be marked as done.
This
On Tue, Jan 28, 2020 at 11:21:46PM -0500, Sandro Tosi wrote:
> ok, whos of the maintainers is working on packaging 1.18? i see
> there's even 1.20 released.
noone, I believe. Also because it needs dnf, which is not packaged for
Debian at all.
I was just going to remove myself from uploaders in
Checking this:
The test code test_mpi_ocl.c works fine for me ("success").
I see the result described for test_lt_dlopen.c, it returns:
0x559b5c923250 can't close resident module
However I agree with Jeff that this does not appear to be an error.
If lt_dlopen() returns a handle, it was
Your message dated Wed, 29 Jan 2020 15:49:04 +
with message-id
and subject line Bug#950144: fixed in imexam 0.8.1-2
has caused the Debian Bug report #950144,
regarding imexam FTBFS with astropy 4.0
to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Processing commands for cont...@bugs.debian.org:
> severity 950141 serious
Bug #950141 [src:rdkit] rdkit downloads additional files during the build
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
950141:
"As a temporary fix, and I only suggest this for the brave, I would
enable experimental repositories:"
But people have no other option if they want a graphical interface
since part of compiling the new version is to first remove the old
version of the modules and since the source of the old
Processing control commands:
> tag -1 pending
Bug #946470 [libreoffice-l10n-de] libreoffice-l10n-de: unhandled symlink to
directory conversion: /usr/share/doc/PACKAGE
Added tag(s) pending.
--
946470: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946470
Debian Bug Tracking System
Contact
Control: tag -1 pending
Hello,
Bug #946470 in libreoffice 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:
Your message dated Wed, 29 Jan 2020 15:05:10 +
with message-id
and subject line Bug#949222: fixed in salt 2019.2.3+dfsg1-1
has caused the Debian Bug report #949222,
regarding salt: CVE-2019-17361
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Wed, 29 Jan 2020 15:04:41 +
with message-id
and subject line Bug#950071: fixed in python-netaddr 0.7.19-2
has caused the Debian Bug report #950071,
regarding python-netaddr: missing build dependency on dh-python
to be marked as done.
This means that you claim that the
Your message dated Wed, 29 Jan 2020 15:04:33 +
with message-id
and subject line Bug#950093: fixed in pbseqlib 5.3.3+dfsg-4
has caused the Debian Bug report #950093,
regarding libblasr-dev: missing Breaks+Replaces: libblasr (<< 5.3.3)
to be marked as done.
This means that you claim that the
Source: apertium-oc-ca
Version: 1.0.6~r57551-3
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-oc-ca.html
...
dh_auto_build -O--fail-missing
make -j15
make[1]: Entering directory
Source: apertium-es-ro
Version: 0.7.3~r57551-3
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-es-ro.html
...
apertium-es-ro.ro.dix:86644: elapertium-es-ro.es.dix:3767: element pardef:
Schemas validity error : Element
Source: apertium-eo-ca
Version: 1:0.9.1~r60655-3
Severity: serious
Tags: ftbfs bullseye sid
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/apertium-eo-ca.html
...
lt-comp rl apertium-eo-ca.eo.dix ca-eo.autogen.bin
apertium-eo-ca.ca.dix:867: element pardef: Schemas validity
Your message dated Wed, 29 Jan 2020 14:47:23 +
with message-id
and subject line Bug#949281: fixed in r-bioc-tximport 1.14.0+dfsg-2
has caused the Debian Bug report #949281,
regarding r-bioc-tximport: autopkgtest regression
to be marked as done.
This means that you claim that the problem has
Processing commands for cont...@bugs.debian.org:
> severity 930178 normal
Bug #930178 [systemd] salt-master: install fails if salt-minion was installed
first
Severity set to 'normal' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
930178:
Source: python-cycler
Version: 0.10.0-2
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/python-cycler.html
...
Exception occurred:
File "/usr/lib/python3/dist-packages/IPython/sphinxext/ipython_directive.py",
line 1021, in run
raise
Source: imexam
Version: 0.8.1-1
Severity: serious
Tags: ftbfs
https://tests.reproducible-builds.org/debian/rb-pkg/unstable/amd64/imexam.html
...
Running Sphinx v1.8.5
/usr/lib/python3/dist-packages/astropy/config/configuration.py:557:
ConfigurationMissingWarning: Configuration defaults will be
Hi everyone,
Based on some small research, I've discovered that there was a fix
included for this in 440.31 (which I'm not sure we can either backport
or bump version):
Your message dated Wed, 29 Jan 2020 13:34:12 +
with message-id
and subject line Bug#949940: fixed in cloud-init 19.3-2
has caused the Debian Bug report #949940,
regarding cloud-init build depends on the removed pep8 transitional package
to be marked as done.
This means that you claim that
Source: pyglet
Version: 1.4.1-3
Severity: serious
Tags: ftbfs
Hi!
According to upstream [1]. This bugs was introduce in the latest Python
version [2]
In pyglet b1.4.9 this bugs is fixed.
[1] https://github.com/pyglet/pyglet/issues/137#issuecomment-579527965
[2]
1 - 100 of 130 matches
Mail list logo
