Processing control commands:
> forwarded -1 Ricardo Signes
Bug #864800 [src:libmail-deliverystatus-bounceparser-perl]
Mail::DeliveryStatus::BounceParser contains a live virus and some real
spam/phishing mails
Set Bug forwarded-to-address to 'Ricardo Signes '.
>
Source: libmail-deliverystatus-bounceparser-perl
Version: 1.531-1
Severity: serious
X-Debbugs-CC: Ricardo Signes
Control: forwarded -1 Ricardo Signes
Control: found -1 1.536-1
Control: found -1 1.542-1
User: debian-ad...@lists.debian.org
Usertags: needed-by-DSA-Team
Package: grafana
Version: 2.6.0+dfsg-3
Severity: grave
Hi,
After making a default installation of Grafana, I went to localhost:3000.
I got redirected to http://localhost:3000/login, which is black and otherwise
entirely blank (Chrome 59). The developer console says:
Uncaught TypeError: Cannot
Hi IOhannes,
On Wed, Jun 14, 2017 at 10:06:27AM +0200, IOhannes m zmölnig wrote:
> thanks a lot for your bug-report.
>
> please do not forget to also file bugs against the remaining packages
> that still use ConvertUTF.c:
> https://lintian.debian.org/tags/license-problem-convert-utf-code.html
Some thoughts about the bug report (sorry for the borked first version
of this mail):
1. There is already code in openldap that maps dn's to paths in the
cn=config backend when it writes the config tree to the file system in
/etc/ldap/slapd.d. Maybe that code or at least its escaping logic can
be
Processing commands for cont...@bugs.debian.org:
> severity 761658 wishlist
Bug #761658 {Done: m...@linux.it (Marco d'Itri)} [systemd] Please do not
default to using Google nameservers
Severity set to 'wishlist' from 'serious'
> thanks
Stopping processing here.
Please contact me if you need
Processing control commands:
> severity 863720 serious
Bug #863720 [src:aiccu] aiccu: SixXS will shutdown on 2017-06-06
Severity set to 'serious' from 'important'
> found 863720 20070115-14
Bug #863720 [src:aiccu] aiccu: SixXS will shutdown on 2017-06-06
Marked as found in versions
Hi guys,
please allow me to add some thoughts to this bug report:
1. Is there any way to re-use the way dn's are mapped to paths by the
cn=config backend for this purpose?
2017-06-14 12:59 GMT+02:00 Thorsten Glaser :
> On Tue, 13 Jun 2017, Ryan Tandy wrote:
>
>>> Hi
Hi
Am 14.06.2017 um 19:49 schrieb benaryorg:
> As this is about the default nameservers to be used when there is
> nothing else configured, how would I disable DNS resolution then?
First of all, systemd-resolved is not used and enabled by default.
If you actually do use systemd-resolved,
As this is about the default nameservers to be used when there is
nothing else configured, how would I disable DNS resolution then?
Because I see that this is a technical issue for which there is no
solution mentioned in this bugreport yet.
At least for settling this part of the issue can you
Control: severity -1 important
Version: 1.2.12
On Wed, Jun 14, 2017 at 04:56:19PM +0200, Andreas Beckmann wrote:
> Package: apt
> Version: 1.0.9.8.4
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> during a test with piuparts I noticed the [non-free]
>
Processing control commands:
> severity -1 important
Bug #864775 [apt] apt-get: computes wrong upgrade path for chained Pre-Depends
on i386
Severity set to 'important' from 'serious'
--
864775: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864775
Debian Bug Tracking System
Contact
Processing commands for cont...@bugs.debian.org:
> affects 864775 + xserver-xorg-video-nvidia
Bug #864775 [apt] apt-get: computes wrong upgrade path for chained Pre-Depends
on i386
Added indication that 864775 affects xserver-xorg-video-nvidia
> thanks
Stopping processing here.
Please contact
Hi, and sorry for the late reply.
1) OK
2) I use it on both stable, testing and unstable, but I'm OK with not
having this available in testing or stable: in fact I think it is better
not to have the buggy version available at all than to have it and then
suffer potential data loss.
3) As you can
Processing commands for cont...@bugs.debian.org:
> notfound 864746 1.1.1+20160115
Bug #864746 [src:radicale] radicale: Radicale 1.1.3 required to migrate data to
Radicale 2
The source 'radicale' and version '1.1.1+20160115' do not appear to match any
binary packages
No longer marked as found in
Processing control commands:
> tag -1 patch
Bug #864316 [libapache2-mod-perl2] libapache2-mod-perl: FTBFS in jessie due to
apache2 changes
Added tag(s) patch.
--
864316: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=864316
Debian Bug Tracking System
Contact ow...@bugs.debian.org with
Control: tag -1 patch
On Tue, Jun 06, 2017 at 11:06:05PM +0300, Niko Tyni wrote:
> Package: libapache2-mod-perl2
> Version: 2.0.9~1624218-2+deb8u1
> Severity: serious
>
> As per
>
>
>
Processing control commands:
> tags -1 help gift
Unknown tag/s: gift.
Recognized are: patch wontfix moreinfo unreproducible fixed potato woody sid
help security upstream pending sarge sarge-ignore experimental d-i confirmed
ipv6 lfs fixed-in-experimental fixed-upstream l10n newcomer etch
Processing commands for cont...@bugs.debian.org:
> notfound 864746 1.1.1+2016011
Bug #864746 [src:radicale] radicale: Radicale 1.1.3 required to migrate data to
Radicale 2
The source 'radicale' and version '1.1.1+2016011' do not appear to match any
binary packages
Ignoring request to alter
Control: tags -1 help gift
On Sun, May 21, 2017 at 7:11 PM, Felipe Sateler wrote:
> On Sun, May 21, 2017 at 10:36 AM, Mattia Rizzolo
> wrote:
> > Source: pulseaudio
> > Version: 10.0-1
> > Severity: serious
> >
> > the copyright file has this paragraph:
Processing commands for cont...@bugs.debian.org:
> severity 864768 serious
Bug #864768 [libquartz2-java] libquartz2-java: Disable the update checker
Severity set to 'serious' from 'important'
> tags 864768 + security
Bug #864768 [libquartz2-java] libquartz2-java: Disable the update checker
Added
Processing commands for cont...@bugs.debian.org:
> severity 864769 serious
Bug #864769 [src:libquartz-java] libquartz-java: Disable the update checker
Severity set to 'serious' from 'important'
> tags 864769 + security
Bug #864769 [src:libquartz-java] libquartz-java: Disable the update checker
Processing commands for cont...@bugs.debian.org:
> forwarded 840516 https://github.com/graphite-project/graphite-web/pull/1960
Bug #840516 [graphite-web] doesn't work with django 1.10
Set Bug forwarded-to-address to
'https://github.com/graphite-project/graphite-web/pull/1960'.
> thanks
Stopping
On Tue, 13 Jun 2017, Ryan Tandy wrote:
>> Hi Thorsten, thanks for reporting this.
You’re welcome.
>> (But I'm curious: how did you wind up with the escaped form on wheezy? For
>> me, slapd via ldapmodify and slapadd both write it in base64.)
I’ve first set up the test server, then, in order
Jonas Smedegaard wrote:
> Exactly: Packages poorly _maintained_ should be removed. E.g. npm!
> My point in previous post was that focusing only on the workload for
> _initial_ packaging masks the actual real workload, which is being
> discussed here!
> - Jonas
I agree. If it is too
❦ 8 mai 2017 10:38 GMT, Stephane Bortzmeyer :
> There are several reasons why graphite-web does not work with Django
> 1.10 (the current version in sid). One of them is that it uses the
> "patterns" variable:
This seems to have been fixed upstream (but unreleased):
On 2017-06-13 18:26, Dmitry Shachnev wrote:
> Source: assimp
> Version: 3.3.1~dfsg-4
> Severity: serious
>
> Dear maintainer,
>
> assimp seems to bundle ConvertUTF library which is under a non-DFSG license.
thanks a lot for your bug-report.
pease do not forget to also file bugs against the
Quoting Timo Boettcher (2017-06-14 00:59:50)
> according to the radicale 1 to 2 migration guide
> http://radicale.org/1to2/
>
> "Calendars and address books are stored in a different way between
> 1.x.x and 2.0.x versions. Launching 2.0.x without migrating your
> collections first will
Your message dated Wed, 14 Jun 2017 06:43:40 +
with message-id
and subject line Bug#864744: fixed in texlive-extra 2017.20170614-1
has caused the Debian Bug report #864744,
regarding texlive-formats-extra: fails to install: fmtutil failed
to be marked as
Processing commands for cont...@bugs.debian.org:
> severity 767465 normal
Bug #767465 [installation-reports] Installed Debian Jessie fails to recognize
USB flash drive upon reboot
Severity set to 'normal' from 'serious'
>
End of message, stopping processing here.
Please contact me if you need
Your message dated Wed, 14 Jun 2017 06:20:18 +
with message-id
and subject line Bug#864750: fixed in texlive-base 2017.20170614-1
has caused the Debian Bug report #864750,
regarding texlive-base: dvipdfmx.def is broken
to be marked as done.
This means
31 matches
Mail list logo