Control: forcemerge 1064681 1067778
On Tue, Mar 26, 2024 at 05:20:33PM +0100, Matthias Klose via Pkg-games-devel
wrote:
> Package: src:retroarch
> Version: 1.16.0.3+dfsg-1
> Severity: serious
> Tags: sid trixie ftbfs
>
> retroarch ftbfs in unstable
>
> [...]
> Checking existence of -lglslang
Control: reassign -1 sdcc
This is going to be a result of the 4.4.0 sdcc upload I did over the
weekend.
On Wed, Mar 20, 2024 at 10:04:12PM +0100, Lucas Nussbaum wrote:
> Source: sigrok-firmware-fx2lafw
> Version: 0.1.7-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User:
Control: retitle -1 sdcc: FTBFS: Error building LyX documentation
On Sun, Feb 25, 2024 at 08:45:34PM +0100, Lucas Nussbaum via
Pkg-electronics-devel wrote:
> Source: sdcc
> Version: 4.2.0+dfsg-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
>
Control: tags -1 - trixie
Control: severity -1 important
On Sun, Feb 25, 2024 at 08:48:32PM +0100, Lucas Nussbaum via Pkg-games-devel
wrote:
> Source: retroarch
> Version: 1.16.0.3+dfsg-1
> Severity: serious
> Justification: FTBFS
> Tags: trixie sid ftbfs
> User: lu...@debian.org
> Usertags:
Control: severity -1 important
On Mon, Apr 17, 2023 at 05:32:06PM +0100, Graham Inggs wrote:
> Source: libretro-bsnes-mercury
> Version: 094+git20220807-6
> Severity: serious
>
> Hi Maintainer
>
> Since the upload of 094+git20220807-6, the
> kodi-game-libretro-bsnes-mercury-* binary packages
Package: trezor
Version: 0.12.4-1
Severity: grave
X-Debbugs-Cc: nood...@earth.li
Control: forwarded -1 https://github.com/trezor/trezor-firmware/issues/2199
Installed trezor and tried to run it, got a traceback:
$ trezorctl
Traceback (most recent call last):
File "/usr/bin/trezorctl", line
On Wed, Mar 01, 2023 at 08:07:09AM +, Jonathan McDowell wrote:
> On Mon, Feb 27, 2023 at 09:11:46PM +0100, Paul Gevers wrote:
> > On 25-02-2023 14:30, Adrian Bunk wrote:
> > > With the bookworm-ignore for #994758,
> >
> > I'll admit that I misjudged that bug
On Mon, Feb 27, 2023 at 09:11:46PM +0100, Paul Gevers wrote:
> Control: tags 994758 - bookworm-ignore
>
> Hi Adrian,
>
> Thanks for caring.
>
> On 25-02-2023 14:30, Adrian Bunk wrote:
> > With the bookworm-ignore for #994758,
>
> I'll admit that I misjudged that bug; with this message I'll
Control: tag -1 pending
Hello,
Bug #978819 in gcc-xtensa-lx106 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:
This is a result of the new "check" 0.15.2 package (updated from
0.12.0), in particular upstream commit
82540c5428d3818b64d6a8aefb601e722520651f:
https://github.com/libcheck/check/commit/82540c5428d3818b64d6a8aefb601e722520651f
"For users of these APIs who do pass a message there will
be a new
Control: tag -1 pending
Hello,
Bug #978512 in gcc-xtensa-lx106 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:
Control: severity -1 important
On Thu, Nov 19, 2020 at 10:47:32AM +0100, Lucas Nussbaum wrote:
> Source: pulseview
> Version: 0.4.2-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: bullseye sid ftbfs
> Usertags: ftbfs-20201119 ftbfs-bullseye
>
> Hi,
>
> During a rebuild of all
Control: severity -1 important
Control: tag -1 pending
This is still building fine with the python3-defaults in unstable so
doesn't warrant the serious severity. Upstream has a minor fix to enable
Python3.9 which I will pull in.
J.
--
/-\ | 101 things you can't have
Control: tag -1 pending
Hello,
Bug #959622 in gcc-xtensa-lx106 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:
Control: block -1 with 954826
On Thu, Mar 26, 2020 at 10:48:27PM +0100, Emilio Pozuelo Monfort wrote:
> On Tue, 05 Nov 2019 13:23:02 + Matthias Klose wrote:
> > Package: ghdl
> > Severity: important
> > Tags: sid bullseye
> > User: debian-...@lists.debian.org
> > Usertags:
Control: reassign -1 libsigrok-dev
Control: retitle -1 Missing bluetooth + hidapi deps on -dev package cause
FTBFSes
On Sun, Feb 23, 2020 at 07:53:00AM +0100, Lucas Nussbaum wrote:
> Source: sigrok-cli
> Version: 0.7.1-1
> Severity: serious
> Justification: FTBFS on amd64
> Tags: buster sid
>
On Sat, Sep 28, 2019 at 07:02:31AM +0200, Gianfranco Costamagna wrote:
> control: severity -1 serious
> control: found -1 0.35+git20181129+dfsg-3
>
> I know this isn't the right bug, but since this bug is about a non-existing
> version that FTBFS, lets recycle it :)
I think you wanted to alter
On Wed, Aug 21, 2019 at 10:40:29AM +, Ivo De Decker wrote:
> A binnmu of binutils-xtensa-lx106 in unstable fails on amd64:
>
> https://buildd.debian.org/status/package.php?p=binutils-xtensa-lx106
>
> It probably needs to be updated for the newer binutils.
binutils has helpfully changed its
Control: severity -1 wishlist
Control: retitle -1 Update GHDL packaging for newer releases
On Sun, Jun 23, 2019 at 11:57:33PM +0200, Pavel Pisa wrote:
> On Sunday 23 of June 2019 10:52:47 Jonathan McDowell wrote:
> > On Sat, Jun 22, 2019 at 12:26:36AM +0200, Pavel Pisa wrote:
> >
On Sat, Jun 22, 2019 at 12:26:36AM +0200, Pavel Pisa wrote:
> Source: ghdl
> Version: 0.36+20190617
This is not a version of GHDL from Debian. testing/unstable both have
0.35+git20181129+dfsg-3. I don't think this is a valid bug against the
Debian package - it seems that you've obtained an
+ varnish plugins. (Closes: #924337)
+
+ -- Jonathan McDowell Wed, 03 Apr 2019 21:56:47 +0100
+
collectd (5.8.1-1.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru collectd-5.8.1/debian/control collectd-5.8.1/debian/control
--- collectd-5.8.1/debian/control 2018-12-19 14:51
On Sat, Feb 09, 2019 at 01:39:34PM +0100, Matthias Klose wrote:
> Package: src:binutils-xtensa-lx106
> Version: 1
> Severity: serious
> Tags: sid buster
> unnecessary b-d's libisl-0.18-dev and libcloog-isl-dev, to be removed
> for buster
Where should I have been paying attention to find this
On Sat, Dec 29, 2018 at 10:39:07PM +0100, Lucas Nussbaum wrote:
> During a rebuild of all packages in sid, your package failed to build
> on amd64.
...
> > ! LaTeX Error: File `footnotehyper.sty' not found.
> >
> > Type X to quit or to proceed,
> > or enter new name. (Default extension: sty)
> >
Control: retitle -1 Clean LyX install fails to configure correctly
Control: reassign -1 lyx
Control: tag -1 patch
Control: affects -1 sdcc
Confirmed that this is a LyX issue. A fresh install of LyX results in
the same /usr/share/lyx/configure.py failure, and removing ~/.lyx/ on an
existing
Weird. This built fine in my sbuild environment for upload to the
archive, but is now failing, so looks like one of the deps has changed.
The failing build log includes:
Traceback (most recent call last):
File "/usr/share/lyx/configure.py", line 1886, in
ret =
Control: tags -1 + pending
Control: block -1 by 897895
I've backported the upstream fix to 0.4.0 but the build still fails due
to #897895 in libsigc++2.0. It's fixed upstream so once that hits
unstable I can upload:
https://github.com/libsigcplusplus/libsigcplusplus/issues/1
J.
--
Life
ca095a1fcbf9bc80d4bae493c2833e615b54b51f
Author: Jonathan McDowell <nood...@earth.li>
Date: Thu Jan 18 09:40:26 2018 +
Prevent some forms of Cross Protocol Scripting attacks (Closes: #887488)
OpenOCD does not detect when a browser attempts to send data to it using
HTTP POST, allowing for a
ng 0.10.0-3, I'm not sure
there's any reason to believe 0.9.0-1 isn't affected as well but I will
need to check later today. Upstream still seem to be discussing the best
fix but I think at least:
http://openocd.zylin.com/#/c/4335/
and
http://openocd.zylin.com/#/c/4331/
seem appropriate pending anyth
Just to note that I provided prior warning of this in 873717, a pointer
to upstream's report about it and also a patch in upstream's tracker.
J.
--
After a number of decimal places, nobody gives a damn.
This .sig brought to you by the letter M and the number 25
Product of the Republic of
Just as a piece of additional information I have an updated Pulseview
0.4 pending which fixes the FTBFS + does various other cleanups. Its
upload is pending on acceptance of updated libsigrok + libsigrokdecode
packages, both of which are currently sitting in NEW.
J.
--
... Sunday morning is
On Thu, May 25, 2017 at 06:54:53PM +0300, Adrian Bunk wrote:
> On Thu, May 18, 2017 at 08:02:49PM +0100, Jonathan McDowell wrote:
> > On Sun, May 14, 2017 at 09:15:50PM +0300, Adrian Bunk wrote:
> > > On Tue, Jul 05, 2016 at 10:09:57AM +, Debian Bug Tracking S
On Sun, May 14, 2017 at 09:15:50PM +0300, Adrian Bunk wrote:
> On Tue, Jul 05, 2016 at 10:09:57AM +, Debian Bug Tracking System wrote:
> >...
> > l2tpns (2.2.1-2) unstable; urgency=low
> > .
> >* Fix log buffer overrun, thanks to Dave Reeve (closes: #817837)
> >...
>
> Hi Jonathan,
>
>
Package: sssd
Version: 1.50.0-2
Severity: grave
I updated my stretch system this morning which led to it failing to
reach a login prompt; the system would start up and then avahi-daemon,
ModemManager and NetworkManager would all fail to start, then
systemd-logind would fail. This repeated in a
On Mon, Nov 07, 2016 at 11:55:13PM +0100, Uwe Hermann wrote:
> On Mon, Nov 07, 2016 at 04:25:14PM +0000, Jonathan McDowell wrote:
> > Uwe, do you have any plans for this?
>
> Yeah, might upload some new packages soonish, but long-term
> I'd be happy to hand over the full sigrok
Graham, is there any reason you haven't performed an NMU with your
patch? I've applied it successfully to pulseview 0.2.0-1.1 (currently in
sid) and thrown it at my sbuild setup and it builds fine, and it would
be nice to get this package back into testing.
Even nicer would be an update both of
Control: tags 822182 + patch
This is caused by a missing stdint.h include in dvbtune.c. The attached
patch (for debian/patches/) fixes this. I intend to do an NMU with this
fix later today, but it is possibly worth considering whether dvbtune is
still useful in the archive.
J.
--
Conscience is
On Tue, Jun 14, 2016 at 03:59:19PM +0200, Jérémie Courrèges-Anglas wrote:
> On Tue, 15 Mar 2016 14:17:08 +0000 Jonathan McDowell <nood...@earth.li>
> wrote:
> > On Thu, Mar 10, 2016 at 07:50:22PM +, Dave Reeve wrote:
> > > Running l2tpns causes a
Control: reassign 822293 tcllib
Control: found 822293 1.18-dfsg-1
Control: retitle 822293 uuid broken in tcllib when /sbin not in PATH
The UUID generation routines in tcllib 1.18 add in information from
nettool about the network information to help generate unique UUIDs.
However nettool shells
On Thu, Mar 10, 2016 at 07:50:22PM +, Dave Reeve wrote:
> Running l2tpns causes an instance crash as follows:
>
> # l2tpns -v
> *** buffer overflow detected ***: l2tpns terminated
> (full trace removed as it doesn't help)
>
> The problem exists in the ring buffer logging code. Specially the
tags 710665 pending
thanks
On Sat, Jun 01, 2013 at 01:43:51PM +0200, Andreas Beckmann wrote:
a test with piuparts revealed that your package uses files from
/usr/share/doc in its maintainer scripts which is a violation of
Policy 12.3: Packages must not require the existence of any files in
On Mon, Oct 29, 2012 at 05:46:17PM -0400, Samuel Bronson wrote:
Package: debian-keyring
Version: 2012.06.01
Severity: serious
Dear Maintainer,
The debian-keyring package seems to be getting a little stale; your
usual at-least-monthly updates stopped abruptly at the beginning of June
fixed 650544 0.4.0-1
thanks
On Wed, Nov 30, 2011 at 07:59:48PM +0100, Helmut Grohne wrote:
Package: onak
Version: 0.3.8-1
Severity: serious
Justification: Policy 10.8
The onak package creates /var/log/onak.log, but this file is never
rotated. Instead it grows indefinitely. Rotation is a
Package: gnome-keyring
Version: 3.0.0-3
Severity: grave
Justification: renders package unusable
I debated over whether this should be grave or just important, but the
inhumanity of having to type my SSH passwords first thing on a Monday
morning rather than being able to use my SSH key led me to
On Mon, May 09, 2011 at 10:03:52AM -0700, Jonathan McDowell wrote:
Package: gnome-keyring
Version: 3.0.0-3
Severity: grave
Justification: renders package unusable
I debated over whether this should be grave or just important, but the
inhumanity of having to type my SSH passwords first
I'm a bit confused by the statement that kernel-package does not work
with the current set of kernels; I built a 2.6.27-rc4 kernel from
vanilla upstream sources using it over the weekend (on i386) and tend to
build the latest vanilla kernels as they come out on my AMD64 box. I
haven't hit any
On Sun, Jan 13, 2008 at 07:41:58PM +0100, Jan Prunk wrote:
Package: onak
Version: 0.3.4-1
Severity: critical
Justification: breaks unrelated software
Please clarify this justification; what unrelated software is broken?
onak fails to install on lenny platforms tested were sparc i386.
On Sat, Aug 11, 2007 at 05:54:32PM +0100, Brett Parker wrote:
The attached patch fixes the config structure when dynamic backends are
used - the basic issue is that when the backend was loaded, it wouldn't
(neccessarily) share the config structure with the program that called
it (and had
Package: asterisk
Version: 1:1.4.8~dfsg-1
Severity: grave
Justification: renders package unusable
After performing my daily sid upgrade Asterisk fails to restart:
Setting up asterisk-config (1:1.4.8~dfsg-1) ...
Stopping Asterisk PBX: asterisk.
Starting Asterisk PBX: /usr/sbin/asterisk: error
On Wed, Mar 14, 2007 at 10:29:52AM +, Jonathan McDowell wrote:
On Tue, Mar 13, 2007 at 09:21:51PM +, Rafal Czlonka wrote:
Jonathan McDowell wrote:
When you have the package installed, does running onak index noodles
as the onak user provide any output? Can you try strace -o
On Tue, Mar 13, 2007 at 09:21:51PM +, Rafal Czlonka wrote:
Jonathan McDowell wrote:
When you have the package installed, does running onak index noodles
as the onak user provide any output? Can you try strace -o onak.strace
onak index noodles and send me the resulting onak.strace
On Thu, Mar 08, 2007 at 08:19:26PM +, Rafal Czlonka wrote:
Jonathan McDowell wrote:
Can you at least give me the md5sum of the file; I want to be certain
it's pristine.
f0cb6bc3f8c2a40d63e7deb1cd4b3131
Right, that matches my local copy.
When you have the package installed, does
On Thu, Mar 08, 2007 at 09:55:26PM +, Rafal Czlonka wrote:
Tried on non-virtual kernel, it doesn't have anything to do with it -
- still the same thing.
This is on the same host, right? A PPC? And you've completed purged the
old package and ensured there are no such files in / before
you've made look fine; I'll include them when I next
upload.
J.
--
Revd. Jonathan McDowell, ULC | Make friends.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Tue, Dec 05, 2006 at 05:36:32PM +0100, Stefan Fritsch wrote:
Package: l2tpns
Severity: grave
Tags: security
Justification: user security hole
A vulnerabilit has been found in l2tpns. See
http://secunia.com/advisories/23230/
for details.
According to secunia, it is fixed in 2.1.21.
On Thu, Aug 17, 2006 at 03:12:06PM +0200, Thijs Kinkhorst wrote:
fidogate:
* Has had a security issue reported;
* Has a number of policy violations;
* Has been orphaned for two months;
* Has 4 popcon installs with 1 vote;
* Is a couple of versions behind upstream;
* Is a gateway for
On Sun, Jul 02, 2006 at 11:42:56AM -0400, Jaldhar H. Vyas wrote:
On Fri, 23 Jun 2006, Wouter Verhelst wrote:
I'm seeing the same issue; however, while IMAPS does indeed not work,
netstat -tl shows me that dovecot does properly listen to port 143,
i.e., the regular IMAP port.
Hi Jonathan and
Package: libcrypt-cbc-perl
Severity: grave
Version: 2.12-1sarge1
The security update of libcrypt-cbc-perl to 2.12-1sarge1 causes
breakage; when the upgrade is applied I see the following errors:
Use of uninitialized value in pattern match (m//) at
/usr/share/perl5/Crypt/CBC.pm line 240, GEN0
57 matches
Mail list logo
