Looking for a sponsor: gtkdialog
Hi, my name is Fabio Tranchitella, and I just started the process to become an official Debian Developer. My first package was already checked and uploaded from sgran, but he haven't enough time to help me with my second package, gtkdialog. It is very similar to xdialog, but with gtkdialog developers can create very complex GUI with an easy-to-learn XML language. This is why I'm looking for a sponsor. Here there is the description of the package: * Package name: gtkdialog Version : 0.58.8 Upstream Author : Pere Laszlo [EMAIL PROTECTED] * URL : http://www.gnu.org/directory/devel/gtkdialog.html * License : GPL Description : GUI-creation command-line utility based on GTK+ library gtkdialog is a GUI-creation utility based on GTK+ library that can be used with an arbitrary interpreter. Developers can describe a graphical user interface in a simple XML-like language, and use it with any interpreter that supports either files, standard I/O, or environment variables. It can be called as an external program from the interpreter or used as a stand-alone framework for the application. Stand-alone, bash, and awk examples are provided. My ready-to-upload (IMHO :)) Debian package is available on http://www.kobold.it/gtkdialog/ If someone is interested in sponsoring me, I can give him any information about the software or the package. Thanks in advance, Fabio T. PS: Please CC me because I'm not subscribed to this mailing list. -- Fabio Tranchitella ! kobold.it, Turin, Italy - Free is better! --- http://www.kobold.it, [EMAIL PROTECTED], [EMAIL PROTECTED] --- GPG Key fingerprint: 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564 signature.asc Description: Questa parte del messaggio è firmata
Re: Looking for a sponsor: gtkdialog
On Thu, May 27, 2004 at 08:50:57AM +0200, Fabio Tranchitella wrote: [...] My ready-to-upload (IMHO :)) Debian package is available on http://www.kobold.it/gtkdialog/ Just my 0.02$: debian/copyright: Copyright: GPL I don't think that copyrights belongs to GPL. Copyrights belongs to authors. Take a look at: http://lists.debian.org/debian-devel/2004/debian-devel-200403/msg02190.html debian/rules: There are many commented dh_* commands. Remove them if you don't use them. [...] Consider that I'm not DD, and thus I won't sponsor this package. regards fEnIo -- _ Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | IRC:fEnIo _|_|_ 32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Polska (0 0) phone:+48602383548 | Slackware - the weakest link ooO--(_)--Ooo http://skawina.eu.org | JID:[EMAIL PROTECTED] | RLU:172001 signature.asc Description: Digital signature
Re: Looking for a sponsor: gtkdialog
On Thu, May 27, 2004 at 08:50:57AM +0200, Fabio Tranchitella wrote: [...] My ready-to-upload (IMHO :)) Debian package is available on http://www.kobold.it/gtkdialog/ One more thing. debian/changelog: * Initial Release. You should certainly close your ITP here. Something like that: * Initial Release. (Closes: #250391) regards fEnIo -- _ Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | IRC:fEnIo _|_|_ 32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Polska (0 0) phone:+48602383548 | Slackware - the weakest link ooO--(_)--Ooo http://skawina.eu.org | JID:[EMAIL PROTECTED] | RLU:172001 signature.asc Description: Digital signature
Re: RFC: various KDE window themes and styles
Mike Hommey wrote: What you call kwin-style seems to me to be the kde widgets theme while what you call kwin-decor seems to me to be the kde window decorations, which I named kwin-style in kwin-style-mkultra for I can't remember exactly which reason. So, for consistency (and even though I asked for deletion of kwin-style-mkultra because it is outdated), I'd say s/kwin-style/kde-theme/ s/kwin-decor/kwin-style/ Can't agree. The terminology follows KDE naming scheme for such elements and it makes sense for me - kwin-style is Window Style (same name is used in K menu), kwin-decor is Windows Decoration (and again: same name is used in K menu). What I'd like to get rid of is kwin- prefix, but since there are other packages that uses such prefix, mine got them too. Regards, -- Daddy, what Formatting drive C: means?... Marcin http://wfmh.org.pl/carlos/
Re: Looking for a sponsor: gtkdialog
Thanks for your replies. I agree with you so I've just made the changes you suggested. The new package is available on the same place, http://www.kobold.it/gtkdialog Take care, Fabio T. Il gio, 2004-05-27 alle 09:17, Bartosz Fenski aka fEnIo ha scritto: On Thu, May 27, 2004 at 08:50:57AM +0200, Fabio Tranchitella wrote: [...] My ready-to-upload (IMHO :)) Debian package is available on http://www.kobold.it/gtkdialog/ One more thing. debian/changelog: * Initial Release. You should certainly close your ITP here. Something like that: * Initial Release. (Closes: #250391) regards fEnIo -- Fabio Tranchitella ! kobold.it, Turin, Italy - Free is better! --- http://www.kobold.it, [EMAIL PROTECTED], [EMAIL PROTECTED] --- GPG Key fingerprint: 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564 signature.asc Description: Questa parte del messaggio è firmata
Re: [[:digit:]] - bashism?
On Thu, 2004-05-27 at 00:25, Stephen Gran wrote: Does anyone know the POSIX standard well enough to know if this is a bug in dash, or a bashism? $ touch a1 $ bash $ echo a[[:digit:]] a1 $ dash $ echo a[[:digit:]] a[[:digit:]] $ posh $ echo a[[:digit:]] a1 The posh shell is supposed to be strictly POSIX and it accepts '[[:digit:]]', so I guess this is a bug in dash. -- Thomas Hood
[RFS/RFM again] kdiff3 - compares and merges 2 or 3 files or directories
Hello! I'm looking for someone to sponsor kdiff3 again. The former versions have already been tested and sponsored by Rene Engelhard, so the package should be in good shape. Upstream is very responsive. kdiff3 is contained in sarge. I'd like to apply as DD in future. kdiff3 is a graphical diff. I think the most useful difference to many other diff programs is that the difference is shown by character, not by line. Additionally, it integrates well into KDE. Packagename:kdiff3 Version:0.9.83-2 URL:http://kdiff3.sourceforge.net License:GPL Description: compares and merges 2 or 3 files or directories KDiff3 compares two or three input files and shows the differences line by line and character by character. It provides an automatic merge facility and an integrated editor for comfortable solving of merge conflicts. KDiff3 allows recursive directory comparison and merging as well. The package lintian and linda clean. It can be found at: http://user.cs.tu-berlin.de/~eikes/debian/kdiff3/ Ciao, Eike
Re: RFS/RFC: gtklp-0.9s-1
On Wed, May 26, 2004 at 07:08:57PM +0200, Andreas Metzler wrote: Hello, A significant percentage of d-ds, including myself is not fond of this kind of changelog entries. The changelog should document changes and not simply be used as bug-closer. 170025 should be merged[1] with 239509. 174518 should be merged with 177478 and should have a explanation in the changelog. None of #153779, #170642, #226839 are requests for a new upstream version, they are just bugs that happen to be fixed in the new version, but your changelog implies this. I'd suggest something like this: * New upstream version, merged patches in 0.9p-1 to upstream source. - Now doesn't dump core when no printers are available (Closes: #239509)[2] - Corrected switched Spanish translation for odd and even (Closes: #226839) - frobnocation of blah (C) ... * other changes * more changes cu andreas [1] http://www.debian.org/Bugs/server-control [2] If bugs are merged they are automatically closed together. Thanks for the input. I've done the necessary changes, so here's the new file: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 May 2004 14:05:34 +0800 Source: gtklp Binary: gtklp Architecture: source i386 Version: 0.9s-1 Distribution: unstable Urgency: low Maintainer: Zak B. Elep [EMAIL PROTECTED] Changed-By: Zak B. Elep [EMAIL PROTECTED] Description: gtklp - Frontend for CUPS written in GTK2 Closes: 153779 170025 170642 174518 177478 218608 226839 249494 Changes: gtklp (0.9s-1) unstable; urgency=low . * New upstream version, merged patches in 0.9p-1 to upstream source: - Look check boxes now work properly (Closes: #153779) - (Some) typos in the man page have been corrected (Closes: #170642) - Spanish translation of even and odd are now correct (Closes: #226839) * GTK2 is now the default, fixed debian/control and description * Fixed debian/rules to deal with leftover .gmo's * Fixed debian/copyright, but source should also be changed to conform with GPL licensing rules (i.e., putting the license declaration _inside_ the source, it's not enough to just include the COPYING file ;) * Rebuilt gtklp against libcupsys2-gnutls10 (Closes: #249494) * Upstream says the following bugs have been fixed since 0.9p: - Printer instances ought to be supported (Closes: #218608) - Now doesn't dump core when no printers are available (Closes: #170025) - Should now save page option on being told to do so (Closes: #174518) - Printing on localhost should now recognize printer settings (Closes: #177478) Files: 1f18c4508dfac5f00608be6eceda0924 626 x11 optional gtklp_0.9s-1.dsc b96d6129dda374538f78a4c39c06dd26 1009713 x11 optional gtklp_0.9s.orig.tar.gz 31a1bd6cd2b3527667dfb4406098c8c2 6076 x11 optional gtklp_0.9s-1.diff.gz ba258b58aa442a0f58500f5a804b49ee 142310 x11 optional gtklp_0.9s-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAtYaWV4ex/fpThR0RAv8MAKCLnqezXixcH2rZdxiHPg0HH9p9bgCgs5D/ epHBfDi2/+1VrG0kZtIvvSw= =aoHs -END PGP SIGNATURE- My deepest appreciation for that tidbit of info. now, I'm one step closer to d-d ;) Cheers, Zakame
reporting FTBFS bugs
hi, I have some questions regarding FTBFS bugs. Sorry if they seem too naive but I'm always afraid of doing something wrong and I thought I'd better ask here then. 1. if a package fails in any buildd machine, thats a FTBFS bug per se, right? 2. who can/should report FTBFS bugs when they occur in a buildd machine? I've mostly seen them reported by the buildd's admin, but cyrus-sasl2-mit failed on arm more than a month ago [1] (but I noticed today) and there has been no bug report. 3. is it tracked anywhere (other than the bug report, non-existant in this case) if this is being worked on? Having a month passed, I'd assume that the maintainer isn't aware of this, but I really can't tell. So I'm mainly asking if it is OK to file the bug myself, and if that should be reported elsewhere. TIA and sorry for the annoyance, [1] http://buildd.debian.org/build.php?arch=armpkg=cyrus-sasl2-mit -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 The total accumulated knowledge of all the men that ever walked the Earth on the topic of women can fit in the period at the end of this sentence.
Re: adopt orphaned package cpuburn
Erik Schanze said: Lucas Albers: I'd like to adopt this package, and I would need someone to sponsor me on it for the upload. Are there any files to look over? Did you realized that the project website and author email has changed? I had also a look at this package and has communicate with upstream, but you anounced this first here, so its yours (I think). If you've already talked to the upstream then go ahead. I'm new to maintaining packages so I'd be slow at it. Your farther along on it then I am. You can have it. -- --Luke CS Sysadmin, Montana State University-Bozeman
Re: adopt orphaned package cpuburn
Erik Schanze said: Lucas Albers: I'd like to adopt this package, and I would need someone to sponsor me on it for the upload. Are there any files to look over? Did you realized that the project website and author email has changed? I had also a look at this package and has communicate with upstream, but you anounced this first here, so its yours (I think). If you've already talked to the upstream then go ahead. Your definiteally more familiar with the package then I am. I'm new to maintaining packages so I'd be slow at it. Your farther along on it then I am. You can have it. -- --Luke CS Sysadmin, Montana State University-Bozeman
RFS: Scorched3D - 3D artillery game similar to Scorched Earth
Hello. I'm looking for sponsor for another game - Scorched3D. * Package name: scorched3d scorched3d-data Version : 37.1 Upstream Author : Scorched3D Development Team * URL : http://www.scorched3d.co.uk/ * License : GPL Scorched 3D is a game based heavily on the classic DOS game Scorched Earth The Mother Of All Games. Scorched 3D adds amongst other new features a 3D island environment and LAN and internet play. . Homepage: http://scorched3d.sourceforge.net/ Packages are linda lintian clean, and build fine with pbuilder. Anyone interested in sponsoring this game? It can be fetched from http://skawina.eu.org/scorched3d/ regards fEnIo -- _ Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | IRC:fEnIo _|_|_ 32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Polska (0 0) phone:+48602383548 | Slackware - the weakest link ooO--(_)--Ooo http://skawina.eu.org | JID:[EMAIL PROTECTED] | RLU:172001 signature.asc Description: Digital signature
Re: reporting FTBFS bugs
On 2004-05-27 Adeodato Simó [EMAIL PROTECTED] wrote: [...] 1. if a package fails in any buildd machine, thats a FTBFS bug per se, right? It is not necessarily a bug in the package, if that is what you are asking, some dependency might not be ready, the buildd might be broken (out of diskspace) or toolchain might be installed in a buggy version. 2. who can/should report FTBFS bugs when they occur in a buildd machine? I've mostly seen them reported by the buildd's admin, but cyrus-sasl2-mit failed on arm more than a month ago [1] (but I noticed today) and there has been no bug report. buildd-maintainers regularily check the build-logs, it is natural that they often submit these bug-reports. 3. is it tracked anywhere (other than the bug report, non-existant in this case) if this is being worked on? Having a month passed, I'd assume that the maintainer isn't aware of this, but I really can't tell. Not that I am aware of. - You could check the archives of debian-arm. So I'm mainly asking if it is OK to file the bug myself, and if that should be reported elsewhere. Yes, it is ok, and the BTS is imho the correct place. TIA and sorry for the annoyance, no problem, there was no annoyance involved. ;-) [1] http://buildd.debian.org/build.php?arch=armpkg=cyrus-sasl2-mit Hmm. if /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../plugins -c -o dlopen.lo `test -f 'dlopen.c' || echo './'`dlopen.c; \ then mv -f .deps/dlopen.Tpo .deps/dlopen.Plo; \ else rm -f .deps/dlopen.Tpo; exit 1; \ fi gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../plugins -I../include -I/usr/include/kerberos gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../plugins -I../include -I/usr/include/kerberos make[3]: *** [dlopen.lo] Error 1 [long lines simply cut off] Strange. The buildlog simply tells absolutely nothing. cu andreas -- See, I told you they'd listen to Reason, [SPOILER] Svfurlr fnlf, fuhggvat qbja gur juveyvat tha. Neal Stephenson in Snow Crash
Re: reporting FTBFS bugs
* Andreas Metzler [Thu, 27 May 2004 19:29:02 +0200]: On 2004-05-27 Adeodato Simó [EMAIL PROTECTED] wrote: [...] 1. if a package fails in any buildd machine, thats a FTBFS bug per se, right? It is not necessarily a bug in the package, if that is what you are asking, some dependency might not be ready, the buildd might be broken (out of diskspace) or toolchain might be installed in a buggy version. yep, I thought it later. 3. is it tracked anywhere (other than the bug report, non-existant in this case) if this is being worked on? Having a month passed, I'd assume that the maintainer isn't aware of this, but I really can't tell. Not that I am aware of. - You could check the archives of debian-arm. I looked there, and nothing. So I'm mainly asking if it is OK to file the bug myself, and if that should be reported elsewhere. Yes, it is ok, and the BTS is imho the correct place. TIA and sorry for the annoyance, no problem, there was no annoyance involved. ;-) ok, thanks! -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 The true teacher defends his pupils against his own personal influence. -- Amos Bronson Alcott
Re: adopt orphaned package cpuburn
Lucas Albers: Erik Schanze said: Lucas Albers: I'd like to adopt this package, and I would need someone to sponsor me on it for the upload. Are there any files to look over? Did you realized that the project website and author email has changed? I had also a look at this package and has communicate with upstream, but you anounced this first here, so its yours (I think). If you've already talked to the upstream then go ahead. I only have searched his new mail address, because my first mail was rejected. (I would tell him that there is a mistake on his site.) I have greped some news groups an find his new website, but his email address was the old one. :-( So I guess his new mail address and had luck. No big deal. This should be noticed in debian/copyright. I'm new to maintaining packages so I'd be slow at it. I'm new in maintaining package, too. This package is right to make the first steps, the codebase will changes slow, too. ;-) Have you read Debian New Maintainer Guide? It helps me a lot on my first packages. Your farther along on it then I am. You can have it. Hm. This is not was I meen as I wrote this mail. I'm sorry, if it sounds this way, I'm not a native speaker of English. Please let me encourage you to do needed work on this package and ask again for comments and sponsors, if you have build a package. First you should retitle bug to ITA as described in: http://www.debian.org/devel/wnpp/index.html#howto-o to show that this package has a new maintainer. Regards, Erik -- www.ErikSchanze.de * Bitte keine HTML-Mails! No HTML mails, please! Maillimit: 1 MB * * Linux-Info-Tag in Dresden, am 30. Oktober 2004 * Info: http://www.linux-info-tag.de *
Re: reporting FTBFS bugs
On Thu, May 27, 2004 at 07:58:54PM +0200, Adeodato Simó [EMAIL PROTECTED] wrote: 3. is it tracked anywhere (other than the bug report, non-existant in this case) if this is being worked on? Having a month passed, I'd assume that the maintainer isn't aware of this, but I really can't tell. Not that I am aware of. - You could check the archives of debian-arm. Well, if I have a bug filed against any of my packages, and I am working on fixing it, then I set the flag 'confirmed', and when it is fixed, but not yet uploaded, I set 'pending'. But that's me, others may not do this way. Cheers, Laszlo
package cleanup script
I have written a (useful?) script to find all packages which have not be
used for a long time and reports this to the user (i.e., some package is
installed but none of its files have been accessed in 60 days). Would
this be useful? Is there some other forum where I should post this?
I have attached the script for consideration. The only requirements are
ruby-1.8 and grep-dctrl.
-Dale Hawkins
#!/usr/bin/ruby
require 'pathname'
require 'getoptlong'
def usage
$stderr.puts usage: #{$0} [ -v ]* [ -r ] [ -d days(60) ] pkg_name [ ... ]
exit 1
end
days = 60
verbose = 0
recursive = false
opts = GetoptLong.new([--days, -d, GetoptLong::REQUIRED_ARGUMENT],
[--verbose, -v, GetoptLong::NO_ARGUMENT],
[--recursive, -r, GetoptLong::NO_ARGUMENT],
[--help, -h, GetoptLong::NO_ARGUMENT])
opts.each {|opt,val|
case opt
when --days then days = val
when --verbose then verbose += 1
# when --recursive then recursive = true
else
usage
end
}
if days.to_i == 0
$stderr.puts illegal value given for days: #{days}
end
days = days.to_i
if ARGV.empty?
packages = IO.popen('grep-status -FStatus -sPackage -n install ok
installed').readlines
else
packages = ARGV
end
class Pathname
@@secondsPerDay = 60 * 60 * 24
def parentInArray(paths)
paths.any? { | p |
fnmatch(p)
}
end
def lastAccessed(t = Time.now)
((t - self.atime)/@@secondsPerDay).to_i
end
end
class Package
@@filesToIgnore = [
'/usr/lib/menu/*',
'/usr/share/applications/*',
'/usr/share/man/*',
'/usr/share/pixmaps/*',
'/usr/share/mime-info/*',
'/usr/lib/mime/packages/*',
'/usr/share/doc-base/*',
]
@@docDirs = [
'/usr/share/doc/*',
]
@@binaryDirs = [
'/lib/*',
'/usr/lib/*',
'/bin/*',
'/usr/bin/*',
]
def initialize(name)
@name = name
end
def getFiles
if not defined? @files
@files = IO.popen(grep-dctrl -FStatus ' installed' /var/lib/dpkg/status
| grep-dctrl -PX -n -s Package [EMAIL PROTECTED]).collect { | pkg |
IO.popen(dpkg --listfiles #{pkg}).collect { | fn |
fn.chomp!
if fn.empty?
false
else
p = Pathname.new(fn.chomp)
end
}.select { | p |
p (p.file? (! p.parentInArray(@@filesToIgnore)))
}
}.flatten
end
if @files.empty?
raise No regular files found (or package not installed)
end
@files
end
def docFiles
if not defined? @docFiles
@docFiles = getFiles.select { | p |
p.parentInArray(@@docDirs)
}.sort {|x,y| y.atime = x.atime }
end
@docFiles
end
def binaryFiles
if not defined? @binFiles
@binFiles = getFiles.select { | p |
p.parentInArray(@@binaryDirs)
}.sort {|x,y| y.atime = x.atime }
end
@binFiles
end
def lastDocAccess
if docFiles.empty?
raise No document files
else
docFiles[0].lastAccessed
end
end
def showlastDocumentAccess(number = 1)
if docFiles.empty?
raise No doc files
else
access_times = (0...([number, docFiles.size].min)).collect { | n |
#{docFiles[n]} was last accessed #{docFiles[n].lastAccessed} days ago
}
end
end
def lastBinaryAccess
if binaryFiles.empty?
raise No binary files
else
binaryFiles[0].lastAccessed
end
end
def showlastBinaryAccess(number = 1)
if binaryFiles.empty?
raise No binary files
else
access_times = (0...([number, binaryFiles.size].min)).collect { | n |
#{binaryFiles[n]} was last accessed #{binaryFiles[n].lastAccessed}
days ago
}
end
end
def getWhatDeps
IO.popen(grep-status -n -s Package -FDepends -e [EMAIL
PROTECTED]).readlines
end
end
packages.each { | pn |
pn.chomp!
next if pn.empty?
if verbose 0
puts === #{pn} ===
end
success = false
p = Package.new(pn)
binDays = 1
begin
binDays = p.lastBinaryAccess
if verbose 1
puts p.showlastBinaryAccess(10).collect { | s | + s }
end
success = true
rescue
if verbose 0
$stderr.puts $!
end
end
docDays = 1
begin
docDays = p.lastDocAccess
if verbose 1
puts p.showlastDocumentAccess(10).collect { | s | + s }
end
success = true
rescue
if verbose 0
$stderr.puts $!
end
end
if success
if [binDays, docDays].min days
puts Recommend #{pn} for removal
if recursive
puts p.getWhatDeps
end
else
if verbose 0
puts Keeping #{pn}
end
end
end
}
Re: Looking for a sponsor: gtkdialog
On Thu, May 27, 2004 at 08:50:57AM +0200, Fabio Tranchitella wrote: [...] My ready-to-upload (IMHO :)) Debian package is available on http://www.kobold.it/gtkdialog/ Just my 0.02$: debian/copyright: Copyright: GPL I don't think that copyrights belongs to GPL. Copyrights belongs to authors. Take a look at: http://lists.debian.org/debian-devel/2004/debian-devel-200403/msg02190.html debian/rules: There are many commented dh_* commands. Remove them if you don't use them. [...] Consider that I'm not DD, and thus I won't sponsor this package. regards fEnIo -- _ Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | IRC:fEnIo _|_|_ 32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Polska (0 0) phone:+48602383548 | Slackware - the weakest link ooO--(_)--Ooo http://skawina.eu.org | JID:[EMAIL PROTECTED] | RLU:172001 signature.asc Description: Digital signature
Re: Looking for a sponsor: gtkdialog
On Thu, May 27, 2004 at 08:50:57AM +0200, Fabio Tranchitella wrote: [...] My ready-to-upload (IMHO :)) Debian package is available on http://www.kobold.it/gtkdialog/ One more thing. debian/changelog: * Initial Release. You should certainly close your ITP here. Something like that: * Initial Release. (Closes: #250391) regards fEnIo -- _ Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | IRC:fEnIo _|_|_ 32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Polska (0 0) phone:+48602383548 | Slackware - the weakest link ooO--(_)--Ooo http://skawina.eu.org | JID:[EMAIL PROTECTED] | RLU:172001 signature.asc Description: Digital signature
Re: RFC: various KDE window themes and styles
Mike Hommey wrote: What you call kwin-style seems to me to be the kde widgets theme while what you call kwin-decor seems to me to be the kde window decorations, which I named kwin-style in kwin-style-mkultra for I can't remember exactly which reason. So, for consistency (and even though I asked for deletion of kwin-style-mkultra because it is outdated), I'd say s/kwin-style/kde-theme/ s/kwin-decor/kwin-style/ Can't agree. The terminology follows KDE naming scheme for such elements and it makes sense for me - kwin-style is Window Style (same name is used in K menu), kwin-decor is Windows Decoration (and again: same name is used in K menu). What I'd like to get rid of is kwin- prefix, but since there are other packages that uses such prefix, mine got them too. Regards, -- Daddy, what Formatting drive C: means?... Marcin http://wfmh.org.pl/carlos/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Looking for a sponsor: gtkdialog
Thanks for your replies. I agree with you so I've just made the changes you suggested. The new package is available on the same place, http://www.kobold.it/gtkdialog Take care, Fabio T. Il gio, 2004-05-27 alle 09:17, Bartosz Fenski aka fEnIo ha scritto: On Thu, May 27, 2004 at 08:50:57AM +0200, Fabio Tranchitella wrote: [...] My ready-to-upload (IMHO :)) Debian package is available on http://www.kobold.it/gtkdialog/ One more thing. debian/changelog: * Initial Release. You should certainly close your ITP here. Something like that: * Initial Release. (Closes: #250391) regards fEnIo -- Fabio Tranchitella ! kobold.it, Turin, Italy - Free is better! --- http://www.kobold.it, [EMAIL PROTECTED], [EMAIL PROTECTED] --- GPG Key fingerprint: 5465 6E69 E559 6466 BF3D 9F01 2BF8 EE2B 7F96 1564 signature.asc Description: Questa parte del messaggio =?ISO-8859-1?Q?=E8?= firmata
Re: [[:digit:]] - bashism?
On Thu, 2004-05-27 at 00:25, Stephen Gran wrote: Does anyone know the POSIX standard well enough to know if this is a bug in dash, or a bashism? $ touch a1 $ bash $ echo a[[:digit:]] a1 $ dash $ echo a[[:digit:]] a[[:digit:]] $ posh $ echo a[[:digit:]] a1 The posh shell is supposed to be strictly POSIX and it accepts '[[:digit:]]', so I guess this is a bug in dash. -- Thomas Hood -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
[RFS/RFM again] kdiff3 - compares and merges 2 or 3 files or directories
Hello! I'm looking for someone to sponsor kdiff3 again. The former versions have already been tested and sponsored by Rene Engelhard, so the package should be in good shape. Upstream is very responsive. kdiff3 is contained in sarge. I'd like to apply as DD in future. kdiff3 is a graphical diff. I think the most useful difference to many other diff programs is that the difference is shown by character, not by line. Additionally, it integrates well into KDE. Packagename:kdiff3 Version:0.9.83-2 URL:http://kdiff3.sourceforge.net License:GPL Description: compares and merges 2 or 3 files or directories KDiff3 compares two or three input files and shows the differences line by line and character by character. It provides an automatic merge facility and an integrated editor for comfortable solving of merge conflicts. KDiff3 allows recursive directory comparison and merging as well. The package lintian and linda clean. It can be found at: http://user.cs.tu-berlin.de/~eikes/debian/kdiff3/ Ciao, Eike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: RFS/RFC: gtklp-0.9s-1
On Wed, May 26, 2004 at 07:08:57PM +0200, Andreas Metzler wrote: Hello, A significant percentage of d-ds, including myself is not fond of this kind of changelog entries. The changelog should document changes and not simply be used as bug-closer. 170025 should be merged[1] with 239509. 174518 should be merged with 177478 and should have a explanation in the changelog. None of #153779, #170642, #226839 are requests for a new upstream version, they are just bugs that happen to be fixed in the new version, but your changelog implies this. I'd suggest something like this: * New upstream version, merged patches in 0.9p-1 to upstream source. - Now doesn't dump core when no printers are available (Closes: #239509)[2] - Corrected switched Spanish translation for odd and even (Closes: #226839) - frobnocation of blah (C) ... * other changes * more changes cu andreas [1] http://www.debian.org/Bugs/server-control [2] If bugs are merged they are automatically closed together. Thanks for the input. I've done the necessary changes, so here's the new file: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 27 May 2004 14:05:34 +0800 Source: gtklp Binary: gtklp Architecture: source i386 Version: 0.9s-1 Distribution: unstable Urgency: low Maintainer: Zak B. Elep [EMAIL PROTECTED] Changed-By: Zak B. Elep [EMAIL PROTECTED] Description: gtklp - Frontend for CUPS written in GTK2 Closes: 153779 170025 170642 174518 177478 218608 226839 249494 Changes: gtklp (0.9s-1) unstable; urgency=low . * New upstream version, merged patches in 0.9p-1 to upstream source: - Look check boxes now work properly (Closes: #153779) - (Some) typos in the man page have been corrected (Closes: #170642) - Spanish translation of even and odd are now correct (Closes: #226839) * GTK2 is now the default, fixed debian/control and description * Fixed debian/rules to deal with leftover .gmo's * Fixed debian/copyright, but source should also be changed to conform with GPL licensing rules (i.e., putting the license declaration _inside_ the source, it's not enough to just include the COPYING file ;) * Rebuilt gtklp against libcupsys2-gnutls10 (Closes: #249494) * Upstream says the following bugs have been fixed since 0.9p: - Printer instances ought to be supported (Closes: #218608) - Now doesn't dump core when no printers are available (Closes: #170025) - Should now save page option on being told to do so (Closes: #174518) - Printing on localhost should now recognize printer settings (Closes: #177478) Files: 1f18c4508dfac5f00608be6eceda0924 626 x11 optional gtklp_0.9s-1.dsc b96d6129dda374538f78a4c39c06dd26 1009713 x11 optional gtklp_0.9s.orig.tar.gz 31a1bd6cd2b3527667dfb4406098c8c2 6076 x11 optional gtklp_0.9s-1.diff.gz ba258b58aa442a0f58500f5a804b49ee 142310 x11 optional gtklp_0.9s-1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAtYaWV4ex/fpThR0RAv8MAKCLnqezXixcH2rZdxiHPg0HH9p9bgCgs5D/ epHBfDi2/+1VrG0kZtIvvSw= =aoHs -END PGP SIGNATURE- My deepest appreciation for that tidbit of info. now, I'm one step closer to d-d ;) Cheers, Zakame -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
reporting FTBFS bugs
hi, I have some questions regarding FTBFS bugs. Sorry if they seem too naive but I'm always afraid of doing something wrong and I thought I'd better ask here then. 1. if a package fails in any buildd machine, thats a FTBFS bug per se, right? 2. who can/should report FTBFS bugs when they occur in a buildd machine? I've mostly seen them reported by the buildd's admin, but cyrus-sasl2-mit failed on arm more than a month ago [1] (but I noticed today) and there has been no bug report. 3. is it tracked anywhere (other than the bug report, non-existant in this case) if this is being worked on? Having a month passed, I'd assume that the maintainer isn't aware of this, but I really can't tell. So I'm mainly asking if it is OK to file the bug myself, and if that should be reported elsewhere. TIA and sorry for the annoyance, [1] http://buildd.debian.org/build.php?arch=armpkg=cyrus-sasl2-mit -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 The total accumulated knowledge of all the men that ever walked the Earth on the topic of women can fit in the period at the end of this sentence. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: adopt orphaned package cpuburn
Erik Schanze said: Lucas Albers: I'd like to adopt this package, and I would need someone to sponsor me on it for the upload. Are there any files to look over? Did you realized that the project website and author email has changed? I had also a look at this package and has communicate with upstream, but you anounced this first here, so its yours (I think). If you've already talked to the upstream then go ahead. I'm new to maintaining packages so I'd be slow at it. Your farther along on it then I am. You can have it. -- --Luke CS Sysadmin, Montana State University-Bozeman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
RFS: Scorched3D - 3D artillery game similar to Scorched Earth
Hello. I'm looking for sponsor for another game - Scorched3D. * Package name: scorched3d scorched3d-data Version : 37.1 Upstream Author : Scorched3D Development Team * URL : http://www.scorched3d.co.uk/ * License : GPL Scorched 3D is a game based heavily on the classic DOS game Scorched Earth The Mother Of All Games. Scorched 3D adds amongst other new features a 3D island environment and LAN and internet play. . Homepage: http://scorched3d.sourceforge.net/ Packages are linda lintian clean, and build fine with pbuilder. Anyone interested in sponsoring this game? It can be fetched from http://skawina.eu.org/scorched3d/ regards fEnIo -- _ Bartosz Fenski | mailto:[EMAIL PROTECTED] | pgp:0x13fefc40 | IRC:fEnIo _|_|_ 32-050 Skawina - Glowackiego 3/15 - w. malopolskie - Polska (0 0) phone:+48602383548 | Slackware - the weakest link ooO--(_)--Ooo http://skawina.eu.org | JID:[EMAIL PROTECTED] | RLU:172001 signature.asc Description: Digital signature
Re: reporting FTBFS bugs
On 2004-05-27 Adeodato Simó [EMAIL PROTECTED] wrote: [...] 1. if a package fails in any buildd machine, thats a FTBFS bug per se, right? It is not necessarily a bug in the package, if that is what you are asking, some dependency might not be ready, the buildd might be broken (out of diskspace) or toolchain might be installed in a buggy version. 2. who can/should report FTBFS bugs when they occur in a buildd machine? I've mostly seen them reported by the buildd's admin, but cyrus-sasl2-mit failed on arm more than a month ago [1] (but I noticed today) and there has been no bug report. buildd-maintainers regularily check the build-logs, it is natural that they often submit these bug-reports. 3. is it tracked anywhere (other than the bug report, non-existant in this case) if this is being worked on? Having a month passed, I'd assume that the maintainer isn't aware of this, but I really can't tell. Not that I am aware of. - You could check the archives of debian-arm. So I'm mainly asking if it is OK to file the bug myself, and if that should be reported elsewhere. Yes, it is ok, and the BTS is imho the correct place. TIA and sorry for the annoyance, no problem, there was no annoyance involved. ;-) [1] http://buildd.debian.org/build.php?arch=armpkg=cyrus-sasl2-mit Hmm. if /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../plugins -c -o dlopen.lo `test -f 'dlopen.c' || echo './'`dlopen.c; \ then mv -f .deps/dlopen.Tpo .deps/dlopen.Plo; \ else rm -f .deps/dlopen.Tpo; exit 1; \ fi gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../plugins -I../include -I/usr/include/kerberos gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -I../plugins -I../include -I/usr/include/kerberos make[3]: *** [dlopen.lo] Error 1 [long lines simply cut off] Strange. The buildlog simply tells absolutely nothing. cu andreas -- See, I told you they'd listen to Reason, [SPOILER] Svfurlr fnlf, fuhggvat qbja gur juveyvat tha. Neal Stephenson in Snow Crash -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: reporting FTBFS bugs
* Andreas Metzler [Thu, 27 May 2004 19:29:02 +0200]: On 2004-05-27 Adeodato Simó [EMAIL PROTECTED] wrote: [...] 1. if a package fails in any buildd machine, thats a FTBFS bug per se, right? It is not necessarily a bug in the package, if that is what you are asking, some dependency might not be ready, the buildd might be broken (out of diskspace) or toolchain might be installed in a buggy version. yep, I thought it later. 3. is it tracked anywhere (other than the bug report, non-existant in this case) if this is being worked on? Having a month passed, I'd assume that the maintainer isn't aware of this, but I really can't tell. Not that I am aware of. - You could check the archives of debian-arm. I looked there, and nothing. So I'm mainly asking if it is OK to file the bug myself, and if that should be reported elsewhere. Yes, it is ok, and the BTS is imho the correct place. TIA and sorry for the annoyance, no problem, there was no annoyance involved. ;-) ok, thanks! -- Adeodato Simó EM: asp16 [ykwim] alu.ua.es | PK: DA6AE621 The true teacher defends his pupils against his own personal influence. -- Amos Bronson Alcott -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: adopt orphaned package cpuburn
Lucas Albers: Erik Schanze said: Lucas Albers: I'd like to adopt this package, and I would need someone to sponsor me on it for the upload. Are there any files to look over? Did you realized that the project website and author email has changed? I had also a look at this package and has communicate with upstream, but you anounced this first here, so its yours (I think). If you've already talked to the upstream then go ahead. I only have searched his new mail address, because my first mail was rejected. (I would tell him that there is a mistake on his site.) I have greped some news groups an find his new website, but his email address was the old one. :-( So I guess his new mail address and had luck. No big deal. This should be noticed in debian/copyright. I'm new to maintaining packages so I'd be slow at it. I'm new in maintaining package, too. This package is right to make the first steps, the codebase will changes slow, too. ;-) Have you read Debian New Maintainer Guide? It helps me a lot on my first packages. Your farther along on it then I am. You can have it. Hm. This is not was I meen as I wrote this mail. I'm sorry, if it sounds this way, I'm not a native speaker of English. Please let me encourage you to do needed work on this package and ask again for comments and sponsors, if you have build a package. First you should retitle bug to ITA as described in: http://www.debian.org/devel/wnpp/index.html#howto-o to show that this package has a new maintainer. Regards, Erik -- www.ErikSchanze.de * Bitte keine HTML-Mails! No HTML mails, please! Maillimit: 1 MB * * Linux-Info-Tag in Dresden, am 30. Oktober 2004 * Info: http://www.linux-info-tag.de * -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: reporting FTBFS bugs
On Thu, May 27, 2004 at 07:58:54PM +0200, Adeodato Sim [EMAIL PROTECTED] wrote: 3. is it tracked anywhere (other than the bug report, non-existant in this case) if this is being worked on? Having a month passed, I'd assume that the maintainer isn't aware of this, but I really can't tell. Not that I am aware of. - You could check the archives of debian-arm. Well, if I have a bug filed against any of my packages, and I am working on fixing it, then I set the flag 'confirmed', and when it is fixed, but not yet uploaded, I set 'pending'. But that's me, others may not do this way. Cheers, Laszlo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
package cleanup script
I have written a (useful?) script to find all packages which have not be
used for a long time and reports this to the user (i.e., some package is
installed but none of its files have been accessed in 60 days). Would
this be useful? Is there some other forum where I should post this?
I have attached the script for consideration. The only requirements are
ruby-1.8 and grep-dctrl.
-Dale Hawkins
#!/usr/bin/ruby
require 'pathname'
require 'getoptlong'
def usage
$stderr.puts usage: #{$0} [ -v ]* [ -r ] [ -d days(60) ] pkg_name [ ... ]
exit 1
end
days = 60
verbose = 0
recursive = false
opts = GetoptLong.new([--days, -d, GetoptLong::REQUIRED_ARGUMENT],
[--verbose, -v, GetoptLong::NO_ARGUMENT],
[--recursive, -r, GetoptLong::NO_ARGUMENT],
[--help, -h, GetoptLong::NO_ARGUMENT])
opts.each {|opt,val|
case opt
when --days then days = val
when --verbose then verbose += 1
# when --recursive then recursive = true
else
usage
end
}
if days.to_i == 0
$stderr.puts illegal value given for days: #{days}
end
days = days.to_i
if ARGV.empty?
packages = IO.popen('grep-status -FStatus -sPackage -n install ok
installed').readlines
else
packages = ARGV
end
class Pathname
@@secondsPerDay = 60 * 60 * 24
def parentInArray(paths)
paths.any? { | p |
fnmatch(p)
}
end
def lastAccessed(t = Time.now)
((t - self.atime)/@@secondsPerDay).to_i
end
end
class Package
@@filesToIgnore = [
'/usr/lib/menu/*',
'/usr/share/applications/*',
'/usr/share/man/*',
'/usr/share/pixmaps/*',
'/usr/share/mime-info/*',
'/usr/lib/mime/packages/*',
'/usr/share/doc-base/*',
]
@@docDirs = [
'/usr/share/doc/*',
]
@@binaryDirs = [
'/lib/*',
'/usr/lib/*',
'/bin/*',
'/usr/bin/*',
]
def initialize(name)
@name = name
end
def getFiles
if not defined? @files
@files = IO.popen(grep-dctrl -FStatus ' installed' /var/lib/dpkg/status |
grep-dctrl -PX -n -s Package [EMAIL PROTECTED]).collect { | pkg |
IO.popen(dpkg --listfiles #{pkg}).collect { | fn |
fn.chomp!
if fn.empty?
false
else
p = Pathname.new(fn.chomp)
end
}.select { | p |
p (p.file? (! p.parentInArray(@@filesToIgnore)))
}
}.flatten
end
if @files.empty?
raise No regular files found (or package not installed)
end
@files
end
def docFiles
if not defined? @docFiles
@docFiles = getFiles.select { | p |
p.parentInArray(@@docDirs)
}.sort {|x,y| y.atime = x.atime }
end
@docFiles
end
def binaryFiles
if not defined? @binFiles
@binFiles = getFiles.select { | p |
p.parentInArray(@@binaryDirs)
}.sort {|x,y| y.atime = x.atime }
end
@binFiles
end
def lastDocAccess
if docFiles.empty?
raise No document files
else
docFiles[0].lastAccessed
end
end
def showlastDocumentAccess(number = 1)
if docFiles.empty?
raise No doc files
else
access_times = (0...([number, docFiles.size].min)).collect { | n |
#{docFiles[n]} was last accessed #{docFiles[n].lastAccessed} days ago
}
end
end
def lastBinaryAccess
if binaryFiles.empty?
raise No binary files
else
binaryFiles[0].lastAccessed
end
end
def showlastBinaryAccess(number = 1)
if binaryFiles.empty?
raise No binary files
else
access_times = (0...([number, binaryFiles.size].min)).collect { | n |
#{binaryFiles[n]} was last accessed #{binaryFiles[n].lastAccessed} days ago
}
end
end
def getWhatDeps
IO.popen(grep-status -n -s Package -FDepends -e [EMAIL PROTECTED]).readlines
end
end
packages.each { | pn |
pn.chomp!
next if pn.empty?
if verbose 0
puts === #{pn} ===
end
success = false
p = Package.new(pn)
binDays = 1
begin
binDays = p.lastBinaryAccess
if verbose 1
puts p.showlastBinaryAccess(10).collect { | s | + s }
end
success = true
rescue
if verbose 0
$stderr.puts $!
end
end
docDays = 1
begin
docDays = p.lastDocAccess
if verbose 1
puts p.showlastDocumentAccess(10).collect { | s | + s }
end
success = true
rescue
if verbose 0
$stderr.puts $!
end
end
if success
if [binDays, docDays].min days
puts Recommend #{pn} for removal
if recursive
puts p.getWhatDeps
end
else
if verbose 0
puts Keeping #{pn}
end
end
end
}
