t in /tmp/cockpit-machines-253
Do these exact commands work for you? What did you do differently? How does your
~/.apt-src/status file look like? If you move it away, or try this as a
different user, what result do you get?
Thanks,
Martin
la 28. elok. 2021 klo 13.43 Martin-Éric Racine
(martin-eric.rac...@iki.fi) kirjoitti:
>
> la 28. elok. 2021 klo 13.40 Aurelien Jarno (aurel...@aurel32.net) kirjoitti:
> >
> > On 2021-08-28 13:36, Martin-Éric Racine wrote:
> > > la 28. elok. 2021 klo 12.58 Aurelien
la 28. elok. 2021 klo 13.40 Aurelien Jarno (aurel...@aurel32.net) kirjoitti:
>
> On 2021-08-28 13:36, Martin-Éric Racine wrote:
> > la 28. elok. 2021 klo 12.58 Aurelien Jarno (aurel...@aurel32.net) kirjoitti:
> > > > $ sudo coredumpctl debug 1011
> > >
0e5134b8a812b05c898c8b859.2083.163014678500.zst
Message: Process 2083 (apt-get) of user 0 dumped core.
Stack trace of thread 2083:
#0 0xb7ae9170 frame_dummy (libstdc++.so.6 + 0x87170)
gdb terminated by signal ILL.
Martin-Éric
: sysret_ss_attrs spectre_v1 spectre_v2 spec_store_bypass
bogomips: 995.99
clflush size: 32
cache_alignment : 32
address sizes : 32 bits physical, 32 bits virtual
power management:
Feel free to reassign as appropriate.
Cheers!
Martin-Éric
-BEGIN PGP SIGNATURE
ke 28. heinäk. 2021 klo 20.21 Martin-Éric Racine
(martin-eric.rac...@iki.fi) kirjoitti:
>
> ke 28. heinäk. 2021 klo 19.18 Dennis Filder (d.fil...@web.de) kirjoitti:
> > * You have tpm2-abrmd installed, and its systemd unit is the only one
> > defining a Requires=systemd-u
ke 28. heinäk. 2021 klo 20.21 Martin-Éric Racine
(martin-eric.rac...@iki.fi) kirjoitti:
>
> ke 28. heinäk. 2021 klo 19.18 Dennis Filder (d.fil...@web.de) kirjoitti:
> > * You have tpm2-abrmd installed, and its systemd unit is the only one
> > defining a Requires=systemd-u
ne from /etc/network/interfaces
> just to see if this solves the problem. Alternatively try disabling
> tpm2-abrmd.service temporarily.
I purged tpm2-abrmd and regular bootup no longer stalls.
Thanks for the above. You zeroed-in on the most probable cause of the
problem. :)
Martin-Éric
ke 28. heinäk. 2021 klo 10.43 Michael Biebl (bi...@debian.org) kirjoitti:
>
> control: reassign -1 ifupdown
>
> Am 28.07.21 um 06:13 schrieb Martin-Éric Racine:
> > Package: systemd
> > Version: 247.3-6
> > Severity: serious
> >
> > Since upgr
the MAC address of a removable
interface. Removing the device made the bridge collapse. The fix indeed was to
specificy the MAC address I want it to use using bridge_hw.
Martin-Éric
-BEGIN PGP SIGNATURE-
iQIzBAEBCAAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmD6g2AACgkQrh+Cd8S0
17a0qxAAuAAYpas
Thanks for the additional info, and for the patch in the first place.
I'll upload it asap.
Thx, Mt.
signature.asc
Description: PGP signature
Hello,
I'm sorry to ask, but I fear I need additional information, please.
It seems to me that this patch merely circumvent the change in
ImageMagik to allow the handling of eps file during the construction
of the package. Am I right, or is it only disabling the dangerous
parts of the converter
Hello,
thanks for the report. I've read through the bugs both in debian and ubuntu,
and I found the location of the issue in the package (ns3 is quite a large
package). ns-3.31/doc/models/Makefile reads (many lines omitted):
```
CONVERT = convert
# specify figures from which .png and .pdf
ntainer setting in production
debci, I'm afraid my only way out is to apply "isolation-machine" to
fatrace-currentmount as well.
At least all the tests are runnning both in upstream and Ubuntu CI.
Thanks,
Martin
[1] https://ci.debian.net/doc/file.MAINTAINERS.html
Package: trac
Version: 1.5.2+dfsg-2
Severity: serious
IMHO, the current version of Trac is not suitable for including
it in a stable release. I'll try to provide backports of future
version 1.6.x for Debian 11.
Thanks for the report.
If you can provide a patch I can try to include it in a bugfix release.
Christoph
Am 02.04.19 um 19:26 schrieb Michael Krieger:
> Package: postfixadmin
> Version: 3.2.1-2
> Severity: important
>
> On a new installation of postfixadmin in Buster,
>
On Sat, 24 Apr 2021 02:59:40 +0300 Adrian Bunk wrote:
> On Tue, Apr 20, 2021 at 05:10:16PM +0200, Andreas Beckmann wrote:
> > Package: git-el
> > Version: 1:2.30.2-1
> > Severity: serious
> > User: debian...@lists.debian.org
> > Usertags: piuparts
> >
> > Hi,
> >
> > during a test with piuparts I
Hello FTP masters,
I'm sorry for the extra burden, but I uploaded the new upstream
release to unstable by error instead of experimental.
This upload needs to be canceled so that I can fix the version in
testing. #858498 is RC and was reopened an hour ago.
Sorry again for the extra burden,
Mt.
Thanks Sebastian for finding the bug,
thanks Michel for finding the upstream fix!
Will upload now!
ssarily point the finger to Matrix,
even though it did not happen for previous versions of Matrix.
In this case, it could be that glmmTMB relied on an undocumented
Matrix behavior which I had decided to change...
though I must say, I would still be surprised.. I'd rather expect
something more complica
Hi Sam,
that looks mostly good. Now I had some time to test your changes, and I
have some things, that may need another check.
I have added pam_tally to common-auth and the upgrade did not stop when
installing the new libpam-modules. I believe the regex is missing these
files, since it does not
'rabbit hole' : Isn't the origin -- long before the Matrix
movie -- in Lewis Carrol's "Alice in Wonderland" (1865 !!):
https://en.wikipedia.org/wiki/White_Rabbit ??
Best, Martin
--
Martin Maechler,
Seminar fuer Statistik, ETH Zurich
mentors looking for a sponsor.
https://mentors.debian.net/package/geda-gaf/
First upload to debian mentors was last week (Tuesday 9th). I reploaded
to amend changes that make lintian complain less and respond to remarks
by reviewers.
All the best,
---<)kaimartin(>---
--
Kai-
)
capabilities()
.Platform
2) Can you send me the result of rankMatrix(Z, method="qr")
i.e. `rnkZ.` from the above example ?
Best, Martin
On Mon, Feb 15, 2021 at 5:12 PM Dirk Eddelbuettel wrote:
>
>
> Martin,
>
> I have this long-running bug report against Mat
Package: regina-rexx
Version: 3.6-2.2
Severity: wishlist
El lun, 15 feb 2021 a las 13:40, Alen Zekulic () escribió:
>
> On Mon, Feb 15, 2021 at 13:16:58 +0100, Agustin Martin wrote:
>
> > I think I have something close to be ready for migration to debhelper.
>
> Me too.
move into testing, as it's prone to
cause assertion crashes in real-life situations as well. But of course Michael
has the last word on this.
Thanks Thomas and Michael for your help here!
Martin
El lun, 15 feb 2021 a las 0:05, Agustin Martin () escribió:
>
> El vie, 12 feb 2021 a las 23:05, Alen Zekulic ()
> escribió:
> >
> > I agree, please go ahead!
>
> Uploaded.
Hi,
Seems this upload has been late for two days, so regina-rexx will not
hit bullseye becaus
El vie, 12 feb 2021 a las 23:05, Alen Zekulic () escribió:
>
> On Fri, Feb 12, 2021 at 13:25:23 +0100, Agustin Martin wrote:
>
> > Alen, I plan to upload a NMU with this changes and may be some minor
> > issues. Even if I have not written rexx for years I think it would
Martin Pitt [2021-02-14 11:41 +0100]:
> So this is some weird NM build system issue that breaks something for any tag
> (i.e. minor/micro version in configure.ac) >= 1.28.0. Note that the 1.28-rc*
> tags
> have version 1.27.x.
I checked out tag 1.30-rc1 (aka version 1.29.
t.
So at the moment I'm totally stumped about this. Thomas, are you aware of any
version sensitive magic in NM's build?
Thanks!
Martin
[0] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=982613#5
[1] https://github.com/martinpitt/python-dbusmock/commit/8350ab65eb
[2] https://github.com/m
is almost surely not a bug in NM itself, but that the current dbusmock
does not properly emulate the new NM 1.29.90. Reassigning, I'll take a look.
Martin
On Sun, 16 Jun 2019 23:26:45 +0200 Andreas Beckmann wrote:
> Followup-For: Bug #930005
> Control: tag -1 patch
>
> The attached patch fixes the linking issue and thus the missing tgetent
> symbol. Thereafter the command
> regina /usr/share/doc/regina-rexx/examples/regutil.rexx
> works on i386,
Package: cryptsetup-initramfs
Version: 2:2.3.4-1~bpo10+1
Severity: grave
Justification: renders package unusable
apt upgrade installed cryptsetup-initramfs 2:2.3.4-2~bpo10+1 over
2:2.3.4-1~bpo10+1 despite the fact that initramfs-tools stayed at 0.133+deb10u1
(no newer version available in buster
On 2021-01-19 14:15, Pirate Praveen wrote:
> It is not about breaking as such, but breaking without coordination and
> planning that is the problem. We have a release team and transition process
> for a reason. I don't think uploading breaking changes without giving
> adequate notice and
On 2021-01-18 14:28, Antonio Terceiro wrote:
> In special, I need to stop including the standalone plugin files,
> because it's already included in the main file. This wasn't the case in
> the previous version, and I get that this is how upstream designed it to
> be.
Pretty "hacky" idea: How
reassign 979694 ispell 3.4.01-1
reassign 979746 ispell 3.4.01-1
forcemerge 979575 979694 979746
affects 979575 ispanish
thanks
El dom, 10 ene 2021 a las 23:02, Agustin Martin
() escribió:
>
> El dom, 10 ene 2021 a las 22:39, Robert Luberda ()
> escribió:
> >
> > reassign 9
El dom, 10 ene 2021 a las 22:39, Robert Luberda () escribió:
>
> reassign 979549 ispell 3.4.01-1
> reassign 979565 ispell 3.4.01-1
> forcemerge 979575 979549 979565
> affects 979575 ingerman iogerman ifrench iesperanto iswiss
> tags 979575 pending fixed-upstream
> thanks
>
>
> Roland Rosenfeld
Package: fastboot
Version: 1:10.0.0+r36-3
Severity: grave
Justification: renders package unusable
$ fastboot
fastboot: error while loading shared libraries: lib7z.so: cannot open shared
object file: No such file or directory
This file is provided only by package android-libunwind, but fastboot
Package: gthumb
Version: 3:3.8.3-0.1
Followup-For: Bug #974608
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Fixed upstream 1 hour ago:
https://gitlab.gnome.org/GNOME/gthumb/-/commit/3bdb4f94ba37b410ac07c25b5c83e587b55482fd
See also:
https://gitlab.gnome.org/GNOME/gthumb/-/issues/137
256 == 0)
I noticed that a few days as well, and someone else also noticed in
https://github.com/martinpitt/umockdev/issues/115
The fix is already upstream, I'll do a new release ASAP.
Thanks for your report and your continous rebuild efforts! These are much
appreciated.
Martin
Hi Alexandre,
Any update on this bug?
It's stopping the migration to testing and it would be nice to have
this tool in the next stable release of Debian.
Thanks!
--
Martin Michlmayr
https://www.cyrius.com/
Hi,
Is it possible to update the version of khal that is being built
here? One of the failures in the latest build log was fixed in
0.10.2 and I'm not sure about the other, and there's currently
no version in testing.
Thanks!
Package: webext-dav4tbsync
Version: 1.21-1
Severity: grave
Justification: makes the package in question unusable by most or
all users
Dear Mechthilde,
many thanks for maintaining the tbsync packages!
Very much appreciated, especially the support of Debian 10 (buster).
The zip file
Thanks for you work. I have just release 0.23 which includes your patch.
Am 08.11.20 um 18:26 schrieb Dominic Hargreaves:
> Control: tags 961152 + patch
> Control: tags 961152 + pending
>
> Dear maintainer,
>
> I've prepared an NMU for apt-show-versions (versioned as 0.22.11+nmu1) and
>
It seems the hamcore.se2 file provided by softether-common is too
small/contains only the authors.
-rw-r--r-- 1 root root 1832 Oct 19 14:14 /usr/share/softether-common/hamcore.se2
Thank you for providing softether as a debian package!
Martin
-- System Information:
Debian Release: bullseye/sid
APT pref
running PCP? I.e.
Depends: ${shlibs:Depends}, ${misc:Depends}, gawk, procps, libpcp-pmda-perl,
python3-pcp, python3, libpcp-web1
Recommends: bpftrace (>= 0.9.2)
Thanks!
Martin
[1] https://packages.debian.org/sid/bpftrace
[2] https://tracker.debian.org/pkg/pcp
signature.asc
Description: PGP signature
t; https://buildd.debian.org/status/fetch.php?pkg=bart=s390x=0.6.00-3=1600702311
> aw=0
>
> has the know issue.
>
> So at least the logs do not hide the issues that might be worth
> investigating or not.
Yes, this is useful. I will try to change the tests so that a
failing test outputs more information.
Best,
Martin
Hi Andreas,
Am Montag, den 21.09.2020, 09:45 +0200 schrieb Andreas Tille:
> Hi Martin,
>
> On Sat, Sep 19, 2020 at 05:50:34PM +, Uecker, Martin wrote:
> > > I'm not sure whether this is a good idea in general. If
> > > we can be sure that for s390x there is a
Am Samstag, den 19.09.2020, 17:09 +0200 schrieb Andreas Tille:
> Hi Martin,
>
> On Sat, Sep 19, 2020 at 01:15:47PM +, Uecker, Martin wrote:
> > > The severity on this bug can be downgraded, however the FTBFS on s390x
> > > remains a release critical bug, since s390
Hi Graham,
Am Samstag, den 19.09.2020, 14:04 +0200 schrieb Graham Inggs:
> On Sat, 19 Sep 2020 at 13:51, Uecker, Martin
> wrote:
> > Could severity be downgraded?
>
> The severity on this bug can be downgraded, however the FTBFS on s390x
> remains a release crit
Could severity be downgraded?
(The build on s390x seems to use a newer compiler.
The failure may be a compiler bug, but similar to
the RISC-V bug I can't investigate as I never got
access to porter boxes.)
On Thu, 17 Sep 2020 15:05:16 +0200 Andreas Tille wrote:
> Control: tags -1 normal
>
>
refrain from setting grave when it isn't. It just causes
additional work for the already overloaded Debian Qt/KDE team. If you
are unsure please ask first in debian-kde mailing list. That is part of
what it is there for.
Best,
--
Martin
Hi!
I used this frequently enough to be hesitant to let apt dist-upgrade
remove it on my system currently.
But I understand it may not make sense to port it as its hard and
upstream is not active anymore.
Is there an alternative in Debian repository?
Best,
--
Martin
ase move to MPC 1.2.0?
>
> Case
>
Thanks Case! Matthias, Vincent, would one of you be willing to do a
non-maintainer upload once Case releases the new version? I would like to
but won't have computer access until October.
> On Thu, Jul 30, 2020 at 6:36 AM Martin Kelly
> wrote:
> &g
On Thu, Jul 30, 2020, 5:34 AM Matthias Klose wrote:
> On 7/30/20 3:42 AM, Martin Kelly wrote:
> > Apparently this bug is going to cause autoremoval from testing soon. Is
> the
> > severity really high enough for that?
>
> yes, because it blocks migration of mpfr4, used b
On Wed, Jul 15, 2020, 4:27 PM Martin Kelly wrote:
> On Tue, Jul 14, 2020, 3:15 AM Vincent Lefevre wrote:
>
>> On 2020-07-14 09:48:18 +0200, Matthias Klose wrote:
>> > There is no 2.1.0 beta4, just a beta1, so I don't know what was
>> packaged in
>> > Februa
and will be in 2.0.4. I'd like to block this
version from testing to avoid the regression.
If you disagree and would rather get this in ASAP (given how young the package
is still), I'm fine with that as well, and disable the cockpit-podman test on
debian-testing for a while.
Thanks,
Martin
Possibly related: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961206
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=961741
On Tue, Jul 14, 2020, 3:15 AM Vincent Lefevre wrote:
> On 2020-07-14 09:48:18 +0200, Matthias Klose wrote:
> > There is no 2.1.0 beta4, just a beta1, so I don't know what was packaged
> in
> > February 2020. However the tests now fail with mpfr 4.1.0, seems to be
> > consistent across all
control: reassign -1 slice
control: found -1 2.28.0~ds1-1
control: retitle -1 wml/slice must depend on wml package
El jue., 9 jul. 2020 a las 13:36, Lucas Nussbaum () escribió:
>
> Source: dictionaries-common
> Version: 1.28.1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye
Package: chromium
Version: 83.0.4103.116-2
Followup-For: Bug #964334
Dear Maintainer,
seeing the same issue in chromium 83.0.4103.116-2, keeps crashing after a few
minutes of use.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964362 is a dup of this one,
Package: gajim-rostertweaks
Version: 1.1.0-1
Severity: grave
This package just needs to be removed.
Thank you for your efforts! Removal of mailplate is definitely the
best option.
--
.''`. martin f. krafft @martinkrafft
: :' : proud Debian developer
`. `'` http://people.debian.org/~madduck
`- Debian - when you have better things to do than fixing systems
digital_signature_gpg.asc
Hello,
thanks for pointing me to this, I didn't know. And even now, I'm not sure of
whether frogatto-data is auto-buildable. The reason why it's non-free is
because the licence file states: "The Frogatto game and all content is
available for download free of charge from
This is accurate to my understanding of the situation.
On Mon, Jun 1, 2020 at 11:33 AM Kurt Roeckx wrote:
> Just to clarify, as I understand it, openssl 1.0.2 (so libssl1.0.2
> in oldstable) still has the problem, which means things like
> libcurl in oldstable have that problem. And removing
On Mon, Jun 1, 2020 at 1:29 AM Axel Beckert wrote:
> > You will need to workaround this. As such this motivates critical me
> think.
>
> I think "grave" is severe enough, as it "only" breaks HTTPS including
> apt with HTTPS-based mirrors (as the one mentioned above) and hence
> only "unrelated
Control: -1 fixed-upstream
Thanks
On Fri, May 22, 2020 at 02:35:34AM +0200, Axel Beckert wrote:
> Hi Martin.
>
> Martin Quinson wrote:
> > I gave another try to this fix, and the current git version of po4a
> > manages to build aptitude even with the recent patch removed
Hello,
I gave another try to this fix, and the current git version of po4a
manages to build aptitude even with the recent patch removed.
Could you please give it a try, just to ensure that I didn't mess up
my verification?
Thanks in advance,
Mt.
--
Reject: The reference on the SimGrid
Hello,
your patch was included in an upstream release. The debian package
should be updated shortly.
Thanks for your patience,
Mt.
--
You have a problem and decide to use floats.
Now you have 2.0001 problems.
signature.asc
Description: PGP signature
alport = g_strdup_printf ("127.0.0.1:%d", port);
>if (str)
> -tc->hostport = g_strdup_printf ("%s:%d", str, port);
> +tc->hostport = g_strdup_printf ("[%s]:%d", str, port);
>if (inet)
> g_object_unref (inet);
>g_free (str);
Spot on, thank you! I tested this and sent an upstream PR to fix this.
Martin
Michael Biebl [2020-05-16 12:39 +0200]:
> Source: cockpit
> Version: 219-1
> Severity: serious
>
> Hi Martin,
>
> looks like the latest release reliably triggers a FTBFS on arch-all:
>
> https://buildd.debian.org/status/logs.php?pkg=cockpit=219-1=all
>
> The
On 5/10/20 8:20 AM, Paul Gevers wrote:
Source: python-gmpy2
Version: 2.1.0~b4-1
X-Debbugs-CC: debian...@lists.debian.org
Severity: serious
User: debian...@lists.debian.org
Usertags: regression
Dear maintainer(s),
Because your autopkgtest was part of the tests for glibc, I spotted that
the
On 4/13/20 2:25 PM, Moritz Mühlenhoff wrote:
On Sat, Feb 08, 2020 at 11:13:20AM -0800, Martin Kelly wrote:
On Sat, 8 Feb 2020 10:55:23 -0800 Martin Kelly
wrote:
On 2/2/20 8:39 PM, Sandro Tosi wrote:
should we remove this package then? or do you want to generate a python3-gmpy?
I didn't
rent version in unstable has been trying to migrate for 60 days
> [2]. Hence, I am filing this bug.
Whoops, thanks for the reminder! Indeed I fixed the RC bug
(https://bugs.debian.org/951114) two months ago already, but typoed the "Closes
#"
so that the bug stayed open. I closed it now.
Martin
On Mon, Feb 24, 2020 at 01:07:40PM +0100, Eric Valette wrote:
> On 24/02/2020 12:57, Agustin Martin wrote:
>
> > Hi,
> >
> > According to https://packages.debian.org/source/experimental/hdf5 there is a
> > new "libhdf5-hl-100" package
Control: affects 952460 -1
Control: tags -1 +pending
On Sun, Feb 23, 2020 at 02:47:12PM +0100, Lucas Nussbaum wrote:
> Source: linuxdoc-tools
> Version: 0.9.73-2
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20200222 ftbfs-bullseye
>
> Hi,
>
>
On Mon, Feb 24, 2020 at 11:38:40AM +0100, Eric Valette wrote:
> On 24/02/2020 10:50, Simon Frei wrote:
>
> > The error message you quote refers to so-version 100, while the required
> > one is 103. That suggests you aren't running the digikam binary from the
> > package, but something else (maybe
On Mon, Feb 24, 2020 at 12:09:58PM +0100, Simon Frei wrote:
> On 24/02/2020 11:38, Eric Valette wrote:
> > On 24/02/2020 10:50, Simon Frei wrote:
> >
> >> one is 103. That suggests you aren't running the digikam binary from the
> >> package, but something else (maybe you self-compiled at some
severity 951115 normal
thanks
Hello,
so I uploaded a version of this package without mipsel, and it built
nicely on all architectures where its dependencies are to be found
(all official architectures plus some others).
Thus downgrading this bug.
Thanks, Mt.
signature.asc
Description: PGP
Hi Alberto,
Am 13.02.20 um 10:11 schrieb Alberto Molina Coballes:
> I don't understand the rule "-F PREROUTING" after a "-A ..." one. It
> seems that the segfault happens in this specific case (it's a bug of
> course, but not a bug with grave severity).
I choose the grave severity because the
Hil Alberto,
Am 13.02.20 um 10:11 schrieb Alberto Molina Coballes:
>
> Is this ruleset a real one obtained from ufw? I ask because the next one
> doesn't result in segfault:
>
> *nat
> -F PREROUTING
> -F POSTROUTING
> -A PREROUTING -i eth0 -p tcp --dport 22 -j REDIRECT --to-ports 1194
> COMMIT
other symlink for device /devices/other: File exists
> autopkgtest [17:12:08]: summary
> upstream FAIL stderr:
Oops! Fixed upstream:
https://github.com/martinpitt/umockdev/commit/af719667e1d27352
Thanks,
Martin
Source: src:ns3
Version: 3.30+dfsg-3.1
Severity: serious
Tag: ftbfs
Tag: help
Hello,
I'm the maintainer of this package. I'm opening this bug to discuss the issue
with whom may be interested, and keep track of the discussion.
The package is currently trying to enter testing to fix 2 (easy) RC
The problem is that the file m4/macros/libtool.m4 in the am-utils source is
out of date relative to the libtool used in the build. The debian/rules
script tries to fix this but the fix is overridden by a later stage of the
build. The attached patch fixes it for me on Raspbian 10.
__Martin
On
On Sat, 8 Feb 2020 10:55:23 -0800 Martin Kelly
wrote:
On 2/2/20 8:39 PM, Sandro Tosi wrote:
> should we remove this package then? or do you want to generate a python3-gmpy?
>
I didn't realize, but it looks like this package actually does support
Python 3. I had assumed we wou
On 2/2/20 8:39 PM, Sandro Tosi wrote:
$ apt-cache rdepends python-gmpy
python-gmpy
Reverse Depends:
obfsproxy
python-tlslite-ng
python-sympy
python-gmpy-doc
Dependencies on obfsproxy and python-sympy documented with affects and
blocks. python-tlslite-ng has been removed
On Fri, Jan 17, 2020 at 04:35:04PM +0100, Agustin Martin wrote:
> On Tue, Dec 10, 2019 at 01:55:50PM -0500, John Scott wrote:
> > Control: forwarded -1 https://bugs.kde.org/show_bug.cgi?id=401306
> >
> > This appears to have been fixed upstream. There are a couple patch
Package: iptables
Version: 1.8.2-4
Severity: grave
Dear Maintainer,
after updateing from stretch to buster ufw failed to work.
we have nat-table entries for PREROUTING and POSTROUTING . iptables-restore
segfaults on these rules. The following rules lead to the error:
*nat
-F PREROUTING
-A
ble.
Just using [!mipsel] would break the build on other architectures like
FreeBSD and Hurd again.
[1] https://www.debian.org/doc/debian-policy/ch-relationships.html
Thanks,
Mit freundlichen Grüßen / With kind regards
Martin Steigerwald •
Proact Deutschland GmbH
Trainer
Telefon: +49 911 30999
ease find attached above patches and the debdiff for my personal build.
Hope this helps
--
Agustin
From: Aguatin Martin
Date: 20200117
Subject: Update libopencv.h.cmake.in for opencv4 and remove obsolete stuff
Based on changes by Gilles Caulier for recent digikam.
--- a/core/app/utils/libopencv.h
Quoting Scott Kitterman :
It's only needed as a Recommends for sat-xmpp-core, whch is about to be
removed from Testing.
Note, that upstream of sat-* already ported everything to Python 3.
I started packaging the new stuff, but got stuck at some point.
It's probably time to give it another try.
e happened in
https://ci.debian.net/data/packages/unstable/amd64/p/python-dbusmock/3694572.log
against NM 1.22.0, while the last successful run was against 1.20.8.
I'll investigate this more closely tomorrow. Right now my sid schroot is rather
broken due to some weirdness with gnupg disappearing from the archive.
Thanks,
Martin
Hello Nathan,
Nathan Scott [2020-01-07 11:18 +1100]:
> Thanks for looking into this issue while we were all off, Martin and Sunil!
>
> To summarise where I understand things are at now: Martin's uploaded
> a pcp package for rebuild which drops the python2 build steps. I think
&g
Control: tag -1 pending
Hello again,
Martin Pitt [2020-01-05 10:54 +0100]:
> > I ran into similar issue when attempting to build with multiple parallel
> > tasks with DEB_BUILD_OPTIONS=parallel=8 or with -j8. If you have this
> > turned on, please try disabling it.
>
>
Stop.
> dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned
> exit status 2
I can't get around this failure in my sid chroot. And I don't want to embarrass
myself by doing a source-only NMU with hoping that it works on the buildds..
Thanks,
Martin
g (in 6 days), I'm interested in doing an NMU. However, with the above
build system trouble, it may be necessary to fix this upstream first?
Thanks,
Martin
diff -Nru pcp-5.0.2/debian/changelog pcp-5.0.2/debian/changelog
--- pcp-5.0.2/debian/changelog 2019-12-04 03:00:17.0 +
+++ pcp-5.0
That's soon enough for sure, pcp's autoremoval is currently
scheduled for Jan 1.
Martin
).
Thanks,
Martin
On Mon, Nov 18, 2019 at 07:28:45AM -0400, David Bremner wrote:
> Dima Kogan writes:
>
> > Thanks for the patches, Agustin. I just tried it out. Works for the most
> > part. One thing that doesn't work for me is (gnuplot-mode) being
> > executed when opening a .gp file. You added this to the
On Mon, Nov 18, 2019 at 08:30:46AM -0400, David Bremner wrote:
> Agustin Martin writes:
>
> > Hi, David,
> >
> >> That's not loaded by elpa packages.
> >
> > But AFAIK it should be loaded by Emacs,
>
> Perhaps. Team packages don't use these startup f
201 - 300 of 4542 matches
Mail list logo
