Hi Bastian,
Thank you for telling me about Debian's package
named "usrmerge".
You very nicely asked me to verify that "usrmerge"
is installed properly.
dpkg says it is now installed:
$ dpkg -l usrmerge
Desired=Unknown/Install/Remove/Purge/Hold
|
Package: apt
Version: 2.7.14
Severity: wishlist
I think this is a bug:
root@hera:/# apt list '?source-package(^mg$) '
Listing... Error!
E: input:21-22: error: Expected end of file
?source-package(^mg$)
^
I think apt should ignore trailing
[James Valleroy 2024-02-12]
> Here is a patch that fixes the build:
Thank you. Can you explain why changing the output from package.json to
mktemp and then moving the result to package.json will solve the build
problem? I fail to understand how this could change anything.
Btw, did you mean
Hi Adam,
Le Mon, Mar 25, 2024 at 06:43:31PM +, Adam D. Barratt a écrit :
> On Thu, 2024-02-29 at 11:10 +0100, David Prévot wrote:
> > [1/9 for bookworm]
> >
> > This is a follow up from composer/DSA-5632-1.
[…]
> All 9 of them. :-/
Yay, sorry about that…
> Please go ahead.
Thanks! All
On Thu, 28 Mar 2024 09:32:01 +0100 Johannes Schauer Marin Rodrigues wrote:
> On 2024-03-28 08:26, Francesco Poli wrote:
[...]
> > before (last 100 chars): "/share/OVMF/OVMF_CODE.fd: Could not open
> > '/usr/share/OVMF/OVMF_CODE.fd': No such file or directory\r\n"
>
> But your system does not
Control: close -1
Control: fixed -1 0.11.89-6
On Di 26 Mär 2024 17:48:59 CET, Mike Gabriel wrote:
Hi Simon,
On Di 26 Mär 2024 16:32:13 CET, Simon McVittie wrote:
Source: plank
Version: 0.11.89-5
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built
[Remus-Gabriel Chelu 2023-12-28]
> Please find attached the Romanian translation of the «sitesummary_debconf»
> file.
Thank you very much. I've added the file to git, to make sure it is
included in the next upload.
--
Happy hacking
Petter Reinholdtsen
Package: dpkg
Version: 1.20.12
Severity: wishlist
We had a similar issue as reported in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=47839 and researched what did
cause the malformed .list package.
In our case we did install a package from a 3rd party which apparently uses a
On Thu, 7 Mar 2024 23:04:29 +0100 Paul Menzel wrote:
Upgrading from 525.147.05-1 to 535.104.12-2 with
apt install -t experimental nvidia-driver`
the DKMS build failed because nvidia-settings was still at 525.147.05-1,
and a newer version is required. I wonder, why it could be installed
Control: found -1 sbuild/0.85.6
Hello,
I finally got around to testing this new feature.
But it seems to fail:
$ mkdir -p ~/var/cache/sbuild/
$ cd /dev/shm
$ TMPDIR=/dev/shm mmdebstrap-autopkgtest-build-qemu \
--size=25G --boot=efi sid sid-amd64.img
$ mv -i
control: tag -1 + moreinfo
Hello,
Looks like you didn't push to master :)
--
Sean Whitton
signature.asc
Description: PGP signature
Package: howm
Version: 1.5.1-1
Severity: serious
User: debian...@lists.debian.org
Usertags: piuparts
Hi,
during a test with piuparts I noticed your package failed to install. As
per definition of the release team this makes the package too buggy for
a release, thus the severity.
>From the
[Gregor Riepl 2024-02-26]
> Unfortunately, it appears that upstream project is dead.
> The last commit was in 2017, and any requests by @pere on their bug tracker
> fell on deaf ears: [2]
>
> It's regrettable, but I don't think yagv can be kept with the current
> situation.
I agree. Someone
Source: music123
Version: 16.6-6
Severity: normal
X-Debbugs-Cc: ametz...@bebt.de
User: ametz...@debian.org
Usertags: mpg321-removal
Hello,
this package recommends 'mpg321 | mpg123'. mpg321 is dead upstream (last change
2012, about 12 years ago), it was initially created because of license
Source: ripperx
Version: 2.8.0-3
Severity: normal
X-Debbugs-Cc: ametz...@bebt.de
User: ametz...@debian.org
Usertags: mpg321-removal
Hello,
this package suggests mpg321. mpg321 is dead upstream (last change
2012, about 12 years ago), it was initially created because of license
issues with mpg123,
Sean Whitton writes:
> control: tag -1 + moreinfo
>
> Hello,
>
> Looks like you didn't push to master :)
Ah indeed. Just done (with tags). PTAL, thanks!
--
Xiyue Deng
signature.asc
Description: PGP signature
Hi Jeremy,
thank you for all your detailed explanations.
Burkard
Am Mittwoch, dem 27.03.2024 um 22:24 + schrieb Jeremy Sowden:
> On 2024-03-27, at 10:48:45 +0100, Dr. Burkard Lutz wrote:
> > Am Dienstag, dem 26.03.2024 um 17:03 + schrieb Jeremy Sowden:
> > > [...]
> > >
> > > The
Source: mp3check
Version: 0.8.7-4
Severity: normal
X-Debbugs-Cc: ametz...@bebt.de
User: ametz...@debian.org
Usertags: mpg321-removal
Hello,
this package suggests mpg321. mpg321 is dead upstream (last change
2012, about 12 years ago), it was initially created because of license
issues with
Source: normalize-audio
Version: 0.7.7-17
Severity: normal
X-Debbugs-Cc: ametz...@bebt.de
User: ametz...@debian.org
Usertags: mpg321-removal
Hello,
this package suggests mpg321. mpg321 is dead upstream (last change
2012, about 12 years ago), it was initially created because of license
issues
On Wed, Mar 27, 2024 at 10:42:07PM -0700, tony mancill wrote:
> On Wed, Mar 27, 2024 at 09:24:34PM -0700, tony mancill wrote:
> > Thank you for the patch and the NMU. Feel free to proceed with a 0-day
> > upload if you'd prefer.
Amazing, thank you!
I've rescheduled it to 0-day.
--
regards,
On 2024-03-28 08:26, Francesco Poli wrote:
$ sbuild-qemu-update --boot=efi \
~/var/cache/sbuild/sid-amd64.img 1> update.out 2> update.err
You added --boot=efi, good!
before (last 100 chars): "/share/OVMF/OVMF_CODE.fd: Could not open
'/usr/share/OVMF/OVMF_CODE.fd': No such file or
Package: kdeconnect
Version: 23.08.2-1
Severity: important
Dear Maintainer,
I have been upgrading my system recently, as I do every day
since I use testing, and with the advent of the 64b time
support I had to reinstall all KDE due to a pebkac.
After that kdeconnect refused to connect to my
Hi,
Quoting Francesco Poli (2024-03-28 09:40:27)
> > But your system does not have /usr/share/OVMF/OVMF_CODE.fd?
> Where should it be?
it's from the package ovmf.
> Debian package [search says] it should be in package 'ovmf'. However, the
> [file list] seems to disagree...
>
> [search says]:
Source: emms
Version: 5.1-1
Severity: normal
X-Debbugs-Cc: ametz...@bebt.de
User: ametz...@debian.org
Usertags: mpg321-removal
Hello,
this package recommends mpg321. mpg321 is dead upstream (last change
2012, about 12 years ago), it was initially created because of license
issues with mpg123,
Hi,
I tried rebuilding autosuspend in Sid, and the build lead to this
traceback in Java:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/sphinxcontrib/plantuml.py", line
223, in html_visit_plantuml
fnames = dict((e, render_plantuml(self, node, e))
Hi Adam,
Le Mon, Mar 25, 2024 at 06:44:54PM +, Adam D. Barratt a écrit :
> On Thu, 2024-02-29 at 11:18 +0100, David Prévot wrote:
> > This is a follow up from composer/DSA-5632-1.
[…]
> + * Track debian/bookworm-security
>
> Even though this update isn't going to the security archive?
Today, dist-upgrade brought to sid the new upstream release of tracker,
namely 3.7.1-1. With that, the problem I had reported disappeared: now
tracker-miner-fs runs for a finite time, and produces a working database.
The command tracker3 status now runs correctly, as do nautilus searches
using
Package: kicad
Version: 7.0.11+dfsg-1
Severity: important
X-Debbugs-Cc: behelfsmas...@gmail.com
Dear Maintainer,
after a regular system update, KiCad no longer seems to recognize any of the
built-in libraries or footprints. When I hit Place / Add Symbol in the
schematic editor, all of the
Source: snd-common
Version: 24.2-1
Severity: normal
X-Debbugs-Cc: ametz...@bebt.de
User: ametz...@debian.org
Usertags: mpg321-removal
Hello,
this package recommends mpg321. mpg321 is dead upstream (last change
2012, about 12 years ago), it was initially created because of license
issues with
I've uploaded a fixed version of buildah to sid yesterday, and a new
upstream version of libpod that builds against the fixed buildah just now.
thanks for filing this report, I believe we should be all set now once the
builds reach the archive.
On Tue, Mar 26, 2024 at 6:00 PM Salvatore
Hello Natalia,
On Fri, 23 Feb 2024 at 03:36, Natalia Lewandowska
wrote:
> Dear Maintainer,
>
> When trying to launch gdb I receive the following error message:
> symbol lookup error: gdb: undefined symbol: rl_eof_found
> and gdb never starts.
Could you share output from the following
Thank You for pursuing this! Please let me know when you have the patch and I
will gladly apply it.
Personally I think the simple solution is fine. No need to go overboard.
Best regards
ZK
Hi ftpmasters,
Am Thu, Mar 28, 2024 at 11:55:24AM +0100 schrieb Alexandre Detiste:
> >
> > ? #1065199 RM: pprintpp -- ROM; leaf package
> > Do we need this package?
> It looks dead upstream & was a trivial utility, let's drop it.
For the package pprintpp there is consens that this can be
Package: sponsorship-requests
Severity: normal
Dear mentors,
I am looking for a sponsor for my package "emacs-format-all-the-code":
* Package name : emacs-format-all-the-code
Version : 0.6.0-1
Upstream contact : Lassi Kortela
* URL :
> Wiadomość napisana przez James Addison w dniu
> 28.03.2024, o godz. 15:51:
>
> On Thu, 28 Mar 2024 at 12:43, Zygmunt Krynicki wrote:
>>
>> Thank You for pursuing this! Please let me know when you have the patch and
>> I will gladly apply it.
>>
>> Personally I think the simple
Package: elpa-debian-el
Version: 37.11
Severity: normal
Dear Debian Emacsen team,
thanks for taking care.
Unfortunately, there is a regression when detecting
apt-sources-mode. Previously, loading the file /etc/apt/sources.list
activated the apt-sources-mode. Now it doesn't.
And there are still
Hi josch,
On 2024-03-28 11:28, Johannes Schauer Marin Rodrigues wrote:
> I think sbuild-qemu-boot and sbuild-qemu-update should do the same as
> autopkgtest did here:
>
> https://salsa.debian.org/ci-team/autopkgtest/-/commit/7a4954ded0f24221ac34ca0aaf10f3f9b083afa2
Thanks for pointing this out!
On Tue, Dec 13, 2016 at 08:43:35AM +, Adam D. Barratt wrote:
> On 2016-12-12 20:25, Perl wrote:
> >* What led up to the situation?
> >I noticed, since long time ago, that I was not anymore able to use
> >Apt-Pinning for installing packages from Stable and Testing Releases.
> >*
Dear Maintainers,
I'm thinking of doing an NMU for the package by updating it to 3.13.0-0.1. The
MR is now open since July 2023 and this bug referencing it has been existing
for about 10 days (in case the MR wouldn't have been noticed).
There is also bug
On 2024-03-28 01:42, Otto Kekäläinen wrote:
> The research done in
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=895570#50 looks good.
>
> Do we have now agreement to default to -ast or -astb for packages that have
> Debhelper 14+?
I don't think making w-a-s defaults depend on the
reopen 1067715
tags 1067715 + fixed-upstream
thanks
On Thu, 28 Mar 2024 15:15:05 +
"Debian Bug Tracking System" wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the calibre package:
>
> #1067715: calibre: doesn't install DeACSM plugin
>
> It
Package: atril
Version: 1.26.2-2
Severity: serious
The latest version of atril depends on both libatrildocument3 and
libatrildocument3t64. As a result it is uninstallable on
architectures that are undergoing the time64 transition
(armel, armhf and some debian-ports archictures).
Package: wnpp
Control: affects -1 + src:qt-avif-image-plugin
Severity: normal
I intend to orphan the qt-avif-image-plugin package. The avif format
support is already provided by KDE's kimageformat-plugins, and a
standalone qt-avif-image-plugin with conflict files may have little
usage.
The
Hello Lucas, thanks for the report.
The issue appeared to be fixed in version 4.3.2-p16.
I am on my way to bring this new version to experimental.
Best wishes, Jerome
--
Jerome BENOIT | calculus+at-rezozer^dot*net
https://qa.debian.org/developer.php?login=calcu...@rezozer.net
AE28 AE15 710D FF1D
Hello Thomas!
Thanks for chiming in on this issue. I had sent a follow-up at about the same
time you did with a few details on the history as I could reconstruct it.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1067771#18
In summary: I believe you changed the default location from to
Control: tags -1 + patch
Hi,
On 2024-03-27 11:02, Sebastian Ramacher wrote:
> export-cache.c: In function ‘junction_flush_exports_cache’:
> export-cache.c:110:51: error: format ‘%ld’ expects argument of type ‘long
> int’, but argument 4 has type ‘time_t’ {aka ‘long long int’} [-Werror=format=]
After further testing, the crash issue when copying multiple files (total
volume 150 GB) or a disk image (250 GB) is present when an SSD is formatted in
GPT format.
This works without problem if the SSD is formatted in MBR/MS-DOS.
Regards.
Package: libraptor2-0
X-Debbugs-Cc: ped...@gmail.com, Debian Security Team
Version: 2.0.15-4
Severity: grave
Justification: user security hole
Tags: patch upstream security
Hi,
Following on Hanno Bock's footsteps [1], I decided to fuzz libraptor2
[2][3] and after a few days found a couple
Source: gcc-14
Severity: wishlist
Tags: patch
User: helm...@debian.org
Usertags rebootstrap
Hi Matthias,
thanks for merging my -for-host work. I'm looking into making practical
use of it and a major issue is the following dependency:
$FRONTEND-$VERSION-for-host:$DEB_HOST_ARCH ->
Package: ftp.debian.org
Severity: normal
User: ftp.debian@packages.debian.org
Usertags: remove
X-Debbugs-Cc: fu...@packages.debian.org
Control: affects -1 + src:fuse3
Please remove fuse3 version 3.14.0-5.1~exp1 from experimental. It
prepares a time64 transition that is not needed and will not
On 28.03.24 15:00, Santiago Vila wrote:
Daniel Swarbrick wrote:
* Add new 0022-Support-prometheus-common-0.47.0.patch (Closes: #1064765)
Hello. I don't quite understand how the above fix is related to
the bug itself (but maybe it's because I don't know prometheus internals).
As described
On 2024-03-28 Peter B wrote:
> On 27/03/2024 14:57, Andreas Metzler wrote:
>> mpg321 is dead upstream
> I don't see that as a show stopper.
>> Please consider moving to another player, e.g. mpg123.
> I moved away from ffmpeg after c-evo-dh showed a puiparts fail
> stemming from libnettle8.
Arslan M.
CRTO, GWAPT, OSCP
Hi again,
#1721 has been merged. Can the impacket package be updated to the latest state
of the repository to allow the Kali Team and me to package NetExec?
Thanks!
On Friday, March 22nd, 2024 at 10:42, Arszilla wrote:
> A small status update:
> -
On Thu, 28 Mar 2024 at 12:43, Zygmunt Krynicki wrote:
>
> Thank You for pursuing this! Please let me know when you have the patch and I
> will gladly apply it.
>
> Personally I think the simple solution is fine. No need to go overboard.
Ok, agreed - I'll test and then provide a patch to use a
Package: rust-coreutils
Version: 0.0.24-2
Severity: serious
rust-coreutils FTBFS with the new version of rust-uutils-term-grid.
The Debian build-dependency allows the new version, but the Cargo
dependency does not.
After bumping the cargo dependency, the code fails to build with a
bunch of
Package: e2fsprogs
Version: 1.47.0-2.4
Severity: important
X-Debbugs-Cc: Helmut Grohne
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
The following packages have unmet dependencies:
e2fsprogs : PreDepends: libcom-err2 (>= 1.43.9)
PreDepends: libss2 (>= 1.38)
E: Error,
Package: javahelper
Version: 0.79
Severity: normal
User: reproducible-bui...@lists.alioth.debian.org
Usertags: fileordering
Control: affects -1 libpixels-java
Dear Maintainer,
I'm an occasional volunteer contributor to the Reproducible Builds[1] project,
and noticed that the 'libpixels-java'
Package: x11-utils
Version: 7.7+5
Severity: normal
X-Debbugs-Cc: rst...@gmx.net
Dear Maintainer,
* What led up to the situation?
- I need to alert users to certain actions and give them the option to
pause or delay those actions for a limited period of time. Due to a wide
variety of
Reinhard,
On Thu, Mar 28, 2024 at 07:30:00AM -0400, Reinhard Tartler wrote:
> I've uploaded a fixed version of buildah to sid yesterday, and a new
> upstream version of libpod that builds against the fixed buildah just now.
>
> thanks for filing this report, I believe we should be all set now
I dug more:
The original ITP states it was a hard dependency of "rich".
Now 'rich' does all that and more all by itself.
(and more importantly is maintained)
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: open...@packages.debian.org
Control: affects -1 + src:openmpi
User: release.debian@packages.debian.org
Usertags: binnmu
nmu openmpi_4.1.6-7 . armel armhf . unstable . -m "Rebuild without the nojava
profile"
Hi Zygmunt,
On Sun, 25 Feb 2024 at 12:12, James Addison wrote:
>
> On Wed, 21 Feb 2024 at 15:52, Zygmunt Krynicki wrote:
> >
> >
> > > Wiadomość napisana przez James Addison w dniu
> > > 21.02.2024, o godz. 15:49:
> > >
> > > Source: snapd
> > > Version: 2.61.1-1
> > > Severity: wishlist
> >
Hi Andreas,
On 27/03/2024 14:57, Andreas Metzler wrote:
mpg321 is dead upstream
I don't see that as a show stopper.
Please consider moving to another player, e.g. mpg123.
I moved away from ffmpeg after c-evo-dh showed a puiparts fail
stemming from libnettle8. c-evo-dh does not use any
found 1064765 2.45.3+ds-3
thanks
Daniel Swarbrick wrote:
* Add new 0022-Support-prometheus-common-0.47.0.patch (Closes: #1064765)
Hello. I don't quite understand how the above fix is related to
the bug itself (but maybe it's because I don't know prometheus internals).
In either case, this
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: subvers...@packages.debian.org
Control: affects -1 + src:subversion
User: release.debian@packages.debian.org
Usertags: binnmu
nmu subversion_1.14.3-1+b3 . armel armhf . unstable . -m "Rebuild without the
nojava profile"
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: jpeg...@packages.debian.org
Control: affects -1 + src:jpeg-xl
User: release.debian@packages.debian.org
Usertags: binnmu
nmu jpeg-xl_0.7.0-10.2 . armel armhf . unstable . -m "Rebuild with java re-
enabled"
Package: release.debian.org
Severity: normal
Tags: bookworm
User: release.debian@packages.debian.org
Usertags: pu
Control: block 1043058 with -1
Control: affects -1 + src:libesmtp
[ Reason ]
libesmtp6 uses Replaces without corresponding Breaks, leaving a crippled
libesmtp5 package behind.
control: fixed -1 1.6.43-4
control: close -1
On Tue, 12 Mar 2024 01:13:08 +0100 Cyril Brulebois wrote:
Source: libpng1.6
Version: 1.6.43-3
Severity: serious
Tags: d-i
Justification: broken shlibs
X-Debbugs-Cc: debian-b...@lists.debian.org
Hi,
Your debian/rules includes this:
Source: terminatorx
Version: 4.2.0-1
Severity: normal
X-Debbugs-Cc: ametz...@bebt.de
User: ametz...@debian.org
Usertags: mpg321-removal
Hello,
this package depends on mpg321. mpg321 is dead upstream (last change
2012, about 12 years ago), it was initially created because of license
issues with
Control: forwarded -1 https://github.com/rcaelers/workrave/issues/532
What do you think about packaging 1.11.0 beta 12? The commit doesn't
apply cleanly since the file structure has been reorganized.
Thank you,
Jeremy Bícha
On 2024-03-27 22:30 +, Thorsten Glaser wrote:
> >OK, got those. but that's just binaries. It was the source changes I
> >was looking for (or did I misunderstand and you didn't actually make
> >any of those?),
>
> Yes, I did not make any source changes. These were the last binaries
> from
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: memcac...@packages.debian.org
Control: affects -1 + src:memcached
User: release.debian@packages.debian.org
Usertags: binnmu
nmu memcached_1.6.23-1 . armel armhf . unstable . -m "Rebuild for time_t"
--
Colin Watson (he/him)
Package: wnpp
Severity: wishlist
Owner: Yogeswaran Umasankar
X-Debbugs-Cc: debian-de...@lists.debian.org, kd8...@gmail.com
* Package name: python-memray
Version : 1.11.0
Upstream Contact: Bloomberg LP
* URL : https://github.com/bloomberg/memray
* License :
Package: release.debian.org
Severity: normal
X-Debbugs-Cc: net...@packages.debian.org
Control: affects -1 + src:netcdf
User: release.debian@packages.debian.org
Usertags: transition
There is no auto-netcdf tracker because libnetcdf19t64 already migrated to
testing because it didn't build
Hi Yogeswaran
There's already an RFP:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1009970
Please see what's needed to do here:
https://github.com/bloomberg/memray/issues/518
You can find my packaging so far at salsa.d.o or
http://sid.ethz.ch/debian/memray/
I'm willing to review
Sean Whitton writes:
> Hello,
>
> Rob, can you review the implementation in d/rules for Xiyue's patch to
> this bug, please? I'm not sure it's the straightforward way to do it.
>
> Xiyue, I think it would make sense to use emacs-common (<< 1:29.3+2-2),
> for the relationships.
Ah indeed, I
Hello,
On Wed 27 Mar 2024 at 11:40pm -07, Xiyue Deng wrote:
> Sean Whitton writes:
>
>> Hello,
>>
>> Rob, can you review the implementation in d/rules for Xiyue's patch to
>> this bug, please? I'm not sure it's the straightforward way to do it.
>>
>> Xiyue, I think it would make sense to use
Hi Christian,
Quoting Johannes Schauer Marin Rodrigues (2024-03-28 10:05:53)
> Christian, can you give this a try as well?
I think sbuild-qemu-boot and sbuild-qemu-update should do the same as
autopkgtest did here:
Package: wnpp
Severity: wishlist
Owner: Victor Seva
X-Debbugs-Cc: debian-de...@lists.debian.org, debian-packag...@sipwise.com,
vs...@debian.org
* Package name: lua-cmsgpack
Version : 0.4.0
Upstream Contact: Salvatore Sanfilippo
* URL :
Package: chromium
Version: 123.0.6312.58-1
Severity: important
X-Debbugs-Cc: d...@bostoncoop.net, d...@bostoncoop.net
After upgrading from 122.0.6261.128-1 to 123.0.6312.58-1, I'm
experiencing repeated crashes/thread hangs on many web pages. It seems
to happen more often on pages with more
On Wed, 27 Mar 2024 08:28:34 +0900
yokota wrote:
> Hello, José.
Hi,
> > oscrypto.errors.LibraryNotFoundError: Error detecting the version of
> > libcrypto
>
> This bug was already fixed on DeACSM upstream development code.
> Try it from DeACSM plugin forum.
>
Hello Graham,
I've modified the debdiff and applied it to master in
https://salsa.debian.org/games-team/mygui/ as well. So we're ready to go
with MyGUI 3.4.3.
Cheers,
Bret
On Mon, Feb 5, 2024 at 2:33 PM Graham Inggs wrote:
> Source: mygui
> Version: 3.4.2+dfsg-1
> Severity: serious
> Tags:
Package: luajit
Version: 2.1.0+openresty20231117-2
Severity: wishlist
Tags: patch
User: debian-loonga...@lists.debian.org
Usertags: loong64
Hi,
We added support for the LoongArch64 architecture in luajit-2.1.0,
which passed the LuaJIT-test-cleanup test set and was successfully used
in
Can this solution be brought too bookworm, either through stable-updates
(preferably) or otherwise backports?
The current package is not useable.
severity 1051496 normal
tags 1051496 + moreinfo
Hello Michael,
thank you for spending your time helping to make Debian better with this bug
report.
We are using mailgraph one multiple server with Debian Bullseye, Bookworm and
Trixie without any failure.
Therefore I set the severity to
package release.debian.org
tags 1065059 = bookworm pending
thanks
Hi,
The upload referenced by this bug report has been flagged for acceptance into
the proposed-updates queue for Debian bookworm.
Thanks for your contribution!
Upload details
==
Package: symfony
Version:
package release.debian.org
tags 1067564 = bookworm pending
thanks
Hi,
The upload referenced by this bug report has been flagged for acceptance into
the proposed-updates queue for Debian bookworm.
Thanks for your contribution!
Upload details
==
Package: cpu
Version:
Le jeudi 28 mars 2024, 17:21:48 UTC Fab Stz a écrit :
> Dear Maintainers,
>
> I'm thinking of doing an NMU for the package by updating it to 3.13.0-0.1.
> The
> MR is now open since July 2023 and this bug referencing it has been existing
> for about 10 days (in case the MR wouldn't have been
I misspoke - a different watchdog will be provided for arm, so this
request is for amd64 only.
On Thu, Mar 28, 2024 at 11:15 AM Debian Bug Tracking System
wrote:
>
> Thank you for filing a new Bug report with Debian.
>
> You can follow progress on this Bug here: 1067908:
>
Hi!
On Thu, 2024-03-28 at 09:54:36 +, Grueninger, Tobias wrote:
> Package: dpkg
> Version: 1.20.12
> Severity: wishlist
> In our case we did install a package from a 3rd party which apparently
> uses a non-conforming .deb package building tool (unknown to us)
> resulting in a malformed
On 2024-03-28 20:35, Martin-Éric Racine wrote:
> Package: libc-devtools
> Severity: normal
>
> libgd3 pulls an excessive amount of dependencies, including fonts. It would
> thus be desirable to downgrade it to a mere Recommends.
>
The /usr/bin/memusagestat binary is linked against libgd3, so
Control: retitle -1 elpa-debian-el: regression regarding apt-sources-mode
Control: tags -1 pending
Xiyue Deng writes:
>
> BTW, please feel free to file one bug per issue which helps us tracking
> those issues. Thanks for your reports!
>
I have filed a separate bug[1] for tracking the comp
Le jeudi 28 mars 2024, 18:16:09 UTC Fab Stz a écrit :
> Hello Bastien,
>
> Iirc not so many packages depend on it and none seems to use the files that
> are not shipped anymore in the binary package (the individual 'rules').
>
> Concerning the build maybe you could look at d/rules on the merge
To build modernizr an additional source file is required (file.js) this file is
added to missing-sources (it comes from the npm package of the same name from
npm server or from upstreams repo). It is required by the build script from
upstream.
The patch is only here to use that file. That way
Package: libc-devtools
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
libgd3 pulls an excessive amount of dependencies, including fonts. It would
thus be desirable to downgrade it to a mere Recommends.
Martin-Éric
- -- System Information:
Debian Release: trixie/sid
APT
Ok, the problem was that CFLAGS now contains
-Werror=implicit-function-declaration
by default, set by dpkg-buildflags in unstable.
The minimal fix is to drop such option, by adding this line to debian/rules:
export DEB_CFLAGS_MAINT_STRIP = -Werror=implicit-function-declaration
I'm Cc:ing
Hi Jörg-Volker,
Jörg-Volker Peetz writes:
> Package: elpa-debian-el
> Version: 37.11
> Severity: normal
>
> Dear Debian Emacsen team,
>
> thanks for taking care.
> Unfortunately, there is a regression when detecting
> apt-sources-mode. Previously, loading the file /etc/apt/sources.list
>
Source: collatinus
Version: 12.2-1
Severity: serious
The package explicitly Build-Depends: libqt5printsupport5, this needs to be
changed to
libqt5printsupport5t64 if it's needed at all.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500,
Source: veusz
Version: 3.6.2-1
Severity: serious
The package explicitly Build-Depends: libqt5*, these need to be changed to
libqt5*t64 (where applicable) if these deps are needed at all.
-- System Information:
Debian Release: trixie/sid
APT prefers unstable-debug
APT policy: (500,
El 28/3/24 a las 22:42, Daniel Swarbrick escribió:
I think you are taking the "FAILED" out of context and misinterpreting the test
output.
This is very likely, yes, and I'm sorry for that.
If you prefer I could report this build failure in a new report
(or you can also use the clone command
1 - 100 of 164 matches
Mail list logo
