Hi Sebastian,
On 04.11.2015 21:20, Sebastian Dröge wrote:
> And also forwarded these upstream for review now, thanks again :) I
> hope I find some time to review them myself soonish, but otherwise I'm
> sure someone else will do it soon
What is the status of this?
The next version of FFmpeg is
Package: qt5-default
Version: 5.5.1+dfsg-10
Severity: minor
Dear Maintainer,
the description points to [1] which returns 404. Working URL is [2].
Cheers, sur5r
[1] http://pkg-kde.alioth.debian.org/packagingqtstuff.html
[2] http://pkg-kde.alioth.debian.org/packagingqtbasedstuff.html
-- System
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an
Hi Dmitry,
On 08.12.2015 10:05, Dmitry Smirnov wrote:
> tag 803850 pending
> --
>
> We believe that the bug #803850 you reported has been fixed in the Git
> repository. You can see the commit message below and/or inspect the
> commit contents at:
>
>
>
Package: icewm
Version: 1.3.8-2
Severity: normal
Dear Maintainer,
When user enables Help option in the menu in .icewm/preferences, the
window appears with error:
invalid path: /usr/share/doc/icewm-1.3.8/icewm.html
And help is missing.
The correct path should be something like:
Hi Olly,
On 03.11.2015 06:20, Olly Betts wrote:
> I've fixed this upstream (but without assuming that AV_PIX_FMT_RGB24 is
> present, so as not to break builds that currently work).
>
> The ffmpeg2.9 transition doesn't even seem to be listed as "planned"
> yet at
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an
On Thu, Jan 07, 2016 at 09:10:32PM +0100, John Paul Adrian Glaubitz wrote:
> Well, I've been receiving multiple bug reports through various lists in the
> past days from the libpng maintainers which asked people to fix their B-D
> regarding libpng-dev to prepare for libpng1.6 and setting these
Hi Bertrand,
On 28.11.2015 17:08, Andreas Cadhalpun wrote:
> On 20.11.2015 12:39, Debian Bug Tracking System wrote:
>>* Add a patch cherry-picked from upstream to fix FTBFS with FFmpeg 2.9
>> (Closes: #803835).
>
> Unfortunately this patch fixes only one half of the problem
>
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an
Package: src:yubico-piv-tool
Version: 1.0.3-1
Severity: wishlist
Since 1.0.3, upstream has released both the 1.1 series and 1.2
(currently at 1.2.2) -- any chance of getting something a little newer
in the archive? :)
(Docker's support for yubikeys requires at least 1.1.0, which is why
I'm
Hi Elimar,
On 14.11.2015 15:45, Elimar Riesebieter wrote:
> * Andreas Cadhalpun [2015-11-14 15:21 +0100]:
>> I'm done testing, so you can put them offline.
>
> Thanks a lot ;-)
the next version of FFmpeg is planned to be released this month
(and it might be called
Hi Ximin,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
So please upload a fixed version of motion now.
If this bug isn't fixed soon, it will become release critical and
thus the package will either get NMUed or removed from
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an
Package: fail2ban
Version: 0.9.3-1
Severity: minor
The section [roundcube-auth] contains the error for log definition. The line
logpath = logpath = %(roundcube_errors_log)s
should read as
logpath = %(roundcube_errors_log)s
otherwise it triggers an error:
# /usr/bin/fail2ban-client -x start
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an
> "NT" == Niko Tyni writes:
>> perldoc -f scalar makes absolutely no mention of what we see (/) here:
>> $ perl -wle '$h{a}=0; print scalar %h;'
>> 1/8
NT> It doesn't explain what happens when you evaluate an array in scalar
NT> context either, and I don't think it should.
Hi Arian,
> I have mpd set up to use alsa and use my desktop user 'arian'.
> When mpd is started by debian's init script, it is unable to open the alsa
> device:
>
> Jan 07 11:42 : alsa_mixer: Failed to read mixer for 'My ALSA Device': failed
> to attach to default: No such file or directory
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an
I've been experimenting with the source package in unstable. There is
still some security advantages of building the source package such as
unique RANDSTRUCT values not known publicly:
https://github.com/Whonix/grsecurity-installer/issues/1#issuecomment-169819722
Installing the build
On Thu, 2016-01-07 at 20:26 +0100, Dariusz Dwornikowski wrote:
> On 19.11.15 11:58:58, Luca Boccassi wrote:
> > On Wed, 2015-11-18 at 15:21 +0100, Giacomo Boffi wrote:
> > > Package: bumblebee
> > > Version: 3.2.1-10
> > > Severity: important
> > > File: /usr/bin/optirun
> > >
> > > Dear
I still had one machine I didn't update yet.
# ls -l /etc/kbd/
-rw-r--r-- 1 root root 2637 2012-04-29 config
-rw-r--r-- 1 root root 170 2012-04-29 remap
# more /etc/kbd/*|sed '/^#/d;/^$/d'
::
/etc/kbd/config
::
BLANK_TIME=30
BLANK_DPMS=off
POWERDOWN_TIME=30
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an
Hi Gabriele,
On 03.11.2015 18:43, Andreas Cadhalpun wrote:
> On 03.11.2015 00:51, Gabriele Giacone wrote:
>> Thanks for providing patches.
>> Could you please make your changes conditional upon
>> LIBAVCODEC_VERSION_{MAJOR,MINOR} / LIBAVUTIL_VERSION_INT / ... when
>> needed to keep supporting old
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an
Hello,
Pino Toscano, on Thu 07 Jan 2016 19:51:18 +0100, wrote:
> In data sabato 19 dicembre 2015 13:47:41, Jörg Frings-Fürst ha scritto:
> > Since the last update the "KDE-Zugangshilfe" is running every time.
Uh.
> > Shortly after closing the program is running again.
>
> Do you have qt-at-spi
Hi Eugen,
> On 09.11.2015 11:55, Eugen Dedu wrote:
> Thank you for the patch. We hope to upload a new release of opal in
> 2 months (very very approximately), which includes most if not all of
> your changes, so I prefer to wait a bit.
The next version of FFmpeg is planned to be released this
Control: tag -1 fixed-upstream
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
As this is already fixed upstream, it would be great if you
could upload a package with the relevant cherry-picked patches.
If this bug
Pino Toscano, on Thu 07 Jan 2016 19:44:50 +0100, wrote:
> So I'm setting this bug as wontfix, sorry.
That should be fine, since:
> (I see the latest version of qt-at-spi does not depend on libkdecore5
> anymore, so this bug is left open as reference.)
so qt-at-spi is multiarch-installable. And
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an
On Thu, Dec 10, 2015 at 04:03:21PM +0100, Olivier Bitsch wrote:
> Dear team,
This package isn't team-maintained.
> I'm currently trying to configure NTLM authentication with Apache and
> Winbind, unfortunately, the system is quite unstable. I used the same
> setup without any problem with Wheezy
Package: wnpp
Severity: normal
I originally packaged this module as it was being used by one of my
clients in a project, but they've switched to using
libapache2-mod-auth-kerb instead, so I no longer have access to an
environment where I can test the package, which means I can't usefully
maintain
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Why didn't you
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Do you plan an upload soon?
* Is upstream already fixed?
On 08.01.2016 00:55, Olly Betts wrote:
> On Fri, Jan 08, 2016 at 12:48:54AM +0100, Andreas Cadhalpun wrote:
>> As there is now a new upstream version (1.2.24) available,
>> could you please upload it to unstable?
>
> Coincidentally I'm actually just waiting for 1.2.26-1 to build, so
> should be
Control: tags -1 pending
Hi Anton,
thanks for uploading a fixed package.
But since it is stuck in the NEW queue, I would have
appreciated to be informed, when you uploaded it.
Best regards,
Andreas
Hey,
> Yes the path is fully correct.
can you just add some echos in the file INSTALL_PATH . 'program/include/
clisetup.php' , to get an idea what path is taken?
Regards,
sandro
PS: I get like Vincent errors when sending you an email - how the hell you
read these mails ?
On Dec 31, Marco d'Itri wrote:
> a) submit a patch which rips out of debootstrap all the devices.tar.gz
>stuff, or
And here it is.
--
ciao,
Marco
diff --git a/Makefile b/Makefile
index 1020cbc..0bbb2c0 100644
--- a/Makefile
+++ b/Makefile
@@ -2,17 +2,9 @@
VERSION :=
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Why didn't you
On 2016/01/08 00:47, Florian Schlichting wrote:
> I think you need to set
>
> group "audio"
If that solves the problem, then Arian's bug report was wrong.
He said the user is in group "audio". Specifying the group manually
would discard membership in all other
On Thu, 2016-01-07 at 16:43 -0500, Sam Hartman wrote:
> control: -1 severity important
>
> I'm not sure what the best way to avoid freeradius being pulled out of
> jessie is besides dropping the severity.
RC bugs do not cause packages to be removed from a stable release!
Anyway, this bug is no
On 09.11.2015 19:44, Jean-Baptiste Kempf wrote:
> On 09 Nov, Andreas Cadhalpun wrote :
>>> So, if you want a recent ffmpeg with VLC, you need 3.0.
>>
>> Is there an estimated release date for VLC 3.0?
>
> In a month or two, for freeze.
The next version of FFmpeg is planned to be released this
Package: gwenview
Version: 4:15.08.3-1
Followup-For: Bug #799157
Just to confirm, this still exists on 4:15.08.3-1. Non-KDE printing works
fine.
Furthermore, it looks like simultaneously with vanishing printing options,
the landscape option stopped working, too: it works on jessie's version
Hi Chris,
On 05.11.2015 11:44, Chris Boot wrote:
> On 02/11/15 21:21, Andreas Cadhalpun wrote:
> Thanks very much for the patch. I've pulled it into my master packaging
> branch and I'll push a release in a week or two once I have tested this
> some more.
Two month rather than two weeks later...
On Fri, Jan 08, 2016 at 12:48:54AM +0100, Andreas Cadhalpun wrote:
> As there is now a new upstream version (1.2.24) available,
> could you please upload it to unstable?
Coincidentally I'm actually just waiting for 1.2.26-1 to build, so
should be fixed in unstable very soon.
Cheers,
Olly
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package emacs-async.
* Package name: emacs-async
Version : 1.6
Upstream Author : John Wiegley
* URL : https://github.com/jwiegley/emacs-async
*
On Mon, 2016-01-04 at 10:08 +0100, Debian stuff wrote:
> Happy new year, maintainer.
>
>
> > When the last upload was made to the repos I had no issues with the
> > latest drivers and the latest Bumblebee on Jessie. I wonder if it
> > might be due to an incompatibility with the newer version of
On Fri, 2016-01-01 at 21:17 +, Nohus wrote:
> Luca Boccassi :
> > Meanwhile, could you please send all the nvidia-related details of
> > your system by running:
> >
> > reportbug --template nvidia-driver
> >
> > and attaching the result?
>
> Sure, here is the
Package: release-notes
I'd like to add a note in the jessie release-notes that the
armel/iop32x subarch was removed.
I have two questions:
1) Do you think this paragraph should be limited to armel or not?
2) Is there a tag to use for subarchitectures?
Any other comments?
Index:
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an
Hi Johannes,
On 05.11.2015 11:30, Johannes Schauer wrote:
> I already forwarded this upstream as https://github.com/vcmi/vcmi/pull/135
The next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since this is fixed upstream since a while it would
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an
Thanks!
it was fixed upstream awhile back in
d278fbca306d8bdcc5b3ffe34b1cfc3cd8963f0b
I guess we should cook up a new upstream release (0.9.4) and update package in
Debian
Cheers
On Fri, 08 Jan 2016, Dmitry Katsubo wrote:
> Package: fail2ban
> Version: 0.9.3-1
> Severity: minor
> The section
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an
On Sep 17, Marco d'Itri wrote:
> > After I switched from libnss-ldap to libnss-ldapd I noticed that at
> > every login proftpd requests the whole content of the passwd database
> > (i.e. like running "getent passwd).
> > This is evident from the nslcd debugging log
Package: wnpp
Severity: wishlist
Owner: Kunal Mehta
* Package name: mediawiki
Version : 1.25.5
Upstream Author : MediaWiki developers
* URL : https://www.mediawiki.org/
* License : GPL-2.0+
Programming
Hi Berto,
On 04.11.2015 08:59, Alberto Garcia wrote:
> On Tue, Nov 03, 2015 at 07:40:13PM +0100, Andreas Cadhalpun wrote:
>>> Do you want me to upload the new fuse package now, or shall I
>>> better wait until the new FFMPEG reaches Debian?
>>
>> It would be good if most the packages were ready
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an
[Jörg Frings-Fürst]
> Package: wnpp
> Severity: wishlist
>
> Package name: python-instagram
I would very much like to see this module in Debian, as it is a dependency
of the creepy package I maintain. Is there anything I can do to help? I
noticed the request for sponsoring in #770149,
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an
Hi Tzafrir,
On 05.11.2015 07:40, Tzafrir Cohen wrote:
> Thanks. Merged in git and seems to work fine at first glance.
The next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
So it would be good, if you could upload a fixed version.
If this
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an
Control: notfound -1 1.1.7-9
Control: found -1 3:1.1.7-9
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past two month
I'm wondering what the status of this bug is:
*
Package: wnpp
Severity: wishlist
Owner: Sean Whitton
* Package name: helm
Version : 1.9.1
Upstream Author : Thierry Volpiatto
* URL : https://emacs-helm.github.io/helm/
* License : GPL-3
Programming
Dear Maintainer,
the next version of FFmpeg is planned to be released this month
(and it might be called 3.0 instead of 2.9).
Since I haven't heard back from you during the past month
I'm wondering what the status of this bug is:
* Are you aware of the patch I provided?
* Do you plan an upload
Package: wnpp
Severity: wishlist
Owner: Sean Whitton
* Package name: perspective-el
Version : 1.12
Upstream Author : Natalie Weizenbaum
* URL : https://github.com/nex3/perspective-el
* License : GPL-3
Programming
On Mon, Dec 28, 2015 at 11:27:28AM +0100, Ph. Marek wrote:
> During a run with my automated test suite for FSVS I noticed that some
> things that previously worked do not any more.
> I can't really give a hard range of SVN versions, but I guess 2 or 3 years
> ago that wasn't a problem yet ;/
Package: sponsorship-requests
Severity: wishlist
Dear mentors,
I am looking for a sponsor for my package perspective-el.
* Package name: perspective-el
Version : 1.12
Upstream Author : Natalie Weizenbaum
* URL :
Package: gettext-lint
Version: 0.4-2.1
Severity: normal
Control: user check-all-the-thi...@packages.debian.org
Control: usertags -1 + false-positive
Control: affects -1 + check-all-the-things
Control: thanks
Dear Maintainer,
currently, there is no sanity check against the list of available
Hi Dimitri,
On Sat, Jul 11, 2015 at 08:27:30PM +0100, Dimitri John Ledkov wrote:
> I believe remaining fixes can be cherrypicked from upstream.
> Specifically for clang / c++11 support the remaining bug of code is
> explicitly converted into bool:
>
>
Control: tags 648126 + patch
Control: tags 648126 + pending
Dear maintainer,
I've prepared an NMU for simage (versioned as 1.7.1~2c958a6.dfsg-2.1) and
uploaded it to DELAYED/7. Please feel free to tell me if I
should delay it longer.
Regards.
diff -Nru simage-1.7.1~2c958a6.dfsg/debian/changelog
Hello,
as far as I can tell is that if running strace, it seems to looking for an
icon and fails, and then looks for the intro.bmp and it fails with this
error.
Other SDL programs seems to run ok (frozen bubble for instance...)
On Thu, Jan 7, 2016 at 8:47 AM, Markus Koschany
Control: repopen -1
Control: retitle -1 "Please update B-D to libpng-dev"
On Tue, 5 Jan 2016 15:25:48 +0100 =?UTF-8?Q?Moritz_M=C3=BChlenhoff?= wrote:
> Version: 3.11.0+dfsg-1
>
> On Tue, Jan 05, 2016 at 01:35:59AM +0100, Tobias Frost wrote:
> > Am Dienstag, den 05.01.2016, 00:54 +0100 schrieb
Control: noowner -1
Hi, does anybody has any hint about ublock integration in Debian?
I personally don't use chromium too much, and I don't know about the quality of
the software
too much, not being a chromium team member and packager.
So I'll leave this RFS to somebody with more knowledge
Only while llvm-3.5 stays in sid, and even for that case it's not a good
policy. We can do it for the good of the users for sometime. Maybe gambas
developer will update the library in the meantime. If you agree I can do
it, if not the only solution is disabling llvm component from being built
in
Control: retitle -1 Block borgbackup migration to stable for now
Hello everyone,
I have thought a lot about this situation and I still think that
blocking migration to stable *for now* is the sensible solution. I do
not want to remove borgbackup from Debian, or keep this blocker alive
Package: unison
Version: 2.48.3-1
Severity: important
Hello,
thank you for maintaining unison.
It seems unison is not able to sync to a jessie system anymore:
$ unison irclogs
Contacting server...
Fatal error: Received unexpected header from the server:
expected "Unison 2.48\n"
Package: rsyslog
Version: 8.4.2-1+deb8u2
Severity: normal
Dear Maintainer,
the gnome-session spams /var/log/{syslog,user.log,messages}. As a workaround I
tried ratelimiting by specifying "$RepeatedMsgContainsOriginalMsg on" in
/etc/rsyslog.d/local.conf. It had no effect.
I tried discarding a
Hello Craig Small.
Thanks for taking this on and drafting a proposal... I'll throw
in some of my own ideas below in case they're helpful so feel
free to leave out or reword things as you see fit.
Fwiw, in case you want to avoid any potential people out there
who might think you're just beating a
Am 07.01.2016 um 09:05 schrieb Gianluca Renzi:
> Hello,
> as far as I can tell is that if running strace, it seems to looking for
> an icon and fails, and then looks for the intro.bmp and it fails with
> this error.
Are you sure that /usr/games is in your PATH? What happens if you change
to
On my ubuntu distribution at work:
apt-file search alienblasterintro.bmp
alienblaster-data:
/usr/share/games/alienblaster/images/alienblasterintro.bmp
So it's seems on debian sid/stretch the alienblaster-data is not installed
as dependency. I will check on launch break @ home
.
On Thu, Jan 7,
Package: letsencrypt
Version: 0.1.1-3
Severity: normal
Dear Maintainer,
letsencrypt gives me a hard time when being run as unprivileged user.
i understand that quite a number of operations require supercow powers, but the
error messages are rather cryptic (being generic python exceptions):
Hi raju,
On Thu, Jan 07, 2016 at 01:27:50AM -0500, Kamaraju Kusumanchi wrote:
>
> This is Kamaraju S. Kusumanchi, the author mentioned in this bug report.
> Sorry about the broken link.
>
> I was a graduate student at Cornell University when I wrote that FAQ. The
> website
On Fri, Jan 01, 2016 at 06:26:22PM +, Adam D. Barratt wrote:
Hi Adam,
> Please go ahead.
Uploaded.
Regards,
S.
Hi,
>Only while llvm-3.5 stays in sid, and even for that case it's not a good
>policy. We can do it for the good of the users for sometime. Maybe gambas
>developer will >update the library in the meantime. If you agree I can do it,
>if not the only solution is disabling llvm component from
Source: ben
Version: 0.7.0
The documentation as well the templates contain http links. Those should
use
https instead of http.
PS: Another remark regarding bluewave.h -- I did not evaluate if this
license is compatible with the GPL-3.. Another thing to check with
debian-legal.
Hi Robert,
(btw, please configure your MTA to wrap your mails)
On Tue, 05 Jan 2016 18:08:55 -0500 Robert James Clay
wrote:
>
Hi Robert,
(btw, please configure your MTA to wrap your mails)
On Tue, 05 Jan 2016 18:08:55 -0500 Robert James Clay
wrote:
> On Tuesday, January 05, 2016 04:27:48 AM Tobias Frost wrote:
> > - Is the patch forwarded to upstream?
>
>The non vendor specific parts of it, you
Hi,
On 6 January 2016 at 18:52, wrote:
> Package: libboost-all-dev
> Version: 1.58.0.1
> Severity: important
>
> Dear Maintainer,
>
> linking programs against latest version (1.58.0.1) fails with similar
> messages:
> -
> /bin/sh
Hi Harald,
On Wed, Jan 06, 2016 at 09:22:46PM +0100, Harald Dunkel wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> On 01/02/16 16:43, Ricardo Mones wrote:
> >
> > Which spam plugin are you using?
> >
>
> Bogofilter.
Messages are not deleted by bogofilter using default
1 - 100 of 281 matches
Mail list logo