>> \"/usr/share/emacs/site-lisp/elpa-src\")" -f package-initialize -L . -L test
>> --eval "(load-file \"test/test-helper.el\")" -l
>> 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&merged=ign&fnewerval=7&flastmodval=7&fusertag=only&fusertagtag=ftbfs-20230925&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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
> Best,
> 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-t
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
-error.awk" 2 nil "x=|\n
> ^ syntax error" 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
"true"', which just divide the
upgrades into smaller batch and elpa-muse didn't make it to the same
batch as Emacs unfortunately.
--
Manphiz
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.
>
> Than
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
-ag/-/merge_requests/1
[2]
https://salsa.debian.org/debian/silversearcher-ag/-/merge_requests/1/diffs#c3fae3beb4cb2adb72f024f933eab442930904a7_0_6
--
Manphiz
signature.asc
Description: PGP signature
!
emacsql-patches.tar.xz
Description: application/xz
--
Manphiz
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
https://salsa.debian.org/emacsen-team/emacs-buttercup/-/merge_requests/1
--
Manphiz
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: 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:
> 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:
>>>>>
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. Als
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
>>
>>
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
lastmodval=7&fusertag=only&fusertagtag=ftbfs-20230726&fusertaguser=lu...@debian.org&allbugs=1&cseverity=1&ctags=1&caffected=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: emacs23
Version: 23.3+1-1.1
Followup-For: Bug #598234
Hi, I just tried rebuilding emacs23 in my loongson box, and both emacs23
and emacs23-nox of the custom build install without problem. It might be
related to my custom kernel or an updated binutils version
(2.21.90.20111004-2). I'd like
Package: gnome-settings-daemon
Version: 2.30.2-4
Followup-For: Bug #629351
It seems that by rebuilding the package without ld flag -Wl,-z,defs
fixes this problem. This shows much resemblance with bug#537572. Though
the relation of such breakage and the ld flag is unclear, it is helpful
to temporar
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: 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 poli
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 si
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 current
>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
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.
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 sym
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 t
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 gli
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
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 again.
32 matches
Mail list logo
