On Sat, 2018-01-06 at 18:04 +, LJ wrote:
> > Looking at the lspci output you have a Xeon E3 from the 1200 series, but
> > you
> > could provide your full /proc/cpuinfo?
>
> Hi, sure...
Thanks
>
> root@sam:~# cat /proc/cpuinfo
> processor : 0
> vendor_id : GenuineIntel
> cpu
On Sat, 2018-01-06 at 15:46 +, LJ wrote:
> Booting in recovery mode the final lines are:
>
> [ 0.058600] x86: Booting SMP configuration:
> [ 0.058632] node #0, CPUs: :1
>
> The cursor is flashing after the "#1" and the system hangs at that point.
>
> I have video and a
control: reassign -1 xen-hypervisor-4.8-amd64
On Sat, 2018-01-06 at 15:23 +0100, Valentin Vidic wrote:
> On Sat, Jan 06, 2018 at 03:08:26PM +0100, Yves-Alexis Perez wrote:
> > According to that link, the fix seems to be configuration rather than
> > code.
> > Does this
On Fri, 2017-11-17 at 07:39 +0100, Valentin Vidic wrote:
> Hi,
>
> The problem seems to be caused by the new multi-queue xen blk driver
> and I was advised by the Xen devs to increase the gnttab_max_frames=256
> parameter for the hypervisor. This has solved the blocking issue
> for me and it has
On Fri, 2018-01-05 at 17:08 +0100, Robert Senger wrote:
> Package: linux-source-4.9
> Version: 4.9.65-3+deb9u2
> Severity: serious
> Justification: fails to build from source (but built successfully in the past)
>
> Dear Maintainer,
>
> compilation of Kernel sources 4.9.65-3+deb9u2 fails:
>
>
On Sun, 26 Nov 2017 11:02:04 +0100 Salvatore Bonaccorso
wrote:
> Hi Martin,
>
> On Wed, Nov 22, 2017 at 02:04:48PM +0100, Martin Scharm wrote:
> > Package: src:linux
> > Version: 4.12.0-1
> > Severity: serious
> >
> > --- Please enter the report below this line. ---
> >
> >
control: severity -1 important
control: tag -1 unreproducible moreinfo
On Tue, 2017-12-19 at 20:58 +0100, Lorenzo Ancora wrote:
> Dear Maintainer,
> shredding a file in a mounted USB key causes `Thunar 1.6.11 (Xfce 4.12)` to
> block permanently.
> The window with the key won't close and Thunar
control: severity -1 important
On Tue, 2017-12-19 at 23:42 +0100, Andreas Beckmann wrote:
> > I just tried a build (in pbuilder/amd64) and it worked just fine. Can you
> > be
> > more specific about your test? Is it an arch-indep build for example?
>
> This was a regular (arch+indep) build with
On Fri, 15 Dec 2017 14:01:55 +0100 "W. Martin Borgert"
wrote:
> Dear Bjoern, dear Dimitris,
>
> thank you for your bug reports! I ask you for a favour:
>
> Could you please try Gajim from Debian experimental?
> The plugins for the new Gajim are in experimental, too,
> if you
control: tag -1 moreinfo unreproducible
On Tue, 2017-12-12 at 19:34 +0100, Andreas Beckmann wrote:
> Hi,
>
> libxfce4ui/experimental recently started to FTBFS, probably due to
> debhelper getting more strict w.r.t. missing files:
>
>debian/rules override_dh_install
> make[1]: Entering
On Fri, 2017-10-27 at 05:58 -0400, Jordan Glover wrote:
> linux-grsec-base[1] is missing from stable-backports and I don't see it
> being prepared for upload there[2]. Other than that this bug can be closed.
> Thanks for your work.
>
> [1] https://tracker.debian.org/pkg/linux-grsec-base
> [2]
On Sun, 2017-10-22 at 17:22 +0200, Yves-Alexis Perez wrote:
> Can you prepare updates for sid, stretch and jessie (please coordinate with
> security team at t...@security.debian.org for the latter two)? Please add
> CVE numbers to the changelog so we can track them easily.
By the w
Source: irssi
Severity: grave
Tags: security
Justification: user security hole
Hi,
irssi 1.0.5 has been released, fixing multiple vulnerabilities
(a) When installing themes with unterminated colour formatting
sequences, Irssi may access data beyond the end of the
string. (CWE-126) Found
On Wed, 2017-10-04 at 18:29 -0400, Jordan Glover wrote:
> I saw that new version landed in unstable. Is it possible to have it in
> stable-backports?
Yes, that's my intention, although I intend to let it stay in unstable for a
bit before doing the stable-backports upload (and
On Fri, 2017-08-04 at 10:55 +0200, Yves-Alexis Perez wrote:
> Not sure if the problem lies in libxfcegui4 or in the toolchain but I'm
> unlikely to find a fix right now.
I take that back. It seems that using autotools-dev addon to update
config.{guess,sub}, fixes the FTBFS. Since they're
On Fri, 2017-08-04 at 00:01 +0200, Helmut Grohne wrote:
> > checking whether environ is declared... yes
> > ./configure: line 13746: syntax error near unexpected token `am'
> > ./configure: line 13746: `XDT_I18N(am ar ast be bn_IN ca cs cy da de dz el
> > en_GB eo es et eu fa fi fr gl gu he hr hu
control: severity -1 important
On Sun, 2017-07-30 at 22:54 +, Daniel Shahaf wrote:
> Package: light-locker
> Version: 1.7.0-3
> Severity: serious
> Justification: breaks unrelated software
>
> Dear Maintainer,
>
> On my system, 'light-locker-command --lock' returns 0 without doing
>
On Mon, 2017-07-17 at 04:13 +0300, Adrian Bunk wrote:
> Package: libgarcon-1-0-dev
> Version: 0.6.1-1
> Severity: serious
>
> Package: libgarcon-1-0-dev
> Version: 0.6.1-1
> Depends: libgarcon-1-dev
>
> Package: libgarcon-1-dev
> Version: 0.6.1-1
> Breaks: libgarcon-1-0-dev
Hi
could you
and
> http://www.synacktiv.ninja/ressources/Knot_DNS_TSIG_Signature_Forgery.pdf
> and filling a bug in BTS to have a reference, afaik there is no CVE
> yet assigned.
>
> [16:19] < KGB-1> Yves-Alexis Perez 52846 /data/CVE/list add temporary entry
> for knot
> [16:21
On Tue, 2017-07-04 at 10:22 -0400, Jordan Glover wrote:
> Thank you for the reply. It's great that you consider packaging one of the
> forward ports.
>
> Just one more question - Is it possible for you to update current package to
> latest official version (from 4.9.18 to 4.9.24)? That would be
On Tue, 2017-07-04 at 08:25 -0400, Jordan Glover wrote:
> I wanted to ask you about the future of linux-grsec in debian. The package
> wasn't updated for some time and it's now at 4.9.18 version while last
> official grsecurity version is 4.9.24. Additionally there are few forward
> ports of
On Fri, 2017-05-12 at 11:53 -0500, Nathaniel Beaver wrote:
> Package: xfce4-weather-plugin
> Version: 0.8.3-2
> Severity: grave
> Justification: renders package unusable
>
> Dear Maintainer,
>
> The met.no Web API is deprecated:
>
>
On Tue, 2017-02-14 at 15:32 +0900, Hideki Yamane wrote:
> > On Mon, 29 Aug 2016 16:15:34 +0200 Yves-Alexis Perez <cor...@debian.org>
> > wrote:
> > I follow src:linux package on this, so I'll do the switch when they do it
> > (and
> > will close thi
On Fri, 2017-02-03 at 12:34 -0500, Daniel Kahn Gillmor wrote:
>
> I'm suprised to see that strongswan-charon is the package providing
> ike-server, if stronswan-starter is the package that contains the system
> integration.
src:strongswan actually provides multiple IKE daemon (charon) in
On Fri, 2017-01-20 at 08:12 -0500, Scott Kitterman wrote:
> Package: linux-grsec
> Version: 4.8.15-2+grsec201701031913+1
> Severity: grave
> Justification: renders package unusable
>
> linux-compiler-gcc-5-x86 and linux-headers-4.8.0-2-common-rt are NBS and to
> be
> removed shortly. Once that
On Sun, 2016-12-18 at 15:51 +0100, Hilko Bengen wrote:
> Yes, I have done successful builds on amd64, mipsel, mips64el, armhf,
> arm64.
> Please do the upload yourself.
>
> Since the Qt symbols that somehow got into the library are not really
> part of the ABI, you may want to change them like
On Sun, 2016-12-18 at 13:28 +0100, Yves-Alexis Perez wrote:
> On Fri, 2016-12-16 at 08:05 +0100, Hilko Bengen wrote:
> > here is a set of patches that I intend to NMU to DELAYED/5 later. I have
> > changed the .symbols file to use C++ name demangling and added some
> > optio
control: severity -1 important
On Tue, 2016-09-20 at 14:10 +0200, Daniel Lange wrote:
> Control: tags -1 unreproducible
>
> I've tried to reproduce the issue for 48h on three AMD64 systems I've
> happened to have around here temporarily with fresh Debian testing
> installs. Got to use the
On Sun, 2016-12-18 at 12:38 +, Holger Levsen wrote:
> Even incomplete, I consider having it in to be better than having the
> totally wrong jessie artwork in stretch for these two reasons:
I understand that, it's just not my opinion (as expressed earlier).
I won't oppose an upload, I was
On Fri, 2016-12-16 at 08:05 +0100, Hilko Bengen wrote:
> here is a set of patches that I intend to NMU to DELAYED/5 later. I have
> changed the .symbols file to use C++ name demangling and added some
> optional symbols that seem to come directly from the Qt library.
>
> I have also taken the
On Sun, 2016-12-18 at 12:17 +, Holger Levsen wrote:
> justification: testing should always be in a releasable state, and even more
> so now the freeze is getting closer…
Well, that won't really change with an upload right now, depending on what you
consider “releasable state“:
- the current
On Sun, 2016-12-18 at 12:33 +0100, Holger Levsen wrote:
> what's stalling the uploads? (either to experimental or unstable even…)
See <1481014791.20278.9.ca...@debian.org> but nothing is really preventing an
upload, just time.
>
> can I help?
I should be able to push an upload to experimental
control: severity -1 important
control; tag -1 moreinfo
On Tue, 2016-12-13 at 11:18 +0100, Network Services wrote:
> * What led up to the situation? : service hp-health won't start anymore.
Did it ever start on a grsec kernel?
> * What exactly did you do (or not do) that was effective (or
control: severity -1 important
control: tag -1 moreinfo
On Mon, 2016-11-28 at 10:05 +0100, Yves-Alexis Perez wrote:
> On Sun, 2016-11-27 at 23:13 +0100, Santiago Vila wrote:
> > The failure happens randomly. Sometimes it fails, sometimes it does not.
>
> Check exactly where the
On Wed, 2016-11-30 at 21:28 +0100, Martin Steigerwald wrote:
>
> As Michael downgraded the bug, there is apt-pinning for keeping the version
> from testing installed:
In case you missed, the downgrade was because of the merge, Michael actually
raised the severity to grave again.
Regards,
--
On Sun, 2016-11-27 at 23:13 +0100, Santiago Vila wrote:
> The failure happens randomly. Sometimes it fails, sometimes it does not.
Check exactly where the testsuite fails, it might be lack of entropy. I'd
rather not disable the testsuite altogether, we already limit it to few
architectures to
control: tag -1 help
On Sat, 2016-11-19 at 15:15 +0100, Yves-Alexis Perez wrote:
> On Mon, 2016-10-31 at 14:00 +0100, Yves-Alexis Perez wrote:
> > On Mon, 2016-10-31 at 10:34 +, Radovan Birdic wrote:
> > > The problem is in liblightdm-qt-3-0.symbols where these symbols
On Mon, 2016-10-31 at 14:00 +0100, Yves-Alexis Perez wrote:
> On Mon, 2016-10-31 at 10:34 +, Radovan Birdic wrote:
> > The problem is in liblightdm-qt-3-0.symbols where these symbols are
> > missing.
> >
> > I have created and attached a patch that adds missing
On Wed, 2016-11-09 at 16:45 +0100, Eric Valette wrote:
> On 11/09/2016 04:16 PM, Yves-Alexis Perez wrote:
> > On Wed, 2016-11-09 at 15:52 +0100, Eric Valette wrote:
> > Can you add set -x to the postinst file?
>
> I did a "sh -x ...dektop-base.postinst configure"
On Wed, 2016-11-09 at 15:52 +0100, Eric Valette wrote:
> On 11/09/2016 03:39 PM, Yves-Alexis Perez wrote:
> > control: tag -1 moreinfo
> >
> > On Wed, 2016-11-09 at 09:06 +0100, Eric Valette wrote:
> > >
> > > I have installed this version on two com
control: tag -1 moreinfo
On Wed, 2016-11-09 at 09:06 +0100, Eric Valette wrote:
>
> I have installed this version on two computers and in both cases it fails to
> install. It runs the postinstall command correctly (as far as I tested by
> executing scripts manually) but still fails. I have no
On Fri, 2016-10-07 at 00:32 +0300, Adrian Bunk wrote:
> Control: tags 837007 +patch
>
> A fix for the xfce4-radio-plugin FTBFS is attached.
Thanks. To be honest I was actually thinking on letting the plugin die (nobody
really takes care of it upstream). The patch is simple enough (although it
On Sat, 2016-10-01 at 16:17 +0200, Lucas Nussbaum wrote:
> Relevant part (hopefully):
> > make[6]: *** [check-recursive] Error 1
> > make[6]: Leaving directory '/<>/src/libstrongswan'
> > Makefile:2131: recipe for target 'check' failed
> > make[5]: *** [check] Error 2
> > make[5]: Leaving
close 839190 4.1+dfsg-1+deb8u11
thanks
517f65760c1d1a9b9aacc92fdbb382afdb074ba1
Author: Yves-Alexis Perez <cor...@debian.org>
Date: Fri Sep 30 09:46:15 2016 +0200
Fix regression in previous upload
* Non-maintainer upload by the Security Team.
* debian/patches/CVE-2016-6635.patch:
- don't duplicate wp_encode_json() which has alread
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On Fri, Sep 30, 2016 at 04:50:03PM +0200, Stefano Zacchiroli wrote:
> On Fri, Sep 30, 2016 at 10:20:30AM +0200, Yves-Alexis Perez wrote:
> > thanks for the report, we're aware of the regression. Can you try the
> > attached
&g
On ven., 2016-09-30 at 10:26 +0200, Laurentiu Pancescu wrote:
>
> Your patch seems to work. The Ansible playbook completes successfully
> (it's pretty extensive, from the database creation to importing old
> posts and media, configuring users and several plugins programmatically
> with
control: tag -1 patch pending
Hi,
thanks for the report, we're aware of the regression. Can you try the attached
patch against functions.php and report back, as soon as possible?
Regards,
--
Yves-Alexis Perez - Debian Security
--- /usr/share/wordpress/wp-includes/functions.php.old 2016-09-30
On Mon, 2016-07-11 at 06:46 -0700, Vincent Lefevre wrote:
> On 2016-07-11 13:03:55 +0200, Yves-Alexis Perez wrote:
> > So it seems stdin is closed for the second login. Could it break dbus-
> > launch/dbus-daemon somehow?
>
> In general, closing stdin is a bad idea,
[adding Robert and the launchpad bug to CC]
On Mon, 2016-07-11 at 13:03 +0200, Yves-Alexis Perez wrote:
> On Mon, 2016-07-11 at 11:46 +0200, Yves-Alexis Perez wrote:
> > > I wonder whether there are other reasons why epoll_ctl can report
> > > EINVAL?
> >
> > T
On Mon, 2016-07-11 at 11:46 +0200, Yves-Alexis Perez wrote:
> > I wonder whether there are other reasons why epoll_ctl can report EINVAL?
>
> The syscall source code is at http://lxr.free-electrons.com/source/fs/eventp
> ol
> l.c#L1849 and it seems EINVAL is used as a
On Mon, 2016-07-11 at 10:38 +0100, Simon McVittie wrote:
> On Mon, 11 Jul 2016 at 11:07:07 +0200, Yves-Alexis Perez wrote:
> > > Misc error when trying to watch fd 4: Invalid argument
> > > Unable to add reload watch to main loopthis watch should have been
> > > inv
On Thu, 2016-07-07 at 21:16 +0200, Yves-Alexis Perez wrote:
> >
> > Or you could try running dbus-launch with DBUS_DEBUG_OUTPUT=1 in the
> > environment, which makes it not close its dbus-daemon's stderr.
>
> I get this:
>
> Misc error when trying to watch fd 4: In
On Fri, 2016-07-08 at 17:02 +0200, Stephane Bortzmeyer wrote:
> Running stretch, I confirm that the problem still exists today (after
> a dist-upgrade).
>
> Installing dbus-user-session AND REBOOTING cured it.
Yeah, we're still investigating the problem, but right now I don't have much
clues
On Thu, 2016-07-07 at 17:55 +0100, Simon McVittie wrote:
> So if you use "xprop -id 4194305" (in this case) to inspect that window,
> you should hopefully find a consistent address and pid attached to it.
From .xsession-errors:
+ eval
On Mon, 2016-07-04 at 17:48 +0100, Simon McVittie wrote:
>
> These indicate that something in your session, whose controlling terminal
> is /dev/pts/0 (?!), used D-Bus and started a dbus-daemon as a side-effect
> ("autolaunching", pid 30347/30348); and in addition, dbus-launch was run
> during
On jeu., 2016-07-07 at 10:06 +0200, Santiago Vila wrote:
> You have to build the package in a chroot with only the build-essential
> packages installed (and the build-dependencies, of course).
>
> Don't install systemd in the chroot, it's not build-essential.
The builds are done in a standard
control: tag -1 unreproducible moreinfo
On mer., 2016-06-29 at 11:44 +0200, Yves-Alexis Perez wrote:
> On mer., 2016-06-29 at 09:00 +, Santiago Vila wrote:
> > This package currently fails to build in stretch:
>
> Did you try a manual build? It builds fine in sid, an
On mer., 2016-06-29 at 09:00 +, Santiago Vila wrote:
> This package currently fails to build in stretch:
Did you try a manual build? It builds fine in sid, and the log shows:
checking for systemd system unit directory... configure: error: not found (try
--with-systemdsystemunitdir)
which
On mar., 2016-06-14 at 13:58 -0500, Kyle Bentley wrote:
>
> It will happen, or it has for the last few days/2 weeks. All that is
> variable is
> the amount of time required. I would be happy to give more information if
> you'll
> kindly tell me how.
Try to identify what update broke
On lun., 2016-05-16 at 12:44 +0200, Santiago Vila wrote:
> Package: src:strongswan
> Version: 5.4.0-1
> Severity: serious
>
> Dear maintainer:
>
> This package currently fails to build from source in stretch:
>
>
> In file
On jeu., 2016-05-12 at 17:15 +0200, Andreas Henriksson wrote:
> >
> > I think we need to reschedule the builds, I'll ask that, but I don't think
> > the
> > problem lies in the package.
>
> If I'm not mistaken there where recent binNMU attempts because of the
> ongoing libical transition.
On jeu., 2016-05-12 at 17:05 +0200, Yves-Alexis Perez wrote:
> On jeu., 2016-05-12 at 09:49 +0200, Andreas Henriksson wrote:
> >
> > It seems since the last sourceful upload (4.12.1-2) the package started
> > failing to build from source on some architecture
On jeu., 2016-05-12 at 09:49 +0200, Andreas Henriksson wrote:
> It seems since the last sourceful upload (4.12.1-2) the package started
> failing to build from source on some architectures.
>
> See https://buildd.debian.org/status/package.php?p=orage
I've checked the log for amd64, and it seems
control: tag -1 confirmed
On ven., 2016-05-06 at 12:38 +0200, Guillem Jover wrote:
> Source: linux-grsec
> Source-Version: 4.5.2-2+grsec201604290633+1
> Severity: serious
>
> Hi!
>
> With latest upload this source package takes over several of the
> generic binary packages from the linux
control: severity -1 important
On jeu., 2016-05-05 at 00:31 +0100, Ian Jackson wrote:
> All Unix programs are entitled to assume that they start with
> reasonable signal dispositions, which (with a few exceptions) means
> everything set to SIG_DFL.
That's very much false in my opinion and
control: tag -1 unreproducible moreinfo
control: severity -1 important
On jeu., 2016-04-21 at 12:04 +0200, Lars Behrens wrote:
> Screen cannot be unlocked after 'light-locker-command -l' as neither
> keyboard nor mouse action brings up the unlocking dialog, screen just
> stays dark. SSH access
On lun., 2016-04-25 at 05:45 +, Amarildo Júnior wrote:
> Any news?
Stay tuned? As already said I was waiting on the kernel to become eligible for
migration. This happened two days ago, so I'll prepare a jessie-backport
upload. But you're not forced to stop breathing in the meantime.
Regards,
On dim., 2016-04-17 at 11:21 +0200, Alexander Wirt wrote:
> > With that in mind, what's the status on this? I didn't take the above mail
> as
> > an ACK for for upload to jessie-backport, but maybe it was actually one?
> It was an ACK.
Thanks!
>
> > I've uploaded a new kernel to sid just
On mar., 2016-03-22 at 13:30 +0100, Yves-Alexis Perez wrote:
> On mar., 2016-03-22 at 13:22 +0100, Alexander Wirt wrote:
> >
> > You - or better more than one person - promise to support this kernel for
> > at least stable and (later) oldstable. Preferably later jessie-lts.
Control: retitle -1 no support for building external plugin
Control: reassign -1 src:linux-grsec
Control: severity -1 wishlist
On ven., 2016-04-08 at 19:01 +0200, Andreas Beckmann wrote:
> Package: linux-headers-4.4.0-1-grsec-amd64
> Version: 4.4.6-1+grsec201604021734+1
> Severity: serious
>
control: affects -1 suricata
On jeu., 2016-03-24 at 07:20 +0100, Florian Weimer wrote:
> * Hilko Bengen:
>
> >
> > the original report may not have been 100% clear on this, but the bug is
> > the main cause of a vulnerability in Suricata (a network IDS/IPS) that
> > allows for remote denial of
On mar., 2016-03-22 at 13:22 +0100, Alexander Wirt wrote:
> You - or better more than one person - promise to support this kernel for
> at least stable and (later) oldstable. Preferably later jessie-lts.
> Supporting means the usual thing frequent uploads and so on.
Yes, I do intend to keep it
[adding the bug on CC so it gets archived there too]
On mar., 2016-03-22 at 11:57 +0100, Alexander Wirt wrote:
> On Tue, 22 Mar 2016, Julien Cristau wrote:
> > It won't be in testing if it's not suitable for stable. That would
> > defeat the purpose of testing.
> Then it defeats the purpose of
Hi,
On jeu., 2016-03-17 at 10:20 +0100, László Böszörményi (GCS) wrote:
> It seems linux-grsec will remain i386 and amd64 only.
There's no reason to, actually. It's just that right now I don't have a way to
test on other architectures, so I prefer keeping it that way. But if someone
steps to to
On jeu., 2016-03-17 at 14:22 +0100, László Böszörményi (GCS) wrote:
> > Well, uploading new Linux major version to stable looks indeed not
> trivial,
> > (thus my filing of #810506), but ultimately it's the RT's call.
> I mean can you remain in sync with kernel updates (security updates
> only)
On mer., 2016-03-02 at 20:06 +0100, Moritz Muehlenhoff wrote:
> Before considering that, did anyone approch grsecurity whether we can get
> access to the grsecurity stable patches? We would most definitely have Debian
> funds to become grsecurity sponsors to obtain access to stable patches.
I
Hi teams,
[first of all, I'm writing this with my linux-grsec hat, not my Debian
security team member hat, obviously]
As you may know, src:linux-grsec was accepted in unstable earlier this year.
As a quick summary, this is a source linux package (forked from and
periodically rebased against
On mar., 2016-02-23 at 16:59 +0100, Balint Reczey wrote:
> > So filing a new RC bug to document that.
> Could you please include the Security Team and the Release Team in the
> discussion here?
I can, but:
- release team is already well aware of this, and didn't show much enthusiasm
for the new
On sam., 2016-02-20 at 17:43 +, Ben Hutchings wrote:
> I apologise for this regression, which of course didn't affect any of
> the several machines I was able to test on.
Hi Ben, no issue, that's why it's called “unstable” :)
>
> Please can you each reply to the bug address with the
On Fri, 19 Feb 2016 16:24:06 +0900 Norbert Preining wrote:
> Package: src:linux
> Version: 4.4.2-1
> Severity: critical
> Justification: breaks the whole system
>
> Dear all,
>
> till now I was running
> linux-image-4.4.0-trunk-amd64 (from experimental)
> without any
control: reassign -1 libwnck-dev
control: retitle -1 missing dependency on libxres-dev
[adding Mate packagers to the loop since they're the maintainers for libwnck-
dev]
On sam., 2016-02-13 at 09:44 +0100, Chris Lamb wrote:
> Source: xfce4-xkb-plugin
> Version: 1:0.7.1-2
> Severity: serious
>
On sam., 2016-01-30 at 16:47 +0100, Markus Koschany wrote:
> Am 30.01.2016 um 15:08 schrieb Yves-Alexis Perez:
> > On jeu., 2016-01-28 at 17:58 +0100, Markus Koschany wrote:
> > > I have prepared security updates for radicale in Wheezy and Jessie. This
> > > is Deb
On jeu., 2016-01-28 at 17:58 +0100, Markus Koschany wrote:
> I have prepared security updates for radicale in Wheezy and Jessie. This
> is Debian bug #809920 [1]. I have tested both patches and they were
> reviewed by upstream. The debdiffs are attached to this e-mail.
Thanks. Can you remove the
On jeu., 2016-01-14 at 15:49 +0100, Christoph Anton Mitterer wrote:
> Hey.
>
> You probably know about this already, but just in case not:
> https://lists.mindrot.org/pipermail/openssh-unix-dev/2016-January/034679.htm
> l
Thanks for the report, yes we're aware of it.
Regards,
--
Yves-Alexis
Source: linux-grsec
Severity: serious
The current grsecurity release model restricts availability of the
“stable” patches to paid customers. The only free of charge release is
the “test” patch, against the latest version of the Linux kernel.
As the release team is unlikely to allow us to upload
control: reassign -1 linux-grsec-source-4.3
On mer., 2016-01-06 at 19:54 +0100, Ralf Treinen wrote:
> Here is a list of files that are known to be shared by both packages
> (according to the Contents file for sid/amd64, which may be
> slightly out of sync):
>
> /usr/src/linux-source-4.3.tar.xz
control: severity -1 important
control: tag -1 unreproducible moreinfo
On sam., 2015-12-05 at 11:04 +0100, Thomas Weber wrote:
> Package: xfce4-terminal
> Version: 0.6.3-2
> Severity: grave
> Justification: renders package unusable
>
> Launching xfce4-terminal as normal user gives the following
On mer., 2015-11-18 at 13:43 +0100, Yves-Alexis Perez wrote:
> On mer., 2015-11-18 at 08:08 +, peter green wrote:
> > Package: light-locker
> > Severity: serious
> >
> > The latest upload of light-locker added a build-dependency on
> > libsystemd-login-de
On mer., 2015-11-18 at 08:08 +, peter green wrote:
> Package: light-locker
> Severity: serious
>
> The latest upload of light-locker added a build-dependency on
> libsystemd-login-dev .
>
> libsystemd-login-dev is no longer built by the systemd source package
> and is not available in
On dim., 2015-11-01 at 15:34 +0100, Emilio Pozuelo Monfort wrote:
> Given xfce4-mixer is gone, is this still useful?
Since it uses GStreamer 0.10 anyway, it's not even the point.
> In order to drop it from
> testing, xfce4-goodies would need to stop depending on it.
I'm uploading a fixed
On lun., 2015-10-19 at 21:57 +0200, Yves-Alexis Perez wrote:
> On lun., 2015-10-19 at 18:19 +0200, Moritz Muehlenhoff wrote:
> > On Wed, May 20, 2015 at 09:38:58PM +0200, Yves-Alexis Perez wrote:
> > > Yeah, unfortunately someone has to do the work upstream, and not much
On lun., 2015-10-19 at 18:19 +0200, Moritz Muehlenhoff wrote:
> On Wed, May 20, 2015 at 09:38:58PM +0200, Yves-Alexis Perez wrote:
> > Yeah, unfortunately someone has to do the work upstream, and not much
> > people have expressed interest in that.
>
> Can we drop xfce4-mixer
control: reassign -1 libgtk-3-0
control: affects -1 evolution
control: retitle -1 gtk 3.18 upgrade leads to segfaults in evolution
On Mon, 05 Oct 2015 01:19:46 +0200 Christoph Anton Mitterer wrote:
> Downgrading libgtk-3-0 and it's friends to 3.16.6-1 "fixes" the
issue.
>
On sam., 2015-10-10 at 11:23 +0200, Yves-Alexis Perez wrote:
> control: reassign -1 libgtk-3-0
> control: affects -1 evolution
> control: retitle -1 gtk 3.18 upgrade leads to segfaults in evolution
>
> On Mon, 05 Oct 2015 01:19:46 +0200 Christoph Anton Mitterer @s
>
On sam., 2015-10-10 at 12:07 +0200, Yves-Alexis Perez wrote:
> Error verifying signature: Cannot verify message signature:
> Error writing to file: No space left on device
> On sam., 2015-10-10 at 11:23 +0200, Yves-Alexis Perez wrote:
> > control: reassign -1 libgtk-3-0
>
On Sat, Aug 22, 2015 at 11:48:47AM +0300, Dmitry Shachnev wrote:
Hi Yves-Alexis,
On Sat, 08 Aug 2015 19:04:21 +0200, Yves-Alexis Perez wrote:
I somehow missed this bug. I'm a bit unsure what to do with those
symbols updates. I guess it's related to some libstdc++ change but I'm
unsure
Control: tag -1 +help
On jeu., 2015-02-12 at 10:33 +, Matthias Klose wrote:
Package: src:lightdm
Version: 1.10.3-3
Severity: normal
Tags: sid stretch
User: debian-...@lists.debian.org
Usertags: ftbfs-gcc-5
[...]
dh_lintian -a -O--parallel
dh_perl -a -O--parallel
On jeu., 2015-05-28 at 21:37 -0400, Michael Gilbert wrote:
control: tag -1 confirmed, help
On Wed, May 27, 2015 at 7:25 AM, Yves-Alexis Perez wrote:
Note that the binary blob is executed throught native client, which is
not enabled by default, so I /think/ you need explicit action from
-plugins
ipsec stop
ipsec start
Hi,
libstrongswan (which is a dependency of the various charon daemons) as a
Recommends: on libstrongswan-standard-plugins so if you install
Recommends: I think it /should/ be the case.
Regards,
--
Yves-Alexis Perez
signature.asc
Description: Digital
101 - 200 of 750 matches
Mail list logo