On 15/07/16 09:20, ChangZhuo Chen (陳昌倬) wrote:
> [...]
Hi Chen,
if you need help with this, let me know. I wanted to package this
myself. There are some issues that I encountered, but these patches
from FreeBSD [1] should be helpful.
Cheers,
Tomasz
[1] https://svnweb.freebsd.org/ports/head/graph
On Fri, Jul 15, 2016 at 08:46:22AM +0200, Tomasz Buchert wrote:
> On 15/07/16 09:20, ChangZhuo Chen (陳昌倬) wrote:
> Hi Chen,
> if you need help with this, let me know. I wanted to package this
> myself. There are some issues that I encountered, but these patches
> from FreeBSD [1] should be helpful.
Quoting Steve McIntyre (st...@einval.com):
> Arg, sorry. :-( It's very easy to make mistakes when editing large
> numbers of files like this by hand. I double-checked the diffs,
> even. Could we add some commit-time checking to run msgfmt etc. and
> warn on errors?
Yes, this is exactly what I did
Control: tags -1 + patch
On 2016-07-13 13:12 -0400, Aaron M. Ucko wrote:
> The hurd-i386 build of procps gets farther now (thanks!) but still fails:
>
> mv /«PKGBUILDDIR»/debian/tmp/bin/kill /«PKGBUILDDIR»/debian/tmp/bbin/
> [...]
> (cd /«PKGBUILDDIR»/debian/tmp/bin && mv kill kill.procps )
Control: tags -1 + patch
On 2016-07-14 21:25 +0200, Sven Joachim wrote:
> Package: procps
> Version: 2:3.3.12-2
>
> After the fix for bug #816237, the procps.install files for kfreebsd and
> hurd install kill(1) as /bin/kill.procps/kill. I suppose that is not
> what has been intended, but sadly
Don't the release notes of the next version address this?
https://ccache.samba.org/releasenotes.html#_ccache_3_2_6
On Thu, 30 Jun 2016 23:08:05 +0200 Joel Rosdahl wrote:
> Thanks for the bug report. I have reproduced the issue, see the attached
> script. Yes, to trigger the bug, the source file
Wow I'm impressed you got that far.
All I get is an empty folder and a log file that I cant read.
I was going to test it tomorrow morning and if nothing different occurs was
going to file a bug report then.
On 15 July 2016 at 12:16, Ben Caradoc-Davies wrote:
> Package: live-wrapper
> Version: 0.
Control: forcemerge 830874 828733
This package has already been uploaded by the Debian OpenStack packagers team.
https://tracker.debian.org/pkg/python-osc-lib
Thanks,
Jeremy Bicha
Package: bibcursed
Version: 2.0.0-6
Followup-For: Bug #817375
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
* debian/compat: Bump to 9.
* debian/control: Build-depend on de
This bug is not fixed in plasma-discover 5.7.0-3.
See below:
Unpacking plasma-discover-common (5.7.0-3) over (5.6.5-1) ...
dpkg: error processing archive
/var/cache/apt/archives/plasma-discover-common_5.7.0-3_all.deb
(--unpack):
trying to overwrite
'/usr/share/libdiscover/backends/knsplasmoids-ba
Another possibility is a bug in addressable 2.4.
https://github.com/sporkmonger/addressable/issues/234
Can you try with addressable 2.3.8?
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
> It looks like -17 reached linux-firmware.git a few hours ago. Maybe
> it's time to update firmware-nonfree?
Yes please, as it also contains iwlwifi-7265D-21.ucode which was needed for my
ASUS ZenBook UX305CA.
I managed to workaround it, but I doubt the average user would.
signature.asc
Descri
Package: bbmail
Version: 0.8.3-6
Followup-For: Bug #817374
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
* debian/compat: Bump to 9.
* debian/control: Build-depend on debhe
Package: audacity
Version: 2.1.2-1+b1
Severity: minor
Dear Maintainer,
In the settings window for LADSPA effects, the sliders do not move to
negative integers. If, for example, an integer option ranges from -3 to
3 (inclusive), the slider will only move within one half of the bar.
What is intere
Package: bb
Version: 1.3rc1-8.4
Followup-For: Bug #817373
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
* debian/compat: Bump to 9.
* debian/control:
- Build-depend on
Package: live-wrapper
Version: 0.3
Severity: normal
Dear Maintainer,
the output live.iso produced by lwr has neither MBR nor any partitions (MBR or
GPT). It appears to be a plain ISO image. It cannot be booted from a thumb
drive.
Kind regards,
Ben.
-- System Information:
Debian Release: stret
Package: live-wrapper
Version: 0.3
Severity: normal
Dear Maintainer,
if isolinux and xorriso are not installed, lwr fails with:
ERROR: [Errno 2] No such file or directory: '/usr/lib/ISOLINUX/isolinux.bin'
After manually installing isolinux, lwr still fails with:
ERROR: No such file or director
Package: courier-mlm
Version: 0.73.1-1.6
Severity: normal
Dear Maintainer,
I've encountered some bugs in couriermlm, when a list is setup the
option 'NOBOZOS=1' is set by default, which should bounce bad ctl
command messages sent to user-list@domain instead of
user-list-command@domain.
What's su
Package: wnpp
Severity: wishlist
Owner: "ChangZhuo Chen (陳昌倬)"
* Package name: lepton
Version : 1.0
Upstream Author : Copyright (c) 2016 Dropbox, Inc.
* URL : https://github.com/dropbox/lepton
* License : Apache-2
Programming Lang: C
Description : tool
On Monday, July 11, 2016 5:38:52 PM CDT Lisandro Damián Nicanor Pérez Meyer
wrote:
> On domingo, 10 de julio de 2016 2:01:04 P. M. ART Steve M. Robbins wrote:
> > Hi,
> >
> > I wanted to make people aware that I have uploaded Digikam 5.0.0 packages
> > to Debian earlier today.
>
> First of all:
On Friday, July 15, 2016 12:09:46 AM Valentin Lorentz wrote:
> Package: opendkim
> Version: 2.10.3-5
> Severity: grave
>
> Dear maintainer,
>
> After a recent upgrade of my system, I get this whenever I try to start
> opendkim (including when run by dpkg while configuring it):
>
> root@Hydro
Package: ttf-mscorefonts-installer
Version: 3.6
Followup-For: Bug #820627
Same problem here, on a system I installed earlier today.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86
Package: libgraph-easy-perl
Version: 0.76-1
Severity: wishlist
File: /usr/bin/graph-easy
Change this
< --helpPrint the full documentation, not just this short overview.
> --helpPrint the full documentation, not just a short overview.
else doesn't make sense in many contexts!
Santiago Vila writes:
> I have the ok from the Release Managers to consider this issue as RC
> for stretch. I'm going to wait at least one week before raising
> this to "serious".
Go ahead and raise the severity whenever you want.
I'll be happy to take a look at this, but I really don't have ti
On 14 July 2016 at 09:50, Lucas Nussbaum wrote:
| Source: rquantlib
| Version: 0.4.2-2
| Severity: serious
| Tags: stretch sid
| User: debian...@lists.debian.org
| Usertags: qa-ftbfs-20160713 qa-ftbfs
| Justification: FTBFS with GCC 6 on amd64
Please see _extended_ discussion with Martin and doko
Package: jquery-goodies
Version: 11-2
Severity: wishlist
Tags: patch
User: ubuntu-de...@lists.ubuntu.com
Usertags: origin-ubuntu yakkety ubuntu-patch
Dear Maintainer,
In Ubuntu, the attached patch was applied to achieve the following:
- Update to PHP7.0 dependencies (LP #1544352).
Thanks fo
Source: libcap-ng
Version: 0.7.7-3
Severity: wishlist
Tags: patch
Hi,
libcap-ng is part of the build-closure of essential and thus needs to be
able to be cross built. On the other hand, cross building python
extensions is currenty non-trivial as the python policy is not yet fully
fleshed out wrt
Antonio Terceiro wrote:
> On Fri, Jul 08, 2016 at 06:53:29PM +, Eric Wong wrote:
> > Thanks for the report. Can you try the patch below?
>
> Didn't help.
>
> I can't, however, reproduce this locally on my workstation.
Thanks for following up.
> > I'd be interested to know what non-standar
On 15.07.2016 01:09, Mark Vejvoda wrote:
> I pushed a fix for the new GCC in our git repo in the develop branch.
>
> https://github.com/MegaGlest/megaglest-source/commit/daf1dac128515d9fc535018c9c4d19b9ac45a1a4
>
> Thanks
Thanks Mark. I was just about to upload the new revision.
Cheers,
Markus
I pushed a fix for the new GCC in our git repo in the develop branch.
https://github.com/MegaGlest/megaglest-source/commit/daf1dac128515d9fc535018c9c4d19b9ac45a1a4
Thanks
Hi Santiago,
- Original Message -
> Greetings.
>
> I have the ok from the Release Managers to consider this issue as RC
> for stretch. I'm going to wait at least one week before raising
> this to "serious".
>
> If you need help to fix this bug, please tag it as "help".
>
I have a build
Control: reassign -1 linux-image-4.6.0-1-686-pae
On 14 July 2016 at 12:36, Loris e Anna wrote:
> Hi Filipe,
> as your request, in attach the verbose log.
For some reason, your kernel is not creating a proper alsa device, and
ALSA does not appear to know about it. Therefore reassigning to the
ker
log states
Daemonize(): Configured to run in foreground mode.
even although in the config file it states:
foreground_mode no
only since upgrading to 1.2.7-1.2
The systemd service file doesn't work for any conmux config file with a hyphen.
I filed a separate bug for this:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=831358
But the short version is it should use %i instead of %I so that conmux
configs of the form foo-bar.cf don't get translated in t
On Thu, 14 Jul 2016 14:10:20 -0700 Kevin Hilman wrote:
> I've encountered this bug both on Debian jessie and Ubuntu xenial, and
> in both cases this change fixes the problem.
Correction: Debian jessie does not have this problem since it doesn't
have the systemd init files.
On Wed, 13 Jul 2016, Emilio Pozuelo Monfort wrote:
> Great. We can handle that for Stretch. You can send a ping to the bug reports
> saying that these are going to be RC for Stretch and that you will bump them
> after a week, and then do that.
Hi. The pings have been sent. Bugs of type "pending u
On Sun, Jul 10, 2016 at 01:04:13PM +0200, Felix Salfelder wrote:
> if that's correct, we shouldn't link libtrilinos_teuchoscore.so to a
> particular revision of libbfd-2.26-system.so. how would that be
> possible?
>
> otoh, if libbfd-2.26.1-system.so
> - is meant to replace libbfd-2.26-system.so,
Package: tarantool
Version: 1.6.7.588.g76bbd9c-1+b1
Severity: grave
/usr/bin/tarantool currently links libbfd dynamically. Since binutils
2.26.1, that library went away but lush's dependency is still satisfied
resulting in a broken binary. Dynamically linking libbfd is not allowed
(see package des
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Control: severity -1 grave
On Wed, Jul 13, 2016 at 04:49:40PM +0200, Yuri D'Elia wrote:
> Seems like tulip depends on libbfd-2.26-system.so, but only
> libbfd-2.26-system.so.1 is available on my system.
Linking libbfd dynamically is explicitly disallowed (see package
description of binutils-dev)
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
El dj 14 de 07 de 2016 a les 07:40 +0100, Adam D. Barratt va escriure:
> For avoidance of doubt, "this user" appears to be you. I'm not sure
> why you didn't just say that.
"This user" is me, Javier Serrano Polo. I was abstracting the problem
from the specific user (me).
El dj 14 de 07 de 2016 a
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Package: lush
Version: 1.2.1-9+cvs20110227+nmu1+b4
Severity: grave
/usr/bin/lush currently links libbfd dynamically. Since binutils 2.26.1,
that library went away but lush's dependency is still satisfied
resulting in a broken binary. Dynamically linking libbfd is not allowed
(see package descripti
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
Greetings.
I have the ok from the Release Managers to consider this issue as RC
for stretch. I'm going to wait at least one week before raising
this to "serious".
If you need help to fix this bug, please tag it as "help".
Thanks.
1 - 100 of 560 matches
Mail list logo
