Bug#939963: Problems compiling orpie with ocaml 4.08
Adding the dependency on libnum was easy, but orpie doesn't compile with ocaml 4.08 anymore. I need to talk to upstream ... signature.asc Description: PGP signature
Bug#1071643: horizon-eda: Missing build dependency on cppzmq-dev
Thanks Adrian! Quite strange. It does have a build depend on cppzmq-dev and compiling it in my local pbuilder environment just works. I just did another compile run after removing libzmq5 without an error. Though, if I remember propperly the first compilation after setting up pbuilder shew the same error, but only once. So I restarted from ground in pbuilder and 1. copied horizon-eda_2.6.0-3.debian.tar.xz, horizon-eda_2.6.0-3.dsc and horizon-eda_2.6.0.orig.tar.xz into /tmp 2. Run pbuilder sudo pbuilder --login --bindmounts /tmp 3. Unpacked the source and went into horizon-eda-2.6.0 dpkg-source -x horizon-eda_2.6.0-3.dsc cd horizon-eda-2.6.0 4. Install all build dependencies and devscripts apt-get build-dep . apt-get install devscripts 5. Run debuild Well, no problem so far, so I will try to upload a new version unless you see something obvious that is missing. Uwe Am Thu, May 23, 2024 at 12:45:06AM +0300 schrieb Adrian Bunk: > Source: horizon-eda > Version: 2.6.0-2 > Severity: serious > Tags: ftbfs > > https://buildd.debian.org/status/logs.php?pkg=horizon-eda&ver=2.6.0-2 > > ... > Has header "zmq.hpp" : NO > > ../meson.build:46:8: ERROR: Problem encountered: cppzmq not found > > > > I haven't checked whether this is the only missing build dependency. > > BTW: > The build dependency on libzmq5 looks wrong and is already covered > by the build dependency on libzmq3-dev, please remove libzmq5 since > this will break with the next soname change of libzmq. -- MMK GmbH, Fleyer Str. 196, 58097 Hagen uwe.steinm...@mmk-hagen.de Tel: 02331 840446Fax: 02331 843920 signature.asc Description: PGP signature
Bug#350088: gringotts: Segm fault when loading file
On Mon, Jan 30, 2006 at 11:41:24PM +0100, Bastian Kleineidam wrote: > severity 350088 grave > reassign 350088 libmhash2 0.9.4a-1 > retitle 350088 libmhash2: crc32 segfaults on big endian machines > tags 350088 + patch > thanks > > Hi, > > this is a bug in the new libmhash2 version 0.9.4a. The severity is grave > since it breaks existing software using the library (in this case > gringotts). > Uwe, if you want you can recompile libmhash2 with the attached patch and > see if it works. I cannot test this since the bug only occurs on big > endian machines like your powerpc. The patch alone doesn't seem to be enough. After applying the patch it crashes in _mhash_gen_key_s2k_simple() when calling mutils_malloc(total). _mhash_gen_key_s2k_simple() has the following code total = times * block_size; times = key_size / block_size; I suppose those two lines have to be swapped. The block_size has a very reasonable value of 20 on my system. Uwe -- MMK GmbH, Fleyer Str. 196, 58097 Hagen [EMAIL PROTECTED] Tel: +2331 840446Fax: +2331 843920 signature.asc Description: Digital signature
Bug#350088: CRC32 faulting on big endian systems
On Sat, Mar 18, 2006 at 11:30:20AM +0100, Marc Haber wrote: > On Fri, Mar 17, 2006 at 02:24:15PM -0800, Jonathan Day wrote: > > Can users of big-endian machines please verify this > > with mhash 0.9.6, which has been released with > > big-endian bugfixes applied. The problem may now be > > fixed, but I want to be certain of that. > > deb-src http://zg.debian.zugschlus.de/zg/pool/main/mhash/ / > > has a ready-to-build source package of 0.9.6, but only i386 binaries > at the moment. Please try with these. Did it and ran gringotts. Program received signal SIGSEGV, Segmentation fault. 0x0f186ae8 in mutils_memcpy () from /usr/lib/libmhash.so.2 (gdb) bt #0 0x0f186ae8 in mutils_memcpy () from /usr/lib/libmhash.so.2 #1 0x0f188038 in _mhash_gen_key_s2k_simple () from /usr/lib/libmhash.so.2 #2 0x0f187da4 in mhash_keygen () from /usr/lib/libmhash.so.2 #3 0x0f5793f0 in grg_key_gen () from /usr/lib/libgringotts.so.2 ... Still broken. Uwe -- MMK GmbH, Fleyer Str. 196, 58097 Hagen [EMAIL PROTECTED] Tel: +2331 840446Fax: +2331 843920 signature.asc Description: Digital signature
Bug#294014: acknowledged by developer (Bug#294014: fixed in php4-ps 1.3.1-2)
On Wed, Feb 09, 2005 at 08:07:54AM +1000, Adam Conrad wrote:
> reopen 294014
> thanks
>
> Debian Bug Tracking System said:
> > This is an automatic notification regarding your Bug report
> > #294014: php4-ps: phpapi revision requires a new upload in sid,
> > which was filed against the php4-ps package.
> >
> > * fixed dependencies, 2nd trial (Closes: #294014)
>
> Guess what?... Still no go. Looking at the bug log, it's probably my
> fault for the typo, mind you, that you blindly cut-and-pasted. :)
>
> I typed "$(php:Depends)", when I meant "{php:Depends}".
I stumbled over the () but expected it be some kind of special syntax
I simply haven't seen before.
> As a pointer, when I'm making changes that I know will affect auto-filled
> control fields, I tend to 'cat debian/package/DEBIAN/control' after the
> build and make sure everything looks the way I expect it to.
Doesn't seem to be day yesterday.
Thanks for your patience.
Uwe
--
MMK GmbH, Universitaetsstr. 11, 58097 Hagen
[EMAIL PROTECTED]
Tel: +2331 840446Fax: +2331 843920
signature.asc
Description: Digital signature
Bug#310286: releaseforge: I can confirm #310286
Package: releaseforge Version: 0.7.1-2 Followup-For: Bug #310286 Same problem as in #310286. Uwe -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (990, 'unstable'), (500, 'testing') Architecture: powerpc (ppc) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.11-rc4 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages releaseforge depends on: ii python2.3.5-2An interactive high-level object-o ii python-qt33.14.1-2 Qt3 bindings for Python (default v ii python2.4 2.4.1-2An interactive high-level object-o -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#294155: php4-pgsql: Cannot be build with additional php installed in /usr/local
Package: php4-pgsql Version: 3:4.3.10-1 Severity: serious Justification: no longer builds from source I have a selfcompiled php5 in /usr/local. Compiling php4-pgsql from source will use the header files from there. Configuring the module in debian/rules should use the option --with-php-config=/usr/bin/php-config Uwe -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (990, 'unstable') Architecture: powerpc (ppc) Kernel: Linux 2.6.6 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) (ignored: LC_ALL set to [EMAIL PROTECTED]) Versions of packages php4-pgsql depends on: ii debconf [debconf-2.0] 1.4.45 Debian configuration management sy ii libapache-mod-php4 [phpapi- 4:4.3.10-3 server-side, HTML-embedded scripti ii libc6 2.3.2.ds1-20 GNU C Library: Shared libraries an ii libpq3 7.4.7-1 PostgreSQL C client library ii php4-cgi [phpapi-20020918-z 4:4.3.10-3 server-side, HTML-embedded scripti ii php4-cli [phpapi-20020918-z 4:4.3.10-3 command-line interpreter for the p -- debconf information: php4/extension_pgsql_cgi: true php4/extension_pgsql_cli: true php4/add_extension: true php4/remove_extension: true php4/extension_pgsql_apache: true -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#418318: Processed: reassign
On Wed, Feb 06, 2008 at 07:57:03PM +0100, Luk Claes wrote: > Debian Bug Tracking System wrote: > > Processing commands for [EMAIL PROTECTED]: > > > >> reassign 418318 ftp.debian.org > > Bug#418318: Don't build a php4-specific package because of php4's removal > > Bug reassigned from package `php4-ps' to `ftp.debian.org'. > > Shouldn't you just remove the php4-ps binary package in your next upload > fixing this bug? That's what I thought as well but Wiesiek Swiatek told me: You should reassign this bug to ftp.debian.org metapackage with ask to removal this package from unstable. Upload new package as "php-ps" is not enougn, becouse source (php4-ps) still is aviable in unstable. Uwe -- MMK GmbH, Fleyer Str. 196, 58097 Hagen [EMAIL PROTECTED] Tel: 02331 840446Fax: 02331 843920 signature.asc Description: Digital signature
Bug#418318: Processed: reassign
On Thu, Feb 07, 2008 at 07:02:16PM +0100, Luk Claes wrote: > Uwe Steinmann wrote: > > On Wed, Feb 06, 2008 at 07:57:03PM +0100, Luk Claes wrote: > >> Debian Bug Tracking System wrote: > >>> Processing commands for [EMAIL PROTECTED]: > >>> > >>>> reassign 418318 ftp.debian.org > >>> Bug#418318: Don't build a php4-specific package because of php4's removal > >>> Bug reassigned from package `php4-ps' to `ftp.debian.org'. > >> Shouldn't you just remove the php4-ps binary package in your next upload > >> fixing this bug? > > That's what I thought as well but Wiesiek Swiatek told me: > > > > > > You should reassign this bug to ftp.debian.org metapackage with ask to > > removal this package from unstable. > > Upload new package as "php-ps" is not enougn, becouse source (php4-ps) > > still is aviable in unstable. > > > > If you really want to change the source package name, then you indeed > have to ask for removal of this package. Though I would advise to upload > the new source package first if that's the case and read [1] to have a > decent bug title for package removals. This is still very confusing for me. Reading [1] I get the impression that everything is done automatically. The source package php4-ps used to produce two binary packages php4-ps and php5-ps. Now that php4 isn't supported anymore, only php5-ps will be left, which is somewhat strange. A source package php4-ps produces a binary package php5-ps. That's why I created a new source package php-ps which produces php5-ps. Isn't this one of the cases where rene takes care of automatic removal? 'Source packages which have had all their binary packages taken over by another source packages' Uwe -- MMK GmbH, Fleyer Str. 196, 58097 Hagen [EMAIL PROTECTED] Tel: 02331 840446Fax: 02331 843920 signature.asc Description: Digital signature
Bug#418318: Processed: reassign
On Thu, Feb 07, 2008 at 10:36:07PM +0100, Luk Claes wrote: > Uwe Steinmann wrote: > > On Thu, Feb 07, 2008 at 07:02:16PM +0100, Luk Claes wrote: > >> Uwe Steinmann wrote: > >>> On Wed, Feb 06, 2008 at 07:57:03PM +0100, Luk Claes wrote: > >>>> Debian Bug Tracking System wrote: > >>>>> Processing commands for [EMAIL PROTECTED]: > >>>>> > >>>>>> reassign 418318 ftp.debian.org > >>>>> Bug#418318: Don't build a php4-specific package because of php4's > >>>>> removal > >>>>> Bug reassigned from package `php4-ps' to `ftp.debian.org'. > >>>> Shouldn't you just remove the php4-ps binary package in your next upload > >>>> fixing this bug? > >>> That's what I thought as well but Wiesiek Swiatek told me: > >>> > >>> > >>> You should reassign this bug to ftp.debian.org metapackage with ask to > >>> removal this package from unstable. > >>> Upload new package as "php-ps" is not enougn, becouse source (php4-ps) > >>> still is aviable in unstable. > >>> > >> If you really want to change the source package name, then you indeed > >> have to ask for removal of this package. Though I would advise to upload > >> the new source package first if that's the case and read [1] to have a > >> decent bug title for package removals. > > This is still very confusing for me. Reading [1] I get the impression > > that everything is done automatically. > > The source package php4-ps used to produce two binary packages php4-ps and > > php5-ps. Now that php4 isn't supported anymore, only php5-ps will > > be left, which is somewhat strange. A source package php4-ps produces > > a binary package php5-ps. That's why I created a new source package > > php-ps which produces php5-ps. > > Isn't this one of the cases where rene takes care of automatic removal? > > > > 'Source packages which have had all their binary packages taken over by > > another source packages' > > Will you have a php4-ps binary package in php-ps or only a php5-ps? If > the latter, this bug is what you should do except for the bug title. I > also would advise you to wait till php-ps is at least in unstable before > retitling this bug correctly. php-ps will only have a binary package php5-ps. Uwe -- MMK GmbH, Fleyer Str. 196, 58097 Hagen [EMAIL PROTECTED] Tel: 02331 840446Fax: 02331 843920 signature.asc Description: Digital signature
Bug#465055: php-ps: FTBFS: libgd2-dev not available anymore.
On Sun, Feb 10, 2008 at 01:32:40PM +0100, Kurt Roeckx wrote: > Package: php-ps > Version: 1.3.6-2 > Severity: serious > > Hi, > > You have a build dependency on: > libgd2-dev (>> 2.0.0) | libgd2-xpm-dev (>> 2.0.0) | libgd2-noxpm-dev (>> > 2.0.0) > > The buildd's will only consider the first of those, and then fail. > You'll want to remove that part. Is this specific for the buildds or the above dependency line in general the wrong approach? Uwe -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#433456: dh-make-php: phppkginfo does not open package.xml properly
On Tue, Jul 17, 2007 at 01:49:09PM +0200, Rafal Krypa wrote: > Package: dh-make-php > Version: 0.2.3 > Severity: grave > Justification: renders package unusable > > I'm sorry for reporting bug in yet unreleased package version, but the > 0.2.2 version is almost unusable because of bug #432880 and I tried the > svn version as Uwe Steinmann suggested. > New dh-make-php dropped xmlstarlet dependency and now uses its own > script to retrieve package information. Usage information printed by > /usr/share/dh-make-php/phppkginfo says: > > - > Usage: /usr//share/dh-make-php/phppkginfo dir > dir - Directory containing package.xml file > > commands: > version - Return version of package > maintainers - Return comma separated list of maintainers > - > > But phppkginfo expects its first argument to full path to package.xml > file, not the directory that contains it. > Because in /usr/share/dh-make-php/dh-make-php.lib the script is also > called with directory argument, dh-make-php does not work. I can only partly reproduce this. phppkginfo calls PEAR_PackageFile::fromAnyFile() which is quite smart and checks for package.xml and package2.xml in the given directory. It also checks, whether the package file is passed directly and it searches it in a .tgz file. That should be sufficient and phppkginfo should be working as intended. It could be that in your case, that /usr/bin/php still points towards /usr/bin/php4. So, please check if /usr/bin/php5 -f phppkginfo works. Uwe -- MMK GmbH, Fleyer Str. 196, 58097 Hagen [EMAIL PROTECTED] Tel: 02331 840446Fax: 02331 843920 signature.asc Description: Digital signature
Bug#433456: I'm experiencing this problem as well
On Thu, Aug 02, 2007 at 10:56:32PM -0400, Charles Fry wrote: > Since we know that the file we are looking for is package.xml, is there any > reason not to specify that explicitely, instead of using . which isn't > working for some of us? I have seen extension which call it package2.xml. Uwe > > Charles > > On 7/21/07, Charles Fry <[EMAIL PROTECTED]> wrote: > > > > % /usr/bin/php5 -f /usr/share/dh-make-php/phppkginfo . package > > % /usr/bin/php5 -f /usr/share/dh-make-php/phppkginfo package.xml package > > Pager% > > > > I don't know what the extra character is at the end, either. > > > > In any case, I am running a stable installation, which may have something > > to do with it? If so, then dh-make-php's dependencies may be incorrect. > > > > Charles > > -- MMK GmbH, Fleyer Str. 196, 58097 Hagen [EMAIL PROTECTED] Tel: 02331 840446Fax: 02331 843920 signature.asc Description: Digital signature
Bug#453222: orpie: FTBFS: `Depends' field, syntax error after reference to package `ocaml-nox'
On Tue, Nov 27, 2007 at 09:35:25PM +0100, Lucas Nussbaum wrote: > Package: orpie > version: 1.5.1-2 Ups, I have just uploaded 1.5.1-3 which doesn't have this error, because I fixed it right before upload. Why is the buildd still trying to build 1.5.1-2 instead of 1.5.1-3? Uwe > Severity: serious > User: [EMAIL PROTECTED] > Usertags: qa-ftbfs-20071126 qa-ftbfs > Justification: FTBFS on i386 > > Hi, > > During a rebuild of all packages in sid, your package failed to build on i386. > > Relevant part: > > > dh_installcron > > dh_installman > > dh_installinfo > > dh_installchangelogs > > dh_link > > dh_strip > > dh_compress > > dh_fixperms > > dh_installdeb > > dh_shlibdeps > > dpkg-shlibdeps: warning: debian/orpie/usr/bin/orpie shouldn't be linked > with libgslcblas.so.0 (it uses none of its symbols). > > dpkg-shlibdeps: warning: debian/orpie/usr/bin/orpie-curses-keys shouldn't > be linked with libgsl.so.0 (it uses none of its symbols). > > dpkg-shlibdeps: warning: debian/orpie/usr/bin/orpie-curses-keys shouldn't > be linked with libgslcblas.so.0 (it uses none of its symbols). > > dh_gencontrol > > dh_md5sums > > dh_builddeb > > dpkg-deb: parse error, in file `debian/orpie/DEBIAN/control' near line 6 > package `orpie': > > `Depends' field, syntax error after reference to package `ocaml-nox' > > dh_builddeb: command returned error code 512 > > make: *** [binary-arch] Error 1 > > dpkg-buildpackage: failure: /usr/bin/fakeroot debian/rules binary gave > error exit status 2 > > The full build log is available from: > http://people.debian.org/~lucas/logs/2007/11/26 > > 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 containing a sid i386 > environment. Internet was not accessible from the build systems. > > -- > | Lucas Nussbaum > | [EMAIL PROTECTED] http://www.lucas-nussbaum.net/ | > | jabber: [EMAIL PROTECTED] GPG: 1024D/023B3F4F | > -- MMK GmbH, Fleyer Str. 196, 58097 Hagen [EMAIL PROTECTED] Tel: 02331 840446Fax: 02331 843920 signature.asc Description: Digital signature
Bug#335994: Isn't the license issue fixed already?
Hi, I wonder if the license issue is fixed in the mean time. Image/Color is licensed with PHP 3.01 according to pear.php.net. Wouldn't that be ok for debian? Uwe -- MMK GmbH, Fleyer Str. 196, 58097 Hagen [EMAIL PROTECTED] Tel: 02331 840446Fax: 02331 843920 signature.asc Description: Digital signature
Bug#441680: orpie: FTBFS: mlgsl_error.c:46: error: void value not ignored as it ought to be
Upstream has commented on it. The next version version will fix it, but it's not clear now, when that version will be released. Uwe -- MMK GmbH, Fleyer Str. 196, 58097 Hagen [EMAIL PROTECTED] Tel: 02331 840446Fax: 02331 843920 signature.asc Description: Digital signature
Bug#494221: netmrg: diff for NMU version 0.20-2.1
On Fri, Oct 03, 2008 at 11:09:54PM +0200, Thomas Viehmann wrote: > tags 494221 + patch pending > thanks > > Hi Uwe, > > here is my netmrg NMU (version 0.20-2.1), bumping the > build-dependency to the fixed rrdtool. Thanks. Uwe -- MMK GmbH, Fleyer Str. 196, 58097 Hagen [EMAIL PROTECTED] Tel: 02331 840446Fax: 02331 843920 signature.asc Description: Digital signature
Bug#416454: depends on unavailable phpapi-20051025
On Tue, Mar 27, 2007 at 10:37:27PM -0400, Filipus Klutiero wrote: > Package: php5-ps > Version: 1.3.4-2 > Severity: grave > > This package should apparently declare a dependency on phpapi-20051025. > However, it does not and phpapi-20051025 is no more available in Etch, > so we missed that it was unusable. I get a > "PHP Warning: PHP Startup: Unable to load dynamic library > '/usr/lib/php5/20060613+lfs/ps.so' - /usr/lib/php5/20060613+lfs/ps > .so: cannot open shared object file: No such file or directory in > Unknown on line 0" > when starting PHP with ps enabled. This should have been fixed in 1.3.4-3, but unfortunetly the new version has another problem as described in #416416. Uwe -- MMK GmbH, Fleyer Str. 196, 58097 Hagen [EMAIL PROTECTED] Tel: 02331 840446Fax: 02331 843920 signature.asc Description: Digital signature
Bug#416416: php5-ps: fails to initialize
On Tue, Mar 27, 2007 at 09:20:35PM +0100, Jorge Tiago Vila wrote: > Package: php5-ps > Version: 1.3.4-3 > Severity: grave > Justification: renders package unusable > > PHP5 PS module fails to initialize under PHP5 (5.2.0-10). > > Apache2 error log: > > [Tue Mar 27 21:08:01 2007] [notice] Digest: generating secret for digest > authentication ... > [Tue Mar 27 21:08:01 2007] [notice] Digest: done > PHP Warning: PHP Startup: SH\x8d\x15\xf5\x01: Unable to initialize > module\nModule compiled with module API=20020429, debug=0, > thread-safety=0\nPHPcompiled with > module API=20 > 060613, debug=0, thread-safety=0\nThese options need to match\n in Unknown on > line 0 > [Tue Mar 27 21:08:01 2007] [notice] Apache/2.2.3 (Debian) PHP/5.2.0-10 > mod_ssl/2.2.3 OpenSSL/0.9.8e configured -- resuming normal operations > > Although it does not state the package name anywhere in the log file, > removing it makes the PHP warning disapear and reinstalling it brings back > the warning. > > It seems the package needs to be recompiled for the new PHP API. Much worse and a fairly stupid error on my side. The php4 module has been installed in the php5 extension dir. Will be fixed in version 1.3.4-4 Uwe -- MMK GmbH, Fleyer Str. 196, 58097 Hagen [EMAIL PROTECTED] Tel: 02331 840446Fax: 02331 843920 signature.asc Description: Digital signature
Bug#416454: Fixed
On Wed, Mar 28, 2007 at 12:44:39AM -0700, Steve Langasek wrote:
> reopen 416454
> thanks
>
> On Wed, Mar 28, 2007 at 02:30:23AM -0400, Filipus Klutiero wrote:
> > Version: 1.3.4-3
>
> > This was fixed by Uwe Steinmann.
>
> No, it wasn't. The current php5-ps package is still missing a dependency on
> the matching phpapi virtual package; so the new version of the package still
> permits installing the package in an unusable configuration. It's almost
> certain that lenny will ship with a different php5 ABI than etch includes,
> but php5-ps's dependency doesn't prevent the package from being broken by
> future partial upgrades; and the php4-ps package from the same source
> package has the same problem, meaning its dependencies are already
> insufficient to prevent installation with existing, incompatible php4
> packages from sarge. That's a serious bug (incorrect dependencies).
>
> Uwe, please fix this package to use the ABI version information available
> from php-config4 --phpapi and php-config5 --phpapi in the Debian php*-dev
> packages. For an example of an out-of-tree extension that implements this,
> feel free to reference php-imlib.
I just missed a ${php:Depends} in the Depends line. Should be fixed
in 1.3.4-4. Thanks for pointing me into the right direction.
Uwe
--
MMK GmbH, Fleyer Str. 196, 58097 Hagen
[EMAIL PROTECTED]
Tel: 02331 840446Fax: 02331 843920
signature.asc
Description: Digital signature
Bug#656586: routino-www: fails to purge - command in postrm not found
On Fri, Dec 05, 2014 at 05:06:27PM +0100, Sebastiaan Couwenberg wrote: > Hi Niels, > > The issues with routino where not on the Debian GIS teams radar because > the Maintainer field is not set the team address even though the source > lives in the Debian GIS git repository on Alioth. > > Uwe Steinmann has taken over maintenance of routino from Thibaut Gridel > since November 2011, so I've added him to the discussion. > > @Uwe, there are no tags in git, can you push your tags to Alioth too? tags are pushed. Sorry for missing that. > In the mean time I'm updating my clone of the repo to incorporate the > recent NMUs and prepare a new upload for unstable if Uwe is unable to do so. I can do the upload if you like. Uwe -- MMK GmbH, Fleyer Str. 196, 58097 Hagen uwe.steinm...@mmk-hagen.de Tel: 02331 840446Fax: 02331 843920 signature.asc Description: Digital signature
