On 2018-06-10 積丹尼 Dan Jacobson wrote:
> Oops. I mean just:
> Setting up exim4-config (4.91-5) ...
> /etc/exim4/update-exim4.conf.conf: line 26: dc_eximconfig_configtype: command
> not found
Hello,
Are you running bash (or other stuff) from experimental? IIRC there is
some breakage there.
cu
Oops. I mean just:
Setting up exim4-config (4.91-5) ...
/etc/exim4/update-exim4.conf.conf: line 26: dc_eximconfig_configtype: command
not found
Setting up exim4-config (4.91-5) ...
/var/lib/dpkg/info/exim4-config.postinst: line 330: export:
`dc_eximconfig_configtype dc_other_hostnames dc_local_interfaces dc_readhost
dc_relay_domains dc_minimaldns dc_relay_nets dc_smarthost CFILEMODE
dc_use_split_config dc_hide_mailname
Hello Debian-Science folks,
Please feel free to CC me if you need any input about deep learning.
> From: Andreas Tille
> the description says:
>
> ... Alternatively, Keras could run on Google's
> TensorFlow (not yet available in Debian, but coming up).
>
> Is there some estimated time frame
Your message dated Sun, 10 Jun 2018 01:05:16 +
with message-id
and subject line Bug#901116: fixed in sane-backends-extras 1.0.22.6
has caused the Debian Bug report #901116,
regarding sane-backends-extras: FTBFS when built with dpkg-buildpackage -A
to be marked as done.
This means that you
Package: libfabric-bin
Version: 1.6.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package fails to upgrade from
'testing'.
It installed fine in 'testing', then the upgrade to 'sid' fails
because it tries to overwrite
Package: libcob4-dev
Version: 2.2-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts replaces-without-breaks
Hi,
during a test with piuparts and DOSE tools I noticed your package causes
removal of files that also belong to another package.
This is caused by using Replaces
Package: timidity,timidity-el
Version: 2.14.0-2
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install
because it tries to overwrite other packages files.
>From the attached log (scroll to the bottom...):
Your message dated Sun, 10 Jun 2018 00:54:04 +0100
with message-id <20180609235404.GA24375@pinky>
and subject line Re: Bug#900511: libcurl4 Conflicts: libcurl3
has caused the Debian Bug report #900511,
regarding libcurl4 Conflicts: libcurl3
to be marked as done.
This means that you claim that the
Processing commands for cont...@bugs.debian.org:
> unarchive 693396
Bug #693396 {Done: Ben Hutchings } [rar] rar: static &
dynamic executables mix
Unarchived Bug 693396
> unarchive 860952
Bug #860952 {Done: Ben Hutchings } [rar] Statically
linked to glibc, in breach of policy and copyright
Processing commands for cont...@bugs.debian.org:
> tags 900791 + buster sid
Bug #900791 [xserver-xorg-input-mouse] xserver-xorg-input-mouse: FTBFS with
newer xserver
Added tag(s) sid and buster.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
900791:
Processing control commands:
> tags -1 + moreinfo
Bug #901185 [exim4-config] exim4-config: fails to install
Added tag(s) moreinfo.
--
901185: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901185
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + moreinfo
On Sun, 2018-06-10 at 00:17 +0200, Eric Valette wrote:
> Paramétrage de exim4-config (4.91-5) ...
> /etc/exim4/update-exim4.conf.conf: ligne 32: dc_eximconfig_configtype
> : commande introuvable
> /etc/exim4/update-exim4.conf.conf: ligne 32: dc_eximconfig_configtype
>
Package: exim4-config
Version: 4.91-5
Severity: grave
Justification: renders package unusable
apt-get -f install
Lecture des listes de paquets... Fait
Construction de l'arbre des dépendances
Lecture des informations d'état... Fait
0 mis à jour, 0 nouvellement installés, 0 à enlever et
Your message dated Sat, 09 Jun 2018 21:37:19 +
with message-id
and subject line Bug#900457: fixed in yade 2018.02b-2
has caused the Debian Bug report #900457,
regarding yade: FTBFS and Debci failure with NumPy 1.14
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 09 Jun 2018 21:00:13 +
with message-id
and subject line Bug#854167: fixed in python-cartopy 0.16.0+dfsg1-1
has caused the Debian Bug report #854167,
regarding src:python-cartopy: Version 0.14.x is not compatible with
matplotlib>=2.0 / owslib>=0.14
to be marked as
Your message dated Sat, 09 Jun 2018 21:00:13 +
with message-id
and subject line Bug#889931: fixed in python-cartopy 0.16.0+dfsg1-1
has caused the Debian Bug report #889931,
regarding python-cartopy FTBFS with proj 5.0.0
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 09 Jun 2018 19:34:59 +
with message-id
and subject line Bug#899481: fixed in dnstap-ldns 0.2.0-4
has caused the Debian Bug report #899481,
regarding dnstap-ldns: Invalid maintainer address
pkg-dns-de...@lists.alioth.debian.org
to be marked as done.
This means that
Processing commands for cont...@bugs.debian.org:
> retitle 809252 node-cli: CVE-2016-10538
Bug #809252 [node-cli] node-cli: insecure use of temporary files
Changed Bug title to 'node-cli: CVE-2016-10538' from 'node-cli: insecure use of
temporary files'.
> forwarded 809252
On Sat, Jun 09, 2018 at 06:39:19PM +0200, Matthias Klose wrote:
> On 09.06.2018 18:31, Matthias Klose wrote:
> > On 09.06.2018 11:55, Philipp Kern wrote:
> > > On 6/9/18 7:20 AM, Steve Langasek wrote:
> > > > - the package is being upgraded; it is in the common case (when no
> > > > python
> > >
Your message dated Sat, 09 Jun 2018 18:21:01 +
with message-id
and subject line Bug#897548: fixed in yabause 0.9.14-3
has caused the Debian Bug report #897548,
regarding yabause: FTBFS: dh_install: missing files, aborting
to be marked as done.
This means that you claim that the problem has
Your message dated Sat, 09 Jun 2018 17:51:37 +
with message-id
and subject line Bug#901158: fixed in postgis 2.4.4+dfsg-2
has caused the Debian Bug report #901158,
regarding postgis: FTBFS: testsuite failure
to be marked as done.
This means that you claim that the problem has been dealt
Your message dated Sat, 09 Jun 2018 17:34:30 +
with message-id
and subject line Bug#901099: fixed in atlas 3.10.3-7
has caused the Debian Bug report #901099,
regarding libatlas-doc: fails to upgrade from 'stretch' - trying to overwrite
/usr/share/doc/libatlas-base-dev/README
to be marked as
Your message dated Sat, 09 Jun 2018 17:20:29 +
with message-id
and subject line Bug#896741: fixed in themole 0.3-2
has caused the Debian Bug report #896741,
regarding themole: missing build dependency on dh-python
to be marked as done.
This means that you claim that the problem has been
On 09.06.2018 18:31, Matthias Klose wrote:
On 09.06.2018 11:55, Philipp Kern wrote:
On 6/9/18 7:20 AM, Steve Langasek wrote:
- the package is being upgraded; it is in the common case (when no python
module names have been dropped from within the package) less important to
run py3clean
Your message dated Sat, 09 Jun 2018 16:35:35 +
with message-id
and subject line Bug#896592: fixed in val-and-rick 0.1a.dfsg1-6
has caused the Debian Bug report #896592,
regarding val-and-rick FTBFS with gdc 8
to be marked as done.
This means that you claim that the problem has been dealt
On 09.06.2018 11:55, Philipp Kern wrote:
On 6/9/18 7:20 AM, Steve Langasek wrote:
- the package is being upgraded; it is in the common case (when no python
module names have been dropped from within the package) less important to
run py3clean because the same files will be recreated
Your message dated Sat, 09 Jun 2018 16:05:18 +
with message-id
and subject line Bug#896631: fixed in python-cryptography 2.2.2-1
has caused the Debian Bug report #896631,
regarding FTBFS with sphinx 1.7.2: exception: cannot import name 'Directive'
to be marked as done.
This means that you
Control: tags -1 upstream
Control: forwarded -1 https://trac.osgeo.org/postgis/ticket/4104
On 06/09/2018 05:05 PM, Niko Tyni wrote:
> This package fails to build from source on current sid/amd64.
Thanks for reporting this issue, I've forwarded it upstream.
In the mean time I'll likely skip this
Processing control commands:
> tags -1 upstream
Bug #901158 [postgis] postgis: FTBFS: testsuite failure
Added tag(s) upstream.
> forwarded -1 https://trac.osgeo.org/postgis/ticket/4104
Bug #901158 [postgis] postgis: FTBFS: testsuite failure
Set Bug forwarded-to-address to
Your message dated Sat, 09 Jun 2018 15:20:11 +
with message-id
and subject line Bug#896591: fixed in tumiki-fighters 0.2.dfsg1-9
has caused the Debian Bug report #896591,
regarding tumiki-fighters FTBFS with gdc 8
to be marked as done.
This means that you claim that the problem has been
Your message dated Sat, 09 Jun 2018 15:20:03 +
with message-id
and subject line Bug#898917: fixed in ruby2.5 2.5.1-2
has caused the Debian Bug report #898917,
regarding ruby2.5: FTBFS with cowbuilder, requires network access
to be marked as done.
This means that you claim that the problem
Control: tag -1 pending
Hello,
Bug #898917 in ruby 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 Sat, 09 Jun 2018 15:09:05 +
with message-id
and subject line Bug#901121: fixed in turing 0.10~beta-2
has caused the Debian Bug report #901121,
regarding turing: missing dependency on python3-matplotlib
to be marked as done.
This means that you claim that the problem has
Processing control commands:
> tag -1 pending
Bug #898917 [ruby2.5] ruby2.5: FTBFS with cowbuilder, requires network access
Added tag(s) pending.
--
898917: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=898917
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Sat, 09 Jun 2018 15:09:18 +
with message-id
and subject line Bug#901041: fixed in viennacl 1.7.1+dfsg1-4
has caused the Debian Bug report #901041,
regarding libviennacl-doc: fails to upgrade from 'testing' - trying to
overwrite /usr/share/doc/libviennacl-dev/README.gz
to
Your message dated Sat, 09 Jun 2018 15:08:26 +
with message-id
and subject line Bug#900834: fixed in perl 5.26.2-6
has caused the Debian Bug report #900834,
regarding perl: CVE-2018-12015: Archive::Tar: directory traversal
to be marked as done.
This means that you claim that the problem has
Package: postgis
Version: 2.4.4+dfsg-1
Severity: serious
This package fails to build from source on current sid/amd64.
### /tmp/pgis_reg/test_50_diff ###
--- rt_gdalwarp_expected 2018-04-06 05:05:52.0 +
+++ /tmp/pgis_reg/test_50_out 2018-06-09 14:27:15.049036062 +
Your message dated Sat, 09 Jun 2018 15:06:32 +
with message-id
and subject line Bug#894045: fixed in libvncserver 0.9.11+dfsg-1.1
has caused the Debian Bug report #894045,
regarding libvncserver: CVE-2018-7225
to be marked as done.
This means that you claim that the problem has been dealt
While we are at it: Is this bug not already fixed?
https://buildd.debian.org/status/package.php?p=msxpertsuite
If it is, please close it with a Version string.
Thanks.
Processing commands for cont...@bugs.debian.org:
> found 900834 5.28.0~rc2-1
Bug #900834 [src:perl] perl: CVE-2018-12015: Archive::Tar: directory traversal
Marked as found in versions perl/5.28.0~rc2-1.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
900834:
retitle 896141 msxpertsuite: FTBFS with new Tex Live packages
thanks
Hi.
The package FTBFS with and without "dpkg-buildpackage -A" so I'm
dropping the binary-all part from the subject.
(The old title was a little bit misleading to me since I am also
occasionally building the entire archive to
Processing commands for cont...@bugs.debian.org:
> retitle 896141 msxpertsuite: FTBFS with new Tex Live packages
Bug #896141 [src:msxpertsuite] msxpertsuite: binary-all FTBFS
Changed Bug title to 'msxpertsuite: FTBFS with new Tex Live packages' from
'msxpertsuite: binary-all FTBFS'.
> thanks
Package: msxpertsuite
Version: 5.3.0-1
Severity: serious
In Bug #896141, where the build fails because of new Tex Live,
Adrian Bunk points out why the build process does not stop
as soon as there is an error.
Quote:
> > ./preface.tex:122: ==> Fatal error occurred, no output PDF file produced!
Your message dated Sat, 09 Jun 2018 13:34:27 +
with message-id
and subject line Bug#901102: fixed in firehol 3.1.5+ds1-1
has caused the Debian Bug report #901102,
regarding firehol-doc,firehol-tools-doc,fireqos-doc: fails to install, trying
to overwrite other packages files
to be marked as
On Sat, Jun 09, 2018 at 02:41:24PM +0200, Ferenc Wágner wrote:
> Are those .a (and .la) files really needed? We mostly avoid shipping
> them, see:
> http://www.debian.org/doc/debian-policy/ch-sharedlibs.html#s-sharedlibs-dev
>
On Sat, Jun 09, 2018 at 02:32:54PM +0200, Michael Biebl wrote:
> No, that's not what $PACKAGE in dpkg-maintscript-helper is used for.
> You can't "mark" a conffile as belonging to another package this way.
Maybe I misundertood something how it works internally.
But it has the effect that I
Hi,
Agent is required by default now but at the same time, we have enabled the
demo-agent to be installed by default and to
auto-start on all non-GNOME desktops. It's been 5 years since geoclue2 was
created, would be nice if other desktops
would implement an agent too. In the meantime, they can
Andreas Beckmann writes:
> Unpacking cluster-glue-dev (1.0.12-9) ...
> dpkg: error processing archive
> /tmp/apt-dpkg-install-iCxNhp/11-cluster-glue-dev_1.0.12-9_amd64.deb
> (--unpack):
>trying to overwrite '/usr/lib/heartbeat/plugins/compress/bz2.a', which is
> also in package
Am 09.06.2018 um 14:28 schrieb Reiner Herrmann:
> On Sat, Jun 09, 2018 at 02:16:14PM +0200, Michael Biebl wrote:
>> Why would the timidity package remove a conffile that belongs to another
>> package? That doesn't make sense to me.
>
> Because the conffile removed from package A could be
On Sat, Jun 09, 2018 at 02:16:14PM +0200, Michael Biebl wrote:
> Why would the timidity package remove a conffile that belongs to another
> package? That doesn't make sense to me.
Because the conffile removed from package A could be installed / taken
over by package B. As far as I understood it,
Am 09.06.2018 um 13:36 schrieb Reiner Herrmann:
> Hi Sven and Michael,
>
> thank you for the report and sorry for breaking it.
>
>> specifically
>>
>> timidity.maintscript
>> rm_conffile/etc/default/timidity2.14.0-1~timidity-daemon
>>
>> doesn't look correct either.
>>
Processing control commands:
> tags -1 + pending
Bug #901141 [timidity-el] '/usr/share/man/ja/man1/timidity.1.gz' is also in
package timidity
Added tag(s) pending.
--
901141: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901141
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tags -1 + pending
Hi David,
thank you for the report.
The problem was that during arch:all-only builds, the manpages
were also installed (in the wrong package).
It is fixed in git:
https://salsa.debian.org/debian/timidity/commit/3e5bff6
Kind regards,
Reiner
signature.asc
Hi Sven and Michael,
thank you for the report and sorry for breaking it.
> specifically
>
> timidity.maintscript
> rm_conffile/etc/default/timidity2.14.0-1~timidity-daemon
>
> doesn't look correct either.
> dpkg-maintscript-helper does not have support for moving conffiles from
>
Package: timidity-el
Version: 2.14.0-2
Severity: serious
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Preparing to unpack .../timidity-el_2.14.0-2_all.deb ...
ERROR: timidity-el is broken - called emacs-package-remove as a new-style
add-on, but has no compat file.
Remove timidity-el for
Processing commands for cont...@bugs.debian.org:
> severity 900750 important
Bug #900750 [thunderbird] thunderbird: Launching Thunderbird completely locks
my Xwindow session
Severity set to 'important' from 'critical'
> thanks
Stopping processing here.
Please contact me if you need assistance.
Your message dated Sat, 09 Jun 2018 10:19:50 +
with message-id
and subject line Bug#901100: fixed in cluster-glue 1.0.12-10
has caused the Debian Bug report #901100,
regarding cluster-glue-dev: missing Breaks+Replaces: cluster-glue (<< 1.0.12-8)
to be marked as done.
This means that you
Your message dated Sat, 09 Jun 2018 10:04:36 +
with message-id
and subject line Bug#901104: fixed in chezscheme 9.5+dfsg-5
has caused the Debian Bug report #901104,
regarding chezscheme: FTBFS when built with dpkg-buildpackage -A
to be marked as done.
This means that you claim that the
On 6/9/18 7:20 AM, Steve Langasek wrote:
> - the package is being upgraded; it is in the common case (when no python
> module names have been dropped from within the package) less important to
> run py3clean because the same files will be recreated shortly afterwards
> by py3compile from the
Package: sreview-common
Version: 0.3.0-1~bpo.1
Severity: grave
User: debian-ad...@lists.debian.org
Usertags: needed-by-DSA-Team
sreview-common failed to configure.
| Setting up sreview-common (0.3.0-1~bpo.1) ...
| usermod: user 'sreview' does not exist in /etc/passwd
| dpkg: error processing
When I said ffmpeg I meant ffmpeg libraries, chromium depends on several
ffmpeg libraries (libavcodec, libavformat, libavutil, ...) and when I
comment that chromium-67 is looking for ffmpeg-4 is because in other
distros (archlinux, gentoo, ...) they are packaging chromium-67 pointing to
ffmpeg-4
Dear Santiago Vila, you wrote:
> Sorry, there was a typo in the bug report. I meant "buster" of course.
Ah, muy bien. Thanks for the clarification.
> The reason for this is that -A was never tried with the current
> version (4.02.00-2).
>
> You can avoid this type of bugs to propagate to
On Sat, Jun 09, 2018 at 08:30:02AM +0200, Frank B. Brokken wrote:
> Dear Santiago Vila, you wrote:
> >
> > Package: src:yodl
> > Version: 4.02.00-2
> > Severity: serious
> >
> > Dear maintainer:
> >
> > I tried to build this package in stretch with "dpkg-buildpackage -A"
> > but it failed:
>
>
It turned out slightly more complicated, the fallback to AST is was
already in place, but memory available to malloc got exhausted via heap
expansion. Messages starting "Error: compilation failed" mean there was
an error while compiling, including out of memory, and that the AST will
be used -
Jose A. Fernandez Gonzalez wrote, on 8.6.2018 19:32:
[...] I think the problem is that chromium-67 is
looking for ffmpeg-4 and the version available in Debian unstable is
ffmpeg-3.4.2
There is no such dependency specified in the chromium package. That is
certainly wrong.
The changes in
https://salsa.debian.org/debian/timidity/commit/3e768cabe537f2a8a22a51f4eb398a974fe15e25
specifically
timidity.maintscript
rm_conffile/etc/default/timidity2.14.0-1~timidity-daemon
doesn't look correct either.
dpkg-maintscript-helper does not have support for moving
The problem persists with 67.0.3396.62-2.
Processing control commands:
> tags -1 + confirmed
Bug #901114 [src:python-coverage] python-coverage: FTBFS when built with
dpkg-buildpackage -A
Added tag(s) confirmed.
--
901114: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=901114
Debian Bug Tracking System
Contact ow...@bugs.debian.org
Control: tags -1 + confirmed
On 09-Jun-2018, Santiago Vila wrote:
> I'm using "sbuild --arch-all --no-arch-any" on a clean chroot, which
> is what an official autobuilder would do to build the arch-indep
> packages.
Yes, thanks. That allows me to reproduce the behaviour.
> My feeling is that
Dear Santiago Vila, you wrote:
>
> Package: src:yodl
> Version: 4.02.00-2
> Severity: serious
>
> Dear maintainer:
>
> I tried to build this package in stretch with "dpkg-buildpackage -A"
> but it failed:
(etc)
Dear Santiago,
Thx for the bug report. I'll have a look at it asap. As a side
Package: timidity
Version: 2.14.0-2
Severity: serious
When upgrading timidity and timidity-daemon from 2.13.2-41 the following
happened (sorry for the German):
,
| Vorbereitung zum Entpacken von .../timidity_2.14.0-2_i386.deb ...
| Entpacken von timidity (2.14.0-2) über (2.13.2-41+b1) ...
|
Source: primesieve
Version: 7.0+ds-1
Severity: serious
Hi Maintainer
Upstream bumped the SONAME to libprimesieve.so.9, please bump the name
of the library package to libprimesieve9 in order to match.
You should have seen a package-name-doesnt-match-sonames [1] Lintian
warning while preparing
73 matches
Mail list logo
