Control: severity -1 important
Control: tag -1 moreinfo
As Stefan, I get warnings, but no crash on Debian 12 bookworm.
tag 1030658 +moreinfo
thanks
Hello Damyan,
sorry for not noticing this bug before, I thought I was subscribed to the
package.
It looks like a missing dependency to me. Could you please give me the output
of `ldd /usr/bin/zeal` ?
I tried to dig a bit to understand what's going wrong, but the
On 2022-11-24 15:37, Paride Legovini wrote:
> Upstream isn't active anymore. I suggest switching to:
>
> https://github.com/Frederick888/external-editor-revived
Thanks! Filed "RFP: external-editor-revived -- Thunderbird MailExtension
which allows using external editors"
Hello Santiago,
Santiago Vila [2023-02-18 0:26 +0100]:
> Martin Pitt wrote:
> > The "flock: not found" is #1014662, but that is already present in our
> > current
> > image with cloud-initramfs-tools 0.18.debian8, and does not seem fatal. So
> > far
>
On 2023-02-16 17:44, Santiago Vila wrote:
> AFAIK, the main reason trac was not ready for Debian 12 was the
> problems with python3, but those in theory have been fixed
1.5.x is the development branch of Trac and I would like to wait for the
official 1.6 release. It probably comes to late for
Hi all,
I am preparing a fix for this bug based on the upstream pull request
https://github.com/graphite-project/graphite-web/pull/2785 which is also
in oldstable security with version 1.1.4-3+deb10u2.
Regards
Christoph
OpenPGP_signature
Description: OpenPGP digital signature
testing this on a Bullseye live image.
It might be specific to HP laptops, can't really say. But it's a nasty surprise
to whoever
gets hit by this and not really obvious how to get around it.
with regards
Martin Kraus
-- Package-specific info:
** Version:
Linux version 6.1.0-3-amd64 (debian-ker
Control: retitle -1 libervia-backend: FTBFS: InvalidVersion: Invalid version:
'0.9.0-hg3993'
Control: user debian-pyt...@lists.debian.org
Control: usertags -1 python3.11
The cause of the error is not the failing unit test (which is ignored as
"known broken"), but that Python 3.11 is more strict
Dear Laurent, dear Jeremy, der Iain,
because I'm not sure, if you saw it: I uploaded libproxy 0.4.18-1.2 with
Sebastians patch to DELAYED/5. You might like to do something different,
therefore my headsup.
Cheers
Control: tags -1 + patch
So far only good reports about the patch by Sebastian ,
applied in experimental.
Hi Markus,
could you please try out, if the problem is fixed with a patched libproxy?
$ echo deb https://deb.debian.org/debian/ experimental main \
| sudo tee /etc/apt/sources.list.d/experimental.list
$ sudo apt update
$ sudo apt install -t experimental libproxy1v5
(IIRC)
It would be very
Sorry, that went to the wrong bug report :-(
Laurent, Jeremy, Iain, I hope you are OK with the upload to
experimental!
On 2023-01-25 15:11, Sebastian Reichel wrote:
> [[PGP Signed Part:Undecided]]
> Hi Martin,
>
> On Tue, Jan 24, 2023 at 10:50:52PM +, Martin wrote:
>> Hi S
Hi Sebastian,
I wonder, if I should upload libproxy with your github patch¹ to
experimental. Then people affected (or not affected) by the bug can test
easily. Or you may upload, of course! :-)
Cheers
¹ https://github.com/libproxy/libproxy/issues/199#issuecomment-1401124997
Control: tag -1 pending
Hello,
Bug #1026602 in python-unicodecsv 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:
On Thu, Jan 19, 2023 at 10:25 PM Beat Bolli wrote:
> On 19.01.23 16:35, Martin-Éric Racine wrote:
> > We've just pushed dhcpcd 9.4.1-14 into unstable. Can you please check
> > whether that fixes it?
>
> Indeed, this new version works.
Marking FIXED as of 9.4.1-14 . I
Greetings,
Something tells me that both of you have encountered the same bug.
We've just pushed dhcpcd 9.4.1-14 into unstable. Can you please check
whether that fixes it?
Martin-Éric
Control: severity -1 normal
The problem disappeared magically for all users who reported it before.
I assume, that there is a hidden bug in libproxy, that only appears in
certain circumstances. Downgrading for now.
Control: found -1 0.4.16-1
Control: notfound -1 0.4.15-15
I tried various versions of libproxy from snapshot.debian.org and could
find the crash to be introduced by version 0.4.16-1 exactly.
Control: clone -1 -2
Control: reassign -2 libproxy1v5 0.4.18-1
Control: retitle -2 libproxy1v5: Gajim 1.6.0-1 crashes in libproxy call
This is the backtrace with a debian.org account:
(gdb) bt
#0 read_encoded_value_with_base(unsigned char, _Unwind_Ptr, unsigned char
const*, _Unwind_Ptr*)
On 2023-01-10 19:49, Stefano Rivera wrote:
> So, probably time to remove this from the archive, clearly they don't
> intend to support the new API.
Yes, I'll file a removal request!
Control: clone -1 -2
Control: reassign -2 python3-nbxmpp 4.0.0-1
Control: retitle -2 python3-nbxmpp: Gajim 1.6.0-1 crashes on connect
On 2023-01-10 18:29, Fiona Klute wrote:
> In that case python3-nbxmpp 4.x must not migrate either, because it
> breaks Gajim 1.5.x. I'm not sure what's the proper
Hi Lucas,
is it possible that this is a transistion issue?
The logs talk about python3.10 and sid has python3.11.
Christoph
Am 01.01.23 um 15:35 schrieb Lucas Nussbaum:
.
warnings.warn(
TEST FAILED:
/<>/debian/tmp/usr/local/lib/python3.10/dist-packages/ does NOT
support .pth files
bad
>
>
> Am 01.01.23 um 15:55 schrieb Uecker, Martin:
> >
> > One could just relax (or simply remove) the test from bullseye
> > or packport the version bookworm.
>
> I guess that would be applying 0003-relax-failing-unit-test.patch
> to the Bu
One could just relax (or simply remove) the test from bullseye
or packport the version bookworm.
The wine code is broken (it violates the effective types
rules of ISO C).
Martin
Am Sonntag, dem 01.01.2023 um 15:39 +0100 schrieb Bernhard Übelacker:
> Dear Maintainer,
> I could rep
Package: firefox
Version: 108.0-1
Severity: grave
Justification: renders package unusable
When starting firefox, it displays the following message and exits immediately
with exit code 255:
XPCOMGlueLoad error for file /usr/lib/firefox/libnssutil3.so:
/usr/lib/firefox/libnssutil3.so: cannot open
scrcpy-server 1.24-1
Versions of packages scrcpy recommends:
ii adb 1:29.0.6-21
scrcpy suggests no packages.
-- no debconf information
--
.''`. martin f. krafft
: :' : proud Debian developer
`. `'` http://people.debian.org/~madduck
`- Debian - when you have better things to do
I am also affected by this bug on a 2020 Lenovo laptop, same as OP
reported. After an upgrade on my unstable debian system it booted only
to a blinking cursor. Going into a terminal and checking logs I also
saw the segmentation fault.
It made my laptop unusable as of now. :( Hope that the driver
reopen -1
thanks
The new version seams to not fix the test on all architectures.
Christoph
Am 30.11.22 um 17:09 schrieb Christoph Martin:
I have uploaded a fixed package as NMU to to the deferred queue.
Am 17.11.22 um 14:13 schrieb Christoph Martin:
I just tried to build php-db
ons of packages scrcpy recommends:
ii adb 1:29.0.6-21
scrcpy suggests no packages.
-- no debconf information
--
.''`. martin f. krafft
: :' : proud Debian developer
`. `'` http://people.debian.org/~madduck
`- Debian - when you have better things to do than fixing systems
Hi
I have uploaded a fixed package as NMU to the deferred queue.
Am 17.11.22 um 13:55 schrieb Christoph Martin:
do you plan to release a new version with the proposed fix anytime soon?
I build it locally with the fix and it builds fine.
I could upload the package if this is ok for you
I have uploaded a fixed package as NMU to to the deferred queue.
Am 17.11.22 um 14:13 schrieb Christoph Martin:
I just tried to build php-db with the new upstream version 1.11.0 and it
builds without a problem.
Do you plan to upload the updated package any time soon?
If you need help, please
Hi,
I just tried to build php-db with the new upstream version 1.11.0 and it
builds without a problem.
Do you plan to upload the updated package any time soon?
If you need help, please let me know.
Christoph
OpenPGP_signature
Description: OpenPGP digital signature
Hi,
do you plan to release a new version with the proposed fix anytime soon?
I build it locally with the fix and it builds fine.
I could upload the package if this is ok for you.
Christoph
OpenPGP_signature
Description: OpenPGP digital signature
Hi Alex,
when do you plan to upload the fixed version?
If you need any help, please let us know.
Regards
Christoph
OpenPGP_signature
Description: OpenPGP digital signature
Control: tag -1 fixed-upstream pending
Hello again,
Martin Pitt [2022-10-26 6:04 +0200]:
> Argh, this keeps haunting us. We already tried to fix that in [1] and [2], but
> no way. Why must glib be so unpredictable?
> [2] https://github.com/cockpit-project/cockpit/pull/17755
Never
above means.
I've recompiled xautolock and if this happens again, I'll be able to
provide an strace and the debug output.
Until then: thanks for your quick response!
--
.''`. martin f. krafft @martinkrafft
: :' : proud Debian developer
`. `'` http://people.debian.org/~madduck
`- De
r or
so?), and not during downstream `make check`?
Thanks,
Martin
[1] https://github.com/cockpit-project/cockpit/pull/17728
[2] https://github.com/cockpit-project/cockpit/pull/17755
--
.''`. martin f. krafft @martinkrafft
: :' : proud Debian developer
`. `'` http://people.debian.org/~madduck
`- Debian - when you have better things to do than fixing systems
Hello everybody,
many thanks for your help. There is no need to delay your NMU any further. You
could also upload it directly, I'm really happy with your help.
I'd really love to see someone helping me updating the package to the latest
version. quilt is in maintainance mode upstream, and it's a
After some digging around Ubuntu seems to have a similar issue
https://bugs.launchpad.net/ubuntu/+source/smarty3/+bug/1986916
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
Package: smarty3
Version: 3.1.45-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
I'm testing some build scripts and testing my package on a VM running bookworm,
my application uses smarty3
Turns out that the latest smarty3 is broken,
Unfortunately, I had to revert to 1.4.7.
The GTK+ dependency was not to workaround.
If there is ever a bullseye-backport of GTK+, I'll upgrade Gajim, too.
Sorry!
Oh, damned. Will try a fix later this day.
Sorry for the inconvenience!
Control: tag -1 help
I seem to remember that this is a transient bug, that does not occure all the
time at all. That being said, I'm not sure I already tested running the tests in
parallel. Is that really a FTBFS if the failure only happens under this setting?
I tend to remove the FTBFS severity
Hi all,
I'll have a look at it.
First I will include the changes from NMU -3.1 into the salsa repository.
Christoph
Am 09.09.22 um 09:33 schrieb Hugh McMaster:
Control: tags 945623 + patch
Control: tags 949086 + patch
Control: tags 998014 + patch
Dear maintainer,
I've prepared an NMU for
Hello Bastien,
thanks for your patch. I discussed the MR on salsa (in short, I'd like to
understand why my current setup is not working and what it is that you try to
fix).
In addition, please note that widelands does not build on salsa's CI because of
its size. You'll have to test your patch
Hello waxhead,
could you please tell us what is the result of the following command on your
machine?
ls -la
/usr/share/games/widelands/data/i18n/fonts/Culmus/TaameyFrankCLM-Medium.ttf
This file is included in the widelands-data package, that seem installed on your
machine, so I fail to
This bug was reported against Stable. It cannot be considered as
closed for as long as a new 5.10 kernel including the fix hasn't been
published.
Martin-Éric
On Thu, Sep 1, 2022 at 5:15 PM Debian Bug Tracking System
wrote:
>
> This is an automatic notification regarding your Bug report
&
On Tue, Aug 30, 2022 at 3:00 PM Peter Zijlstra wrote:
> On Tue, Aug 30, 2022 at 02:42:04PM +0300, Martin-Éric Racine wrote:
> > On Fri, Aug 19, 2022 at 3:15 PM Peter Zijlstra wrote:
> > >
> > > On Fri, Aug 19, 2022 at 01:38:27PM +0200, Ben Hutchings wrote:
> >
gt; Well, both alternatives end with the LFENCE instruction, so I could pull
> it out and do two consequtive ALTs, but unrolling the loop for i386 is
> a better solution in that the sequence, while larger, removes the need
> for the LFENCE.
Have we reached a definitive conclusion on to how to fix this?
Martin-Éric
Hello,
I just tested your patch and it works. I will upload the new package shortly.
Thanks for your work,
Mt.
signature.asc
Description: This is a digitally signed message part
Am Mittwoch, den 24.08.2022, 00:10 +0530 schrieb Nilesh Patra:
> Control: reassign -1 nvidia-cuda-toolkit/11.4.3-4
> Control: retitle -1 Please update nvidia-cuda-toolkit to 11.5.1 or later
>
>
> On 8/23/22 23:58, Martin Uecker wrote:
> > Am Dienstag, den 23.08.2022, 23:45
Am Dienstag, den 23.08.2022, 23:45 +0530 schrieb Nilesh Patra:
> On Tue, Aug 23, 2022 at 07:00:44PM +0200, Martin Uecker wrote:
> > I think I fixed this. At least it compiles locally in
> > a sid pbuilder environment, but I needed to build-depend
> > on gcc-10.
>
>
I think I fixed this. At least it compiles locally in
a sid pbuilder environment, but I needed to build-depend
on gcc-10.
Martin
Am Sonntag, den 07.08.2022, 13:06 +0530 schrieb Nilesh Patra:
> Hi Martin,
>
> [CC'ing both your email addresses since I don't know which one you use]
&
to accept that building for x86-32 inherently means
building for older and thus less secure architectures.
Martin-Éric
um on i386, but it
hasn't worked in recent times, because upstream has started treating
all x86-32 targets as "just a number" instead of an actual CPU sepc.
This also affects, among other things SVG-lib, which also migrated to
Rust a few years ago.
Martin-Éric
ectre v2 mitigation with the
> kernel parameter "nospectre_v2" should allow this kernel version to run
> on older CPUs without SSE2. We'll fix this properly in a later update.
That breakage affects Stable.
Expecting people to go and use workarounds on what was meant to be a
stable update isn't acceptable.
I really hope that the fix will be pushed within the next 24 hours
with high urgency.
Martin-Éric
there is no screen output after the "Loading
initrd..." message from GRUB2.
Reverting to 5.10.0-16-686-pae, the fan runs at low speed and the host boots
normally.
Martin-Éric
- -- Package-specific info:
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 8
I will look at this in a couple of days. I think it only
needs a std=c++14 or something aded to the nvcc flags.
Martin
Am Sonntag, den 07.08.2022, 13:06 +0530 schrieb Nilesh Patra:
> Hi Martin,
>
> [CC'ing both your email addresses since I don't know which one you use]
&
Martin Pitt [2022-07-26 11:58 +0200]:
> A fresh installation of rpcbind fails to start the service:
This can also be seen on package installation [1]:
Setting up rpcbind (1.2.6-5) ...
/usr/lib/tmpfiles.d/rpcbind.conf:2: Failed to resolve user '_rpc': No such
process
Martin
[1] ht
--home /run/rpcbind
--no-create-home _rpc
Please put this back. Or better yet, use systemd's User=, DynamicUser=, and
RuntimeDirectory= options to contain all of the setup in the unit.
Thanks!
Martin
signature.asc
Description: PGP signature
arning_icon"
> > "title" "my text" [] {"urgency": 1, "sender-pid": 168975} 27\n'
Thanks for the report! The tests need to be adjusted to the new libnotify 0.8.
I fixed this upstream, and will do a new release ASAP.
Bonne soirée,
Martin
package frogatto
tag 1010804 - patch
tag 1010804 + helpneeded
thanks
Hello,
I confirm that the package is not building without this patch, and that the
build proceeds with this patch. But the problem is that the code is segfaulting
systematically when I build the package with this patch. The
Dev list,
Someone apparently made a commit to the autoremoval hinter that makes
it mark packages unrelated to an RC-bug package getting marked for
autoremoval.
Could someone please look into this?
Thanks!
Martin-Éric
On Thu, May 26, 2022 at 10:38 AM Debian testing autoremoval watch
wrote
I'd really like to know why a package that that nothing to do with
NVIDIA drivers came to be marked for auto-removal.
Martin-Éric
On Thu, May 26, 2022 at 9:04 AM Debian testing autoremoval watch
wrote:
>
> xserver-xorg-video-geode 2.11.20-9 is marked for autoremoval from testing on
>
I'd really like to know how anyone could ever come to the conclusion
that a package that has nothing to do with graphic drivers needs to be
auto-removed.
Martin-Éric
On Thu, May 26, 2022 at 9:01 AM Debian testing autoremoval watch
wrote:
>
> upgrade-system 1.9.1.0 is marked for autoremova
sed to fix that, I'll test and verify/close this
bug.
Martin
as
3.0.2, so Debian is just the first distro where we noticed.
I confirm this also still happens with current upstream main (02f0a22769a6).
| ❱❱❱ gdb ./generate_rsa_key_test
| Starting program: /var/home/martin/debian/sscg/b/generate_rsa_key_test
| [Thread debugging using libthread_db enabled
> Dear Martin,
>
> I am contacting you as you are listed as the maintainer for the unrar
> package for Debian 10 as listed here:
> https://debian.pkgs.org/10/debian-nonfree-arm64/unrar_5.6.6-1_arm64.deb.html
>
> We recently reported a vulnerability (CVE-2022-30333) to RarLab.
> otherwise, I would suggest to simply add the “allow-stderr” keyword to
> “Restrictions” in the octave-integration stanza of debian/tests/control.
I am happy to do this if this is necessary, but isn't this
obviously caused by a bug in octave?
Martin
El jue, 21 abr 2022 a las 23:47, Agustin Martin
() escribió:
> If a new upstream version contains many changes that maintainer wants
> to inspect closely, it is trivial to just include upstream fix for
> this issue. I am attaching a patch (with unclosed changelog formatted
> for
Control: tags -1 + patch fixed-upstream
On Wed, Apr 20, 2022 at 09:45:26AM +0200, Leonardo Canducci wrote:
> Package: backintime-qt
> Followup-For: Bug #1008653
>
> I've installed backintime-qt from github (it's pretty straightforward,
> just donwload the source and build two deb files with the
On 2022-02-01 23:07, Martin wrote:
> There have been a number of prosody package bugs related to snakeoil
> certs. I wonder, if it is worth the trouble?
>
> For most real world installations, people get LE certs or buy them or
> they have their own CA.
>
> Maybe prosody pac
Control: tag -1 pending
Hello,
Bug #1006465 in python-dbusmock 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:
El dom, 27 feb 2022 a las 22:32, Agustin Martin
() escribió:
>
> Control: tags -1 +patch
>
> El vie, 25 feb 2022 a las 8:51, Lionel Élie Mamane
> () escribió:
> >
> > On Fri, Feb 25, 2022 at 12:51:32AM +0100, Agustin Martin wrote:
> > > El jue, 24 feb
Control: tags -1 +patch
El vie, 25 feb 2022 a las 8:51, Lionel Élie Mamane
() escribió:
>
> On Fri, Feb 25, 2022 at 12:51:32AM +0100, Agustin Martin wrote:
> > El jue, 24 feb 2022 a las 16:09, Lionel Élie Mamane
> > () escribió:
>
> > I have been looking at popcons and
El jue, 24 feb 2022 a las 16:09, Lionel Élie Mamane
() escribió:
>
> On Thu, Feb 24, 2022 at 01:51:58PM +0100, Agustin Martin wrote:
> > On Sat, Feb 19, 2022 at 05:39:28PM +0100, Mattia Rizzolo wrote:
>
> >> Source: ifrench-gut
>
> > * ispell dictiona
On Sat, Feb 19, 2022 at 05:39:28PM +0100, Mattia Rizzolo wrote:
> Source: ifrench-gut
> Version: 1:1.0-32.1
> Severity: serious
>
> Dear maintainer,
>
> we plan to remove src:myspell really soon, and together with it also
> the package "myspell-tools".
> Your package still depends on it.
>
>
On 2022-02-23 12:30, Kouhei Maeda wrote:
> I'm sorry.
No need to by sorry - we're all volunteers :-)
> Please go ahead.
Thank you, will do!
The program jp (package sat-xmpp-jp) has been renamed to libervia-cli
(package libervia-cli). Problem solved.
Control: tags -1 +pending
El mar, 22 feb 2022 a las 8:05, Mikhail Gusarov
() escribió:
>
> Hello Agustin,
>
> On 21 Feb 2022, at 23:46, Agustin Martin wrote:
>
> >> Could you show me the difference?
>
> > Find attached diff. SInce flags ar
El lun, 21 feb 2022 a las 23:26, Mikhail Gusarov
() escribió:
>
> Hello Agustin,
>
> On 21 Feb 2022, at 23:12, Agustin Martin wrote:
>
> I am thinking about using ispellaff2myspell --bylocale flag with
> russian koi8-r locale set. This should only require an extra¡
>
El sáb, 19 feb 2022 a las 17:39, Mattia Rizzolo () escribió:
>
> Source: rus-ispell
> Version: 0.99g5-27
> Severity: serious
>
> Dear maintainer,
>
> we plan to remove src:myspell really soon, and together with it also
> the package "myspell-tools".
> Your package still depends on it.
Hi, thanks
A work in progress can be found at
https://salsa.debian.org/python-team/packages/shortuuid
If there are no objections, I'll upload this week.
Package: wnpp
Control: affects -1 src:shortuuid
X-Debbugs-Cc: team+pyt...@tracker.debian.org
It seems, that the current maintainer of shortuuid is either not
active anymore or just busy. Therefore, I like to move the package to
the Python team, keeping the current maintainer as uploader.
Control: tag -1 upstream pending
Control: forwarded -1 https://github.com/cockpit-project/cockpit/pull/16928
I sent an upstream PR to add the missing node_modules/ copyrights. If there is
anything else wrong, I'll need more information (see my previous reply).
Thanks!
Martin
n test); they are not shipped in debs, but in
the source package, so they should be mentioned. That part is clear.
However, your report sounds like you found other problems apart from
node_modules/ -- what are they? Do you have an example?
Thanks,
Martin
On 2022-01-31 12:21, Julien Cristau wrote:
> prosody's postinst seems to insist on creating
> /etc/prosody/certs/localhost.{crt,key}, but does this in a fragile way.
There have been a number of prosody package bugs related to snakeoil
certs. I wonder, if it is worth the trouble?
For most real
package to the team, fix the bug and update it!
Many thanks in advance!
Cheers, Martin
On 28.12.21 21:05, Lucas Nussbaum wrote:
/<>/src/FSAL/FSAL_RGW/internal.h:50:2: error: #error rados/rgw_file.h
version unsupported (require >= 1.1.1)
50 | #error rados/rgw_file.h version unsupported (require >= 1.1.1)
| ^
Thanks for the report.
The problem is fixed in
GCC bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002505
Minimal test case for armel:
# cat BUG.c
extern _Complex float g(int N, int dims[N]);
void f(void)
{
int dims[1];
_Complex float val = g(1, dims);
}
# arm-linux-gnueabi-gcc --version
arm-linux-gnueabi-gcc (Debian 11.2.0-9) 11.2.0
Copyright (C) 2021 Free Software Foundation,
For armel as s390x the compiler crashes due to an internal
compiler error with gcc 11. Note, that the same souce code
compiles fine on other architectures and did compile also
on armel s390x with gcc 10.
Martin
ke 8. jouluk. 2021 klo 9.41 Mike Hommey (m...@glandium.org) kirjoitti:
> On Wed, Dec 08, 2021 at 09:07:24AM +0200, Martin-Éric Racine wrote:
> > 91.4.0esr-1 was indeed uploaded. However, mipsel was not removed from the
> > list of architectures in the control file, so it att
migration.
Better care in maintaining this package would be appreciated. CVE fixes have
yet to trickle into Testing or be uploaded to Stable-Updates for over 60 days.
That's not acceptable.
Martin-Éric
-BEGIN PGP SIGNATURE-
iQIzBAEBCgAdFiEEyJACx3qL7GpObXOQrh+Cd8S017YFAmGwWasACgkQrh
El mié, 1 dic 2021 a las 16:53, Camm Maguire
() escribió:
>
> Greetings! Am uploading a fix for now. cl-lib for xemacs21 can be
> found in the mmm-mode package. Other change is that image-map needs to
> be nil if not bound. Quite a few byte-compilation warnings in both
> flavors, suppressed on
21
---
Regards,
--
Agustin
From 18b14e632eb26cd469754a9a41b03f0e6e66832e Mon Sep 17 00:00:00 2001
From: Agustin Martin
Date: Fri, 26 Nov 2021 16:17:23 +0100
Subject: [PATCH] Fix byte compilation with emacs and disable it for xemacs.
---
debian/control | 7 +++
debian
On 11/19/21 1:45 PM, Debian Bug Tracking System wrote:
Your message dated Fri, 19 Nov 2021 21:40:53 +
with message-id
and subject line Bug#999376: fixed in python-gmpy2 2.1.0~b5-1
has caused the Debian Bug report #999376,
regarding python-gmpy2 ftbfs with Python 3.10
to be marked as done.
On 2021-11-09 19:26, Chris Carr wrote:
> - please could you explain why it is not suitable for inclusion in
> bullseye? What is it that I am not seeing or experiencing in my daily
> use of it?
Problem is, that Trac (up to version 1.4) used to be a Python 2 program.
Python 2 is not supported
My version was just accepted.
Am 26.10.21 um 03:51 schrieb Paul Wise:
> On Mon, 2021-10-25 at 13:00 +0200, Christoph Martin wrote:
>
>> I will try to upload a new release. I could not do so in the last
>> weeks, because my signature-key had expired and the new one d
101 - 200 of 4546 matches
Mail list logo
