Package: wnpp
Severity: wishlist
* Package name: flashprog
Version : 1.0
Upstream Contact: Nico Huber
* URL : https://flashprog.org/
* License : GPL
Programming Lang: C
Description : Identify, read, write, erase, and verify BIOS/ROM/flash
chips
Forgot to mention, there's nothing going on about flashrom-stable on
the web page yet. Instructions how to fetch the source code and more
can be found in the release announcement:
https://mail.coreboot.org/hyperkitty/list/flashrom-sta...@flashrom.org/thread/HSHMBX7ZWPJC6MSAUMRKNHYBDFQLMIDJ/
Nico
Package: wnpp
Severity: wishlist
X-Debbugs-Cc: nic...@gmx.de
* Package name: flashrom-stable
Version : 1.0
Upstream Contact: Nico Huber
* URL : https://www.flashrom.org/
* License : GPL
Programming Lang: C
Description : Identify, read, write, erase
or directory
This occurs on a debian-edu deployment which has been in use for about a
year
and I could also reproduce this behavior locally on a fresh install with one
mainserver VM an one romaing-workstation VM.
Regards
Nico Winkelsträter
--
Mit freundlichen Grüßen
Nico Winkelsträter
Trainee
to code.ungleich.ch, referencing this thread.
> I might also do a QA upload fixing these issues. No promises though,
> as I'm a bit out of time these days.
Thanks a lot Axel, much appreciated.
Best regards from Paris,
Nico
--
Sustainable and modern Infrastructures by ungleich.ch
just for the record:
I tried to install debian with a recent usb image to a Fujitsu
Lifebook E558 and also this error.
N.
Dear Maintainer,
thanks a lot for your fast and great answer.
I try php7.4-fpm on debian 11 and the startup time was acceptable.
After that i try the php7.3-fpm at debian 10 and got the same issues
(timeout).
The service did not start after boot, sometimes.
I try some more research and found
hello,
i ve some more log entries:
2022-06-09 07:28:12: server.c.1513) server started (lighttpd/1.4.59)
2022-06-09 07:28:16: gw_backend.c.944) gw - found a host 0
2022-06-09 07:28:16: gw_backend.c.944) gw - found a host 0
2022-06-09 07:28:16: gw_backend.c.228) got proc: pid: 171 socket:
Package: lighttpd
Version: 1.4.59-1+deb11u1
Severity: normal
Dear Maintainer,
we use an faster sd-card in our embedded system, nothing else.
Now the start from the lighttpd server takes often over an minute.
we use debian 10, for the bug submit i upgrade to bullseye, but the behaviour
is the
object src/CMakeFiles/mikado.dir/nonlinear_solver.cpp.o
make[2]: *** No rule to make target '/usr/lib/x86_64-linux-gnu/libdl.so', neede
```
Not sure what's going wrong, but looks like an outdated build on Debian's side.
Any hints?
Cheers,
Nico
[1] https://github.com/nschloe/mikado
-- System I
Yeah, that's a little weird. And it only occurs on i386? Sounds like a
CGAL bug then.
On Wed, Oct 13, 2021 at 3:24 PM Drew Parsons wrote:
>
> On 2021-10-13 13:42, Nico Schlömer wrote:
> > Or PR upstream. I can merge and release any time.
>
> Thanks Nico. I'll check which t
Or PR upstream. I can merge and release any time.
Cheers,
Nico
On Wed, Oct 13, 2021 at 1:39 PM Drew Parsons wrote:
>
> Not entirely unexpected. Upstream reorganized tests and tolerances, so
> I wanted to check if we had a full pass or not.
> Looks like we'll have
I posted some updates to the packaging of briar-headless in [0] which is
currently blocking this ITP.
tl;dr: Plans to get into next Debian stable release were given up and
The Briar Project will now focus on setting up their own APT repository [1].
[0]
I posted some updates to the packaging of briar-headless in [0] which is
currently blocking this ITP.
tl;dr: Plans to get into next Debian stable release were given up and
The Briar Project will now focus on setting up their own APT repository [1].
[0]
Some updates on this:
* The Briar Project now offers official briar-headless.jar files at e.g. [0]
* briar-headless in Debian main is not only blocked by Kotlin, but also
by Gradle; both need to be packaged with recent versions before
packaging briar-headless can start
* Additionally, each
Package: wnpp
Severity: wishlist
Owner: Nico Alt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: briar-headless
Version : 1.2.9
Upstream Author : The Briar Project
* URL : https://briarproject.org/
* License : GPLv3
Programming Lang: Java
Package: wnpp
Severity: wishlist
Owner: Nico Alt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: python3-briar-wrapper
Version : 0.0.4
Upstream Author : Nico Alt
* URL : https://code.briarproject.org/briar/python-briar-wrapper
* License
Package: wnpp
Severity: wishlist
Owner: Nico Alt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
* Package name: briar-gtk
Version : 0.1.0
Upstream Author : Nico Alt
* URL : https://code.briarproject.org/briar/briar-gtk
* License : AGPLv3
Programming Lang
ches
his itch, too.
Best regards,
Nico
--
Modern, affordable, Swiss Virtual Machines. Visit www.datacenterlight.ch
FYI, I've added an Ubuntu PPA for it.
Cheers,
Nico
[1] https://launchpad.net/~nschloe/+archive/ubuntu/waybar
Upstream dev here. The location is
```
share/paraview-5.8/plugins
```
now, that's already for 4.0.16.
Cheers,
Nico
On Mon, Jul 20, 2020 at 9:03 AM Drew Parsons wrote:
>
> Package: meshio-tools
> Followup-For: Bug #964078
>
> Thanks for your report. Looks like the symlink might
Thanks a lot for your quick reaction, Martin!
I can confirm this bug to be fixed by now, as I just updated apt and
were able to install dino-im from buster-backports. Thankfully, no chat
history got lost.
y left without any
dino-im client.
Regards
Nico
-- System Information:
Debian Release: 10.4
APT prefers stable-updates
APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-9-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US
Package: ceph-common
Version: 14.2.9-1~bpo10+1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Installing ceph
* What exactly did you do (or not
The test tolerance has already been relaxed for Debian in the latest release.
On Sat, Feb 22, 2020 at 2:48 PM Matthias Klose wrote:
>
> Package: src:pygalmesh
> Version: 0.5.0-4
> Severity: serious
> Tags: sid bullseye
>
> pygalmesh fails it's own autopkg tests:
>
> [...]
> autopkgtest
5 sda5_crypt
[...]
sudo mount --bind /dev /mnt/dev
[...]
Cheers
Nico
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=950556
Just can just relax the relative tolerance to 2.0e-3 with a patch,
I'll include in the next release.
Cheers,
Nico
On Mon, Dec 30, 2019 at 3:27 PM Graham Inggs wrote:
>
> Control: reopen -1
>
> Hi Drew
>
> The test gets a little further
Package: python3-dolfin
Version: 2019.1.0-7
Severity: normal
I don't know if this is a bug in the package or in my system. With the simplest
of python dolfin projects, I'm getting
```
--- Start compiler output
/usr/bin/ld: cannot find -lmpi
collect2:
It's fixed upstream, I released a new version and Drew is on it
bumping the version in Debian. [1]
[1] https://github.com/nschloe/pygalmesh/issues/56
On Fri, Dec 6, 2019 at 2:30 PM Joachim Reichel
wrote:
>
> > Upstream 0.5.0 now builds against CGAL 5, so we only need an upload here.
>
> What do
Upstream 0.5.0 now builds against CGAL 5, so we only need an upload here.
Package: python-numpy
Version: 1.16.0
Severity: wishlist
Since version 1.17.0, numpy's own blas detection order is
mkl,blis,openblas,atlas,accelerate,blas
The first one available on Debian is BLIS, so perhaps it's time to think about
replacingthe BLAS dependency with BLIS.
Cheers,
Nico
Alright, thanks for the update! (I didn't even know there was discussion
about git atm.)
On Fri, Nov 8, 2019, 5:40 PM Joachim Reichel wrote:
> tag 944361 +pending
> thanks
>
> Hi,
>
> I did not see any release announcement for CGAL 5.0 final yet, only for
> Beta 2.
>
> Thanks for your offer to
Package: libcgal-dev
Version: 4.14-5
Severity: wishlist
File: cgal
CGAL 5.0 has been released this afternoon.
I'd love to take a stab at it, but apparently the debian sources aren't on
salsa yet. Any chance of moving them there?
-- System Information:
Debian Release: buster/sid
APT prefers
Any idea what is causing this?
I've fixed this upstream in 3.2.2, upload coming in soon.
On Sat, Oct 19, 2019 at 11:51 PM Matthias Klose wrote:
>
> Package: src:python-meshio
> Version: 3.1.6-1
> Severity; serious
> Tags: sid bullseye
>
> Trying to setup the package with pytho3-defaults installed from experimental,
> the
Upstream recommends against using MPI [1], so we should probably stick to that.
You can always use meshio [2] to convert between mesh formats.
Cheers,
Nico
[1] https://gitlab.onelab.info/gmsh/gmsh/issues/502#note_6582
[2] https://github.com/nschloe/meshio
On Tue, Sep 3, 2019 at 1:51 PM
,
Nico
[1] https://www.mmgtools.org
[2] https://github.com/MmgTools/mmg
[3] https://salsa.debian.org/science-team/mmg
-- System Information:
Debian Release: buster/sid
APT prefers eoan
APT policy: (500, 'eoan')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.2.0-8
ftp.
Hope this helps. This has been bugging me for a while now and I've got no idea
what this is.
Thanks!
Nico
set ftp:passive-mode yes
set ftp:ssl-allow yes
set ftp:ssl-allow-anonymous no
set ftp:ssl-auth TLS
set ftp:ssl-data-use-keys yes
set ftp:ssl-force yes
set ftp:ssl-protect-data yes
set ftp:ssl-p
Package: vtk7
Version:
VTK 8 is now out for about two years (June 2017). Perhaps we should
start supporting it?
cf.
https://stackoverflow.com/questions/55801777/set-compile-flags-when-installing-python-c-project
On Fri, May 3, 2019 at 10:29 AM Drew Parsons wrote:
>
> On 2019-05-03 16:24, Nico Schlömer wrote:
> >> Do you know how to control it?
> >
> > I'd been looking at this
> Do you know how to control it?
I'd been looking at this once, to no avail. Locally I just use CC=clang++ now.
On Fri, May 3, 2019 at 10:11 AM Drew Parsons wrote:
>
> On 2019-04-29 15:49, Nico Schlömer wrote:
> >> No easy way around it.
> >
> > Indeed.
> &g
> No easy way around it.
Indeed.
> Building with -g -O1 (or -O2 without -g) helps mshr, we can test if it helps
> pygalmesh too.
Removing `-g` almost certainly improves things. Using clang++ instead
of c++ also helps.
On Mon, Apr 29, 2019 at 9:06 AM Drew Parsons wrote:
>
> Source: pygalmesh
This could all be fixed in master (where we have Gmsh 4.3.0). Should
perhaps be uploaded soon.
On Wed, Apr 24, 2019 at 8:33 PM Juhani Numminen
wrote:
>
> Control: retitle -1 gmsh: FTBFS in buster
> ("/usr/include/occt/Standard_Version.hxx" cannot be read)
>
>
> Hi,
>
> I believe the relevant
Dear Mika, dear Michael,
thank you for your answers and apologies for answering them so late.
Am 07.03.2019 um 09:15 schrieb Michael Prokop:
* Nico Haase [Thu Mar 07, 2019 at 08:33:57AM +0100]:
Package: systemd
Version: 241-1~bpo9+1
Severity: normal
Dear Maintainer,
this morning
questions rather than providing a solution on
my own, but I'm not that experienced with iptables. I've seen it
throwing an error during an update and this looks like a bug to me. I'd
be very happy if you could guide me to the neccessary steps of providing
more information to inspect this.
Regards
Nico
and that there might be some things that could work in another
way due to a legacy version, but still: how could saving the rules with
the current version result in a file that the current version cannot parse?
Regards
Nico
Hi Gustavo,
thanks for your answer so far!
Am 02.12.2018 um 04:45 schrieb gustavo panizzo:
Hello
On Sat, Dec 01, 2018 at 04:27:19PM +0100, Nico Haase wrote:
Nov 29 06:42:10 host netfilter-persistent[24163]: run-parts: executing
/usr/share/netfilter-persistent/plugins.d/25-ip6tables start
Nov
ration.
What can I do to make this work? Is it a configuration problem on my server, or
a bug in the package?
Regards
Nico
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (700, 'testing'), (500, 'stable-updates'), (500, 'stable')
Architecture: i386 (i686)
Kernel:
As a side note: Can we include the optional dependency on PETSc for the new
Gmsh? I'm getting mesh generation errors without (see
https://github.com/nschloe/pygmsh/pull/214).
Cheers,
Nico
On Tue, 4 Sep 2018 07:29:46 +0200 =?UTF-8?Q?Nico_Schl=C3=B6mer?= <
nico.schloe...@gmail.com> wrote:
&
ndency on PETSc.
Cheers,
Nico
Where can I find this work. (Need Gmsh 4 for another project.)
Cheers,
Nico
Hi itd,
the license change for debian patches is fine!
Cheers,
Nico
--
Nico Golde - XMPP: n...@jabber.ccc.de - GPG: 0xA0A0
signature.asc
Description: PGP signature
Hi,
* Paride Legovini [2018-08-01 22:31]:
> Nico Golde wrote on 29/07/2018:
> > * Paride Legovini [2018-07-29 19:52]:
[...]
> The Debian packaging is Copyright (C) 2009, Nico Golde
> and is licensed under the GPL, see `/usr/share/common-licenses/GPL-2'.
>
> Does this mea
Hi,
I just realized I haven't responded to this bug ever. I'm very short on time
at the moment and in fact will retire my Debian account soon. If you or anyone
is interested in hijacking this package, please go ahead!
Kind regards,
Nico
--
Nico Golde - XMPP: n...@jabber.ccc.de - GPG
Source:lftp
Severity:wishlist
Hey Noël,
Could you update lftp to 4.8.3? This brings some useful features such as
the parallel option for mget.
Thanks!
Nico
--
Nico Golde - XMPP: n...@jabber.ccc.de - GPG: 0xA0A0
signature.asc
Description: PGP signature
I've had that issue in the past, but never bothered looking into it. Me,
I'll hold out for 2018.1 (which kills Python 2 support) to fix these kind
of bugs.
Cheers,
Nico
On Fri, Apr 13, 2018 at 4:54 PM Fabrice Silva <si...@lma.cnrs-mrs.fr> wrote:
> Additional information from Joha
I've been running my desktop with the libinput version 1.10.3-2 and
touchpad enabled for hours now, so I consider this bug resolved.
On my W520 ThinkPad I've disabled my touchpad using Gnome Settings, and
so far this bug hasn't occured. Although this doesn't resolve this
underlying issue, it makes the desktop usable again.
Considering that this bug is touchpad related, using an external mouse
and disabling the touchpad could
Looking for the assertion code, a similar bug pops up, with an offset
of 2 lines in the source file:
https://bugs.freedesktop.org/show_bug.cgi?id=105275
which duplicates:
https://bugs.freedesktop.org/show_bug.cgi?id=105258
That bug is fixed in libinput 1.10.3. I'm currently on 1.10.2-1 so this
I just tried switching to a Wayland session (verified using loginctl
show-session -p Type) but that didn't change the
restarting behavior.
/gdm-x-session[29917]: at
http://wiki.x.org
mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: for help.
mrt 17 08:16:34 t400 /usr/lib/gdm3/gdm-x-session[29917]: (EE) Please also check
the log file at "/home/nico/.local/share/xorg/Xorg.0.log" for additional
information.
mrt
hijack the package? You are more than welcome to do so!
Kind regards,
Nico
--
Nico Golde - XMPP: n...@jabber.ccc.de - GPG: 0xA0A0
signature.asc
Description: PGP signature
I depend on this as well. As a stop-gap measure, I've set of a PPA [1].
Cheers,
Nico
[1] https://launchpad.net/~nschloe/+archive/ubuntu/pybind11-backports/
Perhaps it's useful to report which are the offending lines in the build
log. For Trilinos [1], for example, a hidden flags are reported, but I have
no idea why. Can you help me out?
Cheers,
Nico
[1]
https://buildd.debian.org/status/fetch.php?pkg=trilinos=amd64=12.12.1-5=1517856320=0
Package: libopenimageio-dev
Version: 1.6.17~dfsg0-1ubuntu5
Severity: normal
File: openimageio
OpenImageIO supports Python 3 for a while now. Please provide the respective
package in Debian.
-- System Information:
Debian Release: stretch/sid
APT prefers artful-updates
APT policy: (500,
Ah, yes, these files seem to have moved from Tpetra to Kokkos. These two
upstream packages are tightly related, so no surprise there. I'll see if I
can get this fixed.
Cheers,
Nico
On Thu, Nov 16, 2017 at 2:15 AM Andreas Beckmann <a...@debian.org> wrote:
> Package: libtrilinos-kokko
Chances are slim for to ever be resolved. Upstream only supports amd64, and
PRs to fix building for other architectures are rejected. (See, e.g., [1].)
I'd say we'll have to live with trilinos not running on sparc64.
Cheers,
Nico
[1] https://github.com/kokkos/kokkos/pull/576
On Thu, Nov 16
com/a/42792413/353337
On Mon, Nov 6, 2017 at 4:03 PM Guido Günther <a...@sigxcpu.org> wrote:
> Hi,
> On Mon, Nov 06, 2017 at 02:53:11PM +, Nico Schlömer wrote:
> > Thanks for following up on this.
> >
> > > But this is not Python2.
> >
> > This is th
, 2017 at 02:21:16PM +, Nico Schlömer wrote:
> > I've tried with 0.9.1 and I'm getting the same error. The error message
> > makes sense too: In `_run_parsechangelog` one finds
>
> Then please provide steps to reproduce.
>
> > ```
> > self._contents.encod
Digging further, I found that the error can be fixed with
```
io.open(self.filename, mode='r', encoding='utf-8')
```
in `_read`, just as described in [1]. Note that
```
self._contents.encode()
```
needs to become
```
self._contents.encode('utf-8')
```
then, too.
[1]
Cc:
> Bcc:
> Date: Mon, 6 Nov 2017 14:27:19 +0100
> Subject: Re: Bug#880964: git-buildpackage: non-ascii character in
> d/changelog: UnicodeDecodeError
> Version: git-buildpackge/0.9.1
>
> Hi,
> On Mon, Nov 06, 2017 at 02:17:29PM +0100, Nico Schlömer wrote:
Package: git-buildpackage
Version: 0.8.18
Severity: important
When running
```
gbp import-orig --uscan --pristine-tar
```
on the gmsh package, gbp bails out with the error message
```
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 399:
ordinal not in range(128)
```
referring
ugs, unfortunately,
but then again it's probably a Sisyphean task to do so. As usual for those
bugs, either they are fixed immediately or never.
Cheers,
Nico
[1] https://github.com/trilinos/Trilinos/issues/1332
On Mon, Jul 24, 2017 at 10:53 AM Graham Inggs <gin...@debian.org> wrote:
> O
With tbb 2017~U7-2 in experimental, this can probably be closed now.
Cheers,
Nico
> Still comes out corrupted in the gnome Archive Manager, but extracts fine
on the command line.
Sounds more like a gAM bug then. Can this be closed?
Cheers,
Nico
On Mon, Jul 17, 2017 at 4:33 AM Drew Parsons <dpars...@debian.org> wrote:
> On Mon, 17 Jul 2017 10:21:03 +0800 Drew Pa
Thanks, Graham, for the analysis.
It appears that with 12.10.1-4 we're on top of things, so I guess this can
be closed.
Cheers,
Nico
On Sun, Jul 23, 2017 at 9:51 PM Graham Inggs <gin...@debian.org> wrote:
> On 23 July 2017 at 18:07, Nico Schlömer <nico.schloe...@gmail.com> wrote
will solve your
problem.
Cheers,
Nico
[1]
https://launchpadlibrarian.net/329863686/buildlog_ubuntu-artful-amd64.trilinos_12.11~git20170720-31a5b251-1artful1_BUILDING.txt.gz
[2] https://packages.debian.org/buster/trilinos-all-dev
On Sun, Jul 23, 2017 at 1:12 PM Joachim Wuttke <j.wut...@fz-juelich
be interested to improve the cmake
export config though.
Cheers,
Nico
[1] https://github.com/trilinos/trilinos/issues
On Sun, Jul 23, 2017 at 1:36 PM Joachim Wuttke <j.wut...@fz-juelich.de>
wrote:
> Package: trilinos-dev
> Version: 12.10.1-3
>
> CMake's find_package takes an
I've disabled the phalanx tests in master, and also fixed two other things.
Perhaps it's time for an upload?
Cheers,
Nico
On Sun, Jul 16, 2017 at 2:16 PM Nico Schlömer <nico.schloe...@gmail.com>
wrote:
> The issue was reported to upstream in May [1]. I think until we get a fix,
&g
The issue was reported to upstream in May [1]. I think until we get a fix,
it's best to disable that specific test.
Cheers,
Nico
[1] https://github.com/trilinos/Trilinos/issues/1332
On Sun, Jul 16, 2017 at 1:51 PM Graham Inggs <gin...@debian.org> wrote:
> On 16 July 2017 at 13
Package: libtbb-dev
Version: 4.4~20160526-0ubuntu2
Severity: minor
The watch file still points to
https://www.threadingbuildingblocks.org/download
https://www.threadingbuildingblocks.org/sites/default/files/software_releases/source/tbb([0-9_]+)oss_src\.tgz
but upstream has moved to GitHub [1] a
Hi, I'm the upstream ninja maintainer. Helmut asked me to leave a short
comment here after talking on IRC. I believe option 1 should be safe; ninja
shouldn't change in behavior for different build, host, or target*.
*: (One small deviation is Windows: ninja built on Windows behaves slightly
Let me add also that Epetra isn't that important anymore. Trilinos devs try
to get people to switch over to Tpetra, and in fact Epetra hasn't seen
substantial development in many years now.
Cheers,
Nico
On Thu, Jun 15, 2017 at 5:22 PM Nico Schlömer <nico.schloe...@gmail.com>
wrote:
&g
Thanks Joachim for report.
This is more of an upstream issue, see [1]. Once that is done, the package
will have the Epetra documentation shipped.
Cheers,
Nico
[1] https://github.com/trilinos/Trilinos/issues/1431
On Wed, Jun 14, 2017 at 6:42 PM Joachim Wuttke <j.wut...@fz-juelich.de>
Package: dput-ng
Severity: minor
dput-ng often fails to upload with output like
```
dput -c /path/to/dput.cf mypackage mypackage_1.0.0-1xenial1_source.changes
Return code:
3
Output:
None
```
The return code may differ, and it's always unclear what it actually means.
Please document dput-ng's
uot;: [yes, no]:
```
That makes it impossible to dput in a cron job. I've played around with my SSH
settings, but that doesn't seem to have anything do with it.
Is there a way to skip the above question?
Cheers,
Nico
-- System Information:
Debian Release: stretch/sid
APT prefers zesty-updates
APT policy: (5
Package: python-slepc4py
Version: 3.7.0-2build3
Severity: wishlist
slepc4py is compatible with Python 3.2 and up (see [1]), and it'd be nice to
this reflected in the package.
[1] https://bitbucket.org/slepc/slepc4py
-- System Information:
Debian Release: stretch/sid
APT prefers
Package: python-petsc4py
Version: 3.7.0-2build1
Severity: wishlist
petsc4py is compatible with Python 3.2 and up (see [1]) and it'd be nice to see
this reflected in the package.
[1] https://bitbucket.org/petsc/petsc4py
-- System Information:
Debian Release: stretch/sid
APT prefers
I can confirm the issue of graphical glitches, being on a fully up to
date version of Stretch with Linux 4.9, Gnome 3.22, Mesa 13.0.6.
I'm testing this on a Thinkpad T400.
Kind regards,
Nico Rikken
a good look and push changes
as you see fit. Hopefully we can this out to experimental sometime soon.
Cheers,
Nico
[1] https://github.com/nschloe/debian-vtk7
[2] https://launchpad.net/~nschloe/+archive/ubuntu/vtk7
[3] https://launchpad.net/~nschloe/+archive/ubuntu/vtk7-nightly
Package: libxdmf-dev
Severity: wishlist
Dear Maintainer,
I'm currently in the process of packaging VTK7, and it depends on XDMF3. It
does require a version newer than git20160803 however, so I'd be great if that
could be updated from upstream.
Cheers,
Nico
-- System Information:
Debian
I've had the same error message and definitely isn't a space issue.
Apparently, my input FLAC file was broken (?), but I could work around the
problem by
* converting the sound file to another lossless format, e.g., `ffmpeg -i
input.flac input.wav` and
* using shnsplit on the new input file.
Package: fenics
Version: 1:2016.2.0.1~ppa1~yakkety
Severity: minor
Tags: newcomer
Dear Maintainer,
on [1], the VCS is still listed as SVN and has a dysfunctional link. This
should be updated to the new Git repo (in debian/control).
Cheers,
Nico
[1] https://tracker.debian.org/pkg/fenics
Thanks Anton for the swift reply.
Is the vtk7-branch in the vtk6 or the original vtk package (which is VTK
5)? Considering that history, I would have opened up a whole new package
vtk7.
Cheers,
Nico
On Sat, Feb 4, 2017 at 11:13 AM Anton Gladky <gl...@debian.org> wrote:
> Hi Nico,
&
,
Nico
[1] https://launchpad.net/~nschloe/+archive/ubuntu/vtk7-nightly
[2] https://github.com/nschloe/debian-vtk7
Package: lintian
Version: 2.5.48
Severity: normal
Since recently, I'm seeing a lot of binary-or-shlib-defines-rpath [1] errors
from lintinan on Trilinos [2]. It says in the description of the warning:
```
To fix this problem, look for link lines like:
gcc test.o -o test
Package: exodusii
Severity: minor
Exodus is developed as part of SEACAS [1] for a while now. While separate
releases are still being published [2], it might make more sense to use the
Trilinos package [3] to provide SEACAS and Exodus.
Thoughts?
[1]
Thanks Lucas for the report.
A new version (12.10.1-2) has already been submitted to NEW, fixing the
test failures.
Cheers,
Nico
On Mon, Dec 19, 2016 at 10:43 PM Lucas Nussbaum <lu...@debian.org> wrote:
> Source: trilinos
> Version: 12.10.1-1
> Severity: serious
> Tags:
Done [1] and done [2]. Graham, you might want to subscribe to those PRs.
Cheers,
Nico
[1] https://github.com/kokkos/kokkos/pull/57
<https://github.com/kokkos/kokkos/pull/576>5
[2] https://github.com/kokkos/kokkos/pull/576
On Fri, Dec 9, 2016 at 11:22 AM Graham Inggs <gin...@debian.o
The patch looks really simple. Great! Do you think it'd be worthwhile
updating the PR [1] (or opening a new one)? Perhaps the kokkos devs can
figure out why the remaining tests are failing.
Cheers,
Nico
[1] https://github.com/kokkos/kokkos/pull/410
On Fri, Dec 9, 2016 at 8:18 AM Graham Inggs
1 - 100 of 2532 matches
Mail list logo
