-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I need some advice from you on the bug below.
Am 12.12.2010 12:01, schrieb Lucas Nussbaum:
>> Am 11.12.2010 18:11, schrieb Lucas Nussbaum:
>>> While testing the installation of all packages in squeeze, I ran
>>> into the following problem:
>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Holger,
Holger Levsen schrieb:
> On Dienstag, 1. Juni 2010, Roland Gruber wrote:
>> Is there any way to mark a configuration file as unchanged after package
>> installation? Any other solutions?
>
> You could deploy an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I got a piuparts bug (582020) report because my package
(ldap-account-manager) changes configuration files when running postinst.
E.g. it asks the user via debconf to specify a master configuration
password. This is then written to the config
y 12.3.
thanks for the clarification. I thought 12.3 was talking about runtime
dependencies.
So I will install the files in /usr/share/l-a-m.
--
Best regards
Roland Gruber
LDAP Account Manager
http://lam.sourceforge.net
signature.asc
Description: OpenPGP digital signature
Hi Matt,
Matthew Palmer schrieb:
> Except that the contents of /usr/share/doc must not be relied upon for the
> proper functioning of your package. Somewhere under /usr/share/l-a-m is the
> correct place for these sorts of things.
but when I copy the files at install time (postinst) then /usr/sh
Hi Matt,
Matthew Palmer schrieb:
> Well, don't do that, then. Ship the template files somewhere else, and then
> copy them into /var if they're not already there.
that is probably the best solution. I think I will put them in
/usr/share/doc/ldap-account-manager/examples and copy them from there
Hi all,
I am the maintainer of ldap-account-manager and got bug 462192.
The problem is that my application provides a set of default templates
for user creation. These files must be editable via the application
itself and therefore reside in /var/ldap-account-manager.
But the files are overwritte
Hi Thijs,
Thijs Kinkhorst schrieb:
> I've uploaded it.
thanks a lot for your fast help.
> One problem: I just realised that the urgency of the upload was 'low'
> which should have been 'high'. No need to reupload, you can ask on
> #debian-release to have it bumped.
Ok, will do that.
> Is the v
Hi all,
Roland Gruber schrieb:
> unfortunately, my current sponsor has not enough time to sponsor me
> anymore. Therefore I am looking for a new one.
>
> The name of the package is ldap-account-manager. It is a web frontend to
> manage various account types in an LDAP directory.
Hi all,
unfortunately, my current sponsor has not enough time to sponsor me
anymore. Therefore I am looking for a new one.
The name of the package is ldap-account-manager. It is a web frontend to
manage various account types in an LDAP directory. The application is
written in PHP.
I switched fro
Hi Geert,
Geert Stappers schrieb:
> Please avoid "notes", make unattended installs possible.
you are right, if possible then notes should be avoided.
But the problem is that the package is not usable after the upgrade
because the user has to recreate some configuration files.
The application has
Margarita Manterola schrieb:
> As shown in the Upgrading diagram I made some time ago [1], and also,
> as it is explained in the Debian Policy [2], when doing an upgrade,
> the maintainer scripts are called with a second parameter that
> indicates the package version.
thanks a lot for your fast he
Hi all,
probably this has been asked before but my searches did not give proper
results.
I want to display a message to the user via debconf. The message should
only appear if the user upgrades from a version below a special value
(0.5.0 in my case).
My first attempt was to check if some directo
Hi Laszlo,
Laszlo Boszormenyi schrieb:
I am looking for someone who can upload the latest version of my package.
My usual sponsor is Andreas Barth but it seems that he is heavily
working on releasing Sarge and did not respond to my recent mails.
I think I would do it.
thanks, this would be great.
Hi all,
I am looking for someone who can upload the latest version of my package.
My usual sponsor is Andreas Barth but it seems that he is heavily
working on releasing Sarge and did not respond to my recent mails.
The package is at:
http://lam.sourceforge.net/debian-packages/
There are not much ch
Hi all,
Miguel Gea Milvaques schrieb:
I added a debian/watch file to my package ldap-account-manager some time
ago. But the status on Debian Health is still that no watch file is
existent.
I have the same problem too. It works correctly to me with ftp
(libmatheval package) but not with http (acx100
Luk Claes schrieb:
It's indeed very strange. Someone suggested to use something like
ftp://ftp2.sf.net/l/la/lam/ldap-account-manager_(.*)\.tar\.gz though.
Thus:
ftp://ftp2.sf.net//<2_first_letters>//
so the problem might be that I use HTTP in my watch line?
The strange thing is that the watch file
Hi all,
I added a debian/watch file to my package ldap-account-manager some time
ago. But the status on Debian Health is still that no watch file is
existent.
This is the Debian Health page of my package:
http://dehs.alioth.debian.org/maintainer.php?name=ldap-account-manager
The file contains th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Don Armstrong schrieb:
| On Tue, 02 Nov 2004, Roland Gruber wrote:
|
|>LAM is a webfrontend for managing LDAP accounts which is written in
|>PHP. But there is also a small script included which allows to
|>manage Quota etc.. This script use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Don Armstrong schrieb:
| On Tue, 02 Nov 2004, Roland Gruber wrote:
|
|>LAM is a webfrontend for managing LDAP accounts which is written in
|>PHP. But there is also a small script included which allows to
|>manage Quota etc.. This script use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I got a bug report (#279371) for LDAP Account Manager (LAM) because
parts of the program use a specific Perl module which is not packaged
for Debian.
LAM is a webfrontend for managing LDAP accounts which is written in PHP.
But there is also
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I got a bug report (#279371) for LDAP Account Manager (LAM) because
parts of the program use a specific Perl module which is not packaged
for Debian.
LAM is a webfrontend for managing LDAP accounts which is written in PHP.
But there is also a sm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I got the info from Andreas Barth that Matthew is at the Australian
Linuxconf. So I'll wait some more days.
Greetings,
Roland
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I got the info from Andreas Barth that Matthew is at the Australian
Linuxconf. So I'll wait some more days.
Greetings,
Roland
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.moz
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I am maintainer of the ldap-account-manager package. It came into Debian
in November 2003 and is sponsored by Matthew Palmer.
The problem is that since the end of December Matthew did not reply to
my mails. There were two new releases of the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I am maintainer of the ldap-account-manager package. It came into Debian
in November 2003 and is sponsored by Matthew Palmer.
The problem is that since the end of December Matthew did not reply to
my mails. There were two new releases of the pa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I am looking for a sponsor for LDAP Account Manager.
We recently released our first beta version (0.4) and the new package
should conform with the Debian policy.
The dynamic configuration files are now in
/var/lib/ldap-account-manager. They w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
I am looking for a sponsor for LDAP Account Manager.
We recently released our first beta version (0.4) and the new package
should conform with the Debian policy.
The dynamic configuration files are now in
/var/lib/ldap-account-manager. They wil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Craig Small wrote:
| This reminds me. It has a serious lack of error correction problem.
| I tried editing my account got to the end, had a problem (i suspect
| that i was missing an objectclass and had syntax checking on) and it
| destroyed my accou
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Craig Small wrote:
| This reminds me. It has a serious lack of error correction problem.
| I tried editing my account got to the end, had a problem (i suspect
| that i was missing an objectclass and had syntax checking on) and it
| destroyed my account
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Craig Small wrote:
| On Tue, Sep 02, 2003 at 08:19:45PM +0200, Roland Gruber wrote:
| Unpacking ldap-account-manager (from ldap-account-manager_0.3-1_all.deb)
| ...
| Setting up ldap-account-manager (0.3-1) ...
| chown: failed to get attributes of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Craig Small wrote:
| On Tue, Sep 02, 2003 at 08:19:45PM +0200, Roland Gruber wrote:
| Unpacking ldap-account-manager (from ldap-account-manager_0.3-1_all.deb)
| ...
| Setting up ldap-account-manager (0.3-1) ...
| chown: failed to get attributes of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Keith Dunwoody wrote:
| I think there's already a lam source package in the archive (which
| builds the lam3 binary package, among others), and has been a lam binary
| package in the past, so you might have to pick a different name. LAM in
| thi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Keith Dunwoody wrote:
| I think there's already a lam source package in the archive (which
| builds the lam3 binary package, among others), and has been a lam binary
| package in the past, so you might have to pick a different name. LAM in
| this
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
thanks to Andreas Barth and Artur R. Czechowski for their explanations
about the packet system.
I am looking for a sponsor to upload my packages. The package will be
maintained by myself and I already submitted an ITP bug (#208406).
So I nee
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
thanks to Andreas Barth and Artur R. Czechowski for their explanations
about the packet system.
I am looking for a sponsor to upload my packages. The package will be
maintained by myself and I already submitted an ITP bug (#208406).
So I need a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
|>What is an ITP bug? I read some of the new maintainers manual but I am
|>not really familiar with the process of pushing packages into Debian.
|
| New Maintainers' Guide gives you a hint in chapter 2 section 1:
| Choose your program[1].
| However pa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
|>What is an ITP bug? I read some of the new maintainers manual but I am
|>not really familiar with the process of pushing packages into Debian.
|
| New Maintainers' Guide gives you a hint in chapter 2 section 1:
| Choose your program[1].
| However pack
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thorsten Sauter wrote:
| * Roland Gruber <[EMAIL PROTECTED]> [2003-09-01 18:53]:
| | the LDAP Account Manager (LAM) team is looking for a sponsor.
| |
| | LAM is a tool to manage Samba and Unix accounts in (Open)LDAP. It is
| | written in PH
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
the LDAP Account Manager (LAM) team is looking for a sponsor.
LAM is a tool to manage Samba and Unix accounts in (Open)LDAP. It is
written in PHP4 and should run on all architectures.
Features:
- - management of Unix user and group accounts (
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thorsten Sauter wrote:
| * Roland Gruber <[EMAIL PROTECTED]> [2003-09-01 18:53]:
| | the LDAP Account Manager (LAM) team is looking for a sponsor.
| |
| | LAM is a tool to manage Samba and Unix accounts in (Open)LDAP. It is
| | written in PH
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi all,
the LDAP Account Manager (LAM) team is looking for a sponsor.
LAM is a tool to manage Samba and Unix accounts in (Open)LDAP. It is
written in PHP4 and should run on all architectures.
Features:
- - management of Unix user and group account
42 matches
Mail list logo
