Package: mysql-utilities
Version: 1.6.1-2
Severity: serious
File: /etc/mysql/mysql-fabric-doctrine-1.4.0.zip
There is a zip file in /etc that contains a source package. At minimum
this is an FHS violation. Did you review the package before upload?
pabs@chianamo ~ $ unzip -l /etc/mysql/mysql-fabri
Processing commands for cont...@bugs.debian.org:
> severity 819546 normal
Bug #819546 [vsftpd] vsftpd no longer starts with systemd because of
listen_ipv6=NO from Bug: #803999
Severity set to 'normal' from 'grave'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
8
Control: severity -1 important
On Fri, 11 Dec 2015 18:22:55 +0100 Guido =?iso-8859-1?Q?G=FCnther?=
wrote:
> Source: srtp
> Version: 1.4.5~20130609~dfsg-1.1
> Severity: grave
> Tags: security
>
> Hi,
> from what I figured out it seems the 1.4 series is also affected by
> CVE-2015-6360. While ther
Processing control commands:
> severity -1 important
Bug #807698 [src:srtp] srtp: CVE-2015-6360: Prevent potential DoS attack due to
lack of bounds checking on RTP header CSRC count and extension header length
Severity set to 'important' from 'grave'
--
807698: http://bugs.debian.org/cgi-bin/bu
Package: gnome-maps
Version: 3.20.0-1
Followup-For: Bug #819548
Same problem for me:
(org.gnome.Maps:25763): Gjs-WARNING **: JS ERROR: TypeError:
GObject.ParamSpec.override is not a function
@resource:///org/gnome/Maps/js/mapMarker.js:44
@resource:///org/gnome/Maps/js/placeMarker.js:24
@resource
Your message dated Wed, 30 Mar 2016 22:50:48 +
with message-id
and subject line Bug#819179: fixed in quagga 1.0.20160315-1
has caused the Debian Bug report #819179,
regarding quagga: CVE-2016-2342
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Package: php-horde-webmail
Version: 5.2.12-2
Severity: grave
Tags: sid
I use only 'sid' repository. I install on 'clean' system.
When I try to complete horde webmail installation with script
'webmail-install' I see this message:
~# webmail-install
Configuring database settings
PHP Fatal error:
Your message dated Wed, 30 Mar 2016 21:52:36 +
with message-id
and subject line Bug#819531: fixed in net-snmp 5.7.3+dfsg-1.2
has caused the Debian Bug report #819531,
regarding Invalid user name 'Debian-snmp' for adduser
to be marked as done.
This means that you claim that the problem has bee
Hi,
On Wed, Mar 23, 2016 at 04:41:12PM +0100, Helmut Grohne wrote:
> The attached patch fixes the build. What I cannot tell is whether
> gtk-doc is really at fault and how many other packages this affects.
[We have discussed this on IRC, but copying here for the record.]
According to gtk-doc ups
El 30/03/16 a las 18:45, Santiago Vila escribió:
> On Wed, Mar 30, 2016 at 04:39:17PM +0200, Santiago Ruano Rincón wrote:
...
> I'm not familiar enough with this package to tell, but if that does
> what you want, yes, I suppose it would be better.
>
> Beware, however, that in a future there might
On Wed, Mar 30, 2016 at 01:37:58PM +0200, Steinar H. Gunderson wrote:
> I'll have a look at it tonight and see what I can do. Thanks for alerting me
> of it.
I made a new upload, and tested that it installs (including upgrades from the
version in testing).
/* Steinar */
--
Homepage: https://www.
Source: debian-installer-netboot-images
Version: 20120712
Severity: serious
Justification: silently ignores failures, creating broken packages
Hi,
Whilst preparing the dini uploads for the upcoming point releases, on
debdiffing the binary packages against the previous versions I noticed
that one
Processing control commands:
> severity -1 important
Bug #819550 [linux-image-4.4.0-0.bpo.1-rt-amd64]
linux-image-4.4.0-0.bpo.1-rt-amd64: boot stall while trying 4.4 rt amd64 kernel
Severity set to 'important' from 'critical'
> tag -1 moreinfo
Bug #819550 [linux-image-4.4.0-0.bpo.1-rt-amd64]
lin
Control: severity -1 important
Control: tag -1 moreinfo
On Wed, 2016-03-30 at 12:49 +0200, gregory bahde wrote:
> Package: linux-image-4.4.0-0.bpo.1-rt-amd64
> Severity: critical
> Justification: breaks the whole system
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these quest
Your message dated Wed, 30 Mar 2016 18:19:04 +
with message-id
and subject line Bug#819493: fixed in debian-security-support 2016.03.30+nmu1
has caused the Debian Bug report #819493,
regarding debian-security-support: FTBFS on jessie: attemps to install
nonexistent security-support-ended.deb8
El 29/03/16 a las 20:39, Moritz Mühlenhoff escribió:
> On Tue, Mar 29, 2016 at 05:13:51PM +0200, Santiago Ruano Rincón wrote:
...
> Feel free to make code changes in collab-maint along with an upload
> to unstable.
>
Thanks! Pushed and uploaded,
Santiago
signature.asc
Description: PGP signatu
On Wed, Mar 30, 2016 at 04:39:17PM +0200, Santiago Ruano Rincón wrote:
> What about this?
>
> diff --git a/debian/rules b/debian/rules
> index 10e034a..3fefda0 100755
> --- a/debian/rules
> +++ b/debian/rules
> @@ -1,6 +1,11 @@
> #!/usr/bin/make -f
>
> -DEBIAN_VERSION ?= $(shell LANG=C dpkg -l
Processing commands for cont...@bugs.debian.org:
> tags 812668 fixed-upstream
Bug #812668 [mailfilter] mailfilter: FTBFS - error: no match for 'operator='
Added tag(s) fixed-upstream.
>
End of message, stopping processing here.
Please contact me if you need assistance.
--
812668: http://bugs.deb
Your message dated Wed, 30 Mar 2016 17:19:38 +
with message-id
and subject line Bug#819115: fixed in cowsay 3.03+dfsg1-15
has caused the Debian Bug report #819115,
regarding cowsay: missing dependency on libtext-charwidth-perl
to be marked as done.
This means that you claim that the problem h
Processing commands for cont...@bugs.debian.org:
> retitle 819549 unable to read installation media conf files
Bug #819549 [src:yaboot] What ever happened to yaboot?
Bug #817133 [src:yaboot] yaboot: Invalid device
Changed Bug title to 'unable to read installation media conf files' from 'What
ever
El 29/03/16 a las 21:55, Santiago Vila escribió:
> On Tue, Mar 29, 2016 at 05:13:51PM +0200, Santiago Ruano Rincón wrote:
> > #!/usr/bin/make -f
> >
> > -DEBIAN_VERSION ?= $(shell LANG=C dpkg -l base-files | awk
> > '($$1=="ii"){print $$3}' | cut -d. -f1)
> > +DEBIAN_VERSION ?= $(shell LANG=C d
El 11/10/15 a las 23:29, Dominic Hargreaves escribió:
> On Sun, Oct 11, 2015 at 05:45:05PM +0100, Adam D. Barratt wrote:
> > On Sun, 2015-10-11 at 16:50 +0100, Dominic Hargreaves wrote:
> > > On Sat, Feb 14, 2015 at 01:36:05AM +, Debian Bug Tracking System
> > > wrote:
> > >
> > > > ndisc6 (
On Wed, Mar 30, 2016 at 07:48:03PM +0900, Hideki Yamane wrote:
> Already uploaded :-(
Yes, something went wrong with the delay, like I said. すみません :-/
> git tree is WIP and has bug I thought, so it's bad for me upload...
> I don't know why you've uploaded it based on git, it should be minimize
On Tue, Mar 29, 2016 at 21:34:20 +0200, Salvatore Bonaccorso wrote:
> the following vulnerabilities were published for mercurial.
>
> CVE-2016-3068[0]:
> arbitrary code execution with Git subrepos
>
> CVE-2016-3069[1]:
> arbitrary code execution when converting Git repos
>
> CVE-2016-3630[2]:
>
Processing commands for cont...@bugs.debian.org:
> close 819504 3.7.3-1
Bug #819504 [src:mercurial] mercurial: CVE-2016-3068 CVE-2016-3069 CVE-2016-3630
Marked as fixed in versions mercurial/3.7.3-1.
Bug #819504 [src:mercurial] mercurial: CVE-2016-3068 CVE-2016-3069 CVE-2016-3630
Marked Bug as don
On Tue, 29 Mar 2016 10:41:06 +0200
"Steinar H. Gunderson" wrote:
> I intend to NMU for this bug and a few other bugs that I'd really like to see
> fixed before stretch. I've uploaded to DELAYED/7-day; let me know if you'd
> like anything changed. I've attached my own git diff on top of Steven's di
Processing commands for cont...@bugs.debian.org:
> # seems like grave to me
> severity 817133 grave
Bug #817133 [src:yaboot] yaboot: Invalid device
Bug #819549 [src:yaboot] What ever happened to yaboot?
Severity set to 'grave' from 'normal'
Severity set to 'grave' from 'normal'
>
End of message, s
Processing commands for cont...@bugs.debian.org:
> reassign 817133 src:yaboot
Bug #817133 [yaboot] yaboot: Invalid device
Bug reassigned from package 'yaboot' to 'src:yaboot'.
No longer marked as found in versions yaboot/1.3.17-1.
Ignoring request to alter fixed versions of bug #817133 to the same
Package: linux-image-4.4.0-0.bpo.1-rt-amd64
Severity: critical
Justification: breaks the whole system
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
installing rt 4.4
* What exactly did you do (or not do) that
Processing commands for cont...@bugs.debian.org:
> reopen 817133
Bug #817133 {Done: Barry Warsaw } [yaboot] yaboot: Invalid
device
Bug reopened
Ignoring request to alter fixed versions of bug #817133 to the same values
previously set
> forcemerge 817133 819549
Bug #817133 [yaboot] yaboot: Invali
Processing commands for cont...@bugs.debian.org:
> submitter 819549 Risto Suominen
Bug #819549 [src:yaboot] What ever happened to yaboot?
Changed Bug submitter to 'Risto Suominen ' from
'Mathieu Malaterre '.
>
End of message, stopping processing here.
Please contact me if you need assistance.
-
Processing commands for cont...@bugs.debian.org:
> severity 819548 grave
Bug #819548 [gnome-maps] gnome-maps fails to start
Severity set to 'grave' from 'normal'
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
819548: http://bugs.debian.org/cgi-bin/bugreport.cgi?b
Package: snmpd
Version: 5.7.3+dfsg-1.1
Followup-For: Bug #819531
Confirmed.
WHile I don't have a strong opinion about the "Debian-" prefix (vs a leading
underscore), in any case the postinst script needs to call adduser with the
"--force-badname" (as is done e.g. by exim4-config)
-- System Info
Package: src:yaboot
Version: 1.3.17-1
Severity: grave
Looks like yaboot does not find its conf file any more.
I'm trying to install (CD) Debian on a PowerMac G5 (7,3). Jessie
(yaboot 1.3.16) works.
Stretch (yaboot 1.3.17) does not. It complains:
cd:-1,\install\yaboot.conf: Unable to open file,
2016-03-28 14:44 GMT+02:00 Adam D. Barratt :
> On Mon, 2016-03-28 at 14:39 +0200, Mathieu Parent (Debian) wrote:
>> 2016-03-26 18:35 GMT+01:00 Adam D. Barratt :
>> > On Sat, 2016-03-26 at 17:14 +0100, Mathieu Parent wrote:
>> >> tags 816205 + jessie-ignore
>> >> thanks
>> >
>> > Was that discussed
Package: vsftpd
Version: 3.0.3-3
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Bug #803999 sets listen_ipv6=NO as stated in the manpage. In doing so, it
breaks the systemd unit vsftpd which tries to do the following :
ExecStart=/usr/sbin/vsftpd /etc/vsftpd.conf
Runni
Processing commands for cont...@bugs.debian.org:
> severity 795211 grave
Bug #795211 [yaboot-installer] Yaboot in Jessie, following Jessie OS
installation, fails to boot Mac OS X
Severity set to 'grave' from 'normal'
> user debian-powe...@lists.debian.org
Setting user to debian-powe...@lists.debi
Package: python3-winrm
Version: 0.0.3-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After installing python3-winrm and trying to follow the getting started example
on https://pypi.python.org/pypi/pywinrm
This fails:
edb@lapelidb:/tmp$ cat test.py
#!/usr/bin/env pyt
##SELECTION_END##It seems that the problem is resolved with the last
version of gnome et gnome bluetooth ?
Package: valabind
Version: 0.9.2-2
Severity: serious
Your package needs to be updated to build against the new vala
0.32.
Cheers,
Emilio
Package: gnome-builder
Version: 3.18.1-2
Severity: serious
Your package needs to be updated to build against the new vala
0.32.
Cheers,
Emilio
Source: valadoc
Version: 0.23.2~git20150422-3
Severity: serious
Your package needs to be updated to build against the new vala
0.32.
Cheers,
Emilio
Control: severity -1 serious
(I don't think this deserves to be grave TBH.)
Hi!
On Wed, 2016-03-30 at 14:38:27 +0900, ISHIKAWA Mutsumi wrote:
> Package: snmpd
> Version: 5.7.3+dfsg-1.1
> Severity: grave
> Setting up snmpd (5.7.3+dfsg-1.1) ...
> adduser: Please enter a username matching the regu
Processing control commands:
> severity -1 serious
Bug #819531 [snmpd] Invalid user name 'Debian-snmp' for adduser
Severity set to 'serious' from 'grave'
--
819531: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=819531
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Your message dated Wed, 30 Mar 2016 07:49:18 +
with message-id
and subject line Bug#815607: fixed in namazu2 2.0.21-11
has caused the Debian Bug report #815607,
regarding namazu2: Removal dh_undocumented debhelper command
to be marked as done.
This means that you claim that the problem has be
45 matches
Mail list logo