Package: gnome-netstatus-applet
Version: 2.12.1-1
Severity: normal
Tags: patch
gnome-netstatus-applet currently fails to update its statistics after
disconnection and reconnection. An investigation within the source
revealed it was because the status determination between current and
previous
Sven Arvidsson wrote:
but I'm not sure if gnome-netstatus is actively maintained
these days.
Unfortunately I believe so, since it is still staying at version 2.12.x
while gnome is looking forward to 2.20. However, it is nonetheless still
widely used throughout gnome desktop users as network
retitle 406239 new version 0.9.10 available
GnoCHM version 0.9.10 is out on May 2007. Maybe Carlos is too busy
currently, but I can wait patiently.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
to happen much often with
on-the-spot style. This seems also related to the Nautilus breaks on
several places and can't input anything bugs (for example [1]), as I've
never had problem before with nautilus, but seem to be able to reproduce
them with on-the-spot style.
So manphiz, have you been
Ming Hua wrote:
Hi manphiz,
Thanks for the quick reply。
On Sun, Aug 12, 2007 at 10:27:47AM +0800, manphiz wrote:
Ming Hua wrote:
I've been using scim 1.4.7-1, with /FrontEnd/X11/Dynamic as false, XIM
mode, and over-the-spot style for quite some time. In the past few
weeks, I've only
Ming Hua wrote:
I agree that maybe scim is not the only culprit, I'll keep testing with
/FronEnd/X11/Dynamic set to false. Based on the current information, maybe
it is reasonable to reassign this bug to libX11.
Yes, I do suspect this is a libX11 bug (since Redhat people say so), but
as
Seems it is indeed forsaken upstream. Is it possible for Debian team to
include this patch on its own and provide an update? :)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: libestools1.2-dev
Version: 1:1.2.3-11
Severity: important
Some of the header files contains a macro guarded inclusion which
includes a non-existing file named est_string_config.h. Here's some snips:
// /usr/include/speech_tools/EST_String.h
37 #ifdef HAVE_CONFIG_H
38 #include
Package: gtkmm2.4
Severity: wishlist
gtkmm 2.12.0 has showed up at
http://ftp.gnome.org/pub/GNOME/sources/gtkmm/2.12/
which provide many new features with gtk+ 2.12. Since gtk+ 2.12 has
entered sid, it'll be great to have gtkmm 2.12 as well.
-- System Information:
Debian Release: lenny/sid
APT
retitle 434701 flac: new upstream version 1.2.1 available
thanks
Now 1.2.1 was out on Sep 17th, which can be found at
http://sourceforge.net/project/showfiles.php?group_id=13478
Hope it'll enter sid soon :)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
retitle 430142 libxml++2.6: new version 2.20.0 available
thanks
Now 2.20.0 can be found at:
http://ftp.gnome.org/pub/GNOME/sources/libxml++/2.20/
http://ftp.gnome.org/pub/GNOME/sources/libxml++/2.18/
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble?
Package: libsigc++-2.0
Severity: wishlist
It can be found at http://ftp.gnome.org/pub/GNOME/sources/libsigc++/2.0/
Note that libsigc++ 2.1.1 has also been release, which however is in the
unstable branch.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500,
Package: stardict
Version: 2.4.8-1
Severity: wishlist
New upstream version 3.0.0 is available for Download:
http://sourceforge.net/project/showfiles.php?group_id=80679
But currently there are several impediments for it to be included in
Debian because:
(1) It contains some nonportable
retitle 406239 gnochm: new version 0.9.10 available
Oops, wrong command...
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: bmpx
Version: 0.40.0~rc3-1
Severity: grave
Justification: renders package unusable
Current bmpx version is built against boost 1.34.0, which is now
superseded by boost 1.34.1. As it is depending on
libboost-filesystem1.34.0, libboost-iostreams1.34.0,
libboost-regex1.34.0, it is
Package: libxmmsclient++1
Version: 0.2DrJekyll-4
Severity: grave
Justification: renders package unusable
Currently libxmmsclient++1 is uninstallable because it is depending on
libboost-signals1.34.0, which is part of boost 1.34.0 and is superseded
by boost 1.34.1, which causes the uninstallable
Package: bmpx
Version: 0.40.0~rc3-1
Followup-For: Bug #438921
And, since 0.40.1 version is available[1], it'll be
better to fix this bug with the new version :)
[1] http://bmpx.beep-media-player.org/site/Downloads
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT
retitle 433064 wine: upstream version 0.9.43 available
severity 433064 wishlist
thanks
Since 0.9.41 has entered sid, there's no scim conflict currently, so
knock down severity to wishlist, and retitle for new upstream version.
if you skip releases, the damage is greater if it does happen. If
I somehow resist the possibility of making my system unstable again,
since everything else works fine with Testing and upgrading to 2.18.3
didn't help. Additionally, I noticed no hint showing that this
problem was solved with never versions.
Some search work at http://bugzilla.gnome.org shows no
Hristo Hristov wrote:
Package: libstdc++6-4.2-dev
Version: 4.2.1-4
Severity: important
The file /usr/include/c++/4.2.1/bits/atomicity.h is missing, so any
program using it cannot be compiled.
It has been moved to ext/atomicity.h since 4.2.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
Package: kqemu-source
Version: 1.3.0~pre11-6.1
Severity: normal
I tried to virtualize freebsd using qemu with kqemu but failed, both 6.2
release and 7.0 current, and both w/ and w/o acpi. The failure log said:
Fatal trap 9: general protection fault while in kernel mode
cpuid = 0; apic id = 00
Package: glibmm2.4
Severity: wishlist
It can be found at http://ftp.gnome.org/pub/GNOME/sources/glibmm/2.14/
gtkmm 2.12.0 is available as well, which, however, have to wait for gtk
2.12.0 to enter first.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500,
Current qemu, kqemu and bochsbios from sid still causes freebsd guest
failure, which is described in detail in #442822[1].
[1] http://bugs.debian.org/442822
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
reassign 442822 qemu
merge 442822 402289
thanks
Oops, I should really scrutinize the qemu BTS carefully.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Package: glade-3
Version: 3.2.2-1
Severity: wishlist
It can be found at http://ftp.gnome.org/pub/GNOME/sources/glade3/3.4/ .
Despite that it still doesn't provide GtkBuilder support for gtk+2.12,
it has several bug fixes, such as the notorious Input Dialog bug.
-- System Information:
Debian
Package: glibmm2.4
Followup-For: Bug #442828
I've attached the .diff.gz file for the new 2.14.1 version. Further
more, according to the source code, #415464 has already been handled, so
it can be closed. Hope some one can provide a NMU for it.
-- System Information:
Debian Release: lenny/sid
retitle 442828 glibmm: new upstream version 2.14.1 available
thanks
A new .diff.gz . The one in my last mail contains unnecessary changes,
which are rolled-back in this one.
glibmm2.4_2.14.1-0.1.diff.gz
Description: GNU Zip compressed data
Package: glibmm2.4
Severity: wishlist
A new upstream version 2.12.10 can be found at
http://ftp.gnome.org/pub/GNOME/sources/glibmm/2.12/
which fixed a linkage error. Hope this will get built on mips(el) and
get into testing along with gtkmm 2.10.
-- System Information:
Debian Release: lenny/sid
How's this bug going? As many libraries are packaged with separate debug
packages currently(e.g. related packages as glib, gtk, and glibmm as
well), I really wish gtkmm can be consistant with them, and there's no
downside to have a dbg packages for a libraries which will help
debugging
Package: aptitude
Version: 0.4.5.4-1
Followup-For: Bug #431054
I'm using testing, and the problem is 100% reproducable here as well.
Fortunately, with some experiments, it seems the culprit, as least in my
case, has been found - libc6-i686, whose removal finally makes aptitude
gain response
Daniel Burrows wrote:
Hm, well, I have libc6-i686 installed and I've never noticed this
problem. What CPU do you have? (what does /proc/cpuinfo say?)
Daniel
My /proc/cpuinfo is attached below. I hope it'll be helpful.
Moreover, my conjecture is, as I'm using testing, which has glibc
Daniel Burrows wrote:
Well, that eliminates the processor variable. I don't think it's the
testing libc6-i686 either -- I've tried this on some testing machines
and they work just fine, and nothing in the changelog suggests that it
would impact this bug.
Yeah, you're right. I installed
Daniel Burrows wrote:
On Sun, Jul 08, 2007 at 04:21:35PM +0800, manphiz [EMAIL PROTECTED] was heard
to say:
Here it is the backtrace of optimization-free aptitude with libc6-i686, and
I don't think it can be much helpful, as it doesn't provide more
information than the optimized one
Package: xfonts-wqy
Severity: wishlist
The new release is available at
http://wqy.sourceforge.net/cgi-bin/index.cgi?BitmapSong
and the team has provided a debian packages with a different name.
After all it'll be great to become an official package. And, wrt to
#384149, it'd better not to be
Package: apt
Version: 0.6.46.4-0.1
Severity: wishlist
The man page of apt_preferences lacks the explanation when priority
equals 0. Here is an excerpt:
0 P =100
causes a version to be installed only if there is no installed
version of the package
P 0
Package: libxml++2.6
Severity: wishlist
New upstream version is available at
http://ftp.gnome.org/pub/GNOME/sources/libxml++/2.18/
which contains several bug fixes. It'll be great to have it in Debian
anyway.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy:
Package: wine
Version: 0.9.34-1
Severity: normal
Wine 0.9.41 was released on July 13, wrt previous requests #421510 and #420680.
However I use normal severity instead of wishlist to indicate that a
conflict between scim and wine was supposed to be fixed since 0.9.35,
and all new versions
Here's the upstream bug link in which the problem was discussed:
http://bugs.winehq.org/show_bug.cgi?id=6547
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Upgrading the kernel to 2.6.21 seems to have fixed this.
Same here. The thread backtraces look sane now :)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
According to the partial backtrace provided by Claudius Hubig, in which
the backtrace got lost when encountered libc6-i686 stuff, I've got a
Deja Vu with a recent bug reported toward aptitude(#431054) reporting
keyboard handling lost when lib6-i686 was installed under kernel 2.6.18,
and the
Package: scim
Version: 1.4.7-1
Severity: normal
Already discussed in
https://bugs.launchpad.net/ubuntu/+source/scim/+bug/66104
And the problem showed up from version 1.4.6. Current transitional
solution is changing the value of /FrontEnd/X11/Dynamic in
/etc/scim/config or ~/.scim/config from
Thanks to curiosity, I updated my metacity from 1:2.14.5-4(testing) to
current unstable 1:2.18.5-1, and when encountering Force Quit
situation, everything works fine at my place: no lockup, no
non-responding, everything is fine.
Maybe you were still staying at 2.18.3? Try the newer version.
Package: stardict
Version: 2.4.7-2
Severity: normal
The current stardict cannot make use of the PowerWord dictionaries
provided at the official stardict site at this URL:
http://stardict.sourceforge.net/Dictionaries_PowerWord.php
When check a word using stardict, all dictionaries loaded there
Package: ocserv
Version: 0.11.4-0.1
Severity: wishlist
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
* What exactly did you do (or not do) that was effective (or
ineffective)?
* What was the outcome
Manphiz writes:
> Nicholas D Steeves writes:
>
>> Manphiz writes:
>>
>>> Nicholas D Steeves writes:
>>>
>>>> Manphiz writes:
>>>>
>>>>> Nicholas D Steeves writes:
>>>>>>> Nicholas D Steeves wri
control: tags -1 patch
I have prepared a merge request[1] as a fix. PTAL.
[1] elpa-persp-projectile: broken with recent elpa-perspective
--
Manphiz
!
emacsql-patches.tar.xz
Description: application/xz
--
Manphiz
uests/1
[2]
https://salsa.debian.org/debian/silversearcher-ag/-/merge_requests/1/diffs#c3fae3beb4cb2adb72f024f933eab442930904a7_0_6
--
Manphiz
signature.asc
Description: PGP signature
Nicholas D Steeves writes:
> Thank you for the ping!
>
> Manphiz writes:
>
>> Nicholas D Steeves writes:
>>> Manphiz writes:
>>>> Nicholas D Steeves writes:
>>>>> Manphiz writes:
>>>>>> Nicholas D Steeves write
David Bremner writes:
> Manphiz writes:
>
>>
>> Hi sten,
>>
>> When trying to pick a new upstream to rebase, I found that pulling
>> either upstream repo will result in an incompatible git history versus
>> the current debian/master bran
Nicholas D Steeves writes:
> Hi manphiz,
>
> Manphiz writes:
>
>> Xiyue Deng writes:
>>
>> Hi sten,
>>
>> When trying to pick a new upstream to rebase, I found that pulling
>> either upstream repo will result in an incompatible git history ver
y'll redirect me to the actual team/person
handling the requested packages.
> In this case however I was already in the middle of preparing a backport
> while I saw your report :)
Great! Thanks!
--
Manphiz
control: tags -1 patch
thanks
Lev Lamberov writes:
> Пт 15 сен 2023 @ 14:25 David Bremner :
>
>> Lev Lamberov writes:
>>
elpa-hl-todo has a versioned depends which is wrong.
>>>
>>> It is not wrong. It is as it is stated in the code, and as it is
>>> detected by dh-elpa.
>>>
>>>
tag -1 - unreproducible
thanks
David Bremner writes:
> Manphiz writes:
>
>> Hmm, indeed I cannot reproduce this with "emacs -Q" either. Will see
>> what could have caused this. Any tips on debugging?
>
> The only thing I can think of is to bisect the
Manphiz writes:
> Another finding is that in 28.x, if the term buffer have any further
> questions to ask, debian-bug seems to consider the process stuck and
> would just ignore everything and proceed. In 29.x however, the term
> buffer seems to be able to accept user input and
David Bremner writes:
> Control: tag -1 unreproducible
>
> Xiyue Deng writes:
>
>> Package: elpa-debian-el
>> Version: 37.10
>> Severity: normal
>> X-Debbugs-Cc: none, Xiyue Deng
>>
>> I've encountered an error when using "M-x debian-bug" on certain binary
>> package, such as
Sean Whitton writes:
> Hello,
>
> On Tue 12 Sep 2023 at 01:31am -07, Manphiz wrote:
>
>> I'll try :P
>
> No, not now,
Haha, of course not now. I meant I'll try to become someone they'll
refer to in the (not too extremely far) future.
> it's already in backp
Sean Whitton writes:
> Hello,
>
> On Mon 11 Sep 2023 at 12:02pm -07, Manphiz wrote:
>
>> Ah noted. I guess they'll redirect me to the actual team/person
>> handling the requested packages.
>
> In this case you could have been that person!
I'll try :P
--
Manph
Nicholas D Steeves writes:
> Manphiz writes:
>
>> Nicholas D Steeves writes:
>>> Manphiz writes:
>>>> Nicholas D Steeves writes:
>>>>> Manphiz writes:
>>>
>>> You're welcome. Yes, I agree that the github fork's structure has
run/systemd/system)
> LSM: AppArmor: enabled
>
Hi sten,
When trying to pick a new upstream to rebase, I found that pulling
either upstream repo will result in an incompatible git history versus
the current debian/master branch on salsa. I wonder how I should handle
this? Is it OK to
control: tags -1 patch
After discussing on IRC and with permission from anarcat, I intend to
adopt flycheck. An MR is being prepared at [1].
[1] https://salsa.debian.org/emacsen-team/flycheck/-/merge_requests/3
--
Manphiz
://salsa.debian.org/emacsen-team/emacs-buttercup/-/merge_requests/1
--
Manphiz
control: tag -1 patch
control: forwarded -1 https://debbugs.gnu.org/cgi/bugreport.cgi?bug=65882
Patch attached.
--
Manphiz
--- emacs-29.1+1.orig/lisp/net/rcirc.el
+++ emacs-29.1+1/lisp/net/rcirc.el
@@ -859,6 +859,7 @@ If QUIET is non-nil, no not emit a messa
(if (rcirc--connection-open
FYI I seems to be able to convince the upstream to backport the fix to
29 branch, so it will be part of 29.2. So please feel free to wait for
the next point release.
--
Manphiz
Manphiz writes:
> Nicholas D Steeves writes:
>
>> Hi manphiz,
>>
>> Manphiz writes:
>>
>>> Xiyue Deng writes:
>>>
>>> Hi sten,
>>>
>>> When trying to pick a new upstream to rebase, I found that pulling
>>> ei
Nicholas D Steeves writes:
> Manphiz writes:
>
>> Nicholas D Steeves writes:
>>> Manphiz writes:
>>>> Manphiz writes:
> [snip]
>>> Then finalise the changelog and build the package.
>>>
>>
>> Done as well.
>
&g
Nicholas D Steeves writes:
> I've moved this discussion from debian-emacsen to the relevant bug.
> Please remove debian-emacsen from CC and add me to CC for all
> follow-ups.
>
Dropped debian-emacsen@.
> Manphiz writes:
>
>> Manphiz writes:
>>
>>>
&g
est,
> Nicholas
>
Hi Nicholas,
Thanks for sponsoring the NMU! I have pushed the release commit to
debian/2.2.0+git20200805-1.1 in my repo[1]. Let me know if the tag name
looks OK.
[1]
https://salsa.debian.org/manphiz/silversearcher-ag/-/tags/debian%2F2.2.0+git20200805-1.1
--
Manphiz
signature.asc
Description: PGP signature
Manphiz writes:
> control: tags -1 patch
>
> I have prepared a merge request[1] as a fix. PTAL.
>
> [1] elpa-persp-projectile: broken with recent elpa-perspective
Turned out I didn't paste the URL, silly me. Here it is:
[1] https://salsa.debian.org/emacsen-team/p
;> test/pyvenv-workon-home-test.el -l test/pyvenv-mode-test.el -l
>> test/pyvenv-deactivate-test.el -l test/pyvenv-activate-test.el -l
>> test/pyvenv-hook-dir-test.el -l test/pyvenv-virtualenv-list-test.el -l
>> test/pyvenv-workon-test.el --eval \(ert-run-tests-batch-and-exit\) returned
>> exit code 255
>> make: *** [debian/rules:4: binary] Error 25
>
>
> The full build log is available from:
> http://qa-logs.debian.net/2023/09/25/pyvenv-el_1.21+git20201124.37e7cb1-1_unstable.log
>
> All bugs filed during this archive rebuild are listed at:
> https://bugs.debian.org/cgi-bin/pkgreport.cgi?tag=ftbfs-20230925;users=lu...@debian.org
> or:
> https://udd.debian.org/bugs/?release=na=ign=7=7=only=ftbfs-20230925=lu...@debian.org=1=1=1=1#results
>
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
>
> If you reassign this bug to another package, please mark it as 'affects'-ing
> this package. See https://www.debian.org/Bugs/server-control#affects
>
> If you fail to reproduce this, please provide a build log and diff it with
> mine
> so that we can identify if something relevant changed in the meantime.
>
Prepared a merge request at [1]. Will wait for dogsleg's review.
[1] https://salsa.debian.org/emacsen-team/pyvenv-el/-/merge_requests/1
--
Manphiz
signature.asc
Description: PGP signature
t; warning nil nil nil nil))
>nil)))
>FAILED 110/562 flycheck-define-checker/awk-gawk/syntax-error (0.139626
> sec) at test/flycheck-test.el:1
>
> We are already skipping a bunch of tests in a patch, so maybe we can add also
> this one, or wait for upstream
> to double check what is going wrong.
>
> G.
>
Looks like the best action here is to mark this test as flaky as well.
Unfortunately I don't seem to have permission to push to
emacsen-team/flycheck yet, so I've prepared a merge request[1] instead.
Looking for sponsorship :)
[1] https://salsa.debian.org/emacsen-team/flycheck/-/merge_requests/4
--
Manphiz
signature.asc
Description: PGP signature
"', which just divide the
upgrades into smaller batch and elpa-muse didn't make it to the same
batch as Emacs unfortunately.
--
Manphiz
control: tags -1 pending
thanks
Manphiz writes:
> control: tag -1 patch
> thanks
>
> Gianfranco Costamagna writes:
>
>> Source: flycheck
>> Version: 33~git20230824.e56e30d-1
>> Severity: serious
>> Forwarded: https://github.com/flycheck/flycheck/issues/2
Hi Amin,
Amin Bandali writes:
> Hiya,
>
> Manphiz writes:
>
>> Manphiz writes:
>>
>>> Another finding is that in 28.x, if the term buffer have any further
>>> questions to ask, debian-bug seems to consider the process stuck and
>>> would j
Control: tags 1024695 pending
Control: tags 1034734 pending
Control: tags 1037179 pending
Control: tags 1051478 pending
thanks
Hi,
I have a merge request[1] pending that should fix most of the comp
warnings which should be included in the next release. Stay tuned.
[1]
Nicholas D Steeves writes:
> Hello,
>
> Sorry for the delay, I hadn't realised that I had forgotten to actually
> send this draft:
>
> On Fri, 11 Aug 2023 at 22:09, Manphiz wrote:
>
>> Nicholas D Steeves writes:
>
>> Now also uploaded my PGP keys to htt
I've been dealing with similar spurious error of piuparts when testing
some packages that it reports that package purging left files on system:
,
| 0m45.6s ERROR: FAIL: Package purging left files on system:
| /etc/default/locale -> ../locale.conf not owned
| /etc/vconsole.conf ->
Nicholas D Steeves writes:
> Manphiz writes:
>
>> Nicholas D Steeves writes:
>>>> Nicholas D Steeves writes:
>>>
>>
>> Should have removed the redundant signatures and reuploaded to
>> https://keys.openpgp.org, though I don't think I had 5 s
Nicholas D Steeves writes:
> Manphiz writes:
>
>> Nicholas D Steeves writes:
>>
>>> Manphiz writes:
>>>
>>>> Nicholas D Steeves writes:
>>>>>> Nicholas D Steeves writes:
>>
>> Hmm, indeed I also cannot search it
retitle 1041367 Automate GCC version handling.
# tag with patch as a merge request is available.
tag 1041367 patch
thanks
Manphiz writes:
> Sean Whitton writes:
>
>> Hello,
>>
>> On Mon 17 Jul 2023 at 07:26pm -07, Xiyue Deng wrote:
>>
>>> Currently
Package: elpa-debian-el
Version: 37.10
Severity: normal
X-Debbugs-Cc: none, Manphiz
Dear Maintainers,
I have a merge request on salsa[1] for documentation fixes for the
package elpa-debian-el. The first commit has typo fixes only, the
second one has some proposed wording fixes. Please review
>
> Cheers,
> Nicholas
>
Hi Nicolas,
Friendly ping for comments :) If I missed your comments please help
point me to them and I'll address them soon.
--
Manphiz
Package: elpa-zenburn-theme
Version: 2.7.0-2
Severity: wishlist
X-Debbugs-Cc: none, Manphiz
Hi,
Recently elpa-zenburn-theme 2.8.0-1 hits trixie. It would be great to
have it backported to bookworm as well. Thanks in advance!
-- System Information:
Debian Release: 12.0
APT prefers stable
ed by the removal of
the obsolete "assoc" package in Emacs 29.1 which had been deprecated
since 24. I'll try to work on a fix later this week.
--
Manphiz
signature.asc
Description: PGP signature
his will result in an empty uscan results.
* Sync to latest head version, which basically just incorporated Sean's
patch upstream so that we don't need to host the patch anymore.
Please see the patches attached.
> Cheers,
> Nicholas
>
--
Manphiz
>From 22464e7bee7a9ed7a18401109640a
retitle 1041824 src:volume-el: disable d/watch and sync to latest head version
tag 1041824 patch
severity 1041824 minor
thanks
Apparently I misunderstood how "Control:" and cont...@bugs.debian.org
work. Hopefully this time it should work.
Sean Whitton writes:
> control: tag -1 + wontfix
>
> Hello,
>
> Thank you for these submissions.
>
> On Sun 23 Jul 2023 at 08:48pm -07, Manphiz wrote:
>
>> * Sync to latest head version, which basically just incorporated Sean's
>> patch upstream so that we
control: reopen -1
control: retitle -1 src:volume-el: repair d/watch to track upstream head
Manphiz writes:
> Sean Whitton writes:
>
>> control: tag -1 + wontfix
>>
>> Hello,
>>
>> Thank you for these submissions.
>>
>> On Sun 23 Jul 2023 at 08:
Nicholas D Steeves writes:
> Manphiz writes:
>
>>>> I have been trying to fix uscan error of Emacs addon packages. When
>>>> working on volume-el, I found that the repo on salsa didn't accept merge
>>>> requests while most other packages did. I
control: tags -1 patch
Hi,
I have prepared a merge request[1] that migrates from assoc.el as well
as other minor fixes. PTAL. Thanks!
[1] https://salsa.debian.org/emacsen-team/pointback/-/merge_requests/4
--
Manphiz
signature.asc
Description: PGP signature
Nicholas D Steeves writes:
> On Sun, 6 Aug 2023 at 04:37, Manphiz wrote:
>> Nicholas D Steeves writes:
>>
>> > Hi,
>> >
>> > Reply follows inline. Can we move this discussion to #1016558 to not
>> > bother Axel with our discussion?
>
>
control: retitle -1 ITA: muse-el
Nicholas D Steeves writes:
> On Sun, 6 Aug 2023 at 04:37, Manphiz wrote:
>> Nicholas D Steeves writes:
>>
>> > Hi,
>> >
>> > Reply follows inline. Can we move this discussion to #1016558 to not
>> >
control: tags -1 patch
Manphiz writes:
> Nicholas D Steeves writes:
>
>> Hello,
>>
>> Would you like to fix this RC bug and adopt the package?
>>
>> https://bugs.debian.org/1042911
>>
>> and the orphan bug is here: #1016558
>>
>>
Nicholas D Steeves writes:
> Hello,
>
> Manphiz writes:
>
>>> Nicholas D Steeves writes:
>>>
>>
>> Hi Nicholas,
>>
>> I have now prepared a merge request to migrate away from assoc.el[1] and
>> also forwarded the patch upstream
Nicholas D Steeves writes:
> Hi,
>
> Reply follows inline. Can we move this discussion to #1016558 to not
> bother Axel with our discussion?
>
> Manphiz writes:
>
>> Nicholas D Steeves writes:
>>>>> Nicholas D Steeves writes:
>>>>>
ian.org=1=1=1=1#results
>
> A list of current common problems and possible solutions is available at
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
>
> If you reassign this bug to another package, please mark it as 'affects'-ing
> this package. See https://www.debian.org/Bugs/server-control#affects
>
> If you fail to reproduce this, please provide a build log and diff it with
> mine
> so that we can identify if something relevant changed in the meantime.
>
This is due to newer with-editor starts to depend on compat while magit
hasn't done it in 3.3.0 yet. I have prepared a merge request[1] that
cherrypicks the necessary upstream commit that fixes the compat
detection, as well as a few lintian fixes. PTAL. Thanks!
[1] https://salsa.debian.org/emacsen-team/magit/-/merge_requests/2
--
Manphiz
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "debian-el":
* Package name : debian-el
Version : 37.12
Upstream contact : Debian Emacsen team
* License : GPL-2+
* Vcs :
Package: gnome-settings-daemon
Version: 2.30.2-3
Severity: grave
The daemon segmentation fault on loading the plugins of
/usr/lib/gnome-settings-daemon-2.0/*.so. The log of running
gnome-settings-daemon --no-daemon --debug is attached.
Please note that it segfaults on any *.so loading, not just
Package: cairomm
Severity: wishlist
Version 1.9.8 is available upstream. As gtkmm3.0 requires at lease
cairomm 1.9.2, it will be good to have it in Debian. Thanks.
-- System Information:
Debian Release: wheezy/sid
APT prefers testing
APT policy: (990, 'testing'), (300, 'unstable'), (200,
Package: amule-daemon
Version: 2.2.6+debian0-9+b1
Severity: important
File: /usr/bin/amuled
As subject says, if a URL contains unicode other than ascii characters,
the daemon will crash. Removing those characters in the URL let it get
processed without problem. IIRC this problem showed up before
1 - 100 of 102 matches
Mail list logo