Hi!
On Thu, 2020-07-23 at 03:20:21 +0300, Boian Bonev wrote:
> I have had the same problem last couple of days, finally could track
> what is happening:
Hah, just had finished fixing this locally, when I checked for the bug
number to slap to the commit message, saw this. :)
> - Exit.pm installs
Control: reopen -1
Control: tag -1 - patch
On Tue, 2020-07-07 at 07:06:34 +0200, Guillem Jover wrote:
> On Wed, 2020-07-01 at 17:20:40 -0400, Daniel Kahn Gillmor wrote:
> > Further conversation about problems compiling and linking against Qt and
> > GPGME in debian suggest that th
On Tue, 2020-07-07 at 09:29:44 +, Holger Levsen wrote:
> On Mon, Jul 06, 2020 at 09:08:43PM -0700, Felix Lechner wrote:
> > > not sure if this is the same bug or just a similar one:
> > > lrwxrwxrwx 1 user user 9 Jul 3 16:07 debian/munin.service -> /dev/null
> > As for Holger's package,
ink) reflects the fix proposed
> by Guillem Jover (in cc):
Yes this is what I had locally, thanks for testing! I'm including a
fix in the next upload.
> From 8d01f1419c62e24b662abc2e1ec708a7c63fbbfe Mon Sep 17 00:00:00 2001
> From: Daniel Kahn Gillmor
> Date: Wed, 1 Jul 2020 17:00:
Control: clone -1 -2
Control: reassign -2 dgit
Control: retitle -2 dgit: Incorrect use of Dpkg::Source::Package argument
On Fri, 2020-07-03 at 11:09:40 +0100, Ian Jackson wrote:
> Guillem Jover writes ("Re: Bug#964017: grep-excuses"):
> > On Tue, 2020-06-30 at 14:15:13 +0100
Control: reassign -1 dpkg-dev
Control: retitle -1 dpkg-source: Considers missing symlink targets directory
traversals
Control: found -1 1.20.0
On Sat, 2020-07-04 at 01:20:18 +0200, Andreas Beckmann wrote:
> Source: dpkg,firmware-nonfree
> Version: 20190717-2
> Severity: serious
> Tags: ftbfs
>
On Fri, 2020-07-03 at 05:27:46 -0700, Felix Lechner wrote:
> Why did you lower the severity instead of releasing a fix?
As explained, because the severity seemed off. Also because there
are still other regressions being dealt with…
> If version 1.20.3 progresses to testing, Lintian loses its
Hi!
On Fri, 2020-07-03 at 14:12:10 +, Holger Levsen wrote:
> not sure if this is the same bug or just a similar one:
Yeah, related, but not entirely the same.
> [...]
> dpkg-source: info: extracting munin in munin-2.0.63
> dpkg-source: info: unpacking munin_2.0.63.orig.tar.gz
> dpkg-source:
Hi!
On Tue, 2020-06-30 at 14:15:13 +0100, Ian Jackson wrote:
> Package: src:dpkg
> Version: 1.20.2
> User: debian...@lists.debian.org
> Usertags: breaks
> Affects: dgit
> > autopkgtest regression
> > in dgit (9.11) on amd64
> > due to dpkg (1.19.7 to 1.20.2)
> > test info
> >
Control: severity -1 minor
On Fri, 2020-07-03 at 01:54:11 +0300, Andrei POPESCU wrote:
> Control: reassign -1 dpkg-dev
> On Mi, 01 iul 20, 15:47:53, Felix Lechner wrote:
> > Control: retitle -1 dpkg-source: False positive 'points outside source root'
> > Control: severity -1 serious
> > The
On Mon, 2020-06-29 at 10:27:51 +0900, Norbert Preining wrote:
> > I assume you have the key found in the upstream/signing-key.asc in
> > your keyring,
>
> No, I don't have it. Is this a (new?) requirement?
No, was just a wild guess in case gpg was getting confused by seeing a
missing private key
Hi!
On Mon, 2020-06-29 at 09:19:18 +0900, Norbert Preining wrote:
> Package: libdpkg-perl
> Version: 1.20.2
> Severity: serious
> Justification: breaks unrelated packages
> it seems that the bump to 1.20 changed the behaviour of building
> packages, i.e., dpkg-source -b . doesn't work anymore,
Control: clone -1 -2
Control: reassign -2 sbuild
Control: retitle -2 sbuild: Uses deprecated Dpkg::Build::Info function
Control: severity -2 important
[ Retrying with the correct control syntax this time. :) ]
On Sun, 2020-06-28 at 12:37:25 +0200, Guillem Jover wrote:
> [ Perhaps
Control: clone -1 -2 sbuild
Control: retitle -2 sbuild: Uses deprecated Dpkg::Build::Info function
Control: severity -2 important
[ Perhaps due to autopkgtest failure this should be serious? I'm
leaving this up to the maintainers. :) ]
Hi!
On Sun, 2020-06-28 at 12:18:44 +0200, Sven Joachim
Control: severity -1 serious
On Fri, 2019-12-20 at 03:33:48 +0100, Guillem Jover wrote:
> Source: latencytop
> Source-Version: 0.5
> Severity: important
> This package uses a non-sensical and mismatched source format and
> version. The version is that of a native package,
Control: retitle -1 libgcc1: Can switch to use new Allow-Internal-Symbol-Groups
for aeabi symbols
On Wed, 2014-01-15 at 20:49:30 +0100, Guillem Jover wrote:
> Package: libgcc1
> Version: 1:4.8.2-13
> Severity: wishlist
>
> With dpkg-dev 1.17.6, there's a new symbols file field
Control: reassign -1 debian-policy
Control: retitle -1 debian-policy: Binary and Description fields not mandatory
in .changes on source-only uploads
On Mon, 2020-06-22 at 18:51:21 -0700, Felix Lechner wrote:
> Package: dpkg
> Severity: normal
> X-Debbugs-CC: debian-lint-ma...@lists.debian.org
>
Hi!
On Sat, 2020-05-30 at 14:58:50 +0200, Paul Gevers wrote:
> Source: dpkg
> Version: 1.19.7
> Severity: serious
> X-Debbugs-CC: debian...@lists.debian.org, make-d...@packages.debian.org
> Tags: sid bullseye
> User: debian...@lists.debian.org
> Usertags: needs-update
> Control: affects -1
Hi!
On Sat, 2020-04-11 at 14:44:32 +0200, Sebastian Andrzej Siewior wrote:
> Package: dpkg
> Version: 1.19.7
> Severity: wishlist
> I've been thinking about parallel decompression for dpkg/xz. Is there
> any interest in doing this? I hacked parallel-unxz [0] in the meantime
> to see what is
Control: reassign -1 python3-distro
Control: retitle -1 python3-distro: Please mark as Multi-Arch: foreign
On Thu, 2020-06-11 at 15:14:20 +0100, Mike wrote:
> Package: dpkg
> Version: 1.19.7
> Severity: important
> I am trying to cross-grade at least some of my system from i386 to amd64.
> In
Hi!
On Sun, 2020-06-14 at 21:51:46 -0400, Boyuan Yang wrote:
> On Tue, 21 Apr 2020 21:44:40 -0400 Boyuan Yang wrote:
> > (With my Debian Chinese Team member hat on) Please find the updated
> Simplified
> > Chinese translation for dpkg in the attachment. This updated PO file
> should be
> >
Hi!
On Wed, 2016-09-21 at 08:58:11 +0200, Samuel Thibault wrote:
> Control: reassign -1 hurd
> Control: block -1 by 818618
>
> Helmut Grohne, on Wed 21 Sep 2016 06:09:22 +0200, wrote:
> > Thus I suggest to close this bug or turn it into wishlist bugs for the
> > above.
>
> Right. Also adding
On Thu, 2020-06-11 at 18:32:04 -0700, Felix Lechner wrote:
> On Wed, Mar 11, 2020 at 5:37 AM Ian Jackson wrote:
> >
> > I hope that whatever occurs more widely, this particular message can
> > be downgraded appropriately so that by default it is an warning rather
> > than an error. That's all I'm
Control: tags -1 patch
*Sigh*
On Wed, 2020-06-10 at 08:38:05 -0700, Felix Lechner wrote:
> On Tue, Jun 9, 2020 at 11:15 PM Chris Lamb wrote:
> >
> > Felix, can you help out? I am not in a position to contribute to this
> > discussion itself.
>
> Well, I wish I could. Guillem makes many
Source: msmtp
Source-Version: 1.8.8-1
Severity: wishlist
Hi!
I was trying to use the keepassxc Secret Service integration support
with msmtp, when I realized this is only provided with the msmtp-gnome
package which diverts the program with a rebuild of the binary with
libsecret support.
This
Hi!
On Tue, 2020-05-26 at 17:59:33 +0200, Axel Beckert wrote:
> Johannes Schauer wrote:
> > And I got the same error as Otto ("Unmet build dependencies:
> > build-essential:native")
> One idea was to add some logic to automatically decide if we can use
> dpkg-buildpackage or not and if not, fall
Package: ruby-erubis
Version: 2.7.0-3
Severity: normal
Hi!
When using vagrant, I'm getting the following warning:
,---
NOTE: Gem::Specification#rubyforge_project= is deprecated with no
replacement. It will be removed on or after 2019-12-01.
Gem::Specification#rubyforge_project= called
Package: ruby-net-sftp
Version: 1:2.1.2-4
Severity: normal
Hi!
When using vagrant, I'm getting the following warnings:
,---
NOTE: Gem::Specification#rubyforge_project= is deprecated with no
replacement. It will be removed on or after 2019-12-01.
Gem::Specification#rubyforge_project=
Source: mariadb-10.3
Source-Version: 1:10.3.22-1
Severity: normal
Hi!
This package embeds the mariadb-connector-c into the libmariadb/
directory. That library is licensed under the LGPL-2.1, but the
debian/copyright file does not reflect this, and the catch-all «*»
entry makes it look like this
Control: reassign -1 ucf
Control: retitle -1 ucf: Use DPKG_FORCE to handle dpkg --force-* options
On Mon, 2020-05-11 at 22:39:10 -0700, Manoj Srivastava wrote:
> severity 925375 wishlist
> retitle 925375 dpkg could set confnew/confold env variables for ucf
> Yes, dpkg and ucf are
Package: webext-keepassxc-browser
Vesrion: 1.6.3+repack1-1
Severity: important
[ Perhaps this deserves to be serious? :) ]
Hi!
Thanks for packaging this, it's been very helpful! :)
While trying to use this extension with chromium, I was met with error
messages about not being able to connect
Package: po4a
Version: 0.59.1-1
Severity: normal
Hi!
The POD parser marks the format name in =begin/=for/=end tags as
translatable, but this text should not be translated as it is part of
the syntax. I've very briefly checked the po4a and Pod::Parser code
and didn't see an obvious way to handle
On Thu, 2020-06-04 at 15:58:47 -0700, Felix Lechner wrote:
> > This change means that any current caller which uses lintian as part
> > of its acceptance testing will now silently let broken things through
>
> As I explained on IRC this statement is probably untrue (and you did
> not have the
Hi!
On Thu, 2020-06-04 at 23:06:29 +0100, Chris Lamb wrote:
> severity 962158 serious
> thanks
> > Severity: important
> >
> > This probably deserves to be serious, but I'm not sure I can be
> > bothered…
>
> I can relate to this feeling so let me do this for you. At the very
> least, this
On Thu, 2020-06-04 at 02:39:12 +, Felix Lechner wrote:
> Control: tag -1 pending
>
> Remove command line option --fail-on from the settings in configuration
> files. (Closes: #962157)
>
> The configuration file
Package: lintian
Version: 2.80.0
Severity: important
[ This probably deserves to be serious, but I'm not sure I can be
bothered… ]
Hi,
As was mentioned on debian-devel@l.d.o, and on #debian-qa, the new
default is very problematic, and has not been properly justified.
The general expectation
Package: lintian
Version: 2.80.0
Severity: normal
Hi,
The newly introduced --fail-on option has no way to override a fail-on
setting in the configuration file (say «fail-on=error,warning») to set
it to no error on any condition (as in «--fail-on=none» or similar).
Thanks,
Guillem
Hi!
On Fri, 2020-05-22 at 01:06:51 +0200, Axel Beckert wrote:
> Control: tag -1 moreinfo
> Guillem Jover wrote:
> > This package contains the «debsums» program, which directly accesses
> > the dpkg internal database, instead of using one of the public
> > interfaces pro
Hi!
[ CCing Étienne Mollier for the patch provided. ]
On Mon, 2019-08-05 at 14:02:31 +0200, Chris Hofstaedtler wrote:
> Control: tags -1 + help confirmed
> * Laurent Bigonville [190805 13:19]:
> > On 5/08/19 12:22, Chris Hofstaedtler wrote:
> > > * Laurent Bigonville [190805 10:20]:
> > > >
Control: severity -1 serious
Control: tags -1 + patch
Hi!
This is making at least aptitude and dpkg FTBFS, so bumping to serious.
While the previously sent patches might not actually cover the entire
codebase, as I've not checked all possible instances, they should fix
the problems specific to
s are swapped, nor whether there are other directory
creations missing, though, so that might be worth having a look over.
Thanks,
Guillem
From eaf4f65d4e57a06def62bf89db4f00dd4871be08 Mon Sep 17 00:00:00 2001
From: Guillem Jover
Date: Mon, 18 May 2020 23:39:11 +0200
Subject: [PATCH 1/2] po4a: Find t
Hi!
On Mon, 2020-05-18 at 22:12:04 +0200, Martin Quinson wrote:
> - Le 18 Mai 20, à 18:58, Guillem Jover guil...@debian.org a écrit :
> > Package: po4a
> > Version: 0.58.1
> > Severity: normal
> > When there is a closing parenthesis at the end of line, po4a pa
On Mon, 2020-05-18 at 22:09:21 +0200, Martin Quinson wrote:
> I was thinking about a specific mode=eof that would not need a
> position nor a boundary to put the addendum at the end of the file.
> Would it fit your needs?
Oh, that would be even better yes! The fake boundaries always felt a
bit
Package: po4a
Version: 0.58.1-1
Severity: normal
Hi!
While converting the dpkg man pages from troff to POD, I needed to
convert the addenda too, which was using this header for all addenda:
,---
PO4A-HEADER:mode=after;position=^\.TH;beginboundary=FakePo4aBoundary
`---
Which is nice and
Package: po4a
Version: 0.58.1-1
Severity: wishlist
Hi!
Thanks for adding support for addenda in po4a_paths (in #823189). When
I was switching dpkg to use that, I realized that while this works
nicely in this case, it might be problematic when a project wants to
generate output from different
Package: po4a
Version: 0.58.1
Severity: normal
Hi!
When there is a closing parenthesis at the end of line, po4a parses it
and injects two spaces in the msgid text. I've noticed this when
reviewing the generated «.po» files from both troff and POD source.
Here's a test case:
,--- test.pod ---
Hi!
On Tue, 2020-04-28 at 06:48:21 +0200, Axel Beckert wrote:
> Package: lintian
> Version: 2.68.0
> lintian on aptitude-robot emits (beyond others) these two tags of which
> I'm not sure if they're true or false positives:
>
> W: aptitude-robot: uses-dpkg-database-directly
On Mon, 2020-04-20 at 11:55:42 -0700, Josh Triplett wrote:
> On Sun, 19 Apr 2020 23:12:28 +0200 Guillem Jover wrote:
> > On Sun, 2020-04-19 at 13:45:17 -0700, Josh Triplett wrote:
> > > Package: dpkg-dev
> > > Version: 1.19.7
> > > Severity: normal
> > &g
m
From f3bc14192d80a40c7376bced5e7af27f23de099c Mon Sep 17 00:00:00 2001
From: Guillem Jover
Date: Sun, 19 Jan 2020 01:10:40 +0100
Subject: [PATCH] Parametrize files
This should help both Debian and its derivatives, as now all these
should be able to do most of the work by just adding a new params/
file and updating the
Source: base-files
Source-Version: 11
Severity: normal
Hi!
Attached a patch to switch URLs from http to https.
Thanks,
Guillem
From 731eafe5edad6e79a0d23c4fff60e38a3683cd92 Mon Sep 17 00:00:00 2001
From: Guillem Jover
Date: Tue, 21 Apr 2020 14:35:19 +0200
Subject: [PATCH] Switch to use https
On Thu, 2020-04-30 at 19:26:46 +0200, Max Kellermann wrote:
> On 2020/04/30 18:32, Guillem Jover wrote:
> > You are missing the linux-libc-dev package which gets pulled in by the
> > libc6-dev package.
>
> linux-libc-dev, libc6-dev and build-essential are all installed.
I
Control: reopen -1
On Thu, 2020-04-30 at 18:32:32 +0200, Guillem Jover wrote:
> On Thu, 2020-04-30 at 15:21:30 +0200, Max Kellermann wrote:
> > Package: liburing-dev
> > Version: 0.6-2
>
> > It appears to be impossible to build anything with liburing-dev, not
>
Hi!
On Tue, 2020-04-21 at 12:39:46 +0300, Michael Tokarev wrote:
> On Fri, 10 Apr 2020 19:27:27 +0200 Guillem Jover wrote:
>
> > The packaging is ready, but there were some issues that needed fixed
> > upstream. The blocking one is about getting the licensing situa
Hi!
On Mon, 2020-04-06 at 14:57:30 -0400, Taowa wrote:
> Package: dpkg
> Version: 1.19.7
> Tags: patch
> --require-valid-signature currently uses the DD uploading and DM
> keyrings (among others), it should also check against the DD
> nonuploading keyring as they are treated like DMs as per
Control: ressign -1 libdpkg-perl
Control: merge 950142 -1
On Thu, 2020-04-16 at 21:31:21 +0200, Jiri Palecek wrote:
> Package: dpkg
> Version: 1.20.0+nmu2~1.gbpcd9614
> Severity: normal
> Tags: patch
> while building some of my packages, I noticed they were built without
> patches applied.
Hi!
On Sun, 2020-04-19 at 13:45:17 -0700, Josh Triplett wrote:
> Package: dpkg-dev
> Version: 1.19.7
> Severity: normal
> File: /usr/share/man/man5/deb-control.5.gz
> The deb-control manpage seemed like the right place to look to find out
> if Debian control files can have trailing commas in
Hi!
On Tue, 2020-04-14 at 11:58:57 +0100, Dimitri John Ledkov wrote:
> IMHO virtualbox-guest-utils portion that does settimeofday() to host's
> time should be split into a separate subpackage, and make that one
> provide/conflicts/replaces time-daemon.
I don't think this is possible. The part
On Mon, 2020-04-13 at 17:52:08 +0100, Samuel Henrique wrote:
> On Sun, 26 Jan 2020 at 17:29, Cyril Brulebois wrote:
> > Guillem Jover (2020-01-26):
> > > I'm also not sure whether it would make sense to add also an acl-udeb
> > > binary package, which would match fo
On Tue, 2020-04-07 at 17:18:27 -0700, Sean Whitton wrote:
> On Wed 08 Apr 2020 at 01:18AM +02, Guillem Jover wrote:
> >> +The copyright information for files in a package must be copied
> >> +verbatim into ``/usr/share/doc/package/copyright``, when
> >
Hi!
On Sat, 2020-02-08 at 01:01:01 +0100, Guillem Jover wrote:
> Package: wnpp
> Severity: wishlist
> Owner: Guillem Jover
>
> * Package name: liburing
> Version : 0.4
> Upstream Author : Jens Axboe
> * URL : https://git.kernel.dk/cg
Hi!
On Tue, 2020-04-07 at 13:41:09 +1000, Paul Szabo wrote:
> Package: inetutils-telnetd
> Severity: critical
> Tags: security
> Justification: root security hole
> Looking in https://security-tracker.debian.org/tracker/CVE-2020-10188 :
>
> utility.c in telnetd in netkit telnet through 0.17
Hi!
On Sun, 2020-04-05 at 17:54:01 -0700, Sean Whitton wrote:
> Here's a patch for seconding, and for the FTP Team to approve. Thanks
> to Scott for prompting the "all copies" amendation.
> diff --git a/policy/ch-archive.rst b/policy/ch-archive.rst
> index b8ba081..4217dd4 100644
> ---
Source: hplip
Source-Version: 3.20.3+dfsg0-1
Severity: normal
Hi!
After the switch of the default python to 3.8, this is seen on
upgrades:
,---
Setting up python3 (3.8.2-2) ...
running python rtupdate hooks for python3.8...
/usr/share/hplip/base/utils.py:2060: SyntaxWarning: "is" with a
Hi!
On Thu, 2020-03-19 at 18:30:17 +0100, Guillem Jover wrote:
> Package: wnpp
> Severity: wishlist
> Tags: patch
>
> * Package name: prometheus-redis-exporter
> Version : 1.4.0
Version : 1.5.2
> Upstream Author : Oliver
> * URL
Package: wnpp
Severity: wishlist
Tags: patch
* Package name: prometheus-redis-exporter
Version : 1.4.0
Upstream Author : Oliver
* URL : https://github.com/oliver006/redis_exporter
* License : MIT
Programming Lang: Go
Description : Prometheus exporter
Package: magic-wormhole
Version: 0.11.2-1
Severity: serious
Hi!
This package does not work anymore in unstable. I guess due to the new
python-3.8 transition? Had to use a buster schroot to be able to send
some stuff today. :)
,---
$ wormhole send somedir/
Traceback (most recent call
Source: idl-font-lock-el
Source-Version: 1.5-9
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-mismatch-source-vs-version-format
Hi!
This package uses a native source format, with a non-native version,
which is rather confusing and subverts the semantics of both the
source
Source: sredird
Source-Version: 2.2.1-2
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-mismatch-source-vs-version-format
Hi!
This package uses a native source format, with a non-native version,
which is rather confusing and subverts the semantics of both the
source and
Source: gwhois
Source-Version: 20120626-1.2
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-mismatch-source-vs-version-format
Hi!
This package uses a native source format, with a non-native version,
which is rather confusing and subverts the semantics of both the
source and
Source: xfonts-marumoji
Source-Version: 0.2-11
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-mismatch-source-vs-version-format
Hi!
This package uses a native source format, with a non-native version,
which is rather confusing and subverts the semantics of both the
source
Source: xfonts-a12k12
Source-Version: 1-12
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-mismatch-source-vs-version-format
Hi!
This package uses a native source format, with a non-native version,
which is rather confusing and subverts the semantics of both the
source and
Source: cachefilesd
Version: 0.10.10-0.2
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-mismatch-source-vs-version-format
Hi!
This package uses a native source format, with a non-native version,
which is rather confusing and subverts the semantics of both the
source and
Source: aewm++-goodies
Source-Version: 1.0-10
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-mismatch-source-vs-version-format
Hi!
This package uses a native source format, with a non-native version,
which is rather confusing and subverts the semantics of both the
source
Source: vanessa-socket
Source-Version: 0.0.13-1
Severity: important
User: debian-d...@lists.debian.org
Usertags: dpkg-mismatch-source-vs-version-format
Hi!
This package uses a native source format, with a non-native version,
which is rather confusing and subverts the semantics of both the
source
Source: pkg-kde-tools
Source-Version: 0.15.31
Severity: important
Hi!
This package uses at least one obsolete Dpkg module variable
($Dpkg::version), which has been removed in dpkg 1.20.0, currently
in experimental. Public variables have been renamed to be uppercase
($Dpkg::VERSION).
Please
Hi!
On Sat, 2020-03-14 at 21:49:12 +, Daniel Shahaf wrote:
> Sean Whitton wrote on Sat, 14 Mar 2020 20:39 +00:00:
> > On Sat 14 Mar 2020 at 08:09PM +00, Daniel Shahaf wrote:
> > > Daniel Shahaf wrote on Sat, 14 Mar 2020 18:14 +00:00:
> > >> - ::
> > >> -
> > >> -
Hi!
On Sun, 2020-03-15 at 08:40:10 +1300, Andrew Bartlett wrote:
> On Sat, 2020-03-14 at 19:26 +0100, Guillem Jover wrote:
> > Source: samba
> > Source-Version: 2:4.11.5+dfsg-1
> > Severity: minor
> > This package used to use libattr for its xattr support, but got
>
Hi!
On Sat, 2020-03-14 at 14:07:34 -0700, Kees Cook wrote:
> On Sat, Mar 14, 2020 at 06:56:30PM +, Scott Kitterman wrote:
> > On March 14, 2020 12:14:48 PM UTC, Guillem Jover wrote:
> > >On Fri, 2020-03-06 at 20:43:05 -0800, Kees Cook wrote:
> > >> Package:
Source: squashfuse
Source-Version: 0.1.103-2
Severity: important
User: a...@packages.debian.org
Usertags: libattr-drop-attr-xattr-header
Hi!
This package uses the deprecated header (from libattr)
instead of the one provided now by glibc .
The former header has been removed in upstream libattr,
Source: zfs-fuse
Source-Version: 0.7.0-20
Severity: important
User: a...@packages.debian.org
Usertags: libattr-drop-attr-xattr-header
Hi!
This package uses the deprecated header (from libattr)
instead of the one provided now by glibc .
The former header has been removed in upstream libattr,
Source: fuse-convmvfs
Source-Version: 0.2.6-2
Severity: important
User: a...@packages.debian.org
Usertags: libattr-drop-attr-xattr-header
Hi!
This package uses the deprecated header (from libattr)
instead of the one provided now by glibc .
The former header has been removed in upstream
Source: fuse-posixovl
Source-Version: 1.2.20120215+gitf5bfe35-1
Severity: important
User: a...@packages.debian.org
Usertags: libattr-drop-attr-xattr-header
Hi!
This package uses the deprecated header (from libattr)
instead of the one provided now by glibc .
The former header has been removed
Source: obexpushd
Source-Version: 0.11.2-1.1
Severity: important
User: a...@packages.debian.org
Usertags: libattr-drop-attr-xattr-header
Hi!
This package uses the deprecated header (from libattr)
instead of the one provided now by glibc .
The former header has been removed in upstream libattr,
Source: mod-mime-xattr
Source-Version: 0.4-6
Severity: important
User: a...@packages.debian.org
Usertags: libattr-drop-attr-xattr-header
Hi!
This package uses the deprecated header (from libattr)
instead of the one provided now by glibc .
The former header has been removed in upstream libattr,
Source: nfs4-acl-tools
Source-Version: 0.3.3-3
Severity: important
User: a...@packages.debian.org
Usertags: libattr-drop-attr-xattr-header
Hi!
This package uses the deprecated header (from libattr)
instead of the one provided now by glibc .
The former header has been removed in upstream
Source: libarchive
Source-Version: 3.4.0-2
Severity: important
User: a...@packages.debian.org
Usertags: libattr-drop-attr-xattr-header
Hi!
This package uses the deprecated header (from libattr)
instead of the one provided now by glibc .
The former header has been removed in upstream libattr,
Source: libfile-extattr-perl
Source-Version: 1.09-4
Severity: important
User: a...@packages.debian.org
Usertags: libattr-drop-attr-xattr-header
Hi!
This package uses the deprecated header (from libattr)
instead of the one provided now by glibc .
The former header has been removed in upstream
Source: ima-evm-utils
Source-Version: 1.1-1
Severity: important
User: a...@packages.debian.org
Usertags: libattr-drop-attr-xattr-header
Hi!
This package uses the deprecated header (from libattr)
instead of the one provided now by glibc .
The former header has been removed in upstream libattr,
Source: dar
Source-Version: 2.6.8-2
Severity: minor
Hi!
This package used to use libattr for its xattr support, but got
switched to use the native support from glibc, but the Build-Depends
and Depends got left behind.
Thanks,
Guillem
Source: e2fsprogs
Source-Version: 1.46~WIP.2019.10.03-1
Severity: minor
Hi!
This package used to use libattr for its xattr support, but got
switched to use the native support from glibc, but the Build-Depends
got left behind.
Thanks,
Guillem
Source: rsync
Source-Version: 3.1.3-8
Severity: minor
Hi!
This package used to use libattr for its xattr support, but got
switched to use the native support from glibc, but the Build-Depends
got left behind.
Thanks,
Guillem
Source: libcap-ng
Source-Version: 0.7.9-2.1
Severity: minor
Hi!
This package used to use libattr for its xattr support, but got
switched to use the native support from glibc, but the Build-Depends
got left behind.
Thanks,
Guillem
Source: lxcfs
Source-Version: 3.0.4-2
Severity: important
User: a...@packages.debian.org
Usertags: libattr-drop-attr-xattr-header
Hi!
This package uses the deprecated header (from libattr)
instead of the one provided now by glibc .
The former header has been removed in upstream libattr, but
Source: libisofs
Source-Version: 1.5.2-1
Severity: minor
Hi!
This package used to use libattr for its xattr support, but got
switched to use the native support from glibc, but the Build-Depends
got left behind.
Thanks,
Guillem
Source: gfal2
Source-Version: 2.17.2-1
Severity: minor
Hi!
This package used to use libattr for its xattr support, but got
switched to use the native support from glibc, but the Build-Depends
got left behind.
Thanks,
Guillem
Source: eiciel
Source-Version: 0.9.12.1-1
Severity: important
User: a...@packages.debian.org
Usertags: libattr-drop-attr-xattr-header
Hi!
This package uses the deprecated header (from libattr)
instead of the one provided now by glibc .
The former header has been removed in upstream libattr,
Source: mhddfs
Source-Version: 0.1.39+nmu1
Severity: important
User: a...@packages.debian.org
Usertags: libattr-drop-attr-xattr-header
Hi!
This package uses the deprecated header (from libattr)
instead of the one provided now by glibc .
The former header has been removed in upstream libattr,
Source: proftpd-dfsg
Source-Version: 1.3.6c-2
Severity: minor
Hi!
This package used to use libattr for its xattr support, but got
switched to use the native support from glibc, but the Build-Depends
got left behind.
Thanks,
Guillem
Source: openscap
Source-Version: 1.2.16-2
Severity: important
User: a...@packages.debian.org
Usertags: libattr-drop-attr-xattr-header
Hi!
This package uses the deprecated header (from libattr)
instead of the one provided now by glibc .
The former header has been removed in upstream libattr,
Source: samba
Source-Version: 2:4.11.5+dfsg-1
Severity: minor
Hi!
This package used to use libattr for its xattr support, but got
switched to use the native support from glibc, but the Build-Depends
got left behind.
Thanks,
Guillem
701 - 800 of 4830 matches
Mail list logo
