Package: dpkg
Version: 1.19.4
Followup-For: Bug #921031
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu disco ubuntu-patch
In Ubuntu, the attached patch was applied to achieve the following:
* scripts/Dpkg/Source/Package.pm: use Dpkg::Source:Format (closes: #921031)
Simple
On Wed, Feb 20, 2019 at 12:28:48AM +0100, Sebastian Andrzej Siewior wrote:
> On 2017-10-12 23:44:37 [+0200], To 859...@bugs.debian.org wrote:
> > this is a remainder about the openssl transition [0]. We really want to
> > remove libssl1.0-dev from unstable for Buster. I will raise the severity
> >
Package: beep
Version: 1.4.3-1
Followup-For: Bug #922667
Dear Maintainer,
I tried adding my user to the beep group, but nothing changed. Then I read
everything in /usr/share/doc/beep/INSTALL.md and here are my thoughts,
Before adding my user to the beep group, I had to create that group. I did
On Tue, Feb 19, 2019 at 03:31:21PM +0100, Thierry fa...@linux.ibm.com wrote:
> Package: galax
> Version: 1.1-15
> Severity: important
>
> Compilation on ppc64el fails with the message
>
> ERROR: unable to find camomileLibrary.cmi in /usr/lib/ocaml/camomile
Thanks for your bug report. This
Hello,
Le 20/02/2019 à 00:07, A.C. a écrit :
Source: llvm-toolchain-7
Severity: important
Dear Maintainer,
A recently merged patch that introduced support for KFreeBSD broke the API
compatibility by introducing pointless renamings of enumeration values (KFreeBSD
to kFreeBSD) and
On Sun, 10 Feb 2019 08:54:19 +0100 Matijs van Zuijlen wrote:
> Package: minissdpd
> Version: 1.5.20180223-5
> Severity: normal
>
> Dear maintainer,
>
> With the most recent upgrade of minissdpd, the 'Address already in use'
> messages from #903783 seem to have returned. They now appear every five
On 20/02/2019 01:56, Pierre Ynard wrote:
This isn't an issue in initscripts, and I think it wouldn't even be
possible to add Breaks statements against offending unpurged packages;
so not much can be done here. The offending initscripts are either from
the local administrator or from obsolete
> I fail to see any typos in my copy of the script. Can you provide more
> details? Is this the same as #587665 fied in -11?
This was most likely a duplicate of #587665, and without other
information there is nothing we can do. I think we should merge and/or
close this.
--
Pierre Ynard
Source: odb-api
Severity: wishlist
Dear Maintainer,
Please make it possible to compile with Flang.
-- System Information:
Debian Release: buster/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 4.19.0-3-amd64 (SMP w/2 CPU cores)
Kernel taint
Source: r-cran-vegan
Version: 2.5-4+dfsg-1
Severity: serious
X-Debbugs-CC: debian...@lists.debian.org
User: debian...@lists.debian.org
Usertags: regression
Hi Maintainer
Since the upload of 2.5-4+dfsg-1, r-cran-vegan has been failing its
own autopkgtests [1] with the following error:
On Tue, 19 Feb 2019, Paul Gevers wrote:
> Britney is using RC bugs to determine if package may migrate from
> unstable to testing. If an RC bug is only in unstable and not in
> testing, the package is not allowed to migrate. However, in the above
> case simplejson is listed in both
>
only if the interface starts with a digit, otherwise you get a nice
error msg :)
Hi Sebastian
On Wed, Feb 20, 2019 at 12:28:39AM +0100, Sebastian Andrzej Siewior wrote:
> On 2019-02-19 22:32:59 [+0100], Moritz M??hlenhoff wrote:
> > Someone should NMU it soon, then. We're down to four remaining packages
> > using OpenSSL 1.0 and this will not drag for more than a few weeks,
On Wed, 20 Feb 2019, Dylan Thurston wrote:
> I opened this bug because I thought this might be a candidate for
> "small targeted fixes", per the soft freeze policy. It would be an
> update to one TeXlive package, that is currently broken.
Updates to texlive packages cannot (easily) be done only
Package: wnpp
Severity: wishlist
Owner: Adam Borowski
* Package name: pmdk-convert
Version : 1.5.1
Upstream Author : Intel
* URL : https://github.com/pmem/pmdk-convert
* License : BSD-3
Programming Lang: C, C++
Description : convert pmdk/pmemobj pools
Hello,
While I think there were certainly good points raised about issues with
it, that mv code to migrate /{dev,run}/shm and contents in postinst was
long removed, and nowadays is only left code to set up directories and
symlinks at bootup, when they're still empty. All this `mv /run/shm/*
Hi Helmut,
I have also had this problem since December and hoped no one would
notice. Personally, I think it is related to Perl 5.28.1-3, but I am
not sure.
We also recently added a parallel collection that may have a race
condition. I will look at it in the coming days. Thank you for your
On Wed, Feb 20, 2019 at 01:32:54PM +0900, Norbert Preining wrote:
> Hi
>
> > The spath3 library has recently (2019-02-12) been updated to fix this.
>
> Thanks, unfortunately I cannot upload new packages to Debian, and Buster
> is already in freeze. If it is important for you, please see
>
On Tue, 12 Feb 2019 09:32:48 +0700 Arnaud Rebillout
wrote:
> I looked into this a bit yesterday.
>
> As mentioned in the issue upstream at
> https://github.com/etcd-io/etcd/issues/9353, the fix has been merged in
> the master branch of etcd in March 2018, almost a year ago. The
> conversation
Control: reopen 900671
progress still fails to cross build, because the patch was incorrectly
applied. The patch asked to include "buildtools.mk", but what ended up
being included is "buildflags.mk". Thus PKG_CONFIG is literally
"pkg-config" rather than set up by buildtools.mk.
Helmut
Recent changes in upstream master make blueman compatible with
adwaita-icon-theme and papirus-icon-theme. blueman 2.0 is not.
tango-icon-theme is not compatible at all.
Package: lintian
Version: 2.6.0
Severity: important
User: helm...@debian.org
Usertags: rebootstrap
I use lintian to detect wrongly cross built packages. In this setup,
lintian is run by sbuild inside the (unstable) schroot after the build.
I pass "-T
Control: tags -1 + confirmed
Using the correct syntax for tagging
--
Holger Wansing
PGP-Fingerprint: 496A C6E8 1442 4B34 8508 3529 59F1 87CA 156E B076
Hi
> The spath3 library has recently (2019-02-12) been updated to fix this.
Thanks, unfortunately I cannot upload new packages to Debian, and Buster
is already in freeze. If it is important for you, please see
intermediate packages as described here:
Dear Maintainer,
Taking bug #922176 into account, it works well with the following code.
debian/ubuntu-keyring.postinst: line 5
```
case "$1" in
install|configure)
TRUSTEDPARTS="/etc/apt/tusted.gpg.d/"
eval "$(apt-config shell TRUSTEDPARTS Dir::Etc::trustedparts/d)"
#
My Name is Johann Reimann and i have something important to discuss with you
but only with your permission i will proceed.
Regards
J. Reimann
On Sun, 17 Feb 2019 20:54:34 + to...@debian.org (Dr. Tobias Quathamer)
wrote:
> Source: simgear
> Source-Version: 1:2018.3.2+dfsg-5
>
> We believe that the bug you reported is fixed in the latest version of
> simgear, which is due to be installed in the Debian FTP archive.
Thanks for this
On Sat, Feb 16, 2019 at 10:25:01PM -0600, Daniel Lewart wrote:
>Steve,
>
>> Right, that's as expected. The only non-free bit about those images is
>> that they include some non-free firmware packages too. Otherwise
>> they're just the same as the normal free images. Is there a problem
>> with
Control: forwarded -1 http://www.openldap.org/its/?findid=8982
Update since this came up again in IRC:
slapd.h, portable.h, and other generated headers such as config.h are
"private and subject to change without notice" [ITS#7283]. IMO that
makes them unsuitable for shipping in a Debian
On Wed, Feb 20, 2019 at 12:07:17AM +0100, Javier Barroso wrote:
> Hello,
>
> On Tue, Feb 19, 2019 at 11:33 PM Thomas Dickey wrote:
>
> > I was not able to reproduce this when it was reported, nor can I reproduce
> > it using the same source now (and same applies to the current packages).
> >
>
This isn't an issue in initscripts, and I think it wouldn't even be
possible to add Breaks statements against offending unpurged packages;
so not much can be done here. The offending initscripts are either from
the local administrator or from obsolete package versions, so I don't
see any point in
Hi. Why did the package start depending on QtWebEngine at all? I had to
hold it because of that. If I got the upstream README correctly,
QtWebEngine is needed only for IDE, which is in another package.
Package: texlive-pictures
Version: 2018.20190131-1
Severity: normal
Dear Maintainer,
The TikZ library 'spath3' uses illicit variant forms, and stops with a
warning. As a result, the 'knots' and 'calligraphy' libraries are also
broken, and should not be released as-is. Details here:
Package: aptitude
Version: 0.8.11-7
Severity: normal
aptitude truncates the version number of packages, even when the
window width is large:
i A --\ wpasupplicant
Ok - thanks for the clarification - so it is not a bug, it's a feature
:D - really.
It is damn hard to combine a dark panel and menu with the rest of the
system in lighter colors, so the panel can have it's own icon set
activated.
So - for the dark panel i set the panel override as shown in
Ich beabsichtige, Ihnen einen Teil meines Vermögens als freiwillige finanzielle
Spende zukommen zu lassen. Antworten Sie auf meine E-Mail-Adresse
jian...@wang-wandagroup.com
Ich beabsichtige, Ihnen einen Teil meines Vermögens als freiwillige finanzielle
Spende zukommen zu lassen. Antworten Sie auf meine E-Mail-Adresse
jian...@wang-wandagroup.com
Package: xserver-xorg-input-libinput
Version: 0.28.2-1
Followup-For: Bug #823286
I tried removing xserver-xorg-input-synaptics, as suggested by the
language in the xserver-xorg-input-libinput package description, and my
trackpad behavior changed drastically, including losing vertical
scrolling. I
Package: mate-utils
Version: 1.20.2-1
Severity: important
Dear Maintainer,
It's currently not possible to upgrade mate-utils to 1.20.2-2 on a number
of archs, e.g., amd64, because mate-utils-common 1.20.2-2 is not available
for archs other than i386.
This issue is also visible in the PTS [1],
Package: src:linux
Version: 4.19.12-1~bpo9+1
Severity: important
Feb 19 19:01:04 vhost182 kernel: INFO: task btrfs-transacti:613 blocked for
more than 120 seconds.
Feb 19 19:01:04 vhost182 kernel: Tainted: GE
4.19.0-0.bpo.1-amd64 #1 Debian 4.19.12-1~bpo9+1
Feb 19
Please let me know if you need additional information regarding this issue.
Just updated my test machines to the newly released qemu/1:3.1+dfsg-4
and can confirm it's fixed. Thanks!
Hi!
On Tue, 2019-02-12 at 17:33:03 +, Debian Bug Tracking System wrote:
> Processing commands for cont...@bugs.debian.org:
> > # Breaks autopkgtests and is therefore a migration blocker
> > severity 921031 grave
> Bug #921031 [libdpkg-perl] Dpkg::Source::Package missing use of ::Format
>
On Mon, 18 Feb 2019, Hilmar Preuße wrote:
> So, how to got from here? My suggestion: we put the package on the black
> list and close the bug.
I am against this. There is also xdoc2.sty in the same tlpdb, and who
knows who is using that, it might work while the docindex doesn't.
What is the
Package: python3-milter
Version: 1.0.3-2
Severity: normal
Tags: patch, upstream
0 dkg@alice:~$ ipython3
Python 3.7.2+ (default, Feb 2 2019, 14:31:48)
Type "copyright", "credits" or "license" for more information.
IPython 5.8.0 -- An enhanced Interactive Python.
? -> Introduction and
On 2019-02-19 22:32:59 [+0100], Moritz Mühlenhoff wrote:
> Someone should NMU it soon, then. We're down to four remaining packages
> using OpenSSL 1.0 and this will not drag for more than a few weeks, the
> openssl1.0 is already going on for ages.
Someone just did.
> Cheers,
> Moritz
Hi Michael,
On Sun, Aug 14, 2011 at 05:22:12PM -0400, Michael P. Soulier wrote:
> Package: calibre-bin
> Version: 0.7.7+dfsg-1squeeze1
> Severity: minor
>
> Every time I shut down calibre I see this in the terminal.
>
> Exception in thread Thread-4 (most likely raised during interpreter
On 2017-10-12 23:44:37 [+0200], To 859...@bugs.debian.org wrote:
> this is a remainder about the openssl transition [0]. We really want to
> remove libssl1.0-dev from unstable for Buster. I will raise the severity
> of this bug to serious in a month. Please react before that happens.
There has
On 2019-02-20, John Paul Adrian Glaubitz wrote:
> On 2/19/19 11:56 PM, Vagrant Cascadian wrote:
>> I tried installing an armel chroot on an arm64 machine:
>>
>> $ sudo debootstrap --variant=minbase --arch=armel --no-merged-usr
>> --verbose sid /srv/chroots/armeltest
Package: openssl
Version: 1.1.1a-1
Severity: minor
When I do “openssl rand 4 | hd”, the file ~/.rnd is ignored
(judging from its tiestamp and md5sum, it’s not rewritten,
and probably not read either) despite me adding the line
RANDFILE= $ENV::HOME/.rnd
to openssl.cnf as
Control: tags 851085 + patch
Control: tags 851085 + pending
Dear maintainer,
I've prepared an NMU for conserver (versioned as 8.2.1-1.1) and I am
about to upload (RC bug with no feedback, RM bug filled).
Regards.
Sebastian
diff -u conserver-8.2.1/configure conserver-8.2.1/configure
---
On 2/19/19 11:56 PM, Vagrant Cascadian wrote:
> I tried installing an armel chroot on an arm64 machine:
>
> $ sudo debootstrap --variant=minbase --arch=armel --no-merged-usr --verbose
> sid /srv/chroots/armeltest http://deb.debian.org/debian/
> E: Unable to execute target architecture
I
Source: llvm-toolchain-7
Severity: important
Dear Maintainer,
A recently merged patch that introduced support for KFreeBSD broke the API
compatibility by introducing pointless renamings of enumeration values (KFreeBSD
to kFreeBSD) and classes/structures.
This change is not purely cosmetic and
Hello,
On Tue, Feb 19, 2019 at 11:33 PM Thomas Dickey wrote:
> I was not able to reproduce this when it was reported, nor can I reproduce
> it using the same source now (and same applies to the current packages).
>
Now it works on my laptop too, maybe a temporal problem by the time. So I'm
Package: epiphany-browser
Version: 3.31.91-2
Severity: grave
$ mkdir /tmp/p
$ HOME=/tmp/p epiphany /etc/motd
** (epiphany:11842): WARNING **: 06:53:40.412: Web process crashed
(WebKitWebProcess:12106): GLib-GObject-WARNING **: 06:53:41.133:
../../../gobject/gtype.c:4265: type id '0' is invalid
Hi Guillem,
> > Or perhaps not emit this tag for "local" packages (via the
> > versioning scheme?)
>
> I'm not sure there's any reliable way to distinguish those? I think
> most people even tend to use the defaul target distribution from dch,
> and use normal looking versions for local packages.
#894962 was probably partially due to #909151.
Thanks to Mauricio Oliveira to have fixed #909151.
https://bugs.debian.org/894962
FTBFS and Debci failure with node-process-nextick-args 2.0.0-1
https://bugs.debian.org/909151
'Uncaught TypeError: nextTick is not a function' with
Package: debootstrap
Version: 1.0.114
Severity: normal
I tried installing an armel chroot on an arm64 machine:
$ sudo debootstrap --variant=minbase --arch=armel --no-merged-usr --verbose
sid /srv/chroots/armeltest http://deb.debian.org/debian/
E: Unable to execute target architecture
This
#894962 was probably partially due to #909151.
Thanks to Mauricio Oliveira to have fixed #909151.
https://bugs.debian.org/894962
FTBFS and Debci failure with node-process-nextick-args 2.0.0-1
https://bugs.debian.org/909151
'Uncaught TypeError: nextTick is not a function' with
Sorry for not being understandable enough. I'll try it again.
In your screenshot you have papirus selected, if you select oxygen
it will change all icons except the panel icons.
It should change all icons including the panel icons.
And it does as soon lxqt-branding-debian is removed.
Thanks for
Control: retitle -1 Please warn on packages using getconf(1), except to get
PATH, _NPROCESSORS_{CONF,ONLN}
On Mon, 2017-10-30 at 09:05:46 +, Chris Lamb wrote:
> retitle 879935 Please warn on packages using getconf(1) to get PATH,
> _NPROCESSORS_{CONF,ONLN} etc.
> thanks
> > Well this only
On Mon, 2019-02-18 at 14:16:56 +0100, Chris Lamb wrote:
> > The problem with emitting this tag unconditionally, even within the
> > Debian-vendor realm, is that people create local packages for their
> > own, or for $work, etc.
>
> Hmm. Emitting such a tag here still seems right to me, or at
Hi Marc
In Debian, the pacct file is located in /var/log/account/pacct while in
Fedora it is in /var/account/pacct.
I don't see the reason to be less parsable in that location.
What is your suggestion?
Greetings,
Marcos
On 17/2/19 20:50, Marc Haber wrote:
> Package: acct
> Version: 6.6.4-2
>
> On 19-02-12 14:39:32, Georg Faerber wrote:
>> That is: option one of the second proposal ("quickly patch together a
>> Python 2 Nautilus extension that wraps mat2's CLI").
>
> Unfortunately, and sorry again for my delay working on this, there was
> no feedback. I've poked Jonas today on IRC
On 2019-01-27 06:06:08 [+0100], Moritz Muehlenhoff wrote:
> Should zorp be removed? It's incompatible with OpenSSL 1.1 and the bug has
> been unacknowledged since 15 months (859840). It's one of the few remaining
> packages blocking the removal at this point, so this doesn't get ported
> to
Hi Guillem,
> > Assuming that is why Guillem did not see it I am renaming this bug
> > to match. There is no reason why it cannot be a .changes check;
[…]
> As Mattia mentions, that's the other way around.
(I don't have that message, and nor does the BTS...?)
> The .dsc always get all files
I was not able to reproduce this when it was reported, nor can I reproduce
it using the same source now (and same applies to the current packages).
--
Thomas E. Dickey
https://invisible-island.net
ftp://ftp.invisible-island.net
signature.asc
Description: Digital signature
Hi!
On Mon, 2019-02-18 at 14:51:42 +0100, Chris Lamb wrote:
> > There is already such a tag, orig-tarball-missing-upstream-signature.
> > That's a .changes checks, not a .dsc one, so it would be emitted only
> > for -1.
Right, had seen it but from a very quick skim got the impression it
was for
Hi Guillem,
> > Do others have thoughts before I apply this patch?
>
> As I mentioned initially, I don't think the patch is ready as is, it
> even has syntax errors
Apologies; I meant to communicate some idea of applying this patch
in *spirit* :)
I would certainly agree that we need a
Package: arch-test
Version: 0.15-1
Severity: normal
Control: affects -1 debootstrap
On my pinebook, arch-test displays:
$ arch-test
arm64
armhf
Which prevents running debootstrap --arch=armel.
With arch-test removed, debootstrap is able to run fine, and I'm able
to use the chroot without
On Sun, 2019-02-17 at 23:45:37 +0100, Chris Lamb wrote:
> Do others have thoughts before I apply this patch?
As I mentioned initially, I don't think the patch is ready as is, it
even has syntax errors (at least one ‘?‘ :). It would probably need
a new pass over the newly created tags, a review of
And here the proposed patch refercing the Bug.
Regards,
Salvatore
>From 7bbadff11ddb6e87e263ebd3b6541515beb88e71 Mon Sep 17 00:00:00 2001
From: Salvatore Bonaccorso
Date: Tue, 19 Feb 2019 23:10:06 +0100
Subject: [PATCH] debian/watch: watch github page for released versions
Closes: #922726
---
Source: kde4libs
Severity: important
Tags: security
The security bug filed against kauth in #921995 also seems to affect kde4libs,
the
code is in kdecore/auth/backends/dbus/DBusHelperProxy.cpp?
Cheers,
Moritz
Source: conserver
Version: 8.2.1-1
Severity: minor
Tags: patch
Hi,
conserver releases can be found on https://github/conserver/conserver
so the debian/watch file can monitor new upstream releases on the
GitHub page for conserver.
Regards,
Salvatore
Package: needrestart
Version: 2.11-3+deb9u1
Severity: normal
Dear Maintainer,
please consider blacklisting networking.service in needrestart.conf similar to
NetworkManager or other networking related services.
After the upgrade to the stable point release 9.8 which included updates to
libc, I
Am 19.02.19 um 17:40 schrieb Moritz Mühlenhoff:
> On Fri, Feb 15, 2019 at 11:21:13AM +0100, Markus Koschany wrote:
[...]
>>
>> Upstream solved this problem by adding a new whitelist option for nodes
>> and shards and what they can request. In the latest version Zookeeper
>> would keep track of
On Fri, Dec 21, 2018 at 07:13:52PM +0100, Salvatore Bonaccorso wrote:
> Source: python-pykmip
> Version: 0.7.0-2
> Severity: important
> Tags: patch security upstream
> Forwarded: https://github.com/OpenKMIP/PyKMIP/issues/430
>
> Hi,
>
> The following vulnerability was published for
#971: "management tunnel " ignores port
-+-
Reporter: berni| Owner: (none)
Type: Bug / Defect | Status: new
Priority: minor| Milestone:
Component:
On Tue, Feb 19, 2019 at 10:30:37PM +0100, Salvatore Bonaccorso wrote:
> Hi,
>
> On Tue, Feb 19, 2019 at 10:09:15PM +0100, Moritz Muehlenhoff wrote:
> > Package: ftp.debian.org
> > Severity: normal
> >
> > Please remove conserver. It hasn't seen an upload since 2016 and
> > was removed from
Hi,
On Tue, Feb 19, 2019 at 10:09:15PM +0100, Moritz Muehlenhoff wrote:
> Package: ftp.debian.org
> Severity: normal
>
> Please remove conserver. It hasn't seen an upload since 2016 and
> was removed from testing since Nov 2017. It's one of the last
> remaining packages blocking the removal of
Source: zoneminder
Severity: grave
Tags: security
Please see:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8429
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8428
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-8427
On Wed, Feb 20, 2019 at 02:12:55AM +0500, Andrey Rahmatullin wrote:
> On Tue, Feb 19, 2019 at 10:00:34PM +0100, Moritz Mühlenhoff wrote:
> > If a transition (even though it's marginal in size) isn't an option at this
> > point
> That's not for me to decide. Should we ask the RT?
Sounds like a
On Thu, Jan 10, 2019 at 08:39:36PM +0100, Joost van Baal-Ilić wrote:
> Hi Moritz,
>
> On Thu, Jan 10, 2019 at 08:33:05PM +0100, Moritz Mühlenhoff wrote:
> > On Mon, Nov 05, 2018 at 03:13:08PM +0100, Joost van Baal-Ilić wrote:
> > >
> > > FWIW, this work:
> > >
> > > > validns
On Tue, Feb 19, 2019 at 10:00:34PM +0100, Moritz Mühlenhoff wrote:
> If a transition (even though it's marginal in size) isn't an option at this
> point
That's not for me to decide. Should we ask the RT?
--
WBR, wRAR
signature.asc
Description: PGP signature
On Thu, Dec 13, 2018 at 08:55:05PM +0100, Moritz Mühlenhoff wrote:
> On Tue, Jun 05, 2018 at 11:12:34PM +0200, Moritz Muehlenhoff wrote:
> > On Sun, Jun 26, 2016 at 12:21:20PM +0200, Kurt Roeckx wrote:
> > > OpenSSL 1.1.0 is about to released. During a rebuild of all packages
> > > using
> > >
Package: ftp.debian.org
Severity: normal
Please remove conserver. It hasn't seen an upload since 2016 and
was removed from testing since Nov 2017. It's one of the last
remaining packages blocking the removal of OpenSSL 1.0.
Cheers,
Moritz
Package: ftp.debian.org
Severity: normal
Please remove reconserver. It's dropped from testing for 1.5 years,
RC-buggy and it's blocking the removal of resiprocate (and in turn
OpenSSL 1.0).
Cheers,
Moritz
Package: ftp.debian.org
Severity: normal
Please remove registration-agent. It has only seen two upload,
was never even in testing and it blocks the removal of resiprocate
from the archive.
Cheers,
Moritz
Package: ca-certificates-java
Version: 20170929~deb9u1
Severity: important
Dear Maintainer,
After upgrading to Debian 9.8 today, the following error results
whenever I run update-ca-certificates:
--
$ sudo update-ca-certificates
Updating certificates in /etc/ssl/certs...
0 added, 0 removed;
On Sat, Feb 16, 2019 at 10:35:05PM +0500, Andrey Rahmatullin wrote:
> On Sat, Feb 16, 2019 at 12:33:08PM +, Debian Bug Tracking System wrote:
> > Processing commands for cont...@bugs.debian.org:
> >
> > > severity 776246 grave
> > Bug #776246 [librsync1] MD4 collision/preimage attacks
Control: retitle -1 screen locking does not work without lightdm
Control: severity -1 important
> In xflock4, please support xfce4-screensaver, which is a mate-screensaver
> fork targeted at Xfce4 integration.
>
> If installed, it should get the same priority as mate-screensaver (probably
> one
On Sun, 10 Sep 2017 21:41:52 +0100 Chris West wrote:
> Source: powermock
> Version: 1.6.6
> Severity: normal
> User: debian-j...@lists.debian.org
> Usertags: default-java9
>
> Powermock fails to work properly on Java 9.
Powermock still fails to build but has not been removed from testing yet
Package: src:libpdfbox-java
Version: 1:1.8.16-1
Severity: serious
Justification: Policy 4.15
The package FTBFS with the following error after a recent update to
lcdf-typetools:
[...]
make[1]: Leaving directory '/build/libpdfbox-java-1.8.16'
jh_linkjars -O--buildsystem=maven
debian/rules
On 2019-01-10 23:59:09 [+0100], Christoph Biedl wrote:
> Sebastian Andrzej Siewior wrote...
>
> > On 2019-01-10 20:31:10 [+0100], Moritz Mühlenhoff wrote:
> >
> > > Or should we rather remove netkit-ftp-ssl? There are TLS-capable ftp
> > > client
> > > alternatives in the archive still, e.g.
Control: severity -1 important
On Fri, 06 Jul 2018 13:25:28 + Santiago Vila wrote:
> Package: src:exec-maven-plugin
> Version: 1.1.1+dfsg-3
> Severity: serious
> Tags: ftbfs
Buster/Sid is not affected. Since there is also a simple workaround for
stable and oldstable (disabling the tests), I
Hi Julien,
On Tue, Feb 12, 2019 at 10:28:54AM +0100, Julien Cristau wrote:
> On 2/12/19 7:18 AM, Salvatore Bonaccorso wrote:
> > Agreed on leaving the bug open until clearer what is going on?
>
> Ack.
Right now this seem to be again stalled, at least from some locations.
Regards,
Salvatore
Package: xfce4-session
Version: 4.12.1-6
Severity: wishlist
File: /usr/bin/xflock4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
In xflock4, please support xfce4-screensaver, which is a mate-screensaver
fork targeted at Xfce4 integration.
If installed, it should get the same priority as
Hi HOlger,
On Thu, Feb 14, 2019 at 07:08:23AM +0100, Salvatore Bonaccorso wrote:
> Control: tags -1 + pending
>
> Hi Holger,
>
> On Wed, Feb 13, 2019 at 06:08:31PM +, Holger Levsen wrote:
> > package: security-tracker
> > x-debbugs-cc: debian-...@lists.debian.org
> >
> > Hi,
> >
> > this
> FYI you don't need xboxdrv to use the controller.
Yes I know, but the xpad kernel driver messes up the inputs of my controller in
games. The only workaround I found was to blacklist xpad, install and configure
xboxdrv with the systemd service and then the controller would work perfectly.
Source: uap-core
Version: 20181019-1
Severity: important
Tags: security upstream
Hi,
The following vulnerability was published for uap-core.
CVE-2018-20164[0]:
| An issue was discovered in regex.yaml (aka regexes.yaml) in UA-Parser
| UAP-Core before 0.6.0. A Regular Expression Denial of Service
1 - 100 of 219 matches
Mail list logo
