Re: Bug#503712: the gs-common problem

2009-01-06 Thread Cyril Brulebois
Hello,

Thomas Viehmann t...@beamnet.de (06/01/2009):
 Please allow me the liberty of proposing the attached NMU for fixing
 #503712 (and opportunistically #510691 now that we know, but I've left
 all other dependency stuff out).
 
 If considered desirable, it would be nice if someone could sponsor
 this. Packages are available[1].

on its way, thanks again!

Mraw,
KiBi.


signature.asc
Description: Digital signature


Re: please unblock libsemanage/2.0.25-3

2009-01-06 Thread Neil McGovern
On Mon, Jan 05, 2009 at 06:57:57PM -0600, Manoj Srivastava wrote:
 Hi,
 
 This release fixes a RC bug.
 

Despite the other unrelated changes that weren't mentioned in the
changelog, unblocked.

Neil
-- 
dkscully doesn't the world come to an end if iDunno shaves?
Maulkin That's how the dinosaurs died then...
iDunno and why the dodo was made extinct, the last known habitat for them
was my beard... poor bastards didn't stand a chance.


signature.asc
Description: Digital signature


Re: Bug#503712: the gs-common problem

2009-01-06 Thread Cyril Brulebois
Cyril Brulebois k...@debian.org (06/01/2009):
 Thomas Viehmann t...@beamnet.de (06/01/2009):
  Please allow me the liberty of proposing the attached NMU for fixing
  #503712 (and opportunistically #510691 now that we know, but I've left
  all other dependency stuff out).
  
  If considered desirable, it would be nice if someone could sponsor
  this. Packages are available[1].
 
 on its way, thanks again!

If someone else finds it strange to have the following wdiff between the
version currently in testing and the one uploaded to t-p-u: “libcomerr2
(= [-1.33-3),-] {+1.01),+}”, see e2fsprogs' “Add dpkg-gensymbols
support to track ABI changes to the libraries” in 1.41.1-1 or “Add more
historical information to the debian/*.symbol files” in 1.41.1-3.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Please unblock samba 2:3.2.5-3

2009-01-06 Thread Christian Perrier
That new version was uploaded to fix a security issue that was
unveiled yesterday and fixed in upstream's 3.2.7.

The applied patch, for the security issue, is attached to this mail.

I also fixed two other issues (one spurious file noticed by Dato in
last upload and a documentation-related fix).

Changelog:

samba (2:3.2.5-3) unstable; urgency=high

  * Security update
  * Fix Potential access to / in setups with registry shares enabled
This fixes CVE-2009-0022, backported from 3.2.7
  * Fix links in HTML documentation index file.
Closes: #508388
  * Drop spurious docs-xml/smbdotconf/parameters.global.xml.new
file in the diff. Thanks to the release managers for spotting it

 -- Christian Perrier bubu...@debian.org  Sun, 21 Dec 2008 08:09:31 +0100


Goal: Fix Potential access to / in setups with registry shares enabled

Fixes: CVE-2009-0022

Status wrt upstream: Fixed in 3.2.7

Author: Michael Adam ob...@samba.org

Note: 

Index: samba-3.2.5/source/smbd/service.c
===
--- samba-3.2.5.orig/source/smbd/service.c
+++ samba-3.2.5/source/smbd/service.c
@@ -235,6 +235,10 @@
 		return -1;
 	}
 
+	if ((servicename == NULL) || (*servicename == '\0')) {
+		return -1;
+	}
+
 	if (strequal(servicename, GLOBAL_NAME)) {
 		return -2;
 	}


signature.asc
Description: Digital signature


Re: Please unblock samba 2:3.2.5-3

2009-01-06 Thread Adeodato Simó
* Christian Perrier [Tue, 06 Jan 2009 06:59:49 +0100]:

 That new version was uploaded to fix a security issue that was
 unveiled yesterday and fixed in upstream's 3.2.7.

 The applied patch, for the security issue, is attached to this mail.

 I also fixed two other issues (one spurious file noticed by Dato in
 last upload and a documentation-related fix).

Unblocked.

-- 
Adeodato Simó dato at net.com.org.es
Debian Developer  adeodato at debian.org
 
 Listening to: Vanessa-Mae - I Feel Love


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Re: HPPA and lenny (ruby1.9 build problems)

2009-01-06 Thread Helge Deller
dann frazier wrote:
 On Tue, Jan 06, 2009 at 12:46:34AM +0100, Helge Deller wrote:
 CC: linux-paric mailing list

 Peter Palfrader wrote:
 On Mon, 05 Jan 2009, dann frazier wrote:

 On Tue, Dec 23, 2008 at 11:43:22AM +0100, Helge Deller wrote:
 Peter Palfrader wrote:
 Helge Deller schrieb am Dienstag, dem 23. Dezember 2008:

 Patch in parisc git tree:
 http://git.kernel.org/?p=linux/kernel/git/kyle/parisc-2.6.git;a=commitdiff;h=378fe7c4cc619b561409206605c723c05358edac;hp=6c4dfa8f8bcf032137aacb3640d7dd9d75b2b607
 So just using an SMP kernel should also work?
 Probably yes, since some other developers tried initially to reproduce
 the problem, but they couldn't (as it seems they were running on newer
 SMP machines). But I don't have a SMP server which is why I can't test
 myself...
 Unfortunately, it looks like we're still having problems on the
 buildds w/ 2.6.26 SMP kernels:
   
 http://buildd.debian.org/build.php?pkg=ruby1.9ver=1.9.0.2-9arch=hppafile=log

 The build doesn't take the system down, but does still hang
 indefinitely while running miniruby - though the hang location varies.

 I'll prepare a UP kernel for one of the buildds w/ the
 up-optimization-removal patch just to see if it improves things. I
 don't see why it would, other than it seemed to solve the problem on
 my test box when I first tested the patch.
 It seemed to fix the problem for me as well.
 
 fyi, I tested w/ a 2.6.26 32-bit UP kernel w/ the
 up-optimization-removal patch, and received another hang:
  
 http://buildd.debian.org/fetch.cgi?pkg=ruby1.9;ver=1.9.0.2-9;arch=hppa;stamp=1231212073

Yes, that's the same I can reproduce here as well.
It's AFAICS not the ProtectionID trap kernel bug any longer, which is good :-)

 In principle looking at the logs it looks more like a userspace bugs
 due to threading functions.
 Anyway, I'll try to reproduce it here as well.
 FWIW, I had some additional irq locking code in load_context(), maybe 
 this helps...?
 
 I'd be happy to test it if you can point me to a changeset.

Sorry, nothing yet.
As it does not seem to be related to the Protection ID trap, they are probably
useless anyway.
Overall, this is what I see when running dpkg-buildpackage for ruby1.9:
test_load.rb .
test_exception.rb 
test_thread.rb .
here it hangs

r...@c3000:~/cvs/ruby/ruby1.9-1.9.0.2# ps -efww
root 15817 15815  0 13:36 pts/000:00:00 /usr/bin/perl 
/usr/bin/dpkg-buildpackage
root 25673 3  0 14:56 pts/000:00:00 
/mnt/sdb4/cvs/ruby/ruby1.9-1.9.0.2/miniruby 
-I/mnt/sdb4/cvs/ruby/ruby1.9-1.9.0.2/lib 
-I/mnt/sdb4/cvs/ruby/ruby1.9-1.9.0.2/.ext/common -I./- 
-r/mnt/sdb4/cvs/ruby/ruby1.9-1.9.0.2/ext/purelib.rb -W0 bootstraptest.tmp.rb
root 25676 25673  0 14:56 pts/000:00:00 [miniruby] defunct
root 25892  2014  0 17:16 pts/100:00:00 ps -efwww
root 29832 15817  0 14:46 pts/000:00:00 /usr/bin/make -f debian/rules 
binary
root 32188 29832  0 14:55 pts/000:00:00 make test
root 3 32188  0 14:55 pts/000:00:00 ./miniruby -I./lib 
-I.ext/common -I./- -r./ext/purelib.rb ./bootstraptest/runner.rb 
--ruby=./miniruby -I./lib -I.ext/common -I./- -r./ext/purelib.rb  -q
root 32223 3  0 14:55 pts/000:00:00 ./miniruby -I./lib 
-I.ext/common -I./- -r./ext/purelib.rb ./bootstraptest/runner.rb 
--ruby=./miniruby -I./lib -I.ext/common -I./- -r./ext/purelib.rb  -q
root 32224 32223  0 14:55 pts/000:00:00 ./miniruby -I./lib 
-I.ext/common -I./- -r./ext/purelib.rb ./bootstraptest/runner.rb 
--ruby=./miniruby -I./lib -I.ext/common -I./- -r./ext/purelib.rb  -q

r...@c3000:~/cvs/ruby/ruby1.9-1.9.0.2# strace -p 3
Process 3 attached - interrupt to quit
_newselect(7, [6], NULL, NULL, NULL^C unfinished ...
Process 3 detached

r...@c3000:~/cvs/ruby/ruby1.9-1.9.0.2# strace -p 32223
Process 32223 attached - interrupt to quit
restart_syscall(... resuming interrupted call ...) = 0
getppid()   = 3
poll([{fd=3, events=POLLIN}], 1, 2000)  = 0 (Timeout)
getppid()   = 3
poll([{fd=3, events=POLLIN}], 1, 2000^C unfinished ...
Process 32223 detached

r...@c3000:~/cvs/ruby/ruby1.9-1.9.0.2# strace -p 32224
Process 32224 attached - interrupt to quit
nanosleep({0, 1000}, {0, 7191145})  = 0
nanosleep({0, 1000}, {0, 7191145})  = 0
nanosleep({0, 1000}, {0, 7191145})  = 0
nanosleep({0, 1000}, {0, 7191145})  = 0
...

So, it's probably somehow a threading-related problem.
I'm not sure yet, why the miniruby PID 25676 is defunct.

Needs quite some debugging, but we still have threading problems on hppa. 

 Yeah, penalosa got stuck again today, this was on the console:
 Does panalosa has the patched kernel (same one as the one on peri) ?
 
 Both machines were running an unpatched SMP 2.6.26 until I upgraded
 penalosa for the test I refer to above. The thinking being that -
 though these machines are single CPU - the SMP version should avoid
 the UP 

Please unblock dctrl-tools/2.13.1

2009-01-06 Thread Antti-Juhani Kaijanaho
This is a translation update; no other changes.

dctrl-tools (2.13.1) unstable; urgency=low

  [ Gerfried Fuchs ]  
  * Czech translation update received from Miroslav Kure, thanks.

 -- Antti-Juhani Kaijanaho a...@debian.org  Tue, 06 Jan 2009 16:19:48 +0200

-- 
Antti-Juhani Kaijanaho, Jyväskylä, Finland
http://antti-juhani.kaijanaho.fi/newblog/
http://www.flickr.com/photos/antti-juhani/


signature.asc
Description: Digital signature


Re: Bug#511011: libtdb1: Breaks ABI without SONAME bump.

2009-01-06 Thread Cyril Brulebois
Cyril Brulebois k...@debian.org (06/01/2009):
 Package: libtdb1
 Version: 1.1.2~git20080615-1
 Severity: serious
 Justification: ABI breakage.

Stripping some parts for -release, keeping what matters:

 We don't care about 'U' ones, of course. Checking which ones got away:
 | grep ^-T tdb-symbols.diff
 | -T tdb_clear_spinlocks
 | -T tdb_create_rwlocks
 | -T tdb_logging_function
 | -T tdb_set_lock_alarm
 | -T tdb_spinlock
 | -T tdb_spinunlock
 
 That *might* not be the problem if they are not exposed through the API.
 But both tdb_logging_function and tdb_set_lock_alarm are exposed.
 
 I'm going to have a look at the packages that depend on this library, to
 see how things looks like. I'm in contact with a release manager as well
 (hello dato).

Here is my findings about etch/lenny packages WRT the 6 removed symbols
(looking at main).

Packages both in etch and in lenny:
---
libprintsys/etch:   OK (basic symbols)
libprintsys/lenny:  OK (basic symbols)
pconf-detect/etch:  OK (linked in, no symbols)
pconf-detect/lenny: OK (linked in, no symbols)

Packages only in lenny:
---
fdm/lenny:OK (only a few symbols)
python-tdb/lenny: OK (lots of symbols, built from the same source)

Packages only in etch:
--
adept-installer/etch:OK (linked in, no symbols)
adept-manager/etch:  OK (linked in, no symbols)
adept-notifier/etch: OK (linked in, no symbols)
adept-updater/etch:  OK (linked in, no symbols)
libprinterconf0c2a/etch: OK (linked in, no symbols)
tagcolledit/etch:OK (linked in, no symbols)
tdb-tools/etch:  OK (lots of symbols)


Note that it still can break locally-built packages or pieces of
software. I think you could consider downgrading the severity, or
tagging it lenny-ignore since there seem to be no collateral damages
within Debian.

That said, I guess a t-p-u upload to fix #510886 and a binNMU of fdm
will do the job (I didn't check yet it needs a = on the lenny version,
but I guess it'd be a a nice-to-have anyway).

Mraw,
KiBi.


signature.asc
Description: Digital signature


Re: Bug#511011: libtdb1: Breaks ABI without SONAME bump.

2009-01-06 Thread Cyril Brulebois
Cyril Brulebois k...@debian.org (06/01/2009):
 That said, I guess a t-p-u upload to fix #510886 and a binNMU of fdm
 will do the job (I didn't check yet it needs a = on the lenny
 version, but I guess it'd be a a nice-to-have anyway).

That appears not to be needed after a check with LD_LIBRARY_PATH, it
looks like fdm/lenny loads fine with libtdb1/etch. That's up to you. :)

Cc-ing the “missing shlibs bump” bug this time.

Mraw,
KiBi.


signature.asc
Description: Digital signature


Please unblock gpsd-2.37-7

2009-01-06 Thread Bernd Zeimetz
Hi Release Team,

unfortunately the Python based tools which ship with gpsd don't work with
Lenny's Python2.5 as the pty module is broken. Unfortunately upstream and me
could  not yet figure out if that's a Python, gcc, glibc or kernel problem
(yeah, there's even a minor chance that the problem lies somewhere in the gpsd
python modules).
As i doubt that the real bug will be fixed in time for Lenny, I've patched the
Python tools from gpsd to use python 2.4, which is a bit annoying, but better
than delivering broken tools.

Thanks,

Bernd

-- 
 Bernd Zeimetz   Debian GNU/Linux Developer
 GPG Fingerprint: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79


-- 
To UNSUBSCRIBE, email to debian-release-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org