Bug#850693: RM: goto-fai-backend -- ROM; removal requested by upstream; highly deprecated

[Cajus Pollmeier]

ACK

Am Montag, den 09.01.2017, 14:17 +0100 schrieb Mike Gabriel:
> Package: ftp.debian.org
> Severity: normal
> 
> Please remove goto-fai-backend from Debian, the upstream code is dead
> old
> and not up-to-date anymore regarding latest FAI.
> 
> Thanks,
> Mike
> 
> PS: the original maintainer and upstream is in Cc: and will shortly
> give
> his ACK on the requested removal.

signature.asc
Description: This is a digitally signed message part

Bug#850694: RM: goto-fai-progress -- ROM; removal requested by upstream; highly deprecated

[Cajus Pollmeier]

ACK

Am Montag, den 09.01.2017, 14:19 +0100 schrieb Mike Gabriel:
> Package: ftp.debian.org
> Severity: normal
> 
> Please remove goto-fai-progress from Debian, the upstream code is
> dead old
> and not up-to-date anymore regarding latest FAI.
> 
> Thanks,
> Mike
> 
> PS: the original maintainer and upstream is in Cc: and will shortly
> give
> his ACK on the requested removal.

signature.asc
Description: This is a digitally signed message part

Bug#850695: RM: goto-fai -- ROM; removal requested by upstream; highly deprecated

[Cajus Pollmeier]

ACK

Am Montag, den 09.01.2017, 14:19 +0100 schrieb Mike Gabriel:
> Package: ftp.debian.org
> Severity: normal
> 
> 
> Please remove goto-fai from Debian, the upstream code is dead old
> and not up-to-date anymore regarding latest FAI.
> 
> Thanks,
> Mike
> 
> PS: the original maintainer and upstream is in Cc: and will shortly
> give
> his ACK on the requested removal.

signature.asc
Description: This is a digitally signed message part

Bug#850697: RM: gosa-perl -- ROM; removal requested by upstream; highly deprecated

[Cajus Pollmeier]

ACK

Am Montag, den 09.01.2017, 14:21 +0100 schrieb Mike Gabriel:
> Package: ftp.debian.org
> Severity: normal
> 
> Please remove gosa-perl from Debian, the upstream code is dead old
> and not up-to-date anymore regarding latest FAI (which it is for).
> 
> Thanks,
> Mike
> 
> PS: the original maintainer and upstream is in Cc: and will shortly
> give
> his ACK on the requested removal.

signature.asc
Description: This is a digitally signed message part

Bug#850696: RM: goto-common -- ROM; removal requested by upstream; highly deprecated

[Cajus Pollmeier]

ACK

Am Montag, den 09.01.2017, 14:20 +0100 schrieb Mike Gabriel:
> Package: ftp.debian.org
> Severity: normal
> 
> 
> Please remove goto-common from Debian, the upstream code is dead old
> and not up-to-date anymore regarding latest FAI.
> 
> Thanks,
> Mike
> 
> PS: the original maintainer and upstream is in Cc: and will shortly
> give
> his ACK on the requested removal.

signature.asc
Description: This is a digitally signed message part

Bug#706290: O: uif -- Advanced iptables-firewall script

[Cajus Pollmeier]

Package: wnpp
Severity: normal

I'm retiring and I've probably no time in the near future to maintain
the package.


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

Bug#706289: O: fts -- Modular TFTP/Fuse supplicant

[Cajus Pollmeier]

Package: wnpp
Severity: normal

I'm retiring and I've probably no time in the near future to maintain
the package.


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

Bug#706288: O: python-lepl -- recursive descent parser library

[Cajus Pollmeier]

Package: wnpp
Severity: normal

I'm retiring and I've probably no time in the near future to maintain
the package.


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

Bug#706101: qpid-python: contains DFSG-violating AMQP spec files

[Cajus Pollmeier]

Hi,

I've currently no time slot to do any work on this. Sorry. Probably it's the 
best to RFA all of my packages, to signalize this state until there's more time 
for Debian again. Will do today.

Regards,
Cajus

Am 27.04.2013 um 15:12 schrieb "Adam D. Barratt" :

> Hi,
> 
> On Wed, 2013-04-24 at 18:45 +0200, Jonas Smedegaard wrote:
>> qpid-python contains AMQP spec files licensed under the "AMQP license"
>> which is not compliant with Debian Free Software Guidelines.
>> 
>> BSD-licensed "stripped" specs exist for plain AMQP specs, and JSON-based
>> specs exist for RabbitMQ derived specs.
>> 
>> NB! Please (build-)depend on amqp-specs to avoid duplication, and file
>> bugs against that package for any formats needed but not yet included
>> there.
> 
> qpid-python maintainer - any news on getting this fixed?
> 
> Regards,
> 
> Adam


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

Bug#700535: fts: several issues w.r.t. configuration file handling

[Cajus Pollmeier]

Hi Andreas,

you're welcome to NMU it. Sadly I've not as much time for Debian as I'd 
like in the moment. So it would be really great if you could do it.


Going to pull the stuff later on...

Thanks!
Cajus

Am 14.02.2013 04:33, schrieb Andreas Beckmann:

Package: fts
Version: 1.1-1
Severity: serious
Tags: patch

Hi,

actually I only wanted to look whether #674007 can be fixed easily 
...

but then I found a lot of serious errors handling /etc/fts/config:

* upstream git repository has moved (ok, found the new location)
* incorrect usage of debconf in postrm purge
* shipping /etc/fts/config as conffile *and* generating it in 
postinst

* having the template in /usr/share/doc/ instead of /usr/share/fts/
* not using ucfr/ucfr --purge
* not using ucf --purge in postinst (install, purge, install - and 
ucf

  will notice that the config file was deleted inbetween and keep it
  that way)

I have all the changes that are combined (and duplicated due to the
upstream repository layout) in the attached diff as separate git
commits, I just need to push the repository somewhere so that you can
pull ... from here: git://github.com/anbe42/tmp-fts.git

Since I brought the package into shape so far, I can also NMU it ... 
and

I intend to do so in a few days.


Andreas



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

Bug#698714: Configuring GOsa failed

[Cajus Pollmeier]

close #698714
thanks

Am Donnerstag, 24. Januar 2013, 21:30:38 schrieb Csanyi Pal:
> I finally have successfully Configured GOsa.
> 
> Can one expect in the future that this Configuration works out of the
> box, or at least to get an user more help during the configuration
> process?

The configuration works out of the box, but you've to know a few bits about how 
your infrastructure works. The setups may be very different, the GOsa package 
is not meant as an appliance that just works like "fire and forget".

Cheers,
Cajus


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

Bug#698544: gosa: SASL as "password hash method" fails

[Cajus Pollmeier]

I don't think that seting the default hash to "SASL" is the right thing to do 
here. You've to set the password method to "sasl" and configure the realm in 
the configuration to achieve this.

Note that the sasl password method was initially done with external service 
configuration in mind.

HTH,
Cajus

Am Sonntag, 20. Januar 2013, 10:44:53 schrieben Sie:
> Package: gosa
> Version: 2.7.4-4
> Severity: normal
> 
> Hi,
> 
> I am implementing GOsa for the Debian-LAN setup.  The idea is to use
> SASL to authenticate users in the setup with kerberos.  To implement
> that, I use passwordDefaultHash="sasl" in gosa.conf.
> 
> However, when I add a user in GOsa, I end up with:
> 
> ---8<---
> uid=ante,ou=people,ou=gosa,dc=intern
> sn: Another
> givenName: Test
> uid: ante
> cn: Test Another
> userPassword: {SASL}@INTERN
> ---8<---
>  ^^
>  The uid is missing.
> 
> If I log into GOsa as admin and modify the Password storage in the
> "Generic"-Tab to ssha (press apply) and back to sasl, I end up with
> what I would have expected from the beginning:
> 
>  userPassword: {SASL}ante@INTERN
> 
> Further more, there is no way to enter a password, no dialog shows
> up.   The entered password would be sent to the KDC via a hook.
> 
> The 'perfect' setup would look like this:  When SASL is chosen as
> password method, the password dialog is available if a corresponding
> hook exists in gosa.conf.
> 
> The sugested setup would help debian-lan as well as debian-edu to
> prepare a cleaner setup with central authentication and password
> storage in the KDC.
> 
> Best regards,
> 
>   Andi
> 
> 
> 
> 
> -- System Information:
> Debian Release: 7.0
>   APT prefers testing-updates
>   APT policy: (500, 'testing-updates'), (500, 'testing'), (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 3.2.0-4-amd64 (SMP w/1 CPU core)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> 
> Versions of packages gosa depends on:
> ii  apache22.2.22-12
> ii  apache2-mpm-prefork [httpd]2.2.22-12
> ii  exim4  4.80-7
> ii  exim4-daemon-heavy [mail-transport-agent]  4.80-7
> ii  gettext0.18.1.1-9
> ii  libapache2-mod-php55.4.4-10
> ii  libcrypt-smbhash-perl  0.12-3
> ii  php5   5.4.4-10
> ii  php5-cli   5.4.4-10
> ii  php5-curl  5.4.4-10
> ii  php5-gd5.4.4-10
> ii  php5-imagick   3.1.0~rc1-1+b2
> ii  php5-imap  5.4.4-10
> ii  php5-ldap  5.4.4-10
> ii  php5-mcrypt5.4.4-10
> ii  php5-mysql 5.4.4-10
> ii  php5-recode5.4.4-10
> ii  smarty33.1.10-2
> ii  ttf-liberation     1.07.2-6
> 
> gosa recommends no packages.
> 
> Versions of packages gosa suggests:
> pn  cyrus21-imapd   
> ii  gosa-schema 2.7.4-4
> pn  gosa-si-server  
> pn  php-apc 
> pn  php-fpdf
> pn  php5-suhosin
> pn  postfix-ldap
> ii  slapd   2.4.31-1
> 
> -- no debconf information


-- 
Cajus Pollmeier  (Head of Development)
* GONICUS GmbH * Adelheidstraße 21 * D-80789 München
* Tel.: +49 (0) 29 32 / 9 16 - 0 * Fax: +49 (0) 29 32 / 9 16 - 223
* http://www.GONICUS.de * http://twitter.com/gonicus

* Sitz der Gesellschaft: Moehnestrasse 55 * D-59755 Arnsberg
* Geschaeftsfuehrer: Rainer Luelsdorf, Alfred Schroeder
* Vorsitzender des Beirats: Juergen Michels
* Amtsgericht Arnsberg * HRB 1968
  


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

Bug#698714: [gosa] Configuring GOsa failed

[Cajus Pollmeier]

Am Mittwoch, 23. Januar 2013, 17:43:48 schrieb Csanyi Pal:
> On Wed, Jan 23, 2013 at 09:01:37AM +0100, Cajus Pollmeier wrote:
> > severity 698714 minor
> > thanks
> > 
> > Why don't you enter an administrative DN?
> 
> Because I don't know its DN name.
> 
> When I installed slapd, I set it up with the followings:
> Omit OpenLDAP server configuration? No
> DNS domain name: nodomain
> Organization name: nodomain
> Administrator password: secret1
> Database backend to use: HDB
> Do you want the database to be removed when slapd is purged? No
> Move old database? Yes
> Allow LDAPv2 protocol? No
> 
> What should I enter into Administrator DN field when configuring Gosa?

I personally don't use the debian automatic slapd stuff because it never does 
what I want. In turn I can't tell you the administrative DN it is creating 
automatically. Maybe it's something like "cn=ldapadmin,dc=nodomain" in your 
case.

Please call "slapcat" on the console and take a look if there's a line 
starting with "dn:" followed by something like "cn=admin,...", 
"cn=ldapadmin,...", "cn=manager,...". If you've found it in the output - this 
is your administrative DN. Use this one with the password you've provided.

HTH,
Cajus


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

Bug#698714: [gosa] Configuring GOsa failed

[Cajus Pollmeier]

severity 698714 minor
thanks

Why don't you enter an administrative DN?

Am Dienstag, 22. Januar 2013, 18:08:16 schrieben Sie:
> Package: gosa
> Version: 2.7.4-4
> Severity: grave
> 
> --- Please enter the report below this line. ---
> Hi,
> 
> I'm trying to configure my Gosa installation following the
> /usr/share/doc/gosa/README.Debian.
> 
> Pointing my Internet browser to the
> http://localhost/gosa/setup.php?js=true
> 
> and running
> $ sudo echo -n si3rj6ckpff4gf6jpgfh8328a4 > /tmp/gosa.auth
> 
> I can reach the step 4: LDAP connection setup.
> 
> Here I have:
> * LDAP connection
> Location name: default
> Connection URI: ldap://localhost:389
> TLS connection: No
> Base: dc=nodomain
> * Authentication
> Administrator DN: an empty field
> not checked --> Automatically append LDAP base to administrator DN
> Administrator password: an empty field
> * Schema based settings
> Use RFC 2307bis compliant groups: No
> * Current status
> Information: Anonymous bind to server 'ldap://localhost:389'
> succeeded. Please specify user and password!
> 
> When I installed slapd, I set it up with the followings:
> Omit OpenLDAP server configuration? No
> DNS domain name: nodomain
> Organization name: nodomain
> Administrator password: secret1
> Database backend to use: HDB
> Do you want the database to be removed when slapd is purged? No
> Move old database? Yes
> Allow LDAPv2 protocol? No
> 
> I want to use LDAP only on my desktop machine where I installed slapd.
> 
> Back to the Gosa Configuration.
> 
> Now, when I checked the
> Automatically append LDAP base to administrator DN
> 
> I get:
> Administrator DN: an ampty field and at the and of the field:
> ',dc=nodomain' without quotes,
> Administrator password: secret1
> Current status
> Information   Bind as user ',dc=nodomain' failed!
> 
> I can't go further to configure Gosa.
> What can I do now to solve this problem?
> 
> I expect this Configuration to works out of the box, but it doesn't
> work.
> 
> 
> --- System information. ---
> Architecture: amd64
> Kernel:   Linux 3.2.0-4-amd64
> 
> Debian Release: 7.0
>   500 unstablewww.deb-multimedia.org
>   500 unstableftp.debian.org
>   500 unstabledebian.scribus.net
>   500 testing www.deb-multimedia.org
>   500 testing ftp.debian.org
>   500 stable  dl.google.com
> 1 experimentalftp.debian.org
> 
> --- Package information. ---
> Depends(Version) | Installed
> -+-
> php5 | 5.4.4-12
> php5-cli | 5.4.4-12
> apache2  |
>  OR lighttpd |
>  OR httpd|
> exim4| 4.80-7
>  OR mail-transport-agent |
> php5-gd  | 5.4.4-12
> php5-imap| 5.4.4-12
> php5-ldap| 5.4.4-12
> php5-mcrypt  | 5.4.4-12
> php5-mysql   | 5.4.4-12
> php5-imagick |
>  OR imagemagick  (>= 5.4.4.5-1)  | 8:6.7.7.10-5
>  OR graphicsmagick-im-compat |
> libcrypt-smbhash-perl| 0.12-3
> php5-recode  | 5.4.4-12
> smarty3(>= 3.1.10-1) | 3.1.10-2
> gettext  | 0.18.1.1-10
> libapache2-mod-php5  | 5.4.4-12
>  OR php5-cgi |
> php5-curl| 5.4.4-12
> ttf-liberation   | 1.07.2-6
> 
> 
> Package's Recommends field is empty.
> 
> Suggests     (Version) | Installed
> ==-+-
> gosa-si-server |
> cyrus21-imapd  (>= 2.1.11) |
> postfix-ldap   |
> slapd  | 2.4.31-1
> gosa-schema| 2.7.4-4
> php5-suhosin   |
> php-apc|
> php-fpdf   |


-- 
Cajus Pollmeier  (Head of Development)
* GONICUS GmbH * Adelheidstraße 21 * D-80789 München
* Tel.: +49 (0) 29 32 / 9 16 - 0 * Fax: +49 (0) 29 32 / 9 16 - 223
* http://www.GONICUS.de * http://twitter.com/gonicus

* Sitz der Gesellschaft: Moehnestrasse 55 * D-59755 Arnsberg
* Geschaeftsfuehrer: Rainer Luelsdorf, Alfred Schroeder
* Vorsitzender des Beirats: Juergen Michels
* Amtsgericht Arnsberg * HRB 1968
  


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

Bug#690753: rhmessaging: FTBFS on arm* (and other arches)

[Cajus Pollmeier]

Am 17.10.2012 11:28, schrieb Konstantinos Margaritis:

Package: rhmessaging
Version: 0.16-1
Severity: Important
Tags: patch

For armel/armhf the following simple patch seems to work, the package
builds and the tests pass. I assume similar fixes might be worth 
testing

on mips/mipsel/sparc as well.

Regards



Hi Konstantinos,

thanks for the patch. While it's too late for wheezy, I'll test it for 
unstable.


Cheers,
Cajus


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

Bug#685741: unblock: qpid-cpp/0.16-7

[Cajus Pollmeier]

Hi Moritz,

there will be time on the week-end. The last two months where a bit "packed" 
with stuff :-(

Cheers,
Cajus

Am Donnerstag, 4. Oktober 2012, 17:41:33 schrieb Moritz Muehlenhoff:
> On Wed, Sep 19, 2012 at 08:45:27AM +0100, Adam D. Barratt wrote:
> > On 19.09.2012 08:23, Cajus Pollmeier wrote:
> >> Am Dienstag, 18. September 2012, 18:54:47 schrieben Sie:
> >>> On Mon, Sep 10, 2012 at 02:20:54PM +0200, Mehdi Dogguy wrote:
> >>> > Unfortunately, even if we can unblock qpid-cpp/0.16-7 for
> >>> 
> >>> migration, it
> >>> 
> >>> > will be blocked by redhat-cluster which doesn't seem ready (which
> >>> 
> >>> in
> >>> 
> >>> > turn, is also blocked by gfs2-utils). I think the best way forward
> >>> 
> >>> would
> >>> 
> >>> > be to prepare an upload targeting testing-proposed-updates.
> >>> 
> >>> Cajus, can you prepare a testing-proposed-updates upload with the
> >>> fix
> >>> from qpid-cpp/0.16-7?
> > 
> > [...]
> > 
> >> hmm - do I need to upload a new version for unstable in this case,
> >> too? The
> >> docs say something about: the version for testing-proposed-updates
> >> needs to be
> >> above than the one in testing (check) and under the one in unstable
> >> (buzzer).
> > 
> > Where's the issue?  There's a multitude of available versions that
> > fulfil that criterion - 0.16-6+deb7u1, for instance.
> 
> Cajus, what's the status?
> 
> Cheers,
> Moritz


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

Bug#685741: unblock: qpid-cpp/0.16-7

[Cajus Pollmeier]

Am Dienstag, 18. September 2012, 18:54:47 schrieben Sie:
> On Mon, Sep 10, 2012 at 02:20:54PM +0200, Mehdi Dogguy wrote:
> > Unfortunately, even if we can unblock qpid-cpp/0.16-7 for migration, it
> > will be blocked by redhat-cluster which doesn't seem ready (which in
> > turn, is also blocked by gfs2-utils). I think the best way forward would
> > be to prepare an upload targeting testing-proposed-updates.
> 
> Cajus, can you prepare a testing-proposed-updates upload with the fix
> from qpid-cpp/0.16-7?
> 
> Cheers,
> Moritz

Hi Moritz,

hmm - do I need to upload a new version for unstable in this case, too? The 
docs say something about: the version for testing-proposed-updates needs to be 
above than the one in testing (check) and under the one in unstable (buzzer).

Cheers,
Cajus


signature.asc
Description: This is a digitally signed message part.

Bug#685741: unblock: qpid-cpp/0.16-7

[Cajus Pollmeier]

Am Montag, 27. August 2012, 11:27:43 schrieb Adam D. Barratt:
> On 27.08.2012 08:34, Cajus Pollmeier wrote:
> > Am Freitag, 24. August 2012, 18:39:28 schrieb Adam D. Barratt:
> >> On Fri, 2012-08-24 at 11:00 +0200, Cajus Pollmeier wrote:
> >> > Am Freitag, 24. August 2012, 10:19:45 schrieben Sie:
> >> > > +-static std::auto_ptr
> >> > > createAuthenticator(Connection& connection, bool isShadow); ++
> >> > > static std::auto_ptr
> >> > > createAuthenticator(Connection& connection);
> >> > > 
> >> > > createAuthenticator() is a public symbol of libqpidbroker, which
> >> 
> >> is
> >> 
> >> > > shipped as a public library in /usr/lib.  That means the library
> >> 
> >> has
> >> 
> >> > > changed ABI without changing SONAME afaics.
> >> > 
> >> > libqpidbroker is only used by the qpid broker itself. There's
> >> 
> >> nothing in
> >> 
> >> > testing that uses the broker library - besides the broker itself.
> >> > Unstable has the qpidd-msgstore module that makes use of that
> >> 
> >> library.
> >> 
> >> qpidd-msgstore is also in testing.  Does the earlier version not use
> >> the
> >> broker library?
> > 
> > Hmm. Is it possible to remove it from testing? The version that
> > matches the
> > current 0.16 release of qpidd got stuck because it didn't compile on
> > all
> > architectures. 0.14 qpidd-msgstore will not work with 0.16 of qpidd.
> 
> Okay; removal hint added.

Thanks. Seems to be gone already ;-)

> >> > I'm not sure if and how I can simply change the SONAME for the
> >> 
> >> broker.
> >> 
> >> > And if there's a need for that in this case. Any hints?
> >> 
> >> It's shipped in a public library directory and versioned so yes it
> >> should be updated (even without the existence of a reverse
> >> dependency).
> >> Assuming the SONAMEs come from upstream, it'd be worth discussing
> >> the
> >> issue with them so we don't end up carrying a Debian-specific change
> >> for
> >> it.
> > 
> > Just sent a message to upstream. Lets see.
> 
> Thanks.

That's the answer:

  I don't think that we are currently proposing any upstream library
  versioning at all. As far as I remember the library versioning in the
  Fedora and Red Hat Enterprise packages are not the same as the
  versioning you will get if you just run make install on the upstream
  package.

  Similarly we've not been especially careful to change library versions
  consistent with ABI so I perhaps you should do whatever works for your
  packaging.

  I would note that libqpidbroker really exposes only an entirely private
  interface though so perhaps it's versioning isn't that significant -
  it's not actually separable from qpidd anyway.

  Andrew

Which may lead to these actions:

  * Inspect the SONAME of the upcoming 0.18 release and choose some
non conflicting value between the 0.16 and 0.18 releases. I'd like
to avoid maintaining a completely different scheme on my own. The
qpid packages are very time consuming even without that.

  * Remove these libraries from /usr/lib because they seem to be more
more private - even though they're used by the msgstore component.
But this may lead to complications when the msgstore component is
trying to find the affected .so's without munging around with
library paths.

  * Just leave it as it is for wheezy, because there's nothing that
depends on it - and probably will never be.

I'd personally prefere the latter, because there seems to be no need to care 
about it in this case. Additionally I cannot address these issues within the 
next three weeks due to holiday situations.

But - of course - I'm aware that there are reasons to choose #1 or #2 for 
wheezy.

What do you think? Would it be ok for you to just leave it as it is?

Cheers,
Cajus


signature.asc
Description: This is a digitally signed message part.

Bug#685741: unblock: qpid-cpp/0.16-7

[Cajus Pollmeier]

Am Freitag, 24. August 2012, 18:39:28 schrieb Adam D. Barratt:
> On Fri, 2012-08-24 at 11:00 +0200, Cajus Pollmeier wrote:
> > Am Freitag, 24. August 2012, 10:19:45 schrieben Sie:
> > > +-static std::auto_ptr
> > > createAuthenticator(Connection& connection, bool isShadow); ++   
> > > static std::auto_ptr
> > > createAuthenticator(Connection& connection);
> > > 
> > > createAuthenticator() is a public symbol of libqpidbroker, which is
> > > shipped as a public library in /usr/lib.  That means the library has
> > > changed ABI without changing SONAME afaics.
> > 
> > libqpidbroker is only used by the qpid broker itself. There's nothing in
> > testing that uses the broker library - besides the broker itself.
> > Unstable has the qpidd-msgstore module that makes use of that library.
> 
> qpidd-msgstore is also in testing.  Does the earlier version not use the
> broker library?

Hmm. Is it possible to remove it from testing? The version that matches the 
current 0.16 release of qpidd got stuck because it didn't compile on all 
architectures. 0.14 qpidd-msgstore will not work with 0.16 of qpidd.

> > I'm not sure if and how I can simply change the SONAME for the broker.
> > And if there's a need for that in this case. Any hints?
> 
> It's shipped in a public library directory and versioned so yes it
> should be updated (even without the existence of a reverse dependency).
> Assuming the SONAMEs come from upstream, it'd be worth discussing the
> issue with them so we don't end up carrying a Debian-specific change for
> it.

Just sent a message to upstream. Lets see.

Cheers,
Cajus


signature.asc
Description: This is a digitally signed message part.

Bug#685741: unblock: qpid-cpp/0.16-7

[Cajus Pollmeier]

Am Freitag, 24. August 2012, 10:19:45 schrieben Sie:
> Control: tags -1 + moreinfo
> 
> On Fri, 2012-08-24 at 08:47 +0200, Cajus Pollmeier wrote:
> > Please unblock package qpid-cpp
> > 
> > This upload fixes a security problem inside of qpid client handlings
> > (CVE-2012-3467). Please see
> > 
> > http://www.openwall.com/lists/oss-security/2012/08/09/6
> 
> +--- a/src/qpid/broker/SaslAuthenticator.h
>  b/src/qpid/broker/SaslAuthenticator.h
> +@@ -54,7 +54,7 @@
> + static void init(const std::string& saslName, std::string const &
> saslConfigPath ); + static void fini(void);
> +
> +-static std::auto_ptr
> createAuthenticator(Connection& connection, bool isShadow); ++static
> std::auto_ptr createAuthenticator(Connection&
> connection);
> 
> createAuthenticator() is a public symbol of libqpidbroker, which is
> shipped as a public library in /usr/lib.  That means the library has
> changed ABI without changing SONAME afaics.

libqpidbroker is only used by the qpid broker itself. There's nothing in 
testing that uses the broker library - besides the broker itself. Unstable has 
the qpidd-msgstore module that makes use of that library.

I'm not sure if and how I can simply change the SONAME for the broker. And if 
there's a need for that in this case. Any hints?


signature.asc
Description: This is a digitally signed message part.

Bug#685741: unblock: qpid-cpp/0.16-7

[Cajus Pollmeier]

Subject: unblock: qpid-cpp/0.16-7
Package: release.debian.org
User: release.debian@packages.debian.org
Usertags: unblock
Severity: normal

Please unblock package qpid-cpp

This upload fixes a security problem inside of qpid client handlings
(CVE-2012-3467). Please see

http://www.openwall.com/lists/oss-security/2012/08/09/6

for more information.

unblock qpid-cpp/0.16-7

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
diff -Nru qpid-cpp-0.16/debian/changelog qpid-cpp-0.16/debian/changelog
--- qpid-cpp-0.16/debian/changelog	2012-06-05 09:40:01.0 +0200
+++ qpid-cpp-0.16/debian/changelog	2012-08-10 21:04:14.0 +0200
@@ -1,3 +1,10 @@
+qpid-cpp (0.16-7) unstable; urgency=low
+
+  * Fixes security issue CVE-2012-3467 which may allow bypassing the
+broker authentication mechanism. Closes: #684456.
+
+ -- Cajus Pollmeier   Fri, 10 Aug 2012 20:39:06 +0200
+
 qpid-cpp (0.16-6) unstable; urgency=low
 
   * Included a few additional headers to make the rhmessaging
diff -Nru qpid-cpp-0.16/debian/patches/CVE-2012-3467.patch qpid-cpp-0.16/debian/patches/CVE-2012-3467.patch
--- qpid-cpp-0.16/debian/patches/CVE-2012-3467.patch	1970-01-01 01:00:00.0 +0100
+++ qpid-cpp-0.16/debian/patches/CVE-2012-3467.patch	2012-08-10 21:04:14.0 +0200
@@ -0,0 +1,243 @@
+--- a/src/qpid/broker/Connection.cpp
 b/src/qpid/broker/Connection.cpp
+@@ -87,10 +87,14 @@
+bool link_,
+uint64_t objectId_,
+bool shadow_,
+-   bool delayManagement) :
++   bool delayManagement,
++   bool authenticated_
++) :
+ ConnectionState(out_, broker_),
+ securitySettings(external),
+-adapter(*this, link_, shadow_),
++shadow(shadow_),
++authenticated(authenticated_),
++adapter(*this, link_),
+ link(link_),
+ mgmtClosing(false),
+ mgmtId(mgmtId_),
+@@ -100,7 +104,6 @@
+ timer(broker_.getTimer()),
+ errorListener(0),
+ objectId(objectId_),
+-shadow(shadow_),
+ outboundTracker(*this)
+ {
+ outboundTracker.wrap(out);
+--- a/src/qpid/broker/Connection.h
 b/src/qpid/broker/Connection.h
+@@ -86,7 +86,8 @@
+bool isLink = false,
+uint64_t objectId = 0,
+bool shadow=false,
+-   bool delayManagement = false);
++   bool delayManagement = false,
++   bool authenticated=true);
+ 
+ ~Connection ();
+ 
+@@ -146,6 +147,9 @@
+ /** True if this is a shadow connection in a cluster. */
+ bool isShadow() { return shadow; }
+ 
++/** True if this connection is authenticated */
++bool isAuthenticated() const { return authenticated; }
++
+ // Used by cluster to update connection status
+ sys::AggregateOutput& getOutputTasks() { return outputTasks; }
+ 
+@@ -174,6 +178,8 @@
+ 
+ ChannelMap channels;
+ qpid::sys::SecuritySettings securitySettings;
++bool shadow;
++bool authenticated;
+ ConnectionHandler adapter;
+ const bool link;
+ bool mgmtClosing;
+@@ -188,7 +194,6 @@
+ boost::intrusive_ptr timeoutTimer;
+ ErrorListener* errorListener;
+ uint64_t objectId;
+-bool shadow;
+ framing::FieldTable clientProperties;
+ 
+ /**
+--- a/src/qpid/broker/ConnectionHandler.cpp
 b/src/qpid/broker/ConnectionHandler.cpp
+@@ -102,9 +102,10 @@
+ handler->secured = secured;
+ }
+ 
+-ConnectionHandler::ConnectionHandler(Connection& connection, bool isClient, bool isShadow)  : handler(new Handler(connection, isClient, isShadow)) {}
++ConnectionHandler::ConnectionHandler(Connection& connection, bool isClient)  :
++handler(new Handler(connection, isClient)) {}
+ 
+-ConnectionHandler::Handler::Handler(Connection& c, bool isClient, bool isShadow) :
++ConnectionHandler::Handler::Handler(Connection& c, bool isClient) :
+ proxy(c.getOutput()),
+ connection(c), serverMode(!isClient), secured(0),
+ isOpen(false)
+@@ -115,14 +116,13 @@
+ 
+ properties.setString(QPID_FED_TAG, connection.getBroker().getFederationTag());
+ 
+-authenticator = SaslAuthenticator::createAuthenticator(c, isShadow);
++	authenticator = SaslAuthenticator::createAuthenticator(c);
+ authenticator->getMechanisms(mechanisms);
+ 
+ Array locales(0x95);
+ boost::shared_ptr l(new Str16Value(en_US));
+ locales.add(l);
+ proxy.start(properties, mechanisms, locales);
+-
+ }
+ 
+ maxFrameSize = (64 * 1024) - 1;
+--- a/src/qpid/broker/ConnectionHandler.h
 b/src/qpid/broker/ConnectionHandler.h
+@@ -61,7 +61,7 @@
+ SecureConnection* secured;
+ bool isOpen;
+ 
+-Handler(Connect

Bug#685249: qmf-tool doesn't start: ImportError: No module named cqpid / Failed: TypeError - __init__() takes at most 2 arguments (3 given)

[Cajus Pollmeier]

Hmm. I'm wondering, why there's no 0.16-1 in the archives. Maybe I 
missed to upload it. That's more or less bad.


Will update to 0.16-1 and a 0.14-2 for wheezy.

Am 18.08.2012 22:17, schrieb Jakub Wilk:

Package: qpid-tools
Version: 0.14-1
Severity: important

If python-cqpid is not installed, qmf-tool doesn't start:

$ qmf-tool
Traceback (most recent call last):
  File "/usr/bin/qmf-tool", line 31, in 
import cqpid
ImportError: No module named cqpid


If python-cqpid is installed... qmf-tool doesn't start either:

$ qmf-tool
Failed: TypeError - __init__() takes at most 2 arguments (3 given)


(Disclaimer: I have no idea what is the purpose of qmf-tool. I
discovered that it doesn't work by running some semi-automatic 
tests.)


-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (990, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-3-686-pae (SMP w/1 CPU core)
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Shell: /bin/sh linked to /bin/dash

Versions of packages qpid-tools depends on:
ii  python  2.7.3-2
ii  python-cqmf20.16-7
ii  python-qmf2 0.16-7
ii  python-qpid 0.16-1
ii  python-qpid-extras-qmf  0.16-1
ii  python-setuptools   0.6.24-1
ii  python2.7   2.7.3-3



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

Bug#680945: Please include gosa-plugin-netgroups

[Cajus Pollmeier]

Hi Mike,

the netgroups plugin is no part of GOsa. It's a contributed plugin. Please 
file an RFP for that and I'll handle it as a separate package.

I'm closing this one, because it's no GOsa bug. I understand that it's
important for debian-edu, but I'd not mix contributed and upstream stuff
into one package.

Regards,
Cajus

Am Montag, 9. Juli 2012, 15:03:34 schrieben Sie:
> Package: gosa
> Severity: important
> Version: 2.7.4-4
> 
> Hi,
> 
> the Debian Edu depends on a Gosa plugin called gosa-plugin-netgroups
> (written by Alejandro Aescanero). To continue usage of GOsa² in Debain
> Edu wheezy the inclusion of gosa-plugin-netgroups would be very helpful.
> 
> For squeeze we had to hack that bin:package
> (debian-edu-config-gosa-netgrops) into src:debian-edu-config. We would
> love to avoid that for wheezy.
> 
> An SVN version can be found here...
> https://oss.gonicus.de/repositories/gosa-contrib/netgroups/trunk/
> 
> Maybe more recent probably is the netgroups-plugin of the
> FusionDirectory project (it will be worth looking at the patches
> committed lately):
> https://github.com/fusiondirectory/fusiondirectory-plugins/tree/master/netg
> roups
> 
> If you need help with syncing fusiondirectory-plugins-netgroups with
> gosa-plugin-netgroups, give me a ping.
> 
> Thanks,
> Mike


-- 
Cajus Pollmeier  (Head of Development)
* GONICUS GmbH * Moehnestrasse 11-17 * D-59755 Arnsberg
* Tel.: +49 (0) 29 32 / 9 16 - 0 * Fax: +49 (0) 29 32 / 9 16 - 223
* http://www.GONICUS.de

* Sitz der Gesellschaft: Moehnestrasse 11-17 * D-59755 Arnsberg
* Geschaeftsfuehrer: Rainer Luelsdorf, Alfred Schroeder
* Vorsitzender des Beirats: Juergen Michels
* Amtsgericht Arnsberg * HRB 1968


signature.asc
Description: This is a digitally signed message part.

Bug#678095: smarty3: Smarty 3.1.8 fails to load templates with relative paths

[Cajus Pollmeier]

Package: smarty3
Version: 3.1.8-2
Severity: important

Dear Maintainer,

some packages use the feature of having relative template paths and need major 
workarounds. The bug has been fixed upstream in 3.1.9 - 3.1.10 is the latest 
and greatest which fixes another problem with closing tags. Maybe it would be 
a good idea to update to 3.1.10 before the freeze arrives.

Cheers,
Cajus

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 3.2.0-2-686-pae (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages smarty3 depends on:
ii  php5-cli  5.4.4-1

smarty3 recommends no packages.

smarty3 suggests no packages.

-- no debconf information


signature.asc
Description: This is a digitally signed message part.

Bug#674331: rhmessaging: FTBFS: Exchange.h:28:36: fatal error: qmf/BrokerImportExport.h: No such file or directory

[Cajus Pollmeier]

Yes. I'm waiting for rhmessaging 0.16 to be tagged. A rebuild is not possible 
in the moment.



Am 24.05.2012 um 11:34 schrieb Lucas Nussbaum :

> Source: rhmessaging
> Version: 0.14-2
> Severity: serious
> Tags: wheezy sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20120524 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part:
>> /bin/bash ../libtool --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H -I. -I.. 
>>   -D_FORTIFY_SOURCE=2 -Werror -pedantic -Wall -Wextra -Wno-shadow 
>> -Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long 
>> -Wvolatile-register-var -Winvalid-pch -Wno-system-headers  -I/usr/include 
>> -I./gen -DRHM_CLEAN -pthread -g -O2 -fstack-protector 
>> --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c -o 
>> StorePlugin.lo StorePlugin.cpp
>> libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I.. -D_FORTIFY_SOURCE=2 -Werror 
>> -pedantic -Wall -Wextra -Wno-shadow -Wpointer-arith -Wcast-qual -Wcast-align 
>> -Wno-long-long -Wvolatile-register-var -Winvalid-pch -Wno-system-headers 
>> -I/usr/include -I./gen -DRHM_CLEAN -pthread -g -O2 -fstack-protector 
>> --param=ssp-buffer-size=4 -Wformat -Werror=format-security -c 
>> StorePlugin.cpp  -fPIC -DPIC -o .libs/StorePlugin.o
>> In file included from /usr/include/qpid/broker/Exchange.h:33:0,
>> from /usr/include/qpid/broker/DirectExchange.h:27,
>> from /usr/include/qpid/broker/Broker.h:28,
>> from StorePlugin.cpp:24:
>> /usr/include/qmf/org/apache/qpid/broker/Exchange.h:28:36: fatal error: 
>> qmf/BrokerImportExport.h: No such file or directory
>> compilation terminated.
>> make[4]: *** [StorePlugin.lo] Error 1
> 
> The full build log is available from:
>   
> http://people.debian.org/~lucas/logs/2012/05/24/rhmessaging_0.14-2_unstable.log
> 
> A list of current common problems and possible solutions is available at 
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
> 
> About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
> of the Grid'5000 platform, using a clean chroot.  Internet was not
> accessible from the build systems.
> 
> 



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

Bug#668284: RFP: spice-xpi -- SPICE extension for Mozilla

[Cajus Pollmeier]

There is an initial debian packaging here:

https://github.com/cajus/spice-xpi


signature.asc
Description: This is a digitally signed message part.

Bug#673535: override: libqpid-ruby1.8: oldlibs/extra

[Cajus Pollmeier]

Package: ftp.debian.org
Severity: normal

Hi!

The package ruby-qpid was recently accepted in main. The source
package also builds the transitional package libqpid-ruby1.8 which was
reported as an override disparity.

libqpid-ruby1.8_0.16-1_amd64.deb: package says section is oldlibs,
override says ruby.

Since libqpid-ruby is a transitional package it should have section
oldlibs and priority extra as stated by the package.

I'm not sure if this needs to be done for the other architectures, too.

Thanks for your work!

Cheers,
Cajus




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

Bug#673168: gosa: postinst failure: apache2_invoke: command not found

[Cajus Pollmeier]

Am Donnerstag, 17. Mai 2012, 19:43:33 schrieben Sie:
> Looks like you've apache2.2 instead of apache2.4 installed. Interresting,
> because I cannot reproduce this on my "unstable" system. The way the
> postinst script is done is the recommended way for the time after the
> apache 2.4 transition.
> 
> Additionally you seen to have leftovers of lighttpd installed.

Hmm. I think I'll add a workaround for that.


signature.asc
Description: This is a digitally signed message part.

Bug#673168: gosa: postinst failure: apache2_invoke: command not found

[Cajus Pollmeier]

Looks like you've apache2.2 instead of apache2.4 installed. Interresting, 
because I cannot reproduce this on my "unstable" system. The way the postinst 
script is done is the recommended way for the time after the apache 2.4 
transition.

Additionally you seen to have leftovers of lighttpd installed.

Am Mittwoch, 16. Mai 2012, 17:10:42 schrieben Sie:
> Package: gosa
> Version: 2.7.4-1
> Severity: grave
> Justification: renders package unusable
> 
> 
> Hi,
> 
> here is the problem:
> 
> Setting up gosa (2.7.4-1) ...
> /var/lib/dpkg/info/gosa.postinst: line 58: apache2_invoke: command not
> found Failed to enable the apache2 headers module!
> invoke-rc.d: unknown initscript, /etc/init.d/lighttpd not found.
> dpkg: error processing gosa (--configure):
> 
> 
> -- System Information:
> Debian Release: wheezy/sid
>   APT prefers unstable
>   APT policy: (500, 'unstable'), (1, 'experimental')
> Architecture: i386 (i686)
> 
> Kernel: Linux 3.2.0-2-rt-686-pae (SMP w/1 CPU core; PREEMPT)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/bash
> 
> Versions of packages gosa depends on:
> ii  apache22.2.22-5
> ii  apache2-mpm-prefork [httpd]2.2.22-5
> ii  fonts-liberation [ttf-liberation]  1.07.2-2
> ii  gettext0.18.1.1-7
> ii  imagemagick8:6.7.4.0-5
> ii  libapache2-mod-php55.4.3-4
> ii  libcrypt-smbhash-perl  0.12-3
> ii  micro-httpd [httpd]20051212-15
> ii  nginx-full [httpd] 1.1.19-1
> ii  nullmailer [mail-transport-agent]  1:1.05-1
> ii  php5   5.4.3-4
> ii  php5-cgi   5.4.3-4
> ii  php5-cli   5.4.3-4
> ii  php5-curl  5.4.3-4
> ii  php5-gd5.4.3-4
> ii  php5-imagick   3.1.0~rc1-1+b2
> ii  php5-imap  5.4.3-4
> ii  php5-ldap  5.4.3-4
> ii  php5-mcrypt5.4.3-4
> ii  php5-mysql 5.4.3-4
> ii  php5-recode5.4.3-4
> ii  smarty33.1.8-1
> 
> Versions of packages gosa recommends:
> ii  apache2  2.2.22-5
> ii  apache2-mpm-prefork [httpd]  2.2.22-5
> ii  micro-httpd [httpd]  20051212-15
> ii  nginx-full [httpd]   1.1.19-1
> 
> Versions of packages gosa suggests:
> pn  cyrus21-imapd   
> pn  gosa-schema 2.7.4-1
> pn  gosa-si-server  
> pn  php-apc 3.1.10-1
> pn  php-fpdf3:1.7.dfsg-1
> pn  php5-suhosin
> pn  postfix-ldap
> pn  slapd   
> 
> -- no debconf information


-- 
Cajus Pollmeier  (Head of Development)
* GONICUS GmbH * Moehnestrasse 11-17 * D-59755 Arnsberg
* Tel.: +49 (0) 29 32 / 9 16 - 0 * Fax: +49 (0) 29 32 / 9 16 - 223
* http://www.GONICUS.de

* Sitz der Gesellschaft: Moehnestrasse 11-17 * D-59755 Arnsberg
* Geschaeftsfuehrer: Rainer Luelsdorf, Alfred Schroeder
* Vorsitzender des Beirats: Juergen Michels
* Amtsgericht Arnsberg * HRB 1968


signature.asc
Description: This is a digitally signed message part.

Bug#672091: add patch

[Cajus Pollmeier]

Why not just wait a couple of days until the Qpid guys have finished 
voting for their 0.16 release? If you think there will be a not enough 
time with the wheezy freeze, let me know. In this case there's some more 
stuff to do and I'll do the upload.


Cheers,
Cajus

Am 10.05.2012 23:18, schrieb Matthias Klose:

tags 672091 + patch
thanks

uploaded to delayed/5, part of the boost transition





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

Bug#672398: Test your package with smarty3 (v3.1.x)

[Cajus Pollmeier]

Am Donnerstag, 10. Mai 2012, 21:13:53 schrieben Sie:
> Package: gosa
> Severity: normal
> Version: 2.7.4-1
> 
> Hi Cajus,
> 
> I have adopted the orphaned smarty3 package. As my first action, I
> have updated smarty3 to 3.1.8-1 and uploaded the package to
> experimental.
> 
> Note the description text of the package:
> 
> """
> Smarty 3.1 is a departure from 2.0 compatibility. Most notably, all
> backward compatibility has been moved to a separate class file named
> SmartyBC.class.php. If you require compatibility with 2.0, you will
> need to use this class.
> """
> 
> Please test gosa with this version of smarty3 (3.1.8-1).
> http://packages.debian.org/experimental/smarty3
> 
> I will move the package from experimental to unstable at the end of
> next week if I do not receive a veto from you.

I don't think that there will be a problem since the GOsa included smarty 
version is 3.1.4 (upstream). Just move it to unstable.

Cajus


signature.asc
Description: This is a digitally signed message part.

Bug#631753: gosa-plugin-mail: folder enumeration does not work with cyrusUseSlashes set to false

[Cajus Pollmeier]

This has been fixed in the recent 2.7.4 upload to unstable. Just forgot to add 
the Closes rule...

-- 
Cajus Pollmeier  (Head of Development)
* GONICUS GmbH * Moehnestrasse 11-17 * D-59755 Arnsberg
* Tel.: +49 (0) 29 32 / 9 16 - 0 * Fax: +49 (0) 29 32 / 9 16 - 223
* http://www.GONICUS.de

* Sitz der Gesellschaft: Moehnestrasse 11-17 * D-59755 Arnsberg
* Geschaeftsfuehrer: Rainer Luelsdorf, Alfred Schroeder
* Vorsitzender des Beirats: Juergen Michels
* Amtsgericht Arnsberg * HRB 1968


signature.asc
Description: This is a digitally signed message part.

Bug#672124: CVE-2011-3620

[Cajus Pollmeier]

Hi,

looks like this one:

https://issues.apache.org/jira/browse/QPID-3652

which - according to the bug itself affects 0.12. Comparing the diff 
from


https://reviews.apache.org/r/2988/diff/#index_header

makes me wonder, because the changes are not present in 0.14, but in 
the upcoming 0.16 release. RedHat itself used the CVE to update from 
0.12 to 0.14 - with a ~2MiB patch which includes the changes mentioned 
above.


So my short midnight conclusion is that the fix is not included in the 
upstream 0.14 release and is therefor not included in the Debian 
packages currently in testing and unstable.


I'm not sure how this is handled, because qpid is not in stable. There 
are a couple of compiling issues open that were caused by the GCC 4.7 
migration, that will make it hard to re-compile the 0.14 without adding 
several patches. Because we're not in "stable", I personally tend to 
wait for the final 0.16 release that is sadly a couple of days late. It 
fixes this issue - and also the compilation problems.


How to deal with this?

Am 08.05.2012 19:40, schrieb Moritz Muehlenhoff:

Package: qpid-cpp
Severity: grave
Tags: security

The following was reported for qpid-cpp:
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2011-3620

I'm not sure if this affects the Debian package, please investigate.

Cheers,
Moritz




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

Bug#672091: qpid-cpp: FTBFS: conftest.cpp:40: undefined reference to `dlopen'

[Cajus Pollmeier]

Hi,

these problems have already been fixed upstream. Waiting for 0.16 to be 
released.


Am 08.05.2012 13:43, schrieb Lucas Nussbaum:

Source: qpid-cpp
Version: 0.14-2
Severity: serious
Tags: wheezy sid
User: debian...@lists.debian.org
Usertags: qa-ftbfs-20120508 qa-ftbfs
Justification: FTBFS on amd64

Hi,

During a rebuild of all packages in sid, your package failed to build 
on

amd64.

Relevant part:
cc1: warning: command line option '-fno-rtti' is valid for 
C++/ObjC++ but not for C [enabled by default]

configure:9644: $? = 0
configure:9657: result: no
configure:9967: checking for gcc -std=gnu99 option to produce PIC
configure:9974: result: -fPIC -DPIC
configure:9982: checking if gcc -std=gnu99 PIC flag -fPIC -DPIC 
works
configure:1: gcc -std=gnu99 -c -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=format-security 
-D_FORTIFY_SOURCE=2 -fPIC -DPIC -DPIC conftest.c >&5

configure:10004: $? = 0
configure:10017: result: yes
configure:10046: checking if gcc -std=gnu99 static flag -static 
works

configure:10074: result: yes
configure:10089: checking if gcc -std=gnu99 supports -c -o file.o
configure:10110: gcc -std=gnu99 -c -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=format-security 
-D_FORTIFY_SOURCE=2 -o out/conftest2.o conftest.c >&5

configure:10114: $? = 0
configure:10136: result: yes
configure:10144: checking if gcc -std=gnu99 supports -c -o file.o
configure:10191: result: yes
configure:10224: checking whether the gcc -std=gnu99 linker 
(/usr/bin/ld -m elf_x86_64) supports shared libraries

configure:11382: result: yes
configure:11419: checking whether -lc should be explicitly linked in
configure:11427: gcc -std=gnu99 -c -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=format-security 
-D_FORTIFY_SOURCE=2 conftest.c >&5

configure:11430: $? = 0
configure:11445: gcc -std=gnu99 -shared  -fPIC -DPIC conftest.o  -v 
-Wl,-soname -Wl,conftest -o conftest 2\>\&1 \| /bin/grep  -lc  
\>/dev/null 2\>\&1

configure:11448: $? = 0
configure:11462: result: no
configure:11627: checking dynamic linker characteristics
configure:12141: gcc -std=gnu99 -o conftest -g -O2 -fstack-protector 
--param=ssp-buffer-size=4 -Wformat -Werror=format-security 
-D_FORTIFY_SOURCE=2 -Wl,-z,relro -Wl,-rpath -Wl,/foo conftest.c  >&5

configure:12141: $? = 0
configure:12367: result: GNU/Linux ld.so
configure:12474: checking how to hardcode library paths into 
programs

configure:12499: result: immediate
configure:13039: checking whether stripping libraries is possible
configure:13044: result: yes
configure:13079: checking if libtool supports shared libraries
configure:13081: result: yes
configure:13084: checking whether to build shared libraries
configure:13105: result: yes
configure:13108: checking whether to build static libraries
configure:13112: result: no
configure:13135: checking how to run the C++ preprocessor
configure:13162: g++ -E -D_FORTIFY_SOURCE=2 conftest.cpp
configure:13162: $? = 0
configure:13176: g++ -E -D_FORTIFY_SOURCE=2 conftest.cpp
conftest.cpp:29:28: fatal error: ac_nonexistent.h: No such file or 
directory

compilation terminated.
configure:13176: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "qpidc"
| #define PACKAGE_TARNAME "qpidc"
| #define PACKAGE_VERSION "0.14"
| #define PACKAGE_STRING "qpidc 0.14"
| #define PACKAGE_BUGREPORT "d...@qpid.apache.org"
| #define PACKAGE_URL ""
| #define PACKAGE "qpidc"
| #define VERSION "0.14"
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define __EXTENSIONS__ 1
| #define _ALL_SOURCE 1
| #define _GNU_SOURCE 1
| #define _POSIX_PTHREAD_SEMANTICS 1
| #define _TANDEM_SOURCE 1
| #define lint 1
| #define HAVE_DLFCN_H 1
| #define LT_OBJDIR ".libs/"
| /* end confdefs.h.  */
| #include 
configure:13201: result: g++ -E
configure:13221: g++ -E -D_FORTIFY_SOURCE=2 conftest.cpp
configure:13221: $? = 0
configure:13235: g++ -E -D_FORTIFY_SOURCE=2 conftest.cpp
conftest.cpp:29:28: fatal error: ac_nonexistent.h: No such file or 
directory

compilation terminated.
configure:13235: $? = 1
configure: failed program was:
| /* confdefs.h */
| #define PACKAGE_NAME "qpidc"
| #define PACKAGE_TARNAME "qpidc"
| #define PACKAGE_VERSION "0.14"
| #define PACKAGE_STRING "qpidc 0.14"
| #define PACKAGE_BUGREPORT "d...@qpid.apache.org"
| #define PACKAGE_URL ""
| #define PACKAGE "qpidc"
| #define VERSION "0.14"
| #define STDC_HEADERS 1
| #define HAVE_SYS_TYPES_H 1
| #define HAVE_SYS_STAT_H 1
| #define HAVE_STDLIB_H 1
| #define HAVE_STRING_H 1
| #define HAVE_MEMORY_H 1
| #define HAVE_STRINGS_H 1
| #define HAVE_INTTYPES_H 1
| #define HAVE_STDINT_H 1
| #define HAVE_UNISTD_H 1
| #define __EXTENSIONS__ 1
| #define _ALL_SOURCE 1
| #define _GNU_SOURCE 1
| #define _POSIX_PTHREAD_SEMANTICS 1
| #define

Bug#671933: ITP: python-lepl -- A Parser Library for Python

[Cajus Pollmeier]

Package: wnpp
Severity: wishlist

* Package name: python-lepl
  Version : 5.1.1
  Upstream Author : Andrew Cooke 
* URL : http://www.acooke.org/lepl/
* License : Dual licensed MPL/LGPL
  Programming Lang: Python
  Description : A Parser Library for Python

A recursive descent parser for Python 2.6+ (including 3). Lepl is powerful, 
simple to use, and easy to extend: grammars are written directly as Python 
code, using a syntax similar to BNF; new matchers can be simple functions.


signature.asc
Description: This is a digitally signed message part.

Bug#608920: gosa-plugin-ldapmanager: source code package not up to date

[Cajus Pollmeier]

Am Dienstag, 4. Januar 2011, 17:19:39 schrieben Sie:
> Package: gosa-plugin-ldapmanager
> Version: 2.6.11-3
> Severity: wishlist
> Tags: upstream
> 
> the source package seems to belong to a former version.

Hi,

this ticket looks outdated. The content of the package looks ok for me.

Please re-open if you disagree.

Cheers,
Cajus

-- 
Cajus Pollmeier  (Head of Development)
* GONICUS GmbH * Moehnestrasse 11-17 * D-59755 Arnsberg
* Tel.: +49 (0) 29 32 / 9 16 - 0 * Fax: +49 (0) 29 32 / 9 16 - 223
* http://www.GONICUS.de

* Sitz der Gesellschaft: Moehnestrasse 11-17 * D-59755 Arnsberg
* Geschaeftsfuehrer: Rainer Luelsdorf, Alfred Schroeder
* Vorsitzender des Beirats: Juergen Michels
* Amtsgericht Arnsberg * HRB 1968


signature.asc
Description: This is a digitally signed message part.

Bug#608918: gosa-plugin-ldapmanager: locale po file not in sync

[Cajus Pollmeier]

Am Dienstag, 4. Januar 2011, 17:13:58 schrieben Sie:
> Package: gosa-plugin-ldapmanager
> Version: 2.6.11-3
> Severity: wishlist
> Tags: l10n upstream
> 
> Hi,
> at least the german po file hasn't been updated during last revision - it
> doesn't match the changed content of contentcvs.tpl in the binary package.
> 
> Wolfgang

Hi,

this ticket looks outdated. The content of the package looks ok for me.

Please re-open if you disagree.

Cheers,
Cajus

-- 
Cajus Pollmeier  (Head of Development)
* GONICUS GmbH * Moehnestrasse 11-17 * D-59755 Arnsberg
* Tel.: +49 (0) 29 32 / 9 16 - 0 * Fax: +49 (0) 29 32 / 9 16 - 223
* http://www.GONICUS.de

* Sitz der Gesellschaft: Moehnestrasse 11-17 * D-59755 Arnsberg
* Geschaeftsfuehrer: Rainer Luelsdorf, Alfred Schroeder
* Vorsitzender des Beirats: Juergen Michels
* Amtsgericht Arnsberg * HRB 1968


signature.asc
Description: This is a digitally signed message part.

Bug#610174: gosa: fails to install,looks for lighttpd

[Cajus Pollmeier]

I'm closing this one due to being unreproducible and looking dead for some 
time now.

Am Sonntag, 16. Januar 2011, 13:37:46 schrieben Sie:
> Hello,
> 
> i just installed a fresh sid debian box to test the problem reported, here
> are my findings, i'am using aptitude like you have done for installing
> the programs
> 
> aptitude install gosa gosa-plugin-ssh = installing apache and php5 etc OK
> 
> aptitude purge gosa gosa-plugin-ssh = removing php5 etc OK
> 
> aptitude install lighttpd OK
> 
> aptitude install gosa gosa-plugin-ssh = install dependencies OK
> 
> aptitude purge gosa gosa-plugin-ssh = removing dependancies OK
> 
> so for me there is no problem here :)
> 
> if you still have to issue please give me a detailled way of reproducing
> it. If not i will close the bug as invalid
> 
> Cheers


-- 
Cajus Pollmeier  (Head of Development)
* GONICUS GmbH * Moehnestrasse 11-17 * D-59755 Arnsberg
* Tel.: +49 (0) 29 32 / 9 16 - 0 * Fax: +49 (0) 29 32 / 9 16 - 223
* http://www.GONICUS.de

* Sitz der Gesellschaft: Moehnestrasse 11-17 * D-59755 Arnsberg
* Geschaeftsfuehrer: Rainer Luelsdorf, Alfred Schroeder
* Vorsitzender des Beirats: Juergen Michels
* Amtsgericht Arnsberg * HRB 1968


signature.asc
Description: This is a digitally signed message part.

Bug#629573: getent passwd shows the gosa template

[Cajus Pollmeier]

I'm closing this one, because it's no bug. Please re-open if someone 
disagrees, please re-open.

Am Montag, 27. Juni 2011, 11:58:45 schrieben Sie:
> If you use templates, there's no way around the "special" filter,
> because templates are pseudo users.
> 
> Am Mittwoch, den 15.06.2011, 11:16 +0200 schrieb Andreas B. Mundt:
> > User: debian-...@lists.debian.org
> > Usertags: debian-edu
> > 
> > Hi,
> > 
> > On Tue, Jun 07, 2011 at 10:05:28PM +0200, Klaus Ade Johnstad wrote:
> > > Package: gosa
> > > Severity: normal
> > > 
> > > A getent password shows the gosa template also, like this:
> > > root@tjener:~# getent passwd
> > > newteacher:x:1001:1001:NewTeacher
> > > NewTeacher:/skole/tjener/home0/%uid:/bin/bash
> > > newstudent:x:1002:1002:NewStudent
> > > NewStudent:/skole/tjener/home0/%uid:/bin/bash
> > > 
> > > These template should not show up when doing a simple getent passwd.
> > 
> > It can be avoided by modifying /etc/nslcd.conf.  Here is the cfengine
> > rule (from the debian-edu-config package svn, cf/cf.ldapclient):
> > 
> > #   ## Avoid showing the GOsa template as user:
> > #   { /etc/nslcd.conf
> > #  AppendIfNoSuchLine "filter passwd
> > #   (&(objectClass=posixAccount)(!(objectClass=gosaUserTemplate)))"
> > #}
> > 
> > It's commented because we want to get rid of these rules.  If it's
> > unavoidable, we can switch it on.
> > 
> > Regards,
> > 
> > Andi


-- 
Cajus Pollmeier  (Head of Development)
* GONICUS GmbH * Moehnestrasse 11-17 * D-59755 Arnsberg
* Tel.: +49 (0) 29 32 / 9 16 - 0 * Fax: +49 (0) 29 32 / 9 16 - 223
* http://www.GONICUS.de

* Sitz der Gesellschaft: Moehnestrasse 11-17 * D-59755 Arnsberg
* Geschaeftsfuehrer: Rainer Luelsdorf, Alfred Schroeder
* Vorsitzender des Beirats: Juergen Michels
* Amtsgericht Arnsberg * HRB 1968


signature.asc
Description: This is a digitally signed message part.

Bug#629312: gosa says UID but means username.

[Cajus Pollmeier]

I'm closing this one, because it's no bug. Please re-open if someone 
disagrees, please re-open.

Am Montag, 27. Juni 2011, 11:24:00 schrieben Sie:
> The fileds UID, GIVENNAME and SURNAME represent the corresponding LDAP
> attributes. I tend to leave them as they are because the UID is the
> username used for log in.
> 
> Am Sonntag, den 05.06.2011, 16:39 +0200 schrieb Klaus Ade Johnstad:
> > Package: gosa
> > Severity: normal
> > 
> > In gosa ldap-manager the CSV-import page says one must include the
> > three fields UID, GIVENNAME and SURNAME. In reality it's not UID, but
> > username that is meant.
> > Please correct the wording.
> > 
> > -- System Information:
> > Debian Release: 6.0
> > 
> >   APT prefers stable
> >   APT policy: (500, 'stable')
> > 
> > Architecture: i386 (x86_64)
> > 
> > Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
> > Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8)
> > Shell: /bin/sh linked to /bin/dash


-- 
Cajus Pollmeier  (Head of Development)
* GONICUS GmbH * Moehnestrasse 11-17 * D-59755 Arnsberg
* Tel.: +49 (0) 29 32 / 9 16 - 0 * Fax: +49 (0) 29 32 / 9 16 - 223
* http://www.GONICUS.de

* Sitz der Gesellschaft: Moehnestrasse 11-17 * D-59755 Arnsberg
* Geschaeftsfuehrer: Rainer Luelsdorf, Alfred Schroeder
* Vorsitzender des Beirats: Juergen Michels
* Amtsgericht Arnsberg * HRB 1968


signature.asc
Description: This is a digitally signed message part.

Bug#651298: gosa-schema deploys NO schema files at all.

[Cajus Pollmeier]

It's not reproducible on my side. Please re-open if you think this is an 
error.


signature.asc
Description: This is a digitally signed message part.

Bug#662033: primary group filter (revisited)

[Cajus Pollmeier]

Am Samstag, 5. Mai 2012, 22:23:34 schrieben Sie:
> Hi Cajus,
> 
> I have looked at the primary group filter issue in gosa 2.6 again more
> closely and found the following filter definition:
> 
>   
>  checkbox
>  PRIMARY
>  true
>  
>  (!(objectClass=gosaObject))
>
> 
> So, this filter expects that all primary groups lack objectClass:
> gosaObject, but that all non-primary groups have objectClass:
> gosaObject set.
> 
> However, primary _and_ non-primary groups in gosa-2.6 get created with
> objectClass: gosaObject _not_ set. So the fix for this issue maybe
> introducing gosaObject as objectClass for non-primary groups(?).

That's not 100% correct. You've missed that the filter is or'ed. The gosaObject 
is just a trick to save hundreds of LDAP lookups. You can replace it by any 
object class that is not present inside a posix group.


signature.asc
Description: This is a digitally signed message part.

Bug#665950: Research/Questions on GOsa² issue: ,,unescaped arguments used on a command line''

[Cajus Pollmeier]

Hi Mike,

can you check if the patch does what you want. If so, I'll prepare a new 
upload.

Cheers,
Cajus


signature.asc
Description: This is a digitally signed message part.

Bug#670056: qpid-cpp: FTBFS on s390 ("error: ambiguous overload for 'operator=' ")

[Cajus Pollmeier]

Yes, I've seen that in the build logs already. These issues have been 
fixed upstream and there's a 0.16 in approximately 5 days. It fixes the 
other build failures (armel, etc.), too. I tend to just wait for that 
one.


Am 22.04.2012 18:19, schrieb Adam D. Barratt:

Source: qpid-cpp
Version: 0.14-2
Severity: serious
Tags: wheezy sid

Hi,

qpid-cpp FTBFS on s390.  From the most recent build log:

/bin/bash ../libtool --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H
-I. -I../include -I../include -I. -I=.  -D_FORTIFY_SOURCE=2 -Werror
-pedantic -Wall -Wextra -Wno-shadow -Wpointer-arith -Wcast-qual
-Wcast-align -Wno-long-long -Wvolatile-register-var -Winvalid-pch
-Wno-system-headers -Woverloaded-virtual
-DQPID_LIBEXEC_DIR=\"/usr/lib/qpid\" -DBOOST_FILESYSTEM_VERSION=2 -g
-O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Wformat-security -Werror=format-security -c -o
qpid/broker/MessageGroupManager.lo 
qpid/broker/MessageGroupManager.cpp

libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../include -I../include
-I. -I=. -D_FORTIFY_SOURCE=2 -Werror -pedantic -Wall -Wextra
-Wno-shadow -Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long
-Wvolatile-register-var -Winvalid-pch -Wno-system-headers
-Woverloaded-virtual -DQPID_LIBEXEC_DIR=\"/usr/lib/qpid\"
-DBOOST_FILESYSTEM_VERSION=2 -g -O2 -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Wformat-security
-Werror=format-security -c qpid/broker/MessageGroupManager.cpp  -fPIC
-DPIC -o qpid/broker/.libs/MessageGroupManager.o
qpid/broker/MessageGroupManager.cpp: In member function 'virtual void
qpid::broker::MessageGroupManager::query(qpid::types::Variant::Map&)
const':
qpid/broker/MessageGroupManager.cpp:283:56: error: ambiguous overload
for 'operator=' in 'info.std::map<_Key, _Tp, _Compare,
_Alloc>::operator[] [with _Key = std::basic_string, _Tp =
qpid::types::Variant, _Compare = std::less >,
_Alloc = std::allocator,
qpid::types::Variant> >, std::map<_Key, _Tp, _Compare,
_Alloc>::mapped_type = qpid::types::Variant, std::map<_Key, _Tp,
_Compare, _Alloc>::key_type = std::basic_string]((* &
{anonymous}::GROUP_MSG_COUNT)) =
g.std::tr1::__detail::_Hashtable_const_iterator<_Value,
__constant_iterators, __cache>::operator-> [with _Value =
std::pair,
qpid::broker::MessageGroupManager::GroupState>, bool
__constant_iterators = false, bool __cache = false,
std::tr1::__detail::_Hashtable_const_iterator<_Value,
__constant_iterators, __cache>::pointer = const std::pair,
qpid::broker::MessageGroupManager::GroupState>*]()->std::pair,

qpid::broker::MessageGroupManager::GroupState>::second.qpid::broker::MessageGroupManager::GroupState::members.std::deque<_Tp,
_Alloc>::size [with _Tp = qpid::framing::SequenceNumber, _Alloc =
std::allocator, std::deque<_Tp,
_Alloc>::size_type = long unsigned int]()'
qpid/broker/MessageGroupManager.cpp:283:56: note: candidates are:
../include/qpid/types/Variant.h:100:32: note: qpid::types::Variant&
qpid::types::Variant::operator=(bool)
../include/qpid/types/Variant.h:101:32: note: qpid::types::Variant&
qpid::types::Variant::operator=(uint8_t)
../include/qpid/types/Variant.h:102:32: note: qpid::types::Variant&
qpid::types::Variant::operator=(uint16_t)
../include/qpid/types/Variant.h:103:32: note: qpid::types::Variant&
qpid::types::Variant::operator=(uint32_t)
../include/qpid/types/Variant.h:104:32: note: qpid::types::Variant&
qpid::types::Variant::operator=(uint64_t)
../include/qpid/types/Variant.h:105:32: note: qpid::types::Variant&
qpid::types::Variant::operator=(int8_t)
../include/qpid/types/Variant.h:106:32: note: qpid::types::Variant&
qpid::types::Variant::operator=(int16_t)
../include/qpid/types/Variant.h:107:32: note: qpid::types::Variant&
qpid::types::Variant::operator=(int32_t)
../include/qpid/types/Variant.h:108:32: note: qpid::types::Variant&
qpid::types::Variant::operator=(int64_t)
../include/qpid/types/Variant.h:109:32: note: qpid::types::Variant&
qpid::types::Variant::operator=(float)
../include/qpid/types/Variant.h:110:32: note: qpid::types::Variant&
qpid::types::Variant::operator=(double)
../include/qpid/types/Variant.h:115:32: note: qpid::types::Variant&
qpid::types::Variant::operator=(const qpid::types::Variant&)
../include/qpid/types/Variant.h:116:32: note: qpid::types::Variant&
qpid::types::Variant::operator=(const qpid::types::Uuid&)
make[4]: *** [qpid/broker/MessageGroupManager.lo] Error 1
make[4]: Leaving directory
`/build/buildd-qpid-cpp_0.14-2-s390-V8Rr8u/qpid-cpp-0.14/src'
make[3]: *** [all-recursive] Error 1
make[3]: Leaving directory
`/build/buildd-qpid-cpp_0.14-2-s390-V8Rr8u/qpid-cpp-0.14/src'
make[2]: *** [all] Error 2
make[2]: Leaving directory
`/build/buildd-qpid-cpp_0.14-2-s390-V8Rr8u/qpid-cpp-0.14/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory
`/build/buildd-qpid-cpp_0.14-2-s390-V8Rr8u/qpid-cpp-0.14'
dh_auto_build: make -j1 returned exit code 2
make: *** [build-arch] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit 
status 2


Full logs available via
https://buildd.de

Bug#662033: Primary Group Filter in GOsa²'s group management view fails to work

[Cajus Pollmeier]

Am Dienstag, 6. März 2012, 09:57:42 schrieben Sie:
> Hi Cajus,
> 
> On Mo 05 Mär 2012 08:29:36 CET Cajus Pollmeier wrote:
> > Am Samstag, 3. März 2012, 19:54:06 schrieben Sie:
> >> Package: gosa
> >> Severity: important
> >> Version: 2.6.11-3+squeeze1
> >> 
> >> in the right part of the GOsa² GUI layout there is a view filter to
> >> filter out objects in GOsa²/LDAP. For the group management, it is
> >> possible to filter out primary groups (which can be many if every user
> >> has his/her own primary POSIX group).
> >> 
> >> This filter switch, however, fails to work in GOsa² 2.6.11 (as in
> >> Debian squeeze and used for Debian Edu).
> > 
> > Please detail why you think that it does not work. There were some
> > misunderstandings of this switch in the past.
> 
> The primary groups (to my understanding) are those groups that are
> used in the 4th field of /etc/passwd entries. On Debian, these groups
> get created on user creation and they normally bear the same name as
> the user. Home directories also get create with ownership and
> groupship for this = tuple.
> 
> The mass import of GOsa² 2.6 creates posixAccounts and per
> posixAccount one posixGroup. These groups being created I consider as
> primary groups.
> 
> For a school with 600 students these groups are many in occurrence and
> they are mostly not needed for system administration (only to grant
> access to individual homes, which is not a common use case here
> around). It would be good to be able to hide those in the GOsa²-WebGUI
> on a Debian Edu system.

Hi Mike,

sorry for beeing late ;-)

Ok. There is the filter named "Show primary groups". If you uncheck that box, 
you'll not see all primary groups. That's how it is in 2.6.11 available in 
squeeze. Just checked it, because I didn't use 2.6.x for some time now. For me 
it works fine. Working fine means, that all primary groups disappear from the 
list.

So what "does not work" mean in detail? Is there a special setup that makes 
the filters stop working? Is there an easy way for me to reproduce it? I.e. 
minimum ldap setup + ldif + gosa.conf?
 
> >> I tag this issue as important as it highly reduces usability of GOsa²
> >> with Debian Edu for large setups (i.e. schools).
> >> 
> >> I hope to come up with a patch soon... Does anyone know if this issue
> >> occurs with GOsa² 2.7.x in Debian sid?
> > 
> > 2.7 releases do have a revised filtering. There's no filter like
> > that anymore.
> 
> Hmmm ok... does this mean, that I will not be able to hide these
> many many groups from the administrator? Any other approach available?

The filter are user defineable beeing bound to a filter class. In the moment, 
there's a groupLDAPFilter, but it doesn't filter out primary groups. The 
feature has been dropped some time ago, because it is a big performance issue:

To get the list of primary groups, you've to check for all users, and get 
their gidNumber. Then you've to search for all posixGroups inside the current 
scope and eliminate these groups with these gidNumbers.

For big environments, this cannot be done with just two LDAP searcher, because 
it will exceed the maximum size of query strings. So you've to either split 
into multiple queries or do this manually in the code. That's where the filter 
does not finish in a reasonable timeframe if having multiple 1k's of users.

If you want this feature back (maybe as a group filter extension), please open 
a ticket on oss.gonicus.de. We'll add it back if it's really required.

Cheers,
Cajus


signature.asc
Description: This is a digitally signed message part.

Bug#653562: Fix for non-DNS-compliant host names in GOsa²

[Cajus Pollmeier]

Am Samstag, 3. März 2012, 18:41:01 schrieben Sie:
> Hi Caius,
> 
> Could you please check, if GOsa² 2.7.x in Debian sid also contains
> such a fix for this issue?
> https://forge.fusiondirectory.org/projects/fd/repository/revisions/136a4f59
> a0315b4e2314657b2643f1ee6b1298c4/diff/include/class_tests.inc

Mike,

2.7 does not allow an underscore there - and additionally does a couple of 
additional checks there.

To be nitpicking, the fusiondirectory fix is only working for hostnames, but 
not for dns names. It just removes the underscore from the list of valid 
characters, but at the time of checking the provided string may be a complete 
DNS name. And underscores are in fact allowed for domain names (RFC 1034, 
Preferred name syntax). Thats why 2.6 initially allowed the underscore.

Cheers,
Cajus


signature.asc
Description: This is a digitally signed message part.

Bug#662033: Primary Group Filter in GOsa²'s group management view fails to work

[Cajus Pollmeier]

Am Samstag, 3. März 2012, 19:54:06 schrieben Sie:
> Package: gosa
> Severity: important
> Version: 2.6.11-3+squeeze1
> 
> Hi all,
> 
> in the right part of the GOsa² GUI layout there is a view filter to
> filter out objects in GOsa²/LDAP. For the group management, it is
> possible to filter out primary groups (which can be many if every user
> has his/her own primary POSIX group).
> 
> This filter switch, however, fails to work in GOsa² 2.6.11 (as in
> Debian squeeze and used for Debian Edu).

Please detail why you think that it does not work. There were some 
misunderstandings of this switch in the past.
 
> I tag this issue as important as it highly reduces usability of GOsa²
> with Debian Edu for large setups (i.e. schools).
> 
> I hope to come up with a patch soon... Does anyone know if this issue
> occurs with GOsa² 2.7.x in Debian sid?

2.7 releases do have a revised filtering. There's no filter like that anymore.

Cheers,
Cajus


signature.asc
Description: This is a digitally signed message part.

Bug#650258: Squeeze-Update

[Cajus Pollmeier]

Am Dienstag, 24. Januar 2012, 14:22:16 schrieben Sie:
> Hi Cajus,
> 
> thanks for fixing the dhcpHost removal issue in SID. Will you prepare
> the update for squeeze? Or shall I provide a debdiff and communicate
> with debian-release?

Hi Mike,

it would be very very cool if you could take over the communication. The patch 
should be attached somewhere to the bug - so, if you need something more, just 
tell me.

Additionally, there's another bug open from the Debian edu team. Maybe these 
both can be combined?

Thanks,
Cajus


signature.asc
Description: This is a digitally signed message part.

Bug#657086: gosa: Should use characters in idGenerator rule, not bytes

[Cajus Pollmeier]

Am Montag, 23. Januar 2012, 23:28:33 schrieben Sie:
> Package: gosa
> Version: 2.6.11-3
> Severity: important
> User: debian-...@lists.debian.org
> Usertags: debian-edu
> 
> I discovered this problem in Debian Edu/Squeeze.  When a user with a
> non-ASCII character in the third position of the first or last name is
> created, the generated username contain a non-valid UTF-8 character.
> 
> In Debian Edu, our gosa.conf contain the following rule:
> idGenerator="{%givenName[3-6]}{%sn[3-6]}".
> 
> When using UTF-8, the range [3-6] at the moment do not refer to
> characters, but bytes in the UTF-8 string.  This caused the user 'Gunnar
> Grændal' to get a propsed username with gungr?, where ? was half the
> UTF-8 bytestream for æ.  I believe it would be better if [3-6] refered
> to characters 3-6, not bytes 3-6.
> 
> As non-ASCII usernames can cause problem when trying to log in to
> different systems, I believe it would be best if usernames are always
> converted to ASCII, preferably using the //TRANSLIT rule in glibc.
> 
> For the example above, one would then end up with "echo gungræ | iconv
> -t ASCII//TRANSLIT" = gungrae as the proposed username.

While it is discussable why this bug is "important", 2.7.x packages do the 
conversation in another way:

 $value = iconv('UTF-8', 'US-ASCII//TRANSLIT', $value);

Same for the 2.6.x maintainance series. You can simply take the function 
gen_uids from here

https://oss.gonicus.de/labs/gosa/browser/tags/2.6.13/gosa-
core/include/functions.inc

in order to create a patch for squeeze.

HTH,
Cajus


signature.asc
Description: This is a digitally signed message part.

Bug#573859: Not build-able

[Cajus Pollmeier]

Even more TODOs: it only builds against xqilla 2.2 series - which is not 
available in unstable as of mid december. Either upstream plans to move to a 
newer version, or it has to be ported, or statically linked, or just not 
packaged.


signature.asc
Description: This is a digitally signed message part.

Bug#650258: 2nd status ping on ,,dhcpHost not removed if system is removed''

[Cajus Pollmeier]

Am Sonntag, 22. Januar 2012, 00:36:27 schrieben Sie:
> Hi Cajus,
> 
> this is a second status ping on the ,,dhcpHost not removed if system
> is removed'' issue with GOsa² in Debian sid and squeeze.
> 
> To be able to upload a fix for this to Debian squeeze this bug has to
> be fixed in Debian sid.
> 
> The Debian Edu team is really desperate for this fix to be introduced
> into Debian squeeze.
> 
> If you need any help with this, please let me/us know.
> 
> Thanks!!!
> Mike

Sorry for the delay, Mike. We've already prepared a new release with a couple 
of fixes including this one. Will be uploaded on monday. Promised! ;-)

Cheers,
Cajus


signature.asc
Description: This is a digitally signed message part.

Bug#655151: python-newt: ImportError: No module named _snack

[Cajus Pollmeier]

Hiho,

at least on my system it doesn't seem to be fixed:

8<---
cajus@frost:~$ dpkg -l python-newt
ii  python-newt 0.52.14-6   NEWT module for 
Python
cajus@frost:~$ python
Python 2.7.2+ (default, Jan 10 2012, 21:52:50) 
[GCC 4.6.2] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import snack
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python2.7/dist-packages/snack.py", line 42, in 
import _snack
ImportError: No module named _snack
>>>
8<---

I'm on amd64, too.


signature.asc
Description: This is a digitally signed message part.

Bug#653053: ldap2zone: Sending email every hour fill up the mail spool

[Cajus Pollmeier]

Am Donnerstag, 5. Januar 2012, 16:16:06 schrieben Sie:
> Hi,
> 
> so I have this (also attached), it builds + works fine, may I upload?
> 
> $ debdiff ldap2zone_0.1-7.dsc ldap2zone_0.1-7.1.dsc
> diff -u ldap2zone-0.1/debian/changelog ldap2zone-0.1/debian/changelog
> --- ldap2zone-0.1/debian/changelog
> +++ ldap2zone-0.1/debian/changelog
> @@ -1,3 +1,13 @@
> +ldap2zone (0.1-7.1) stable-proposed-updates; urgency=low
> +
> +  * Non-maintainer upload.
> +  * Include half the patch from #653053 to silence the cronjob on success,
> to +avoid excessive emails and instead log this with syslog.
> +The full patch has been accepted by the maintainer and is already in
> +wheezy and sid in version 0.2-2. (Closes: #653053)
> +
> + -- Holger Levsen   Thu, 05 Jan 2012 15:59:49 +0100
> +
>  ldap2zone (0.1-7) unstable; urgency=low
> 
>* Corrected error in notify dns statement breaking the program
> diff -u ldap2zone-0.1/debian/patches/00list
> ldap2zone-0.1/debian/patches/00list
> --- ldap2zone-0.1/debian/patches/00list
> +++ ldap2zone-0.1/debian/patches/00list
> @@ -9,0 +10 @@
> +11_be_silent_on_success_653053
> only in patch2:
> unchanged:
> --- ldap2zone-0.1.orig/debian/patches/11_be_silent_on_success_653053.dpatch
> +++ ldap2zone-0.1/debian/patches/11_be_silent_on_success_653053.dpatch
> @@ -0,0 +1,21 @@
> +#! /bin/sh /usr/share/dpatch/dpatch-run
> +## 11_be_silent_on_success_653053.dpatch by Holger Levsen
>  +##
> +## All lines beginning with `## DP:' are a description of the patch.
> +## DP: Made script log using logger by a patch contributed by
> +## DP: Petter Reinholdtsen
> +## DP: modified to only do this on success for squeeze by Holger Levsen
> +## DP: see #653053
> +
> +@DPATCH@
> +
> +
> +--- ldap2zone-0.2.orig/ldap2bind
>  ldap2zone-0.2/ldap2bind
> +@@ -85,6 +85,6 @@
> +   printf "Reloading the zone '$domain' failed: $result\n"
> 1>&2 +   else
> +-  printf "Reloading the zone '$domain' was successful\n" 1>&2
> ++  logger -t ldap2bind "Reloading the zone '$domain' was
> successful\n"
> +   fi
> + done
> 
> 
> cheers,
>   Holger

Hi Holger,

for me, this is OK - but I'm not the last instance ;-)

Cheers,
Cajus


signature.asc
Description: This is a digitally signed message part.

Bug#628207: Announce of the upcoming NMU for the fts package

[Cajus Pollmeier]

Am Montag, 2. Januar 2012, 10:14:06 schrieben Sie:
> Dear maintainer of fts and Debian translators,
> 
> Some days ago, I sent a notice to the maintainer of the fts Debian
> package, mentioning the status of at least one old po-debconf translation
> update in the BTS.
> 
> I announced the intent to build and possibly upload a non-maintainer upload
> for this package in order to fix this long-time pending localization
> bug as well as all other pending translations.
> 
> The package maintainer agreed for the NMU or did not respond in four
> days, so I will proceed with the NMU.
> 
> The full planned schedule is available at the end of this mail.
> 
> The package is currently translated to:
> cs de es fr it ja pt pt_BR ru sk sv vi zh_CN
> 
> Among these, the following translations are incomplete: it ja pt_BR sk vi
> zh_CN
> 
> If you did any of the, currently incomplete, translations you will get
> ANOTHER mail with the translation to update.
> 
> Other translators also have the opportunity to create new translations
> for this package. Once completed, please send them as a bug report
> against the fts package so I can incorporate them in the build.
> 
> The deadline for receiving updates and new translations is Tuesday, January
> 10, 2012. If you are not in time you can always send your translation to
> the BTS.
> 
> The POT file is attached to this mail.
> 
> If the maintainer objects to this process I will immediately abort my NMU
> and send him/her all updates I receive.
> 
> Otherwise the following will happen (or already has):
> 
>  Wednesday, December 28, 2011   : send the first intent to NMU notice to
>  the package maintainer.
>  Monday, January 02, 2012   : send this notice
>  Tuesday, January 10, 2012   : (midnight) deadline for receiving
> translation updates Wednesday, January 11, 2012   : build the package
> and upload it to DELAYED/7-day send the NMU patch to the BTS
>  Wednesday, January 18, 2012   : NMU uploaded to incoming
> 
> Thanks for your efforts and time.

Hi Christian,

feel free to NMU. There's a bunch of stuff going on here in the moment, so that 
I'll not be able to do the upload myself within the next days.

Thanks!
Cajus


signature.asc
Description: This is a digitally signed message part.

Bug#650258: Status-Ping on this issue

[Cajus Pollmeier]

Am Montag, 2. Januar 2012, 10:52:54 schrieben Sie:
> Hi Cajus et al.
> 
> this is a status-query-ping for this issue. The Debian Edu team is
> about to release beta2 (within only 2 weeks after beta1) and this bug
> is problematic for a clean GOsa² setup in our schools...
> 
> Happy new year!!!

Same to you! Sadly, I did not find the time to update the unstable packages 
until now. Hopefully I'll have some this week.

Cheers,
Caus


signature.asc
Description: This is a digitally signed message part.

Bug#653795: FTBFS with Boost 1.48: error: boost/pool/detail/singleton.hpp: No such file or directory

[Cajus Pollmeier]

Ok. I've seen that in the qpid bugtracker already and I've patched it. 
While re-building, I've noticed that libboost-all-dev installs 1.46 
boost packages. Did you use libboost1.48-all-dev or is there something 
wrong on my side?


$ apt-cache show libboost-all-dev
Package: libboost-all-dev
Source: boost-defaults
Version: 1.48.0.2
Installed-Size: 26
Maintainer: Debian Boost Team 
Architecture: amd64
Depends: libboost-dev, libboost-date-time-dev, libboost-filesystem-dev, 
libboost-graph-dev, libboost-graph-parallel-dev, libboost-iostreams-dev, 
libboost-math-dev, libboost-mpi-dev, libboost-mpi-python-dev, 
libboost-program-options-dev, libboost-python-dev, libboost-regex-dev, 
libboost-serialization-dev, libboost-signals-dev, libboost-system-dev, 
libboost-test-dev, libboost-thread-dev, libboost-wave-dev
Description: Boost C++ Libraries development files (ALL, default 
version)

 The Boost web site provides free, peer-reviewed, portable C++ source
 libraries. The emphasis is on libraries which work well with the C++
 Standard Library. One goal is to establish "existing practice" and
 provide reference implementations so that the Boost libraries are
 suitable for eventual standardization. Some of the libraries have
 already been proposed for inclusion in the C++ Standards Committee's
 upcoming C++ Standard Library Technical Report.
 .
 This package provides the complete Boost development environment,
 including all separately-packaged libraries.
 .
 This package is a dependency package, which depends on Debian's 
default

 Boost version (currently 1.46).
Homepage: http://www.boost.org/
Tag: devel::library
Section: libdevel
Priority: optional
Filename: 
pool/main/b/boost-defaults/libboost-all-dev_1.48.0.2_amd64.deb

Size: 2928
MD5sum: abfef854f6f4669bc367b8b0b43fb448
SHA1: 28b62a6284ba585538b0d93e073ac045a9be8ed8
SHA256: 
b2955ffa2b560e8d9dc55cf8a9e7ffad2b0a0f997e2dd1ef444e67bedfa78f9b


and

$ sudo apt-get install libboost-all-dev
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following extra packages will be installed:
  gccxml libboost-date-time-dev libboost-date-time1.46-dev 
libboost-date-time1.46.1 libboost-dev libboost-filesystem-dev
  libboost-filesystem1.46-dev libboost-graph-dev 
libboost-graph-parallel-dev libboost-graph-parallel1.46-dev
  libboost-graph-parallel1.46.1 libboost-graph1.46-dev 
libboost-graph1.46.1 libboost-iostreams-dev libboost-iostreams1.46-dev
  libboost-math-dev libboost-math1.46-dev libboost-math1.46.1 
libboost-mpi-dev libboost-mpi-python-dev libboost-mpi1.46-dev
  libboost-mpi1.46.1 libboost-program-options-dev 
libboost-program-options1.46-dev libboost-python-dev 
libboost-python1.46-dev
  libboost-regex-dev libboost-regex1.46-dev libboost-serialization-dev 
libboost-serialization1.46-dev libboost-serialization1.46.1
  libboost-signals-dev libboost-signals1.46-dev libboost-system-dev 
libboost-system1.46-dev libboost-test-dev libboost-test1.46-dev
  libboost-test1.46.1 libboost-thread-dev libboost-thread1.46-dev 
libboost-wave-dev libboost-wave1.46-dev libboost-wave1.46.1
  libboost1.46-dev libibverbs-dev libibverbs1 libicu-dev libnuma1 
libopenmpi-dev libopenmpi1.3 libtorque2 mpi-default-dev

  openmpi-common
Suggested packages:
  libboost1.46-doc libboost-random1.46-dev xsltproc doxygen default-jdk 
fop icu-doc


Am 31.12.2011 01:56, schrieb Steve M. Robbins:

Source: qpid-cpp
Version: 0.12-3
Severity: normal

Package failed to build with new Boost 1.48:

libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../include -I../include
-I. -I=. -D_FORTIFY_SOURCE=2 -Werror -pedantic -Wall -Wextra
-Wno-shadow -Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long
-Wvolatile-register-var -Winvalid-pch -Wno-system-headers
-Woverloaded-vi
rtual -DQPID_LIBEXEC_DIR=\"/usr/lib/qpid\"
-DBOOST_FILESYSTEM_VERSION=2 -g -O2 -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Wformat-security
-Werror=format-security -c qpid/framing/Uuid.cpp  -fPIC -DPIC -o
qpid/framing/.libs/Uuid.o
/bin/bash ../libtool --tag=CXX   --mode=compile g++ -DHAVE_CONFIG_H
-I. -I../include -I../include -I. -I=.  -D_FORTIFY_SOURCE=2 -Werror
-pedantic -Wall -Wextra -Wno-shadow -Wpointer-arith -Wcast-qual
-Wcast-align -Wno-long-long -Wvolatile-register-var -Winvalid-pch
-Wno-
system-headers -Woverloaded-virtual
-DQPID_LIBEXEC_DIR=\"/usr/lib/qpid\" -DBOOST_FILESYSTEM_VERSION=2 -g
-O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat
-Wformat-security -Werror=format-security -c -o qpid/log/Logger.lo
qpid/log/Logger.cpp
libtool: compile:  g++ -DHAVE_CONFIG_H -I. -I../include -I../include
-I. -I=. -D_FORTIFY_SOURCE=2 -Werror -pedantic -Wall -Wextra
-Wno-shadow -Wpointer-arith -Wcast-qual -Wcast-align -Wno-long-long
-Wvolatile-register-var -Winvalid-pch -Wno-system-headers
-Woverloaded-vi
rtual -DQPID_LIBEXEC_DIR=\"/usr/lib/qpid\"
-DBOOST_FILESYSTEM_VERSION=2 -g -O2 -fstack-protector
--param=ssp-buffer-size=4 -Wformat -Wformat-security
-Werror=format-security -c qpid/log/Logger.c

Bug#653053: ldap2zone: Sending email every hour fill up the mail spool

[Cajus Pollmeier]

It does not close the bug for squeeze ;-) To have it fixed we need to
comunicate with the release team. Which will not be possible for me
within the remaining time in this year...

Am Freitag, den 23.12.2011, 10:31 +0100 schrieb Petter Reinholdtsen:
> [Cajus Pollmeier]
> > I've changed that in 0.2-2 - which doesn't help for squeeze in the
> > moment.
> 
> Do you need help preparing a fix for squeeze?  See
> http://wiki.debian.org/StableUpdates > and
> http://wiki.debian.org/StableProposedUpdates >.
> 
> PS: you forgot to add (Closes: #) in the changelog of your latest
> upload.



signature.asc
Description: This is a digitally signed message part

Bug#653053: ldap2zone: Sending email every hour fill up the mail spool

[Cajus Pollmeier]

I've changed that in 0.2-2 - which doesn't help for squeeze in the
moment.

Am Freitag, den 23.12.2011, 08:35 +0100 schrieb Petter Reinholdtsen:
> Package: ldap2zone
> Version: 0.1-7
> Severity: important
> Tags: patch
> User: debian-...@lists.debian.org
> Usertags: debian-edu
> 
> I discovered this problem on a freshly installed Debian Edu main-server.
> The mail box for the root user is quickly filling up with emails from
> the cron job ldap2zone, calling /usr/sbin/ldap2bind at boot and every
> hour and causing an email with this content to be sent:
> 
>   Reloading the zone '0.168.192.in-addr.arpa.' was successful
>   Reloading the zone '10.in-addr.arpa.' was successful
>   Reloading the zone '1.168.192' was successful
>   Reloading the zone 'intern' was successful
>   Reloading the zone 'subnet00.intern' was successful
>   Reloading the zone 'subnet01.intern' was successful
> 
> This behaviour is going to fill up /var/ on Debian Edu servers, causing
> Debian Edu servers to fail after a short time.  I'm setting severity to
> important though this problem would be critical to fix for Debian Edu.
> 
> Please change the cron job in Debian/Squeeze to only send emails on
> errors or not at all, and redirect the output on successful runs to
> /var/log/ somewhere.  I would recommend rewriting the script to syslog
> messages instead of printing to stdout.  This can be done by replacing
> echo/printf with 'logger -t ldap2bind'.
> 
> This patch would solve the problem.  It might be a good idea to convert
> some of the other echo/print statemets to log to syslog as well.
> 
> --- ldap2zone-0.1.orig/debian/patches/05_correct_bashisms_ldap2bind.dpatch
> 2011-12-23 08:28:53.0 +0100
> +++ ldap2zone-0.1/debian/patches/05_correct_bashisms_ldap2bind.dpatch 
> 2011-12-23 08:31:22.999519872 +0100
> @@ -26,8 +26,8 @@
>   result=$($rndc reload $domain 2>&1)
>   if [ $? -ne 0 ]; then
>  -echo -e "Reloading the zone '$domain' failed:\n$result" 1>&2
> -+printf "Reloading the zone '$domain' failed: $result\n" 1>&2
> ++logger -t ldap2bind "Reloading the zone '$domain' failed: 
> $result\n"
>  +else
> -+printf "Reloading the zone '$domain' was successful\n" 1>&2
> ++logger -t ldap2bind "Reloading the zone '$domain' was 
> successful\n"
>   fi
>   done



signature.asc
Description: This is a digitally signed message part

Bug#651298: gosa-schema deploys NO schema files at all.

[Cajus Pollmeier]

Am Mittwoch, 7. Dezember 2011, 14:47:51 schrieben Sie:
> Package: gosa-schema
> Version: 2.6.11-3
> Severity: normal
> 
> gosa-schema deploys NO schema files, which are needed to run gosa tool.
> 
> # dpkg -L gosa-schema
> /etc/ldap/schema/gosa/goto.schema
> /etc/ldap/schema/gosa/gosystem.schema
> /etc/ldap/schema/gosa/rfc2307bis.schema
> /etc/ldap/schema/gosa/goserver.schema
> /etc/ldap/schema/gosa/gosa-samba3.schema
> /etc/ldap/schema/gosa/trust.schema
> /etc/ldap/schema/gosa/gofon.schema
> /etc/ldap/schema/gosa/gofax.schema
> /etc/ldap/schema/gosa/samba3.schema
> /etc/ldap/schema/gosa/goto-mime.schema
> 
> But:
> # ls -l /etc/ldap/schema/gosa
> total 0
> 
> 
> 
> -- System Information:
> Debian Release: 6.0.3
>   APT prefers stable
>   APT policy: (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 2.6.32-5-amd64 (SMP w/3 CPU cores)
> Locale: LANG=lt_LT.utf8, LC_CTYPE=lt_LT.utf8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash

Sorry, I cannot reproduce this:

cajus@frost:~$ sudo dpkg -i gosa-schema_2.6.11-3_all.deb 
[sudo] password for cajus: 
Vormals nicht ausgewähltes Paket gosa-schema wird gewählt.
(Lese Datenbank ... 146346 Dateien und Verzeichnisse sind derzeit 
installiert.)
Entpacken von gosa-schema (aus gosa-schema_2.6.11-3_all.deb) ...
gosa-schema (2.6.11-3) wird eingerichtet ...
cajus@frost:~$ ls -la /etc/ldap/schema/gosa/
insgesamt 115
drwxr-xr-x 2 root root  1024 Dez 12 09:31 .
drwxr-xr-x 3 root root  1024 Dez 12 09:31 ..
-rw-r--r-- 1 root root  3284 Aug  6  2010 gofax.schema
-rw-r--r-- 1 root root 13033 Aug  6  2010 gofon.schema
-rw-r--r-- 1 root root 16874 Aug  6  2010 gosa-samba3.schema
-rw-r--r-- 1 root root 20352 Aug  6  2010 goserver.schema
-rw-r--r-- 1 root root 12910 Aug  6  2010 gosystem.schema
-rw-r--r-- 1 root root  2604 Aug  6  2010 goto-mime.schema
-rw-r--r-- 1 root root  7150 Aug  6  2010 goto.schema
-rw-r--r-- 1 root root  9549 Aug  6  2010 rfc2307bis.schema
-rw-r--r-- 1 root root 20221 Aug  6  2010 samba3.schema
-rw-r--r-- 1 root root   783 Aug  6  2010 trust.schema

Did you remove them some time ago? Did you try "apt-get remove --purge gosa-
schema && apt-get install gosa-schema"?

-- 
Cajus Pollmeier  (Head of Development)
* GONICUS GmbH * Moehnestrasse 11-17 * D-59755 Arnsberg
* Tel.: +49 (0) 29 32 / 9 16 - 0 * Fax: +49 (0) 29 32 / 9 16 - 223
* http://www.GONICUS.de

* Sitz der Gesellschaft: Moehnestrasse 11-17 * D-59755 Arnsberg
* Geschaeftsfuehrer: Rainer Luelsdorf, Alfred Schroeder
* Vorsitzender des Beirats: Juergen Michels
* Amtsgericht Arnsberg * HRB 1968


signature.asc
Description: This is a digitally signed message part.

Bug#650258: Version information

[Cajus Pollmeier]

Am Montag, den 05.12.2011, 08:29 +0100 schrieb Mike Gabriel:
> version #650258 2.6.11-3 + 2.7.2-1
> thanks
> 
> Hi all,
> 
> Caius asked me to update the version information for this reported issue.
> 
> The problem description applies to GOsa² 2.6.11-3 as in Debian squeeze  
> (20111205) and 2.7.2-1 as in Debian sid (20111205) and also to all  
> available upstream development versions.
> 
> FusionDirectory upstream (Git):
> https://github.com/fusiondirectory/fusiondirectory-plugins/blob/master/systems/admin/systems/class_termDNS.inc
> 
> and GOsa² upstream Git (3.0-alpha something):
> https://github.com/cajus/gosa-gui/blob/master/plugins/systems/src/systemsPlugin/class_termDNS.inc
> 
> Thanks
> Mike

FusionDirectory is not maintained by the GOsa team and has no relation
to this package. I'm not sure why you're referencing to it...

GOsa upstream is here: 

https://oss.gonicus.de/repositories/gosa/branches/2.6
https://oss.gonicus.de/repositories/gosa/branches/2.7

The problem has been fixed upstream already (2.6, 2.7 and trunk), but
there's no upload yet.

Cheers,
Cajus


signature.asc
Description: This is a digitally signed message part

Bug#650258: dhcpHost not removed if system is removed

[Cajus Pollmeier]

Am Montag, 28. November 2011, 11:14:30 schrieben Sie:
> Package: gosa
> Severity: important
> Tags: patch
> 
> User: debian-...@lists.debian.org
> UserTags: debian-edu
> 
> If you remove a system from GOsa that had DHCP enabled then the
> dhcpHost entry is not removed from the dhcpService configuration.
> 
> A more accurate description on how to produce this issue (and a patch)
> is given here:
> https://forge.fusiondirectory.org/issues/553
> 
> It would be great to have this patch applied as an update for GOsa 2.6
> in Debian squeeze as it is relevant to Debian Edu squeeze. Thanks!
> 
> The patch is also attached to this issue report.
> 
> Greets,
> Mike

Hi Mike,

thanks for reporting the bug. Will check that one, but I'm not sure if it 
justifies the severity "important" and an upload to stable. We will see.

Cheers,
Cajus


signature.asc
Description: This is a digitally signed message part.

Bug#573859: Berkeley DB XML library packaging

[Cajus Pollmeier]

I've continued to work on the package, it's currently here:

https://github.com/cajus/dbxml-debian

Known issues:

 * license inspection: every binding carries various licenses, needs
to be listed in copying.

 * java bindings: not packaged in the moment.

 * PHP bindings: not packagable, because it depends on php-db
which is not built alongside of libdb*.

 * The test suite is not run during the build.


signature.asc
Description: This is a digitally signed message part.

Bug#647425: g++-4.6: warn_unused_result error triggerd even if casted

[Cajus Pollmeier]

Package: g++-4.6
Version: 4.6.2-3
Severity: normal

Dear Maintainer,

while preparing the next upload for the qpid package, I've stumbled 
over

a changed behaviour in handling unused results.

The code that is rising errors:

   (void) ::lockf(f, F_ULOCK, 0);

If I change it to some construct like:

   size_t foo;
   foo = ::lockf(f, F_ULOCK, 0);
   (void)foo;

works, but is a bit hackish.

The complete build log can be found at:

  https://ferdi.naasa.net/url/cajus/qpid-cpp_0.12-2_amd64.build

-- System Information:
Debian Release: wheezy/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.0.0-2-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages g++-4.6 depends on:
ii  gcc-4.6 4.6.2-3
ii  gcc-4.6-base4.6.2-3
ii  libc6   2.13-21
ii  libgmp102:5.0.2+dfsg-2
ii  libmpc2 0.9-4
ii  libmpfr43.1.0-2
ii  libstdc++6-4.6-dev  4.6.2-3
ii  zlib1g  1:1.2.3.4.dfsg-3

g++-4.6 recommends no packages.



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

Bug#645160: [LCFC2] templates://qpid-cpp/{qpidd.templates}

[Cajus Pollmeier]

Am 30.10.2011 18:17, schrieb Christian PERRIER:

This is the last call for comments for the review of debconf
templates for qpid-cpp.

The reviewed templates will be sent on Tuesday, November 01, 2011 to this bug 
report
and a mail will be sent to this list with "[BTS]" as a subject tag.

(changes after Justin's remarks)



Ok. Updated in git.

@Justin: well - I think I missed some of the comments because it was not 
clear which of the diffs was the latest.




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

Bug#646658: qpid-python: FTBFS: cp: cannot stat `debian/tmp/usr/lib/python2.6/dist-packages': No such file or directory

[Cajus Pollmeier]

Hi,

interresting. I did the build with sbuild, too. But it seems it's just because 
of the 2.6 -> 2.7 python migration. Will clean the install file - which isn't 
needed anyway and re-upload.

Thanks,
Cajus

Am 26.10.2011 um 02:28 schrieb Mònica Ramírez Arceda:

> Source: qpid-python
> Version: 0.12-1
> Severity: serious
> Tags: wheezy sid
> User: debian...@lists.debian.org
> Usertags: qa-ftbfs-20111022 qa-ftbfs
> Justification: FTBFS on amd64
> 
> Hi,
> 
> During a rebuild of all packages in sid, your package failed to build on
> amd64.
> 
> Relevant part:
>> creating 
>> /build/qpid-python-CH9xSC/qpid-python-0.12/debian/tmp/usr/lib/python2.7/dist-packages/mllib
>> copying build/lib.linux-x86_64-2.7/mllib/transforms.py -> 
>> /build/qpid-python-CH9xSC/qpid-python-0.12/debian/tmp/usr/lib/python2.7/dist-packages/mllib
>> copying build/lib.linux-x86_64-2.7/mllib/__init__.py -> 
>> /build/qpid-python-CH9xSC/qpid-python-0.12/debian/tmp/usr/lib/python2.7/dist-packages/mllib
>> copying build/lib.linux-x86_64-2.7/mllib/parsers.py -> 
>> /build/qpid-python-CH9xSC/qpid-python-0.12/debian/tmp/usr/lib/python2.7/dist-packages/mllib
>> copying build/lib.linux-x86_64-2.7/mllib/dom.py -> 
>> /build/qpid-python-CH9xSC/qpid-python-0.12/debian/tmp/usr/lib/python2.7/dist-packages/mllib
>> caching 
>> /build/qpid-python-CH9xSC/qpid-python-0.12/debian/tmp/usr/lib/python2.7/dist-packages/qpid/specs/amqp-0-10-qpid-errata.xml
>>  to amqp-0-10-qpid-errata.pcl
>> running install_scripts
>> creating /build/qpid-python-CH9xSC/qpid-python-0.12/debian/tmp/usr/bin
>> copying build/scripts-2.7/qpid-python-test -> 
>> /build/qpid-python-CH9xSC/qpid-python-0.12/debian/tmp/usr/bin
>> changing mode of 
>> /build/qpid-python-CH9xSC/qpid-python-0.12/debian/tmp/usr/bin/qpid-python-test
>>  to 775
>> running install_egg_info
>> Writing 
>> /build/qpid-python-CH9xSC/qpid-python-0.12/debian/tmp/usr/lib/python2.7/dist-packages/qpid_python-0.12.egg-info
>>   dh_install -O--sourcedirectory=python
>> cp: cannot stat `debian/tmp/usr/lib/python2.6/dist-packages': No such file 
>> or directory
>> dh_install: cp -a debian/tmp/usr/lib/python2.6/dist-packages 
>> debian/python-qpid//usr/lib/python2.6/ returned exit code 1
>> make: *** [binary] Error 2
> 
> The full build log is available from:
>   
> http://people.debian.org/~lucas/logs/2011/10/22/qpid-python_0.12-1_lsid64.buildlog
> 
> A list of current common problems and possible solutions is available at 
> http://wiki.debian.org/qa.debian.org/FTBFS . You're welcome to contribute!
> 
> About the archive rebuild: The rebuild was done on about 50 AMD64 nodes
> of the Grid'5000 platform, using a clean chroot.  Internet was not
> accessible from the build systems.
> 
> 




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

Bug#645160: [RFR] templates://qpid-cpp/{qpidd.templates}

[Cajus Pollmeier]

Am 21.10.2011 10:05, schrieb Cajus Pollmeier:

Am 21.10.2011 06:00, schrieb Christian PERRIER:

Quoting Cajus Pollmeier (ca...@naasa.net):


But, ok. Its now lowercase. Not adding the diff this time. The
latest and greatest version is here:

https://github.com/cajus/qpid-cpp-debian/blob/master/debian/control


I'd just suggest s/This package contains/This package provides (we
tend to standardize on this over all reviews).

Ok. I've fixed that.

Here are the current patch/infos.
diff -u qpid-cpp-debian.orig/debian/changelog qpid-cpp-debian/debian/changelog
--- qpid-cpp-debian.orig/debian/changelog   2011-09-29 08:28:53.0 
+0200
+++ qpid-cpp-debian/debian/changelog2011-10-20 09:19:02.984957927 +0200
@@ -1,3 +1,18 @@
+qpid-cpp (0.12-2) unstable; urgency=low
+
+  [ Cajus Pollmeier ]
+  * Updated valgrind dependencies to allow builds on architectures
+not supported by valgrind.
+  * Fixed compilation error on armel.
+  * Added accidently missing qpid-doc package.
+
+  [ Christian Perrier ]
+  * Debconf templates and debian/control reviewed by the debian-l10n-
+english team as part of the Smith review project. Closes: #645160
+  * [Debconf translation updates]
+
+ -- Cajus Pollmeier   Mon, 10 Oct 2011 16:25:38 +0200
+
 qpid-cpp (0.12-1) unstable; urgency=low
 
   * Initial release. (Closes: #640497)
diff -u qpid-cpp-debian.orig/debian/control qpid-cpp-debian/debian/control
--- qpid-cpp-debian.orig/debian/control 2011-10-05 15:58:52.0 +0200
+++ qpid-cpp-debian/debian/control  2011-10-21 10:04:56.496957757 +0200
@@ -12,362 +12,362 @@
 Depends: ${shlibs:Depends}, ${misc:Depends}, adduser, libsasl2-modules, 
sasl2-bin
 Replaces: qpid-broker
 Conflicts: qpid-broker
-Description: Apache qpid AMQP broker
- Apache Qpid is a cross-platform Enterprise Messaging system which implements
+Description: enterprise messaging system - AMQP broker
+ Apache Qpid is a cross-platform enterprise messaging system which implements
  the Advanced Message Queuing Protocol (AMQP), providing message brokers
  written in C++ and Java, along with clients for C++, Java JMS, .Net, Python,
  and Ruby.
  .
- This package contains the AMQP broker.
+ This package provides the AMQP broker.
 
 Package: qpid-client
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
-Description: Apache qpid AMQP client
- Apache Qpid is a cross-platform Enterprise Messaging system which implements
+Description: enterprise messaging system - AMQP client
+ Apache Qpid is a cross-platform enterprise messaging system which implements
  the Advanced Message Queuing Protocol (AMQP), providing message brokers
  written in C++ and Java, along with clients for C++, Java JMS, .Net, Python,
  and Ruby.
  .
- This package contains the AMQP client support.
+ This package provides the AMQP client support.
 
 Package: libqmf1
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
-Description: Apache qpid AMQP libraries
- Apache Qpid is a cross-platform Enterprise Messaging system which implements
+Description: enterprise messaging system - QMF libraries
+ Apache Qpid is a cross-platform enterprise messaging system which implements
  the Advanced Message Queuing Protocol (AMQP), providing message brokers
  written in C++ and Java, along with clients for C++, Java JMS, .Net, Python,
  and Ruby.
  .
- This package contains the QMF libraries.
+ This package provides the Qpid Management Framework libraries.
 
 Package: libqmf-dev
 Architecture: any
 Section: libdevel
 Depends: ${misc:Depends}
-Description: Apache qpid AMQP develpment files
- Apache Qpid is a cross-platform Enterprise Messaging system which implements
+Description: enterprise messaging system - QMF development files
+ Apache Qpid is a cross-platform enterprise messaging system which implements
  the Advanced Message Queuing Protocol (AMQP), providing message brokers
  written in C++ and Java, along with clients for C++, Java JMS, .Net, Python,
  and Ruby.
  .
- This package contains the QMF development files.
+ This package provides the Qpid Management Framework development files.
 
 Package: libqmf2-1
 Architecture: any
 Depends: ${shlibs:Depends}, ${misc:Depends}
-Description: Apache qpid AMQP libraries
- Apache Qpid is a cross-platform Enterprise Messaging system which implements
+Description: enterprise messaging system - QMF2 libraries
+ Apache Qpid is a cross-platform enterprise messaging system which implements
  the Advanced Message Queuing Protocol (AMQP), providing message brokers
  written in C++ and Java, along with clients for C++, Java JMS, .Net, Python,
  and Ruby.
  .
- This package contains the QMF2 libraries.
+ This package provides the QMF2 libraries.
 
 Package: libqmf2-dev
 Architecture: any
 Section: libdevel
 Depends: ${misc:Depends}
-Description: Apache qpid AMQP develpment files
- Apache Qpid is a cross-platform Enterprise Messaging system which implements
+Description: enterprise messaging system - QMF2 development files
+ A

Bug#645160: [RFR] templates://qpid-cpp/{qpidd.templates}

[Cajus Pollmeier]

Am 21.10.2011 06:00, schrieb Christian PERRIER:

Quoting Cajus Pollmeier (ca...@naasa.net):


But, ok. Its now lowercase. Not adding the diff this time. The
latest and greatest version is here:

https://github.com/cajus/qpid-cpp-debian/blob/master/debian/control


I'd just suggest s/This package contains/This package provides (we
tend to standardize on this over all reviews).

Ok. I've fixed that.



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

Bug#646085: ITP: qpidd-msgstore -- persistent queue module for Apache Qpid

[Cajus Pollmeier]

Package: wnpp
Severity: wishlist

* Package name: qpidd-msgstore
  Version : 0.12
  Upstream Author :
* URL : http://qpidcomponents.org/download.html#persistence
* License : GNU Lesser General Public License 2.1
  Programming Lang: C++
  Description : Apache Qpid persistent storage module

 Qpid/C++ is a C++ implementation of the AMQP protocol described at
 http://amqp.org/

I'm currently in progress of building packages that are needed to use
qpid in Debian. This module is required to persist queue messages on disk.



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

Bug#645160: [RFR] templates://qpid-cpp/{qpidd.templates}

[Cajus Pollmeier]

Am 20.10.2011 11:04, schrieb Justin B Rye:

Cajus Pollmeier wrote:

On the one hand "Apache Qpid" is shorter and gives a reference to
what is packaged. On the other hand "Enterprise messaging system"
tells more about what it is - but it's more generic. I'm not sure
how the short description should be in this case.

[...]

+Description: Enterprise messaging system - AMQP broker

 ^
No need to capitalise the first word of a synopsis - it isn't a
sentence.  Unless of course it's a Star Trek reference.


LOL. I *thought* that I remembered that lintian was picky about that 
some time ago ;-)


But, ok. Its now lowercase. Not adding the diff this time. The latest 
and greatest version is here:


https://github.com/cajus/qpid-cpp-debian/blob/master/debian/control

Best,
Cajus



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

Bug#645160: [RFR] templates://qpid-cpp/{qpidd.templates}

[Cajus Pollmeier]

Am 19.10.2011 23:10, schrieb Justin B Rye:

Christian PERRIER wrote:

  Template: qpidd/password2

[...]

I actually re-used the exact same wording than the one used in Debian
Installerr, for consistency.

My only comment is that "the QPID daemon administrator" should be
"Qpid" to match how it's used elsewhere.

(I'm assuming the answer to "why Qpid?" is "because Qpid™!")


Yes, you're right. I've unified that over the control file.


  Package: qpidd

[...]

-Description: Apache qpid AMQP broker
- Apache Qpid is a cross-platform Enterprise Messaging system which implements
+Description: cross-platform enterprise messaging system - broker

That would be fine except that standardising it across the suite would
leave us saying things like
Description: cross-platform enterprise messaging system - common 
development files
which is a bit too long.  Could we perhaps drop "cross-platform" from
the synopsis version?  The alternative (not implemented below) is to
go back to "Apache Qpid" as the suite-name:
Description: Apache Qpid - common development files


On the one hand "Apache Qpid" is shorter and gives a reference to what 
is packaged. On the other hand "Enterprise messaging system" tells more 
about what it is - but it's more generic. I'm not sure how the short 
description should be in this case.



Trying to fill in the blanks:


  Package: qpid-client

As above.


  Package: libqmf1

[...]

+Description: cross-platform enterprise messaging system - QMF libraries

[...]

+ This package provides the QMF libraries.

Fair enough, assuming that QMF1 is the "default" QMF.  I'd like to
expand it in the long descriptions, though (throughout):

 This package provides the Qpid Management Framework libraries.


  Package: libqpidmessaging2

[...]

+Description: cross-platform enterprise messaging system - AMQP libraries

Are these the only things that can claim to be AQMP libraries?  I've
gone for
Description: enterprise messaging system - AMQP messaging libraries
and likewise, just squeezing under the 80-column limit:


  Package: libqpidmessaging2-dev

Description: enterprise messaging system - AMQP messaging development files


  Package: libsslcommon2

[...]

+Description: cross-platform enterprise messaging system - common SSL files

[...]

+ This package provides the AMQP libraries.

Surely (here and equivalently in the -dev package):
 This package provides the common SSL files.
(whatever that means exactly)...


  Package: libsslcommon2-dev

[...]

+Description: cross-platform enterprise messaging system - common SSL 
development files
  Description: Apache qpid AMQP develpment files

Editing glitch.


  Package: librdmawrap2

[...]

+Description: cross-platform enterprise messaging system - ?

[...]

+ This package provides the AMQP libraries.

Best guess:
Description: enterprise messaging system - RDMA libraries
[...]
This package provides the Remote Direct Memory Access libraries.
(and equivalently in the -dev package)


  Package: libqpidtypes1

Description: enterprise messaging system - API libraries


  Package: libqpidcommon2

Description: enterprise messaging system - common libraries


  Package: libqpidclient2

Description: enterprise messaging system - AMQP client libraries


  Package: libqpidbroker2

Description: enterprise messaging system - AMQP broker libraries


  Package: libqmfengine1

Description: enterprise messaging system - QMF engine libraries


  Package: python-cqpid
  Package: python-qmf2
  Package: python-cqmf2
  Package: python-qmf
  #Package: qpid-doc

These ones just need to drop the word "AMQP" a few times.


  Package: libqpid-ruby1.8
  #Package: libqpid-perl

Why do Python modules get called modules while Ruby and Perl ones get
called "bindings" and/or "support"?  Oh well, maybe there are reasons,
so I'll leave them incompletely standardised.


I've unified the support/module/binding information to be "binding" and 
tried to fix most of the comments above. Thanks for reviewing.


Cajus
diff -u qpid-cpp-debian.orig/debian/changelog qpid-cpp-debian/debian/changelog
--- qpid-cpp-debian.orig/debian/changelog	2011-09-29 08:28:53.0 +0200
+++ qpid-cpp-debian/debian/changelog	2011-10-20 09:19:02.984957927 +0200
@@ -1,3 +1,18 @@
+qpid-cpp (0.12-2) unstable; urgency=low
+
+  [ Cajus Pollmeier ]
+  * Updated valgrind dependencies to allow builds on architectures
+not supported by valgrind.
+  * Fixed compilation error on armel.
+  * Added accidently missing qpid-doc package.
+
+  [ Christian Perrier ]
+  * Debconf templates and debian/control reviewed by the debian-l10n-
+english team as part of the Smith review project. Closes: #645160
+  * [Debconf translation updates]
+
+ -- Cajus Pollmeier   Mon, 10 Oct 2011 16:25:38 +0200
+
 q

Bug#645160: [ITR] templates://qpid-cpp/{qpidd.templates}

[Cajus Pollmeier]

You're welcome ;-)



Am 17.10.2011 um 07:49 schrieb Christian PERRIER :

> Dear Debian maintainer,
> 
> The Debian internationalisation team and the Debian English
> localisation team will soon begin the review of the debconf
> templates used in qpid-cpp.
> 
> This review takes place for all packages that use debconf to interact with
> users and its aims are:
> - to improve the use of English in all debconf templates;
> - to make the wording of debconf templates more consistent;
> - to encourage more translations of templates.
> 
> Even if your first language is English, this process is likely to help
> track down typos or errors, and improve consistency between the
> debconf templates of your package and that of other packages in the
> distribution.
> 
> The process involves both debian-l10n-english contributors and
> Debian translators.
> 
> The details of the process are given in
> http://wiki.debian.org/I18n/SmithDebconfReviewProcess.
> 
> I will act as the coordinator of this activity for qpid-cpp.
> 
> The first step of the process is to review the debconf source
> template file(s) of qpid-cpp. This review will start on Thursday, October 20, 
> 2011, or
> as soon as you acknowledge this mail with an agreement for us to
> carry out this process.
> 
> All parts of the process will be carried out in close collaboration
> with you, and, unless you explicitely ask for it, no upload nor NMU
> will happen for qpid-cpp.
> 
> If you approve this process, please let us know by replying to this
> mail. If some work in progress on your side would conflict with such a
> rewrite (such as adding or removing debconf templates), please say so,
> and we will defer the review to later in the development cycle.
> 
> Thank you for your attention.
> 
> -- 
> 
> 



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

Bug#640497: Package split

[Cajus Pollmeier]

Relevant for this bug is only:

https://github.com/cajus/qpid-cpp-debian


signature.asc
Description: This is a digitally signed message part

Bug#640888: ITP: qpid-qmf -- python bindings for QMF

[Cajus Pollmeier]

Package: wnpp
Severity: wishlist

* Package name: qpid-qmf
  Version : 0.12
  Upstream Author : QPID development team 
* URL : http://qpid.apache.org
* License : Apache License, Version 2.0
  Programming Lang: C++/Python
  Description : Python bindings for QMF

 Qpid/C++ is a C++ implementation of the AMQP protocol described at
 http://amqp.org/

I'm currently in progress of building packages that are needed to use
qpid in Debian. Not on alioth, but github in the moment:

https://github.com/cajus/python-qpid-extras-qmf


signature.asc
Description: This is a digitally signed message part

Bug#640887: ITP: qpid-python -- python bindings for qpid

[Cajus Pollmeier]

Package: wnpp
Severity: wishlist

* Package name: qpid-python
  Version : 0.12
  Upstream Author : QPID development team 
* URL : http://qpid.apache.org
* License : Apache License, Version 2.0
  Programming Lang: C++/Python
  Description : Apache qpid AMQP python bindings

 Qpid/C++ is a C++ implementation of the AMQP protocol described at
 http://amqp.org/

I'm currently in progress of building packages that are needed to use
qpid with python in Debian. Not on alioth, but github in the moment:

https://github.com/cajus/python-qpid

See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640497 for more
information.


signature.asc
Description: This is a digitally signed message part

Bug#640886: ITP: qpid-tools -- management tools for qpid

[Cajus Pollmeier]

Package: wnpp
Severity: wishlist

* Package name: qpid-tools
  Version : 0.12
  Upstream Author : QPID development team 
* URL : http://qpid.apache.org
* License : Apache License, Version 2.0
  Programming Lang: C++/Python
  Description : Apache qpid AMQP broker management tools

 Qpid/C++ is a C++ implementation of the AMQP protocol described at
 http://amqp.org/

I'm currently in progress of building packages that are needed to use
qpid in Debian. These are the management tools.

See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=640497 for more 
information.


signature.asc
Description: This is a digitally signed message part

Bug#640497: ITP: qpid -- cross-platform enterprise AMQP messaging system

[Cajus Pollmeier]

Package: wnpp
Severity: wishlist

* Package name: qpid
  Version : 0.12
  Upstream Author : QPID development team 
* URL : http://qpid.apache.org
* License : Apache License, Version 2.0
  Programming Lang: C++/Python
  Description : Apache qpid AMQP broker

 Qpid/C++ is a C++ implementation of the AMQP protocol described at
 http://amqp.org/

I'm currently in progress of building packages that are needed to use
qpid in Debian. Not on alioth, but github in the moment:

https://github.com/cajus/qpid-cpp-debian
https://github.com/cajus/qpid-tools
https://github.com/cajus/python-qpid
https://github.com/cajus/python-qpid-extras-qmf


signature.asc
Description: This is a digitally signed message part

Bug#634952: xfsprogs: xfs_quota commands are internationalized

[Cajus Pollmeier]

Package: xfsprogs
Version: 3.1.5
Severity: normal


If your system locale is non english and you use the xfs_quota tool, you
run into problems if you do not set LC_ALL=C in front of your command:

# xfs_quota -x -c report /home
Befehl »report« nicht gefunden

vs

# LC_ALL=C xfs_quota -x -c report /home
...

The command registration uses gettext for the command 'name', which
makes it work like this:

# xfs_quota -x -c Bericht /home
...

The manualpage does not give any hints to the fact that commands are
translated and I'd recommend to remove the _() around the registered
names to not confuse users.

-- System Information:
Debian Release: 6.0.2
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash




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

Bug#629315: gosa ldap-manager csv-import should as minimum only ask for given- and surname.

[Cajus Pollmeier]

Can you check if this helps in your case:

https://oss.gonicus.de/labs/gosa/ticket/1146#comment:2

Am Montag, den 27.06.2011, 11:30 +0200 schrieb Cajus Pollmeier:
> I've moved this to the gosa bugtracker as a features request. Will be
> solved ASAP if time allows.
> 
> Am Sonntag, den 05.06.2011, 17:04 +0200 schrieb Klaus Ade Johnstad:
> > Package: gosa
> > Severity: normal
> > 
> > Gosa ldap-manager csv-import currently has uid/username, givenname and 
> > surname
> > as minimum requirements. It needs to be possible to massimport users via
> > csv-import using only givenname and surname (or fullname), gosa should
> > then automatically create usernames. Having username as a requirement makes
> > mass-import of users difficult in schools.
> > 
> > -- System Information:
> > Debian Release: 6.0
> >   APT prefers stable
> >   APT policy: (500, 'stable')
> > Architecture: i386 (x86_64)
> > 
> > Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
> > Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8)
> > Shell: /bin/sh linked to /bin/dash
> > 
> > 
> 



signature.asc
Description: This is a digitally signed message part

Bug#629573: getent passwd shows the gosa template

[Cajus Pollmeier]

If you use templates, there's no way around the "special" filter,
because templates are pseudo users.

Am Mittwoch, den 15.06.2011, 11:16 +0200 schrieb Andreas B. Mundt:
> User: debian-...@lists.debian.org
> Usertags: debian-edu
> 
> Hi,
> 
> On Tue, Jun 07, 2011 at 10:05:28PM +0200, Klaus Ade Johnstad wrote:
> > Package: gosa
> > Severity: normal
> > 
> > A getent password shows the gosa template also, like this:
> > root@tjener:~# getent passwd
> > newteacher:x:1001:1001:NewTeacher 
> > NewTeacher:/skole/tjener/home0/%uid:/bin/bash
> > newstudent:x:1002:1002:NewStudent 
> > NewStudent:/skole/tjener/home0/%uid:/bin/bash
> > 
> > These template should not show up when doing a simple getent passwd.
> 
> 
> It can be avoided by modifying /etc/nslcd.conf.  Here is the cfengine
> rule (from the debian-edu-config package svn, cf/cf.ldapclient):
> 
> #   ## Avoid showing the GOsa template as user:
> #   { /etc/nslcd.conf
> #  AppendIfNoSuchLine "filter passwd
> #   (&(objectClass=posixAccount)(!(objectClass=gosaUserTemplate)))"
> #}
> 
> It's commented because we want to get rid of these rules.  If it's
> unavoidable, we can switch it on.
> 
> Regards,
>   Andi
> 
> 



signature.asc
Description: This is a digitally signed message part

Bug#629315: gosa ldap-manager csv-import should as minimum only ask for given- and surname.

[Cajus Pollmeier]

severity 629315 whishlist
thanks

I've moved this to the gosa bugtracker as a features request. Will be
solved ASAP if time allows.

Am Sonntag, den 05.06.2011, 17:04 +0200 schrieb Klaus Ade Johnstad:
> Package: gosa
> Severity: normal
> 
> Gosa ldap-manager csv-import currently has uid/username, givenname and surname
> as minimum requirements. It needs to be possible to massimport users via
> csv-import using only givenname and surname (or fullname), gosa should
> then automatically create usernames. Having username as a requirement makes
> mass-import of users difficult in schools.
> 
> -- System Information:
> Debian Release: 6.0
>   APT prefers stable
>   APT policy: (500, 'stable')
> Architecture: i386 (x86_64)
> 
> Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
> Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> 
> 



signature.asc
Description: This is a digitally signed message part

Bug#629312: gosa says UID but means username.

[Cajus Pollmeier]

The fileds UID, GIVENNAME and SURNAME represent the corresponding LDAP
attributes. I tend to leave them as they are because the UID is the
username used for log in.

Am Sonntag, den 05.06.2011, 16:39 +0200 schrieb Klaus Ade Johnstad:
> Package: gosa
> Severity: normal
> 
> In gosa ldap-manager the CSV-import page says one must include the 
> three fields UID, GIVENNAME and SURNAME. In reality it's not UID, but 
> username that is meant.
> Please correct the wording.
> 
> -- System Information:
> Debian Release: 6.0
>   APT prefers stable
>   APT policy: (500, 'stable')
> Architecture: i386 (x86_64)
> 
> Kernel: Linux 2.6.32-5-amd64 (SMP w/2 CPU cores)
> Locale: LANG=nb_NO.UTF-8, LC_CTYPE=nb_NO.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> 
> 



signature.asc
Description: This is a digitally signed message part

Bug#626960: ldap2zone: man page for ldap2bind

[Cajus Pollmeier]

Hi Andi,

thanks. It's now included.

Cheers,
Cajus

Am Montag, den 16.05.2011, 20:19 +0200 schrieb Andreas B. Mundt:
> Package: ldap2zone
> Severity: normal
> Tags: patch
> 
> Find attached a manual page for the executable ldap2bind.
> 
> Best Regards,
> 
>  Andi
> 
> 
> -- System Information:
> Debian Release: wheezy/sid
>   APT prefers stable-updates
>   APT policy: (500, 'stable-updates'), (500, 'testing'), (500, 'stable')
> Architecture: amd64 (x86_64)
> 
> Kernel: Linux 2.6.38-2-amd64 (SMP w/2 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash



signature.asc
Description: This is a digitally signed message part

Bug#624209: gosa: [INTL:cs] Wrong Czech PO Debconf file name

[Cajus Pollmeier]

Thanks,

it'll be included in the next upload.

Am Dienstag, den 26.04.2011, 18:38 +0200 schrieb Michal Simunek:
> Renamed and corrected file attached, please include it instead.
> 
> Best regards
> 
> David Prévot píše v Út 26. 04. 2011 v 08:48 -0400:
> > Package: gosa
> > Version: 2.7.1-1
> > Severity: normal
> > Tags: l10n
> > 
> > Hi,
> > 
> > While working on the PO Debconf file stats of the website [0], I noticed
> > an extra spurious Czech translation file in gosa (cz.po).
> > 
> >   0: http://www.debian.org/international/l10n/po-debconf/
> > 
> > Regards
> > 
> > David
> > 
> > -- System Information:
> > Debian Release: wheezy/sid
> >   APT prefers unstable
> >   APT policy: (600, 'unstable'), (500, 'oldstable'), (500, 'stable'), (150, 
> > 'experimental')
> > Architecture: amd64 (x86_64)
> > 
> > Kernel: Linux 2.6.38-2-amd64 (SMP w/1 CPU core)
> > Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
> > Shell: /bin/sh linked to /bin/dash
> > 
> > 
> > 
> 



signature.asc
Description: This is a digitally signed message part

Bug#596792: closed by Stig Sandbeck Mathisen (Please use dpkg-statoverride)

[Cajus Pollmeier]

reopen 596792
thanks

Am Samstag 15 Januar 2011, 20:06:15 schrieben Sie:
> This is an automatic notification regarding your Bug report
> which was filed against the puppet package:
> 
> #596792: Reports should be created with adjustable group
> 
> It has been closed by Stig Sandbeck Mathisen .
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Stig Sandbeck Mathisen
>  by replying to this email.

Hi Stig,

I don't see how this can be solved by dpkg-statoverride. My problem are not 
upgrades, my problem is that the logfiles created by puppet have the wrong 
permission set.

Overrride is not possible, because the client directories might even not 
exist. They're created by puppet after a clients pops up.

Cheers,
Cajus



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

Bug#596792: Reports should be created with adjustable group

[Cajus Pollmeier]

Package: puppet
Version: 2.6.0-2
Severity: whishlist
Tags: squeeze

Hi,

when using tools to analyze the puppet report files, they've to be run as root 
in order to be able to read the reports. The top level directory 
(/var/log/puppet by default) permission and ownership values seem to be 
adjustable, but the per machine directories created inside /var/log/puppet are 
owned by root:root.

$ ls -la /var/log/puppet/
total 12
drwxr-x--- 3 puppet puppet 4096 Sep 14 11:12 .
drwxr-xr-x 8 root   root   4096 Sep 14 11:10 ..
drwxr-x--- 2 root   root   4096 Sep 14 11:12 client1.test.net

It would be nice to be able to modify this (i.e. root:adm, root:puppet).

Cheers,
Cajus



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

Bug#457279: gnarwl: ISPEnv.schema ISPEnv2.schema LICENSE not GPL compliant

[Cajus Pollmeier]

Sure. Just take it.

Cheers,
Cajus



Am 08.11.2009 um 01:26 schrieb Barry deFreese :


Cajus,

Are you OK with me orphaning gnarwl and hopefully Fancesco can take  
over

maintenance?

Thank you,

Barry deFreese
Debian QA







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

Bug#538820: php5-suhosin: Random segfault when loading PHP scripts with suhosin enabled

[Cajus Pollmeier]

Am Montag 27 Juli 2009 21:46:38 schrieben Sie:
> Hi Cajus,
>
> On Monday 27 July 2009, Cajus Pollmeier wrote:
> > Package: php5-suhosin
> > Version: 0.9.27-1
> > Severity: important
> >
> > On a new clean unstable test setup, I ran into problems with launching a
> > simple PHP script. It loads initialy - and the next four or five times.
> > Then apache segfaults:
>
> just guessing, but maybe you have the same problem than reported in
> #537788? Could you please downgrade to 5.2.9 from testing and double check?
>
> Thanks, Jan.

Downgraded to testing, I'm only getting empty pages with:

::1 - - [29/Jul/2009:10:47:40 +0200] "OPTIONS * HTTP/1.0" 200 - "-" 
"Apache/2.2.11 (Debian) PHP/5.2.9-4 with Suhosin-Patch (internal dummy 
connection)"

in the logs. Maybe there's something wrong after downgrading like suggested in 
#537788.

Cajus



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

Bug#538820: php5-suhosin: Random segfault when loading PHP scripts with suhosin enabled

[Cajus Pollmeier]

Package: php5-suhosin
Version: 0.9.27-1
Severity: important

On a new clean unstable test setup, I ran into problems with launching a 
simple PHP script. It loads initialy - and the next four or five times. Then 
apache segfaults:

[Mon Jul 27 11:45:24 2009] [notice] child pid 10362 exit signal Segmentation 
fault (11), possible coredump in /tmp

After that segfault, it starts working for some times. Then it segfaults 
again. Not reproducable with a single reload.

I'm not deep enough in the subject to determine if this is a php5 or php5-
suhosin problem. Fact is, that the problem is gone when disabling the suhosin 
module inside my php5 configuration.

Here's a stacktrace:

r...@frost:/etc/php5/apache2/conf.d# gdb /usr/sbin/apache2 /tmp/core
 
GNU gdb (GDB) 6.8.50.20090628-cvs-debian
 
Copyright (C) 2009 Free Software Foundation, Inc.   
 
License GPLv3+: GNU GPL version 3 or later    
 
This is free software: you are free to change and redistribute it.  
 
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"  
 
and "show warranty" for details.
 
This GDB was configured as "i486-linux-gnu".
 
For bug reporting instructions, please see: 
 
...  
 
(no debugging symbols found)
 

warning: Can't read pathname for load map: Eingabe-/Ausgabefehler.
Reading symbols from /usr/lib/libpcre.so.3...(no debugging symbols 
found)...done.
Loaded symbols for /usr/lib/libpcre.so.3
 
Reading symbols from /usr/lib/libaprutil-1.so.0...(no debugging symbols 
found)...done.
Loaded symbols for /usr/lib/libaprutil-1.so.0   
  
Reading symbols from /usr/lib/libapr-1.so.0...(no debugging symbols 
found)...done.
Loaded symbols for /usr/lib/libapr-1.so.0   
  
Reading symbols from /lib/i686/cmov/libpthread.so.0...(no debugging symbols 
found)...done.
Loaded symbols for /lib/i686/cmov/libpthread.so.0   
  
Reading symbols from /lib/i686/cmov/libc.so.6...(no debugging symbols 
found)...done.  
Loaded symbols for /lib/i686/cmov/libc.so.6 
  
Reading symbols from /lib/libuuid.so.1...(no debugging symbols found)...done.   
  
Loaded symbols for /lib/libuuid.so.1
  
Reading symbols from /lib/i686/cmov/librt.so.1...(no debugging symbols 
found)...done. 
Loaded symbols for /lib/i686/cmov/librt.so.1
  
Reading symbols from /lib/i686/cmov/libcrypt.so.1...(no debugging symbols 
found)...done.  
Loaded symbols for /lib/i686/cmov/libcrypt.so.1 
  
Reading symbols from /lib/i686/cmov/libdl.so.2...(no debugging symbols 
found)...done. 
Loaded symbols for /lib/i686/cmov/libdl.so.2
  
Reading symbols from /usr/lib/libexpat.so.1...(no debugging symbols 
found)...done.
Loaded symbols for /usr/lib/libexpat.so.1   
  
Reading symbols from /lib/ld-linux.so.2...(no debugging symbols found)...done.  
  
Loaded symbols for /lib/ld-linux.so.2   
  
Reading symbols from /lib/i686/cmov/libnsl.so.1...(no debugging symbols 
found)...done.
Loaded symbols for /lib/i686/cmov/libnsl.so.1   
  
Reading symbols from /lib/i686/cmov/libnss_compat.so.2...(no debugging symbols 
found)...done.
Loaded symbols for /lib/i686/cmov/libnss_compat.so.2
 
Reading symbols from /lib/i686/cmov/libnss_nis.so.2...(no debugging symbols 
found)...done.   
Loaded symbols for /lib/i686/cmov/libnss_nis.so.2   
 
Reading symbols from /lib/i686/cmov/libnss_files.so.2...(no debugging symbols 
found)...done. 
Loaded symbols for /lib/i686/cmov/libnss_files.so.2 
 
Reading symbols from /usr/lib/apache2/modules/mod_alias.so...(no debugging 
symbols found)...done.
Loaded symbols for /usr/lib/apache2/modules/mod_alias.so
 
Reading symbols from /usr/lib/apache2/modules/mod_auth_basic.so...(no 
debugging symbols found)...done.
Loaded symbols for /usr/lib

Bug#532321: Problem persists

[Cajus Pollmeier]

Hi Michael,

the latest code from svn doesn't work here with lenny. I needed to change
this in order to get a installation because %vg_info is undefined:

--- Volumes.pm  2009-06-16 20:39:34.0 +0200
+++ Volumes.pm.new  2009-06-16 21:07:55.0 +0200
@@ -308,9 +308,13 @@

# store the vg size in MB
my %vg_info = get_volume_group_information($vg);
-$FAI::current_lvm_config{$vg}{size} =
-  &FAI::convert_unit( $vg_info{alloc_pe_size} .
-$vg_info{alloc_pe_size_unit} );
+if (defined %vg_info) {
+  $FAI::current_lvm_config{$vg}{size} =
+&FAI::convert_unit( $vg_info{alloc_pe_size} .
+  $vg_info{alloc_pe_size_unit} );
+} else {
+  $FAI::current_lvm_config{$vg}{size} = "0MB";
+}

# store the logical volumes and their sizes
my %lv_info = get_logical_volume_information($vg);

Cheers,
Cajus



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

Bug#457279: remove gnarwl from lenny?

[Cajus Pollmeier]

I'm not able to provide tested gnarwl packages anymore. Sorry. I'm  
fine with getting it removed from lenny.


Cheers,
Cajus

Am 31.08.2008 um 19:07 schrieb Thomas Viehmann:


Hi,

gnarwl has an RC bug (#457279) about non-DFSG files (open for 8  
months,
set to serious for >=1 month). gnarwl seems to seriously lack  
maintainer

attention: #334873 is a segfault bug almost three years old without
maintainer response. The last maintainer upload was more than three
years ago, i.e. before sarge.

Kind regards

T.
--
Thomas Viehmann, http://thomas.viehmann.net/








--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#487823: Fix fatal error on call function get_template_patch() in /usr/share/gosa/include

[Cajus Pollmeier]

I'm not, because ubuntu changed the smarty paths, not debian. This is  
just an ubuntu problem - and that for years.


Cheers,
Cajus

Am 24.06.2008 um 12:37 schrieb Devid Filoni:

diff -Nru gosa-2.5.16.1/debian/changelog gosa-2.5.16.1/debian/changelog
diff -Nru gosa-2.5.16.1/debian/control gosa-2.5.16.1/debian/control
--- gosa-2.5.16.1/debian/control2008-06-15 18:08:16.0 +0200
+++ gosa-2.5.16.1/debian/control2008-06-23 16:30:36.0 +0200
@@ -1,9 +1,10 @@
 Source: gosa
 Section: web
 Priority: optional
 Maintainer: Cajus Pollmeier <[EMAIL PROTECTED]>
 Build-Depends: debhelper(>= 4.2.32), dpatch
-Standards-Version: 3.7.2.2
+Standards-Version: 3.8.0.1
 
 Package: gosa
 Architecture: all
diff -Nru gosa-2.5.16.1/debian/rules gosa-2.5.16.1/debian/rules
--- gosa-2.5.16.1/debian/rules  2008-06-15 18:08:33.0 +0200
+++ gosa-2.5.16.1/debian/rules  2008-06-23 16:29:16.0 +0200
@@ -98,7 +98,7 @@
mv debian/gosa/usr/share/gosa/include/functions.inc.new 
debian/gosa/usr/share/gosa/include/functions.inc;
-if [ -z "${SARGE_PACKAGE}" ]; then \
rm -rf debian/gosa/usr/share/gosa/include/smarty; \
-   sed 
's%require("smarty/Smarty.class.php");%require("/usr/share/php/smarty/libs/Smarty.class.php");%g'
 debian/gosa/usr/share/gosa/include/php_setup.inc > 
debian/gosa/usr/share/gosa/include/php_setup.inc.new; \
+   sed 
's%require("smarty/Smarty.class.php");%require("/usr/share/php/smarty/Smarty.class.php");%g'
 debian/gosa/usr/share/gosa/include/php_setup.inc > 
debian/gosa/usr/share/gosa/include/php_setup.inc.new; \
mv debian/gosa/usr/share/gosa/include/php_setup.inc.new 
debian/gosa/usr/share/gosa/include/php_setup.inc; \
fi
install -D -m 644 debian/overrides-lintian 
debian/gosa/usr/share/lintian/overrides/gosa

Bug#486121: gosa-schema: goserver.schema lacks a structuralObjectClass goServer

[Cajus Pollmeier]

Am Freitag, 13. Juni 2008 16:30:18 schrieb Erik Rossen:
> Package: gosa-schema
> Version: 2.5.16.1-1
> Severity: important
>
>
> Somewhere between version 2.4beta2-1 and 2.5.16, the definition of the
> objectClass "goServer" underwent a regression where it got changed from
> a STRUCTURAL to an AUXILLARY objectClass (line 230 of the current
> version).
>
> This causes LDAP trees exported from older systems containing GOsa
> configurations to fail importation into newer (and stricter) OpenLDAP
> servers since the objects lack a valid structural object class.  The
> failure looks like
>
>   [EMAIL PROTECTED]:~# slapadd -c -l oldldap.ldif
>   slapadd: dn="cn=mail,ou=servers,ou=systems,dc=example,dc=com"
>   (line=248): (65) no structural object class provided
>
> even though "cn=mail,ou=servers,ou=systems,dc=example,dc=com" is
> perfectly well-defined:
>
>   dn: cn=mail,ou=servers,ou=systems,dc=example,dc=com
>   structuralObjectClass: goServer
>   entryUUID: a279e56e-bd5d-1029-8625-9ebaa3928079
>   creatorsName: cn=admin,dc=example,dc=com
>   createTimestamp: 20050919133257Z
>   cn: mail
>   goImapSievePort: 2000
>   goImapPassword: NONEOFYOURBUSINESS
>   goImapAdmin: cyrus
>   objectClass: top
>   objectClass: goImapServer
>   objectClass: goServer
>   goImapName: imap://mail.example.com
>   goImapSieveServer: mail.example.com
>   goImapConnect: {mail.example.com:143/imap/notls}
>   entryCSN: 20060220124346Z#01#00#00
>   modifiersName: cn=admin,dc=example,dc=com
>   modifyTimestamp: 20060220124346Z
>
> A temporary workaround is just to change line 230 from AUXILLARY back to
> STRUCTURAL.
>
> It would also be nice if the version number at the head of the file
>
>   ## Version 030403
>
> got incremented when there were changes. ;-)
>
> -- System Information:
> Debian Release: 4.0
>   APT prefers oldstable
>   APT policy: (991, 'oldstable'), (991, 'stable'), (66, 'oldstable'), (33,
> 'unstable') Architecture: i386 (i686)
> Shell:  /bin/sh linked to /bin/dash
> Kernel: Linux 2.6.18-6-vserver-686
> Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)

Add the GOhard objectClass to your server entries and you're fine. The GOsa 
package cannot modify your ldap content to do a smooth update in this case.

I cannot fix your issue - except writing a note inside of the README.

Cheers,
Cajus



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#478388: gosa: bashism in debian/rules

[Cajus Pollmeier]

Then something with the upload is wrong. My sources for 2.5.16.1 have  
the fix (two times). In the uploaded version the fix is present only  
one time. Strange. Will do an re-upload tomorrow.


Am 08.06.2008 um 19:19 schrieb Chris Lamb:


Cajus Pollmeier wrote:

Please point me to the error so that I can fix it. I'm no dash  
expert and

I'm not interested in getting one.


diff -urNad gosa-2.5.16.1.orig/debian/rules gosa-2.5.16.1/debian/rules
--- gosa-2.5.16.1.orig/debian/rules 2008-06-08  
18:15:52.0 +0100

+++ gosa-2.5.16.1/debian/rules  2008-06-08 18:17:24.0 +0100
@@ -73,7 +73,7 @@
   -mv debian/gosa/usr/share/gosa/bin/* debian/gosa/usr/bin
   -rm -rf debian/gosa/usr/share/gosa/bin
   -rm -rf debian/gosa/usr/share/doc/gosa/marketing
-   -find debian/gosa -type f -exec chmod -x {} \; &> /dev/null
+   -find debian/gosa -type f -exec chmod -x {} \; >/dev/null 2>&1
   -chmod +x debian/gosa/usr/bin/mkntpasswd
   -rm -rf debian/gosa/usr/share/gosa/doc/guide/user/*/lyx-source
   -rm -rf debian/gosa/usr/share/gosa/doc/guide/admin

(..which I already posted to this bug report)  Let me know if you  
would like

an NMU for this.


Regards,

--
Chris Lamb, UK   [EMAIL PROTECTED]
   GPG:  
0x634F9A20





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#478388: ...

[Cajus Pollmeier]

Please point me to the error so that I can fix it. I'm no dash expert and I'm 
not interested in getting one.

[EMAIL PROTECTED]:~/temp/gosa-2.5.16.1/debian$ checkbashisms -f rules; echo $?
0
[EMAIL PROTECTED]:~/temp/gosa-2.5.16.1/debian$



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#480426: [gosa] not useable on sid

[Cajus Pollmeier]

Ok. I re-installed sid from scratch:

* perl is in transition and packages are not installable
   -> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=479504
* PHP5 is currently not installable because the meta package got no  
update yet.


I will close the bug. Please wait until the above problems are solved.

Cheers,
Cajus

Am 10.05.2008 um 00:24 schrieb Hans-Georg Bork:


Package: gosa
Version: 2.5.15-2
Severity: serious

--- Please enter the report below this line. ---

After installation the setup wizard started normally, but at the  
installation check

I get (among other warnings) this message:
--
SAMBA password hash generation
Error
In order to use SAMBA 2/3 you've to install additional perl libraries.
Take a look at mkntpasswd. GOsa will NOT run without fixing this.
--

Checked mkntpasswd, perl needs Crypt::SmbHash (.deb package unknown to
me) and cpan shows "Crypt::SmbHash is up to date (0.12)"

There's nowhere any description which additional libraries are needed
here.

BTW: php5-snmp 5.2.5-3 is installed, but setup shows that it's not
there.

Regards
-- hgb


--- System information. ---
Architecture: i386
Kernel:   Linux 2.6.22.sokrates.home

Debian Release: lenny/sid
 500 unstablewww.debian-multimedia.org
 500 unstableftp.de.debian.org

--- Package information. ---
Depends(Version) | Installed
-+-
php5 | 5.2.5-3
apache2  |
exim4|
OR mail-transport-agent |
php5-gd  | 5.2.5-3
php5-imap| 5.2.5-3
php5-ldap| 5.2.5-3
php5-mhash   | 5.2.5-3
php5-mysql   | 5.2.5-3
php5-imagick |
OR imagemagick  (>= 5.4.4.5-1)  | 7:6.3.7.9.dfsg1-2+b2
OR graphicsmagick-im-compat |
fping| 2.4b2-to-ipv6-15
libcrypt-smbhash-perl| 0.12-2
smarty   | 2.6.19-1
php5-recode  | 5.2.5-3
wwwconfig-common | 0.1.1
smarty-gettext   | 1.0b1-2






--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#480426: [gosa] not useable on sid

[Cajus Pollmeier]

severity 480426 normal
thanks

On Sat, 10 May 2008 00:24:56 +0200, Hans-Georg Bork <[EMAIL PROTECTED]>
wrote:
> Package: gosa
> Version: 2.5.15-2
> Severity: serious
> 
> --- Please enter the report below this line. ---
> 
> After installation the setup wizard started normally, but at the
> installation check 
> I get (among other warnings) this message:
>
--
> SAMBA password hash generation
> Error
> In order to use SAMBA 2/3 you've to install additional perl libraries.
> Take a look at mkntpasswd. GOsa will NOT run without fixing this. 
>
--

The deb-Package is libcrypt-smb-perl and it is installed by dependency. If
you do not touch the setup defaults, it works out of the box. Have you
removed the smb crypt string in the setup?

GOsa is not pure debian specific, so the error message above just tells you
to try to figure a *possible* error. For debian, it installs
/usr/bin/mkntpasswd as a helper binary. Try to execute this one.

You can enter this command as the smb-hash generation command in the setup.

If it still does not work, maybe you've safe mode switched to on?

> Checked mkntpasswd, perl needs Crypt::SmbHash (.deb package unknown to
> me) and cpan shows "Crypt::SmbHash is up to date (0.12)"
> 
> There's nowhere any description which additional libraries are needed
> here.

All dependencies are installed automatically. You don't have do install
anything manually. I can't reproduce this problem.

> BTW: php5-snmp 5.2.5-3 is installed, but setup shows that it's not
> there.

Can't reproduce this one, too. Please check if it's really included with
php_info().

Cheers,
Cajus




--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#478388: gosa: bashism in debian/rules

[Cajus Pollmeier]

Am Samstag, 3. Mai 2008 22:59:04 schrieb Chris Lamb:
> tags 478388 + patch
> thanks
>
> Patch attached.
>
>
> Regards,

This one changes the logic and will fail if you package from an "svn export". 
I've removed the "find" completely (upstream) and will upload a new version 
later on.

Cheers,
Cajus




-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#402010: How to deal with #402010?

[Cajus Pollmeier]

Am 05.04.2008 um 11:59 schrieb sean finney:

hi,

On Saturday 05 April 2008 11:26:14 am Cajus Pollmeier wrote:

The problem is that these aspects are not packagable as some kind of
"fire and forget" installation. I'd prefer the way Roland proposed,
using some kind of


option 3 could work out of the box, though it just requires more  
initial setup
work to get right in the packaging.  i'm not saying it's the Right  
Way, but

it would provide the necessary compartmentalizing.


Well - I guess this information would be good for the README. You  
think about providing another apache init script + configs? Hmm. But  
gosa+php works with other webservers, too. So the packaging overhead  
might grow.


Or you force the use of apache-mpm-itk and let it run in a different  
vhost as a different user.



RequestHeader set FooPassword very-secret-credentials


i suspect php users will still be able to find that out, in the same  
way that
they can read ssl private keys from the webserver's memory (you  
*did* know

they can do that, right? :)


Do you have more information about this? I guess this is only the case  
for unpatched php instances, isn't it?


Cheers,
Cajus



--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#402010: How to deal with #402010?

[Cajus Pollmeier]

The problem is that these aspects are not packagable as some kind of  
"fire and forget" installation. I'd prefer the way Roland proposed,  
using some kind of


# cat /etc/apache2/conf.d/gosa.conf
Alias /gosa /usr/share/gosa/html

include /etc/gosa/gosa.secrets


# cat /etc/gosa/gosa.secrets
RequestHeader set FooPassword very-secret-credentials

The latter file can only be read by root, so the security "problem" is  
as critical as beeing able to read cleartext kerberos or sasldb  
passwords as root.


This implementation only requires minimum changes and has no big  
overhead on the server side... Uh, and a "a2enmod headers" from  
postinst.


Cheers,
Cajus

Am 05.04.2008 um 11:07 schrieb sean finney:

hi,

a few more ideas for you to think about:

- create a user specific to the package, and

1: use a setuid wrapper binary for doing all ldap communications

or

2: use some kind of user-restricted fastcgi type setup instead of  
standard

apache mod_php/python/whatever

or

3: run a seperate instance of $webserver listening on a different port
(localhost:8080 or similar), and running as the specific user.  you  
can then
drop in a proxy config to make that available from the standard  
$webserver.





sean





--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Bug#402010: How to deal with #402010?

[Cajus Pollmeier]

Am Freitag, 4. April 2008 11:50:42 schrieb Holger Levsen:
> Hi,
>
> On Friday 04 April 2008 09:18, Cajus Pollmeier wrote:
> > to virtually any kind of web application accessing some kind of
> > database/ldap passwords somewhere in the filesystem.
>
> I dont consider a web application which is used to configure the LDAP
> database and FAI configuration (to install and configure all machines in
> the network) just like any other web application.
>
> In this bug are several suggestions how to implement a way better mechanism
> to deal with the password then the current one.

If you read the comments, I'll see that it is not possible to use these 
suggestions. Besides maybe the last one, but there's no propper 
infrastructure in debian to use it directly.

> Also I unarchived this bug, because I think the least you can and should do
> is to document this in the README.Debian. (This=dont allow public html dirs
> for users and leave safe mode on.)

As said - I'm not responsible for the webserver setup of other people. Sure, I 
can put it inside the README and close this bug - waiting until the next one 
comes around and urges me to do something about it again. Ah wait, I can just 
orphan the gosa packages.

> P.S.: regarding those four major ldap servers.. I think it would be a great
> start if it would be more secure with one of them :-)

You're welcome. Send patches.

Cheers,
Cajus



-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]