Re: YMMFPQ (Yet More My First Package Questions)
Hi, * Thomas -Balu- Walter <[EMAIL PROTECTED]> [2003-08-27 18:07]: | As usual I've used the New Maintainers' Guide to get started and nearly | all went well. Besides two warnings lintian gives me: | | W: camsource source: newer-standards-version 3.5.10 | -> which should be fixed by a new lintian version; I've used the one |from testing | W: camsource: postinst-should-not-set-usr-doc-link | -> should be fixed with a new debhelper (if built on unstable e.g.) | | So I can ignore those warnings, correct? you _must_ use sid/unstable to build your packages. If the package is only for yourself, you can safely ignore the lintian warnings above. | Another problem I experienced is that I have to start dpkg-buildpackage | using [EMAIL PROTECTED], because it tries to find a key related to | 'Thomas -Balu- Walter <[EMAIL PROTECTED]>', but gpg stored my key as | 'Thomas Walter (Balu) <[EMAIL PROTECTED]>'. | | Is it a bug or a feature that dpkg-buildpackage doesn't only use the | email address to make gpg search for keys? dpkg-buildpackage tries to sign the package with your name, which is used in the debian/changelog file. You can change the name (and email) in this file to the name which is used for your gpg key. | Checking the contents of the .deb lists some include-files which should | not be there IMHO. Am I supposed to put them in a camsource-dev package | as they are only needed if one wants to develop new modules? What would | be the best way to handle those? fixing the makefile or simply removing the include files after the "make install". rm -fr $(CURDIR)/debian/camsource/usr/include Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) pgpyAQlrYzQCE.pgp Description: PGP signature
Re: YMMFPQ (Yet More My First Package Questions)
Hi Thomas, * Thomas -Balu- Walter <[EMAIL PROTECTED]> [2003-08-28 10:06]: | And what about people that want to develop modules for camsource? They | might need them. I only see two choices: leave them in the main package | or create an additional camsource-dev package (which I need to figure | out then). create a second package, which contains all relevant files (headers, libs, ...) to compile camsource modules: $package-dev Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) pgppeeCeFj2n0.pgp Description: PGP signature
Re: RFS: LDAP Account Manager
* 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 PHP4 and should run on all architectures. interesting. | | Debian package: Homepage or | http://mentors.debian.net/debian/dists/unstable/main/binary-all/ldap-account-manager to help possible sponsors I guess it's a good idea to post some basic informations about the package. Is there a ITP bug filled? Basic package infos like short description, long, description, ... Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) pgphwUPXKm5wT.pgp Description: PGP signature
Re: pbuilder: How to get debconf interactive?
Hi, * Frank K??ster <[EMAIL PROTECTED]> [2003-09-05 16:41]: | to test debconf questions I would like to do installations, upgrades | etc. in a pbuilder environment. However, debconf seems to be fixed to | the noninteractive frontend. I can get something else by setting | DEBIAN_FRONTEND, but even after | | DEBIAN_FRONTEND=dialog dpkg-reconfigure debconf | | and choosing dialog (which was on the top anyway, IIRC) debconf stayed | silent. I couldn't find any mention of debconf or confmodule in | pbuilders manual page, the html documentation or the executables (even | in /usr/lib/pbuilder). | | Any ideas? untested, but you can try to change the DEBIAN_FRONTEND variable in /etc/pbuilderrc. Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) pgpoCsJhcewfU.pgp Description: PGP signature
Re: RFS: phpsysinfo
* Frederik Schueler <[EMAIL PROTECTED]> [2003-10-06 23:52]: | I am seeking a sponsor for phpsysinfo, which was orphaned some weeks | ago. I renamed the bug #211701 to RFA, hope this was the right procedure. | | preliminary packages are availeble at | | deb http://users.idf.de/~fs/debian ./ | deb-src http://users.idf.de/~fs/debian ./ | | the upload would close 1 RC bug and 3 others by changelog, and 2 more | bugs could be closed because they where fixed upstream. I'm using the package myself. So I'm willing to sponsor you. | I am planning to apply as new maintainer, so if someone in the area | around Hamburg, Germany is willing to sign gpg keys, please let me know | :-) | bad timing. :) One week ago, there was a meeting of the debian-installer Team in Oldenburg. Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) signature.asc Description: Digital signature
How to deal with sql-database structures on upgrade
Hi all, I'm going to adopt cacti[1]. But I have a problems with a clean upgrade path to the new upstream version. Cacti use a mysql database to store the configuration values (including users/password, graphic options, layouts, ...). The new upstream version (0.8.x) use a completly new designed database structure then the old version, which is currently already packed for Debian. I have tried to write some postinst scripts to migrate the existing database into the new one, but I think now this is impossible, because maybe informations which are needed in the new version are missing in the old one. Some other packages like sysstat simply prints a message about a incompatible dataformat, and move or delete the old datafile. Is this an acceptable way for such a program also? And if so, should I do a database export first, before deleting and recreating the database with the new tables? Any hints are welcome :-) Thanks for your help Thorsten [1] Description: Frontend to rrdtool for monitoring systems and services Cacti is a complete frondend to rrdtool, it stores all of the necessary information to create graphs and populate them with data in a MySQL database. The frontend is completely PHP driven. Along with being able to maintain Graphs, Data Sources, and Round Robin Archives in a database, cacti handles the data gathering also. There is also SNMP support for those used to creating traffic graphs with MRTG. signature.asc Description: Digital signature
Re: RFS: passepartout - fixes 1 RC bug
Hi Gaudenz, * Gaudenz Steinlin <[EMAIL PROTECTED]> [2004-01-19 17:53]: | My sponsor for passepartout is on vacation. Therefore I'm looking for a | "one time" sponsor for my package passepartout. The package was | initially sponsored by Matthias Ulrichs and later by Sebastian Ley. | | The new package includes the following changes: |* New upstream release (closes: #225925, #228088) |* command renamed to passepartout upstream (closes: #226082) |* NEWS corrected upstream (closes: #225551) |* manpages now included upstream |* updated configuration file /etc/pptout | | In addition to 1 RC bug the sponsoring of this package would close | all other bugs. | | You can download the package at: | http://www.soziologie.ch/~steinlin/passepartout/ I'm willing to sponsor you. Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?)
Re: RFS: SniffDet
Hi Marcin, * Marcin Kurpiewski <[EMAIL PROTECTED]> [2004-01-23 23:32]: | Package name: sniffdet | | Licence: GPL | | Short description: | Remote sniffers detection in TCP/IP networks are you still looking for a sponsor? Before you should create an ITP for your package. I can't find such a bug. If you have filled the ITP, I'm willing to sponsor you. Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) signature.asc Description: Digital signature
Re: RFS(2) : xtermcontrol
Hi Robert, * Robert Lemmen <[EMAIL PROTECTED]> [2004-01-29 17:43]: | come on guys, it's a nice small package without massive | dependencies that is really usefull (for some people, of course), it is | lintian- and linda clean and builds fine in a chroot, should be no | problem. are you still looking for a sponsor? If so, please contact me privatly and I'll be happy to sponsor your package. Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) signature.asc Description: Digital signature
Re: Packaging for Sid on the Debian machines?
* Jochen Friedrich <[EMAIL PROTECTED]> [2004-03-10 07:48]: | Hi Jörgen, | | > Question: how and where do I build for Sid? | > Has '+chroots' anything to do with it? | | Just try "dchroot sid" on one of these machines :-) | Hint: copy your package to /home/chroots/sid/home/ first. nope that isn't needed. The home directories are available via bind-mount. Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) signature.asc Description: Digital signature
Re: Packaging for Sid on the Debian machines?
* Joe Nahmias <[EMAIL PROTECTED]> [2004-03-10 19:08]: | (base)[EMAIL PROTECTED]:~$ dchroot sid | (unstable)[EMAIL PROTECTED]:~$ cat /etc/debian_version ^ how do you do this? I have also tried something like this, but without any success. Thanks Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?)
Re: Packaging for Sid on the Debian machines?
* Colin Watson <[EMAIL PROTECTED]> [2004-03-10 20:14]: | On Wed, Mar 10, 2004 at 07:52:20PM +0100, Thorsten Sauter wrote: | > * Joe Nahmias <[EMAIL PROTECTED]> [2004-03-10 19:08]: | > | (base)[EMAIL PROTECTED]:~$ dchroot sid | > | (unstable)[EMAIL PROTECTED]:~$ cat /etc/debian_version | > | > ^ | > | > how do you do this? I have also tried something like this, but without | > any success. | | Put a file in each chroot (in /etc, say) identifying it, and then read | it into a shell variable in .bashrc so that your prompt can use it. ok. I do this on my private chroots. But how can I make something on machines without root permissions. Like the debian.org machines. I have played with an dchroot wrapper shellscript and exported environment variables, but dchroot remove the complete environment. Maybe the debian-admin team could create such a file in every chroot filesystem? Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) signature.asc Description: Digital signature
Re: Packaging for Sid on the Debian machines?
* Martin Michlmayr <[EMAIL PROTECTED]> [2004-03-10 20:02]: | * Thorsten Sauter <[EMAIL PROTECTED]> [2004-03-10 19:52]: | > | (base)[EMAIL PROTECTED]:~$ dchroot sid | > | (unstable)[EMAIL PROTECTED]:~$ cat /etc/debian_version | > | > ^ | > | > how do you do this? I have also tried something like this, but without | > any success. | | Look at the dchroot package. | | | Description: Execute commands under different root filesystems | This package contains a setuid binary that allows users to execute a shell or | other command under different root filesystems. A typical installation might | provide 'stable', 'testing' and 'unstable' chroots. Users can move between | chroots as necessary. I doesn't mean the dchroot command in generally. I mean the "(base)" and "(unstable)" string before the shell prompt. Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?)
question about creating own devices
Hi,
I'm currently createing a package which needs a device file in /dev.
This device is only available after applying a kernel patch, so
the standard makedev script doesn't known anything about it.
Rever to the debian policy 11.6 (device files), packages should not
create device files without the makedev script. But the whole package
isn't usable without the device.
So, is it legal to create the device (with the mknod command) after
quering the user via debconf ("should I create the device for you...?")?
And removing it in the postrm script (only if the package is purged)?
I have also included detailed information about this in the
README.Debian file. So the user should known enough about this step.
Any ideas/comments?
Tia
Thorsten
--
Thorsten Sauter
<[EMAIL PROTECTED]>
(Is there life after /sbin/halt -p?)
msg08022/pgp0.pgp
Description: PGP signature
how to deal with i386 packages only
Hello, what should happen with programs, which currently runs only on i386 architectures? Is it a good idea to upload such programs into the debian archive. Sure, I must simply change the Architecture field in the control file: Architecture: i386 ...but is this generaly a good solution? And secondly, how to deal which packages, which ar binary indep, but depend on a package, which is only available on one platform? Leave the Arch-field on "all" or set it also to "i386"? Thanks Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) msg08031/pgp0.pgp Description: PGP signature
Re: RFS (2nd call): tsclient-0.56
Hi, I think you have enough time, because tsclient should go to non-US and the incoming queue isn't activated since the fire. :) Maybe thats the problem. Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) msg08054/pgp0.pgp Description: PGP signature
[mindas@ziedas.ktu.lt: Bug#177332: libphp-adodb on testing should be applied to the stable]
Hi all, just to make sure. Is the following bug report (problem) enough to upload the libphp-adodb version from testing into stable? I think not. It's only a feature request for the old version which is already included in the latest libphp-adodb version. And the in testing is much newer then the stable version: it's internal complete new version with many code rewrites. Should I do nothing an tag as wontfix? Or try to upload into stable? Any comments? Thanks for your help... Bye Thorsten - Forwarded message from Mindaugas Zaksauskas <[EMAIL PROTECTED]> - To: [EMAIL PROTECTED] Subject: Bug#177332: libphp-adodb on testing should be applied to the stable Package: libphp-adodb Version: 1.51-1 The version of libphp-adodb package on stable release should be upgraded to (at least the one that exists on testing). The reason is obvious: when I use the function GetUpdateSQL, it returns me the query string that _contains_no_ WHERE clause, e.g. $updateSQL = $conn->GetUpdateSQL($rs, $record); gives me "UPDATE FOO set bar=1". I guess this will be quite strong argument. Also, it'd be great if the package upgrade script should change the php.ini include path. Stable has include_path = ".:/php/includes:/usr/lib/adodb" and after the upgrade to the version 2.50-1 (that is currently available on testing), the new (and *correct*) location of the adodb library is include_path = ".:/php/includes:/usr/share/adodb" However, there are no suggestions to fix this path for php4-apache, php4-cgi package installations. If you need any aditional details on this - don't hesitate to mail me. Mindaugas Zaksauskas - End forwarded message - -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) msg08342/pgp0.pgp Description: PGP signature
Re: Some packages to you for testing
Hi, * Jaime Robles <[EMAIL PROTECTED]> [2003-06-03 23:48]: > KWifimanager, a WIFI card configuration program. > > I would like you to test them and check for bugs, errors and so on. 1.) kwifimanager has incorrect build-depends (at least kde headers are missing) 2.) you should check you package with lintian and linda: $ lintian -c kwifimanager_1.0.2-1_i386.changes | wc -l 6 $ linda kwifimanager_1.0.2-1_i386.changes | wc -l 1 Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) pgp0.pgp Description: PGP signature
Re: YMMFPQ (Yet More My First Package Questions)
Hi, * Thomas -Balu- Walter <[EMAIL PROTECTED]> [2003-08-27 18:07]: | As usual I've used the New Maintainers' Guide to get started and nearly | all went well. Besides two warnings lintian gives me: | | W: camsource source: newer-standards-version 3.5.10 | -> which should be fixed by a new lintian version; I've used the one |from testing | W: camsource: postinst-should-not-set-usr-doc-link | -> should be fixed with a new debhelper (if built on unstable e.g.) | | So I can ignore those warnings, correct? you _must_ use sid/unstable to build your packages. If the package is only for yourself, you can safely ignore the lintian warnings above. | Another problem I experienced is that I have to start dpkg-buildpackage | using [EMAIL PROTECTED], because it tries to find a key related to | 'Thomas -Balu- Walter <[EMAIL PROTECTED]>', but gpg stored my key as | 'Thomas Walter (Balu) <[EMAIL PROTECTED]>'. | | Is it a bug or a feature that dpkg-buildpackage doesn't only use the | email address to make gpg search for keys? dpkg-buildpackage tries to sign the package with your name, which is used in the debian/changelog file. You can change the name (and email) in this file to the name which is used for your gpg key. | Checking the contents of the .deb lists some include-files which should | not be there IMHO. Am I supposed to put them in a camsource-dev package | as they are only needed if one wants to develop new modules? What would | be the best way to handle those? fixing the makefile or simply removing the include files after the "make install". rm -fr $(CURDIR)/debian/camsource/usr/include Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) pgp0.pgp Description: PGP signature
Re: YMMFPQ (Yet More My First Package Questions)
Hi Thomas, * Thomas -Balu- Walter <[EMAIL PROTECTED]> [2003-08-28 10:06]: | And what about people that want to develop modules for camsource? They | might need them. I only see two choices: leave them in the main package | or create an additional camsource-dev package (which I need to figure | out then). create a second package, which contains all relevant files (headers, libs, ...) to compile camsource modules: $package-dev Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) pgp0.pgp Description: PGP signature
Re: RFS: LDAP Account Manager
* 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 PHP4 and should run on all architectures. interesting. | | Debian package: Homepage or | http://mentors.debian.net/debian/dists/unstable/main/binary-all/ldap-account-manager to help possible sponsors I guess it's a good idea to post some basic informations about the package. Is there a ITP bug filled? Basic package infos like short description, long, description, ... Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) pgp0.pgp Description: PGP signature
Re: pbuilder: How to get debconf interactive?
Hi, * Frank K??ster <[EMAIL PROTECTED]> [2003-09-05 16:41]: | to test debconf questions I would like to do installations, upgrades | etc. in a pbuilder environment. However, debconf seems to be fixed to | the noninteractive frontend. I can get something else by setting | DEBIAN_FRONTEND, but even after | | DEBIAN_FRONTEND=dialog dpkg-reconfigure debconf | | and choosing dialog (which was on the top anyway, IIRC) debconf stayed | silent. I couldn't find any mention of debconf or confmodule in | pbuilders manual page, the html documentation or the executables (even | in /usr/lib/pbuilder). | | Any ideas? untested, but you can try to change the DEBIAN_FRONTEND variable in /etc/pbuilderrc. Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) pgp0.pgp Description: PGP signature
Re: RFS: phpsysinfo
* Frederik Schueler <[EMAIL PROTECTED]> [2003-10-06 23:52]: | I am seeking a sponsor for phpsysinfo, which was orphaned some weeks | ago. I renamed the bug #211701 to RFA, hope this was the right procedure. | | preliminary packages are availeble at | | deb http://users.idf.de/~fs/debian ./ | deb-src http://users.idf.de/~fs/debian ./ | | the upload would close 1 RC bug and 3 others by changelog, and 2 more | bugs could be closed because they where fixed upstream. I'm using the package myself. So I'm willing to sponsor you. | I am planning to apply as new maintainer, so if someone in the area | around Hamburg, Germany is willing to sign gpg keys, please let me know | :-) | bad timing. :) One week ago, there was a meeting of the debian-installer Team in Oldenburg. Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) signature.asc Description: Digital signature
How to deal with sql-database structures on upgrade
Hi all, I'm going to adopt cacti[1]. But I have a problems with a clean upgrade path to the new upstream version. Cacti use a mysql database to store the configuration values (including users/password, graphic options, layouts, ...). The new upstream version (0.8.x) use a completly new designed database structure then the old version, which is currently already packed for Debian. I have tried to write some postinst scripts to migrate the existing database into the new one, but I think now this is impossible, because maybe informations which are needed in the new version are missing in the old one. Some other packages like sysstat simply prints a message about a incompatible dataformat, and move or delete the old datafile. Is this an acceptable way for such a program also? And if so, should I do a database export first, before deleting and recreating the database with the new tables? Any hints are welcome :-) Thanks for your help Thorsten [1] Description: Frontend to rrdtool for monitoring systems and services Cacti is a complete frondend to rrdtool, it stores all of the necessary information to create graphs and populate them with data in a MySQL database. The frontend is completely PHP driven. Along with being able to maintain Graphs, Data Sources, and Round Robin Archives in a database, cacti handles the data gathering also. There is also SNMP support for those used to creating traffic graphs with MRTG. signature.asc Description: Digital signature
Re: RFS: passepartout - fixes 1 RC bug
Hi Gaudenz, * Gaudenz Steinlin <[EMAIL PROTECTED]> [2004-01-19 17:53]: | My sponsor for passepartout is on vacation. Therefore I'm looking for a | "one time" sponsor for my package passepartout. The package was | initially sponsored by Matthias Ulrichs and later by Sebastian Ley. | | The new package includes the following changes: |* New upstream release (closes: #225925, #228088) |* command renamed to passepartout upstream (closes: #226082) |* NEWS corrected upstream (closes: #225551) |* manpages now included upstream |* updated configuration file /etc/pptout | | In addition to 1 RC bug the sponsoring of this package would close | all other bugs. | | You can download the package at: | http://www.soziologie.ch/~steinlin/passepartout/ I'm willing to sponsor you. Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: SniffDet
Hi Marcin, * Marcin Kurpiewski <[EMAIL PROTECTED]> [2004-01-23 23:32]: | Package name: sniffdet | | Licence: GPL | | Short description: | Remote sniffers detection in TCP/IP networks are you still looking for a sponsor? Before you should create an ITP for your package. I can't find such a bug. If you have filled the ITP, I'm willing to sponsor you. Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) signature.asc Description: Digital signature
Re: RFS(2) : xtermcontrol
Hi Robert, * Robert Lemmen <[EMAIL PROTECTED]> [2004-01-29 17:43]: | come on guys, it's a nice small package without massive | dependencies that is really usefull (for some people, of course), it is | lintian- and linda clean and builds fine in a chroot, should be no | problem. are you still looking for a sponsor? If so, please contact me privatly and I'll be happy to sponsor your package. Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) signature.asc Description: Digital signature
Re: Packaging for Sid on the Debian machines?
* Jochen Friedrich <[EMAIL PROTECTED]> [2004-03-10 07:48]: | Hi Jörgen, | | > Question: how and where do I build for Sid? | > Has '+chroots' anything to do with it? | | Just try "dchroot sid" on one of these machines :-) | Hint: copy your package to /home/chroots/sid/home/ first. nope that isn't needed. The home directories are available via bind-mount. Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) signature.asc Description: Digital signature
Re: Packaging for Sid on the Debian machines?
* Joe Nahmias <[EMAIL PROTECTED]> [2004-03-10 19:08]: | (base)[EMAIL PROTECTED]:~$ dchroot sid | (unstable)[EMAIL PROTECTED]:~$ cat /etc/debian_version ^ how do you do this? I have also tried something like this, but without any success. Thanks Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Packaging for Sid on the Debian machines?
* Colin Watson <[EMAIL PROTECTED]> [2004-03-10 20:14]: | On Wed, Mar 10, 2004 at 07:52:20PM +0100, Thorsten Sauter wrote: | > * Joe Nahmias <[EMAIL PROTECTED]> [2004-03-10 19:08]: | > | (base)[EMAIL PROTECTED]:~$ dchroot sid | > | (unstable)[EMAIL PROTECTED]:~$ cat /etc/debian_version | > | > ^ | > | > how do you do this? I have also tried something like this, but without | > any success. | | Put a file in each chroot (in /etc, say) identifying it, and then read | it into a shell variable in .bashrc so that your prompt can use it. ok. I do this on my private chroots. But how can I make something on machines without root permissions. Like the debian.org machines. I have played with an dchroot wrapper shellscript and exported environment variables, but dchroot remove the complete environment. Maybe the debian-admin team could create such a file in every chroot filesystem? Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) signature.asc Description: Digital signature
Re: Packaging for Sid on the Debian machines?
* Martin Michlmayr <[EMAIL PROTECTED]> [2004-03-10 20:02]: | * Thorsten Sauter <[EMAIL PROTECTED]> [2004-03-10 19:52]: | > | (base)[EMAIL PROTECTED]:~$ dchroot sid | > | (unstable)[EMAIL PROTECTED]:~$ cat /etc/debian_version | > | > ^ | > | > how do you do this? I have also tried something like this, but without | > any success. | | Look at the dchroot package. | | | Description: Execute commands under different root filesystems | This package contains a setuid binary that allows users to execute a shell or | other command under different root filesystems. A typical installation might | provide 'stable', 'testing' and 'unstable' chroots. Users can move between | chroots as necessary. I doesn't mean the dchroot command in generally. I mean the "(base)" and "(unstable)" string before the shell prompt. Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
how to deal with i386 packages only
Hello, what should happen with programs, which currently runs only on i386 architectures? Is it a good idea to upload such programs into the debian archive. Sure, I must simply change the Architecture field in the control file: Architecture: i386 ...but is this generaly a good solution? And secondly, how to deal which packages, which ar binary indep, but depend on a package, which is only available on one platform? Leave the Arch-field on "all" or set it also to "i386"? Thanks Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) pgp5PdWwpKrQu.pgp Description: PGP signature
Re: RFS (2nd call): tsclient-0.56
Hi, I think you have enough time, because tsclient should go to non-US and the incoming queue isn't activated since the fire. :) Maybe thats the problem. Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) pgpcpCasuxBph.pgp Description: PGP signature
question about creating own devices
Hi,
I'm currently createing a package which needs a device file in /dev.
This device is only available after applying a kernel patch, so
the standard makedev script doesn't known anything about it.
Rever to the debian policy 11.6 (device files), packages should not
create device files without the makedev script. But the whole package
isn't usable without the device.
So, is it legal to create the device (with the mknod command) after
quering the user via debconf ("should I create the device for you...?")?
And removing it in the postrm script (only if the package is purged)?
I have also included detailed information about this in the
README.Debian file. So the user should known enough about this step.
Any ideas/comments?
Tia
Thorsten
--
Thorsten Sauter
<[EMAIL PROTECTED]>
(Is there life after /sbin/halt -p?)
pgpHkEbiiKAwP.pgp
Description: PGP signature
[mindas@ziedas.ktu.lt: Bug#177332: libphp-adodb on testing should be applied to the stable]
Hi all, just to make sure. Is the following bug report (problem) enough to upload the libphp-adodb version from testing into stable? I think not. It's only a feature request for the old version which is already included in the latest libphp-adodb version. And the in testing is much newer then the stable version: it's internal complete new version with many code rewrites. Should I do nothing an tag as wontfix? Or try to upload into stable? Any comments? Thanks for your help... Bye Thorsten - Forwarded message from Mindaugas Zaksauskas <[EMAIL PROTECTED]> - To: [EMAIL PROTECTED] Subject: Bug#177332: libphp-adodb on testing should be applied to the stable Package: libphp-adodb Version: 1.51-1 The version of libphp-adodb package on stable release should be upgraded to (at least the one that exists on testing). The reason is obvious: when I use the function GetUpdateSQL, it returns me the query string that _contains_no_ WHERE clause, e.g. $updateSQL = $conn->GetUpdateSQL($rs, $record); gives me "UPDATE FOO set bar=1". I guess this will be quite strong argument. Also, it'd be great if the package upgrade script should change the php.ini include path. Stable has include_path = ".:/php/includes:/usr/lib/adodb" and after the upgrade to the version 2.50-1 (that is currently available on testing), the new (and *correct*) location of the adodb library is include_path = ".:/php/includes:/usr/share/adodb" However, there are no suggestions to fix this path for php4-apache, php4-cgi package installations. If you need any aditional details on this - don't hesitate to mail me. Mindaugas Zaksauskas - End forwarded message - -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) pgpKsb2sLyIyp.pgp Description: PGP signature
licence question
Hi all, I have collected some nice skins for xmms-kjofol from various webpages around. I plan to include these skins into xmms-kjofol. Unfortunately, most of these zip-files doesn't include any copyright information. For this reason I have written to the authors and ask to publish the skins under the GPL or any other DFSG-compliant licence. Now, I have some answers from the authors and most of them simply write something like "GPL is fine", "you have my permission", and others like these. My question is now, how should I deal with this? Including a copyright file (with the selected copyright) into the zip files with the license, include the answer emails from the authors, do nothing? Thanks for your help Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) pgpkKIYRVeVLT.pgp Description: PGP signature
Re: Some packages to you for testing
Hi, * Jaime Robles <[EMAIL PROTECTED]> [2003-06-03 23:48]: > KWifimanager, a WIFI card configuration program. > > I would like you to test them and check for bugs, errors and so on. 1.) kwifimanager has incorrect build-depends (at least kde headers are missing) 2.) you should check you package with lintian and linda: $ lintian -c kwifimanager_1.0.2-1_i386.changes | wc -l 6 $ linda kwifimanager_1.0.2-1_i386.changes | wc -l 1 Bye Thorsten -- Thorsten Sauter <[EMAIL PROTECTED]> (Is there life after /sbin/halt -p?) pgpN85Sw3wk93.pgp Description: PGP signature
