Processing commands for cont...@bugs.debian.org:
> severity 704879 serious
Bug #704879 [findutils] findutils: Regression: dh_shlibdeps (find -perm +111)
no more works with findutils 4.5.11-1 (compared to 4.4.2-5)
Severity set to 'serious' from 'important'
> thanks
Stopping processing here.
Pleas
On Sat, 20 Apr 2013 01:35, clo...@igalia.com said:
> I think it would be a good idea to add this feature to libgcrypt.
See attached patch against master. It is not tested, though. You may
backport it to 1.5 and use it like this:
#if GCRYPT_VERSION_NUMBER > 0x010502
gcry_control (GCRYCTL_DI
On 20/04/13 00:08, Werner Koch wrote:
>> At least, I think that you should consider adding a new flag to
>> > libgcrypt that allows the application/library developer to complete
>> > disable the dropping privileges feature. Perhaps something like:
> That was my suggesttion. Shall we go for that?
>
On Fri, 19 Apr 2013 22:37, clo...@igalia.com said:
> They just call a standard function (ex: getpwent). This function may or
> may not chain with libgcrypt depending on how the system libraries are
> compiled and how the system is configured.
Okay, then it is the fault of the libnss code to allow
On 04/19/2013 10:38 PM, Svante Signell wrote:
> Package: gdm3
> Version: 3.4.1-8, 3.4.1-7
> Severity: Serious
>
> Hi,
>
> After having classic running for a long time, suddenly when upgrading to
> 3.4.1-8 (same problem in -7?, haven't rebooted for some time), when
> rebooting gnome default is bac
http://bugs.debian.org/705452 > is a similar issue triggering "E:
Couldn't configure pre-depend xml-core for docbook-xml, probably a
dependency cycle" from APT when upgrading KDE. The trigger was a RC fix
for #678902 in sgml-base. The issue is now reassigned to 'general', and
I am not quite sure
On 19/04/13 20:56, Werner Koch wrote:
> Having said this, I don't see a reason why not to put the
> responsibilities in the hands of the suid program authors. They anyway
> wake up every night due to a nightmare telling them to check this and
> that and - oh - I am using a library I didn't checked
Package: gdm3
Version: 3.4.1-8, 3.4.1-7
Severity: Serious
Hi,
After having classic running for a long time, suddenly when upgrading to
3.4.1-8 (same problem in -7?, haven't rebooted for some time), when
rebooting gnome default is back. This is NOT ACCEPTABLE, I hate the
default. (and still a debi
On Fri, 19 Apr 2013 19:25, jcris...@debian.org said:
> If that "solution" is to have sudo itself call into libgcrypt, that
> doesn't sound like a solution at all. sudo doesn't know how libldap
> implements crypto, it doesn't care, and it shouldn't have to care IMO.
Uh-oh. A suid program that do
On Sun, Apr 07, 2013 at 02:31:06PM +0200, Niels Thykier wrote:
> user release.debian@packages.debian.org
> usertags 677795 + wheezy-will-remove
> thanks
>
> On 2013-04-02 13:13, Didier Raboud wrote:
> > Package: release.debian.org
> > Severity: normal
> > User: release.debian@packages.debi
On Fri, 19 Apr 2013 20:15, clo...@igalia.com said:
> What about removing this feature of dropping privileges from libgcrypt
> and adding it to gpg itself? gpg could check if is run suid and drop
I already explained that this is not possible because we can't know the
applications which rely on thi
On 19/04/13 10:22, Werner Koch wrote:
> While we are in the business of refreshing our URL memories, let me
> follow up with:
>
> http://thread.gmane.org/gmane.comp.encryption.gpg.libgcrypt.devel/2198
>
> Florian Weimer comes to the same conclusion regarding the PAM
> architecture but also asked
Processing commands for cont...@bugs.debian.org:
> reassign 705751 ruby-paint 0.8.5-1
Bug #705751 [lolcat] no-rubygems patch breaks lolcat on ruby1.8
Bug reassigned from package 'lolcat' to 'ruby-paint'.
No longer marked as found in versions lolcat/42.0.99-1.
Ignoring request to alter fixed versio
reassign 705751 ruby-paint 0.8.5-1
tags 705751 - help + patch
forwarded 705751 https://github.com/janlelis/paint/issues/9
retitle 705751
thanks
> When /usr/bin/ruby is ruby 1.8 the program fails:
>
> $ lolcat /proc/cpuinfo
> /usr/lib/ruby/vendor_ruby/paint/util.rb:37:in `detect_mode': uninitialize
On 19/04/13 19:25, Julien Cristau wrote:
> On Fri, Apr 19, 2013 at 19:07:02 +0200, Werner Koch wrote:
>
>> What about my suggestion on how to solve the problem?
>>
> If that "solution" is to have sudo itself call into libgcrypt, that
> doesn't sound like a solution at all. sudo doesn't know how l
Processing commands for cont...@bugs.debian.org:
> tags 705751 + help
Bug #705751 [lolcat] Doesn't work with ruby 1.8
Added tag(s) help.
> retitle 705751 no-rubygems patch breaks lolcat on ruby1.8
Bug #705751 [lolcat] Doesn't work with ruby 1.8
Changed Bug title to 'no-rubygems patch breaks lolcat
tags 705751 + help
retitle 705751 no-rubygems patch breaks lolcat on ruby1.8
owner 705751 !
thanks
hello andrey, thanks for your bug report.
> When /usr/bin/ruby is ruby 1.8 the program fails:
>
> $ lolcat /proc/cpuinfo
> /usr/lib/ruby/vendor_ruby/paint/util.rb:37:in `detect_mode': uninitialized
Your message dated Fri, 19 Apr 2013 17:32:42 +
with message-id
and subject line Bug#641811: fixed in openvpn-auth-ldap 2.0.3-5.1
has caused the Debian Bug report #641811,
regarding Segmentation fault at startup
to be marked as done.
This means that you claim that the problem has been dealt wi
Your message dated Fri, 19 Apr 2013 17:32:42 +
with message-id
and subject line Bug#641811: fixed in openvpn-auth-ldap 2.0.3-5.1
has caused the Debian Bug report #641811,
regarding openvpn-auth-ldap: segmentation fault
to be marked as done.
This means that you claim that the problem has been
Processing control commands:
> severity -1 important
Bug #704422 [dovecot-solr] dovecot-solr: Segfault using dovecot-solr plug-in
Severity set to 'important' from 'grave'
--
704422: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=704422
Debian Bug Tracking System
Contact ow...@bugs.debian.org w
Control: severity -1 important
N@bugs doesn't reach the submitter by default; you need to
explicitly CC them. I've done so on this message, so have left the full
quote in place.
On Fri, 2013-04-19 at 18:09 +0100, Steven Ayre wrote:
> This appears to be caused by a configuration error.
>
> Yo
On Fri, Apr 19, 2013 at 19:07:02 +0200, Werner Koch wrote:
> What about my suggestion on how to solve the problem?
>
If that "solution" is to have sudo itself call into libgcrypt, that
doesn't sound like a solution at all. sudo doesn't know how libldap
implements crypto, it doesn't care, and it
Processing commands for cont...@bugs.debian.org:
> tags 641811 + patch
Bug #641811 [openvpn-auth-ldap] openvpn-auth-ldap: segmentation fault
Bug #681930 [openvpn-auth-ldap] Segmentation fault at startup
Added tag(s) patch.
Added tag(s) patch.
> tags 641811 + pending
Bug #641811 [openvpn-auth-ldap]
On 04/18/2013 08:34 PM, Jon Dowland wrote:
> Hi,
>
> I saw this bug and I got a bit concerned.
We used to use python ObjConfig, but it's not compatible with Openstack
.ini files...
> I'm a likely user of the
> openstack packages in Debian — well I/we could be, if they fit our
> needs — but I'm r
tags 641811 + patch
tags 641811 + pending
thanks
Dear maintainer,
I've prepared an NMU for openvpn-auth-ldap (versioned as 2.0.3-5.1) and
uploaded it. NMU diff attached.
Cheers,
Julien
diff -Nru openvpn-auth-ldap-2.0.3/debian/changelog openvpn-auth-ldap-2.0.3/debian/changelog
--- openvpn-auth-l
On Fri, 19 Apr 2013 18:54, clo...@igalia.com said:
> I couldn't find anything relevant on the archives.
Next step would be to check the repos and all packages using Libgcrypt.
> Saying that there is a good reason for this commit to be there and at
> the same time saying that such good reason is
This appears to be caused by a configuration error.
Your example sets fts_squat, but not fts_solr.
Compare yours:
plugin {
fts = solr
fts_squat = url=http://localhost:8080/solr/
}
To the example in the documentation http://wiki.dovecot.org/Plugins/FTS/Solr:
plugin {
In fact fuser is 0x0. Set is an offset in the fuser struct.
On 19/04/13 10:22, Werner Koch wrote:
> On Fri, 19 Apr 2013 02:52, mgilb...@debian.org said:
>>> 1.a) Patch libgcrypt to revert commit
>>> d769529a71ccda4e833f919f3c5693d25b005ff0
>>> >>
>>> >> Urgs. That is a short sighted fix.
>> >
>> > That seems to be the solution the rest of th
Reproduced as described. Backtrace (some values optimised out):
(gdb) bt
#0 fts_backend_solr_init (_backend=,
error_r=) at fts-backend-solr.c:160
#1 0x7fac0530af52 in fts_backend_init
(backend_name=backend_name@entry=0x7fac07b50e10 "solr",
ns=0x7fac07b4afe0, error_r=error_r@entry=0x7fffe7ca5
Hello!
You wrote:
> It has been closed by Felix Geyer .
I can confirm that the bug is fixed.
Next to XFS, also JFS was affected.
best regards
Markus
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.o
On Thu, Apr 18, 2013 at 14:58:21 +1000, Stuart Prescott wrote:
> I don't doubt that there is a smaller subset of packages that can reproduce
> this failure, especially since installing those two drags in several hundred
> others -- that was just as far as I had managed to get in narrowing it dow
Your message dated Fri, 19 Apr 2013 18:19:59 +0200
with message-id <20130419161959.gh5...@radis.cristau.org>
and subject line Re: Bug#705649: Document solutions for re-enabling static mtab
has caused the Debian Bug report #705649,
regarding document solutions for re-enabling static mtab
to be marke
Processing commands for cont...@bugs.debian.org:
> tags 705649 + wheezy
Bug #705649 [release-notes] document solutions for re-enabling static mtab
Added tag(s) wheezy.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
705649: http://bugs.debian.org/cgi-bin/bugreport
On Tue, Apr 9, 2013 at 18:17:00 +0200, David Kalnischkies wrote:
> On Thu, Apr 4, 2013 at 10:46 PM, Julien Cristau wrote:
> > On Sun, Mar 24, 2013 at 18:17:46 +0100, David Kalnischkies wrote:
> >
> >> Pictures^Wdpkg-status files or it didn't happen, as I said multiple times
> >> now.
> >>
> > Y
Your message dated Fri, 19 Apr 2013 15:32:59 +
with message-id
and subject line Bug#705746: fixed in cp2k 2.2.426-8
has caused the Debian Bug report #705746,
regarding cp2k: wrong basis set definition for 6-31++G** basis sets
to be marked as done.
This means that you claim that the problem ha
Hi all,
Le jeudi, 18 avril 2013 12.55:09, Steven Chamberlain a écrit :
> On 09/04/13 19:15, Didier 'OdyX' Raboud wrote:
> > - gdm3 … doesn't finish loading. It fullscreen-says "Oops, an error
> > occured". - lightdm + "Gnome": same.
> > - lightdm + "Gnome classic": same.
>
> Many thanks for testi
Your message dated Fri, 19 Apr 2013 15:03:59 +
with message-id
and subject line Bug#705753: fixed in pocketsphinx 0.8-2
has caused the Debian Bug report #705753,
regarding pocketsphinx: FTBFS: test_gst fails
to be marked as done.
This means that you claim that the problem has been dealt with.
Source: rapicorn
Version: 13.03.0~ds0-1
Severity: serious
Justification: fails to build from source
Builds of rapicorn for non-x86 processors fail because it insists on
using the x86 lfence opcode:
../rcore/threadlib.hh: Assembler messages:
../rcore/threadlib.hh:18: Error: Unrecognized opcode
Source: rapicorn
Version: 13.03.0~ds0-1
Severity: serious
Justification: fails to build from source
Builds of rapicorn on 32-bit systems fail because it expects uint32_t
and size_t to be distinct types:
aida.hh:400:15: error: 'void
Rapicorn1303::Aida::FieldBuffer::operator<<=(uint32_t)' cannot
Source: rapicorn
Version: 13.03.0~ds0-1
Severity: serious
Justification: fails to build from source
Builds of rapicorn on kFreeBSD and the Hurd fail because they lack
eventfd and (at least in the case of kFreeBSD) use a port of legacy
Linuxthreads rather than NPTL. Depending on how fundamentally
Source: pocketsphinx
Version: 0.8-1
Severity: serious
Justification: fails to build from source
Automated builds of pocketsphinx have been failing with test_gst errors:
(test_gst:N): GStreamer-CRITICAL **: gst_element_link_pads_filtered:
assertion `GST_IS_ELEMENT (dest)' failed
(test_
Package: lolcat
Version: 42.0.99-1
Severity: serious
When /usr/bin/ruby is ruby 1.8 the program fails:
$ lolcat /proc/cpuinfo
/usr/lib/ruby/vendor_ruby/paint/util.rb:37:in `detect_mode': uninitialized
constant Module::RbConfig (NameError)
from /usr/lib/ruby/vendor_ruby/paint.rb:164:in `mo
Processing commands for cont...@bugs.debian.org:
> reassign 705746 cp2k-data
Bug #705746 [cp2k] cp2k: wrong basis set definition for 6-31++G** basis sets
Bug reassigned from package 'cp2k' to 'cp2k-data'.
No longer marked as found in versions cp2k/2.2.426-1.
Ignoring request to alter fixed version
Processing commands for cont...@bugs.debian.org:
> tags 705746 + pending
Bug #705746 [cp2k] cp2k: wrong basis set definition for 6-31++G** basis sets
Added tag(s) pending.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
705746: http://bugs.debian.org/cgi-bin/bugre
Package: cp2k
Version: 2.2.426-1
Severity: serious
Tags: patch
A problem has been been found today with the 6-31++G** version of the
standard EMSL basis sets, which will lead to wrong results.
The problem has been fixed in upstream revision 12850:
http://sourceforge.net/p/cp2k/code/12850/
Mich
Hi Aron
On Fri, Apr 19, 2013 at 05:29:59PM +0800, Aron Xu wrote:
> found 705722 2.9.0+dfsg1-4
> thanks
>
> I think this bug only exist from 2.9.0? xmlBufGetInputBase() does not
> exist before that.
Thanks a lot for your quick checking and marking version accordingly.
(I did not check the versio
Hi,
It's too late for wheezy, but I will cut a new upstream version
from svn (just one.last.commit I'd like to get in), it's been
pretty stable for a while, must be about time to do it. :)
I believe the patches for 2.11 are too much, most of the recent
development has been me putting out small fi
Your message dated Fri, 19 Apr 2013 09:48:07 +
with message-id
and subject line Bug#704717: fixed in pcp 3.7.2
has caused the Debian Bug report #704717,
regarding pcp: FTBFS - missing build-dep on python-dev
to be marked as done.
This means that you claim that the problem has been dealt with.
On 19 April 2013 09:13, jari wrote:
> Dear maintainer,
>
> I have some free time and I'm offering help.
>
> Here is the NMU diff[1] to fix SERIOUS bug #680856 for the release.
>
If the fix is correct and you have tested it, and can take care of
fixing fallout, then no need to "NMU" it.
Just do a
On Thu, Apr 18, 2013 at 09:24:30AM +0200, Helmut Grohne wrote:
> I believe that we will need a deeper look at #482140. At the moment I do
> not fully understand that issue and its implications. The root cause
> appears to be lenny's update-xmlcatalog being in a temporarily
> inconsistent state due
Processing commands for cont...@bugs.debian.org:
> found 705722 2.9.0+dfsg1-4
Bug #705722 [libxml2] libxml2: CVE-2013-1969
Marked as found in versions libxml2/2.9.0+dfsg1-4.
> thanks
Stopping processing here.
Please contact me if you need assistance.
--
705722: http://bugs.debian.org/cgi-bin/bug
found 705722 2.9.0+dfsg1-4
thanks
I think this bug only exist from 2.9.0? xmlBufGetInputBase() does not
exist before that.
On Fri, Apr 19, 2013 at 12:51 PM, Salvatore Bonaccorso
wrote:
> Package: libxml2
> Severity: grave
> Tags: security patch upstream
>
> Hi,
>
> the following vulnerability wa
On 2013-04-18 09:24, Helmut Grohne wrote:
> Andreas, could you test those debdiffs with your piuparts setup? I have
I'll be offline over the weekend and look at this on Monday
> a few more requests though:
> * Can you ensure to pass -o Debug::pkgPackageManager=true to apt?
no problem
> * Can yo
Werner Koch wrote:
On Fri, 19 Apr 2013 09:22, h...@symas.com said:
Frankly, speaking for the OpenLDAP Project, what we want is to delete
all support for GnuTLS. It is, like Mozilla NSS, a poorly designed API
Split OpenLDAP into a daemon and a simple access library and things
would be more robu
Attaching the patch for convenience.
I'd be happy to step up and NMU this for Wheezy to get it fixed as soon
as possible. I will be preparing the NMU anyway and attach the debdiff
here for review.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaub...@debian.org
`. `
On Fri, 19 Apr 2013 09:22, h...@symas.com said:
> Excuse me? By what measure is this correct? Certainly not by any
> published official documentation.
The correct solution is to let the application handle this. But I don't
want to repeat this now. "most correct" here means, it is not worse
than
On Fri, 19 Apr 2013 02:52, mgilb...@debian.org said:
>>> 1.a) Patch libgcrypt to revert commit
>>> d769529a71ccda4e833f919f3c5693d25b005ff0
>>
>> Urgs. That is a short sighted fix.
>
> That seems to be the solution the rest of the open source community is
> converging toward. Short sighted i
On Fri, Apr 19, 2013 at 11:13:02 +0300, jari wrote:
> Dear maintainer,
>
> I have some free time and I'm offering help.
>
> Here is the NMU diff[1] to fix SERIOUS bug #680856 for the release.
>
> Please let me know if it is ok to proceed with the NMU. Feel free to
> contact if you have any ques
Hi,
there’s currently a discussion on the pcc upstream mailing list
about having a shippable version of pcc that actually works on
GNU/Linux. There currently is none (except severely older versions
that have known deficiencies on amd64), and the ETA is rather high.
Since the M-A changes needed ar
Dear maintainer,
I have some free time and I'm offering help.
Here is the NMU diff[1] to fix SERIOUS bug #680856 for the release.
Please let me know if it is ok to proceed with the NMU. Feel free to
contact if you have any questions.
Thank you for maintaining the package,
Jari Aalto
[1] http:/
Werner Koch wrote:
On Thu, 18 Apr 2013 20:40, clo...@igalia.com said:
I see two options to get this fixed for Wheezy:
[Option 1] -- Do the same that Ubuntu did. That is:
1.a) Patch libgcrypt to revert commit
d769529a71ccda4e833f919f3c5693d25b005ff0
Urgs. That is a short sighted fix.
Am Donnerstag, den 18.04.2013, 21:30 +0300 schrieb Tzafrir Cohen:
> One test if you don't mind: merely rebuilding it vs. Asterisk -3 does
> not fix the issue, right?
>
Right, it does not.
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Troub
63 matches
Mail list logo
