Hi Kevin,
those 4 security issues were fixed via DSA-3798-1 in jessie-security, by
backporting the appropriate upstream changes (thanks to Thorsten for
doing that).
I've verified 1.4.13 only contains those security fixes, and no new
major evolution or feature, so could you please prepare and
On Tue, Feb 28, 2017 at 10:16 AM, Michael Tokarev wrote:
> 17.02.2017 13:48, Christian Ehrhardt wrote:
>
> > - a) Ubuntu only fixes that can be hidden under the vendor based
> > control-in -> control mechanism
> > - b) Fixes applying to Debian as well (only for those there
On Tue, Feb 28, 2017 at 11:54:05PM +0100, Emilio Pozuelo Monfort wrote:
> On 24/02/17 11:30, Adrian Bunk wrote:
> > + * Switch from -dbg to -dbgsym.
>
> Please avoid doing that for future unblocks.
libpreludecpp0 was split from libprelude2 to fix an RC bug.
Given the choice between either
On 2017-03-01 00:50:59 [+0100], John Paul Adrian Glaubitz wrote:
> Hi!
Hi,
> The problem is that if the package was to be rebuilt now, it would be
> rebuilt with OpenSSL 1.1 and not OpenSSL 1.0 which is the original
> motivation for this bug report by Sebastian!
it already has been built with
The character "载" can't be displayed with the following versions of
xfonts-unifont
xfonts-unifont_7.0.06-1_all.deb
xfonts-unifont_9.0.06-2_all.deb
So the unicode font in stable version wasn't generated from xfonts-unifont.
发件人: 张 敬强
发送时间: 2017年3月1日 6:58:53
Source: gcc-7
Version: 7-20170221-1
Severity: wishlist
User: helm...@debian.org
Usertags: rebootstrap
Hi Matthias,
thank you for disabling brig in stage1 and stage2. It still is rightly
enabled in the unstaged cross compiler build. Since it is not needed for
bootstrapping, I'd like to disable
Control: severity -1 important
Control: notfound -1 2.02-beta2-22+deb8u1
This will has a major impact on chinese or even CJK users,
so I'm changing the severity to important.
Control: severity -1 important
Control: notfound -1 2.02-beta2-22+deb8u1
This will has a major impact on chinese or even CJK users,
so I'm changing the severity to important.
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hey!
We would like to upload HAProxy 1.7.3 to unstable. This is mostly a
bugfix only release (1.7 is the current stable branch). Here is
Steven Chamberlain:
> Package: release.debian.org
> User: release.debian@packages.debian.org
> Usertags: unblock
> X-Debbugs-Cc: debian-b...@lists.debian.org
>
> Hi!
>
> Attached are proposed debdiffs for anna, cdebootstrap and their
> dependency libdebian-installer (Bug #856210).
>
> Would
Martin Michlmayr writes:
...
> Rick Thomas has offered to test on the OpenRD Ultimate and (I believe)
> Client.
If you can point me at relevant images, or instructions on how to build
something that is worth testing, I should have time to do tests of the
OpenRD Ultimate this
Package: texlive-lang-japanese
Version: 2016.20170123-3
Severity: serious
Dear Norbert,
Two scripts, /usr/bin/kanji-config-updmap{,-sys}, are not provided
because of "debian/scripts.lst" doesn't follow upstream renaming:
jfontmaps -> ptex-fontmaps.
As you know, these scripts are very important
Hi,
Sorry for the bug report, it turns out that upgrading to the current kernel
git master caused the issue.
You can close this bug report, I'm just hoping someone will spot this
upstream in the kernel and it'll be fixed (unless its intentional).
Package: libgtk-3-0
Version: 3.22.9-1
Severity: normal
Dear maintainer,
Since upgrading to version 3.22.9, dragging operations cannot be performed using
two fingers on a touchpad without any exposed buttons (e.g. where pushing the
surface
itself is the button). What happens now is that the
Cyril Brulebois (2017-02-21):
> I think that should work, yes. Please let me know when that's happened,
> and I'll do the testing as soon as possible.
This has happened, and building a netboot-gtk image with stretch udebs
and with p-u enabled got me a 1.18-4.1 version of the
Source: gdk-pixbuf
Version: 2.31.1-2
Severity: important
Tags: upstream security
Forwarded: https://bugzilla.gnome.org/show_bug.cgi?id=779020
Hi,
the following vulnerability was published for gdk-pixbuf.
CVE-2017-6314[0]:
Infinite loop in io-tiff.c
If you fix the vulnerability please also make
Source: gdk-pixbuf
Version: 2.31.1-2
Severity: important
Tags: security upstream
Hi,
the following vulnerability was published for gdk-pixbuf. There is no
patch upstream yet, and from a quick skim over io-icns.c the soure is
there.
CVE-2017-6313[0]:
An dangerous integer underflow in io-icns.c
clone 817193 -1 -2
found -1 77
retitle -1 diffoscope: test_cbfs::test_listing fails due to unexpected header
in output
found -2 77
retitle -2 diffoscope: test_icc::test_diff fails due to locale difference in
output
thanks
Zbigniew Jędrzejewski-Szmek wrote:
> With diffoscope-77, I get the
Source: gdk-pixbuf
Version: 2.31.1-2
Severity: important
Tags: security upstream
Forwarded: https://bugzilla.gnome.org/show_bug.cgi?id=779012
Hi,
the following vulnerability was published for gdk-pixbuf.
CVE-2017-6312[0]:
Out-of-bounds read on io-ico.c
If you fix the vulnerability please also
The WNPP request is now created as https://bugs.debian.org/856425 >.
--
Happy hacking
Petter Reinholdtsen
On Tue, Feb 21, 2017 at 7:17 AM, Vincent Lefevre wrote:
> On 2017-02-16 11:00:09 -0700, Jaimos Skriletz wrote:
>> The original bug in which the patch appears to have fixed is every
>> time a Button was added/removed from FvwmIconMan causing the window to
>> change sizes, the
Package: mousepad
Version: 0.4.0-4
Severity: normal
Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What led up to the situation?
Normal working
* What exactly did you do (or not do) that was effective (or
ineffective)?
Changing the
Control: retitle -1 ITP: libclasslojure-clojure -- Clojure library to
create a classloader with an alternate classpath
Hi,
I took a stab at packaging this. This is my first package submitted to
Debian so I don't know what I'm doing.
All the debian/ stuff can be found here:
Package: awesome
Version: 4.0-1
Severity: minor
Hi!
Go to /usr/share/doc/awesome and "ls -l":
=
-rw-r--r-- 1 root root 2814 jan 19 04:25 00-authors.md
-rw-r--r-- 1 root root 2198 jan 19 04:25 01-readme.md.gz
-rw-r--r-- 1 root root 3543 jan 19 04:25 02-contributing.md
-rw-r--r-- 1 root root
> A new bug is better
Agreed:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=856439 (
fakeroot doesn't detect and handle message queue and semaphore id collision
On Wed, 1 Mar 2017, Olly Betts wrote:
But the release manager gets to override your artificially inflated severity
so all that really achieves is to waste the RM's precious time.
Why was this binNMU done anyway?
On Tue, Feb 28, 2017 at 06:35:16PM +0100, Michael Biebl
wrote:
> Can you elaborate where and how such data corruption can happen?
> Not being able to shutdown/detach all DM devices has been the case for
> basically forever in Debian (most prominent example if / is on LVM).
>
On Tue, Feb 28, 2017 at 02:55:30PM +0100, Michael Biebl
wrote:
> >> Can you please elaborate why you filed this against systemd?
> >
> > Because I thought systemd is what cleans up dm-targets at shutdown.
>
> From your initial bug report, it was not clear where exactly you
Hi Daniel,
Daniel Kahn Gillmor , 2017-02-28 18:30 -0800:
>
> On Tue 2017-02-28 18:17:08 -0800, Michael[tm] Smith wrote:
> > Per discussion at
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850982#75
> > please consider adding the following to
> >
Package: u-boot
Version: 2016.11+dfsg1-3
Severity: wishlist
Debian introduced OpenRD images and later removed them because the
stopped working (see #837629).
A fix has now been posted upstream:
https://lists.denx.de/pipermail/u-boot/2017-February/282676.html
I would like to kindly request that
Package: yabar
Version: 0.4.0-1
Severity: important
I'm using yabar with bspwm, and have it set to start through my wm's
bootstrap routine. I hadn't noticed anything strange until I opened
up a spreadsheet with libreoffice. Upon opening the program, the bar
disappeared from my
On Tue 2017-02-28 18:17:08 -0800, Michael[tm] Smith wrote:
> Per discussion at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850982#75
> please consider adding the following to /etc/logcheck/ignore.d.server/systemd
> as part of the gnupg-agent package install.
thanks for this suggestion,
Daniel Kahn Gillmor , 2017-02-28 16:12 -0800:
> ...
> Sure, i'd be happy to accept reasonable logcheck filters to the
> gpg-agent and dirmngr binary packages. Please submit a separate bug
> report with the suggested filters, and i'll review them and roll them
> into the
Package: fakeroot
Version: 1.20.2-1
Severity: normal
Tags: patch
Dear Maintainer,
I'm raising this as requested by Clint in:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=855662#15
Fixing that bug (fakeroot: when msgrcv is interrupted by a signal, faked
accidentally reprocesses the
On Wed, Mar 01, 2017 at 02:58:29AM +0100, Guillem Jover wrote:
> Hi!
>
> On Fri, 2017-02-17 at 06:08:25 +0100, Guillem Jover wrote:
> > On Thu, 2017-02-16 at 17:23:00 +, Ximin Luo wrote:
> > > Control: tags + patch
> >
> > > I've done an initial implementation here:
> > >
> > >
Package: gnupg-agent
Version: 2.1.18-3
Severity: wishlist
Per discussion at https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850982#75
please consider adding the following to /etc/logcheck/ignore.d.server/systemd
as part of the gnupg-agent package install.
^\w{3} [ :[:digit:]]{11}
Hi,
On 2017-02-27 22:57:37 +0100, Axel Beckert wrote:
> Vincent: Can you still reproduce this issue? I'm not sure what exactly
> I should do to reproduce the bug as I have not much of an idea what
> you mean with "a server is running inside screen". Can you please
> provide an example on how to
On Fri, Feb 24, 2017 at 12:30:50AM +0100, Petr Vanek wrote:
> I have been using Evince for years and am happy with it, but for
> whatever reason, it doesn't make links clickable in my own created
> documents, see example here: http://www.penguin.cz/~vanous/out.pdf - the
> numbers in circles have
Hi!
On Fri, 2017-02-17 at 06:08:25 +0100, Guillem Jover wrote:
> On Thu, 2017-02-16 at 17:23:00 +, Ximin Luo wrote:
> > Control: tags + patch
>
> > I've done an initial implementation here:
> >
> > https://anonscm.debian.org/cgit/collab-maint/devscripts.git/log/?h=pu/debsign-buildinfo
> >
On Tue, Feb 28, 2017 at 08:37:39PM -0500, Scott Talbert wrote:
> On Wed, 1 Mar 2017, Olly Betts wrote:
>
> >>It sure would be nice to get rid of this warning which will otherwise be
> >>around for the duration of stretch. You don't think it's worth filing a
> >>freeze exception?
> >
> >Severity
On Tue 2017-02-28 13:04:15 -0800, Michael[tm] Smith wrote:
> OK one small very concrete thing I think would help would be if the package
> added logcheck filters for messages the change has caused to now start
> getting logged to syslog in the following form:
>
> Feb 17 01:24:15 sideshowbarker
On Wed, 1 Mar 2017, Olly Betts wrote:
This will have started because wxwidgets3.0 got binNMUed a few days ago.
I doubt we can address this for stretch though.
It sure would be nice to get rid of this warning which will otherwise be
around for the duration of stretch. You don't think it's
On Wed, 1 Mar 2017, Olly Betts wrote:
It sure would be nice to get rid of this warning which will otherwise be
around for the duration of stretch. You don't think it's worth filing a
freeze exception?
Severity "minor" means it doesn't meet the criteria:
Jonathan Wiltshire writes:
> Control: tag -1 confirmed moreinfo
>
> On Sat, Feb 25, 2017 at 09:10:01AM -0400, David Bremner wrote:
>> I've appended a diff from upstream git, this also includes any debian
>> changes except finalizing the date and distribution in the
>>
On Tue, Feb 28, 2017 at 08:24:24PM -0500, Scott Talbert wrote:
> On Wed, 1 Mar 2017, Olly Betts wrote:
> >This will have started because wxwidgets3.0 got binNMUed a few days ago.
> >I doubt we can address this for stretch though.
>
> It sure would be nice to get rid of this warning which will
Control: owner -1 !
On Tue, Feb 28, 2017 at 07:48:55PM +, John Hackett wrote:
> Go ahead - do I need to do anything to release it to you?
I will handle it, thanks.
--
ChangZhuo Chen (陳昌倬)
Debian Developer (https://nm.debian.org/public/person/czchen)
Key fingerprint =
On Tue, Feb 28, 2017 at 06:57:43PM +0200, Adrian Bunk wrote:
> This is caused by the recent binNMU (sic) of wxwidgets3.0,
> that resulted in wx3.0-headers requiring a C++11 compiler
> (first rebuild with gcc 6 that defaults to C++11).
>
> This breaks building of qutemol (and potentially other
On Tue, Feb 28, 2017 at 6:38 PM, Samuel Thibault wrote:
> When running e.g. reportbug -N xyz and selecting
>
> x - Provide extra information.
>
> only x...@bugs.debian.org is set as recipient,
> xyz-submit...@bugs.debian.org is not. That is not what people expect to
>
Package: postgresql-plproxy
Version: 2.7-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu zesty ubuntu-patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
* d/t/control: the newpid package fails to install in LXD
On Tue, Feb 28, 2017 at 11:33:08AM +0300, Andrey Skvortsov wrote:
> If wxPython application (for example wxglade) is started, warning about
> mismatching C++ ABI is shown.
>
> Here is simple example to reproduce the case.
>
> $ python -c 'import wx'
> 11:15:20: Warning: Mismatch between the
Package: xrdp
Version: 0.9.1-7
Severity: normal
Dear Maintainer,
If in xrdp.ini the option security_layer=tls is configured, a client is not
able to connect.
E.g. on the client-side using rdesktop the following error is displayed:
140464326739656:error:1408F10B:SSL
Package: libortp-dev
Version: 3.6.1-3
Severity: minor
Dear Maintainer,
The description of the package mentions RFC 1890, which has been
replaced by RFC 3551, 13 years ago.
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64
Control: tags -1 + moreinfo
On Tue, Feb 28, 2017 at 03:31:41PM +0200, Andres Gomez wrote:
> Package: libglib2.0-0
>
> my locally built epiphany SIGSEVed in slab_allocator_free_chunk, after
> visiting several pages.
On Tue, Feb 28, 2017 at 05:41:02PM +0200, Andres Gomez wrote:
> Package:
Control: severity 856152 important
On Wed, Mar 01, 2017 at 06:39:37AM +0800, Chris Lamb wrote:
> retitle 856152 python-apt: FTBFS: AptKeyError: recv from
> 'hkp://localhost:19191' failed for
> '0xa1bD8E9D78F7FE5C3E65D8AF8B48AD6246925553'
> thanks
>
> Julian Andres Klode wrote:
>
> > Retry it.
On Wed, Mar 01, 2017 at 01:21:22AM +0100, Julian Andres Klode wrote:
> Package: sbuild
> Version: 0.73.0-4
> Severity: important
>
> Fails with a lot of errors for Debian chroots, but it works perfectly fine
> with Ubuntu ones. Not sure what's going wrong here. I think this has been
> going on
Package: sbuild
Version: 0.73.0-4
Severity: important
Fails with a lot of errors for Debian chroots, but it works perfectly fine
with Ubuntu ones. Not sure what's going wrong here. I think this has been
going on for months, but I often forget about it because I don't do much
binary building
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock influxdb-python 3.0.0-2. If fixes 841559 which caused FTBFS.
It failed to build because of an introduced FutureWarning which we don't
have to solve right now because the
Control: tags -1 moreinfo
Hi Reiner!
> Running apt-get again to complete the update, is aborted with the hint to use
> 'dpkg --configure -a'.
> But doing so, the update is also not completed, again a reboot is done.
> Finally, this leaves the system in a half-installed mode, without no
>
Jean-Philippe MENGUAL, on mer. 01 mars 2017 00:18:53 +0100, wrote:
> I think accessibility::accessible-with::at-spi is the most transversal tag,
> and then very interesting. Other proposals you do seem for me good, but more
> difficult to do: 1st because it means a package should be tested with a
Control: tags -1 + fixed-upstream patch
Upstream addressed this by avoiding linking libxapianbackend.so to
openssl (apparently it doesn't use it anyway):
https://github.com/FabriceColin/pinot/commit/3a40d5abe159a106f3aabaedf1a199020946b3b5
Cheers,
Olly
Package: gitlab
Version: 8.13.11+dfsg-4
Severity: grave
Justification: renders package unusable
Dear Maintainer,
gitlab installs, but will not complete configuration, because (at least)
it is looking for a wrong version of a postgresql extension.
Possibly also incompatible with latest
Hi!
> We shouldn't be changing the way a package builds during freeze.
> It was last built with openssl 1.0, so that's what we should have for now.
The problem is that if the package was to be rebuilt now, it would be
rebuilt with OpenSSL 1.1 and not OpenSSL 1.0 which is the original
motivation
Hi Ondřej,
Ondřej Surý wrote:
> d/copyright doesn't list all license holders and has wrong copyright
> for at least some files:
>
> Please convert to machine-readable copyright file and add missing copyrights:
> + Files: * is GPLv2+, e.g. any later version and not just GPL-2
I disagree here:
tag 850282 + pending
thanks
Some bugs in the influxdb package are closed in revision
c72b959213ca374ee4697d7fab28fa5a9bf83fb8 in branch 'master' by aviau
The full diff can be seen at
https://anonscm.debian.org/cgit/pkg-go/packages/influxdb.git/commit/?id=c72b959
Commit message:
Disable
On 28.02.2017 23:26, Michael Biebl wrote:
> Roland, would you be willing to try that?
Sorry, I've stopped using cryptswap a while ago, and I'm not sure
whether I'll remember enough of the howtos to get it running again :-|
The GitHub PR indeed sounds a lot like the problem I had, so if no one
Package: reportbug
Version: 7.1.5
Severity: normal
Hello,
When running e.g. reportbug -N xyz and selecting
x - Provide extra information.
only x...@bugs.debian.org is set as recipient,
xyz-submit...@bugs.debian.org is not. That is not what people expect to
happen, they expect to be sharing
Thanks for the info. Sounds like something we want to support. How do
you know which proguard can you use? What kind of testing did you do?
partially solved => no more crash, but same debug message (and more)
issue= remove all personal libraries added in config/kicad/fp-lib-table
and re-add this personal libraries with "libraries wizard"
new error message at the pcbnew startup(#840287
Package: open-vm-tools
Version: 2:10.1.5-5055683-1
Severity: normal
Tags: newcomer
Dear Maintainer,
* What led up to the situation?
After a recent update added the vgauth.service unit file, I checked
the status of vgauthd.service. While it apparently starts, I noticed
there
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package: android-sdk-meta
Support for some common devices was missing in 25.0.0+1 (#814056).
This also fixes another usability bugs with the SDK license handling
that was
Package: debtags
Followup-For: Bug #855446
Hi,
1st, thanks Samuel to re-open this topic. I think it's an excellent and simple
idea to apply. From 2 packages, it would be very useful to know, before
installing, wether it's usable or not with an assistive techno.
I think
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package: repo
It previously had bash-completion, and a build bug preventing the
upstream completion file from being installed in 1.12.37-2 (XX).
Attached is the source
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package: android-platform-system-coreq
It previously had bash-completion, and a build bug preventing the
upstream completion file from being installed in 1:7.0.0+r1-2
Package: release.debian.org
Severity: normal
User: release.debian@packages.debian.org
Usertags: unblock
Please unblock package: android-platform-frameworks-base
It previously had bash-completion, and a build bug preventing the
upstream completion file from being installed in 1:7.0.0+r1-2
Package: wnpp
Severity: wishlist
Owner: Philippe Thierry
* Package name: scap-security-guide
Version : 0.1.31-10
Upstream Author : Watson Yuuma Sato
* URL : https://www.open-scap.org/security-policies/scap-security-
guide/
*
Bastian Blank wrote:
> On Tue, Feb 28, 2017 at 10:00:01PM +, Steven Chamberlain wrote:
> > That differs from the latest version of my patch, and from what I sent
> > earlier today to the release team when asking about a potential unblock:
> >
On 24/02/17 11:30, Adrian Bunk wrote:
> + * Switch from -dbg to -dbgsym.
Please avoid doing that for future unblocks. The rest looks good so I have
unblocked it this time.
Thanks,
Emilio
Control: fixed -1 reportbug/7.1.5
On Mon, 27 Feb 2017 20:00:48 -0500 Sandro Tosi wrote:
> On Mon, Feb 20, 2017 at 4:52 PM, Francesco Poli (wintermute)
> wrote:
> > In my opinion, the bug report may be safely closed as fixed in
> > reportbug/7.1.5 : maybe the original
On 28/02/17 18:04, Jonathan Wiltshire wrote:
> On 2017-02-26 19:16, Tomasz Buchert wrote:
> > Control: tag -1 -moreinfo
> >
> > On 26/02/17 18:51, Jonathan Wiltshire wrote:
> > > Control: tag -1 confirmed moreinfo
> > >
> > > [...]
> > >
> > > You should close the bug in your changelog, and you do
On Tue, Feb 28, 2017 at 10:00:01PM +, Steven Chamberlain wrote:
> That differs from the latest version of my patch, and from what I sent
> earlier today to the release team when asking about a potential unblock:
> https://lists.debian.org/debian-release/2017/02/msg01033.html
This happens if
retitle 856152 python-apt: FTBFS: AptKeyError: recv from
'hkp://localhost:19191' failed for '0xa1bD8E9D78F7FE5C3E65D8AF8B48AD6246925553'
thanks
Julian Andres Klode wrote:
> Retry it. Maybe it timed out or something.
I don't think this is a timeout issue, but if it is, surely the package
build
Package: libvcflib-tools
Version: 1.0.0~rc1+dfsg1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
I installed libvcflib-tools on testing/stretch. When I ran 'vcflib', I
saw this:
$ vcflib
Usage: /usr/bin/vcflib
We can't regenerate the upstream version since it is generated from a
git commit ID, but that git commit is not public:
fastboot/Android.mk:
fastboot_version := $(shell git -C $(LOCAL_PATH) rev-parse --short=12
HEAD 2>/dev/null)-android
Sebastian Humenda, on lun. 27 févr. 2017 14:30:19 +0100, wrote:
> Sebastian Humenda schrieb am 20.02.2017, 11:13 +0100:
> >>Ok, we can wait more, no pb :)
> >No crashes, I think it's safe.
> Ok, seems hard to reproduce. Here's another bt.
Does the change at least reduce the frequency of
Am 28.02.2017 um 21:39 schrieb Felipe Sateler:
> Control: forwarded -1 https://github.com/systemd/systemd/pull/5480
>
> On Thu, 28 May 2015 00:25:49 +0200 Roland Hieber wrote:
>> Package: systemd
>> Version: 219-10
>> Severity: normal
>>
>> Dear Maintainers,
>>
>> I have now
xrdp-sesman is starting, but xrdp fails to start and automatically stops
xrdp-sesman.
output of journalctl -xn is:
Failed at step RUNTIME_DIRECTORY spawning /usr/sbin/xrdp-sesman: File exists
Actually, "socksetup" is now called more than once, which could be avoided by
removing one line from
Hello João
Could you create a patch and post it in this thread?
Thank you very much for the fix!
Greetings,
Marcos
tags 855350 + help
thanks
Hi Kertesz and Martin
Thank you for the report and information regarding options.
The performance issue is definitely a problem. I do not have a solution at
the moment.
I have a little problem testing this myself at the moment as only have sid
in a chroot and X will
Hi
Thank you for the report. I was not aware that xvnc4 had those options.
Is it possible to set a lower color level on the server side? Or do you
want this on only certain clients?
I'm quite sure you can set the color depth on the server side.
// Ola
On 22 February 2017 at 21:38, Celelibi
I believe the bug is not yet fixed.
xrdp-service is now starting, but starting xrdp leads to an error.
Proposed fix is to remove the line "RuntimeDirectory=xrdp" from xrdp.service:
--- a/instfiles/xrdp.service
+++ b/instfiles/xrdp.service
@@ -7,7 +7,6 @@ After=network.target xrdp-sesman.service
Package: postgresql-plproxy
Version: 2.7-1
Severity: normal
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu zesty ubuntu-patch
Dear Maintainer,
The autopkgtests for postgresql-plproxy have been failing ever since
2.6-2 because postgres is not network namespace aware.
In
On Tue, 2017-02-28 at 16:06 -0400, Raymond Burkholder wrote:
> In installing today’s (2016/02/28) netbook.tar.gz:
>
> https://d-i.debian.org/daily-images/amd64/daily/netboot/netboot.tar.gz
>
> And installing manually via pxeboot, in the console I see:
>
> scsi_mod: disagrees about version of
Bastian Blank wrote:
> Adopted and commited to
> https://anonscm.debian.org/git/d-i/libdebian-installer.git, branch
> sha256
That differs from the latest version of my patch, and from what I sent
earlier today to the release team when asking about a potential unblock:
Source: openldap
Severity: minor
Hi,
Roland Bauerschmidt isn't a Debian developer since 2010, you can
remove him from Uploaders.
Cheers,
Moritz
* Adrian Bunk:
> Doesn't seem to work:
> https://buildd.debian.org/status/fetch.php?pkg=google-perftools=i386=2.5-2.1=1488295669=0
Yeah, those test scripts a bit crappier than I thought. Let's try that
again...
Cheers,
-Hilko
Package: icedove
Version: 1:45.6.0-1~deb8u1
Dear Maintainer,
I'm not 100% sure but I think I have the same issue and I'm able to provide
a verbose stack trace. (or at least a related one)
I have included some interesting but in my oppinion unrelated warning
messages about an incomplete added
found 850282 1.1.1+dfsg1-3
thanks
On Tue, 28 Feb 2017, Alexandre Viau wrote:
>* Disable tests on i386 (Closes: #850282)
Disabling all the tests on i386 is unnecessary and also it does not fix
the bug I reported at all (so, no point in using Closes here).
Instead of disabling all the tests
On Sun, Feb 26, 2017 at 06:30:31PM +, Steven Chamberlain wrote:
> I've attached only the most minimal patch to allow reverse-depends do
> implement SHA256. They must adapt to the new names of struct members
> *and* remember that the hash length is now different. (The hash data is
> stored in
Hello Lukas Wunner,
Thanks for following up with both a new proposal and patch!
On Mon, Feb 27, 2017 at 02:34:34PM +0100, Lukas Wunner wrote:
[...]
> Okay, let's define a policy first. How about:
>
> (1) Users can set HWCLOCKACCESS=no in /etc/default/hwclock to prohibit
> setting the
I do not want to reopen old issues but this seems to be the only source for a
similar strange log entries we were facing.
I found that any call to expand users might trigger the request to be
generated, which is quite logical if known. Therefore this is not a bug.
For example:
$ python
import
1 - 100 of 288 matches
Mail list logo