.
Thanks
Paolo
Package: python3-wxgtk4.0
Version: 4.2.0+dfsg-3
Severity: minor
While updating:
Setting up python3-wxgtk4.0 (4.2.1+dfsg-2) ...
/usr/lib/python3/dist-packages/wx/lib/docview.py:1026: SyntaxWarning: invalid
escape sequence '\*'
"""
/usr/lib/python3/dist-packages/wx/lib/layoutf.py:135:
) worked for me.
Paolo
violation while setting translation unit for unique types
(Closes: #1055637)
+
+ -- Paolo Pisati Thu, 09 Nov 2023 11:29:34 +
+
libabigail (2.4-1) unstable; urgency=medium
* New upstream version.
diff -Nru
libabigail-2.4/debian/patches/0001-Bug-31045-Don-t-try-setting-translation-unit
Source: libabigail
Version: 2.4-1
Severity: normal
Dear Maintainer,
while building the zfs-dkms package in Ubuntu/noble, in the checkabi target,
abidiff core dumps:
https://launchpadlibrarian.net/696568269/buildlog_ubuntu-noble-amd64.zfs-linux_2.2.0-0ubuntu2_BUILDING.txt.gz
abigail-2.3 was
-4
python3-pyvmomi recommends no packages.
Versions of packages python3-pyvmomi suggests:
pn python-pyvmomi-doc
-- no debconf information
Best regards.
Paolo
1. https://github.com/vmware/pyvmomi/pull/732
diff --git a/pyVmomi/VmomiSupport.py b/pyVmomi/VmomiSupport.py
index 925d4a9..b3b7878
On Mon, Sep 04, 2023 at 10:10:05PM +0200, Jeremy Lecour wrote:
Package: proftpd-core
Version: 1.3.8+dfsg-4+deb12u1
Severity: normal
Dear Maintainer,
After upgrading to Debian 12, my SFTP client stopped working with errors when
connecting.
I've opened a GitHub issue and the problem has been
Package: wnpp
Severity: wishlist
Owner: Francesco Paolo Lovergine
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: libmozilla-ca-perl
Version : 20230821-1
Upstream Contact: Gisle Aas
* URL : https://github.com/libwww-perl/Mozilla-CA
* License : MPL
ine
426, in filter
raise exc
sphinx.errors.SphinxWarning:
/<>/documentation/source/specific.rst:195:Invalid C++
declaration: Expected identifier in nested name. [error at 0]
^
> /usr/lib/python3/dist-packages/sphinx/util/logging.py(426)filter()
-> raise exc
(Pdb)
ma
: tex)
Enter file name:
! Emergency stop.
l.211 \input{topics}
^^M
! ==> Fatal error occurred, no output PDF file produced!
Transcript written on refman.log.
I attach the full build log.
Paolo
-- System Information:
Debian Release: trixie/sid
APT pref
error,
aborting now)
make[3]: *** [docs/CMakeFiles/doc_all.dir/build.make:74:
docs/CMakeFiles/doc_all] Error 1
I attach the full build log.
Paolo
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 6
=xelatex)
restricted \write18 enabled.
entering extended mode
(./refman.tex
LaTeX2e <2023-06-01>
L3 programming layer <2023-06-05>
make[2]: *** [Makefile:12: refman.pdf] Error 1
I attach the full build log.
Paolo
-- System Information:
Debian Release: trixie/sid
, inClass)
^
File "/<>/etgtools/extractors.py", line 1185, in __init__
self.extract(element)
File "/<>/etgtools/extractors.py", line 1189, in extract
super(EnumDef, self).extract(element)
File "
,2p,20b,20s
! ==> Fatal error occurred, no output PDF file produced!
make[3]: *** [Makefile:663: stamp-latex] Error 1
I attach the full build log.
Paolo
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: am
to 1.9.7.
I'll take care.
Paolo
I think this long-standing bug can be closed as the explanations
provided on how the reload and force-reload actions work have been
satisfactory.
Regards.
Paolo Miotto
I was able to apply the patch to the network.js file in
/usr/share/webext/eas4tbs...@jobisoft.de.xpi and now it works as expected.
let oauth = new OAuth2(config.scope, {
> authorizationEndpoint: config.auth_uri,
> tokenEndpoint: config.token_uri,
> clientId: config.client_id,
> clientSecret: config.client_secret
> });
Regards.
Paolo
1. https://github.com/jobisoft/TbSync/issu
Package: btrbk
Version: 0.27.1-1.1
I'm using a Raspberry Pi4 with RaspberryOS bullseye. RaspberryOS is
Debian with some modified packages: in particular a personalized
kernel.
RaspberryOS Bullseye has recently updated the kernel to 6.1 (against
Bullseye's 5.10). I have installed the backported
Package: marco
Version: 1.26.1
Severity: important
Hi,
during my tests with commonly used software here, I found that the Mate window
manager is currently unusable under X2go due to a seg fault at startup.
I even found the reason:
https://github.com/mate-desktop/marco/issues/746
fixed in
ong with a solution effective in case of an upgrade.
Regards.
Paolo
? ~600 packages build-depend on
doxygen, I would not want to break havoc
3. reading some threads about enabling large file support for all
packages, I was scared by the issue of ABI breaking, are we 100% sure
that we will not trigger that?
Thanks for you comments,
Paolo
for the NMU. I'll let it go through and afterwards import it back
into the salsa git repo for reference.
Paolo
On Tue, 13 Sep 2022 14:50:00 + Debian FTP Masters
wrote:
> Source: redmine
> Source-Version: 5.0.2-1
[---]
> We believe that the bug you reported is fixed in the latest version of
>redmine, which is due to be installed in the Debian FTP archive.
This bug was reported for version
\
ruby-railties=2:5.2.2.1+dfsg-1+deb10u3 \
ruby-actionmailer=2:5.2.2.1+dfsg-1+deb10u3
Paolo
be nice to have a oneliner I can try at home
to reproduce here the reproducible builds!
Thanks,
Paolo
the greeter to stop.
It looks to me as a race condition.
Probably the PAM system is not yet ready when sddm-helper tries to connect.
Paolo
-- System Information:
Debian Release: 11.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable-security'), (500,
'stabl
Hi! thanks for the quick reaction.
Il 22/07/22 18:01, Sebastiaan Couwenberg ha scritto:
Control: tags -1 upstream
Control: forwarded -1 https://github.com/libgeos/geos/issues/654
On 7/22/22 17:37, Paolo Greppi wrote:
I am about to upload the current version of doxygen, before doing that
I ran
or: "(" unexpected
make[4]: *** [Makefile:30: refman.dvi] Error 2
The errors do not occur with the current version of doxygen (1.9.1). I
attach the build logs.
Paolo
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architec
/ratt_doxygen_1.9.4-1_amd64-partial)
and found that this package FTBFS with this error:
mv: cannot stat 'docs/Doxyfile.bak': No such file or directory
The error does not occur with the current version of doxygen (1.9.1). I
attach the build logs.
Paolo
-- System Information:
Debian Release: bookworm
s and
worth uploading!
Paolo
===
but this does not prevent the package to build (?).
Anyway I m not familiar with this style of tracking only the debian dir
in salsa (I normally use gbp and push the upstream sources as well). How
can you enable salsa CI BTW ?
Paolo
Thanks for your bug report. This is caused by doxygen not reporting dot
failures, which is tracked at bug #818379.
Paolo
Il 15/07/22 00:23, Sebastian Ramacher ha scritto:
On 2022-07-14 16:23:16 +0200, Paolo Greppi wrote:
...
ACK, I've canceled the NMU. Please consider that doxygen is a key
package and thus effectively keeping llvm-toolchain-11 in testing. A
timely fix for this issue would be much appreciated
:
with 1.9.4 I get:
so the build path is not embedded anymore.
If you have time to test yourself, you can try with this package here on
unstable:
https://salsa.debian.org/debian/doxygen/-/jobs/3001759/artifacts/browse/debian/output/
Paolo
I reproduced with the attached minimal example and no warning is printed.
Upstream issue is also closed.
Will now close.
P.
test.tar.xz
Description: application/xz
I reproduced with the attached minimal example and no warning is printed.
Upstream issue is also closed.
Will now close.
P.
test.tar.xz
Description: application/xz
a valid solution for Debian?
Paolo
to doxygen maintenance; for me the preferred way is by means of
Merge Requests on salsa.
MfG,
Paolo
P.S. I also tried reviving the salsa gitlab CI:
https://salsa.debian.org/debian/doxygen/-/commits/bugfix/sramacher/1000932
but ATM the pipeline is failing for unrelated reasons:
https
Package: libnssswitch-nis
Version: 3.1-4
Severity: grave
It seems that currently unstable has a totally not working NIS binding for
users. I
performed my trials using an existing setup (bullseye-based NIS master+slaves
and
clients network in the real life).
I recently upgraded a bullseye NIS
Il 29/05/22 21:34, Pirate Praveen ha scritto:
On തി, മേയ് 30 2022 at 12:56:53 രാവിലെ +05:30:00 +05:30:00, Pirate
Praveen wrote:
On ഞാ, മേയ് 29 2022 at 09:34:45 രാവിലെ +02:00:00 +02:00:00, Paolo
Greppi wrote:
Hi Andreas! thanks for your report. To try to reproduce it, I set
...
Finally
tack: [ 'error:0386:digital envelope
routines::initialization error' ],
library: 'digital envelope routines',
reason: 'unsupported',
code: 'ERR_OSSL_EVP_UNSUPPORTED'
}
error Command failed with exit code 1.
(this also happens on amd64 BTW).
According to the interwebs this should only occur with node v17 (whereas
in unstable we have v16.15.0) and indeed the commonly proposed
workaround fails:
NODE_OPTIONS=--openssl-legacy-provider yarnpkg build
/usr/bin/node: --openssl-legacy-provider is not allowed in NODE_OPTIONS
Paolo
Il 29/03/22 21:24, Simon McVittie ha scritto:
Control: tags -1 + moreinfo unreproducible
On Tue, 29 Mar 2022 at 20:40:03 +0200, Paolo Redaelli wrote:
the Online Account section of gnome control center disappered.
I tried to explicitly invoke it with "gnome-control-center online-acc
Il 29/03/22 21:24, Simon McVittie ha scritto:
Control: tags -1 + moreinfo unreproducible
On Tue, 29 Mar 2022 at 20:40:03 +0200, Paolo Redaelli wrote:
the Online Account section of gnome control center disappered.
I tried to explicitly invoke it with "gnome-control-center online-acc
Package: gnome-online-accounts
Version: 3.43.1-1
Severity: important
Dear Maintainer,
the Online Account section of gnome control center disappered.
I tried to explicitly invoke it with "gnome-control-center online-accounts" and
all I got is this error:
(gnome-control-center:49141):
/modprobe
Connot repeat a full install: maybe you could need the output of some
system command or file?
Thanx,
Pp
l e x h a c k . i t
PIER PAOLO FRANCO
avvocato | diritto tributario e d'impresa
www.lexhack.it // pierpaolo.fra...@lexhack.it /
pierpaolo.fra...@pec.lexhack.it (PEC)
P.Iva 03459781203
On Thu, Jan 13, 2022 at 05:06:29PM +1100, Trent W. Buck wrote:
Francesco,
Is dbus-user-session installed?
xfce4-session recommends dbus-user-session, so
it SHOULD already be installed.
As explained this is a bug found casually while using testing64, at the stage
of its development in that
this yarn.js binary.
Sorry for the long message, this is a mess!
Paolo
bel7-runtime which is listed as a "dep" of yarnpkg here:
https://packages.debian.org/bullseye/yarnpkg
Is it possible that on your system you have installed some non-Debian
node module that takes precedence over the ones installed by the Debian
packages?
Paolo
t;
1:3.1+dfsg-1~), qemu-utils (<< 1:3.1+dfsg-3~)
Replaces: qemu-system-data (<< 1:3.1+dfsg-1~), qemu-utils (<< 1:3.1+dfsg-3~)
Homepage: http://www.qemu.org/
As you can see, it breaks libvirt-daemon < 7.2.0-1.
It would be great if you backported the 7.6.0-1 version of
libvirt-daemon in bookworm to bullseye-backports.
--
Mandi.
Paolo
Package: libmutter-9-0
Version: 41.1-1
Severity: important
X-Debbugs-Cc: pierpaolo.fra...@gmail.com
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Update libmutter to 41 or 40
* What exactly did you do
Package: release-notes
Severity: normal
NIS does not more use debconf for its initial installation. While existing
setups should smoothly upgrade to the new multi-package organization,
the recommended configuration way in bullseye is by following the nis-howto
document included in the `nis`
See https://bugs.debian.org/985857
Paolo
there is no activity in #985857 yet, so it's basically up for
anyone to pick it (we welcome new contributors ;-).
Paolo
Indeed, the general NIS howto included in the nis package provides the full
documentation for who upgrades or install both servers and clients. A small per
program README could probably be a good idea for minimal setup. My original
idea was having the nis package as a doc only package after
I suppose 1.1.16 does not solve the underlying issue of gmusicbrowser
relying on gtk2.
However 1.1.99.1 beta is out supporting gtk3, so it might be worth
packaging for experimental!
Development is active upstream. Not frenetic, but definitely not dead.
Paolo
Package: krb5-kdc
Version: 1.18.3-4
Severity: minor
Syslog warns about that.
systemd[1]: /lib/systemd/system/krb5-kdc.service:7: PIDFile= references a path
below legacy directory /var/run/, updating
/var/run/krb5-kdc.pid → /run/krb5-kdc.pid; please update the unit file
accordingly.
-- System
On Wed, Feb 03, 2021 at 02:58:27PM +0200, Juhani Numminen wrote:
Package: manpages-posix
Version: 2017a-1
Severity: grave
Hello,
The latest upload of manpages-posix was source-only but was not built
on the buildd network either. So, no binaries are available.
I think the text of this lintian
On Tue, Feb 02, 2021 at 09:37:00AM +0300, Sergey B Kirpichev wrote:
tags 981459 +wontfix
thanks
No.
Please read README.Debian.
I see, indeed the only reason to have it still around is my laziness :-)
Ok, let it to go as a ruin of the past...
--
Francesco P. Lovergine
Package: fetchmail
Version: 6.4.15-1
Severity: wishlist
Please, add at least a proper systemd service unit file as current systemd
complains about that at every restart:
systemd-sysv-generator: SysV service V'/etc/init.d/fetchmail' lacks a native
systemd unit file.
Automatically generating a
Package: hddtemp
Version: 0.3-beta15-53
Severity: wishlist
Please, provide a native systemd service support, as current systemd complains
about the missing of a proper unit file.
systemd-sysv-generator: SysV service '/etc/init.d/hddtemp' lacks a native
systemd unit file. Automatically
Package: monit
Version: 1:5.27.2-1
Severity: wishlist
As taken from syslog at every restart:
systemd-sysv-generator: SysV service '/etc/init.d/monit' lacks a native systemd
unit file. Automatically generating a unit file for compatibility.
Please update package to include a native systemd unit
Package: vtun
Version: 3.0.4-2
Severity: wishlist
As taken from syslog, at every restart of services:
systemd-sysv-generator: SysV service '/etc/init.d/vtun' lacks a native systemd
unit file. Automatically generating a unit file for compatibility. Please
update package to include a native
Package: sasl2-bin
Version: 2.1.27+dfsg-2
Severity: wishlist
Please, provide a systemd unit file for sasl-auth and help to reduce
systemd-sysv-generator verbosity at boot time about a missing one.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500,
Package: bitlbee-common
Version: 3.6-1.2
Severity: normal
Please, help to reduce the noise of systemd-sysv-generator in syslog by
providing a
proper unit file for bitlbee.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing'), (1,
Package: systemd
Version: 247.2-5
Severity: wishlist
Tags: upstream
This is the result of rebooting one of my boxes with bullseye:
$ sudo dmesg|grep 'lacks a native systemd'|wc -l
463
It gives the same message for tons of init scripts and even for scripts that are
there for historical reasons
-actual.diff#L26
and the autopkgtest baffles me:
https://salsa.debian.org/js-team/node-yarnpkg/-/jobs/1387234#L273
I have parked my work in the wip/paolog/jest branch.
I'll release 1.22.10+~cs22.25.14-2 without the test suite FTMB, we can pick it
up from there later.
Paolo
The option was added with devscripts 2.20.5:
https://lists.debian.org/debian-perl/2020/11/msg00047.html
Please upgrade devscripts so that uscan works reliably for packages that use
the option.
BTW thanks for the excellent service! Paolo
-- System Information:
Debian Release: bullseye/sid
APT
Dear Xavier,
Il 27/01/21 06:30, Xavier ha scritto:
Le 27/01/2021 à 00:14, Paolo Greppi a écrit :
I fixed the error:
Cannot find module 'babel-preset-env'
but I am not sure if the fix is 100% right.
Now I get:
TypeError: Cannot read property 'mkdir' of undefined
5
s-team list:
https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2021-January/052152.html
Paolo
uot;:
https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2021-January/052128.html
Thanks, Paolo
sa.debian.org/js-team/node-yarnpkg/-/jobs/1373973
I tried the obvious fix in debian/tests/control:
-Depends: @, jest
+Depends: @, jest, node-babel-preset-env
but no change.
Paolo
I tried using the docker "official image" for node:
docker pull node
docker run -it --rm node bash
mkdir -p test/foo
cd test
yes '' | yarn init
yarn add file:foo
yields:
yarn add file:foo
yarn add v1.22.5
info No lockfile found.
[1/4] Resolving packages...
[2/4] Fetching
dependencies
└─ foo@1.0.0
Done in 0.25s.
Paolo
Hi I see "pass" for clazy/1.9-3 with llvm-toolchain-11/1:11.0.1-2:
https://ci.debian.net/packages/c/clazy/testing/amd64/
I also tried this here on unstable and the autopkgtest did pass.
Can you check and if confirmed as fixed close this bug?
Thanks,
Paolo
pocl 1.6-3 has migrated to testing on 2021-01-13, and upstream declares that v1.6
includes "Support for Clang/LLVM 11".
Can you try your reproducer now ?
Thanks
Paolo
Package: offlineimap
Version: Required dependency now available in main.
Severity: normal
As reported in d/changelog:
Patch OfflineIMAP to remove 'Happy Eyeballs' functionality.
The code relies on the rfc6555 Python package, which is not available on
Debian.
rfc6555 is now available in Debian.
Dear Melvin,
Il 14/01/21 13:51, Melvin Vermeeren ha scritto:
Hi Paolo,
On Thursday, 14 January 2021 10:28:32 CET Paolo Greppi wrote:
Doh I had not seen this: https://bugs.debian.org/976227
Let me put both the future Debian maintainer and the current upstream
maintainer in Cc.
Thanks
://salsa.debian.org/salsa-ci-team/pipeline) is active in my repo
and most tests have passed:
https://salsa.debian.org/paolog/breathe/-/pipelines/218933
This is blocking the new minor version of doxygen from entering testing.
Please push the fix through soon !
Paolo
4de3.patch
This is blocking the new minor version of doxygen from entering testing.
Paolo
Il 08/01/21 11:35, Jonas Smedegaard ha scritto:
Quoting Paolo Greppi (2021-01-08 08:46:36)
I guess that's because the bullseye-slim image lacks the manpages.
A Debian install with man pages excluded seems to be an unsupported
system: Whatever hooks applied to do that trick should be extended
Should it not just be a build-dep ?
Paolo
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 5.9.0-4-amd64 (SMP w/12 CPU threads)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_WARN
Package: cloud.debian.org
Severity: normal
While upgrading the current debian/current-testing64 (half of 2020) under
virtualbox provider:
[...]
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 5.9.0-5-amd64:Error! Your
kernel headers for kernel 5.9.0-5-amd64
recommend buildah ?
Or should /etc/containers/policy.json be installed by a new package from which
both skopeo and buildah depend ?
Thanks,
Paolo
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (500, 'testing'), (400, 'unstable'), (1, 'experimental
Package: offlineimap
Version: 7.3.3+dfsg1
Severity: normal
Offlineimap does allow multiple ways of installing services via systemd as
suggested by manual and examples. The package should also install required unit
files and allow users to enable/start at their will, which could be useful
in
Il 02/01/21 02:51, Scott Talbert ha scritto:
On Sat, 2 Jan 2021, Paolo Greppi wrote:
The ext/wxWidgets/docs/doxygen/out/xml dir produced with doxygen 1.8.20 is 50
MB and contains 1812 files.
The ext/wxWidgets/docs/doxygen/out/xml dir produced with doxygen 1.9.0 is 42 MB
and contains 1583
produced with doxygen 1.9.0 is 42 MB
and contains 1583 files.
I attach the list of contained files.
This could well be a doxygen issue. Please let me know what you think about it.
I am not yet 100% sure that it makes sense to rush doxygen 1.9.0 to bullseye,
but I might try, and if so, I'll increase th
libvigraimpex_1.11.1+dfsg-7.xz
Description: application/xz
hon script to
be more lax with Unicode errors.
I am not yet 100% sure that it makes sense to rush doxygen 1.9.0 to bullseye,
but I might try, and if so, I'll increase the severity of this bug to serious.
Paolo
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT
akes sense to rush doxygen 1.9.0 to bullseye,
but I might try, and if so, I'll increase the severity of this bug to serious.
Paolo
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable-debug
APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental')
Architectur
-yarnpkg/-/jobs/1287491
Not sure how to proceed ..
Paolo
ed, 111 total
Time:74.936s
Ran all test suites matching /__tests__\//i.
I think we can include it in the autopkgtest, later we can try to understand
why some tests are failing ..
Note:
https://alioth-lists.debian.net/pipermail/pkg-javascript-devel/2020-November/047062.html
Paolo
in upstream and master branches:
https://wiki.debian.org/Javascript/GroupSourcesTutorial
Paolo
cd `mktemp -d`
yarnpkg init -y
yarnpkg add d3-color
Adding the nodeLinker: "node-modules" option to ~/.yarnrc.yml or the global
locations does not help.
It would be interesting to debug the JavaScript execution after it prints "Fetching
packages..."
Paolo
Source: proftpd-dfsg
Version: 1.3.7a+dfsg-2
Severity: serious
After upgrade:
$ sudo proftpd -t
Checking syntax of configuration file
2020-12-14 09:59:09,942 legolas proftpd[5444]: mod_dso/0.5: unable to load
'mod_tls.c'; check to see if '/usr/lib/proftpd/mod_tls.la' exists
2020-12-14
/ criticality serious to make sure the new TL packages do not migrate to
testing until the issue is sorted out.
Hilmar
well done !
Paolo
saying IMHO we shouldn't be mad at debian for what happened, just hope
someone will find a way to fix it.
Paolo
Il lun 7 dic 2020, 02:12 Del Fernandes ha scritto:
> It was quite disappointing to see (or not see) the GUI/WM stop working
> after a causal system update (not upGrade).
>
>
@jim_p Is it possible for you to avoid putting all system information
and Xorg logs in every message?
It makes the thread very difficult to follow on the online bug tracker.
I too rolled back to linux-image-5.9.0-3-amd64 which works, hope it
won't be my very last kernel version.
://bugs.debian.org/976405#10
It would be interesting to know when you last run the archive rebuild on arm64
or amd64, because it's not clear since when this error happens.
Paolo
Hi Norbert,
Il 04/12/20 23:29, Norbert Preining ha scritto:
Hi Paolo,
/usr/bin/pdflatex: Not writing to
../html/examples/group/latex//group__group2.aux (openout_any = p).
make[4]: *** [doc/CMakeFiles/doxygen_pdf.dir/build.make:81:
doc/CMakeFiles/doxygen_pdf] Error 1
Is this new
1 - 100 of 1908 matches
Mail list logo
