Re: RFS: gtklp (updated package)
On Tue, 2009-08-25 at 22:48 +0800, Zak B. Elep wrote: > Note that I'm not closing the door on separating patches as files > altogether; I may go back to simple-patchsys style when I have more than > a handful of patches to keep. And go back, I did. ;) I've updated my gtklp to 1.2.7-2, here's the changelog: gtklp (1.2.7-2) unstable; urgency=low * Use TopGit and Quilt to manage patches * Re-add debian/patches, autogenerated from git branches * debian/rules: call autogen.sh after applying patches dget http://mentors.debian.net/debian/pool/main/g/gtklp/gtklp_1.2.7-2.dsc -- Zak B. Elep -- 1486 7957 454D E529 E4F1 F75E 5787 B1FD FA53 851D I like the idea of 256 bits, though: 32 for the (Unicode) character leaves room for 224 Bucky bits, which ought to be enough for anyone. -- Roland Hutchinson, in alt.folklore.computers signature.asc Description: This is a digitally signed message part
Re: Need help for xiterm+thai on s390 compilation failed
On Fri, Aug 28, 2009 at 2:17 AM, Neutron Soutmun wrote: > https://buildd.debian.org/fetch.cgi?&pkg=xiterm%2Bthai&ver=1.09-2&arch=s390&stamp=1249926993&file=log > > The issue is the link fail to the function getutmpx(), I'm not sure about the > different definition about this function on this architecture (s390) which > I couldn't do any emulator for compilation testing. Given that the symbols for the s390 libc6 deb contains getutmpx[1], I suggest that the issue was a temporarily broken eglibc on that platform (and I seem to remember something about that on the -release or -devel lists recently). Please mail s...@buildd.debian.org to get them to retry the package. More info about this sort of thing can be found in the developers reference. > To whom concerns for this architecture, please advices me, Thanks in advance. For porting issues, in general, please consult the relevant porting list[2]. 1. http://qa.debian.org/cgi-bin/mole/symbols/.dump/symbols?key=DEBIAN/pool/main/e/eglibc/libc6_2.9-25_s390.deb 2. http://lists.debian.org/ports.html -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: burn 0.4.3-2.2 (Lenny security bug fixes)
Felipe Sateler writes: > I believe packages with updates to stable debian releases are versioned > -+lenny1 or something like that. Felipe Sateler writes: > BTW, I know this is not a hard requirement, but it is to easily detect > stable updates. Okay. Given that the release team has approved a specific set of changes that includes the package release version string, would I need to seek approval again when changing that string? -- \ “Following fashion and the status quo is easy. Thinking about | `\your users' lives and creating something practical is much | _o__)harder.” —Ryan Singer, 2008-07-09 | Ben Finney -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: opendchub (updated package)
On Thu, 2009-08-27 at 18:38 +0200, Patrick Matthäi wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Zak B. Elep schrieb: > > On Thu, 2009-08-27 at 20:48 +0800, Zak B. Elep wrote: > >> On Thu, 2009-08-27 at 14:22 +0200, Patrick Matthäi wrote: > >>> Okay, please report it against CDBS. > >> I have, waiting for the ticket. > > > > Its Debian Bug #543916. > > > > In the meantime, I've uploaded 0.8.0-4 building with the workaround > > (declaring DEB_ACLOCAL_ARGS at debian/rules) to mentors. > > > > dget > > http://mentors.debian.net/debian/pool/main/o/opendchub/opendchub_0.8.0-4.dsc > > > > Thanks for your work, I will upload it now. Yay! Thank you very much for the upload! -- Zak B. Elep -- 1486 7957 454D E529 E4F1 F75E 5787 B1FD FA53 851D I like the idea of 256 bits, though: 32 for the (Unicode) character leaves room for 224 Bucky bits, which ought to be enough for anyone. -- Roland Hutchinson, in alt.folklore.computers signature.asc Description: This is a digitally signed message part
Re: how to upload a debian binary for lyx
On Thu, Aug 27, 2009 at 12:55:40PM +0200, Alexander Reichle-Schmehl wrote: Hi, > There's a team maintaining the lyx package. You can reach it by e-mail > via Debian LyX Maintainers . > Please ask them if you can help them / join their team. Yes you can. ;) We maintain a wiki page http://wiki.debian.org/PkgLyx listing the 'bigger' issue that should be worked out over time and there is still the Debian BTS to find something to work on. I'm currently lacking some time to dedicate to the not so easy to solve bugs. One that comes to mind, that would be a candidate for some love, is #531992. It's not a LyX issue but someone has to find out where to forward it. > * Jonathan Wiltshire [090827 12:43]: > > You want the debian-mentors list. Setting Mail-Followup-To and keeping the > > full text below. Please upload your package somewhere for the mentors to > > review, and drop the other lists when you reply. Not that clever for a package that seems to be actively maintained. At least we're not years behind the last upstream release and the changelog clearly shows recent actions from at least one maintainer. > > On Thu, Aug 27, 2009 at 11:24:47AM +0100, belahcene wrote: > > > Hi, > > > > > > I generate a debian package for the more recent lyx (1.6.4), I want > > > to share it, how and where to upload it. > > > > > > The file is generated for debian lenny (5.0) and can normally used > > > on recent ubuntu . What makes me courious is where I as one of the maintainer and we as team failed to comunicate so that one person I've never heard of before feels motivated to package a new upstream release without writing a mail to the maintainers first. Taking into account that Juergen (the upstream release manager) prepared the release on Sunday and announced it to the world on Monday we're not lacking this far behind with an upload on Thursday the same week. And the commit mails on the team mailinglist are from Tuesday evening. So it should've been obvious that there is someone working on packaging the new release. So I'm wondering now where we can improve our comunication so that nobody feels the need to waste some energy with doublicating work? Or maybe this is afterall just a gross missunderstanding of how packages are released with Debian/stable? I've to admit that some backports would be nice but last time I tried I had no success to find a sponsor for a bpo upload. I'll promise to work on one again when I'm through NM. Cheers, Sven -- They're the cowards We are rebels We got the power to fight the devil [ AIV - We are rebels ] -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: logiweb
Hi Klaus! 2009/8/27 Klaus Grue : > > I am looking for a sponsor for my package "logiweb". > I will take a look at the package. Cheers, -- Jens Peter Secher. _DD6A 05B0 174E BFB2 D4D9 B52E 0EE5 978A FE63 E8A1 jpsecher gmail com_. A. Because it breaks the logical sequence of discussion. Q. Why is top posting bad? -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Need help for xiterm+thai on s390 compilation failed
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 https://buildd.debian.org/fetch.cgi?&pkg=xiterm%2Bthai&ver=1.09-2&arch=s390&stamp=1249926993&file=log The issue is the link fail to the function getutmpx(), I'm not sure about the different definition about this function on this architecture (s390) which I couldn't do any emulator for compilation testing. The testing migration of my package is blocked for 27 days old. To whom concerns for this architecture, please advices me, Thanks in advance. Best regards, Neutron Soutmun -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkqWzZ0ACgkQ1k7Ar9TO/TfDQgCgi6uODohJ4Vo0ZpmcJ7/7iywb kaQAn1NoZqkrZHgP4Jx5jQWsyM+ZMW5R =KByM -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: burn 0.4.3-2.2 (Lenny security bug fixes)
Felipe Sateler wrote: > Ben Finney wrote: > >> Howdy mentors, >> >> I am looking for a sponsor for the new release 0.4.3-2.2 of my package >> ‘burn’ in Lenny. > > I believe packages with updates to stable debian releases are versioned > -+lenny1 or something like that. BTW, I know this is not a hard requirement, but it is to easily detect stable updates. -- Felipe Sateler -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: burn 0.4.3-2.2 (Lenny security bug fixes)
Ben Finney wrote: > Howdy mentors, > > I am looking for a sponsor for the new release 0.4.3-2.2 of my package > ‘burn’ in Lenny. I believe packages with updates to stable debian releases are versioned -+lenny1 or something like that. -- Felipe Sateler -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: opendchub (updated package)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zak B. Elep schrieb: > On Thu, 2009-08-27 at 20:48 +0800, Zak B. Elep wrote: >> On Thu, 2009-08-27 at 14:22 +0200, Patrick Matthäi wrote: >>> Okay, please report it against CDBS. >> I have, waiting for the ticket. > > Its Debian Bug #543916. > > In the meantime, I've uploaded 0.8.0-4 building with the workaround > (declaring DEB_ACLOCAL_ARGS at debian/rules) to mentors. > > dget > http://mentors.debian.net/debian/pool/main/o/opendchub/opendchub_0.8.0-4.dsc > Thanks for your work, I will upload it now. - -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer E-Mail: pmatth...@debian.org patr...@linux-dev.org Comment: Always if we think we are right, we were maybe wrong. */ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkqWtpQACgkQ2XA5inpabMegXwCgoxswZjJbZcjnNVnRmn/CUBoh 1xIAnR9nPT1oP5GYCT9a92i+vEA7s6fR =lBFQ -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: ttt (updated package)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tony Palma schrieb: > Dear mentors, > > I am looking for a sponsor for the new version 1.7-4 > of my package "ttt". > > It builds these binary packages: > ttt- A standalone program for local traffic-monitoring > tttprobe - A probe to collect traffic-data and send it to a viewer > tttview- A graphical viewer for remote captured traffic-data > > The package appears to be lintian clean. > > The upload would fix these bugs: 262758, 294377, 439448, 451138, 472602 > > The package can be found on mentors.debian.net: > - URL: http://mentors.debian.net/debian/pool/main/t/ttt > - Source repository: deb-src http://mentors.debian.net/debian unstable main > contrib non-free > - dget http://mentors.debian.net/debian/pool/main/t/ttt/ttt_1.7-4.dsc > > I would be glad if someone uploaded this package for me. Hello, there are many old and new direct changes in source without a patchsystem. Could you please fix them and split them up in debian/patches sets? Also it would be nice to have it working with tcl8.5. - -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer E-Mail: pmatth...@debian.org patr...@linux-dev.org Comment: Always if we think we are right, we were maybe wrong. */ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkqWsmwACgkQ2XA5inpabMcrfQCghZIPiqq0h74LCEcT/A4xkP7q W4wAn1UfaXKeIcQB6G2dd0APzgEtY8zv =CFCY -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
RFS: ttt (updated package)
Dear mentors, I am looking for a sponsor for the new version 1.7-4 of my package "ttt". It builds these binary packages: ttt- A standalone program for local traffic-monitoring tttprobe - A probe to collect traffic-data and send it to a viewer tttview- A graphical viewer for remote captured traffic-data The package appears to be lintian clean. The upload would fix these bugs: 262758, 294377, 439448, 451138, 472602 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/t/ttt - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/t/ttt/ttt_1.7-4.dsc I would be glad if someone uploaded this package for me. Kind regards Tony Palma -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: opendchub (updated package)
On Thu, 2009-08-27 at 20:48 +0800, Zak B. Elep wrote: > On Thu, 2009-08-27 at 14:22 +0200, Patrick Matthäi wrote: > > Okay, please report it against CDBS. > > I have, waiting for the ticket. Its Debian Bug #543916. In the meantime, I've uploaded 0.8.0-4 building with the workaround (declaring DEB_ACLOCAL_ARGS at debian/rules) to mentors. dget http://mentors.debian.net/debian/pool/main/o/opendchub/opendchub_0.8.0-4.dsc -- Zak B. Elep -- 1486 7957 454D E529 E4F1 F75E 5787 B1FD FA53 851D I like the idea of 256 bits, though: 32 for the (Unicode) character leaves room for 224 Bucky bits, which ought to be enough for anyone. -- Roland Hutchinson, in alt.folklore.computers signature.asc Description: This is a digitally signed message part
Re: RFS: opendchub (updated package)
В Thu, 27 Aug 2009 11:52:43 +0300, George Danchev написа: > But those diffs are applied in a combined fashion to the upstream source > (not very helpful for people actually interested to understand the > code), while they might be extremely interested to understand how many > *logical* changes have been applied, what are the reasons behind such a > deviation from the upstream, hence they would need to find out and dig > into your own VCS repo which is not so tightly associated with the bits > Debian actually and officially releases. I agree, and there is yet another very important use case for separating patches: inter-distro patch hunting. When I look at my packages at Fedora and Gentoo, I really like that all changes to the upstream source are in the form of "descriptive-name.patch", "another-descriptive-name.patch". I don't care much about the .spec of .ebuild files, but I care about patches. It is very easy to read and grab them, and they're self-contained, often directly usable for the Debian package. Imagine the inconvenience for the Fedora/Gentoo/whatever maintainers who look at one giant .diff.gz with scattered patches and tons of uninteresting and mostly useless (for them) Debian-specific files. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: opendchub (updated package)
On Thu, 2009-08-27 at 14:22 +0200, Patrick Matthäi wrote: > Zak B. Elep schrieb: > > Hmm, I built that package earlier today and it was fine (both in and out > > cowbuilder.) I noticed a new CDBS version up just now and upgraded, and > > now I get the same result as above, confirming the FTBFS. What's more, > > I got the same result with my updating of gtklp to topgit/quilt. > > Previous versions do not seem to be affected, however. > > > > It appears that the new CDBS broke something. Tracing, the offending > > line in /usr/share/cdbs/1/class/autotools-files.mk is: > > > > DEB_ACLOCAL_ARGS ?= $(if $(wildcard $(DEB_SRCDIR)/m4)),-I m4) the relevant /usr/share/doc/cdbs/changelog.gz entry: * Simplify autotools-files.mk and make m4 dir configurable through new variable DEB_ACLOCAL_ARGS. Fix copyright of that file. Closes: bug#537497, thanks to Robert Millan. > > I have not removed anything in my debian/rules since the new version, on > > additions to use patchsys-quilt.mk and tg2quilt.mk Apparently the solution is declaring DEB_ACLOCAL_ARGS in my debian/rules, but the way the line was defined above in autotools-files.mk seems broken. > Okay, please report it against CDBS. I have, waiting for the ticket. -- Zak B. Elep -- 1486 7957 454D E529 E4F1 F75E 5787 B1FD FA53 851D I like the idea of 256 bits, though: 32 for the (Unicode) character leaves room for 224 Bucky bits, which ought to be enough for anyone. -- Roland Hutchinson, in alt.folklore.computers signature.asc Description: This is a digitally signed message part
Re: RFS: opendchub (updated package)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zak B. Elep schrieb: > On Thu, 2009-08-27 at 13:46 +0200, Patrick Matthäi wrote: >> Your build ftbfs: >> /usr/share/cdbs/1/class/autotools-files.mk:49: *** insufficient number >> of arguments (1) to function `if'. Stop. >> dpkg-buildpackage: error: debian/rules build gave error exit status 2 >> E: Failed autobuilding of package >> I: unmounting dev/pts filesystem >> I: unmounting proc filesystem >> I: cleaning the build env >> I: removing directory /var/cache/pbuilder/build//9552 and its subdirectories > > Hmm, I built that package earlier today and it was fine (both in and out > cowbuilder.) I noticed a new CDBS version up just now and upgraded, and > now I get the same result as above, confirming the FTBFS. What's more, > I got the same result with my updating of gtklp to topgit/quilt. > Previous versions do not seem to be affected, however. > > It appears that the new CDBS broke something. Tracing, the offending > line in /usr/share/cdbs/1/class/autotools-files.mk is: > > DEB_ACLOCAL_ARGS ?= $(if $(wildcard $(DEB_SRCDIR)/m4)),-I m4) > > I have not removed anything in my debian/rules since the new version, on > additions to use patchsys-quilt.mk and tg2quilt.mk > Okay, please report it against CDBS. - -- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi GNU/Linux Debian Developer E-Mail: pmatth...@debian.org patr...@linux-dev.org Comment: Always if we think we are right, we were maybe wrong. */ -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkqWemwACgkQ2XA5inpabMdl8QCfbMTEDZl48q5j0lWa82XmDFpa j7YAoIFWbg9e58H9MrBiDEMsMkrSKoeZ =uabp -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: RFS: opendchub (updated package)
On Thu, 2009-08-27 at 13:46 +0200, Patrick Matthäi wrote: > Your build ftbfs: > /usr/share/cdbs/1/class/autotools-files.mk:49: *** insufficient number > of arguments (1) to function `if'. Stop. > dpkg-buildpackage: error: debian/rules build gave error exit status 2 > E: Failed autobuilding of package > I: unmounting dev/pts filesystem > I: unmounting proc filesystem > I: cleaning the build env > I: removing directory /var/cache/pbuilder/build//9552 and its subdirectories Hmm, I built that package earlier today and it was fine (both in and out cowbuilder.) I noticed a new CDBS version up just now and upgraded, and now I get the same result as above, confirming the FTBFS. What's more, I got the same result with my updating of gtklp to topgit/quilt. Previous versions do not seem to be affected, however. It appears that the new CDBS broke something. Tracing, the offending line in /usr/share/cdbs/1/class/autotools-files.mk is: DEB_ACLOCAL_ARGS ?= $(if $(wildcard $(DEB_SRCDIR)/m4)),-I m4) I have not removed anything in my debian/rules since the new version, on additions to use patchsys-quilt.mk and tg2quilt.mk -- Zak B. Elep -- 1486 7957 454D E529 E4F1 F75E 5787 B1FD FA53 851D I like the idea of 256 bits, though: 32 for the (Unicode) character leaves room for 224 Bucky bits, which ought to be enough for anyone. -- Roland Hutchinson, in alt.folklore.computers signature.asc Description: This is a digitally signed message part
Re: RFS: opendchub (updated package)
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zak B. Elep schrieb: > On Thu, 2009-08-27 at 08:36 +0800, Zak B. Elep wrote: >> Thanks, all in all, that was a better take on why separate patching >> should be done. I'll take a look at topgit (and quilt, too) and will >> probably rebuild the package. > > OK, I've updated my package, here's 0.8.0-3's changelog: > > opendchub (0.8.0-3) unstable; urgency=low > > * Use TopGit and Quilt to manage patches > * Re-add debian/patches, with diffs autogenerated from git branches > * Add debian/README.source describing the package build > > And here's the diffstat: > > NEWS | 20 > README.Debian| 37 +++ > README.source| 34 ++ > changelog| 151 > +++ > compat |1 > config.default | 62 > control | 41 > copyright| 33 ++ > docs |2 > init | 58 +++ > manpages |1 > motd.default |3 > opendchub.1 | 71 ++ > patches/bugs/495063.diff | 58 +++ > patches/fixes/avoid-buffer-overflow.diff | 29 + > patches/series |2 > postinst | 85 + > postrm | 20 > rules| 30 ++ > watch|4 > 20 files changed, 742 insertions(+) > > dget > http://mentors.debian.net/debian/pool/main/o/opendchub/opendchub_0.8.0-3.dsc > Your build ftbfs: make[1]: Entering directory `/tmp/buildd/opendchub-0.8.0' make[1]: *** No rule to make target `distclean'. make[1]: Leaving directory `/tmp/buildd/opendchub-0.8.0' make: [makefile-clean] Error 2 (ignored) rm -f debian/stamp-makefile-build for i in ./config.guess ./config.sub ; do \ if test -e $i.cdbs-orig ; then \ mv $i.cdbs-orig $i ; \ fi ; \ done dh_clean /usr/bin/make -f debian/rules reverse-config make[1]: Entering directory `/tmp/buildd/opendchub-0.8.0' for i in ./config.guess ./config.sub ; do \ if test -e $i.cdbs-orig ; then \ mv $i.cdbs-orig $i ; \ fi ; \ done make[1]: Leaving directory `/tmp/buildd/opendchub-0.8.0' if [ -d "." ]; then \ cd . && QUILT_PATCHES=/tmp/buildd/opendchub-0.8.0/debian/patches quilt --quiltrc /dev/null pop -a -R || test $? = 2 ; \ fi No patch removed rm -rf ./.pc rm -f debian/stamp-patch* rm -f debian/stamp-autotools-files rm -f Makefile.in config.h.in configure src/Makefile.in dpkg-source -b opendchub-0.8.0 dpkg-source: info: using source format `1.0' dpkg-source: info: building opendchub using existing opendchub_0.8.0.orig.tar.gz dpkg-source: info: building opendchub in opendchub_0.8.0-3.diff.gz dpkg-source: warning: ignoring deletion of file Makefile.in dpkg-source: warning: ignoring deletion of file config.h.in dpkg-source: warning: ignoring deletion of file ChangeLog~ dpkg-source: warning: ignoring deletion of file configure dpkg-source: warning: ignoring deletion of file src/Makefile.in dpkg-source: info: building opendchub in opendchub_0.8.0-3.dsc debian/rules build test -x debian/rules mkdir -p "." /usr/bin/make -f debian/rules reverse-config make[1]: Entering directory `/tmp/buildd/opendchub-0.8.0' for i in ./config.guess ./config.sub ; do \ if test -e $i.cdbs-orig ; then \ mv $i.cdbs-orig $i ; \ fi ; \ done make[1]: Leaving directory `/tmp/buildd/opendchub-0.8.0' cd . && QUILT_PATCHES=/tmp/buildd/opendchub-0.8.0/debian/patches quilt - --quiltrc /dev/null push -a || test $? = 2 Applying patch bugs/495063.diff patching file src/perl_utils.c Applying patch fixes/avoid-buffer-overflow.diff patching file src/commands.c Now at patch fixes/avoid-buffer-overflow.diff touch debian/stamp-patched /usr/bin/make -f debian/rules update-config make[1]: Entering directory `/tmp/buildd/opendchub-0.8.0' if test -e /usr/share/misc/config.guess ; then \ for i in ./config.guess ; do \ if ! test -e $i.cdbs-orig ; then \ mv $i $i.cdbs-orig ; \ cp --remove-destination /usr/share/misc/config.guess $i ; \ fi ; \ done ; \ fi if test -e /usr/share/misc/config.sub ; then \ for i in ./config.sub ; do \ if ! test -e $i.cdbs-or
Re: how to upload a debian binary for lyx
[ Keeping full quote for added Cc: ] [ Keeping you in copy, since I assume to don't read the mentors list ] Hi Bela! There's a team maintaining the lyx package. You can reach it by e-mail via Debian LyX Maintainers . Please ask them if you can help them / join their team. Best Regards, Alexander * Jonathan Wiltshire [090827 12:43]: > You want the debian-mentors list. Setting Mail-Followup-To and keeping the > full text below. Please upload your package somewhere for the mentors to > review, and drop the other lists when you reply. > > On Thu, Aug 27, 2009 at 11:24:47AM +0100, belahcene wrote: > > Hi, > > > > I generate a debian package for the more recent lyx (1.6.4), I want > > to share it, how and where to upload it. > > > > The file is generated for debian lenny (5.0) and can normally used > > on recent ubuntu . > > > > > > I am not a guru for creating debian package, so I need feed back. > > Thanks for testing and help > > > > best regards > > > > bela signature.asc Description: Digital signature
Re: Bug#543741: ettercap: should this package be orphaned?
I mean taking required action when I refer to close bugs. 2009/8/27 Sandro Tosi > On Thu, Aug 27, 2009 at 11:25, Murat Demirten wrote: > > I'm planning to close all bugs related to ettercap. Ettercap authors > don't > > work on this project anymore > > Why would you close bugs (I suppose Debian ones) if they are still valid? > > > but it is good to have this package at least a few years more, it runs > very > > well on most scenario. > > in particular if you plan to leave the package in Debian. > > Regards, > -- > Sandro Tosi (aka morph, morpheus, matrixhasu) > My website: http://matrixhasu.altervista.org/ > Me at Debian: http://wiki.debian.org/SandroTosi >
Re: Bug#543843: gqview -- simple image viewer using GTK+
also sprach Michal Čihař [2009.08.27.1224 +0200]: > Please note that there is geeqie, which took gqview code and now > provides active upstream for it. There is also pending patch for > geeqie package to provide gqview, which we will integrate once geeqie > will get out of beta phase. And then it will be time to drop gqview > package. Much appreciated! I retract my offer and would also like to see gqview removed as soon as the patch is out. Is there any reason why the patch has to wait for the beta phase to complete? [consider removing debian-mentors from CC] Also, I am not entirely sure there's a need for Provides, given that only two packages suggest gqview. Howver, being able to invoke geeqie as gqview (finger memory!) would be nice, ideally along with a deprecation warning to retrain those fingers. I am sure you know what you are doing and will just retreat to my box. Thanks for the note. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems perl -e 'print "The earth is a disk!\n" if ( "a" == "b" );' (dedicated to nori) digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: how to upload a debian binary for lyx
You want the debian-mentors list. Setting Mail-Followup-To and keeping the full text below. Please upload your package somewhere for the mentors to review, and drop the other lists when you reply. On Thu, Aug 27, 2009 at 11:24:47AM +0100, belahcene wrote: > Hi, > > I generate a debian package for the more recent lyx (1.6.4), I want > to share it, how and where to upload it. > > The file is generated for debian lenny (5.0) and can normally used > on recent ubuntu . > > > I am not a guru for creating debian package, so I need feed back. > Thanks for testing and help > > best regards > > bela > > > > > -- > To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org > -- Jonathan Wiltshire 1024D: 0xDB800B52 / 4216 F01F DCA9 21AC F3D3 A903 CA6B EA3E DB80 0B52 4096R: 0xD3524C51 / 0A55 B7C5 1223 3942 86EC 74C3 5394 479D D352 4C51 -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#543843: gqview -- simple image viewer using GTK+
Hi Dne Thu, 27 Aug 2009 11:48:57 +0200 martin f krafft napsal(a): > also sprach Daniel Baumann [2009.08.27.0944 +0200]: > > I am orphaning gqview. > > > > Maintaining a package requires time and skills. Please only adopt this > > package if you will have enough time and attention to work on it. > > I'd be willing to sponsor anyone who will take up maintenance of > this package. Please note that there is geeqie, which took gqview code and now provides active upstream for it. There is also pending patch for geeqie package to provide gqview, which we will integrate once geeqie will get out of beta phase. And then it will be time to drop gqview package. -- Michal Čihař | http://cihar.com | http://blog.cihar.com signature.asc Description: PGP signature
Re: Bug#543843: gqview -- simple image viewer using GTK+
also sprach Daniel Baumann [2009.08.27.0944 +0200]: > I am orphaning gqview. > > Maintaining a package requires time and skills. Please only adopt this > package if you will have enough time and attention to work on it. I'd be willing to sponsor anyone who will take up maintenance of this package. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: Bug#543825: acct -- The GNU Accounting utilities for process and login accounting
also sprach Daniel Baumann [2009.08.27.0931 +0200]: > I am orphaning acct. > > Maintaining a package requires time and skills. Please only adopt this > package if you will have enough time and attention to work on it. I'd be willing to sponsor anyone who will dedicate to maintaining acct. -- .''`. martin f. krafft Related projects: : :' : proud Debian developer http://debiansystem.info `. `'` http://people.debian.org/~madduckhttp://vcs-pkg.org `- Debian - when you have better things to do than fixing systems digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/)
Re: Bug#543741: ettercap: should this package be orphaned?
On Thu, Aug 27, 2009 at 11:25, Murat Demirten wrote: > I'm planning to close all bugs related to ettercap. Ettercap authors don't > work on this project anymore Why would you close bugs (I suppose Debian ones) if they are still valid? > but it is good to have this package at least a few years more, it runs very > well on most scenario. in particular if you plan to leave the package in Debian. Regards, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#543741: ettercap: should this package be orphaned?
On Thu, 2009-08-27 at 10:48 +0200, Andreas Henriksson wrote:
> *If* this package becomes orphaned, I'll happily sponsor someone willing to
> maintain it. Maybe there's someone on debian-mentors who would be willing to
> adopt it if it's orphaned. Any volunteers?
I'm taking a look at it, although even at grabbing the build-deps I seem
to running across something:
zak...@perlis:~/pkg/e/ettercap$ sudo aptitude build-dep ettercap
Reading package lists... Done
Building dependency tree
Reading state information... Done
Reading extended state information
Initializing package states... Done
Reading task descriptions... Done
Unable to satisfy the build-depends: Build-Dependslibncurses-dev.Unable
to satisfy the build-depends: Build-Dependslibltdl3-dev.Unable to
satisfy the build-depends: Build-Dependslibncurses-dev.Unable to satisfy
the build-depends: Build-Dependslibltdl3-dev.The following NEW packages
will be installed:
libnet1{a} libnet1-dev libpcap0.8-dev libpcre3-dev libpcrecpp0{a}
0 packages upgraded, 5 newly installed, 0 to remove and 2 not upgraded.
Need to get 526kB/734kB of archives. After unpacking 2171kB will be
used.
--
Zak B. Elep -- 1486 7957 454D E529 E4F1 F75E 5787 B1FD FA53 851D
I like the idea of 256 bits, though: 32 for the (Unicode) character
leaves room for 224 Bucky bits, which ought to be enough for anyone.
-- Roland Hutchinson, in alt.folklore.computers
signature.asc
Description: This is a digitally signed message part
Re: Bug#543741: ettercap: should this package be orphaned?
I'm planning to close all bugs related to ettercap. Ettercap authors don't work on this project anymore but it is good to have this package at least a few years more, it runs very well on most scenario. 2009/8/27 Andreas Henriksson > Hello Lucas! > > Adding debian-mentors list to the discussion... > > On Wed, Aug 26, 2009 at 06:28:29PM +0200, Lucas Nussbaum wrote: > > Package: ettercap > [...] > > While reviewing some packages, your package came up as a package that > > should maybe be orphaned by its maintainer, because: > [...] > > [ To Andreas: are you interested in adopting ettercap? ] > [...] > > Not being a heavy user of the program myself and to be honest not extremely > entusiastic about it either I'd rather see someone else take lead. > > *If* this package becomes orphaned, I'll happily sponsor someone willing to > maintain it. Maybe there's someone on debian-mentors who would be willing > to > adopt it if it's orphaned. Any volunteers? > > -- > Andreas Henriksson > > >
Re: RFS: opendchub (updated package)
On Thu, 2009-08-27 at 11:52 +0300, George Danchev wrote: > Quoting "Zak B. Elep" : > > Wait, a giant budget excluding a non-internetworked environment? Then > > again, with the government where I come from, its not too far off to > > imagine that. :P > > It simply boils down to the (strange) security policies they are > using, tightly controlled environments and physically separated > networks they are in. You don't connect sensitive systems and networks > to the public networks like internet is ;-) Agreed. That quip was rather referring to my government's capabilities (or lack thereof.) Sorry for that aside. > > Thanks, all in all, that was a better take on why separate patching > > should be done. I'll take a look at topgit (and quilt, too) and will > > probably rebuild the package. > > Good. I've pushed 0.8.0-3 to mentors with the change. I'm going to do the same for my other RFS'd package (gtklp). -- Zak B. Elep -- 1486 7957 454D E529 E4F1 F75E 5787 B1FD FA53 851D I like the idea of 256 bits, though: 32 for the (Unicode) character leaves room for 224 Bucky bits, which ought to be enough for anyone. -- Roland Hutchinson, in alt.folklore.computers signature.asc Description: This is a digitally signed message part
Re: RFS: opendchub (updated package)
Quoting "Zak B. Elep" : Hi, On Wed, 2009-08-26 at 20:49 +0200, George Danchev wrote: Nice argumentation, but not bullet proof ;-) Was never really an argument. Remember that I did use separate patching in the previous version (if you read my response in the other thread I made it quite clear that I'm not closing the door on separate patching.) Sorry, I was/am not familiar with your previous package versions. Actually your repo is a very weak reference to what actually Debian currently releases -- source and binary packages, eventually burned on optical media people use here and there. Let's, imagine a secret lab, giant budgets, and perhaps a team of government scientists working within a non-internetworked area (surprise, heh;-) using Debian source and binary CD/DVD's. Now, do you see the disconnect? Providing more use cases like that, even in the days of Web 2.0, is a trivial task, just try harder ;-) Wait, a giant budget excluding a non-internetworked environment? Then again, with the government where I come from, its not too far off to imagine that. :P It simply boils down to the (strange) security policies they are using, tightly controlled environments and physically separated networks they are in. You don't connect sensitive systems and networks to the public networks like internet is ;-) That aside, I note that it doesn't really matter if those guys above have no access to the package VCS repo: they have the source packages anyway, which already contains the diffs. They can dpkg-source -x it, they can dpkg-buildpackage it, and they can read debian/changelog. But those diffs are applied in a combined fashion to the upstream source (not very helpful for people actually interested to understand the code), while they might be extremely interested to understand how many *logical* changes have been applied, what are the reasons behind such a deviation from the upstream, hence they would need to find out and dig into your own VCS repo which is not so tightly associated with the bits Debian actually and officially releases. What if your own server goes down, repo changed or disappeared. Compare that to a Debian release which never disappears. What really goes on here is that there's a stronger preference towards having patches in debian/patches/ m as it is a particular convenience for maintainers, as opposed to navigating the source tree for diffs. for maintainers and *any sort of users* of your source/binary package. I don't object to this at all, as long as it doesn't break my maintaining the package. Hopefully that could be fixed by actually distributing package's VCS repo, that we can call boldly `self-contained', which would effectively be addressed by the new debian source formats like 3.0 (git) and friends. However they are not ready yet AFAICT, so until then topgit might be your best bet, if you want to re-connect all the users of your source package(s) Debian proudly distributes. Thanks, all in all, that was a better take on why separate patching should be done. I'll take a look at topgit (and quilt, too) and will probably rebuild the package. Good. -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: Bug#543741: ettercap: should this package be orphaned?
Hello Lucas! Adding debian-mentors list to the discussion... On Wed, Aug 26, 2009 at 06:28:29PM +0200, Lucas Nussbaum wrote: > Package: ettercap [...] > While reviewing some packages, your package came up as a package that > should maybe be orphaned by its maintainer, because: [...] > [ To Andreas: are you interested in adopting ettercap? ] [...] Not being a heavy user of the program myself and to be honest not extremely entusiastic about it either I'd rather see someone else take lead. *If* this package becomes orphaned, I'll happily sponsor someone willing to maintain it. Maybe there's someone on debian-mentors who would be willing to adopt it if it's orphaned. Any volunteers? -- Andreas Henriksson -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
RFS: logiweb
Dear mentors, I am looking for a sponsor for my package "logiweb". * Package name: logiweb Version : 0.2.0-1 Upstream Author : Klaus Grue * URL : http://logiweb.eu/doc/0.2.0/download/debian.html * License : GPL Programming Lang: C Description : a system for electronic distribution of mathematics Section : math It builds these binary packages: logiweb - a system for electronic distribution of mathematics The package appears to be lintian clean. The upload would fix this bug: 543550 The package can be found on logiweb.eu: http://logiweb.eu/doc/0.2.0/download/debian I would be glad if someone would sponsor this package. Bug 543550 is the ITP for logiweb. I have included more info on logiweb below. I have tried hard to get the package right, but it is the first Debian package I have ever made. Cheers, Klaus --- Long description: Logiweb allows to web publish 'Logiweb pages', i.e. journal quality articles which contain machine readable objects like programs, testsuites, definitions, axioms, lemmas, and proofs. Among other, Logiweb is suited for literate programming, for publication of machine verified proofs, and for writing proof checkers. Logiweb allows Logiweb pages to reference previously published Logiweb pages such that programs on a page may call programs on referenced pages, proofs on a page may reference lemmas on referenced pages, and so on. --- Logiweb was presented at MKM2003 (c.f. K.Grue: Logiweb, Mathematical Knowledge Management Symposium 2003, Ed. Fairouz Kamareddine, Electronic Notes in Theoretical Computer Science, Vol. 93, pp.70-101, 2004). See also http://www.diku.dk/~grue/papers/logiweb/ It was also presented at the International Conference of Mathematical Software ICMS2006 (c.f. K.Grue: Logiweb - A System for Web Publication of Mathematics, In: Mathematical Software - ICMS 2006, Springer Berlin / Heidelberg, Lecture Notes in Computer Science, Vol. 4151/2006, pp.343-353, 2006). See also http://www.diku.dk/~grue/papers/icms/icms.pdf The latter paper was produced using Logiweb itself. --- The 0.1.x beta test series of Logiweb was released 2006-2007. It was tested by graduate students at the University of Copenhagen. Based on the beta test, Logiweb has been ported from clisp to C and has been cleaned up 2008-2009. The purpose of the 0.2.x pre-release series is to test the C version and get packaging right. A 1.0.x series is going to follow the 0.2.x series. The 0.1.x beta test series followed a 0.grue.x alpha test series which was released 2004-2006 and which was also tested by graduate students. The design of Logiweb began in 1996, based on a previous system which was used at the University of Copenhagen 1985-1996. That system in turn built on a system that was developed 1972-1985. Logiweb contains a regression testsuite with 15000+ small test cases plus a number of larger test cases where the Logiweb compiler is applied to a number of well- and ill-formed sources. The easiest way to get and run the regression test is to use the .tar.gz version, c.f. http://logiweb.eu/doc/0.2.0/download/gz.html. Note that the main pages (http://logiweb.eu/ and the mirror sites http://topps.diku.dk/logiweb/ and http://logiweb.imm.dtu.dk/) are concerned with the 0.1.9 version of Logiweb and not relevant for the present 0.2.0 release. --- In the present version, Logiweb essentially consists of the "Logiweb compiler" (lgc) and the Logiweb Abstract Machine (lgwam). The lgc compiler translates sources expressed in the Logiweb Source language (lgs) to a binary format. Thus, essentially, the present release of Logiweb is yet another compiler for yet another programming language. The lgs language is particularly suited to writing proof systems. But it has also been used for other purposes. As an example, the lgc compiler itself is written in its own language. Furthermore, software for a 'star tracker' (c.f. http://en.wikipedia.org/wiki/Attitude_dynamics_and_control) has been implemented in lgs for the European Space Agency as an experiment in using literate programming for reducing cost of critical software. (for 'literate programming' see http://en.wikipedia.org/wiki/Literate_programming). The deep structures of the lgs language resembles those on Lisp. The syntax is quite different. In lgs, the programmer defines the language he or she wants to use in a header, and then uses that syntax in the body. Through use of the macro expansion facilities and rendering capabilities, the programmer can also define the semantics of lgs. So a determined programmer can write in any language using lgs. Programs written in lgs can reference libraries across the Internet in a safe way. The output from the lgc compiler is in turn suited for web publication by putting the output within reach of an http server (such as Apache). This feature is the reason for the 'web' in 'Logiweb': the system is suited for
Re: RFS: burn 0.4.3-2.2 (Lenny security bug fixes)
Hi Ben, Ben Finney ha scritto: > Ben Finney writes: > >> The debdiff against the version currently in Lenny is online at >> http://paste.debian.net/45120/>. > > The syntax highlighter at that site is munging the display of some > characters. (I've reported this issue to the site maintainer.) The patch > as plain text is at http://paste.debian.net/45120/plain/45120> and > is correct. > I'm not a DD, but just a note. "TEMP-0542329" is not thought for external reference, probably you should remove that from your changelog. Cheers, Giuseppe. signature.asc Description: OpenPGP digital signature
