Your message dated Wed, 4 Dec 2019 08:42:41 +0100
with message-id <20191204084241.7439b...@monsterix.mbehrle.de>
and subject line Re: Bug#944073: tryton-proteus breaks
tryton-modules-purchase-request autopkgtest: trytond.exceptions.UserError:
('UserError', ('Purchase requests are only created by
Your message dated Wed, 4 Dec 2019 08:44:34 +0100
with message-id <20191204084434.1230a...@monsterix.mbehrle.de>
and subject line Re: Bug#944074: tryton-proteus breaks
tryton-modules-account-fr autopkgtest: Doctest: scenario_fec.rst ... FAIL
has caused the Debian Bug report #944074,
regarding
On 2019-12-03 12:27:00 +0100, Vincent Lefevre wrote:
> The purpose of unison-all is the following (see the latest sentence
> in particular):
>
> Description: file synchronization tool (all console versions)
> This is a metapackage that depends on all supported console versions
> of Unison, a
Your message dated Tue, 03 Dec 2019 08:54:35 +
with message-id
and subject line Bug#946003: fixed in pyresample 1.13.2-2
has caused the Debian Bug report #946003,
regarding pyresample: autopkgtest failures
to be marked as done.
This means that you claim that the problem has been dealt with.
Processing control commands:
> tag -1 pending
Bug #945976 [octave-dicom] octave-dicom: fails to find GDCM on many
architectures.
Added tag(s) pending.
--
945976: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945976
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #945976 in octave-dicom 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:
Package: unison
Version: 2.48.4-2
Severity: grave
Justification: renders package unusable
When synchronizing with Debian 10 (buster), unison-latest-stable fails
with errors:
Fatal error: Server: Fatal error during unmarshaling (input_value: ill-formed
message),
possibly because client and
Hi Ole,
On Mon, Dec 02, 2019 at 01:01:07PM +0100, Ole Streicher wrote:
> Hi Andreas,
>
> I think that is the moment where the skimage build should be simplified
> to the "official" build process: Python convention is that symbols
> starting with an underscore are internal only (and ofcourse
Your message dated Tue, 03 Dec 2019 09:34:27 +
with message-id
and subject line Bug#945976: fixed in octave-dicom 0.2.2-5
has caused the Debian Bug report #945976,
regarding octave-dicom: fails to find GDCM on many architectures.
to be marked as done.
This means that you claim that the
Hi Scott,
Someone approached me and volunteered to port presage to Python 3 in late
October, but I haven't heard back since them.
Let me take a look at what kind of an effort it would be to port to python 3:
that would be my preferred option if I can find the time to do.
Else, the suggestion to
Package: picport
Version: 1.9.1-4
Severity: serious
Justification: always crash on x86
Hello,
Admittedly this is early since 5.5 is not released yet, but
better submit this while I'm thinking about it: as described in
https://lwn.net/Articles/804143/ , starting from version 5.5, Linux
will make
Hi,
This workaround works for me. Thank you.
Sébastien
Le lun. 2 déc. 2019 à 19:42, Patrice Duroux a
écrit :
>
> Hi,
>
> It is may be the same bug as the one in my bug report here:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945887
>
> I found a solution by editing the following file
Your message dated Tue, 03 Dec 2019 11:04:57 +
with message-id
and subject line Bug#946041: fixed in unison 2.48.4-3
has caused the Debian Bug report #946041,
regarding unison-latest-stable: can't synchronize with Debian 10 (buster)
to be marked as done.
This means that you claim that the
Package: unison-all
Version: 2.48+2
Severity: grave
Justification: renders package unusable
The purpose of unison-all is the following (see the latest sentence
in particular):
Description: file synchronization tool (all console versions)
This is a metapackage that depends on all supported
Le 03/12/2019 à 12:27, Vincent Lefevre a écrit :
> The purpose of unison-all is the following (see the latest sentence
> in particular):
> [...]
> Each of the supported versions uses a different protocol version;
> installing this metapackage ensures the ability to synchronize with
> old
Control: tags + patch
Control: tags + pending
This turned out to be a little tricker than expected. While the
tray-monitor code itself only needed a tiny adjustment to compile
against Qt5, getting the actual binary into the package needed more
work.
Upstream is using libtool to link and install
Your message dated Tue, 03 Dec 2019 10:05:25 +
with message-id
and subject line Bug#938631: fixed in tea4cups 3.14~alpha0+svn3576-2
has caused the Debian Bug report #938631,
regarding tea4cups: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
The patch there is a backport of some upstream fixes and seems to be
enough to fix the build (it has been uploaded to Ubuntu now)
yt/units/tests/test_ytarray.py | 15 +++
yt/units/yt_array.py | 23 ---
2 files changed, 35 insertions(+), 3 deletions(-)
Package: ledger
Version: 3.1.2+dfsg1-1
Severity: grave
What happens:
$ ledger
ledger: error while loading shared libraries: libboost_python27.so.1.67.0:
cannot open shared object file: No such file or directory
$ $ dpkg -L libboost-python1.67.0
/.
/usr
/usr/lib
/usr/lib/x86_64-linux-gnu
Your message dated Tue, 03 Dec 2019 09:22:50 +
with message-id
and subject line Bug#939623: fixed in python-mne 0.19.1+dfsg-1
has caused the Debian Bug report #939623,
regarding python3-mne: missing Breaks+Replaces: python-mne
to be marked as done.
This means that you claim that the problem
Your message dated Tue, 03 Dec 2019 09:23:11 +
with message-id
and subject line Bug#946019: fixed in rust-rusty-tags 3.5.1-2
has caused the Debian Bug report #946019,
regarding rust-rusty-tags build-depends on nonexistent virtual package.
to be marked as done.
This means that you claim that
Hi Ole,
I had a quick look what you mean and tried to make the build more
standard[1]. The build issues are remaining and need some work.
Kind regards, Andreas.
[1]
https://salsa.debian.org/science-team/skimage/commit/d787835f7293dc105b9b8cf37d59c1f9fbf46110
On Mon, Dec 02, 2019 at
Hello,
Right now, I can't dedicate time towards porting ModelBuilder. It should be
a quick fix to port to Python3. BIP is already python3 compatible.
So whatever you decide is fine with me.
thanks,
Flávio Codeço Coelho
On Tue, Dec 3, 2019 at 4:48 AM Andreas Tille wrote:
> Hi Scott,
>
> On
On Tue, 3 Dec 2019 at 01:33, peter green wrote:
>
> Package: zeroinstall-injector
> Version: 2.14.1-3
> Severity: serious
>
> zeroinstall-injector build-depends on libcurl-ocaml-dev which is not
> currently in testing, either libcurl-ocaml-dev needs to be fixed so it can
> return to testing,
Control: fixed -1 0.28+git20190813.37e5b53-2
This is fixed in last upload.
Processing commands for cont...@bugs.debian.org:
> reassign 946036 libboost-python1.67.0
Bug #946036 [ledger] Broken by boost dropping Python 2 support
Bug reassigned from package 'ledger' to 'libboost-python1.67.0'.
No longer marked as found in versions ledger/3.1.2+dfsg1-1.
Ignoring request to
Le 03/12/2019 à 12:54, Vincent Lefevre a écrit :
> BTW, I think that "unison" should just be a metapackage depending
> on unison-debian, where is the Debian version (with adapted
> paths and executable names). That way, users could install both
> Unison from stable and from testing/unstable
Package: etckeeper
Version: 1.18.12-1
Severity: serious
Justification: Policy 10.4
/etc/etckeeper/commit.d/50vcs-commit[22]: ${@#-m}: bad substitution
This is because doing trim operations on an array are not implemented
in mksh, and unspecified in POSIX:
[…] If parameter is '#', '*', or '@',
Hi Matteo,
The timeline for removing python2 is "before bullseye." Because it will
take a long time, the effort has started now. We are starting with leaf
packages, of which presage is one, so that is why I've poked this bug. :)
Thanks,
Scott
On Tue, 3 Dec 2019, Matteo Vescovi wrote:
Processing control commands:
> severity -1 important
Bug #942620 [src:python-espeak] src:python-espeak: Maintainer email address not
working
Severity set to 'important' from 'serious'
--
942620: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942620
Debian Bug Tracking System
Contact
Control: severity -1 important
On Sun, 27 Oct 2019 15:53:15 +0100 Samuel Thibault
wrote:
> Hello Siegfried,
>
> Scott Kitterman, le sam. 19 oct. 2019 00:24:39 -0400, a ecrit:
> > rai...@ubuntu.com
> > host mx.canonical.com [91.189.95.10]
> > SMTP error from remote mail server after
Processing control commands:
> fixed -1 0.28+git20190813.37e5b53-2
Bug #940490 [golang-gopkg-libgit2-git2go.v28-dev]
golang-gopkg-libgit2-git2go.v28-dev: ships files in
/usr/share/gocode/src/gopkg.in/libgit2/git2go.v27
Marked as fixed in versions
Your message dated Tue, 3 Dec 2019 18:07:02 +0530
with message-id
and subject line closing, already fixed
has caused the Debian Bug report #940490,
regarding golang-gopkg-libgit2-git2go.v28-dev: ships files in
/usr/share/gocode/src/gopkg.in/libgit2/git2go.v27
to be marked as done.
This means
Processing commands for cont...@bugs.debian.org:
> forcemerge 945840 946036
Bug #945840 [libboost-python1.67.0] /usr/bin/ledger: error while loading shared
libraries: libboost_python27.so.1.67.0: cannot open shared object file: No such
file or directory
Unable to merge bugs because:
package of
Your message dated Tue, 03 Dec 2019 14:44:43 +
with message-id
and subject line Bug#944602: fixed in ocurl 0.9.0-1
has caused the Debian Bug report #944602,
regarding FTBFS with OCaml 4.08.1 (Need update for HTTP_VERSION)
to be marked as done.
This means that you claim that the problem has
Your message dated Tue, 03 Dec 2019 14:43:42 +
with message-id
and subject line Bug#942393: fixed in mlpack 3.2.2-1
has caused the Debian Bug report #942393,
regarding mlpack: downloads stuff from internet during build?
to be marked as done.
This means that you claim that the problem has
Source: landslide
Version: 1.1.3-1
Severity: grave
Currently package landslide FTBFS in Sid. I noticed that it was just made into
a compatibility package with nothing inside. This is unnecessary, plus that
current setup actually fails to build from source.
Since python-landslide has no reverse
Processing commands for cont...@bugs.debian.org:
> found 943521 2.1.3+~1.0.1+~1.0.2-4
Bug #943521 {Done: Jonas Smedegaard } [src:node-proxyquire]
node-proxyquire: fails to clean after build: rm: cannot remove
'./debian/node_modules': Is a directory
Marked as found in versions
On 2019-12-03 14:39:47 +0100, Stéphane Glondu wrote:
> Le 03/12/2019 à 12:54, Vincent Lefevre a écrit :
> > BTW, I think that "unison" should just be a metapackage depending
> > on unison-debian, where is the Debian version (with adapted
> > paths and executable names). That way, users could
On Tue, 03 Dec 2019 11:04:57 +, Stéphane Glondu wrote:
> unison (2.48.4-3) unstable; urgency=medium
> .
>* Add entry in NEWS.Debian documenting the incompatibility due to
> compilation with a different OCaml version (Closes: #946041)
I seems that the NEWS file hasn't made it into
Source: lv2dynparam1
Version: 2-6
Severity: serious
Tags: ftbfs
lv2dynparam1 fails to build from source in unstable, because it fails
finding lv2core.pc using pkg-config:
| checking for LV2... no
| configure: error: Package requirements (lv2core >= 1) were not met:
|
| No package 'lv2core'
Processing commands for cont...@bugs.debian.org:
> fixed 834026 0.11-2
Bug #834026 {Done: Sean Whitton }
[libghc-yi-rope-dev] libghc-yi-rope-dev: links against libicu but doesn't
depend on it
Marked as fixed in versions haskell-yi-rope/0.11-2.
> thanks
Stopping processing here.
Please contact
Processing commands for cont...@bugs.debian.org:
> reassign 940491 src:meep 1.11.0-1
Bug #940491 [libmeep16] libmeep16: missing Breaks+Replaces: libmeep12
Warning: Unknown package 'libmeep16'
Bug reassigned from package 'libmeep16' to 'src:meep'.
No longer marked as found in versions
Processing commands for cont...@bugs.debian.org:
> reassign 940825 src:linux 5.2.9-2~bpo10+1
Bug #940825 [linux-source-5.2] linux-source-5.2: Backport of wifi driver fixes
to enable wifi on whiseylake based system in 5.2.9
Warning: Unknown package 'linux-source-5.2'
Bug reassigned from package
Source: waylandpp
Version: 0.2.5-1
Severity: serious
Tags: patch ftbfs
User: debian-cr...@lists.debian.org
Usertags: ftcbfs
waylandpp fails to cross build from source, because it requires passing
a native wayland-scanner++ for cross building. It also fails to build
from source, because a template
Processing control commands:
> tags -1 + upstream patch
Bug #945864 [unhide] unhide[208429]: segfault at 7ffd06cfec58 ip
55c15aa077d3 sp 7ffd06cfec60 error 6 in unhide-linux[55c15aa07000+6000]
Added tag(s) upstream and patch.
--
945864:
Control: severity -1 important
On 01.12.19 06:12, YunQiang Su wrote:
> YunQiang Su 于2019年11月30日周六 上午11:19写道：
>>
>> YunQiang Su 于2019年11月29日周五 下午2:21写道：
>>>
>>> 在 2019-11-29五的 07:00 +0100，Matthias Klose写道：
On 28.11.19 18:09, YunQiang Su wrote:
> Matthias Klose 于2019年11月28日周四 下午5:51写道：
Processing control commands:
> severity -1 important
Bug #945763 [src:gcc-9] gcc-9 ftbfs on mipsel
Severity set to 'important' from 'serious'
--
945763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945763
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Processing commands for cont...@bugs.debian.org:
> severity 910945 serious
Bug #910945 [src:fontcustom] fontcustom: autopkgtest fails
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
910945:
Hi,
if someone will show interest by writing an autopkgtest (or would
provide some test script to prove the functionality which I'd
volunteer to turn into an autopkgtest) I'd feel slightly motivated
to package BIP and try my luck with a Python3 port.
Kind regards
Andreas.
On Tue, Dec 03,
Dear Salvatore,
> > Security team, would you like an upload for stable?
>
> As far I can see this issue has been introduced around 2.1 where the
> search support for view permissions and a read-only admin support was
> added. […]
Upon further inspection that is my reading too. I was being
Your message dated Tue, 03 Dec 2019 19:00:13 +
with message-id
and subject line Bug#944582: fixed in paraview 5.7.0-2
has caused the Debian Bug report #944582,
regarding python3 -c 'import paraview.simple' fails
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 03 Dec 2019 19:00:13 +
with message-id
and subject line Bug#944533: fixed in paraview 5.7.0-2
has caused the Debian Bug report #944533,
regarding paraview-python converted to python3, but not the autopkg test
to be marked as done.
This means that you claim that the
Your message dated Tue, 03 Dec 2019 19:00:13 +
with message-id
and subject line Bug#944353: fixed in paraview 5.7.0-2
has caused the Debian Bug report #944353,
regarding paraview: FTBFS on armhf
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Control: tags -1 + upstream patch
Dear Maintainer,
I tried to have a look into this issue and guess I found something.
It looks like the application is exhausting its stack by
allocation an integer array with maxpid elements.
At least in my test VM this leads to 16 MB array size,
while stack
Your message dated Tue, 3 Dec 2019 22:16:38 +0100
with message-id <20191203211638.neuxipukds6tl...@sar0.p1otr.com>
and subject line fixed in 0.14.0+ds1-1
has caused the Debian Bug report #943621,
regarding uvloop needs an update for python 3.8
to be marked as done.
This means that you claim that
On Sun, Oct 06, 2019 at 05:09:30PM -0400, Jeremy Bicha wrote:
> Control: severity -1 serious
> Control: tags -1 -buster
>
> As part of the Python2 removal, it is our intent that pygtk will be removed
> from Testing before the release of Debian 11
> "Bullseye". Therefore, I am bumping the
On 2019-12-01 11:35:08 [-0800], Daniel Schepler wrote:
> ...
> debian/rules build
> dh build --parallel
>dh_update_autotools_config -O--parallel
>dh_auto_configure -O--parallel
>dh_auto_build -O--parallel
>dh_auto_test -O--parallel
> fakeroot debian/rules binary
> dh binary
Hi Andreas and Ole,
The problem here stems from an old version of Cython. My recommended approach
would be to build from the git tag instead of the source tarball (i.e., the
version without pre-generated Cython files). I don't think the Cython-related
patches that were applied since would
Hi,
I agree with Giovanni, I think we need to re-enable python2 for a while.
Regards
Anton
Your message dated Tue, 03 Dec 2019 21:48:04 +
with message-id
and subject line Bug#896358: fixed in python-flask-rdf 0.2.0-1.1~deb9u1
has caused the Debian Bug report #896358,
regarding python3-flask-rdf: flask_rdf fails to import
to be marked as done.
This means that you claim that the
Your message dated Tue, 03 Dec 2019 21:48:04 +
with message-id
and subject line Bug#896385: fixed in python-flask-rdf 0.2.0-1.1~deb9u1
has caused the Debian Bug report #896385,
regarding python-flask-rdf: flask_rdf fails to import
to be marked as done.
This means that you claim that the
Your message dated Tue, 03 Dec 2019 21:47:59 +
with message-id
and subject line Bug#928420: fixed in php-imagick 3.4.3~rc2-2+deb9u1
has caused the Debian Bug report #928420,
regarding php-imagick: CVE-2019-11037
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Tue, 03 Dec 2019 21:48:04 +
with message-id
and subject line Bug#867429: fixed in python-flask-rdf 0.2.0-1.1~deb9u1
has caused the Debian Bug report #867429,
regarding python3-flask-rdf: missing dependencies
to be marked as done.
This means that you claim that the problem
Processing control commands:
> tag -1 pending
Bug #937901 [src:python-lz4] python-lz4: Python2 removal in sid/bullseye
Added tag(s) pending.
--
937901: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=937901
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tag -1 pending
Hello,
Bug #937901 in python-lz4 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:
Hi,
Il 01/12/19 23:33, Dimitri John Ledkov ha scritto:
> All the broken packages, are RC buggy themselves already. Anything that
> is using py2 is RC buggy.
I'm sorry, but this does not look like the way Python maintainers asked
to deal with reverse dependencies: from [1] it is clear that you
Processing control commands:
> block 944417 by -1
Bug #944417 [release.debian.org] transition: cgal
944417 was blocked by: 944776 944775
944417 was not blocking any bugs.
Added blocking bug(s) of 944417: 946114
--
944417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944417
946114:
Source: crrcsim
Version: 0.9.13-3.1
Severity: serious
Tags: ftbfs
Control: block 944417 by -1
Hi,
the transition to CGAL 5.0 started (see bug #944417) and your package FTBFS. I
intend to NMU the package with the attached diff to DELAYED/5-day.
Best regards,
Joachim
diff -Nru
Hi Peter,
On Mon, Dec 02, 2019 at 03:42:21PM +, Peter Cock wrote:
> This was included in Biopython 1.74 and 1.75, yet your copy of
> Tests/test_psw.py
> would seem to date from Biopython 1.73 or older.
>
> I suspect an old cached copy of the test folder is largely to blame?
Arghhh, sorry
On Fri, Nov 22, 2019 at 11:04:18AM +0300, Dmitry Shachnev wrote:
> Dear maintainers,
>
> I am going to remove the Python 2 part of python-qt4 from sid soon, but not
> before 10 days from now, 2019-12-02.
>
> If your package does not migrate away from it, it will become uninstallable.
>
> You
On Wed, Jul 24, 2019 at 07:31:32PM -0400, Nicholas D Steeves wrote:
> Dear Steve Langasek and contributors to these threads,
>
> Steve, are you still interested in maintaining this package?
>
> Heimdall-flash has not seen an update since 2016, and Bug #872788
> requesting an update to 1.4.2 has
Your message dated Tue, 3 Dec 2019 22:12:46 +0100
with message-id <20191203211246.2qmpe2xbi7rwd...@sar0.p1otr.com>
and subject line fixed in 0.20.0-1
has caused the Debian Bug report #943832,
regarding asyncpg fails tests with python3.8
to be marked as done.
This means that you claim that the
Hi Alastair,
On 02-12-2019 11:09, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the src:mpich package:
>
> #945933: mpich FTBFS on armel, armhf and mipsel
mipsel still fails, albeit with a different error.
Paul
Processing control commands:
> severity -1 serious
Bug #944776 [src:prepair] FTBFS with CGAL 5.0
Severity set to 'serious' from 'important'
> tag -1 ftbfs
Bug #944776 [src:prepair] FTBFS with CGAL 5.0
Ignoring request to alter tags of bug #944776 to the same tags previously set
> block 944417 by
Processing control commands:
> severity -1 serious
Bug #944775 [src:pprepair] FTBFS with CGAL 5.0
Severity set to 'serious' from 'important'
> tag -1 ftbfs
Bug #944775 [src:pprepair] FTBFS with CGAL 5.0
Ignoring request to alter tags of bug #944775 to the same tags previously set
> block 944417
Your message dated Tue, 03 Dec 2019 21:35:15 +
with message-id
and subject line Bug#945725: fixed in py-autopep8-el 2016.1-3
has caused the Debian Bug report #945725,
regarding py-autopep8-el: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem
Processing control commands:
> block 944417 by -1
Bug #944417 [release.debian.org] transition: cgal
944417 was blocked by: 944776 944775 946114
944417 was not blocking any bugs.
Added blocking bug(s) of 944417: 946116
--
944417: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944417
946116:
Source: rheolef
Version: 7.0-3
Severity: serious
Tags: ftbfs
Control: block 944417 by -1
Hi,
the transition to CGAL 5.0 started (see bug #944417) and your package FTBFS.
Attached are two patches to fix the problem, however, the build fails at a
later stage due to bug #944197.
Best regards,
Processing commands for cont...@bugs.debian.org:
> severity 943187 serious
Bug #943187 [src:qmidiarp] qmidiarp: Python2 removal in sid/bullseye
Severity set to 'serious' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
943187:
Processing commands for cont...@bugs.debian.org:
> severity 946030 serious
Bug #946030 [xul-ext-firetray] xul-ext-firetray classified as a legacy
extension by Thunderbird 68.2.2 (Debian Stable AMD64)
Severity set to 'serious' from 'normal'
> clone 946081 -1 -2
Bug #946081 [ftp.debian.org] RM:
Your message dated Wed, 04 Dec 2019 00:04:43 +
with message-id
and subject line Bug#937901: fixed in python-lz4 2.2.1+dfsg-1
has caused the Debian Bug report #937901,
regarding python-lz4: Python2 removal in sid/bullseye
to be marked as done.
This means that you claim that the problem has
That would appear to be #429510.
This seems like a job for lintian. #946126.
Package: webext-browserpass
Version: 3.4.1-2
Severity: serious
When I click on the BrowserPass icon in Firefox ESR I get this error:
Error: TypeError: localStorage is null
When I click on the BrowserPass icon in Firefox I get this error:
TypeError: null is not a valid URL.
These persist
Your message dated Tue, 3 Dec 2019 19:10:04 -0800
with message-id <20191204031004.itpip6vk555c65fp@stgulik>
and subject line Re: Bug#945446: efl: FTBFS on most architectures in
experimental
has caused the Debian Bug report #945446,
regarding efl: FTBFS on most architectures in experimental
to be
Hi,
Sebastian Andrzej Siewior wrote:
> I don't know what changed but I think it is debhelper. We have now:
>
> |(sid)bigeasy@debbuildd:~/xz/1/xz-utils-5.2.4$ dh binary --no-act
> | debian/rules install
> | dh_installdeb
> | dh_gencontrol
> | dh_md5sums
> | dh_builddeb
>
> and that
Your message dated Wed, 04 Dec 2019 05:19:16 +
with message-id
and subject line Bug#944947: fixed in python-uinput 0.11.2-2.1
has caused the Debian Bug report #944947,
regarding python-uinput: needs an explicit build dependency on dh-python
to be marked as done.
This means that you claim
Your message dated Wed, 04 Dec 2019 05:19:16 +
with message-id
and subject line Bug#945233: fixed in python-uinput 0.11.2-2.1
has caused the Debian Bug report #945233,
regarding python-uinput: needs an explicit build dependency on dh-python
to be marked as done.
This means that you claim
Your message dated Wed, 04 Dec 2019 05:19:16 +
with message-id
and subject line Bug#945233: fixed in python-uinput 0.11.2-2.1
has caused the Debian Bug report #945233,
regarding python-uinput: needs an explicit build dependency on dh-python
to be marked as done.
This means that you claim
Your message dated Wed, 04 Dec 2019 05:19:16 +
with message-id
and subject line Bug#944947: fixed in python-uinput 0.11.2-2.1
has caused the Debian Bug report #944947,
regarding python-uinput: needs an explicit build dependency on dh-python
to be marked as done.
This means that you claim
Hi,
The issue described in this bug is fixed. However, after the update to
5.7.0-2, the new python3-paraview has no vtk dependencies (python3-
vtk7). Previously, paraview-python had dependencies on python-vtk6 and
python3-vtk7. Yet, `python -c "import vtk"` runs successfully even when
`dpkg -l |
Sebastian Andrzej Siewior dixit:
>| build clean install binary-arch binary-indep binary:
AFAIK, dh7-style does not know an “install” target at all,
but build-{arch,indep} are missing in that list.
bye,
//mirabilos
--
11:56⎜«liwakura:#!/bin/mksh» also, i wanted to add mksh to my own distro │
i
92 matches
Mail list logo
