On Wed, Jun 27, 2012 at 05:46:23PM -0500, Gunnar Wolf wrote:
Luca Falavigna dijo [Wed, Jun 27, 2012 at 11:41:21PM +0200]:
tags 679300 + moreinfo
thanks
Not ready yet:
# Broken Depends:
dhelp: dhelp
Hi,
Grr, it seems the dhelp version I just uploaded contains my fix - But
Hi all,
Switching to ruby 1.9.1 was left for next version (0.6.22), in order to
have 0.6.21 ready before the freeze (it was not a trivial change because
the test suite fails when using 1.9.1 and -cf. the changelog- I had
already a long list of things to be done).
When I find a sponsor and have
Done,
thanks for the patch! Already updated source tree in
http://anonscm.debian.org/gitweb/?p=collab-maint/dhelp.git;a=summary
and added a new version of the package at mentors.debian.net
(http://mentors.debian.net/debian/pool/main/d/dhelp/dhelp_0.6.21.dsc).
I only hope to manage find a
Hi,
I have uploaded a new version of the dhelp package to also address bug
#678055, which showed up shortly after my initial RFS.
In case someone is reviewing the previous version of the package, the
changes are located in only one file: src/dhelp_parse.rb (and also
debian/changelog, of course).
from
http://anonscm.debian.org/gitweb/?p=collab-maint/dhelp.git.
Changes since the last upload:
dhelp (0.6.21) unstable; urgency=low
* New maintainer: Georgios M. Zarkadas g...@member.fsf.org (Closes:
#650441).
* Support other web servers in addition to apache2 (Closes: #669041
Στις 24-05-2012, ημέρα Πεμ, και ώρα 21:11 +0100, ο/η Ian Jackson έγραψε:
Joey Hess writes (Bug#665851: Bug#597050: GNU parallel, name conflict with
moreutils):
Ian Jackson wrote:
Ah, I'm sorry, I must have misunderstood your comments in #597050.
I took them for an objection, rather
Confirmed the bug using a minimal sid chroot where bozohttpd and dhelp were
installed with default configurations. The fix is to insert a symlink with
name doc inside /var/www pointing to /usr/share/doc. That is, issue (as root)
the command:
ln -s /usr/share/doc /var/www/doc
The bug went
Package: openclipart
Version: 0.18+dfsg-10
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The clipart contained in version 2.0 is an almost totally different set
of images. From the initial 8121 clips of ver. 0.18+dfsg, only about 582
survive (the about because some of the
Sorry for the previous message, it left my console incomplete;
continuing with the intended reply:
Προωθημένο Μήνυμα
Από: Georgios M. Zarkadas georgios.zarka...@gmail.com
Προς: Rogério Brito rbr...@ime.usp.br
Θέμα: Re: Progress?
Ημ/νία: Mon, 05 Mar 2012 01:30:00 +0200
Στις 04
/iEVs82oSFIQQp7CUj9w4yMnqAJjiFbkvqxxUw48A6C7COLyCw5d1Qb567
S2O7b1Kj9TLvmq4FwlQlR5paeKV/t/oAYfQ8DDSvqLngtLWUmG9uHwQfWbiiO+/r
K+0PtuWSYRWEqnkY/WNzN2BvHA5TFd0ePH8Nqqd/CBHUH7ymmSh6vjDGOHDl8M4=
=RYfu
-END PGP SIGNATURE-
From 18733cfaa05bbd9956ced1333c20f95f0d2cff0d Mon Sep 17 00:00:00 2001
From: Georgios M. Zarkadas
From the OP's message:
...
This is not what was set in /etc/backup-manager.conf at that time.
For me it looks like the config file is not read, maybe because of
the warning, and debconf uses some kind of defaults for its report.
I had changed the config file by hand, but AFAIK it was correct
Package: highlight
Version: 2.16-1
Severity: normal
Tags: upstream patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
As is, the shebang recognition code matches the shebang against the entire
first line of the file.
This has the undesired effect that shebangs which contain switches after the
Package: highlight
Version: 2.16-1
Severity: wishlist
Tags: upstream
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Attached is a patch (file: patch2.tar.bz2) with updated and new shebang
regexes to account for the following use cases:
* Whitespace between the starting #! and the executable's
A few remarks, after looking the source:
-- libfile-slurp-perl is not a dependency anymore from version 0.7.9
(cf. the diff between commits 9a00cd (version 0.7.9) and 91830b (version
0.7.8) at upstream's cvs: https://github.com/sukria/Backup-Manager ,
branch 'releases').
-- libnet-amazon-s3-perl
Στις 23-01-2012, ημέρα Δευ, και ώρα 19:25 +0100, ο/η Sven Joachim
έγραψε:
On 2012-01-22 17:44 +0100, Georgios M. Zarkadas wrote:
Στις 21-01-2012, ημέρα Σαβ, και ώρα 14:00 +0100, ο/η Sven Joachim
έγραψε:
On 2012-01-16 17:58 +0100, Sven Joachim wrote:
It seems that we need a migration
Στις 21-01-2012, ημέρα Σαβ, και ώρα 14:00 +0100, ο/η Sven Joachim
έγραψε:
On 2012-01-16 17:58 +0100, Sven Joachim wrote:
It seems that we need a migration path to the single md5sums file, since
(with backup-manager from git master) cron spams me with mails
containing messages like these:
tags 615900 + patch
thanks
Hi,
I attach a set of three patches that fix this bug, to be applied in the
order they are numbered (...once_NUM-...).
[Please read notes at the end of this message on how to apply]
The core idea behind the patch-set is to defer the indexing until the
installation
+5lXuzSN3KCDPCZGkPlEs/3e6+ka3cbz/0KLsc478cKbu7rKy2W1xPKUyZRM=
=cAdy
-END PGP SIGNATURE-
# Greek translation of the debsums package.
# Copyright (C) 2011 THE PACKAGE'S COPYRIGHT HOLDER(S)
# This file is distributed under the same license as the debsums package.
# Georgios M. Zarkadas g
Package: dhelp
Version: 0.6.19
Severity: normal
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The postrm script removes directory /etc/dhelp. However this directory is not
created by the package during install since lenny (the last version I could
find which did, is 0.5.24 in etch).
tags 554660 + patch
thanks
The attached patch builds the package successfully in a sid pbuilder
chroot with EXTRAPACKAGES=binutils-gold on an amd64 system. I attach
the build log also, FYI.
In my opinion this should be treated as a Debian-specific patch to make
the package build until upstream
/el.po
@@ -0,0 +1,107 @@
+# Greek translation of dhelp messages.
+# Copyright (C) 2011 Georgios M. Zarkadas g...@member.fsf.org
+# This file is distributed under the same license as the dhelp package.
+# Georgios M. Zarkadas g...@member.fsf.org, 2011.
+#
+msgid
+msgstr
+Project-Id-Version: dhelp\n
tags 561883 + patch
thanks
The attached patch solves the issue in all affected versions of dhelp
(up to 0.6-19).
What the patch does is to use shell scripts for decompression and
conversion. The scripts hide the -often quite large- output from the
tools and instead just output one line with the
tags 556509 + patch
tags 556509 + upstream
thanks
The attached patch seems to resolve the issue. The package built
succesfully after applying it, inside a pbuilder chroot with
EXTRAPACKAGES=binutils-gold, on an amd64 system.
The patch modifies just the Makefile. It is thus IMO an upstream issue,
reassign 641917 dhelp 0.6.19
thanks
The +nmu1 appearing in the package version at my first message
is from the local version made to test this as well as #561883 and
#567889 patches.
The patch is to the version 0.6.19 sources of the package.
regards
George Zarkadas
signature.asc
Description:
Package: swish++
Version: 6.1.5-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Please disregard the comments of my previous message; while I had the gold
linker in my system, the build chroot contained the old ld. Thus, the patch
supplied in bug #629813 does not alone fix
Package: jailer
Version: 0.4-16
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I confirmed the bug on a clean debian unstable distribution and also that the
changes to debian/rules from the OP's patch indeed make the package to build.
However the OP's patch cannot apply as-is
I just noticed that upstream has already incorporated a relevant patch
for its 0.7.10 release source tree.
Thus, I will resubmit only a subset of this patch (namely the support
for connecting through local unix sockets and for the archive file
format) directly to upstream.
Therefore I guess
Package: backup-manager
Version: 0.7.9-3
Severity: wishlist
Tags: upstream patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Attached is a patch to replace the current scheme for storing md5 sums (one
file per day) with a single file. IMHO this simplifies the procedure and works
better with
Package: backup-manager
Version: 0.7.9-3
Severity: wishlist
Tags: upstream patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Currently when more than one job is run at the same day, backup-manager
uploads all archives of the day that exist in the repository in each job's
invocation. This
Package: backup-manager
Version: 0.7.9-3
Severity: normal
Tags: upstream patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Backup-manager calculates the date string of the archive name (the TODAY env
var) upon startup, then performs the backup, then runs backup-manager-upload
with a date
I resubmit the same patch as in my previous message, but in a form
suitable for direct inclusion to the package's debian/patches directory.
I have confirmed that the patch is applied cleanly by making a test
build with both this and the patches from the #637743 bug report.
regards
George
Package: backup-manager
Version: 0.7.9-3
Severity: wishlist
Tags: upstream patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Attached you will find a patch (backup-method-postgresql.diff) to add a
postgresql method
to backup manager. AFAIK PostgreSQL is the default DBMS installed by Debian
The attached patch:
-- moves the crack files in question from /var/run/Crack
to /var/lib/Crack
-- modifies the postrm script to purge /var/lib/Crack also
Thus it fixes both #387756 and #611720.
I didn't touched the debian/changelog; it will also need to be modified
to reflect the changes of the
The following patch fixes the issue (builds the package in an amd64):
==
diff --git a/encoded_char.h b/encoded_char.h
index 819c993..6b9a371 100644
--- a/encoded_char.h
+++ b/encoded_char.h
@@ -25,6 +25,7 @@
// standard
#include
Package: backup-manager
Version: 0.7.9-3
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The patch supplied in previous message leaves the paths in absolute form when
backup path is /. This works with tar, but not with dar which requires that
paths passed with the -P option be
Package: pbuilder
Version: 0.200
Severity: normal
Tags: patch
When issuing DIST=... pdebuild [1] from within a package source directory
to start building it, /usr/lib/pbuilder/pbuilder-buildpackage outputs
the above error and build fails.
After searching it, it appears that the following line
Hi,
thanks for the response, I give update information below.
Στις 24-07-2011, ημέρα Κυρ, και ώρα 14:22 +0100, ο/η Stephen Gran
έγραψε:
...
# check user and group names also against this regular expression.
- -#NAME_REGEX=^[a-z][-a-z0-9_]*\$
+#NAME_REGEX=^[a-z][-a-z0-9_]*\$?$
This
Package: bash
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Unable to reproduce on my system.
The initial script executed without coredumping. A sample (first few lines) of
the log file that created in my /tmp is provided below:
unixy-backup.restore_metadata:
Package: base-files
Version: 6.0squeeze2
Severity: wishlist
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
This is a solution to bug #571086 (now closed) which keeps /etc/login.defs as
the only place to set PATH, by computing the set there value on the fly using
only grep and
Package: base-files
Version: 6.0squeeze2
Severity: normal
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Per bash manual: When bash is invoked with the name sh, it tries to mimic
the startup behavior of historical versions of sh as closely as possible,
while conforming to the posix
Package: global
Version: 5.7.1-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I just confirmed that both bugs exist and that both patches
(for /usr/lib/cgi-bin/gsearch.cgi and for /usr/bin/htconfig)
are working on a debian/squeeze system.
(NB: The debsums error is due to the
Package: adduser
Version: 3.112+nmu2
Severity: normal
Tags: patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The default value of variable NAME_REGEX shipped within the package's file
/usr/share/adduser/adduser.conf (which is copied upon installation to
etc/adduser.conf) is incorrect.
42 matches
Mail list logo
