Bug#669565: RFS: gammaray/1.1.0-1 [ITP] -- Tool for examining the internals of Qt application
On 14.08.2012 22:40, Jakub Adam wrote: Hi, Gammaray is now team-maintained by Debian KDE Extras Team and its git repository relocated to http://anonscm.debian.org/gitweb/?p=pkg-kde/kde-extras/gammaray.git Old repo in collab-maint is not available anymore. Great! I noticed some issues in the copyright file: - This one is missing: ./core/palettemodel.cpp: Copyright (C) 2010 Ariya Hidayat ariya.hida...@gmail.com - tools/ has been moved to core/tools/ - cmake/* is missing. Some of those files don't have a license header. It would be good to check with upstream under what license they are released. Felix -- 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/502cb790.7080...@debian.org
Re: Bug#685042: ITP: libpam-ssh -- Authenticate using SSH keys
Hello: On 16/08/12 11:29, Thomas Goirand wrote: On 08/16/2012 09:01 AM, Jerome Benoit wrote: Package: wnpp Severity: wishlist Owner: Jerome Benoitg62993...@rezozer.net * Package name: libpam-ssh Version : 1.97 Upstream Author : Akorty Rosenauer * URL : http://pam-ssh.sourceforge.net/ * License : BSD Programming Lang: C Description : Authenticate using SSH keys This PAM module provides single sign-on behavior for SSH. The user types an SSH passphrase when logging in and is authenticated if the passphrase successfully decrypts the user's SSH private key. In the PAM session phase, an ssh-agent process is started and keys are added. For the entire session, the user can SSH to other hosts that accept key authentication without typing any passwords. As much as I can see, the package is still in Debian (though removed from Wheezy). You shouldn't open an ITP for a package that is already in the archive. If your intention is to adopt the package, then you should follow the MIA process, have the package orphaned, then rename the orphaned bug as ITA (Intention To Adopt) adopt it by uploading new versions. And for that, there's no need for an ITP. The situation is ambiguous as I posted before in the debian-de...@lists.debian.org list: the package is not orphaned, was removed but it is still present. There is a void here, and it is why I asked on the list: it was suggested to make an ITP since it was removed. It appears that the Maintainer has retired from Debian. According to him, his Debian packages are orphaned, and he has no more access to his Debian account. Thanks for your intention to adopt this package, Cheers, Best wishes, Jerome Thomas Goirand (zigo) -- 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/502d002f.9060...@rezozer.net
Re: Bug#685042: ITP: libpam-ssh -- Authenticate using SSH keys
Hello: On 16/08/12 08:40, Neil Williams wrote: On Thu, 16 Aug 2012 03:01:33 +0200 Jerome Benoitg62993...@rezozer.net wrote: Package: wnpp Severity: wishlist Owner: Jerome Benoitg62993...@rezozer.net * Package name: libpam-ssh Version : 1.97 Upstream Author : Akorty Rosenauer * URL : http://pam-ssh.sourceforge.net/ * License : BSD Programming Lang: C Description : Authenticate using SSH keys This PAM module provides single sign-on behavior for SSH. The user types an SSH passphrase when logging in and is authenticated if the passphrase successfully decrypts the user's SSH private key. In the PAM session phase, an ssh-agent process is started and keys are added. For the entire session, the user can SSH to other hosts that accept key authentication without typing any passwords. Is this about using removable media to store the SSH private key to login to machines which only have the public key? NO ! That would be useful (but isn't that covered by existing PAM support?) Is this some form of hot-desking support? If not, why is this better than a user having a different password for login and for the SSH key? Why tie login to one of my SSH private keys? Let say that I used it to launch ssh-agent when I login (from console or desktop). The homepage doesn't make this clear, it sounds like the module just maps the user login via a graphical desktop manager to a particular SSH key the private key for which has to live on the system behind the login anyway. What's the point? I am agree that the descriptions on the homepage and within the Debian package are confusing: I will try to improve this part as well. Thanks, Jerome -- 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/502d02fa.8020...@rezozer.net
Re: Bug#685042: ITP: libpam-ssh -- Authenticate using SSH keys
On Thu, Aug 16, 2012 at 04:14:07PM +0200, Jerome BENOIT wrote: The situation is ambiguous as I posted before in the debian-de...@lists.debian.org list: the package is not orphaned, was removed but it is still present. There is no ambiguity. The package is present in unstable and thus is not removed in the sense that word is commonly used without qualifiers. (The proper way to describe what happened to the package is removed from testing - a release engineering action that doesn't imply any change in a package's maintainership.) There is a void here, and it is why I asked on the list: it was suggested to make an ITP since it was removed. An ITP is inappropriate so long as the package is present in unstable or experimental. It appears that the Maintainer has retired from Debian. In that case, the package likely is available for salvaging (that is, for taking over maintainership without going throug a period of formal ITA or O period). -- Antti-Juhani Kaijanaho, Jyväskylä, Finland http://antti-juhani.kaijanaho.fi/newblog/ http://www.flickr.com/photos/antti-juhani/ -- 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/20120816153138.gb2...@kukkavihko.kaijanaho.fi
Re: Bug#685042: ITP: libpam-ssh -- Authenticate using SSH keys
Hello: On 16/08/12 17:31, Antti-Juhani Kaijanaho wrote: On Thu, Aug 16, 2012 at 04:14:07PM +0200, Jerome BENOIT wrote: The situation is ambiguous as I posted before in the debian-de...@lists.debian.org list: the package is not orphaned, was removed but it is still present. There is no ambiguity. The package is present in unstable and thus is not removed in the sense that word is commonly used without qualifiers. (The proper way to describe what happened to the package is removed from testing - a release engineering action that doesn't imply any change in a package's maintainership.) There is a void here, and it is why I asked on the list: it was suggested to make an ITP since it was removed. An ITP is inappropriate so long as the package is present in unstable or experimental. According to its PTS ( http://packages.qa.debian.org/libp/libpam-ssh.html ): [2011-12-03] libpam-ssh REMOVED from testing (Britney) [2011-12-02] Removed 1.92-14 from unstable (Alexander Reichle-Schmehl) So I guess it must be considered as removed. It appears that the Maintainer has retired from Debian. In that case, the package likely is available for salvaging (that is, for taking over maintainership without going throug a period of formal ITA or O period). Best wishes, Jerome -- 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/502d1446.50...@rezozer.net
Re: Bug#685042: ITP: libpam-ssh -- Authenticate using SSH keys
On Thu, Aug 16, 2012 at 05:39:50PM +0200, Jerome BENOIT wrote: According to its PTS ( http://packages.qa.debian.org/libp/libpam-ssh.html ): [2011-12-03] libpam-ssh REMOVED from testing (Britney) [2011-12-02] Removed 1.92-14 from unstable (Alexander Reichle-Schmehl) So I guess it must be considered as removed. Yes, you are right. Sorry for my careless reading of that page. In any case, no ambiguity, it seems. I don't think a package's presence in stable or oldstable alone is a problem. -- Antti-Juhani Kaijanaho, Jyväskylä, Finland http://antti-juhani.kaijanaho.fi/newblog/ http://www.flickr.com/photos/antti-juhani/ -- 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/20120816154232.gd2...@kukkavihko.kaijanaho.fi
Re: Bug#685042: ITP: libpam-ssh -- Authenticate using SSH keys
Antti-Juhani Kaijanaho antti-juh...@kaijanaho.fi (16/08/2012): There is no ambiguity. The package is present in unstable and thus is not removed in the sense that word is commonly used without qualifiers. (The proper way to describe what happened to the package is removed from testing - a release engineering action that doesn't imply any change in a package's maintainership.) $ ssh release.debian.org dak ls libpam-ssh libpam-ssh |1.92-14 |stable | source, amd64, armel, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc $ rmadison libpam-ssh libpam-ssh | 1.92-14 | squeeze | source, amd64, armel, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc $ wget http://ftp-master.debian.org/removals-2011.txt -q -O - | grep libpam-ssh -B 10 -A 1 --- Reason --- ROM; unmaintained, somewhat obsolete -- Also closing bug(s): 381023 539727 610827 633152 Also closing WNPP bug(s): = = [Date: Fri, 02 Dec 2011 16:51:17 +] [ftpmaster: Alexander Reichle-Schmehl] Removed the following packages from unstable: libpam-ssh |1.92-14 | source libpam-ssh | 1.92-14+b1 | amd64, armel, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc Closed bugs: 650644 Mraw, KiBi. signature.asc Description: Digital signature
Re: Bug#685042: ITP: libpam-ssh -- Authenticate using SSH keys
On Thu, 16 Aug 2012, Antti-Juhani Kaijanaho wrote: On Thu, Aug 16, 2012 at 04:14:07PM +0200, Jerome BENOIT wrote: The situation is ambiguous as I posted before in the debian-de...@lists.debian.org list: the package is not orphaned, was removed but it is still present. There is no ambiguity. The package is present in unstable and thus is not removed in the sense that word is commonly used without qualifiers. (The proper way to describe what happened to the package is removed from testing - a release engineering action that doesn't imply any change in a package's maintainership.) What let you think this? rmadison libpam-ssh libpam-ssh | 1.92-14 | squeeze | source, amd64, armel, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc W: Archive maintenance is in progress; database inconsistencies are possible. [Date: Fri, 02 Dec 2011 16:51:17 +] [ftpmaster: Alexander Reichle-Schmehl] Removed the following packages from unstable: libpam-ssh |1.92-14 | source libpam-ssh | 1.92-14+b1 | amd64, armel, i386, ia64, kfreebsd-amd64, kfreebsd-i386, mips, mipsel, powerpc, s390, sparc Closed bugs: 650644 Alex -- 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/20120816154108.gc5...@snow-crash.org
Re: Bug#685042: ITP: libpam-ssh -- Authenticate using SSH keys
On Thu, Aug 16, 2012 at 05:41:08PM +0200, Alexander Wirt wrote: What let you think this? Carelessness in investigating (looked at http://packages.qa.debian.org/libp/libpam-ssh.html, noticed that the last news entry was removal from testing and did not read closely enough to notice the unstable removal notice below it - in retrospect, I should have expected such a pattern, as removals from testing are often preceded by removals from unstable). Sorry for the noise. (I do not need a personal CC, by the way. I am subscribed.) -- Antti-Juhani Kaijanaho, Jyväskylä, Finland http://antti-juhani.kaijanaho.fi/newblog/ http://www.flickr.com/photos/antti-juhani/ -- 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/20120816155600.ge2...@kukkavihko.kaijanaho.fi
Re: Bug#685042: ITP: libpam-ssh -- Authenticate using SSH keys
On 08/16/2012 11:42 PM, Antti-Juhani Kaijanaho wrote: On Thu, Aug 16, 2012 at 05:39:50PM +0200, Jerome BENOIT wrote: According to its PTS ( http://packages.qa.debian.org/libp/libpam-ssh.html ): [2011-12-03] libpam-ssh REMOVED from testing (Britney) [2011-12-02] Removed 1.92-14 from unstable (Alexander Reichle-Schmehl) So I guess it must be considered as removed. Yes, you are right. Sorry for my careless reading of that page. In any case, no ambiguity, it seems. I don't think a package's presence in stable or oldstable alone is a problem. On my side, I got fooled by reading too fast: http://packages.debian.org/search?keywords=libpam-sshsearchon=namessuite=allsection=all The package is in SID, but only on few arch. Which makes me wonder: WHY ? How does such things happen? Is this because such ports aren't part of official Debian anymore? Thomas -- 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/502d1aa1.1010...@goirand.fr
Re: logkeys in Debian
On 08/07/2012 08:48 AM, Bart Martens wrote: Hi Vedran, I suggest to remove logkeys 0.1.1a+svn20120529-2 (2012-08-06 23:55) from mentors. It might fix the FTBFS on mips (bug 679182), but it still does not help to get the bugs in wheezy fixed. I suggest to follow the approach we quoted above. Hello, I did you you asked for, and uploaded that version to: http://mentors.debian.net/package/logkeys But it doesn't work for me, logkeys uses 100% CPU and doesn't log anything, at least on Sid (someone please test). It would be sad if logkeys doesn't make it into wheezy due to an obvious gcc bug (#679182). Regards, Vedran attachment: vedran_furac.vcf
Re: logkeys in Debian
On Thu, Aug 16, 2012 at 06:48:24PM +0200, Vedran Furač wrote: http://mentors.debian.net/package/logkeys But it doesn't work for me, logkeys uses 100% CPU and doesn't log anything, at least on Sid (someone please test). I don't see an open bug about this problem uses 100% CPU. http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=logkeys Regards, Bart Martens -- 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/20120816173126.ga10...@master.debian.org
Bug#683184: RFS: suckless-tools/39-1 [ITA]
* Vasudev Kamath kamathvasu...@gmail.com, 2012-07-30, 21:56:
It doesn't look like it's suitable for wheezy, so please make it
s/unstable/experimental/.
Done! When it should be moved to unstable? After wheezy release?
Yes, after wheezy is released.
+-$ $(tabbed -d /tmp/tabbed.xid); urxvt -embed $(/tmp/tabbed.xid);
++$ $(tabbed \-d /tmp/tabbed.xid); urxvt \-embed $(/tmp/tabbed.xid);
If you're fixing this, please also fix the security hole (insecure use
of temporary files).
Done too
So it's now:
TMPFILE=$(mktemp \-\-tmpdir tabbedxid.XXX);$(tabbed \-d ${TMPFILE});urxvt
\-embed $(${TMPFILE})
which is certainly better from security perspective, but not necessarily
from usability one. I think the reason for storing xid in a file with
predictable name was that it allowed you to connect more than one urxvt
to the same tabbed. So I think that:
1) TMPFILE is a bad variable name for this purpose;
2) you could have saved one level of indirection by storing tabbed -d
output directly into the variable (rather than into temporary file);
3) perhaps it would make more sense to use a file somewhere in $HOME.
+ @cd /tmp
+ @tar -cvf - suckless-tools_$(CURRENT_VERSION) 2 /dev/null | gzip -9
../suckless-tools_$(CURRENT_VERSION).orig.tar.gz
+ @rm -rf /tmp/suckless-tools_$(CURRENT_VERSION)
This creates temporary files insecurely.
Fixed.
I see you did this:
get-orig-source: TMPDIR :=$(shell (mktemp --tmpdir -d suckless-tools.))
It looks like a nice hack, but... it will create a temporary directory
every time debian/rules is run (not only for the get-orig-source
target).
Instead of pushing new package to mentors I've pushed my changes to
collab-maint repository [1] Hope that is fine with you if not let me
know
[1] git.debian.org:/git/collab-maint/suckless-tools.git
That's okay.
--
Jakub Wilk
--
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/20120816184623.ga4...@jwilk.net
Processed (with 1 errors): retitle 684944
Processing commands for cont...@bugs.debian.org: retitle 684944 RFS: ecere-sdk/0.44.01-1 [ITP: #665332] - Ecere SDK Bug #684944 [sponsorship-requests] RFS: ecere/0.44.01-1 [ITP] -- SDK Changed Bug title to 'RFS: ecere-sdk/0.44.01-1 [ITP: #665332] - Ecere SDK' from 'RFS: ecere/0.44.01-1 [ITP] -- SDK' packaging for Debian thanks Stopping processing here. Please contact me if you need assistance. -- 684944: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=684944 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems -- 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/handler.s.c.134514790327561.transcr...@bugs.debian.org
dpkg-source aborting due to unexpected upstream changes when run inside pbuilder
Hi all, I'm trying to learn how to use pbuilder, but cannot manage to build a simple package. The pbuilder baze.tgz looks OK, it is something about dpkg-source and quilt patches that I cannot grasp. My steps are: 1. Download the source of my package: apt-get source liblcms2-2 It downloads the source, unpacks it and applies all patches to the unpacked source folder. I don't touch anything. 2. Make pbuilder rebuild it for me without any changes: sudo pbuilder build ./lcms*.dsc pbuilder extracts its baze.tgz, installs additional packages and necessary debs, then I see how it begins to build the package: Current status: 0 broken [-1]. - Finished parsing the build-deps I: Copying back the cached apt archive contents I: Copying source file I: copying [./lcms2_2.2+git20110628-2ubuntu3.dsc] I: copying [./lcms2_2.2+git20110628.orig.tar.gz] I: copying [./lcms2_2.2+git20110628-2ubuntu3.debian.tar.gz] I: Extracting source ... Then dpkg-source applies patches: dpkg-source: info: extracting lcms2 in lcms2-2.2+git20110628 dpkg-source: info: unpacking lcms2_2.2+git20110628.orig.tar.gz dpkg-source: info: unpacking lcms2_2.2+git20110628-2ubuntu3.debian.tar.gz dpkg-source: info: applying tificc.1 ... Then dpkg-buildsource builds everything: I: Running cd tmp/buildd/*/ env PATH=/usr/lib/ccache:/usr/sbin:/usr/bin:/sbin:/bin dpkg-buildpackage -us -uc -rfakeroot ... And then it all ends with a message claiming that dpkg-source detected changes to upstream due to the patches it applied itself earlier. dpkg-source -b lcms2-2.2+git20110628 dpkg-source: info: using source format `3.0 (quilt)' dpkg-source: warning: Version number suggests Ubuntu changes, but Maintainer: does not have Ubuntu address dpkg-source: warning: Version number suggests Ubuntu changes, but there is no XSBC-Original-Maintainer field dpkg-source: info: building lcms2 using existing ./lcms2_2.2+git20110628.orig.tar.gz dpkg-source: warning: newly created empty file 'config.status' will not be represented in diff dpkg-source: info: local changes detected, the modified files are: lcms2-2.2+git20110628/Makefile patched files skipped dpkg-source: info: you can integrate the local changes with dpkg-source --commit dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/lcms2_2.2+git20110628-2ubuntu3.diff.nAswlJ dpkg-buildpackage: error: dpkg-source -b lcms2-2.2+git20110628 gave error exit status 2 E: Failed autobuilding of package Why dpkg-source thinks the patches are a problem and shouldn't be applied? The environment is Ubuntu 12.04, but it shouldn't matter. Complete log file is attached. -Alex pbuilder-lcms2.log Description: Binary data
Re: dpkg-source aborting due to unexpected upstream changes when run inside pbuilder
On Thu, Aug 16, 2012 at 06:21:39PM -0400, Alex Korobkin wrote: 1. Download the source of my package: apt-get source liblcms2-2 Note that we don't have Ubuntu precies as our default repo so the command doesn't do the same as for you. You mean dget http://archive.ubuntu.com/ubuntu/pool/main/l/lcms2/lcms2_2.2+git20110628-2ubuntu3.dsc This is important because the sid version doesn't have this problem. And then it all ends with a message claiming that dpkg-source detected changes to upstream due to the patches it applied itself earlier. Wrong. The changes are caused by the clean target and I get the same message just by running dpkg-buildpackage in the unpacked source (even *before* building). dpkg-source -b lcms2-2.2+git20110628 dpkg-source: info: using source format `3.0 (quilt)' dpkg-source: warning: Version number suggests Ubuntu changes, but Maintainer: does not have Ubuntu address dpkg-source: warning: Version number suggests Ubuntu changes, but there is no XSBC-Original-Maintainer field dpkg-source: info: building lcms2 using existing ./lcms2_2.2+git20110628.orig.tar.gz dpkg-source: warning: newly created empty file 'config.status' will not be represented in diff dpkg-source: info: local changes detected, the modified files are: lcms2-2.2+git20110628/Makefile patched files skipped dpkg-source: info: you can integrate the local changes with dpkg-source --commit dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/lcms2_2.2+git20110628-2ubuntu3.diff.nAswlJ dpkg-buildpackage: error: dpkg-source -b lcms2-2.2+git20110628 gave error exit status 2 E: Failed autobuilding of package Why dpkg-source thinks the patches are a problem and shouldn't be applied? It never said the patches are problem. The problem is Makefile files that are regenerated by configure called in the clean target. That these files are patched by debian/patches/debian-changes-* is another problem, caused by this one. This problem was reported in September as #643177 and fixed in the Debian package version 2.2+git20110628-2.1 in March. -- WBR, wRAR signature.asc Description: Digital signature
Re: dpkg-source aborting due to unexpected upstream changes when run inside pbuilder
On 16 August 2012 18:38, Andrey Rahmatullin w...@wrar.name wrote: On Thu, Aug 16, 2012 at 06:21:39PM -0400, Alex Korobkin wrote: 1. Download the source of my package: apt-get source liblcms2-2 Note that we don't have Ubuntu precies as our default repo so the command doesn't do the same as for you. You mean dget http://archive.ubuntu.com/ubuntu/pool/main/l/lcms2/lcms2_2.2+git20110628-2ubuntu3.dsc This is important because the sid version doesn't have this problem. And then it all ends with a message claiming that dpkg-source detected changes to upstream due to the patches it applied itself earlier. Wrong. The changes are caused by the clean target and I get the same message just by running dpkg-buildpackage in the unpacked source (even *before* building). dpkg-source -b lcms2-2.2+git20110628 dpkg-source: info: using source format `3.0 (quilt)' dpkg-source: warning: Version number suggests Ubuntu changes, but Maintainer: does not have Ubuntu address dpkg-source: warning: Version number suggests Ubuntu changes, but there is no XSBC-Original-Maintainer field dpkg-source: info: building lcms2 using existing ./lcms2_2.2+git20110628.orig.tar.gz dpkg-source: warning: newly created empty file 'config.status' will not be represented in diff dpkg-source: info: local changes detected, the modified files are: lcms2-2.2+git20110628/Makefile patched files skipped dpkg-source: info: you can integrate the local changes with dpkg-source --commit dpkg-source: error: aborting due to unexpected upstream changes, see /tmp/lcms2_2.2+git20110628-2ubuntu3.diff.nAswlJ dpkg-buildpackage: error: dpkg-source -b lcms2-2.2+git20110628 gave error exit status 2 E: Failed autobuilding of package Why dpkg-source thinks the patches are a problem and shouldn't be applied? It never said the patches are problem. The problem is Makefile files that are regenerated by configure called in the clean target. Looks like I chose a wrong package to try out. Thanks for your prompt reply, Andrey. -Alex -- 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/ca+3rnfiyqiqqf5ddvdt9k2zqmy49eqfy86ksphaztyn2pgn...@mail.gmail.com
Bug#683500: marked as done (RFS: freefoam/0.1.0+dfsg-1 [RC])
Your message dated Fri, 17 Aug 2012 04:20:08 + with message-id e1t2e2a-00011e...@quantz.debian.org and subject line closing RFS: freefoam/0.1.0+dfsg-1 [RC] has caused the Debian Bug report #683500, regarding RFS: freefoam/0.1.0+dfsg-1 [RC] to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 683500: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=683500 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems ---BeginMessage--- Package: sponsorship-requests Severity: normal X-Debbugs-CC: debian-scie...@lists.debian.org Dear mentors, I am looking for a sponsor for my package freefoam * Package name: freefoam Version : 0.1.0+dfsg-1 Upstream Author : Michael Wild them...@users.sourceforge.net * URL : http://freefoam.sourceforge.net * License : GPL-3+ (+GFDL-NIV-1.2, permissive, PSF-2, LGPL-2.1+, BSD-4-clause, GPL-2) Section : science It builds those binary packages: freefoam - programs for Computational Fluid Dynamics (CFD) freefoam-dev-doc - software for Computational Fluid Dynamics - developers documentation freefoam-user-doc - software for Computational Fluid Dynamics - user documentation libfreefoam1 - libraries for Computational Fluid Dynamics (CFD) libfreefoam-dev - libraries for Computational Fluid Dynamics (CFD) - development files To access further information about this package, please visit the following URL: http://mentors.debian.net/package/freefoam Alternatively, one can download the package with dget using this command: dget -x http://mentors.debian.net/debian/pool/main/f/freefoam/freefoam_0.1.0+dfsg-1.dsc More information about FreeFOAM can be obtained from http://freefoam.sourceforge.net. Changes since the last upload: * [92ca47f] New upstream version 0.1.0+dfsg (Closes: #682928) * [e07e2f1] Removed d/p/copyright.diff. This information belongs into debian/copyright and the CHEMKIN ckinterp.f file has been removed by the 0.1.0+dfsg import. * [300a38d] Remove DFSG-deleted directories from the build system - Added d/p/remove-dfsg-deleted-directories-from-build-system.diff - Removed d/p/userd.diff. * [5ff801c] Update documentation and completion scripts for DFSG-cleaning - Added d/p/update-for-removed-apps.diff * [d813ede] Added missing build-deps: graphviz (Closes: #682940) * [6a280d2] Fix FTBFS with GCC-4.7 because of non-qualified template-dependent names - Added d/p/missing-qualifications-of-template-dependent-names.diff - Removed the -fpermissive flag from CXXFLAGS. (Closes: #682927) * [a669cc7] Fix bogus lintian override * [a414aa0] Make debian/copyright complete, cleanup (Closes: #682942) * [7f41940] Fix /usr/share/freefoam/DoxyDocIndex installation, fix name mangling - Install it into freefoam-dev-doc package instead of libfreefoam-dev - Add d/p/doxygen-generated-file-names-breakage.diff to fix the name mangling issue - Add d/p/fix-api-doc-location.diff to fix the API documentation location in DoxyDocIndex. (Closes: #682934) * [c14eda9] Fix error in freefoam-log when operating on truncated log files - Add d/p/handle-truncated-logs-in-freefoam-log.diff (Closes: #682931) * [f35bb9c] Fix freefoam-log to create logs/ directory in the case directory, not $PWD - Added d/p/correct-output-directory-for-freefoam-log.diff (Closes: #682932) * [6de0d22] Rename the libfreefoam package to libfreefoam1 - This is to be compliant with policy 8.2 - Also rename the plugins0 directory to plugins1 to honour the same policy (Closes: 682953) * [d2767a3] Install *.so links into the libfreefoam-dev package, not libfreefoam1 (Closes: #682943) * [a307676] Add Michael Wild to the uploaders * [199ae68] Escape meta-characters before creating doc/Doxygen/filter.py - Added d/p/escape-meta-chars-for-doxygen-filter.diff * [6f94315] Fix installation dirs for template files (Closes: #683175) * [b5cc1ea] Install foamLog.db into the freefoam binary package (Closes: #683176) * [149cf7e] Install Doxygen CSS and image resources, update FoamHeader.html - In d/freefoam-dev-doc.install install the css/ and img/ folders - Update doc/Doxygen/FoamHeader.hmtl to Doxygen version 1.8.1.2 (Closes: #683369) Gerber van der Graaf, who originally packaged the freefoam-0.1.0-1 package asked me to add myself directly to the uploaders and asking for sponsorship instead of going through him. I think with the modifications I made I fixed some important bugs, some of
