Re: debian OID / dicom3tools packaging

2009-01-27 Thread Michael Hanke
On Tue, Jan 27, 2009 at 01:05:25PM +0100, Mathieu Malaterre wrote:
> Hi there,
> 
>   I am in the process of packaging dicom3tools:
> 
> * http://debian-med.alioth.debian.org/tasks/imaging.html
> 
>   One important step of the packaging is the DICOM UID. In order to
> write a DICOM file, one need a unique UID for each instance of a DICOM
> object.  For more details:
> 
> http://www.dclunie.com/medical-image-faq/html/part2.html#UID
> 
> As documented at:
> 
> http://www.dclunie.com/medical-image-faq/html/part8.html#UIDRegistration

I wonder whether it is possible/feasible to come up with a single OID
suiteable for all users. IMHO every user/institution would need an OID
-- since somehow each DICOM generated by that OID needs to result in a unique
UID.

In a medical context there is probably already an OID available that
could be used for this purpose. For all others it might be helpful to
provide some guidance for the users how such an OID can be constructed.

Maybe it is possible to generate 'dummy' OIDs in a Debian namespace to
ease the life of people who are not interested in generating 'official' DICOMS
but simply need to convert files from one format into another.


Michael


-- 
GPG key:  1024D/3144BE0F Michael Hanke
http://apsy.gse.uni-magdeburg.de/hanke
ICQ: 48230050


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



Looking for a mentor for 'arno-iptables-firewall' package

2005-08-25 Thread Michael Hanke
Hi!

I found it difficult to setup a NAT firewall with iptables - till I
found "Arno's Iptables firewall" - which is an extremly easy to
understand configuration shell script.

Unfortunately it is not part of Debian, yet.

So I decided to give it a try and packaged it.

I would like someone to have a look at it:

http://apsy.gse.uni-magdeburg.de/~hanke/mentors

There is one open issue. To actually setup the firewall one has to set
the name of the external interface. Therefore it would be nice if a
list of interfaces could be generated and displayed through debconf,
but I don't know how to do it. So I decided to display a note instead,
that this has to be done manually.

I would be happy to get suggestions for improvements from the list
(e.g. What would be the best time to start the init-script during
system startup, etc.)


Regards,

Michael



Re: Looking for a mentor for 'arno-iptables-firewall' package

2005-09-17 Thread Michael Hanke
On 9/15/05, Sven Mueller <[EMAIL PROTECTED]> wrote:
> Joost van Baal wrote on 14/09/2005 10:56:
> > On Thu, Aug 25, 2005 at 05:11:03PM +0200, Michael Hanke wrote:
> > 
> >>I would like someone to have a look at it:
> >>http://apsy.gse.uni-magdeburg.de/~hanke/mentors
> > 
> > debian-mentors readers: I am looking at it know.  The package is marked
> > as such on http://sponsors.debian.net/ .
> > 
> >>There is one open issue. To actually setup the firewall one has to set
> >>the name of the external interface. Therefore it would be nice if a
> >>list of interfaces could be generated and displayed through debconf,
> >>but I don't know how to do it.
> > 
> > The only thing I can come up with is: parse the
> > 
> >  ip -o link show
> > 
> > output.  You'd have to depend upon iproute for this, of course.
> 
> Why not use "ifconfig -a"? On all my systems, it seems to work OK:
> 
> ifconfig -a | grep Link\ encap \
> | sed -e 's/[   ][  ]*Link.*//;s/:[0-9]*//' \
> | sort -u
> 
> The sed line removes the "Link encap" and hwaddr stuff and subsequently
> removes :[0-9]* tails from alias interfaces. Since that could list
> interfaces which have aliases more than once, the sort -u is used.
> 
> I'm assuming here that you wouldn't want to use an alias interface as
> the name of the external interface...
That's it! Thanks. One question left: Is there any situation you can
think of where an external interface would have no hardware address?
If there is no such situation one could grep for 'HWaddr' instead.


Ciao,

Michael


-- 

GPG key:  1024D/3144BE0F Michael Hanke
http://apsy.gse.uni-magdeburg.de/hanke
ICQ: 48230050



Lintian error binary-or-shlib-defines-rpath

2005-10-11 Thread Michael Hanke
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hi!

I'm packaging kbibtex which is a KDE bibtex editor. Lintian reports the
following error for the package:

N: Processing 1 packages...
N: 
N: Processing binary package kbibtex (version 0.1.2a-2) ...
W: kbibtex: binary-or-shlib-defines-rpath ./usr/bin/kbibtex /usr/lib
N:
N:   The binary or shared library defines the `RPATH'. Usually this is a
N:   bad thing. Most likely you will find a Makefile with a line like:
N:   gcc test.o -o test -Wl,--rpath
N:   or
N:   gcc test.o -o test -R/usr/local/lib
N:   Please contact debian-devel@lists.debian.org if you have questions
N:   about this.
N:
W: kbibtex: binary-or-shlib-defines-rpath
./usr/lib/kde3/libkbibtexpart.so /usr/lib


I first thought there might be something wrong with my debian/rules, so
I switched to CDBS to get a second oppinion. That made the rules file
pretty simple

#!/usr/bin/make -f
include /usr/share/cdbs/1/rules/debhelper.mk
include /usr/share/cdbs/1/class/kde.mk

But the error remained. CDBS makes configure get called with the
follwing arguments.

./configure  --build=i486-linux-gnu --prefix=/usr
- - --includedir="\${prefix}/include/kde" --mandir="\${prefix}/share/man"
- - --infodir="\${prefix}/share/info" --sysconfdir=/etc --localstatedir=/var
- - --libexecdir="\${prefix}/lib/kbibtex"  --disable-maintainer-mode
- - --with-qt-dir=/usr/share/qt3 --disable-rpath --with-xinerama

The argument --disable-rpath does not have the promised consequence -
lintian still reports the error.

Does someone have an idea what I'm doing wrong?

The package is available from mentors.debian.net

Thanks in advance,


Michael

- --
GPG key:  1024D/3144BE0F Michael Hanke
http://apsy.gse.uni-magdeburg.de/hanke
ICQ: 48230050

-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFDTBgT93+NsjFEvg8RAlJAAKC1Eof1yq/lwDORpvtgoTFWGlX8WwCcCUqH
26nRRl9FA1pljVBHgv0LseE=
=vu5r
-END PGP SIGNATURE-


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



Lintian error about missing debconf dependency (which is not missing)

2005-12-21 Thread Michael Hanke
Hi!


I'm preparing a package which uses debconf. When I run lintian on the
package the following error is reported:

E: arno-iptables-firewall: settitle-requires-versioned-depends config
N:
N:   Debconf only supports the SETTITLE command as of version 1.3.22. To
N:   ensure upgrades work correctly, packages that use this new command
N:   should declare a dependency on that version of debconf.
N:

The strange thing is, that I have the following line in the control file:

Depends: ${misc:Depends}, iptables (>=1.2.11), gawk, debconf (>=1.3.22) | 
debconf-2.0


There is clearly a versioned debconf dependency. The above line is
expanded to the following when building the package.

Depends: debconf (>= 0.5) | debconf-2.0, iptables (>= 1.2.11), gawk, debconf 
(>= 1.3.22) | debconf-2.0


Does anybody know where the problem is?

Thanks in advance.

Cheers,

Michael


-- 
GPG key:  1024D/3144BE0F Michael Hanke
http://apsy.gse.uni-magdeburg.de/hanke
ICQ: 48230050


signature.asc
Description: Digital signature


Re: Lintian error about missing debconf dependency (which is not missing)

2005-12-22 Thread Michael Hanke
Hi!

On Wed, Dec 21, 2005 at 04:18:13PM -0800, Steve Langasek wrote:
> > The strange thing is, that I have the following line in the control file:
> 
> > Depends: ${misc:Depends}, iptables (>=1.2.11), gawk, debconf (>=1.3.22) | 
> > debconf-2.0
> 
> > There is clearly a versioned debconf dependency. The above line is
> > expanded to the following when building the package.
> 
> > Depends: debconf (>= 0.5) | debconf-2.0, iptables (>= 1.2.11), gawk, 
> > debconf (>= 1.3.22) | debconf-2.0
> 
> > Does anybody know where the problem is?
> 
> It's pretty likely that the lintian check is buggy in this case;
> nevertheless, your depends: line is *also* buggy.
> 
>   Depends: debconf (>= 0.5) | debconf-2.0, debconf (>= 1.3.22) | debconf-2.0
> 
> Reduces to
> 
>   Depends: debconf (>= 1.3.22) | debconf-2.0
> 
> *but*, this in turn reduces to 
> 
>   Depends: debconf-2.0
> 
> because there are versions of debconf older than 1.3.22 which provide
> debconf-2.0 (the Provides: was introduced in debconf 1.2.30), so they
> satisfy the second branch of the dependency relationship when they
> *shouldn't*.
> 
> If you depend on newer features than those guaranteed by the debconf-2.0
> interface, you will need to depend on the providers of those features
> explicitly, *without* an or on "debconf-2.0".
Thanks. I did'nt realize this fact. So if I get you right the solution
would be to get rid of the debconf-2.0 dependency. If I do so lintian is
fine, but I guess Joey Hess is not:

http://lists.debian.org/debian-devel/2005/08/msg00136.html
(and follow-ups)

This post was the reason why I included this dependency in the first
place.

As the debconf-2.0 package's purpose is to allow transition to cdebconf,
is depending on cdebconf explicitely as an alternative to debconf an
option? How compatible are those 'alternatives' currently. 

Cheers,

Michael


-- 
GPG key:  1024D/3144BE0F Michael Hanke
http://apsy.gse.uni-magdeburg.de/hanke
ICQ: 48230050


signature.asc
Description: Digital signature


Re: Lintian error about missing debconf dependency (which is not missing)

2005-12-23 Thread Michael Hanke
Hi!

On Fri, Dec 23, 2005 at 12:37:20PM +0100, Joost van Baal wrote:
> Op vr 23 dec 2005 om 02:31:16 -0800 schreef Steve Langasek:
> > 
> > I don't know what minimum version of cdebconf (if any) you should specify to
> > get support for settitle.
> 
> From the changelog:
> 
>  cdebconf  (0.43)
>   "Add new command SETTITLE"
Thanks.

I added cdebconf (>= 0.43) as an alternative to the debconf dependency.
Now, all should be fine -- lintian is.

Cheers,

Michael




-- 
GPG key:  1024D/3144BE0F Michael Hanke
http://apsy.gse.uni-magdeburg.de/hanke
ICQ: 48230050


signature.asc
Description: Digital signature


Automatically build packages for a multi dist/multi arch repository with pool structure?

2006-05-21 Thread Michael Hanke
Hi Mentors,

I provide several packages in my private apt-get'able package
repository. I (want to) support several dists (sarge, etch, sid, Ubuntu breezy, 
...)
and two architectures (i386, amd64).

To build the packages I use pbuilder on several machines. What I usually get 
are several binary packages with identical version numbers for each
dists/arch combination. This makes it impossible to have them in a
repository with a pool layout (like debpool would create). I would like to
move from my handcrafted repository to a debpool-managed one. 
Please comment on the following outline, and tell me whether this is a sane way
to reach this goal.

I think what I do is essentially backporting packages to a number of
dists. Therefore I'm writing a little script to facilitate the build process. I 
want 
to be able to build a package for all dists/arch combinations I have a
build environment for -- with a single command. 

I'm  posting this message to prevent myself from doing what others might
already have done.

As I use svn-buildpackage to manage my packages I start in my local
working copy of the package.

1. Export the package to a build area.
2. Extract version from debian/changelog (dpkg-parsechangelog)
3. If the target dist is not Debian unstable:
  Decrease Debian package version by one and add some backport
  suffix. Modify debian/changelog accordingly.
  Example: '(1.0.14-3) unstable;' could become '(1.0.14-2sarge0) stable;' 
  for a Debian stable backport. 
4. Build source package (dpkg-source -b ...) from the modified source
   tree.
5. Build the binary package(s) using pbuilder on some machine. Use
   '--debbuildopts "-B"' if the pool structure already contains binary
   packages of the current dist.
6. Finally debsign and dput/dupload to the repository

My to-be-completed script would cover step 1 to 5. 

My question is now: Is there already software in Debian that does this or 
something
similar and does versioning the backported packages work this way?


Thanks in advance,


Michael

-- 
GPG key:  1024D/3144BE0F Michael Hanke
http://apsy.gse.uni-magdeburg.de/hanke
ICQ: 48230050


signature.asc
Description: Digital signature


Re: using cow-shell to build a package

2006-07-29 Thread Michael Hanke
Hi,

On Fri, Jul 28, 2006 at 12:27:59PM +0200, Martin Man wrote:
> Hi Bastian,
> 
> Bastian Venthur napsal(a):
> > Hi all,
> > 
> > [snip/]
> > 
> > Is it possible to login to a clean environment with you package, make
> > changes and test until its ready and leave the environment later with no
> > changes made to the environment but the package-tree? Does cow-shell
> > provide this functionality. If yes, how?
> 
> I have no answer to your question, but I did exactly what you describe
> using pbuilder, you can even optimize the process and loop-mount some
> directory to the pbuilder so that you don't loose your changes after you
> tweak rules properly...
> 
> As I think about it, I did set it up in a way that post-build hook in
> pbuilder (or was it pre-build hook?) invoked interactive bash for me,
> and I could continue using modify debian/rules && dpkg-buildpckage right
> from the extracted & patched sources in a pbuilder provided chroot.
It would be nice if you could describe your setup in more detail (or
even provide the hook scripts somewhere). I tried a A00login hookscript
that invokes in interactive bash, but for some reason it exits
immediately when invoked by pbuilder:

 -> user script /var/cache/pbuilder/build//1695/tmp/hooks/A00login finished
 su: Authentication service cannot retrieve authentication info.
 (Ignored)

Thanks in advance,


Michael


-- 
GPG key:  1024D/3144BE0F Michael Hanke
http://apsy.gse.uni-magdeburg.de/hanke
ICQ: 48230050


signature.asc
Description: Digital signature


Re: using cow-shell to build a package

2006-07-31 Thread Michael Hanke
Hi,

On Mon, Jul 31, 2006 at 11:32:43AM +0200, Martin Man wrote:
> 
> 
> Michael Hanke wrote On 2006-07-29 18:08,:
> >Hi,
> >
> >[snip/]
> >
> >It would be nice if you could describe your setup in more detail (or
> >even provide the hook scripts somewhere). I tried a A00login hookscript
> >that invokes in interactive bash, but for some reason it exits
> >immediately when invoked by pbuilder:
> 
> I didn't do anything special than reading the pbuilder-doc and using 
> examples from /usr/share/doc/pbuilder
> 
> > -> user script /var/cache/pbuilder/build//1695/tmp/hooks/A00login finished
> > su: Authentication service cannot retrieve authentication info.
> > (Ignored)
> 
> I don't have access to debian/ubuntu system right now, but I think in 
> order to go interactive from a hook I did something like this in a hook 
> script
> 
> bash /dev/tty
   ^^^

This was the missing piece of information. Thanks!

> 
> I also didn't use the A hook, only the pre-build hook and 
> build-failed/build-success hook (sorry, don't remember the hook letters 
> anymore)
The A hooks are called after all dependencies are installed on the source
package is unpackaged, so this should be the prebuild hook.


Thanks,

Michael



-- 
GPG key:  1024D/3144BE0F Michael Hanke
http://apsy.gse.uni-magdeburg.de/hanke
ICQ: 48230050


signature.asc
Description: Digital signature


Re: using cow-shell to build a package

2006-08-11 Thread Michael Hanke
Hi,

On Fri, Aug 11, 2006 at 09:21:51PM +0900, Junichi Uekawa wrote:



> > > I also didn't use the A hook, only the pre-build hook and 
> > > build-failed/build-success hook (sorry, don't remember the hook letters 
> > > anymore)
> > The A hooks are called after all dependencies are installed on the source
> > package is unpackaged, so this should be the prebuild hook.
> > 
> 
> Note that hook example files are available in /usr/share/doc/pbuilder/examples
> which you could even point to it using 
> 
> cowbuilder --build --hookdir /usr/share/doc/pbuilder/examples XXX.dsc
> 
> to see the full extent of current available hooks.  If you had looked
> at C10shell hook, it would have been obvious...
True. Meanwhile I studied the provided examples ;-)

> 
> BTW, I like your idea of using A hooks to do it.
> I presume you're doing something like 
> 
>   pdebuild -- --hookdir  --bindmount $(pwd)/.. --pbuilder cowbuilder 
Almost. ;-)

I'm writing a remote frontend for pbuilder. It handles exporting source 
packages from svn-buildpackage repositories and/or applies 
distribution-specific patches to ease backporting. It also handles versions 
mangling for backports (with recently became much easier, thanks to ~).

Modified or unmodified source packages are then uploaded to a remote
build machine and pbuilder is invoked on that machine. Afterwards build
results are downloaded.

I wrote this, because I have a single machine in our lab that runs
pbuilder and has a number of basetgzs on it -- for all dists (sarge, etch,
breezy and dapper) and platforms (i386 and amd64) we have in our lab. 
I found no tool that could recompile a downloaded source
package for a certain distribution, so I tried to write my own.

Meanwhile it works pretty well. But quite often a simple recompile for backports
fails (mostly because of simple dependency issues). I'm currently adding a
--{pre|post}build-login option to my script that allows for interactive
logins on the buildmachine to handle such issues. The script generates
the necessary hook script by itself.

Cheers,

Michael

-- 
GPG key:  1024D/3144BE0F Michael Hanke
http://apsy.gse.uni-magdeburg.de/hanke
ICQ: 48230050


signature.asc
Description: Digital signature


Re: RFS: eqonomize -- personal accounting software for the small household economy

2006-09-23 Thread Michael Hanke
Hi,

On Sat, Sep 23, 2006 at 10:20:21AM +0200, Frank S. Thomas wrote:
> Hi,
> 
> I'm looking for a sponsor for the eqonomize package. The description is:
> 
>  Eqonomize! is a personal accounting software, with focus on efficiency
>  and ease of use for the small household economy. Eqonomize! provides a
>  complete solution, with bookkeeping by double entry and support for
>  scheduled recurring transactions, security investments, and budgeting.
>  It gives a clear overview of past and present transactions, and
>  development of incomes and expenses, with descriptive tables and
>  charts, as well as an approximation of future account values.
> 
> For more information see http://bugs.debian.org/386816 and 
> http://eqonomize.sourceforge.net
> 
> The package is avaiable at:
> http://frank.thomas-alfeld.de/download/debian/eqonomize/
> http://frank.thomas-alfeld.de/download/debian/eqonomize/eqonomize_0.4-1_i386.changes
I'd really like to see this in Debian. I used gnucash in the past for
this purpose, but it seems to be a bit overkill for this little bookkeeping. 

In the package description you could mention that this is a KDE app. I'd
look for this information when searching gnucash alternatives.



I tried building the package with pbuilder, but did not succeed:

/usr/bin/make -f admin/Makefile.common
make[1]: Entering directory `/tmp/buildd/eqonomize-0.4'
./admin/cvs.sh: line 33: --version: command not found
*** AUTOCONF NOT FOUND!.
*** KDE requires autoconf 2.53 or newer
make[1]: *** [cvs] Error 1
make[1]: Leaving directory `/tmp/buildd/eqonomize-0.4'
make: *** [post-patches] Error 2
pbuilder: Failed autobuilding of package


However, it was build in an etch chroot -- will try sid later.


Cheers,

Michael


-- 
GPG key:  1024D/3144BE0F Michael Hanke
http://apsy.gse.uni-magdeburg.de/hanke
ICQ: 48230050


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



RFS: arno-iptables-firewall

2006-10-27 Thread Michael Hanke
Hi,


I'd like to ask for a sponsored upload of the arno-iptables-firewall
package. My usual sponsor (Joost van Baal) is not available at the
moment, but as the freeze has not happend yet I'd like to bring this
version on its way into etch. This upload contains a new upstream release 
that fixes a number of minor bugs.

There are only trivial changes regarding the packaging.

The package is lintian clean and available from mentors:

http://mentors.debian.net/cgi-bin/maintainer-packages?action=details;package=arno-iptables-firewall

or (dget friendly)

http://mentors.debian.net/debian/pool/main/a/arno-iptables-firewall/arno-iptables-firewall_1.8.8.b-1.dsc


Thanks in advance,

Michael



-- 
GPG key:  1024D/3144BE0F Michael Hanke
http://apsy.gse.uni-magdeburg.de/hanke
ICQ: 48230050


signature.asc
Description: Digital signature


Re: RFR: eegdev

2012-01-19 Thread Michael Hanke
Hi,

On Fri, Jan 20, 2012 at 12:33:44AM +0100, Nicolas Bourdaud wrote:
> I am looking for reviews for my package "eegdev".

If nobody is quicker than me I will have a look at this package tonight.

Cheers,

Michael

-- 
Michael Hanke
http://mih.voxindeserto.de


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120120054102.GB9230@meiner



Re: RFR: eegdev

2012-01-20 Thread Michael Hanke
Hi,

On Fri, Jan 20, 2012 at 12:33:44AM +0100, Nicolas Bourdaud wrote:
> I would be glad if someone review this package.

The packaging looks pretty good. There are a few things that you could
take a look at.

The comments at the top of debian/rules should go away -- it is no
longer a sample rules file.

When I build the package on my i386 laptop (up-to-date wheezy) the build
hangs in one of the tests until I kill it (reproduced every time):

make[4]: Entering directory `/home/michael/debian/cnbi/eegdev/tests'
PASS: verify-cast.sh
PASS: verifysplit
PASS: syseegfile
Testing biosemi with float data type
Testing biosemi with double data type
PASS: testfakeact2.sh
error caught (97) Address family not supported by protocol
^C

When I build the package with 'nocheck' it builds.

I noticed the eegdev-plugins-free binary package name and that the
build uses this configuration

Core library build : yes
--
EEG file support : yes
Biosemi support  : yes
gTec support : no
Neurosky support : no
TobiIA support   : yes

Do the two missing plugins depend on something that is not in Debian? Or
that is non-free? It looks like (at least some of) the code for these
plugins is shipped with the package. I didn't see any copyright notice
that would indicate 3rd-party code. It might make sense to put some
information about the "missing" plugins into README.Debian or
README.source, depending on why they are missing and whether there are
plans to add them later on.

I have updated the information on this package in the Debian Science
taskfiles.

Cheers,

Michael




-- 
Michael Hanke
http://mih.voxindeserto.de


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20120120122027.GA29830@meiner



Re: multiple pbuilders (sid and hardy)

2009-04-30 Thread Michael Hanke
On Thu, Apr 30, 2009 at 10:58:31AM +0200, Grammostola Rosea wrote:
> Hi,
>
> Is it possible to have multiple pbuilders for Sid and Hardy (ubuntu) on  
> Debian?

Yes. An easy way is to install Ubuntu's 'debootstrap' package instead
of Debian's. If that is available you can simply specify Ubuntu releases
in pbuilder's 'create' mode.

Michael

-- 
GPG key:  1024D/3144BE0F Michael Hanke
http://apsy.gse.uni-magdeburg.de/hanke
ICQ: 48230050


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



Re: multiple pbuilders (sid and hardy)

2009-04-30 Thread Michael Hanke
On Thu, Apr 30, 2009 at 11:30:46AM +0200, Mike Hommey wrote:
> On Thu, Apr 30, 2009 at 11:14:59AM +0200, Michael Hanke 
>  wrote:
> > On Thu, Apr 30, 2009 at 10:58:31AM +0200, Grammostola Rosea wrote:
> > > Hi,
> > >
> > > Is it possible to have multiple pbuilders for Sid and Hardy (ubuntu) on  
> > > Debian?
> > 
> > Yes. An easy way is to install Ubuntu's 'debootstrap' package instead
> > of Debian's. If that is available you can simply specify Ubuntu releases
> > in pbuilder's 'create' mode.
> 
> No need for Ubuntu's deboostrap:
> http://packages.debian.org/sid/all/debootstrap/filelist
> --> /usr/share/debootstrap/scripts/hoary

Cool! Thanks for the pointer.

Michael


-- 
GPG key:  1024D/3144BE0F Michael Hanke
http://apsy.gse.uni-magdeburg.de/hanke
ICQ: 48230050


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



insserv: warning: current stop runlevel(s) ... overwrites defaults

2009-11-11 Thread Michael Hanke
Hi,

I recently switch to dependency-based boot order. While updating one of my
packages I noticed an inconsistency of init script LSB header and
update-rc.d call.

I have trouble figuring out what would be the appropriate fix. The
LSB header looks like this:

### BEGIN INIT INFO
# Provides:  arno-iptables-firewall
# Required-Start:$syslog $local_fs $network
# Required-Stop: $syslog $local_fs $network
# Default-Start: S 2 3 4 5
# Default-Stop:  0 1 6
# Short-Description: Setup iptables firewall configuration
### END INIT INFO


I am trying to find the matching update-rc.d call, but no luck so far:

: update-rc.d arno-iptables-firewall start 41 2 3 4 5 S . stop 34 0 1 6 .
update-rc.d: using dependency based boot sequencing
insserv: warning: current start runlevel(s) (S) of script 
`arno-iptables-firewall' overwrites defaults (2 3 4 5 S).
insserv: warning: current stop runlevel(s) (empty) of script 
`arno-iptables-firewall' overwrites defaults (0 1 6).


The above call should match precisely what I want -- it looks like the
arguments of the call are not considered as a whole. Going with the
defaults also doesn't help:


: update-rc.d arno-iptables-firewall defaults 41 34
update-rc.d: using dependency based boot sequencing
update-rc.d: warning: arno-iptables-firewall start runlevel arguments (2
3 4 5) do not match LSB Default-Start values (S 2 3 4 5)
insserv: warning: current start runlevel(s) (S) of script
`arno-iptables-firewall' overwrites defaults (2 3 4 5 S).
insserv: warning: current stop runlevel(s) (empty) of script
`arno-iptables-firewall' overwrites defaults (0 1 6).


Can anyone please point me to the problem and its solution?


Thanks,

Michael

-- 
GPG key:  1024D/3144BE0F Michael Hanke
http://mih.voxindeserto.de


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



Re: insserv: warning: current stop runlevel(s) ... overwrites defaults

2009-11-11 Thread Michael Hanke
On Wed, Nov 11, 2009 at 04:44:13PM +0200, Peter Pentchev wrote:
> On Wed, Nov 11, 2009 at 03:35:40PM +0100, Didier 'OdyX' Raboud wrote:
> > Michael Hanke wrote:
> > 
> > > Hi,
> > > 
> > > Can anyone please point me to the problem and its solution?
> > 
> > Hi Michael,
> > 
> > without pre-judging your problem and its solutions, this is the wrong list 
> > for this type of problems.
> > 
> > debian-mentors mailing list
> > Helping newbie developers
> > Newbie Debian developers can seek help with packaging and other 
> > developer-
> > related issues here. 
> > This list is not meant for users' questions, but for new maintainers'!
> > 
> > Please re-post your question to debian-u...@lists.debian.org
> 
> Well, that would have been fine, except that Michael Hanke is actually
> the maintainer of the arno-iptables-firewall package, and he may be
> asking this question from a "what can I do to make my package work"
> point of view :)

That is correct -- maybe I should have mentioned that. I won't to
actually prevent people having to post to -users, because they are
concerned by that warning message.


Thanks in advance,

Michael


-- 
GPG key:  1024D/3144BE0F Michael Hanke
http://mih.voxindeserto.de


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



Re: insserv: warning: current stop runlevel(s) ... overwrites defaults

2009-11-12 Thread Michael Hanke
On Thu, Nov 12, 2009 at 09:03:59AM -0600, Raphael Geissert wrote:
> Michael Hanke wrote:
> [...]
> > 
> > Can anyone please point me to the problem and its solution?
> > 
> 
> When making changes to the runlevels either via update-rc.d or the lsb
> header, the init script needs to be removed first (via update-rc.d, as
> simply removing the symlink won't work in the case of file-rc).

Ah! Thanks a lot, that explains it.

> In other words: you need to check if the user is upgrading from an affected
> version (probably anything lt the new version) and then do an update-rc.d
> remove. All that before the #DEBHELPER# mark so that the rest is done for
> you.
> 
> And like Rogéiro Brito said, remove the S runlevel. First of all, S is only
> used by some special cases where the script only needs to be run once,
> second, syslog daemons are only available from post-rcS (which at some
> point would render your package uninstallable because of unmet init script
> dependencies).

Well, the respective package is a firewall. I'd say it should run
once in S pretty much right after networking becomes available.
It may even not be necessary to run it again when switching to a runlevel
other then 0 1 6, correct?

So instead of removing S I should remove 2 3 4 5, I guess.

Additionally, as you mentioned syslog is not available at that early
stage.  The question is now whether I should sacrifice the startup
log-message for the sake of establishing the firewall as early as
possible -- or not?

Oppinions very much appreciated!


Michael


-- 
GPG key:  1024D/3144BE0F Michael Hanke
http://mih.voxindeserto.de


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



Re: Status of SIGAR (Was: InVesalius packaging)

2010-03-29 Thread Michael Hanke
Hey,

On Mon, Mar 29, 2010 at 03:46:20PM -0300, Thiago Franco Moraes wrote:
> On Mon, Mar 29, 2010 at 10:40 AM, Andreas Tille wrote:
> W: libsigar: package-installs-python-pyc
> usr/lib/python2.6/dist-packages/sigar.pyc
> N:
> N:Compiled python source files should not be included in the package.
> N:These files should be removed from the package and created at package
> N:installation time in the postinst.
> N:
> N:Severity: normal, Certainty: certain
> 
> How can I only compile in installation time? I'm using this command in rule
> file to install the files:
> 
> cd $(CURDIR)/bindings/python && python setup.py install --install-layout=deb
> --root=$(CURDIR)/debian/$(PACKAGE)

I wasn't following this effort before -- forgive me if that had been
talked about before.

Looks like the Python-bindings (and others too) should go into separate
binary packages and be handled by proper tools. pysupport should take
care of all Python-related issue (including the one above).

Is there any reason for this verbose rules file. Both debhelper7 and
cdbs should help a lot with the common cases of packaging (like this
one) and also provide convenient helpers for python packages.

I might be able to help with the general and python-related aspects of
this packaging, but wanted to ask first if there is need to stay close
to the current state?

Right now the packaging looks quite raw -- lots of unused/unedited
files. The rules file only seems to build the python-bindings and none
of the rest -- including the main library -- is that intended?

Given these facts the binary package should be named 'python-sigar'.

Is there a repository for this packaging somewhere? You chose to take an
SVN snapshot (upstream also offers the code in git). Did you just
download that snapshot or have the code in a repository together with
the packaging?

Michael


-- 
GPG key:  1024D/3144BE0F Michael Hanke
http://mih.voxindeserto.de


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100329192755.ga22...@meiner



Re: RFS: gpick

2010-12-04 Thread Michael Hanke
On Sat, Dec 04, 2010 at 10:14:22AM -0500, Kevin Coyner wrote:
> I downloaded your files from mentors and tried to build it without
> touching anything and got the following:



> dpkg-buildpackage: warning: Build dependencies/conflicts unsatisfied; 
> aborting.

I think it is relatively clear that your system lacks the specified
build-dependencies, and hence the packages is not even expected to be
buildable. To perform any compilation tests the respective environment
needs to have all build-deps available.

Michael


-- 
Michael Hanke
http://mih.voxindeserto.deGPG key: 4096R/7FFB9E9B


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20101204155344.ga6...@meiner



Re: Build-Dep: libqtwebkit-dev

2011-03-16 Thread Michael Hanke
On Wed, Mar 16, 2011 at 01:32:31PM -0700, Ludovico Cavedon wrote:
> On Wed, Mar 16, 2011 at 11:40 AM, Sune Vuorela  wrote:
> 
> > > I need to specify something like: B-D on libqtwebkit-dev only if
> > > libQt4-dev does not provide libqtwebkit-dev
> >
> > libqtwebkit-dev | libqt4-dev (<< 4.7) ?
> >
> 
> I agree this is the right thing, but...
> unfortunately buildd only uses the first dependecy and ignores the "|", so
> that lines does not actually work for building with buildd if you have libqt
> 4.6... [1]

Which is probably a good thing as any new build should depend on
libqtwebkit4 instead of the libqt4-webkit, I guess.

Michael

-- 
Michael Hanke
http://mih.voxindeserto.de


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110316204710.GA6736@meiner



Re: FAIL: Package purging left files on system:

2011-03-17 Thread Michael Hanke
On Thu, Mar 17, 2011 at 06:28:32PM +0200, Peter Pentchev wrote:
> On Thu, Mar 17, 2011 at 05:21:55PM +0100, Mathieu Malaterre wrote:
> > Dear mentors,
> > 
> >   I am trying to fix the following errors on the dcmtk package:
> > 
> > 0m18.3s ERROR: FAIL: Package purging left files on system:
> >   /var/lib/dcmtk not owned
> >   /var/lib/dcmtk/db  not owned
> > 
> > /var/lib/dcmtk/db is a special directory. This is the location where
> > incoming DICOM files are stored on disk. So this directory should IMHO
> > only be removed when the user really understand what it does. when and
> > how should I remove this directory ?
> 
> Add a postrm script that checks if the user is really purging your
> package (check if [ "$1" = 'purge' ]) and, if so, remove the directory,
> assuming that the user who specifically issued a purge request really
> understands what she's doing to the package and all of its data files :)

And since it might be precious data, you could also check whether the
directory is empty and not remove it in this case, but issue a warning
saying why it was left on the system.

Michael



-- 
Michael Hanke
http://mih.voxindeserto.de


-- 
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20110317174026.GC22586@meiner