Package: sogo
Version: 4.0.4-1
Severity: important
Dear Maintainer,
* What led up to the situation?
New installation of sogo on a clean debian buster machine
* What exactly did you do (or not do) that was effective (or
ineffective)?
Configured sogo with ldap backend and
On Sat, Nov 24, 2018 at 02:55:20PM +0100, Axel Beckert wrote:
> > It's coordinated, it started 3 days ago, but since then pochu have yet
> > to trigger the rebuilds...
>
> IIRC pochu also did parts (if not most) of the near-perfect Perl 5.28
> transition I was refering, too.
Yes, pochu deals
Hi Mattia,
Mattia Rizzolo wrote:
> > JFTR: I see quite some issues like this, but no transition hints in
> > neither the PTS nor the Package Tracker. And there was also no
> > announcement on d-d-a like for the (compared to this very smooth) Perl
> > transition. (If I would have seen a hint on a
Hi,
On 11/24/18 2:19 AM, Cesare Leonardi wrote:
>
> On Sat, 24 Nov 2018 01:08:56 +0100 Hans van Kranenburg
> wrote:
>> You didn't share any part of your logging. Can you share a part of dmesg
>> logging that shows Oops in it?
>
> Here it is, attached to this message.
> Previously I didn't
Package: ftp.debian.org
X-Debbugs-Cc: rar...@packages.debian.org
Affects: src:rarian
Tags: moreinfo
Control: block -1 by 885638
Please remove rarian from Debian. Its last release was a decade ago.
.omf files are no longer needed for displaying DocBook help files.
There is one package still
Hi,
Il 22/10/18 20:59, Andreas Beckmann ha scritto:
> Just an idea, do not know if this can be implemented efficiently:
>
> If libboost-python1.62.0 provides pythonX.Y-libboost-python1.62.0
> and the consumers depend on pythonX.Y-libboost-python1.62.0 instead of
> (or in addition to)
Per upstream; this seems to be a kernel bug which is fixed in 4.18.20.
Unclear whether the fix (1e9c75fb9c47a75a9aec0cd17db5f6dc36b58e00) can be
cherrypicked back to current stable / bpo kernels; investigating.
Hi,
Axel Beckert wrote:
> for a few days now, the python3 metapackage is at 3.7.1-… and since then
> sigil became uninstallable in Sid due to its dependency on "python3 (<<
> 3.7)".
>
> A rebuild/BinNMU against the newer python3 package might already fix
> this.
JFTR: I see quite some issues
Wow... ...your message coincided with a report of a bad bug I had to
correct, too => mentors now contains an updated package with a new
service release of wxMaxima.
Thanks a lot!
and
Kind regards,
Gunter.
On 24.11.18 13:02, Adrian Bunk wrote:
> Package: wxmaxima
> Version: 18.10.2-1
>
Package: sigil
Version: 0.9.10+dfsg-1
Severity: serious
Hi,
for a few days now, the python3 metapackage is at 3.7.1-… and since then
sigil became uninstallable in Sid due to its dependency on "python3 (<<
3.7)".
A rebuild/BinNMU against the newer python3 package might already fix
this.
--
Hello Faustin,
I had the same issue. Then commented out the audit plugin lines in the
configuration file, finished the upgrade and un-commented them again.
These are my configuration files (with some info removed):
# cat /etc/mysql/mariadb.cnf | grep -v ^#
[client-server]
Source: cdo
Version: 1.9.6~rc4-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=cdo=sid
...
/usr/bin/ld: cdo-Gradsdes.o: in function `Gradsdes(void*)':
./src/Gradsdes.cc:1293: undefined reference to `pstreamInqGRIBinfo(int, int*,
float*, long*)'
collect2: error: ld
Source: cppcheck
Version: 1.85-1
Severity: serious
Tags: ftbfs
https://buildd.debian.org/status/package.php?p=cppcheck=sid
...
Testing Complete
Number of tests: 3289
Number of todos: 208
Tests failed: 2
test/testsymboldatabase.cpp:5164: Assertion failed.
Expected:
1
Actual:
0
_
Dear Maintainer, hello Klaus Ethgen,
I just tried to get some more information out of this bug.
I could not reproduce it with a stretch testing or unstable
as of date 2016-07-20 inside a i386 qemu VM.
As far as I see is the problematic function in WDM:
(gdb) list ManageSession#
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: binnmu
The following packages have unmet dependencies:
dovecot-antispam : Depends: dovecot-abi-2.3.abiv3 but it is not installable
nmu dovecot-antispam_2.0+20171229-1 . ANY . unstable . -m
Control: tags -1 moreinfo
On Sat, Nov 24, 2018 at 12:34:52AM +0100, Gunter Königsmann wrote:
>...
> Changes since the last upload:
>
> * New upstream release that drastically improves the drawing speed, provides
> a better lisp mode,
>improves the loop of the program and fixes many bugs
Package: wxmaxima
Version: 18.10.2-1
Severity: minor
The Homepage filed points to a no longer exisiting page,
current upstream seems to be
http://wxmaxima-developers.github.io/wxmaxima/
Well, it's too late for turkey stuffing. Any hopes for stockings ? What
is the "copyright question" you're alluding to ?
I also noted that there does not seem to be any unversioned version of
the docs (emacs-common-non-dfsg) : the package is known to dpkg, but
uninstallable. One has to install
Le samedi 24 novembre 2018 à 11:43 +0100, Rafael Laboissière a écrit :
> [Moving this discussion from Bug#914373 into debian-octave.]
>
> * James Van Zandt [2018-11-22 13:34]:
> >
> > [snip]
> >
> > Please provide a file /usr/share/doc/octave-
> > statistics/README.Debian
> > with a note
Adrian Bunk wrote...
> Any update on that?
As I wrote in the previous message, allow me until end of November to
create the fixes. This still is my plan.
Christoph
signature.asc
Description: PGP signature
Note, that the package split has been reverted in
0.11~hg20181007.7c1cdf5f9f83-2, because other team members
objected.
[Moving this discussion from Bug#914373 into debian-octave.]
* James Van Zandt [2018-11-22 13:34]:
[snip]
Please provide a file /usr/share/doc/octave-statistics/README.Debian
with a note something like
By default installed packages are not available from the Octave
prompt. The
Op vr 23 nov. 2018 om 10:55 schreef Christos Trochalakis
:
> >What about ExecStartPre?
>
> It's already at `ExecStartPre=` [0], the problem is that in `systemd
> restart nginx` ExecStartPre is executed **after** the service is
> stopped, not in the start of the sequence.
In that case, does it
Control: tags -1 pending
This is fixed by applying the Ubuntu patch; see
https://salsa.debian.org/debian-astro-team/python-casacore/commit/e9c03147
However, it currently does not build due to another problem connected
with the recent casacore transition.
Hi,
On Sat, Nov 24, 2018 at 11:07:25AM +0100, Rene Engelhard wrote:
> Did a rebuild using ratt and (almost) all packages built fine, except
> some otherwise failing packages (mudlet and plume-creator (both sid
> only) because of #907159 and #887534)
Sorry, missed one: aegisub (also sid-only):
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: transition
hunspell 1.7 was finally released. It includes a load of fixes
we miss e.g. in LibreOffice because instead of using the
patched-internal version we use the system version.
Cleared NEW
Package: gimp-plugin-registry
Version: 9.20180625
Followup-For: Bug #907178
Dear Maintainer,
indeed, it seems resynthesize is currently broken, one cannot use the "Heal"
filters. That's a bummer, these filters are the only reason I have
gimp-plugin-registry installed to begin with.
Kind
Package: dpkg
Version: 1.19.2
Severity: wishlist
Hi,
lintian recently tagged mmdebstrap with uses-dpkg-database-directly
because mmdebstrap contains the string "/var/lib/dpkg" in several
places. Instead of overwriting the lintian tag in mmdebstrap, dpkg could
also gain an interface which avoids
Hi,
Il 22/11/18 20:39, Adrian Bunk ha scritto:
> I don't know, adding the boost maintainers to Cc for that.
I posted a new bug to discuss the issue of Python links. Please, follow
the discussion there and bring your contribution if necessary.
Package: atop
Version: 2.3.0-1+b1
Severity: normal
Dear Maintainer,
In managing my log directory and customize logrotate, I discovered
limitations in the way atop handles log files (which are different
from text files since they are process accounting files,, to my
understanding).
Can this
Package: boost1.67
Version: 1.67.0-10
Severity: important
Hi,
the symbolic links created in Python-related Boost packages are
currently inconsistent, both with the past and between themselves. While
some change was actually intended to happen, the current situation does
not seem ideal. This bug
>
> Please consider to upgrade to the current upstream version of qemu
> (3.0.0).
>
Actually IMHO we are just 11 days away from 3.1 [1]
Maybe do the work just once and directly prep 3.1 instead of doing ->3.0
and then ->3.1 later?
[1]: https://wiki.qemu.org/Planning/3.1
Package: php-apcu
Version: 5.1.12+4.0.11-2
Severity: normal
Dear Maintainer,
Most of the other PHP packages are prefixed with the version number, for
example "php7.2-gd", "php7.2-curl", etc. This allows multiple PHP versions to
be installed side-by-side.
However, the APCU package is just
On Fri, Nov 16, 2018 at 03:14:36AM +0100, Axel Beckert wrote:
> Hi,
>
> Tobias Frost wrote:
> > Yes, we're are on it (however, I hoped to dedicate a bit more time to
> > this week)
>
> Before creating a VCS repo for it: I wonder why the package is ITP'ed
> as "backuppc-rsync" despite upstream
> So shall we start with 3.0.9.12 or 3.1.2.beta0? (I tend to stay on the
> safe side and start with 3.0.9.12, but then we at least should try to
> apply all security updates against rsync 3.0.9 in Wheezy.)
I think you can use rsync 3.1.2, in my git I had a working version
based on 3.1.2:
I am sorry, I don't understand the explanation for closing this bug. It
happens out of the box (fresh install) for various applications, on
different machines without having any user modifications done. So I have
to assume some more global issue.
How can the average user be expected to dig out
On Sat, Nov 24, 2018 at 08:45:21AM +0100, Sebastiaan Couwenberg wrote:
> tags 914489 wontfix
> thanks
>
> Hi Alberto,
>
> On 11/23/18 9:26 PM, Alberto Gonzalez Iniesta wrote:
> > After updating nagios-nrpe-plugin in my monitoring host to
> > 3.2.1-1~bpo9+1 most of my monitored instances fail to
101 - 137 of 137 matches
Mail list logo
