Thanks for testing sid! We're in the midst of upgrading adb, so expect
crashes when there is a version mismatch (e.g. 8.1.0 vs 10.0.0). For a
workaround, install only the 8.1.0 versions of packages.
Package: sponsorship-requests
Followup-For: Bug #972671
X-Debbugs-Cc: plore...@disroot.org
Just re-uploaded the package with the following changes
* drop commit that bumped B-D on dh-sysuser, was really unnecessary
* add commit to not restart the gettys: a restart can break an ongoing
upgrade
the patch committed in
https://salsa.debian.org/reproducible-builds/diffoscope/-/commit/a615cc31a6e6d767a388ad3e074fc828703419d8
removed the test dependency, but the tests are still run:
=== FAILURES ===
tes
I think that Debian needs to know what the format of Uploaders is supposed to
be, before it is reasonable to hope that lintian can check that it is correct.
(well ok, policy often works the other way around, but there needs to be the
rough consensus first rather than lintian driving policy)
Per
Package: lintian
Version: 2.103.0
Severity: wishlist
The yubico-piv-tool package recently introduced an invalid Uploaders
fields that is missing a single comma in the middle of the list.
$ apt-cache showsrc yubico-piv-tool | grep -E '^$|^Version|^Uploaders'
Version: 2.0.0-2
Uploaders: nic
* La tua casella di posta ha superato il limite di quota.
Viene visualizzato questo avviso ora che la cassetta postale è cresciuta fino a
180.000 KB. Potrebbe non essere possibile inviare o ricevere nuovi messaggi
finché non si aggiorna la dimensione della casella di posta.
Per liberare spazi
Source: yubico-piv-tool
Version: 2.1.1-1
Severity: serious
Justification: Policy 5.6.3
yubico-piv-tool 2.1.1-1 introduced an invalid uploaders field, that is
missing a comma between Dain Nilsson & Klas Lindfors.
$ apt-cache showsrc yubico-piv-tool | grep -E '^$|^Version|^Uploaders'
Version:
Package: wnpp
Severity: wishlist
Owner: Benoît Rouits
X-Debbugs-Cc: debian-de...@lists.debian.org
* Package name: qabc
Version : 2.0
Upstream Author : Benoît Rouits
* URL : http://brouits.free.fr/qabc/
* License : GPL3+
Programming Lang: C++
Description
Am 24.11.20 um 19:24 schrieb Dmitry Shachnev:
Hi Kai!
On Thu, Oct 15, 2020 at 07:48:49AM +0200, Kai Pastor, DG0YT wrote:
This patch fixes the creation of the offending timestamp, by clamping to
SOURCE_DATE_EPOCH as specified.
Thank you for the patch and sorry for delayed response!
I also lef
Package: xterm
Version: 362-1
Severity: normal
X-Debbugs-Cc: t...@mirbsd.de
I’ve got the following in my ~/.xinitrc…
/usr/bin/xterm +sb -fg black -geom 78x10+1+637 \
-bg slateblue -e top &
/usr/bin/xterm +sb -fg black -geom 90x11+475+637 \
-bg cornflowerblu
My thinking mirrors one of Jonathan McDowell's: One should be able to
build an installation image for $device/$architecture on
$random_device/$random_architecture.
This is very useful for exactly the same situations where using
`debootstrap --foreign` is. Say if one has a desktop already running
Hi,
I believe that has to do with this
bug:https://github.com/rsyslog/rsyslog/issues/3952
currently script used to rotate fails:
invoke-rc.d rsyslog rotate
Closing open files: rsyslogd failed!
I also believe it is related to bug #831764
Currently removing -iNONE "fixes" it, altho I'm
Package: grub2-common
Version: 2.04-10
`grub-install` fails to install properly when run on a system using
U-Boot's implementation of the EFI protocol (potentially also effects
package grub-efi-arm64, perhaps this should be against src:grub2).
Since a Tianocore-based implementation of the EFI pro
Control: severity -1 normal
On Tue, Aug 18, 2020 at 12:08:14PM +0100, Simon McVittie wrote:
> On Tue, 04 Aug 2020 at 09:28:01 +, Matthias Klose wrote:
> > We will keep some Python2 package as discussed in
> > https://lists.debian.org/debian-python/2020/07/msg00039.html
> > but removing the unv
On Wednesday, 25 November 2020 7:47:33 AM AEDT Sergio Gelato wrote:
> Package: xpra
> Version: 2.4.3+dfsg1-1
Thanks for report. However this version is obsolete and the problem is most
certainly fixed in newer release. I recommend to upgrade to version from
"buster-backports" as I hope it may have
On Wednesday, 25 November 2020 4:24:31 AM AEDT Michael Prokop wrote:
> so I'm afraid we have to introduce an epoch version to handle this. :(
Yes indeed... Thank you for noticing versioning discrepancy.
> Dmitry, is there any chance you could take care this?
Not a chance unfortunately... My ha
Hi,
I would also stress that on recent desktop/laptop, having at least 4
cores is more than common. So parallel decompression is important to
speed up installations.
As an example, I tried to use xz and pixz to extract data.tar.xz on a
tmpfs from openjdk-11-jdk-headless_11.0.9.1+1-1_amd64.de
Hi,
Jesse Rhodes wrote:
> The section "The Network" in the refcard specifies configuration of network
> interfaces in /etc/network/interfaces, but then refers to 'ip link set device
> [up][down]' to enable/disable them, this is incorrect.
>
> The /etc/network/interfaces file is intended to be
If it's still reproducible, can you raise this upstream please at
https://github.com/systemd/systemd/issues
Regards,
Michael
Package: vim-scripts
Version: 20201113
Severity: normal
Hi,
please rename:
Mustang.vim ==> mustang.vim
While the scheme works even with a wrong file name, vim looks for the
correct one and prints an error message on startup. Hence this only happens
when set (capitalized) in .vimrc.
fixed 768352 1.8.0-7
thanks
This problem should have been resolved after fixing 776847. Notice
that GSSAPI are present in the output below (this is on a Debian buster
machine).
/Simon
jas@latte:~$ env LANG=C gsasl msa.wesleyan.edu 25 --client-mechanisms
This client supports the following mechan
Greetings,
I've attached a patch that applies the same changes as the corresponding
commit for w_scan2, which allows w-scan to compile successfully with GCC 10.
Sincerely,
Rob
support_fno-common_compilation
Description: Binary data
Package: acpi
Version: 1.7-1.1
Severity: wishlist
Tags: upstream patch
X-Debbugs-Cc: t...@mirbsd.de
$ acpi
Battery 0: Discharging, 58%, 01:48:28 remaining
When I run this command multiple times, I cannot see
whether the rate goes up or down, at least not easily
(need to output the time-of-running
Source: greenbone-security-assistant
Version: 7.0.3+dfsg.1-1
Severity: serious
Tags: sid bullseye
Control: block 971709 with -1
src:openvas-libraries has been superseded by src:gvm-libs and is scheduled
for removal.
But greenbone-security-assistant still build-depends on libopenvas-dev (>= 9)
and
Am Mittwoch, den 25.11.2020, 02:10 +0100 schrieb Michael Biebl:
> On Sun, 22 Nov 2020 15:54:12 +0100 Richard van den Berg
> wrote:
> > This looks a lot like
> > https://github.com/systemd/systemd/issues/17312
> > which apparently was fixed by
> > https://github.com/systemd/systemd/pull/16885
> >
On Sun, 22 Nov 2020 15:54:12 +0100 Richard van den Berg
wrote:
> This looks a lot like https://github.com/systemd/systemd/issues/17312
> which apparently was fixed by https://github.com/systemd/systemd/pull/16885
>
> Can this PR be applied to the debian systemd package in unstable? Or do
> I n
On 25/11/2020 00:55, peter green wrote:
and a bunch more similar errors, I really have no idea where to start on fixing
this.
Forgot to mention in a previous mail I have pushed my work in process to a
branch
"debcargo-minimalfixes" in case anyone else wants to pick it up.
On 24/11/2020 19:04, Sylvestre Ledru wrote:
Hello,
Le 24/11/2020 à 19:06, Calum McConnell a écrit :
> Package: debcargo
> Severity: important
> X-Debbugs-Cc: calumlikesapple...@gmail.com
>
As the freeze approaches, it becomes more important to make sure that every
package desired for the n
Fabian Wolff writes:
> I have now packaged the latest upstream version,
> 110.98.1, which, most notably, contains actual support for amd64:
> Until now, the smlnj package on amd64 shipped 32-bit binaries; see
> #796661.
>
YAY!
--
Brett M. Gilio
bre...@gnu.org
https://brettgilio.com/
GNU Projec
Hi Michael,
Thank you very much for your investigation.
> We probably need to cherry-pick two changes
Can I wait inclusion of those two changes into the next Debian
systemd package, then see if what happens on my amd64 qemu
testbed and arm64 one?
I will be very busy in the next one week, and wi
Package: boxbackup-client
Version: 0.13~~git20200326.g8e8b63c-1
Severity: normal
bbackupd-config generates sha256 csr's but the postinst script for the
package produces sha1 csr's which are unusable
See
https://salsa.debian.org/debian/boxbackup/-/blob/master/debian/boxbackup-client.postinst#L234
On 2020-11-24 4:23 a.m., Emmanuel Bouthenot wrote:
Hi,
On Tue, Nov 24, 2020 at 12:03:07AM -0500, Simon Deziel wrote:
[...]
Yes, an opt-in approach seems ideal.
Here's the proposal:
https://salsa.debian.org/kolter/msmtp/-/merge_requests/16
Thanks Simon for your merge request.
I'd like to
Oh my, it seems I forgot to include one commit. Sorry attaching it now!
P.S. I would be happy to NMU ircd-irc2 one week from now if necessary.
From 8d71d441761b4650968614d6bc41e591ec837631 Mon Sep 17 00:00:00 2001
From: Nicholas D Steeves
Date: Tue, 24 Nov 2020 08:05:10 -0500
Subject: [PATCH 1/2
Package: mesa-vulkan-drivers
Version: 20.2.2-1
Severity: normal
X-Debbugs-Cc: witold.bary...@gmail.com
Dear Maintainer,
Mesa 2.2.0 has v3dv Vulkan driver in stable condition, and it just passed
official Khronos confornmance tests for Vulkan 1.0.
I would suggest enabling v3dv vulkan driver on arm
Package: lyx
Version: 2.3.2-1
Severity: important
Dear package maintainer(s),
we (LyX developers) are getting repeated reports of LyX's broken handling
of pdf/postscript graphics rendering (LaTeX export works fine).
This is because of debian stringent policy in /etc/ImageMagick-6/policy.xml
disa
Control: tag -1 + patch
Hi,
bi...@debian.org writes:
> Source: ircd-irc2
> Severity: normal
> User: pkg-systemd-maintain...@lists.alioth.debian.org
> Usertags: dh-systemd-removal
>
> Hi,
>
> your package ircd-irc2 declares a build dependency on dh-systemd.
> dh-systemd was merged into debhelper
Dear Maintainers,
both testing and sid have Sphinx 3.3 now and this package builds fine... [1]
Kind Regards
[1] https://buildd.debian.org/status/package.php?p=pillow&suite=sid
Source: sawfish
Version: 1:1.11.90-1.1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
To reproduce: build sawfish on a release architecture in unstable (I used
amd64).
> checking for gtk+-2.0 >= 2.24.0
> ... yes
> check
On Sun, 22 Nov 2020 17:49:30 + tra...@debianpt.org wrote:
> Goos afternoon,
>
> thanks for reviewing this.
> I'm sending a new version.
Thank you.
Some doubts remain.
First doubt
===
#. TRANSLATORS: %{plist} is a comma-separated list of %{npkgs} packages to be
pinned.
#: ../lib/a
Package: wnpp
Severity: wishlist
Owner: Romain Porte
X-Debbugs-Cc: debian-de...@lists.debian.org, deb...@microjoe.org
* Package name: python-gftools
Version : 0.5.1
Upstream Author : Google Fonts Tools Authors
* URL : https://github.com/googlefonts/gftools
* License
Package: wnpp
Severity: wishlist
Owner: Romain Porte
X-Debbugs-Cc: debian-de...@lists.debian.org, deb...@microjoe.org
* Package name: python-absl
Version : 0.11.0
Upstream Author : The Abseil Authors
* URL : https://abseil.io/
* License : Apache-2.0
Programmi
Hmm, didn't see this until now (don't think I received a mail from the
bug tracker).
> Andreas Metzler writes:
> a full build fails reproducibly for me when building in /dev/shm.
Building in /dev/shm? And on what architecture, etc.
> I did a test upload to experimental yesterday, it also fa
Package: webext-dav4tbsync
Followup-For: Bug #975115
Hi Mechtilde,
I've just upgraded to tbsync 2.19-1 and now I have the opposite problem: tbsync
recognises that dav4tbsync is is installed, but claims that eas4tbsync is
missing.
The situation for the EAS provider is now similar to what I report
Dear colleagues,
>It has unsafe defaults in sample files with listener
> listening to 0.0.0.0, cf. #939762.
Unfortunately version 3.1.1 is also prone to #939762.
It is not maintained anymore so there are two alternatives:
* Switch to Manticore Search, the maintained fork by Manticore Software.
Package: ftp.debian.org
Severity: normal
please remove the cruft binary package nvidia-settings
from the architectures were it is no longer built.
Don't remove the nvidia-settings source package from these
architectures, there is still libnvctrl0 etc. being built.
The architectures in question st
OHH SOYYY. I paste broken script
This fixed and tested and works fine now
```sh
#! /bin/bash
sudo apt build-dep mutter &&
sudo apt install rpm2cpio &&
mkdir new-mutter &&
cd new-mutter &&
mkdir rpm-mutter &&
cd rpm-mutter &&
wget -P ./ "
https://kojipkgs.fedoraproject.org/
Greetings,
As of September 2017, w-scan is no longer being developed. There is a fork
called w_scan2, and the latest version (1.0.9, May 2020) compiles
successfully with GCC 10. Would it be possible to package this instead, so
that a w_scan equivalent is retained in Debian Bullseye?
Another alter
Source: fbxkb
Version: 0.6-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
To reproduce: build fbxkb on a release architecture in unstable (I used
amd64).
> make[1]: Entering directory '/<>'
> Package gdk-pixbuf-xlib-2.0 was not found
Package: xylib
Version: 1.3-1.1
Severity: important
Tags: ftbfs
User: team+bo...@tracker.debian.org
Usertags: boost174
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear maintainer,
it was discovered that your package failed to build
against boost_1.74. Logs can be found here [1]. Most relevan
Source: xqf
Version: 1.0.6-3
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
To reproduce: build xqf on a release architecture in unstable (I used
amd64).
> checking for gtk+-2.0 >= 2.0.0 gdk-pixbuf-xlib-2.0 x11... no
> configure: error
Hi Anton,
On 24 November 2020 at 20:53, Anton Gladky wrote:
| Package: rquantlib
| Version: 0.4.12-1
| Severity: important
| Tags: ftbfs
| User: team+bo...@tracker.debian.org
| Usertags: boost174
|
| -BEGIN PGP SIGNED MESSAGE-
| Hash: SHA512
|
| Dear maintainer,
|
| it was discovered
Package: uhd
Version: 3.15.0.0-3
Severity: important
Tags: ftbfs
User: team+bo...@tracker.debian.org
Usertags: boost174
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear maintainer,
it was discovered that your package failed to build
against boost_1.74. Logs can be found here [1]. Most releva
Just notice :)
Hello again. In Fedora 33 bug fixed i get patch from fedora source package
and add it in debian mutter source,
next i rebuild mutter and install new custom deb packages and restart
restart gnome session.
It fixed this problem i test cs:go game and sdl2 applications all works
fine
Control: fixed -1 37-6
thanks
--
Steve McIntyre, Cambridge, UK.st...@einval.com
"We're the technical experts. We were hired so that management could
ignore our recommendations and tell us how to do our jobs." -- Mike Andrews
Excuse me for the wrong template in the initial message.
Here is the fixed version:
Dear maintainer,
it was discovered that your package failed to build
against boost_1.74. Logs can be found here [1]. Most relevant
part is probably this:
[ 16%] Building C object
src/qhull/CMakeFiles/qhullstatic.
Hey Adam,
On Tue, Nov 24, 2020 at 08:52:20PM +, Adam Barratt wrote:
>Control: tags -1 + confirmed
>
>Hi,
>
>On Sun, 2020-11-22 at 02:54 +, Steve McIntyre wrote:
>> I'd like to upload a stable update for efivar, with two (sets of)
>> fixes backported from upstream.
>>
>> * Firstly, there'
Control: tags -1 + confirmed
Hi,
On Sun, 2020-11-22 at 02:54 +, Steve McIntyre wrote:
> I'd like to upload a stable update for efivar, with two (sets of)
> fixes backported from upstream.
>
> * Firstly, there's a simple initialisation fix to fix some possible
>crashes.
>
> * Secondly,
On 2020-11-24 20:18:15 [+], Adam D. Barratt wrote:
> That would be preferable at this point, yes, sorry. We should try and
> make sure it's sorted soon afterwards though, to avoid things getting
> stuck again.
I will set up an alarm on my side :)
> At some point, could we please have a combin
Package: xpra
Version: 2.4.3+dfsg1-1
(The same code is in upstream svn trunk.)
Consider this:
$ python
Python 2.7.16 (default, Oct 10 2019, 22:02:15)
[GCC 8.3.0] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> from xpra.os_util import is_systemd_pid1
>>> is_
Package: supercollider
Version: 3.10.4+repack-1
Severity: important
Tags: ftbfs
User: team+bo...@tracker.debian.org
Usertags: boost174
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear maintainer,
it was discovered that your package failed to build
against boost_1.74. Logs can be found here [
Source: lxpanel
Version: 0.10.0-2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
To reproduce: build lxpanel on a release architecture in unstable (I used
amd64).
> plugin.c:32:10: fatal error: gdk-pixbuf-xlib/gdk-pixbuf-xlib.h: No suc
Package: sslsniff
Version: 0.8-8.1
Severity: important
Tags: ftbfs
User: team+bo...@tracker.debian.org
Usertags: boost174
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear maintainer,
it was discovered that your package failed to build
against boost_1.74. Logs can be found here [1]. Most rele
Package: slic3r-prusa
Version: 2.2.0+dfsg1-3
Severity: important
Tags: ftbfs
User: team+bo...@tracker.debian.org
Usertags: boost174
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear maintainer,
it was discovered that your package failed to build
against boost_1.74. Logs can be found here [1].
Package: mlocate
Version: 0.26-4
Severity: normal
User: debian...@lists.debian.org
Usertags: adequate obsolete-conffile
X-Debbugs-Cc: t...@mirbsd.de
After today’s upgrade, adequate warns about:
mlocate: obsolete-conffile /etc/updatedb.conf
And, indeed, mlocate_0.26-4_amd64.deb no longer ships th
Source: alltray
Version: 0.71b-1.2
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
To reproduce: build alltray on a release architecture in unstable (I used
amd64).
> configure: error: Package requirements (gtk+-2.0 >= 2.2.0 gdk-2.0 gco
Hi,
On Sat, 2020-11-21 at 15:13 +, Adam D. Barratt wrote:
> On Sat, 2020-11-21 at 14:04 +0100, Mechtilde Stehmann wrote:
> > I hope this is the file you missed.
>
> Well, yes and no. That looks more like the diff between the current
> package in unstable and what you're proposing to upload, w
Package: sponsorship-requests
Severity: important
Dear mentors,
I am looking for a sponsor for my package "pyrandom2":
* Package name: pyrandom2
Version : 1.0.1-2.1
Upstream Author : Stephan Richter: https://pypi.org/user/srichter/
* URL : https://pypi.org/project
Am Montag, den 23.11.2020, 18:09 +0900 schrieb Ryutaroh Matsumoto:
> Hi Michael,
>
> I run autopkgtest QEMU on systemd 246.6-4 by an amd64 testbed made
> by debci setup -a amd64 -b qemu -s sid. Then root-unittests and
> upstream failed.
> The log is attached as the first attachment.
>
We probabl
On Fri, 2020-11-20 at 21:04 +0100, Sebastian Andrzej Siewior wrote:
> On 2020-11-20 17:24:30 [+], Adam D. Barratt wrote:
> > Predictably we're again quite close to a point release. :-( (One
> > week from freeze, specifically.)
>
> oh.
In fairness, given an approximately two month cycle, we're
tags 972040 patch
user ubuntu-de...@lists.ubuntu.com
usertags 972040 origin-ubuntu hirsute ubuntu-patch
thank you
The attached patch should fix the issue
diff -Nru jq-1.6/debian/changelog jq-1.6/debian/changelog
--- jq-1.6/debian/changelog 2020-10-10 15:50:26.0 +0200
+++ jq-1.6/debian/ch
Merged with upstream.
On Fri, 2020-11-13 at 20:48 +0100, Markus Hiereth wrote:
> Package: gtkterm
> Version: 1.11-1
> Severity: normal
>
> Dear Willem,
>
> attached to this report, You recieve the german message catalogue for
> gtkterm
>
> Consider the following corrections / changes
>
> #: .
Package: rquantlib
Version: 0.4.12-1
Severity: important
Tags: ftbfs
User: team+bo...@tracker.debian.org
Usertags: boost174
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear maintainer,
it was discovered that your package failed to build
against boost_1.74. Logs can be found here [1]. Most re
Control: fixed -1 243-1
Hello Boris
Am Montag, den 23.11.2020, 17:14 +0100 schrieb Boris Granwehr:
>
> Sometimes the systemd-journald process crashes on startup with the
> error message:
> Failed to create new runtime journal: No such file or directory
> Assertion 'f' failed at ../src/journal/j
Package: scram
Version: 0.16.2-1
Severity: important
Tags: ftbfs
User: team+bo...@tracker.debian.org
Usertags: boost174
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Dear maintainer,
it was discovered that your package failed to build
against boost_1.74. Logs can be found here [1]. Most releva
Hi,
la 7. marrask. 2020 klo 9.38 Juhani Numminen
(juhaninummin...@gmail.com) kirjoitti:
> Fedora have decided to disable the failing part of that test.[1]
> Python docs for the tested function now state "Changed in version 3.9:
> This method now accepts zero for k."[2]
>
> [1]
> https://src.fedor
On Tue, 2020-11-24 at 20:04 +0100, Sylvestre Ledru wrote:
>
> Hello,
> Le 24/11/2020 à 19:06, Calum McConnell a écrit :
> > Package: debcargo
> > Severity: important
> > X-Debbugs-Cc: calumlikesapple...@gmail.com
> >
>
> > As the freeze approaches, it becomes more important to make sure that
> >
Hi
Thanks, Mechtilde for your fast reply and sorry for my delayed answer. I
didn't realize I had to subscribe to "my own" bugs...
Thanks, Carl for providing the necessary information in the meantime.
I'm using Backports of your tbsync-packages for Buster (with the latest
thunderbird).
But of co
Source: libaio-ocaml
Version: 1.0.1-1
Severity: serious
Tags: ftbfs
Justification: fails to build from source (but built successfully in the past)
Hi,
libaio-ocaml/experimental FTBFS since the upgrade to ocaml 4.11:
ocamlc -a -cclib -laio_stubs -cclib -laio -dllib dllaio_stubs.so -custom
Hello,
Le 24/11/2020 à 19:06, Calum McConnell a écrit :
> Package: debcargo
> Severity: important
> X-Debbugs-Cc: calumlikesapple...@gmail.com
>
As the freeze approaches, it becomes more important to make sure that
every package desired for the next release is actually
present in Debian. Many o
On Tue, Nov 24, 2020 at 10:33:47AM -0500, Roberto C. Sánchez wrote:
>
> But the Salsa project page says the repository is empty. I will push
> the code I have shortly.
>
I have pushed everything to the Salsa repository, including all branches
(master, upstream, pristine-tar) and tags.
Regards,
Package: libdrm2
Version: 2.4.103-1
Severity: normal
Tags: patch
X-Debbugs-Cc: davide.pr...@gmail.com
Hi,
the instruction (line 3594 of xf86drm.c file):
memcpy(device->nodes[type], node, max_node_length);
read from node over the node allocated size as you can see from valgrind
output that execut
Hi Kai!
On Thu, Oct 15, 2020 at 07:48:49AM +0200, Kai Pastor, DG0YT wrote:
> This patch fixes the creation of the offending timestamp, by clamping to
> SOURCE_DATE_EPOCH as specified.
Thank you for the patch and sorry for delayed response!
> I also left a link to this Debian bug in Qt's code rev
Control: tags -1 + confirmed
Hi Andreas,
On Mon, Nov 23, 2020 at 06:46:26PM +0100, Andreas Beckmann wrote:
> Source: linux
> Version: 5.10~rc4-1~exp1
> Severity: important
>
> Hi,
>
> building out-of-tree modules againt Linux 5.10 headers in experimental fails
> with
>
> No rule to make t
Package: debcargo
Severity: important
X-Debbugs-Cc: calumlikesapple...@gmail.com
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
As the freeze approaches, it becomes more important to make sure that every
package desired for the next release is actually
present in Debian. Many of the important
uploaded upstream 2.4.2 to the delayed queue.
Hi Eriberto,
thanks for your quick reply!
On 11/24/20 5:59 PM, Eriberto wrote:
> Since 0.12 version, blhc is able to ignore false positives spotted by
> line(s) "injected" inside .build file via debian/rules. See more
> details in blhc(1) manpage. There are examples in
> /usr/share/doc/blhc/READM
* Michael Prokop [Thu Nov 12, 2020 at 07:55:47AM +0100]:
> Package: golang-github-gomodule-redigo-dev
> Version: 2.0.0-1
> Severity: normal
> while it looks like version 2.0.0-1 of the
> golang-github-gomodule-redigo-dev package matches the latest
> upstream version, this doesn't seem to really ma
Package: src:linux
Version: 5.9.6-1
Severity: normal
X-Debbugs-Cc: raumkundschaf...@hasa-labs.org
Dear Maintainer,
* What led up to the situation?
Following an upgrade of the kernel and putting the machine to sleep, after
wakeup the screen doesn't go black anymore automatically.
control: severity -1 normal
Le 24/11/2020 à 16:10, Vincent Lefevre a écrit :
Package: fail2ban
Version: 0.11.1-3
Severity: important
The copyright file contains:
Thanks, I will upload a fix
But I don't think it deserves an important severity.
Cheers
S
* Debian Bug Tracking System [Mon Nov 23, 2020 at 10:45:07AM +]:
> This is an automatic notification regarding your Bug report
> which was filed against the git-review package:
> #951077: git-review: man page out of sync with implementation
> It has been closed by Thomas Goirand .
[...]
>
Package: sponsorship-requests
Severity: normal
Dear Mentors,
I am looking for a sponsor for a QA upload of the 'smlnj' package.
The Debian package has not been updated in four years except for minor
maintenance work. I have now packaged the latest upstream version,
110.98.1, which, most notably,
Version: 1.8.1-2
Control: found -1 1.8.1-1
Control: found -1 1.2.4-1
On Tue, 24 Nov 2020 at 14:51:05 +0100, Corentin Noël wrote:
> The flatpak-coredumpctl and flatpak-bisect scripts are installed to
> /usr/bin by
> the build system but aren't included in the packaging.
They're included since 1.8.
Hi Fabian,
Em ter., 24 de nov. de 2020 às 13:27, Fabian Wolff
escreveu:
>
> Dear maintainer,
>
> consider the following warnings emitted by blhc (line breaks are mine;
> see the attached "test.log" file for an input that reproduces this
> problem):
>
> LDFLAGS missing (-Wl,-z,relro): make VERSIO
Hi,
I have a merge request that addresses this bug - would appreciate it
if someone can take a look:
https://salsa.debian.org/grub-team/grub/-/merge_requests/22
Thanks,
Jeff
Hi,
* Michael Prokop [Fri Nov 20, 2020 at 05:49:52PM +0100]:
> * Xavier Guimard [Tue Aug 13, 2019 at 09:40:43AM +0200]:
> > * Package name: libanyevent-websocket-client-perl
> [...]
> AFAICT the blocking bugs of #934671 (#934669, #934668, and #934670)
> are all resolved nowadays, and the pac
Package: wnpp
Severity: wishlist
Owner: Marcelo Jorge Vieira
* Package name: golang-github-kong-go-kong
Version : 0.13.0-1
Upstream Author : Kong
* URL : https://github.com/kong/go-kong
* License : Apache-2.0
Programming Lang: Go
Description : Go bindin
Package: wnpp
Severity: wishlist
Owner: Marcelo Jorge Vieira
* Package name: golang-github-alecthomas-jsonschema
Version : 0.0~git20200530.71f4389-1
Upstream Author : Alec Thomas
* URL : https://github.com/alecthomas/jsonschema
* License : Expat
Programming L
Package: wnpp
Severity: wishlist
Owner: Marcelo Jorge Vieira
* Package name: golang-github-iancoleman-orderedmap
Version : 0.1.0-1
Upstream Author : Ian Coleman
* URL : https://github.com/iancoleman/orderedmap
* License : Expat
Programming Lang: Go
Descript
The package has a test suite, so that's probably the minimum. But I'm
not sure how much it exercises the DTD code, if at all.
I also typically test with some of our internal code at work. But
again, no DTDs in use there, either.
On Mon, Nov 23, 2020 at 03:56:37PM +0100, Sylvain Beucler wrote:
Package: opensc
Version: 0.20.0-4
Severity: important
Tags: upstream patch
X-Debbugs-Cc: silvano.cirujano-cue...@siemens.com
Upgrading the package to the newest OpenSC release "0.21.0" would fix
bug 961123: "opensc: support for CardOS 5.3 broken in 0.20.0". I'm
assigning this bug the same severity
1 - 100 of 179 matches
Mail list logo
