Bug#1052693: sisu Re: live-manual-pdf: PDF manual is unreadable
I have updated sisu-pdf (latex output for texlive) and pdfs (from sisu) once again work for me. https://git.sisudoc.org/sisu Re live-manual this is a partial fix as I have not got the Japanese font to work yet (my recollection is that this was considerably easier many years ago developing the first time round). Actually I ended up so focused on that that (it being so obviously faulty, based on a default Chinese font that) I have not checked other language outputs, which others will in any event be in a better position to verify. sisu 7.3.0 - uploaded to Debian October 31 - migrated to testing November 5 I see that in addition to further fixes, there is quite a bit of debian packaging tidying that should be done. https://tracker.debian.org/pkg/sisu Bugs to sisu might be helpful, I will try to monitor live-manual, but my noticing this issue with live-manual (and thereby being notified of an issue with sisu on debian, and finding out about the need for updates for a newer version of texlive) was a bit perchance. Thanks, Ralph
Bug#1052693: sisu Re: live-manual-pdf: PDF manual is unreadable
Summary: - the "cause" of failure of sisu and hence live-manual to produce pdf output is that sisu's latex output is out of date and needs updating..., - I am on it and am making headway :-) - changes have not yet been uploaded upstream, I will report when they are. The longer story :-) I thought it time to post an update since I am looking at this, though I have been procrastinating :-( A week ago I was back on a my old debian box, forgotten password reset and dist-updated. My assumption as to where the fault was likely to lie proved incorrect, 2 or three .sty files had moved, but they were all installed by sisu-pdf or sisu-complete and available on the system. So, ... minor surprise, Debian (testing/unstable at least) is using a newer version of texlive (2023) than NixOS (texlive 2022-final) and somewhere therein lies the problem, of the issue not having come up for me. sisu.spine the not-shared D lang version of sisu in its rewrite has more recently "developed" latex output and, though not developed or tested previously on texlive 2023 is not afflicted to the same extent as sisu.ruby that we fixing here. This meant, I had something to look at and could no minor (very incomplete) backporting for output and make headway in solving the sisu-pdf issue reported for live-manual pdf output. In short, progress has been made, I do have some output. Current status, though checking will be necessary, I do have portrait pdf output for languages other than Chinese, Japanese, Korean (are made to work in an updated way on sisu.spine.d i.e. not using CJK.sty whatever that sty that is claimed to be obsolete is called... have not looked at yet, but should be doable). For landscape pdf output, I expect the effort to be relatively minor, just it all takes a bit of time (especially with a procrastinator, I am plodding towards getting it done though). I will report again when I have got further or better yet, when I upload a first set of changes to sisudoc.org This bug, should be cross-assigned to sisu.
Bug#1052693: live-manual-pdf: PDF manual is unreadable
(i hope this is how to reply to the right place in the bugtracker, it has been a while and recall using reportbugs? in the past). I see the live-manual lack of pdfs bug and am jumping in somewhat prematurely as I am making assumptions as to the likely cause without having done any tests on Debian, and without knowing anything really about the setup or infrastructure in place for generating live-manual apart from the fact that sisu has been responsible for the output in question in the bug report. The issue: "no pdfs" is somewhat familiar, it reminds me of a previous issue on Debian that affected the ability of sisu to produce pdfs. The good news, since this bug report (using NixOS) I have: - checked sisu with ruby-3.2 (and ruby-3.1) and it works - (more specifically) checked sisu latex pdf output (against an old reference copy of debian-live-manual sisu source markup) with ruby 3.2 and it works The less good news: - the tests were not on Debian but on NixOS though the program code is the same for both distributions and has worked unchanged. (I switched from Debian to using NixOS as my primary distribution around 2020 and am not sure I even have a functional Debian box to log into or test on). - I have not programmed in ruby since 2015 (when I started my rewrite of sisu in the programming language D) - Since 2019 or so I use a D version of sisu that I have not shared or decided how or whether to share. Back again to better news: - The stoping of sisu genrating pdfs on Debian has happened a couple of times before with new debian releases containing texlive packages that rearrange the locations of latex .sty files within them. It has (in the past) been relatively easy to fix. ./lib/sisu/texpdf_format.rb (towards the end of the file) contains notes on steps that were taken last time to locate the .sty files relevant to sisu and where they were to be found within Debian. Once the relavant texlive packages are identified what needed to be done was to make sure their dependencies were in place within ./debian for sisu-pdf . It appears that this last needed to be done in 2019 and 2017 before that. https://sisudoc.org/projects/sisu/log/?qt=grep=.sty https://sisudoc.org/projects/sisu/commit/?id=55df651b572c5737ba01ac68f90d8475331a208b https://sisudoc.org/projects/sisu/log/?h=debian=grep=tex https://sisudoc.org/projects/sisu/commit/?h=debian=2a3350c959d83c88e498b87345b06b1f42f96df3 https://sisudoc.org/projects/sisu/commit/?h=debian=86f1de612b231a929e2d815097cdd3c4766809b9 I have no idea what texlive packaging in Debian looks like now, nor indeed can I be certain that this (or indeed anything to do with sisu) is the cause of the problem, (though it does seem likely to me). The notes in the file ./lib/sisu/texpdf_format.rb should give an idea of how to find out which texlive packages are needed as dependencies for sisu to produce pdfs. Sisu is a ruby program that is largely distribution agnostic, that there have been no hiccups in the behaviour of sisu in producing pdfs on NixOS suggests, hopefully that this is nothing major. If this is the cause a bug should be filed somewhere against sisu packaging (texlive dependencies). Given my current situation, willing to help but (for the time being at least) using another distro, there should perhaps be another uploader in debian, and sisu upstream should relinquish having a ./debian (packaging) directory, which can be handled by the Debian project? (i hope this is how to reply to the right place in the bugtracker, it has been a while and recall using reportbug? in the past). Greetings, Ralph
Bug#864224: sisu-pdf: switch dependency from texlive-math-extra to texlive-science
Andreas, thank you, Ralph On Mon, Jun 5, 2017 at 4:59 PM, Andreas Beckmannwrote: > Followup-For: Bug #864224 > Control: tag -1 patch pending > > Hi, > > I just uploaded a 0-day NMU directly to sid, s.t. this can still reach > stretch r0. > > > Andreas
Bug#606337: po4a: [text] Add support for SiSU markup
Please close bug (and do not apply patch). As far as I understand it the patch was not needed, and ended up being forgotten about. Ben please feel free to chime in. On 2016-09-05 14:56, Martin Quinson wrote: > Hello, > > I'd like to come back on that very old bug of PO4A. How did you > guys deal with the problem in the meanwhile? Is the patch still > relevant? The patch was not needed... as far as I understand it, regular text mode was used while retaining sisu markup in the original and translated texts. > I would like to have some more documentation and at least one test > before merging it, please. Does it sound like something feasible > to you? Please do not merge it, and you may close this particular bug. > Thanks in advance, and sorry for all these years. > Thanks, ... no worries, we did not post follow up requests. It may in future be of interest to have something ... if so we will make the request. Po4a and sisu work well together. > Bye, Mt. > Thanks, Ralph > -- > I don't care whichever programming language we choose, as long as it's C. -- D chosen
Bug#807793: sisu: sisu-mode.el install to site-lisp
Kevin, thank you. I am in last minute packing mode, family holiday, travel tomorrow, back around the 4th. There should be Internet connection, probably sporadic, (visiting another generation and expect to be kept busy). Will look at your post and expect to pick up on again in the new year if not before. Happy Holidays, and Best Wishes for the coming year. Thanks, Ralph On Fri, Dec 18, 2015 at 10:58 PM, Kevin Ryde <user42_ke...@yahoo.com.au> wrote: > Ralph Amissah <ralph.amis...@gmail.com> writes: >> >> I did use a subdirectory as it looks cleaner and is available should >> there ever be more files to place there > > The startup will need that, eg. per attached below. > >> (and I copied the autoload file there as well). > > Slight doubt about extending load-path in sisu-autoloads.el, otherwise > no worries. > >> ultimately as upstream, > > Actually on the upstream front I meant to say I think outline-regexp > should be buffer-local. It could go in the main mode function too > as a setup for inter-operation. Bit of a diff attached below, > > 2015-12-19 Kevin Ryde <user42_ke...@yahoo.com.au> > > * sisu-mode.el: outline-regexp buffer local, more autoload cookies, > auto-mode-alist use \' for end-of-string. > > >> Remaining holdouts: (i) from the most recent posting, not having sorted >> syntax highlighting for tic block types ``` > > Non-greedy might help (untested), > > ```.*?\n```\n > > which matches as little as possible to satisfy. Except . doesn't match > newline so umm \\(.\\|\n\\)*? A matcher function is also possible if it > gets too much. > > You might have seen in info node "(elisp)Multiline Font Lock" some extra > trouble is needed to make a multi-line match work fully. Hard work this > font lock eh :-) > >> (ii) anticipated changes for code block tags: >> will need to identify the code language held by the block (but that is >> down the line, as sisu does not take this into account yet (having come >> from a more law and literature text background rather than a code text >> one)). > > Some "multiple major modes" things can supposedly apply different modes > to buffer sub-parts. I think I've seen it work but never needed it. >
Bug#807793: sisu: sisu-mode.el install to site-lisp
On Wed, Dec 16, 2015, user42_ke...@yahoo.com.au wrote: > (The site-lisp dir is designed for packages to put stuff in. You can > contemplate a subdirectory and some byte compiling later if desired. > Usually a subdirectory is when a package has multiple lisp files.) Kevin thanks again. sisu 7.1.6-1 was pushed to Debian 2015-12-15. It tries to take into account your recommendation and patch. https://tracker.debian.org/news/733057 http://git.sisudoc.org/gitweb/?p=code/sisu.git;a=shortlog;h=refs/tags/sisu_7.1.6 http://git.sisudoc.org/gitweb/?p=code/sisu.git;a=shortlog;h=refs/tags/debian/sisu_7.1.6-1 I am not certain it is implemented as it should be and whilst pointing to the bug in the changefiles I have not thought to close it. I did use a subdirectory as it looks cleaner and is available should there ever be more files to place there (and I copied the autoload file there as well). There may be a bit of unnecessary duplication with the autoload file for example being copied to more locations than necessary. sisu 7.1.6 was also uploaded to Arch linux as well, though no attempt has been made to sort out the emacs files there as yet. Thanks, Ralph On Wed, Dec 16, 2015, user42_ke...@yahoo.com.au wrote: > > Ralph Amissah <ralph.amis...@gmail.com> writes: >> >> I do not know enough about emacs packaging, though I have started to >> really enjoy using it (with vim bindings and evil-mode (and look forward >> to trying spacemacs)). > > It's a long time since I tried the vi emulations. But Saint Ignucius > teaches us that using vi is a penance, not a blasphemy. :-) > His penance is my bliss; remind me to thank him for my being in the clear re. blasphemy (and for my bliss, the St. together with the many other contributers starting with "evil-mode" that granted access to his church ... and "org-mode" etc.). >> I together with Ambrose Kofi Laing assigned an earlier version of the >> file to the FSF, and see them and maintenance of it ultimately as >> upstream, > > A Debian-specific startup might not be of interest unless you keep the > rest of packaging there too. > Guess it is time to forward to the FSF what it is for now. Remaining holdouts: (i) from the most recent posting, not having sorted syntax highlighting for tic block types ``` (there I have not been able to provide what should not be matched within the block, so the tags exist more as a written expression of the desired bock style than for being functional), and; (ii) anticipated changes for code block tags: will need to identify the code language held by the block (but that is down the line, as sisu does not take this into account yet (having come from a more law and literature text background rather than a code text one)). > > With respect to Debian packaging or interaction with the installed > > Debian package, I have a couple of questions. Should not file deposits > > to /usr/share/emacs/site-lisp/sisu-mode.el be co-ordinated with the > > debian-emacs team? > > No need. As long as it works (it does for me) you can just go ahead. > > (The site-lisp dir is designed for packages to put stuff in. You can > contemplate a subdirectory and some byte compiling later if desired. > Usually a subdirectory is when a package has multiple lisp files.) sisu-mode.el and sisu-mode-autoloads.el for 7.1.6 can be found at: http://git.sisudoc.org/gitweb/?p=code/sisu.git;a=tree;f=data/sisu/conf/editor-syntax-etc/emacs;h=add7360107c780122f9fa857a5fb5d2854a20614;hb=9664f4d70025b54adf8ba45fce6358f066f1444f debian/sisu.emacsen-startup http://git.sisudoc.org/gitweb/?p=code/sisu.git;a=blob;f=debian/sisu.emacsen-startup;h=e598e666fb60577ac5977506e6f2800adcc283a1;hb=b5538310dabc893ee54c3a2be4b0fec7ce968511 again thanks, (many of them :) Ralph
Bug#807793: sisu: sisu-mode.el install to site-lisp
Kevin, thank you for your feedback. It is very helpful. I do not know enough about emacs packaging, though I have started to really enjoy using it (with vim bindings and evil-mode (and look forward to trying spacemacs)). I together with Ambrose Kofi Laing assigned an earlier version of the file to the FSF, and see them and maintenance of it ultimately as upstream, so I am obliged to forward it to them. Which I intend to and shall do. There are a few things that ought to be done with the file before its submission though. With respect to Debian packaging or interaction with the installed Debian package, I have a couple of questions. Should not file deposits to /usr/share/emacs/site-lisp/sisu-mode.el be co-ordinated with the debian-emacs team? What is the protocol? I will look up email, do they have an IRC presence? I am out a fair bit these days and will be quite busy, but would like to see that this is sorted. Thank you. Ralph Amissah On Sun, Dec 13, 2015 at 02:42:20PM +1100, Kevin Ryde wrote: > Package: sisu > Version: 7.1.5-1 > Severity: wishlist > Tags: patch > File: /usr/share/sisu/conf/editor-syntax-etc/emacs/sisu-mode.el > > It'd be good to install sisu-mode.el to > /usr/share/emacs/site-lisp/sisu-mode.el ready for use in emacs. > A symlink to or from /usr/share/sisu/conf/editor-syntax-etc/emacs/ could > be left if desired if users might expect to see it there too. > > I suggest file debian/sisu.emacsen-startup below for autoloads which > dh_installemacsen will install to /etc/emacs/site-start.d/50sisu.el > > This doesn't create a dependency on emacs, just makes it ready for use > if you do run emacs. > > ;;; 50sisu.el -- debian emacs setups for sisu > > (if (not (file-exists-p "/usr/share/emacs/site-lisp/sisu-mode.el")) > (message "sisu removed but not purged, skipping setup") > > (autoload 'sisu-mode "sisu-mode" "Major mode for editing SiSU files." t) > (add-to-list 'auto-mode-alist '("\\.sst\\'" . sisu-mode)) > (add-to-list 'auto-mode-alist '("\\.ssm\\'" . sisu-mode)) > (add-to-list 'auto-mode-alist '("\\.ssi\\'" . sisu-mode)))
Bug#804315: [ralph.amis...@gmail.com: outrageous, thievery]
I post not in anger but sadness, I should not let my voice go uncounted. Attached is my note to Daniel of earlier today, before his posting of "an abrupt end to Debian Live". Debian Live which he said Debian should have (as a Debian developer) in 2006 and went on to deliver, rather nicely (with (and without) help). - Forwarded message from Ralph Amissah <ralph.amis...@gmail.com> ----- From: Ralph Amissah <ralph.amis...@gmail.com> To: Daniel Baumann Subject: outrageous, thievery Date: Mon, 9 Nov 2015 09:28:44 -0500 Message-ID: <20151109142844.GA28261@niu> User-Agent: Mutt/1.5.24 (2015-08-30) Daniel, (already one of the more active Debian Developers then) I remember you telling Debian at Debconf 2006, Mexico about how "we"[1] needed a live-maker within the project. I said then that I thought this one of the most important projects within Debian (I was surprised that there was not more interest and effort offered by others at the time, though there was some, those so keen now did not seem to pay attention then). Already then it was clear that it would one day be able to and possibly be the preferred way to do a Debian install... as I said, important. I saw how you contributed to Debian then, and I know how you have contributed since. Instead of welcoming you and your work, there seems to have been an effort to isolate you. Well clearly others have seen the fruits of your labor as a threat and with envy, and ripe for their plucking! Outrageous! Disgusting. It is nasty. A bit strange to think that I "know" some of those guys. My interest in Debian proper, dropped with your earlier treatment, it took away the desire to be a closer part of it. At least that took out much of any idealized notion of the inner workings of it. And there have been other moves since. I continue to be amazed by the politics of groups within Debian. This though has the feel of blatant thievery. Chals characterization of a dictatorial coup would seem to be most accurate. It has no doubt to do with power (perhaps indirectly money is involved as well), your work & work area being seen as strategically important. They do it because they can, & justify it whatever which way they will. I am sorry. I feel pretty bruised on your behalf. We have not spoken in a long while. I hope we have the chance to talk in happier times. Greetings. Ralph P.S. We are ok, not much to report. - End forwarded message - [edits: addition of footnote, &; s/picking/plucking/] Indeed I am a friend of Daniel and primarily a user of Debian (a minor contributor of a package (sisu[2]) that I wrote that I am happy to have in Debian). In other circumstances I would consider myself at least an admirer of individuals involved on the other side of this. Indeed I (use use some of your software daily and) have met a number of you over the years at a number of Debconfs and have fond memories for example of visits to Cambridge when I lived in the U.K. and of being "introduced" to Debian by Debian insiders. Thanks to all who have stood up for Daniel, he is a wonderful, generous, (and capable) person. And yes, I do think him "wronged" by "Debian". There are others that know him pretty well, who have followed a fairly long sequence of events who must be outraged as well. Of course I wish Debian well, but I do not see your "handling" of Daniel as its finest hour. This will no doubt "blow over" as it must ultimately for the good of the project, but it sticks in my craw as it no doubt does others, and there should be some record of conscientious objection. Ralph Amissah [1] to be clear, "we" was Debian. [2] http://www.sisudoc.org/ https://qa.debian.org/developer.php?login=s...@lists.sisudoc.org
Bug#784210: ruby-setup: update required module name to RbConfig
Source: ruby-setup Severity: important Tags: upstream Dear Maintainer, Browsing current source it seems line 789 should now be RbConfig::CONFIG (rather than Config::CONFIG) else if working now, there are likely to be problems with subsequent versions of Ruby. s/::Config::CONFIG/::RbConfig::CONFIG Similar issues may exist with other ruby libs? -- System Information: Debian Release: stretch/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#768399: unblock: sisu/5.7.1-2
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: unblock Please unblock package sisu It includes 2 rather small but significant cleanup bug fixes made for Jessie. * bugreports: #767761 * bug report closure: Subject: sisu: Irritating terminal reporting bug, re composite documents verbose mode https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767761 Reported by: Ralph Amissah ralph.amis...@gmail.com Severity: normal Tags: upstream Found in version sisu/5.7.1-1 Fixed in version sisu/5.7.1-2 Done: Ralph Amissah ra...@amissah.com #767776 * bug report closure: Subject: debian/changelog improvements (grammatical etc.) proposed for Jessie https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=767776 Reported by: Ralph Amissah ralph.amis...@gmail.com Severity: minor Found in version sisu/5.7.1-1 Fixed in version sisu/5.7.1-2 Done: Ralph Amissah ra...@amissah.com * relevant debian/changelog entries: #767761 * v5 v6: ao, composite documents, on --verbose report loading of .sst files, fix * without fix sisu reports loading of .ssm .ssi files but not .sst (sub-documents are imported correctly and resulting document outputs are correct and unaffected, but unless aware of this bug it would seem otherwise until the correct operation of sisu was manually verified e.g. by examining documents produced); (issue somewhat mitigated by not being the most common sisu operation) * sisu is in development freeze, this fix is provided for Debian Jessie (Closes: #767761) #767776 * debian/control sisu description, minor refinement * (Closes: #767776) full debian/changelog: http://sources.debian.net/src/sisu/5.7.1-2/debian/changelog/ Note other upstream changes provided by 5.7.2 are not included in the Debian package 5.7.1-2 as is shown by the attached debdiff debdiff sisu_5.7.1-1.dsc sisu_5.7.1-2.dsc \ sisu_5.7.1-2.dsc.diff unblock sisu/5.7.1-2 -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash diff -Nru sisu-5.7.1/debian/changelog sisu-5.7.1/debian/changelog --- sisu-5.7.1/debian/changelog 2014-10-19 21:23:24.0 -0400 +++ sisu-5.7.1/debian/changelog 2014-11-02 22:04:10.0 -0500 @@ -1,3 +1,31 @@ +sisu (5.7.1-2) unstable; urgency=medium + + * [b6e6eb5] v5 v6: version changelog (Frozen: bugfix documentation changes + only) +* NOTE: sisu is in development freeze mirroring the Debian release cycle; + bugfix documentation update only, pending the release of Debian Jessie +* (as sisu upstream) the cleanest git workflow solution to the Debian freeze + appears to be to follow the Debian freeze with respect to upstream + alterations of sisu (bugfix documentation only), incrementing upstream + version number as usual, whilst building package as required for Debian + freeze version of sisu 5.7.1-* + * [e206fef] v5 v6: ao, composite documents, on --verbose report loading of + .sst files, fix +* without fix sisu reports loading of .ssm .ssi files but not .sst + (sub-documents are imported correctly and resulting document outputs are + correct and unaffected, but unless aware of this bug it would seem + otherwise until the correct operation of sisu was manually verified e.g. + by examining documents produced); (issue somewhat mitigated by not being + the most common sisu operation) +* sisu is in development freeze, this fix is provided for Debian Jessie + (Closes: #767761) + * [a45079f] version changelog (revert to 5.7.1 state, minimize 5.7.1-2 diff) + * [3ea8131] debian/control sisu description, minor refinement +* (Closes: #767776) + * [f3cd973] .gitignore ignore .pc quilt dir + + -- Ralph Amissah ra...@amissah.com Sun, 02 Nov 2014 21:40:58 -0500 + sisu (5.7.1-1) unstable; urgency=medium [ Ralph Amissah ] diff -Nru sisu-5.7.1/debian/control sisu-5.7.1/debian/control --- sisu-5.7.1/debian/control 2014-10-19 21:23:24.0 -0400 +++ sisu-5.7.1/debian/control 2014-11-02 22:04:10.0 -0500 @@ -22,21 +22,22 @@ structuring, publishing and search framework for document collections. . With minimal preparation of a plain-text (UTF-8) file, using sisu markup - syntax in your text editor of choice, SiSU can generate various document + syntax in a text editor of your choice, SiSU can generate various document formats (most of which share a common object numbering system for locating content), including plain text, HTML, XHTML, XML, EPUB, OpenDocument text (ODF:ODT), LaTeX, PDF files, and populate an SQL database
Bug#767761: sisu: Irritating terminal reporting bug, re composite documents verbose mode
Package: sisu Version: 5.7.1-1 Severity: normal Tags: upstream Irritating terminal reporting bug, re composite documents verbose mode, could be classified as a documentation bug at a pinch In verbose mode, when generating composite documents (a master file .ssm that pulls in one or more .sst or .ssi files)... sisu reports as it should the loading of the initial master file (.ssm) and any subsequent insert only files (.ssi), but in error does not report any imported (independently processable) .sst files. These should also be reported and always have been in the past... The result is that it looks as though the event does not happen, and as though this feature is broken, but verification of the generated output document would show, the document produced is as it should be. As an example a marked up master document (.ssm) pulling in sub-documents, with the following: A~ @title @creator B~ Alice in Wonderland alice_in_wonderland.lewis_carroll.sst B~ Through the Looking Glass through_the_looking_glass_insert.lewis_carroll.ssi ... - running: sisu --html --verbose aiw_and_ttlg.lewis_carroll.ssm - reports omitting the .sst file as follows: Composite Document [en] loading: aiw_and_ttlg.lewis_carroll.ssm loading: through_the_looking_glass_insert.lewis_carroll.ssi - instead of as it should: Composite Document [en] loading: aiw_and_ttlg.lewis_carroll.ssm loading: alice_in_wonderland.lewis_carroll.sst loading: through_the_looking_glass_insert.lewis_carroll.ssi In any event the resulting output is fine (as the document is correctly imported (though this is not reported as it should be)). The fix is straightforward, an upstream fix will be posted, and packaged for Debian as sisu 5.7.1-2 and a freeze exception requested of the Jessie Release team. (it may also include minor grammatical corrections to the debian/control description of sisu) -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_US.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sisu depends on: ii rsync 3.1.1-2 ii ruby1:2.1.0.4 ii ruby2.1 [ruby-interpreter] 2.1.4-1 ii unzip 6.0-12 ii xz-utils5.1.1alpha+20120614-2 ii zip 3.0-8 Versions of packages sisu recommends: ii imagemagick8:6.8.9.9-2 ii keychain 2.7.1-1 ii openssh-client 1:6.7p1-2 ii openssl1.0.1j-1 pn po4a none pn qrencode none ii rake 10.3.2-2 pn ruby-rmagick none ii ruby-thor 0.19.1-1 ii sisu-pdf 5.7.1-1 ii sisu-postgresql5.7.1-1 ii sisu-sqlite5.7.1-1 pn tidy none ii tree 1.7.0-3 ii vim-addon-manager 0.5.3 Versions of packages sisu suggests: pn calibre none ii lv 4.51-2.2 pn pinfonone pn poedit none pn sisu-markup-samples none pn texinfo none pn trangnone -- Configuration Files: /etc/sisu/rc/sisurc_by_fn.yml 9abc3aeb1a8c00a82aa0047c79f211c8 [Errno 2] No such file or directory: u'/etc/sisu/rc/sisurc_by_fn.yml 9abc3aeb1a8c00a82aa0047c79f211c8' /etc/sisu/rc/sisurc_by_ft.yml fe4c507e5937f1f7f96fbbc52f9168f2 [Errno 2] No such file or directory: u'/etc/sisu/rc/sisurc_by_ft.yml fe4c507e5937f1f7f96fbbc52f9168f2' /etc/sisu/rc/sisurc_by_lng.yml 4eecf84de8e7affc2dec66344fe0edcc [Errno 2] No such file or directory: u'/etc/sisu/rc/sisurc_by_lng.yml 4eecf84de8e7affc2dec66344fe0edcc' -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#767776: debian/changelog improvements (grammatical etc.) proposed for Jessie
Package: sisu Version: 5.7.1-1 Severity: minor debian/changelog could be improved, contains minor grammatical errors, and could be clearer. Minor improvements to debian/changelog take opportunity to do this as requesting a release exception for #767761. currently proposed changes, to be included in 5.7.1-2 (along with fix for #767761) diff --git a/debian/control b/debian/control index d424f95..ee82149 100644 --- a/debian/control +++ b/debian/control @@ -22,21 +22,22 @@ Description: documents - structuring, publishing in multiple formats and search structuring, publishing and search framework for document collections. . With minimal preparation of a plain-text (UTF-8) file, using sisu markup - syntax in your text editor of choice, SiSU can generate various document + syntax in a text editor of your choice, SiSU can generate various document formats (most of which share a common object numbering system for locating content), including plain text, HTML, XHTML, XML, EPUB, OpenDocument text (ODF:ODT), LaTeX, PDF files, and populate an SQL database with objects (roughly paragraph-sized chunks) so searches may be performed and matches returned with that degree of granularity. Think being able to finely match - text in documents across different output formats and across languages if you - have translations of the same document, using common object numbers. - Additionally for search, your criteria is met by these documents at these - locations within each document (equally relevant across different output - formats and languages). To be clear (if obvious) page numbers provide none of - this functionality. Object numbering is particularly suitable for published - works (finalized texts as opposed to works that are frequently changed or - updated) for which it provides a fixed means of reference of content. Document - outputs also share semantic meta-data provided. + text in documents, using object numbers, across different output formats and + across languages if you have translations of the same document. Search results + can be an index of documents and object numbers within them, your criteria is + met by these documents at these locations within each document (equally + relevant across different output formats and languages). To be clear (if + obvious) page numbers provide none of this functionality. Object numbering is + particularly suitable for published works (finalized texts as opposed to + works that are frequently changed or updated) for which it provides a fixed + means of reference of content. Document outputs can also share provided + semantic meta-data. . SiSU also provides concordance files, document content certificates and manifests of generated output. SiSU provides the means to make book indexes @@ -50,7 +51,7 @@ Description: documents - structuring, publishing in multiple formats and search The package sisu-complete installs the whole of SiSU. . Additional document markup samples are provided in the package - sisu-markup-samples which is found in the non-free archive the licenses for + sisu-markup-samples which is found in the non-free archive. The licenses for the substantive content of the marked up documents provided is that provided by the author or original publisher. . -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763557: sisu-* namespace Re: ITP: Bug#763752, Bug#763557, Bug#763704
* Emmanuel Bourg ebo...@apache.org [Sat, 04 Oct 2014 09:57:50 +0200], wrote: Hi Ralph, Thank you for the notice. I wasn't aware of the existing sisu packages, here is some information to help evaluation the situation: - there are five sisu-* Java packages: sisu-inject and sisu-plexus currently in the NEW queue, and sisu-maven-plugin, sisu-ioc and sisu-guice already in the archive. sisu-ioc will eventually be removed as it is superseded by sisu-inject and sisu-plexus. No other sisu Java package is expected as far as I know. Thanks for the feedback. - the binary packages are all named lib*-java - they do not install any command line tools As you can see the invasion is fairly limited, and there is no risk of technical conflict, so they can safely coexist. Reassured, thank you, it sounds that way to me. ... and it should not result in undue user confusion either (FTP-Masters appear to have made that call) all good. Emmanuel Bourg Thanks, Ralph Amissah -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#763557: sisu-* namespace Re: ITP: Bug#763752, Bug#763557, Bug#763704
Emmanuel, Debian Project, I am Debian maintainer (and upstream) for package SiSU. It appears worth pointing out that your packages sisu-* will be sharing namespace with sisu, a command line document generator and search application written in ruby. Though inconvenient, this should not a problem (unless the Debian project determines otherwise:), provided there is no technical conflict. sisu is invoked from the command line using sisu or a number of related hyphenated variations depending on the intended output (e.g. sisu-html, sisu-epub). The package sisu currently contains sisu-postgresql, sisu-sqlite, sisu-pdf, and sisu-complete; there is also sisu-markup-samples in nonfree. If there could be a technical conflict I request a changing of name of your packages in some way to make the distinction clear, otherwise this note is just to make sure you are aware that a sisu already exists in the Debian archive. SiSU is not particularly widely used, but has been developed since 1997 and shared as open source through Debian since 2005. I did not think it necessary to mention initially, but with the growing list of sisu-* package additions, it seems a major enough sharing/invasion of namespace to take note of and make sure all are aware of. https://tracker.debian.org/pkg/sisu https://tracker.debian.org/pkg/sisu-markup-samples Re: Bug#763752: ITP: sisu-plexus -- Plexus adapter for the Sisu dependency injection container Re: Bug#763557: ITP: sisu-maven-plugin -- Maven plugin indexing JSR-330 components Re: Bug#763704: ITP: sisu-inject -- Dependency Injection container for Java All the best, Ralph Amissah P.S. I am away from the net this weekend and responses should any be expected may be delayed. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744405: sisu: set default font size
Fixed (in sisu 5.3.5 not in Debian but) these changes included in 5.3.6-1 now in unstable v6: texpdf, pdf default font size configurable (cli sisurc.yml) (no fractions) * --pdf-fontsize-12 --pdf-fontsize-8 * default: texpdf_fontsize: 12 * (Closes: #744405) http://sources.sisudoc.org/gitweb/?p=code/sisu.git;a=commitdiff;h=df9e4219258cd799a11be6f2d18f2af5b88d8352 signature.asc Description: Digital signature
Bug#744378: --no-manifest not working anymore
* Daniel Baumann daniel.baum...@progress-technologies.net [Sun, 13 Apr 2014 16:12:13 +0200], wrote: Package: sisu Version: 5.3.4-1 Severity: wishlist when running sisu-pdf with --no-manifest, the output (pdf) still contains the sisu manifest at the end of the document. Regards, Daniel fix, the metadata page in pdf should not contain link to manifest where --no-manifest flag is used the --no-metadata flag to suppress the metadata page (within a pdf, html text etc.) is not implemented Version: 5.3.5-1 will contain this other fixes described in response to bug reports (5.3.5::6.0.5) Debian upload currently awaiting clearance from the ruby debian team: This package is part of the ongoing testing transition known as ruby1.9.1-rm. Please avoid uploads unrelated to this transition, they would likely delay it and require supplementary work from the release managers. On the other hand, if your package has problems preventing it to migrate to testing, please fix them as soon as possible. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug. As sisu is developed on ruby 2.0 and tested on ruby 2.1 I may get impatient after a while upload anyway. Thanks, Ralph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744360: includes do not work properly
* Daniel Baumann daniel.baum...@progress-technologies.net [Sun, 13 Apr 2014 12:38:59 +0200], wrote: Package: sisu Version: 5.3.4-1 Severity: wishlist using this in foo.ssm: :A~ foo :B~ bar bar/baz.ssi and this in baz.ssi: 1~ foo bar baz then everything works. using the more natural foo.ssm: :A~ foo bar/baz.ssi and baz.ssi: :B~ bar 1~ foo bar baz makes ':B~ bar' being ignored in the output (pdf) entirely. Regards, Daniel It appears both give faulty text, though in different ways, fixed Version: 5.3.5-1 will contain this other fixes described in response to bug reports (5.3.5::6.0.5) (see note in bug #744378 on current Debian upload blocker) Thanks, Ralph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744353: please do not use typewriter for urls
* Daniel Baumann daniel.baum...@progress-technologies.net [Sun, 13 Apr 2014 12:28:27 +0200], wrote: Package: sisu Version: 5.3.4-1 Severity: wishlist when using urls in sisu like this: http://example.org sisu then creates in the output (pdf) links like this: http://example.org where as 'http://example.org' is written in typewriter font (monospace). please don't do that automagically since it's desturbing the visual flow when reading. If the users wants that, he should be able to configure it. Regards, Daniel monospace for url outputs in pdf this is default behavior of the latex url package (it uses tt typewriter font) it is easily possible to modify the font to sf class or tm/rm class, I now default to sf this means when the sisu default sf is used there will be no difference in typeface, but when times roman or other is used, urls will be in sf instead of that font, (instead of the latex default typewriter) it provides a visual cue even when output is monochrome, without color (and is in some way related to #744391 sisu output: no color on a4 portrait) however, it is worth noting here that urls are printed in a smaller font so as to fit more on a line of text Version: 5.3.5-1 (sisu v6) will contain this other fixes described in response to bug reports (5.3.5::6.0.5) (see note in bug #744378 on current Debian upload blocker) Thanks, Ralph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744355: vim syntaxhighlighting: includes and directories
* Daniel Baumann daniel.baum...@progress-technologies.net [Sun, 13 Apr 2014 12:28:46 +0200], wrote: Package: sisu Version: 5.3.4-1 Severity: wishlist When using includes like this: foo.ssi then vim correctly displays the line in blue. However, when using includes in a subdirectory like this: bar/foo.ssi then vim doesn't use any colors at all. Regards, Daniel Done Version: 5.3.5-1 will contain this other fixes described in response to bug reports (5.3.5::6.0.5) (see note in bug #744378 on current Debian upload blocker) Thanks, Ralph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744356: vim syntaxhighlighting: urls and tags
* Daniel Baumann daniel.baum...@progress-technologies.net [Sun, 13 Apr 2014 12:28:56 +0200], wrote: Package: sisu Version: 5.3.4-1 Severity: wishlist When using an URL at the end of a sentence like this: Foo bar baz http://example.org. then vim properly highlights the url in blue. this also works properly when a second sentence after it, like: Foo bar baz http://example.org. Foo bar baz http://example.org. it works with html tag as well, like this: Foo bar baz http://example.org. br /Foo bar baz http://example.org. but it doesn't work if there's no space: Foo bar baz http://example.org.br /Foo bar baz http://example.org. then, the string 'http://www.gnu.org/licenses/.' is shown red. Regards, Daniel This is meant to be flagged as an error (red indicates error, and is an error will not parse correctly and even if the sisu parser works in the flagged case there is no promise that it will in future) Use of angle bracket markers (html markers) in sisu markup is depreciated. for line-break use \\ instead, for which there should be surrounding spaces or a preceding space and end of line; If br / is still used there should be a space after the url - which sisu should remove in output. Would like to close without further action. Re-open if necessary Version: 5.3.5-1 will contain this other fixes described in response to bug reports (5.3.5::6.0.5) (see note in bug #744378 on current Debian upload blocker) Thanks, Ralph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744358: please do not add ';' after :copyright:
* Daniel Baumann daniel.baum...@progress-technologies.net [Sun, 13 Apr 2014 12:29:20 +0200], wrote: Package: sisu Version: 5.3.4-1 Severity: wishlist When using: :copyright: foo bar baz. sisu generates the following in the output format (pdf): foo bar baz.; Please do not automagically add a semicolon (;). If the user wants a semicolon, he would add one. Regards, Daniel Fix copyright, remove trailing semi-colon. Version: 5.3.5-1 will contain this other fixes described in response to bug reports (5.3.5::6.0.5) (see note in bug #744378 on current Debian upload blocker) Thanks, Ralph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744379: missing includes doesn't give an error
* Daniel Baumann daniel.baum...@progress-technologies.net [Sun, 13 Apr 2014 16:14:46 +0200], wrote: Package: sisu Version: 5.3.4-1 Severity: wishlist When using includes (*.ssi) in a sisu master document (*.ssm) like: foo.ssi and that to be included file foo.ssi (for whatever reason) doesn't exist, sisu doesn't error out but include ' foo.ssi' literally as a string in the output (pdf). Regards, Daniel 5.3.4-1 writes the following to the screen: ERROR test.ssm.sst requires invalid or non-existent file: foo.ssi and unsatisfactorily within the text output it writes no error message but the include instruction: foo.ssi 5.3.5, the current fix/ solution, is to add an error message within the text rather than to stop processing with an error. In addition to (i) slightly modified (you could say corrected) to the following: ERROR test.ssm requires an invalid or non-existent file: foo.ssi the following is written within the text output: foo.ssi [ERROR test.ssm requires an invalid or non-existent file: foo.ssi] Version: 5.3.5-1 will contain this other fixes described in response to bug reports (5.3.5::6.0.5) (see note in bug #744378 on current Debian upload blocker) Thanks, Ralph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744381: inconsistency between :copyright: and :license:
* Daniel Baumann daniel.baum...@progress-technologies.net [Sun, 13 Apr 2014 16:26:55 +0200], wrote: Package: sisu Version: 5.3.4-1 Severity: wishlist when using ':copyright: foo', then the output contains 'foo'. when using ':license: foo', then the output contains 'License: foo'. this is inconsistent. either both should have a 'prefix' in the output, or neither should have one (i'd prefere the latter). Regards, Daniel -- Address:Daniel Baumann, Donnerbuehlweg 3, CH-3012 Bern Email: daniel.baum...@progress-technologies.net Internet: http://people.progress-technologies.net/~daniel.baumann/ (thanks chose the former suggestion) Under rights there are a series of sub-categories starting with copyright, that need to be distinguished. Until now started distinguishing after after Copyright. For consistency have add the prefix 'Copyright' to the output. Preference to omit noted, but this solution is consistent with options provided. Bug (to be) closed (with upload), re-open if necessary. Version: 5.3.5-1 will contain this other fixes described in response to bug reports (5.3.5::6.0.5) (see note in bug #744378 on current Debian upload blocker) Thanks, Ralph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744386: sisu syntax: 1~ and 2~ result in the same formatting
* Daniel Baumann daniel.baum...@progress-technologies.net [Sun, 13 Apr 2014 16:43:51 +0200], wrote: Package: sisu Version: 5.3.4-1 Severity: wishlist similar as with #744383, the same also applies for 1~ and 2~ - they should be different in the output format (pdf here). Regards, Daniel 1~ 2~ 3~ are now differentiated Version: 5.3.5-1 (sisu v6) will contain this other fixes described in response to bug reports (5.3.5::6.0.5) (see note in bug #744378 on current Debian upload blocker) Thanks, Ralph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744391: sisu output: please use (blue) color for links
* Daniel Baumann daniel.baum...@progress-technologies.net [Sun, 13 Apr 2014 17:35:33 +0200], wrote: retitle 744391 sisu output: no color on a4 portrait thanks now this is strange.. turns out that (yes, i have colors enabled in sisurc) the portrait a4 pdf has no colors at all, while the landscape a4 pdf does indeed have colors (red for toc, blue for links). Regards, Daniel background: portrait was provided for print/paper copy and is great for that in monochrome (without grays for colored links), landscape better matching a screen for visual presentations, color affecting the landscape only solution: make configurable by cli rc file make both (portrait landscape colors) configurable either as hyperlinks monochrome or colored overriding existing default which remains as described document cli: --pdf-hyperlinks-no-color or --pdf-hyperlinks-mono --pdf-hyperlinks-color rc: default: pdf_hyperlinks: *[possible values] pdf_hyperlinks_portrait: *[possible values] pdf_hyperlinks_landscape: *[possible values] * 'color' or ('mono' or 'no-color' or 'color-off') Version: 5.3.5-1 (sisu v6) will contain this other fixes described in response to bug reports (5.3.5::6.0.5) (see note in bug #744378 on current Debian upload blocker) Thanks, Ralph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744402: sisu: support sha512
* Daniel Baumann daniel.baum...@progress-technologies.net [Sun, 13 Apr 2014 18:06:56 +0200], wrote: Package: sisu Version: 5.3.4-1 Severity: wishlist Tags: upstream sisu uses sha256 when using sha as digest, please support sha512. it would be even nicer if you could specify the actual digest like 'sha512', 'sha256', etc. rather than just 'sha'. Regards, Daniel Implemented (document command line option --sha512) Version: 5.3.5-1 (sisu v6) will contain this other fixes described in response to bug reports (5.3.5::6.0.5) (see note in bug #744378 on current Debian upload blocker) Thanks, Ralph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744383: sisu syntax: :B and :C result in the same formatting
* Daniel Baumann daniel.baum...@progress-technologies.net [Sun, 13 Apr 2014 16:32:07 +0200], wrote: Package: sisu Version: 5.3.4-1 Severity: wishlist when using :A, :B, and :C in sisu, in the output (pdf) both :B and :C are formatted identically. imho :C should be 'smaller' than :B. or, as an analogy with html: i would expect that :A equals h1, :B equals h2, and :C equals h3. currently, (in that analogy), :B and :C both equal h2. Regards, Daniel (for pdf) now is same size (rather than larger and plan to close bug) see #744383 latex sisu \part (level A B C D) \chapter (skipped) \section (level 1) \subsection(level 2) \subsubsection (level 3) Version: 5.3.5-1 (sisu v6) will contain this other fixes described in response to bug reports (5.3.5::6.0.5) (see note in bug #744378 on current Debian upload blocker) -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744405: sisu: set default font size
* Daniel Baumann daniel.baum...@progress-technologies.net [Sun, 13 Apr 2014 18:29:46 +0200], wrote: Package: sisu Version: 5.3.4-1 Severity: wishlist Tags: upstream in sisurc, one can set the default fonts. it would be nice to be also able to set the default font size. Regards, Daniel For pdf make configurable, done yaml.rc default: texpdf_fontsize: 12 command-line --pdf-fontsize-12 --pdf-fontsize-8 etc. (no fractions) Version: 5.3.5-1 (sisu v6) will contain this other fixes described in response to bug reports (5.3.5::6.0.5) (see note in bug #744378 on current Debian upload blocker) Thanks, Ralph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744383: sisu syntax: :B and :C result in the same formatting
* Daniel Baumann daniel.baum...@progress-technologies.net [Sun, 13 Apr 2014 16:32:07 +0200], wrote: Package: sisu Version: 5.3.4-1 Severity: wishlist when using :A, :B, and :C in sisu, in the output (pdf) both :B and :C are formatted identically. imho :C should be 'smaller' than :B. or, as an analogy with html: i would expect that :A equals h1, :B equals h2, and :C equals h3. currently, (in that analogy), :B and :C both equal h2. Regards, Daniel This is in part an artifact of LaTeX defaults not having as many document heading levels and trying to take advantage of the behavior of existing levels rather than customising further. Look for a solution, possibly overriding the default font sizes for each. The current settings were chosen because, there are not enough levels and I find too many different font sizes disconcerting, especially running sisu over a wide variety of document types. The following levels are available in LaTeX \part \chapter \section \subsection \subsubsection The levels in sisu are A [title] B [part] C [subpart] D [subsubpart] 1 [segment (chapter)] 2 [subsegment] 3 [subsubsegment] sisu current mapping: level A[title] level B C D\part (it is up to the user to make part levels visually distinguishable e.g. Book Part Section) [skipped \chapter] [skipped \section] level 1\subsection level 2\subsubsection level 3\subsubsection The reason for skipping section was the default configuration and resulting fact that it made for a table of contents that takes more space sisu new mapping: level A[title] level B C D\part (it is up to the user to make part levels visually distinguishable e.g. Book Part Section) [skipped \chapter] level 1\section level 2\subsection level 3\subsubsection levels B C D are the same size, it is up to the user to make part levels visually distinguishable e.g. Book Part Section Levels 1 2 3 are now distinguished Fixed (#744386) sisu syntax: 1~ and 2~ result in the same formatting (under consideration yet to be done #744383) sisu syntax: :B and :C result in the same formatting Version: 5.3.5-1 (sisu v6) will contain this partial fix other fixes described in response to bug reports (5.3.5::6.0.5) (see note in bug #744378 on current Debian upload blocker) Thanks, Ralph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744384: sisu syntax: relies on empty lines
* Daniel Baumann daniel.baum...@progress-technologies.net [Sun, 13 Apr 2014 16:34:46 +0200], wrote: Package: sisu Version: 5.3.4-1 Severity: wishlist the following snipped: :C~ foo bar foo-bar.ssi means that the include is ignored entirely. apparently sisu relies on having an empty line in between like this: :C~ foo bar foo-bar.ssi Regards, Daniel Will consider but not likely to implement. (i) as a general observation, sisu relies on emptly lines to identify separate objects such as headings, paragraphs (and indeed insertions) (ii) a heading need not be on a single line (so would be part of that heading) this means sisu should be able to work identifying headings in wrapped texts (e.g. where the text is wrapped at 80 and the heading is longer than that) There has been no rule to the contrary (i.e. that headings should be on a single text line) Consider, should there be such a rule? For now at least I prefer the existing state. Thanks, Ralph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#736699: O: diakonos
Package: wnpp Severity: normal This package has not had the attention it deserves. I lack the time, the modest development time I have being taken fully by sisu. Diakonos is a neat console text editor written in ruby. As a vim user I have never really used it. I hope someone finds it useful and is able to pick it up. Ralph Amissah -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#736700: O: rant
Package: wnpp Severity: normal rant is a ruby make tool similar to rake. Perhaps too similar, as rake was the original (ruby make) implementation. There appears to be little activity upstream. I lack the time to maintain it. Family commitments. The modest development time I have being taken by sisu. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#735585: sisu: please do not depend on rubygems and depend on ruby | ruby-interpreter
* Cédric Boutillier bou...@debian.org [Fri, 17 Jan 2014 14:18:26 +0100], wrote: Package: sisu Followup-For: Bug #735585 Dear Maintainer, The changes to make it run with the default interpreter (ruby1.9.1 is going away at some point before jessie) are a bit larger than the ones I mentionned in my previous patch. Please find attached a debdiff fixing this issue. Unless you say otherwise, I consider sending an NMU next week to DELAYED/5 to fix this problem and be able to remove rubygems. Thanks! Cédric Dear Cédric, Thank you very much. It is very helpful to have you look into sisu debian packaging and provide fixes. I believe these have now been incorporated in the latest release of sisu 4.2.19 (which makes the claim that these particular bugs are closed). Please note though that sisu has not been tested with other ruby interpreters, so other issues are likely to arise. I welcome your feedback. Sincerely, Ralph signature.asc Description: Digital signature
Bug#735671: sisu: please remove unbreakable spaces in debian/sources/options
* Cédric Boutillier bou...@debian.org [Fri, 17 Jan 2014 12:12:25 +0100], wrote: Package: sisu Severity: wishlist The debian/source/options file contains (I believe by error) unbreakable spaces around the equal sign. They are causing dpkg to raise a warning: dpkg-source: warning: --compression�=�xz is not a valid option for Dpkg::Source::Package::V3::Quilt Cédric Thanks, done. ralph signature.asc Description: Digital signature
Bug#722403: sisu: Depend on fonts-liberation instead of ttf-liberation
* Jeremy Bicha jbi...@ubuntu.com [Tue, 10 Sep 2013 13:40:07 -0400], wrote: Package: sisu Version: 4.2.3-1 User: ubuntu-de...@lists.ubuntu.com Usertags: origin-ubuntu saucy Please depend on fonts-liberation instead of ttf-liberation as the latest release of fonts-liberation in unstable has dropped the transitional ttf-liberation package. Thanks, Jeremy Thank you for the bug report. Will fix and close immediately. Thanks again, Ralph signature.asc Description: Digital signature
Bug#699541: Maintainer address bounces
* Luca Falavigna dktrkr...@debian.org [Fri, 01 Feb 2013 15:33:37 +0100], wrote: Package: sisu,sisu-markup-samples Version: sisu/3.3.2-1 Version: sisu-markup-samples/4.0.0-1 Severity: serious Tags: sid Maintainer address bounces with the following error: A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: s...@lists.sisudoc.org retry timeout exceeded ra...@amissah.com retry timeout exceeded It will be fixed within a few days (a week or so). (Had hoped to wait for updates for Wheezy, a bit, recursive). I do get bug related mail here for the time being, and am fairly responsive. signature.asc Description: Digital signature
Bug#620748: [sisu-pdf] hyphenation problem building manual
Chals, * Ralph Amissah ralph.amis...@gmail.com [Tue, 05 Apr 2011 11:36:00 -0400], wrote: chals, thanks for the bug report (and sorry i missed you online yesterday) Line breaking and line-justification the smooth right text margin are determined by latex/texlive according to parameters it is given. The trick for us is to come up with a (generic) solution that works decently over as wide a body of documents as possible. To decide line-breaking, LaTeX uses: (a) the language setting; (b) a sloppy value; (c) additionally provided hyphenation points. There may be additional things, and I am not necessarily using the right LaTeX terminology. May I close this bug? (would mark done as of 3.1.0, I do not find that I tweaked the sloppy value though) Ralph signature.asc Description: Digital signature
Bug#665067: live-manual: FTBFS: wc: live-manual.ssm.sst: No such file or directory
I Hope I claimed this bug too quickly.[*] Unless otherwise directed I will not obstruct the transition of sisu 3.2.0 to testing. Thanks, Ralph PS the Washington DC cherry blossom were lovely in great weather (last Friday, and much depleted by very wet weather on Saturday :) [*] it was not posted to and has not been moved to sisu; and I have not run into it (on my non-AMD laptop). * Ralph Amissah ralph.amis...@gmail.com [Thu, 22 Mar 2012 13:44:56 -0400], wrote: On Thu, Mar 22, 2012 at 8:23 AM, Lucas Nussbaum lu...@lucas-nussbaum.net wrote: Source: live-manual Version: 1:3.0~a10-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120321 qa-ftbfs Justification: FTBFS on amd64 This bug should (almost certainly) be forwarded to sisu. almost certainly because I am not in a possition to test properly at the moment. I am without my development machine until at least Tuesday (which is in for repairs), and off shortly on a family trip to Washington DC to see the cherry blossom (without a computer)... Will make sure sisu 3.2 series does not hit testing till this is fixed; will start looking, and hope to come up with a fix (as soon as my laptop is up and running) next week. I won't be able to do any follow up, mail etc. until we return ( that is late Sunday). Sorry for the inconvenience. Ralph -- Ralph Amissah (ralph on irc.oftc.net) GPG fp: A5F9 C48C 4059 B688 6CC5 7A42 6F78 18A9 B98F 62B1 * GPG fp: 9267 6F8D E64B CD4B 4880 482E E4AF EBC6 1BB4 B289 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#665067: live-manual: FTBFS: wc: live-manual.ssm.sst: No such file or directory
On Thu, Mar 22, 2012 at 8:23 AM, Lucas Nussbaum lu...@lucas-nussbaum.net wrote: Source: live-manual Version: 1:3.0~a10-1 Severity: serious Tags: wheezy sid User: debian...@lists.debian.org Usertags: qa-ftbfs-20120321 qa-ftbfs Justification: FTBFS on amd64 This bug should (almost certainly) be forwarded to sisu. almost certainly because I am not in a possition to test properly at the moment. I am without my development machine until at least Tuesday (which is in for repairs), and off shortly on a family trip to Washington DC to see the cherry blossom (without a computer)... Will make sure sisu 3.2 series does not hit testing till this is fixed; will start looking, and hope to come up with a fix (as soon as my laptop is up and running) next week. I won't be able to do any follow up, mail etc. until we return ( that is late Sunday). Sorry for the inconvenience. Ralph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#617298: sisu: undocumented br command in example files
* Jonas Stein n...@jonasstein.de [Mon, 07 Mar 2011 22:57:45 +0100], wrote: Package: sisu Version: 3.0.1-1 Severity: normal /usr/share/doc/sisu/v3/markup-samples/samples/de$ grep br * |wc -l shows br is used 6 times. I could not find br in the sisu manual. br has not been documented because, there has been no intention for it to be or to keep it as part of sisu markup; but it was indeed the way to break a line in a paragraph object if that was needed, and; it was used because though it did not fit aesthetically most people familiar with markup were likely to recognise it if they came across it, but; true it was not readily available to them if needed without digging into document samples. In sisu 3.0.13 I have opted to use a pair of backslashes preceded by a space and followed by a space or newline (\n character) ' \\ ' for line-breaks within a paragraph (similar to an option available in LaTeX) (in sisu grouped objects, you would just use a newline) and made an effort to mention in the documentation under sisu_markup. So, br never documented is still available, but depreciated. SiSU markup samples/examples will be switching from br wherever used to \\ I had thought that I might be able to close this bug report with that, (and made mention of it in the debian changelogs) but your mention of odt that follows, means it will remain open for some time to come: this example http://paste.debian.net/109930/ had missing whitespace version.This and details.You after sisu-odt in the Openoffice Document. (Opened it with OpenOffice.org 3.2.1) is br a proper Sisu command and sisu-odt fails, or is there an error in the example? (It is unlikely that there is an error in the example). There is indeed a bug (that remains) in sisu generated odt output with regard to this (placing a line-break within a paragraph object). A while back I believe br / worked within an odt paragraph. It stopped doing so and I have not resolved the issue. It probably can be instructed to do so again (else will have to break the odt paragraph without paragraph spacing, have a new paragraph start that is defined to look like a line-break within one paragraph). (actually have not had the chance to look at it). Not sure when this will be resolved (or what will be used as an alternative demarcation for odt until resolved). I will report back here when able to get back to it. kind regards. Sorry for the delayed response (I hoped to have alternative markup when I posted the answer, and indeed partly as a result now have, thanks); sorry the matter reported is not yet resolved in odt. Thank you, Ralph Amissah -- Ralph Amissah (ralph on irc.oftc.net) GPG fp: A5F9 C48C 4059 B688 6CC5 7A42 6F78 18A9 B98F 62B1 * GPG fp: 9267 6F8D E64B CD4B 4880 482E E4AF EBC6 1BB4 B289 signature.asc Description: Digital signature
Bug#619041: sisu: more broken links follow here
* Jonas Stein n...@jonasstein.de [Sun, 20 Mar 2011 19:46:33 +0100], wrote: Package: sisu Version: 3.0.1-1 Followup-For: Bug #619041 $ find -L /usr/share/doc/sisu -not \( -type d -path '/dev' -prune \) -type l -ls | nl 1 4528250 lrwxrwxrwx 1 root root 19 Mar 2 15:11 /usr/share/doc/sisu/v2/markup-samples/sisu_manual/_sisu/skin/dir/skin_sisu.rb - ../doc/skin_sisu.rb 2 4528240 lrwxrwxrwx 1 root root 25 Mar 2 15:11 /usr/share/doc/sisu/v2/html/index.html - ../sisu_manual/index.html 3 4528230 lrwxrwxrwx 1 root root 20 Mar 2 15:11 /usr/share/doc/sisu/v2/html/_sisu - ../sisu_manual/_sisu 4 4609170 lrwxrwxrwx 1 root root 19 Mar 2 15:11 /usr/share/doc/sisu/v3/markup-samples/sisu_manual/_sisu/skin/dir/skin_sisu.rb - ../doc/skin_sisu.rb 5 4528270 lrwxrwxrwx 1 root root 25 Mar 2 15:11 /usr/share/doc/sisu/v3/html/index.html - ../sisu_manual/index.html 6 4528260 lrwxrwxrwx 1 root root 20 Mar 2 15:11 /usr/share/doc/sisu/v3/html/_sisu - ../sisu_manual/_sisu Thank you for your bug reports on documentation (#616101 #617297 #617365 #619041). They resulted in at an overdue look at links and references in the manuals and help files and an attempt at correcting them in sisu-3.0.2 3.0.3 through updates, removals and general cleaning. These bugs should have been taken care of in sisu 3.0.2 to 3.0.4, (though documentation leaves a lot to be desired (and I hope new bugs were not introduced ... there are likely to be new issues to clear up with the alternative output paths available in v3)). For now unless you suggest otherwise, I plan to close this bug in 10 days. -- Ralph Amissah (ralph on irc.oftc.net) GPG fp: A5F9 C48C 4059 B688 6CC5 7A42 6F78 18A9 B98F 62B1 * GPG fp: 9267 6F8D E64B CD4B 4880 482E E4AF EBC6 1BB4 B289 signature.asc Description: Digital signature
Bug#616101: man sisu: broken links in manpage
* Jonas Stein n...@jonasstein.de [Wed, 02 Mar 2011 15:23:59 +0100], wrote: Package: sisu Version: 3.0.1-1 Severity: normal there are several broken links in the manpage one example: http://www.jus.uio.no/sisu/sample/on_markup.txt Thank you for your bug reports on documentation (#616101 #617297 #617365 #619041). They resulted in at an overdue look at links and references in the manuals and help files and an attempt at correcting them in sisu-3.0.2 3.0.3 through updates, removals and general cleaning. These bugs should have been taken care of in sisu 3.0.2 to 3.0.4, (though documentation leaves a lot to be desired (and I hope new bugs were not introduced ... there are likely to be new issues to clear up with the alternative output paths available in v3)). For now unless you suggest otherwise, I plan to close this bug in 10 days. -- Ralph Amissah (ralph on irc.oftc.net) GPG fp: A5F9 C48C 4059 B688 6CC5 7A42 6F78 18A9 B98F 62B1 * GPG fp: 9267 6F8D E64B CD4B 4880 482E E4AF EBC6 1BB4 B289 signature.asc Description: Digital signature
Bug#617297: wrong path in sisu --help markup
* Jonas Stein n...@jonasstein.de [Mon, 07 Mar 2011 22:46:25 +0100], wrote: Package: sisu Version: 3.0.1-1 Severity: normal $ sisu --help markup returns = .. .. sample marked up documents are provided in directory: sisu-examples/sample/document_samples_sisu_markup/ .. = cd sisu-examples/sample/document_samples_sisu_markup/ fails (this path does not exist here) perhaps /usr/local/doc/ or similar is missing Thank you for your bug reports on documentation (#616101 #617297 #617365 #619041). They resulted in at an overdue look at links and references in the manuals and help files and an attempt at correcting them in sisu-3.0.2 3.0.3 through updates, removals and general cleaning. These bugs should have been taken care of in sisu 3.0.2 to 3.0.4, (though documentation leaves a lot to be desired (and I hope new bugs were not introduced ... there are likely to be new issues to clear up with the alternative output paths available in v3)). For now unless you suggest otherwise, I plan to close this bug in 10 days. -- Ralph Amissah (ralph on irc.oftc.net) GPG fp: A5F9 C48C 4059 B688 6CC5 7A42 6F78 18A9 B98F 62B1 * GPG fp: 9267 6F8D E64B CD4B 4880 482E E4AF EBC6 1BB4 B289 signature.asc Description: Digital signature
Bug#617365: man sisu: there is no sisu_help
* Jonas Stein n...@jonasstein.de [Tue, 08 Mar 2011 14:30:58 +0100], wrote: Package: sisu Version: 3.0.1-1 Severity: normal man sisu: = 4. HELP SOURCES For a summary of alternative ways to get help on SiSU try one of the following: man page man sisu_help = $ man sisu_help No manual entry for sisu_help Thank you for your bug reports on documentation (#616101 #617297 #617365 #619041). They resulted in at an overdue look at links and references in the manuals and help files and an attempt at correcting them in sisu-3.0.2 3.0.3 through updates, removals and general cleaning. These bugs should have been taken care of in sisu 3.0.2 to 3.0.4, (though documentation leaves a lot to be desired (and I hope new bugs were not introduced ... there are likely to be new issues to clear up with the alternative output paths available in v3)). For now unless you suggest otherwise, I plan to close this bug in 10 days. -- Ralph Amissah (ralph on irc.oftc.net) GPG fp: A5F9 C48C 4059 B688 6CC5 7A42 6F78 18A9 B98F 62B1 * GPG fp: 9267 6F8D E64B CD4B 4880 482E E4AF EBC6 1BB4 B289 signature.asc Description: Digital signature
Bug#627625: installation of sisu without installation of db server
Thanks for your report(s). * Jonas Stein n...@jonasstein.de [Sun, 22 May 2011 23:13:28 +0200], wrote: Package: sisu Severity: wishlist i think sisu can work without sql server. you are correct Selecting 'sisu' and 'sisu-pdf' suggests 'sisu-postgresql' In some environments its forbidden to install a db server, but it might be allowed to run a local sisu text converter. So it would be nice to install sisu without any sql deamons/server after selecting 'sisu'. Selecting sisu does 'recommend' the other possible sisu dependencies, including 'sisu-postgresql': apt-cache show sisu In addition to the packages sisu depends on, sisu recommends and suggests some other packages that are not depended on. These additional packages may be useful to use in some circumstances with sisu but are not required/depended on. sisu, sisu-postgresql, sisu-pdf etc. are packaged separately for the reason you mention, in some environments it may not be desirable to pull in the additional dependencies. All code related to sisu is contained in the package sisu, that is, the package sisu contains everything except the dependencies to the larger engines that sisu can use for specific purposes - xetex for pdf; postgresql for search etc. (this means that the package sisu is able to produce latex and all else it would need to populate an sql database for granular search, without the actual xetex engine or database drivers and engine respectively) i.e. sisu-pdf pulls in xetex; sisu-postgresql pulls in postgresql and related drivers (nothing else being added to sisu code). This is I believe what you want and request - the separate packaging of large engines that though sisu uses for certain purposes it does not necessarily have to have... and I believe the way with a debian package to achieve what you request, and be helpful about informing users that fuller utility of the program might be achieved by installing additional packages (that you do not have to install). I hope this explanation is (correct and) satisfactory. I would like to close this bug in the next 10 days. I hope this is ok with you. Ralph Amissah P.S. Sorry for the delay in this response, in this case I (in a rush these days as usual) misread your exchange on irc and mistakenly thought the problem mentioned originated from chals, and explained to chals at a time when you may not have been present. The exchange suggests that you ended up with postgresql (or perhaps with postgresql being updated?) and did not want it. If that is the case you may wish to check the configuration of you apt tool. -- Ralph Amissah (ralph on irc.oftc.net) GPG fp: A5F9 C48C 4059 B688 6CC5 7A42 6F78 18A9 B98F 62B1 * GPG fp: 9267 6F8D E64B CD4B 4880 482E E4AF EBC6 1BB4 B289 signature.asc Description: Digital signature
Bug#622171: sisu: --color flag, which toggles color on/off
* Jonas Stein n...@jonasstein.de [Sun, 10 Apr 2011 19:21:49 +0200], wrote: Package: sisu Version: 3.0.4-1 Severity: wishlist IRC #sisu 16:26 ralph for bug report outputs might help to incorporate -c flag, which toggles color on/off (in this case off) 19:16 jstein i suggest --color like in the ls command 19:17 jstein its nice if widely known commands work similar i hope its ok to post a wishlist for it now. sure ... will take time to implement. (Time is occupied with getting version 3 to a usable state and then ironing out a number of version 3 related things). I thought about it and my preference would be that --color turned color on (rather than switched from what had been configured to the opposite), and something like --color-off turned color off. For now what has been implemented (in response to your wishlist bug) is the switch --color-toggle, which does exactly the on off toggle (depending on whether color is configured to be on or off) that -c does. Whilst not so widely known as --color, it is easily found in the man page (alphabetically where you would look for to find --color). Sorry it is not exactly your wish ... that may come in time. Thank you, Ralph Amissah -- Ralph Amissah (ralph on irc.oftc.net) GPG fp: A5F9 C48C 4059 B688 6CC5 7A42 6F78 18A9 B98F 62B1 * GPG fp: 9267 6F8D E64B CD4B 4880 482E E4AF EBC6 1BB4 B289 signature.asc Description: Digital signature
Bug#619068: typo: Bul garian
* Jonas Stein n...@jonasstein.de [Sun, 20 Mar 2011 23:11:25 +0100], wrote: Package: sisu Version: 3.0.1-1 Severity: wishlist http://sisudoc.org/sisu/sisu_markup/headers.html bg - Bul garian ) = bg - Bulgarian) Thanks, expect this to be fixed and closed in next version of sisu released. Apologies for the delay. Ralph Amissah -- Ralph Amissah (ralph on irc.oftc.net) GPG fp: A5F9 C48C 4059 B688 6CC5 7A42 6F78 18A9 B98F 62B1 * GPG fp: 9267 6F8D E64B CD4B 4880 482E E4AF EBC6 1BB4 B289 signature.asc Description: Digital signature
Bug#622902: sisu: Unclear how to get latex output
* Harald Geyer har...@ccbib.org [Fri, 15 Apr 2011 19:34:49 +0200], wrote: Package: sisu Version: 2.7.9-1 Severity: normal The package description and the man page both claim that sisu can produce latex code. But from the documentation I don't see how to call sisu to actually get there. If I try to generate PDF output then latex code probably gets generated in some temporary file, but gets deleted afterwards. this is correct. Notes: 1. if you wish to keep the .tex file pass the maintenance flag, and interim processing files are kept, you would run sisu -pM filename.sst or sisu --maintenace --pdf filename.sst this should also provide information as to where the interim processing files are located 2. it is possible to change where processing is done, if you do not wish that this occurs in /tmp..., to do so you would need to edit the sisurc.yml file under processing: path: dir: (should be better documented) 3. the tex files are generated whether or not the texlive depends needed to actually generate the pdf placed in sisu-pdf are actually installed or not. In the event that they are not, the tex files would be created (and destroyed without the maintenance flag) but they would not be processed. Sorry if I'm missing something obvious. You did not: the man page description of the maintenance flag should be clearer, and; even if it were, it is not so obvious that such a flag would exist or what it would be called ... (to get from how to generate a particular output type to knowing how to keep the interim processing files). Will try improve man page description of the maintenance flag and close this bug. Thanks, Ralph -- Ralph Amissah (ralph on irc.oftc.net) GPG fp: A5F9 C48C 4059 B688 6CC5 7A42 6F78 18A9 B98F 62B1 * GPG fp: 9267 6F8D E64B CD4B 4880 482E E4AF EBC6 1BB4 B289 signature.asc Description: Digital signature
Bug#620748: [sisu-pdf] hyphenation problem building manual
chals, thanks for the bug report (and sorry i missed you online yesterday) Line breaking and line-justification the smooth right text margin are determined by latex/texlive according to parameters it is given. The trick for us is to come up with a (generic) solution that works decently over as wide a body of documents as possible. To decide line-breaking, LaTeX uses: (a) the language setting; (b) a sloppy value; (c) additionally provided hyphenation points. There may be additional things, and I am not necessarily using the right LaTeX terminology. (a) the language setting (provided and) is almost certainly not relevant in this case. (b) The sloppy value, gives the degree of flexibility in spreading words along the line to have a flush right margin. (In very the worst case (i can imagine) you might have two short words, one at the start of the line the other at the end; the more words that fit neatly with the optimum spacing the cleaner the text.) Here there is scope for problems to arise as they have in your text. The sloppy value has already been increased considerably above the default acceptable value. Increasing it even more may solve the problem, but could also result in generally less (or unattractive) spacing to achieve justification. Some options are (i) to increase the value generally; (ii) to increase the value for the landscape column text where there is less space in which latex can find a convenient break-point; (iii) provide a header option in sisu where an alternative value may be passed to LaTeX for a given text. (c) Line break-points could be added for directory paths on for example forward slash and hyphens. This would result in more frequent breaks on directory paths, and some ambiguity in interpreting path re. the hyphens used, whether to add them in making up the path or not. (I believe sisu currently provides such breaks for urls though, because they are often even longer than directory paths (and even more frequently created problems), and in that case the link is provided) I will experiment a bit more with the tweaking of sloppy values. Feedback is also welcome if there are promising alternatives to the current settings. As said, this is unlikely ever to work in all cases (with a generally acceptable presentation). Also opinions on (sisu) providing hyphenation points (to LaTeX) for directory paths (something that has been deliberately avoided so far) is welcome. Any attempt at an improved solution will take some time. Thanks, Ralph P.S. (thanks for your previous informal bug-report, received through Ben Armstrong (on irc), about pdf output crashing where a name-tag is not found. It resulted in a couple of solutions to the problem, one of them implemented so far.) -- Ralph Amissah (ralph on irc.oftc.net) GPG fp: A5F9 C48C 4059 B688 6CC5 7A42 6F78 18A9 B98F 62B1 * GPG fp: 9267 6F8D E64B CD4B 4880 482E E4AF EBC6 1BB4 B289 signature.asc Description: Digital signature
Bug#616706: debian/watch file is out of date
Thank you for the updated watch file. It is worth having it fixed. I will rebuild the package shortly. There appears not to be much activity upstream, but that is a side issue, what good is a watch file that does not watch; it would be better not to have one at all. Thanks, Ralph -- Ralph Amissah (ralph on irc.oftc.net) GPG fp: A5F9 C48C 4059 B688 6CC5 7A42 6F78 18A9 B98F 62B1 * GPG fp: 9267 6F8D E64B CD4B 4880 482E E4AF EBC6 1BB4 B289 signature.asc Description: Digital signature
Bug#616101: man sisu: broken links in manpage
* Jonas Stein n...@jonasstein.de [Wed, 02 Mar 2011 15:23:59 +0100], wrote: Package: sisu Version: 3.0.1-1 Severity: normal there are several broken links in the manpage one example: http://www.jus.uio.no/sisu/sample/on_markup.txt Thank you for the bug report, it got me looking at links in the documentation related pages, which themselves need to be reviewed. I am not yet confident that all link issues have been addressed. The one given by you as an example should hopefully have been removed. -- Ralph Amissah (ralph on irc.oftc.net) GPG fp: A5F9 C48C 4059 B688 6CC5 7A42 6F78 18A9 B98F 62B1 * GPG fp: 9267 6F8D E64B CD4B 4880 482E E4AF EBC6 1BB4 B289 signature.asc Description: Digital signature
Bug#617621: FR: description environment
* Jonas Stein n...@jonasstein.de [Thu, 10 Mar 2011 01:31:48 +0100], wrote: Package: sisu Version: 3.0.1-1 Severity: wishlist it would be nice to have a description environment (item) like in LaTeX \begin{description} Thanks, noted (and thank you for the clarification you gave on irc/oftc). Will look into a bit further. It is likely to be a considerable while before a more specialised option is implemented. Very generic tools for markup are provided that usually work across all output types. At present focus is on getting output modules for version 3 implemented, a number of which have not yet been tackled and version 3 is targeted to be ready in time for Wheezy. All that said, if a hanging indent is sufficient, and of need to a lot of users, an attempt may be made to implement that (possibly after version 3 is in place). Thank you, Ralph -- Ralph Amissah (ralph on irc.oftc.net) GPG fp: A5F9 C48C 4059 B688 6CC5 7A42 6F78 18A9 B98F 62B1 * GPG fp: 9267 6F8D E64B CD4B 4880 482E E4AF EBC6 1BB4 B289 signature.asc Description: Digital signature
Bug#617379: sisu: markup version declared (3.0) is newer than SiSU version (2.8.0)
* Jonas Stein n...@jonasstein.de [Tue, 08 Mar 2011 15:43:19 +0100], wrote: Package: sisu Version: 3.0.1-1 Severity: normal i have put % SiSU 3.0 in the headline now sisu-pdf claims Warning: markup version determined (2.0) or markup version declared (3.0) is newer than SiSU version (2.8.0) but sisu is v3 $ aptitude show sisu | grep Version Version: 3.0.1-1 Jonas, thank you for the bug report. Best for now the headline be kept to SiSU 2.0, the markup has not changed between v2 and v3, and the default interpreter run is version 2 (try sisu -v on its own), not version 3 (which is available in the package for testing (sisu --v3 or sisu3) and hopefully due (as the default replacing version 2) in time for Wheezy). Thanks, Ralph -- Ralph Amissah (ralph on irc.oftc.net) GPG fp: A5F9 C48C 4059 B688 6CC5 7A42 6F78 18A9 B98F 62B1 * GPG fp: 9267 6F8D E64B CD4B 4880 482E E4AF EBC6 1BB4 B289 signature.asc Description: Digital signature
Bug#617365: man sisu: there is no sisu_help
* Jonas Stein n...@jonasstein.de [Tue, 08 Mar 2011 14:30:58 +0100], wrote: Package: sisu Version: 3.0.1-1 Severity: normal man sisu: = 4. HELP SOURCES For a summary of alternative ways to get help on SiSU try one of the following: man page man sisu_help = $ man sisu_help No manual entry for sisu_help Jonas, thanks man sisu_help is not longer available and references to it should (now) have been removed from the documentation. Ralph -- Ralph Amissah (ralph on irc.oftc.net) GPG fp: A5F9 C48C 4059 B688 6CC5 7A42 6F78 18A9 B98F 62B1 * GPG fp: 9267 6F8D E64B CD4B 4880 482E E4AF EBC6 1BB4 B289 signature.asc Description: Digital signature
Bug#617297: wrong path in sisu --help markup
* Jonas Stein n...@jonasstein.de [Mon, 07 Mar 2011 22:46:25 +0100], wrote: Package: sisu Version: 3.0.1-1 Severity: normal $ sisu --help markup returns = .. .. sample marked up documents are provided in directory: sisu-examples/sample/document_samples_sisu_markup/ .. = cd sisu-examples/sample/document_samples_sisu_markup/ fails (this path does not exist here) perhaps /usr/local/doc/ or similar is missing Jonas, thank you, in response to your bug report that particular path should have been corrected in the now current version of the program sisu-3.0.4 Ralph -- Ralph Amissah (ralph on irc.oftc.net) GPG fp: A5F9 C48C 4059 B688 6CC5 7A42 6F78 18A9 B98F 62B1 * GPG fp: 9267 6F8D E64B CD4B 4880 482E E4AF EBC6 1BB4 B289 signature.asc Description: Digital signature
Bug#597953: ruby1.9.1: segfaults on a number of sisu operations
Fixed upstream ruby1.9.2p180 I have done a little testing with RVM (Ruby Version Manager) and more recent versions of ruby1.9.2 (ruby1.9.2p180), and can report that the segfault problems appear to be fixed in upstream builds of ruby. This bug was present in earlier upstream builds of ruby1.9.2, though I am not certain with which build the issues reported here were cured. One of the problems appears at least to have been with the new garbage collector. But there were quite likely others. Anyhow, I hope this is the case (re: the fix), and look forward to developing for ruby1.9.2 on Debian soon :) Thanks, Ralph Amissah P.S. for sisulist cc. note that ruby1.9.1 branch in Debian is currently ruby1.9.2p0 (and the same in Squeeze). Debian bug report at: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=597953 -- Ralph Amissah (ralph on irc.oftc.net) GPG fp: A5F9 C48C 4059 B688 6CC5 7A42 6F78 18A9 B98F 62B1 * GPG fp: 9267 6F8D E64B CD4B 4880 482E E4AF EBC6 1BB4 B289 signature.asc Description: Digital signature
Bug#606337: po4a: [text] Add support for SiSU markup
I spoke to Ben Armstrong and we agreed that I should post a follow-up message. (a) as far as I know, the no-wrap bug in sisu related to bulleted text has been resolved in sisu upstream, (and live-manual is already using that, and the patch should not be necessary at this time; if this is not the case, please feel free to correct me.) (b) Unknown to Ben or anyone else, I have been working on (read experimenting) with sisu to po4a output, (based on a few documents for which I have at least partial translations). It either reads a source file and generates a pot of the source with empty translation fields, or; reads in two sisu markup files, the source language and the translation file, and generates a po file for that language. Various text blocks types are identified and marked as such vis. regular paragraph, bulleted text, indented text, headings, tables, grouped text, code blocks, footnotes, book index tags and so on... at this stage I am experimenting with what might be done. The idea being that if text blocks are identified and po4a can be deal with them to produce sisu files, generation of po4a and sisu files should be bi-directional. Work is not complete on this pot file generator, and it is still early to determine how successful it will be, but working on it this way gives the opportunity to tease out what can be done. Most of logical separation of parts being made for the pot file is done with the view to make its use more straightforward for the translator. Once I have something that works, I would hope to share it with the po4a team, so they can provide feedback as to what else might need to be done with respect to sisu po4a output; and what po4a can make of it. I have been content to plod on quietly offline as this is post Squeeze work. Early notes: For most but not all text block types line-wrapped text is perfectly acceptable (text-block types are described as text objects in sisu, I have not yet familiarised myself with po4a lingo) e.g. paragraphs, bulleted text (after today's bugfix), indented text, headings, footnotes. But not for example for code blocks, tables (or at present book index tags). The list will be more comprehensive when the code is complete, as block type is identified. Special treatment would also be required for book index tags (which in producing the sisu document should be attached unwrapped to the preceding text block, rather than with an empty line as other text blocks require); Footnotes have also been taken out of the main text, and follow the code block to which they belong (this resulting in un-interrupted regular text and footnotes, that should be easier on the translators eye) - sisu is able to deal with this markup form, though it would be wonderful if the document that is rebuilt by po4a could contain the footnotes using sisu inline footnote markup ... perhaps a bit cryptic now, if unfamiliar with sisu syntax. Thanks in advance, Ralph -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#598063: sisu: SiSU texinfo output broken
Package: sisu Version: 2.6.3-6 Severity: important Tags: upstream *** Please type your report below this line *** When run against a sisu markup document --texinfo (or the short flag -I) results in a code break and ruby bug report as to the offending code. #sisu --texinfo \ #free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst # #/usr/local/lib/site_ruby/1.8/sisu/v2/texinfo.rb:65:in `require': \ #/usr/local/lib/site_ruby/1.8/sisu/v2/texinfo_format.rb:583: syntax error, \ #unexpected $end, expecting kEND (SyntaxError) #__END__ # ^ #from /usr/local/lib/site_ruby/1.8/sisu/v2/texinfo.rb:65 #from /usr/local/lib/site_ruby/1.8/sisu/v2/hub.rb:88:in `require' #from /usr/local/lib/site_ruby/1.8/sisu/v2/hub.rb:88:in `select' #from /usr/local/lib/site_ruby/1.8/sisu/v2/hub.rb:274:in `op' #from /usr/local/lib/site_ruby/1.8/sisu/v2/hub.rb:467:in `actions' #from /usr/local/lib/site_ruby/1.8/sisu/v2/hub.rb:572 #from /usr/bin/sisu:11:in `require' #from /usr/bin/sisu:11 Thanks to rama for bringing this bug to my attention http://lists.sisudoc.org/pipermail/sisu/2010-September/73.html The bug is straightforward, in testing sisu output produced it seems I failed to test --texinfo (-I), a fix is posted (shortly) to the git repo and a Debian submission/fix will follow. (Apparently the bug predates 2.6.3 having already existed in sisu-2.6.2) -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sisu depends on: ii libruby [libwebrick-ruby] 4.5Libraries necessary to run Ruby 1. ii libwebrick-ruby 4.2transitional dummy package ii rsync 3.0.7-2fast remote file copy program (lik ii ruby 4.5An interpreter of object-oriented ii unzip 6.0-4 De-archiver for .zip files ii zip 3.0-3 Archiver for .zip files Versions of packages sisu recommends: ii imagemagick8:6.6.0.4-2.2 image manipulation programs ii keychain 2.6.8-2 key manager for OpenSSH ii librmagick-ruby2.13.1-1 ImageMagick API for Ruby ii libruby [librexml-ruby]4.5 Libraries necessary to run Ruby 1. ii openssh-client 1:5.5p1-5 secure shell (SSH) client, for sec ii openssl0.9.8o-2 Secure Socket Layer (SSL) binary a ii sisu-pdf 2.6.3-6 dependencies to convert SiSU LaTeX ii sisu-postgresql2.6.3-6 SiSU dependencies for use with Pos ii sisu-sqlite2.6.3-6 SiSU dependencies for use with SQL ii tidy 20091223cvs-1 HTML syntax checker and reformatte ii vim-addon-manager 0.4.3 manager of addons for the Vim edit Versions of packages sisu suggests: ii calibre 0.7.18+dfsg-1 e-book converter and library manag ii lv4.51-2 Powerful Multilingual File Viewer ii pinfo 0.6.9-5An alternative info-file viewer ii texinfo 4.13a.dfsg.1-5 Documentation system for on-line i pn trang none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#597953: ruby1.9.1: segfaults on a number of sisu operations
Package: ruby1.9.1 Version: 1.9.2.0-1 Severity: important Tags: upstream *** Please type your report below this line *** ruby1.9.2 segfaults running sisu (with a number of sisu options), that do not occur with ruby1.8.7, ruby1.9.0 or ruby1.9.1 (which I had to install separately to verify). This is not just the case with the current version of sisu but with previous versions as well. (it is possible that sisu needs some re-coding to be ruby1.9.2 compliant, but more graceful bug handling from ruby is expected) for example, using the markup-sample free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst provided in the package data/doc/sisu/v2/markup-samples/samples installed to /usr/share/doc/sisu/v2/markup-samples/samples/ * these work in ruby1.8.7, ruby1.9.0 and ruby1.9.1 but segfault in ruby1.9.2 [BUG] Segmentation fault first change directory to the directory in which the sample is located, then using the version of sisu in testing or sid, type sisu --html \ free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst any combination using the --verbose option fails sisu --txt --verbose \ free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst likewise sisu -N \ free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst There are likely others. # the following sisu options work (in all four: ruby1.8.7, ruby1.9.1 and # ruby1.9.2) (without the --verbose option): # # sisu -wepotbxXy \ # free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst # # sisu --txt --epub --pdf --odt --concordance --xhtml --xml-sax --xml-dom \ # --manifest \ # free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst however things may be getting worse rather than better upstream with ruby as a test on (a separate debian box with the manual installation of) ruby 1.9.2p0 (2010-08-18 revision 29036) [i686 linux], failed segfaulted on the first test passed to it sisu --txt \ free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst in earlier versions of sisu the equivalent of sisu -a \ free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst which does not happen with the version of ruby 1.9.2p0 (2010-08-18 revision 29036) [i486-linux] on unstable. I have a Sid box, it is likely to be the same in testing, please confirm otherwise. Thanks, Ralph Amissah -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ruby1.9.1 depends on: ii libc6 2.11.2-6 Embedded GNU C Library: Shared lib ii libruby1.9.1 1.9.2.0-1 Libraries necessary to run Ruby 1. ruby1.9.1 recommends no packages. Versions of packages ruby1.9.1 suggests: pn graphviz none (no description available) ii ri1.9.1 1.9.2.0-1 Ruby Interactive reference (for Ru ii ruby1.9.1-examples1.9.2.0-1 Examples for Ruby 1.9 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#596736: sisu: epub output not readable by all epub-reader software
Package: sisu Version: 2.6.3-4 Severity: important Tags: upstream *** Please type your report below this line *** sisu epub output for certain content works in some epub readers (found on debian) but not in others. The epub generated on for example in the markup sample provide: free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst sisu -ev \ free_as_in_freedom.richard_stallman_crusade_for_free_software.sam_williams.sst can be viewed in calibre, but not in either fbreader or okular It appears that some epub readers are more demanding about the xhtml they render. The cause of the problem appears to be an un-escaped line break (br instead of a br /) once this has been corrected epub documents generated can be read by the epub readers tested. The un-escaped occurs in sisu metadata, which is apparently not properly xhtml sanitized. More specifically the library param.rb sets line-breaks on metadata in relation to rights, which epub does not properly mark-up. (with the result that, calibre reads it without problem; fbreader fails to open it; okular crashes!) (this brought to my attention, I report against the package for which I am also upstream) A patch will follow (2.6.3-5) together with an unblock request for Squeeze. SiSU produces multiple outputs, one of which is EPUB. Ralph -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sisu depends on: ii libruby [libwebrick-ruby] 4.5Libraries necessary to run Ruby 1. ii libwebrick-ruby 4.2transitional dummy package ii rsync 3.0.7-2fast remote file copy program (lik ii ruby 4.5An interpreter of object-oriented ii unzip 6.0-4 De-archiver for .zip files ii zip 3.0-3 Archiver for .zip files Versions of packages sisu recommends: ii imagemagick8:6.6.0.4-2.2 image manipulation programs ii keychain 2.6.8-2 key manager for OpenSSH ii librmagick-ruby2.13.1-1 ImageMagick API for Ruby ii libruby [librexml-ruby]4.5 Libraries necessary to run Ruby 1. ii openssh-client 1:5.5p1-5 secure shell (SSH) client, for sec ii openssl0.9.8o-2 Secure Socket Layer (SSL) binary a ii sisu-pdf 2.6.3-4 dependencies to convert SiSU LaTeX ii sisu-postgresql2.6.3-4 SiSU dependencies for use with Pos ii sisu-sqlite2.6.3-4 SiSU dependencies for use with SQL ii tidy 20091223cvs-1 HTML syntax checker and reformatte ii vim-addon-manager 0.4.3 manager of addons for the Vim edit Versions of packages sisu suggests: ii calibre 0.7.13+dfsg-1 e-book converter and library manag ii lv4.51-2 Powerful Multilingual File Viewer ii pinfo 0.6.9-5An alternative info-file viewer ii texinfo 4.13a.dfsg.1-5 Documentation system for on-line i pn trang none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#594949: sisu: html headers do not include the title field
Package: sisu Version: 2.6.3-3 Severity: normal Tags: upstream For html output the html headers do not include title field. This also affects the version in testing (sisu 2.6.3-2) -- System Information: Debian Release: squeeze/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.32-5-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sisu depends on: ii libruby [libwebrick-ruby] 4.5Libraries necessary to run Ruby 1. ii libwebrick-ruby 4.2transitional dummy package ii rsync 3.0.7-2fast remote file copy program (lik ii ruby 4.5An interpreter of object-oriented ii unzip 6.0-4 De-archiver for .zip files ii zip 3.0-3 Archiver for .zip files Versions of packages sisu recommends: ii imagemagick8:6.6.0.4-2.2 image manipulation programs ii keychain 2.6.8-2 key manager for OpenSSH ii librmagick-ruby2.13.1-1 ImageMagick API for Ruby ii libruby [librexml-ruby]4.5 Libraries necessary to run Ruby 1. ii openssh-client 1:5.5p1-5 secure shell (SSH) client, for sec ii openssl0.9.8o-2 Secure Socket Layer (SSL) binary a ii sisu-pdf 2.6.3-3 dependencies to convert SiSU LaTeX ii sisu-postgresql2.6.3-3 SiSU dependencies for use with Pos ii sisu-sqlite2.6.3-3 SiSU dependencies for use with SQL ii tidy 20091223cvs-1 HTML syntax checker and reformatte ii vim-addon-manager 0.4.3 manager of addons for the Vim edit Versions of packages sisu suggests: ii calibre 0.7.13+dfsg-1 e-book converter and library manag ii lv4.51-2 Powerful Multilingual File Viewer ii pinfo 0.6.9-5An alternative info-file viewer ii texinfo 4.13a.dfsg.1-5 Documentation system for on-line i pn trang none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#573636: diakonos fails to start
looks as though all work has been done, will rebuild and repost this evening or over the weekend. Thanks Nate Bargmann (bug report), Daiki Ueno (fix and work on patch), and Evgeni Golov. Ralph Amissah -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#555496: SiSU parameter -n is not working
Stefan, Thank you and my apologies for the long delay in response, somehow I missed your report. Thus spake Stefan T. (won...@xdn.de): Package: sisu Version: 0.71.4-1 Severity: normal When I invoke 'sisu -an' it generates a textfile with appendix DOCUMENT INFORMATION (METADATA). But I used both parameters '-n' and '-a' extra to avoid this, as it is explained in manpages: -a: produces plaintext with Unix linefeeds and without markup -n: skip meta-markup The short answer is: your submission is not a bug in the applications behavior, but rather; but a bug or a failure of clarity on my part in the man pages describing the behavior of -n (was not programmed to have the behavior you expect). I will attempt to make the description of the behavior -n clearer in the in the man pages and other documentation. It should probably read more along the following text: -n skips the creation of intermediate processing files if intermediate processing files already exist. With some apologies for the length and being off-topic in relation to the feature you desire, here is what -n does, (and an explanation of th odd language used to describe it): sisu generates documents in two steps first, it produces a processing file (that i originally described as meta-marked up, i am now more inclined to describe as a document abstraction, but this is in fact just an interim processing document) that is used by various output format generation modules. It is a necessary step to produce a various output formats; -m ensures that it is performed, but it is usually assumed as necessary by the program. However, sisu additionally produces a marshalled version of these interim processing files, which if they still exist can be used to generate various output formats that are downstream of the interim processing files, skipping the re-creation of an interim processing file (the -m step). You might want this if you first produce one form of output, e.g. -a (plaintext) and subsequently decide to produce html, and decide you would rather skip re-generating the interim processing files, (possibly as it saves a bit of time). You do not want to use it if you have made changes to your document as these will not appear, the old or pre-existing interim processing files are used. (Whilst on the subject the marshalled documents are used in batch processing where many documents are processed first for one output file format type then the next, otherwise it would have been necessary to create the same interim processing files for each step. The processing files by default are written to the /tmp/sisu/username directory, however as this might result in privacy issues they may be redirected in the config file) Now what you wish may be a feature that should be added, at least for plaintext output. I suggest that the function of parameter -n is corrected in order to generate a text-file without any headers or meta-markups. Rather I will attempt to make clearer (correct) the description in the man pages and other documents as to the expected behavior for -n (and I would intend at that time to close this bug) The feature you desire could be submitted as a wishlist/feature request, though will not get my immediate attention. Would the flag you request apply only to plain text files, if so a different parameter may be used to be added only to -a, e.g. --without-metadata Again thank you. Sorry I do not have an answer that satisfies your wish directly. Sincerely, Ralph Amissah -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (890, 'testing'), (850, 'stable'), (845, 'unstable'), (800, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 2.6.26-2-openvz-amd64 (SMP w/1 CPU core) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to de_DE.UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages sisu depends on: ii libruby [libwebrick-ruby] 4.2Libraries necessary to run Ruby 1. ii rsync 3.0.6-1fast remote file copy program (lik ii ruby 4.2An interpreter of object-oriented ii unzip 6.0-1 De-archiver for .zip files ii zip 3.0-1 Archiver for .zip files Versions of packages sisu recommends: ii hyperestraier 1.4.9-1.4 a full-text search system for comm ii imagemagick7:6.5.5.3-1 image manipulation programs ii keychain 2.6.8-2 key manager for OpenSSH ii librmagick-ruby2.11.1-1 ImageMagick API for Ruby ii libruby [librexml-ruby]4.2 Libraries necessary to run Ruby 1. ii openssh-client 1:5.1p1-8 secure shell client, an rlogin/rsh ii openssl0.9.8k-5 Secure Socket Layer (SSL) binary a ii sisu-pdf 0.71.4-1 dependencies
Bug#464824: sisu: Conform with Vim addon policy
James, Thanks for the bug report. I hope it is finally addressed with sisu-0.67.1 uploaded today along with a close instruction. (It corrects a related bug introduced in 0.67.0). If there is a further issue don't hesitate to re-open the bug or to let me know. Sorry for the delay. The vim-addon-manager looks good. Ralph signature.asc Description: Digital signature
Bug#454372: sisu -- Doesn't purge all files after piuparts Install+Upgrade+Purge test
Kumar, Thanks for the bug report, (and for the testing). The build sisu-0.64.0 now contains a debian/postrm.sisu that on a purge (of sisu) should remove the directory /etc/sisu I would be grateful for confirmation if possible, else propose closing the bug in a couple of weeks (if all looks ok). Best Wishes for 2008, Ralph P.S. sorry about the late acknowledgement. (I expected to have dealt with it considerably sooner). signature.asc Description: Digital signature
Bug#451795: RFP: rocaml (library) - fast, easy Ruby extensions in Objective Caml
Package: wnpp Severity: wishlist fast, easy Ruby extensions in Objective Caml, explained as follows: Developing Ruby extensions with rocaml is easier and more convenient than writing a plain old C extension because rocaml performs Ruby-OCaml conversions for a wide range of types, including abstract types and arrays, tuples, variants and records of values of any supported type (e.g. arrays of arrays of variants of tuples of ...). Moreover, exceptions raised in the OCaml code are captured by the generated extension and raised inside Ruby. eigenclass http://eigenclass.org/hiki/rocaml-0.6.0 http://eigenclass.org/hiki/rocaml Tarball: http://eigenclass.org/static/rocaml/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#451797: RFP: JoCaml - OCaml extended for concurrent and distributed programming.
Package: wnpp Severity: wishlist JoCaml - OCaml extended for concurrent and distributed programming. http://jocaml.inria.fr/ Unsurprisingly, the JoCaml solution is much faster than those written in interpreted (or even JIT-compiled, as Erlang) languages. As I write this, the last JoCaml implementation Tim Bray tested is two times faster than the second entry, a 345-line, multi-process (not multi-thread) Erlang program with a specialized pattern matcher. I've made a comparable (i.e., without regexps) JoCaml version that is about three times faster than its Erlang counterpart (and still shorter). eigenclass http://eigenclass.org/hiki/wide-finder-conclusions Tarball directory: http://jocaml.inria.fr/pub/distri/ Current version at time of writing: http://jocaml.inria.fr/pub/distri/jocaml-3.10/ Source tarball (current version at time of writing): http://jocaml.inria.fr/pub/distri/jocaml-3.10/jocaml-3.10.0.tar.gz -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#450602: RFP: supmail (mail) - console based email client with tagging and fast search
Package: wnpp Severity: wishlist as described on its homepage: Sup is a console-based email client for people with a lot of email. It supports tagging, very fast full-text search, automatic contact- list management, custom code insertion via a hook system, and more.If you're the type of person who treats email as an extension of your long-term memory, Sup is for you. Sup is written in Ruby. Homepage: http://sup.rubyforge.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#450604: RFP: Wup - web based front end for Sup (a console based email client with tagging and fast search)
Package: wnpp Severity: wishlist as (currently) described on its homepage: wup! the web-powered version of William Morgan's sup. Unlike Apple's iPhone [tm] client, it lets you search through all your email. Unlike Gmail [tm], it works across your other IMAP mail accounts too! Homepage: http://jinsync.com/?q=node/16 Re: Sup: as described on its homepage: Sup is a console-based email client for people with a lot of email. It supports tagging, very fast full-text search, automatic contact- list management, custom code insertion via a hook system, and more.If you're the type of person who treats email as an extension of your long-term memory, Sup is for you. Sup is written in Ruby. Homepage: http://sup.rubyforge.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#434168: sisu: fails to initialize output directories, ok in previous version
Package: sisu Version: 0.55.3-1 Severity: important sisu -CC fails to initialize output directories, ok in previous version introduced in 0.55.3 is also in 0.55.4 (current upload to Sid) (new upstream fix on its way) -- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.21-2-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages sisu depends on: ii libwebrick-ruby1.3.1+ruby1.8.2-1 Simple HTTP Server Toolkit for Rub ii ruby 1.8.2-1 An interpreter of object-oriented ii unzip 5.52-10 De-archiver for .zip files ii zip2.32-1Archiver for .zip files Versions of packages sisu recommends: ii hyperestraier1.4.9-1.1 a full-text search system for comm ii kdissert 1.0.6.c-2 mindmapping tool ii keychain 2.6.6-1 key manager for OpenSSH ii librexml-ruby3.1.2.1+ruby1.8.2-1 pure Ruby non-validating XML parse ii librmagick-ruby 1.15.7-1ImageMagick API for Ruby ii openssh-client 1:4.6p1-4 secure shell client, an rlogin/rsh ii openssl 0.9.8e-5Secure Socket Layer (SSL) binary a ii rsync2.6.9-3 fast remote file copy program (lik ii sisu-pdf 0.55.3-1dependencies to convert SiSU LaTeX ii sisu-postgresql 0.55.3-1SiSU dependencies for use with pos ii sisu-sqlite 0.55.3-1SiSU dependencies for use with sql ii tidy 20051018-1 HTML syntax checker and reformatte ii trang20030619-5.1+b1 Multi-format XML schema converter -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#429741: vim-scripts: git.vim not packaged (please do)
Package: vim-scripts Version: 7.0.5 Severity: wishlist *** Please type your report below this line *** git.vim is not provided as a vim script. It is a useful tool (that appears to be prepared by a debian developer) Please clear licenses and offer it as a vim-script, see MadCoder's blog: http://blog.madism.org/index.php/2006/10/17/109-vim-mode-for-git-commits Thanks, Ralph Amissah -- System Information: Debian Release: lenny/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.21-1-686 (SMP w/2 CPU cores) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash vim-scripts depends on no packages. Versions of packages vim-scripts recommends: ii vim 1:7.1-000+1 Vi IMproved - enhanced vi editor ii vim-ruby [gvim] 1:7.1-000+1 Vi IMproved - enhanced vi editor - -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#419294: PL/Ruby now available for 8.2, issue rather with libdbd-pg-ruby, libdbi-ruby, libdbm-ruby, talking to postgresql-8.2
[postgresql installation wishlist] Please set the environment variable PGPORT on postgresql installation (it is not set on my system). The default for 8.2 on Debian appears to be 5433 (unless this is because i had 8.1 running concurrently for a while, which used 5432 as is noted and unchanged for 8.2 in postgresql documentation). export PGPORT=5433 This would make available the simplest of generic tests for the default port used by postgresql... and make available a fix for the current bug. sisu would check PGPORT and make decisions based on that (with the possibility of changing the default postgresql tcp/ip port in its rcfile sisurc.yml) Setting the correct TCP/IP port is all that is required to remove this bug; and this ideally should not have to be hardwired (especially to something different from the postgresl manual stated default) if the system correctly set up provides the information. http://www.postgresql.org/docs/8.2/interactive/app-postgres.html Thanks, Ralph Amissah
Bug#419294: [postgresql installation wishlist]
copy with more appropriate subject line On 08/05/07, Ralph Amissah [EMAIL PROTECTED] wrote: [postgresql installation wishlist] Please set the environment variable PGPORT on postgresql installation (it is not set on my system). The default for 8.2 on Debian appears to be 5433 (unless this is because i had 8.1 running concurrently for a while, which used 5432 as is noted and unchanged for 8.2 in postgresql documentation). export PGPORT=5433 This would make available the simplest of generic tests for the default port used by postgresql... and make available a fix for the current bug. sisu would check PGPORT and make decisions based on that (with the possibility of changing the default postgresql tcp/ip port in its rcfile sisurc.yml) Setting the correct TCP/IP port is all that is required to remove this bug; and this ideally should not have to be hardwired (especially to something different from the postgresl manual stated default) if the system correctly set up provides the information. http://www.postgresql.org/docs/8.2/interactive/app-postgres.html Thanks, Ralph Amissah
Bug#419294: PL/Ruby now available for 8.2, issue rather with libdbd-pg-ruby, libdbi-ruby, libdbm-ruby, talking to postgresql-8.2
Martin thanks, seems ruby postgresql connection drivers need some updating to talk to postgresql-8.2 libdbd-pg-ruby does not find postgresql-8.2 Rescued An ERROR occurred, message: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket /var/run/postgresql/.s.PGSQL.5432? Full detail of the complaint: /usr/lib/ruby/1.8/DBD/Pg/Pg.rb:111:in `initialize'/usr/lib/ruby/1.8/DBD/Pg/Pg.rb:55:in `new'/usr/lib/ruby/1.8/DBD/Pg/Pg.rb:55:in `connect'/usr/lib/ruby/1.8/dbi.rb:424:in `connect'/usr/lib/ruby/1.8/dbi.rb:215:in `connect'/usr/local/lib/site_ruby/1.8/sisu/0.52/dbi.rb:85:in `read_psql'/usr/local/lib/site_ruby/1.8/sisu/0.52/dbi.rb:100:in `connect'/usr/local/lib/site_ruby/1.8/sisu/0.52/hub.rb:177:in `select'/usr/local/lib/site_ruby/1.8/sisu/0.52/hub.rb:271:in `op'/usr/local/lib/site_ruby/1.8/sisu/0.52/hub.rb:483:in `actions'/usr/local/lib/site_ruby/1.8/sisu/0.52/hub.rb:567/usr/bin/sisu:8:in `require'/usr/bin/sisu:8 Thanks, I do look forward to using postgresql-8.2 (and even more 8.3 with native tsearch2 and related indexes) so having dependencies sorted for seamless postgresql version upgrades will be 'nice'. I should perhaps cross-post the bug report to libdbd-pg-ruby, (libdbi-ruby, libdbm-ruby) ... but have not yet done so. This being a generic postgresql ruby issue you may wish to do so. again, thanks, Ralph Amissah
Bug#407932: sisu -S [filename] where file is not found zips entire directory
Package: sisu Version: 0.48.8-7 Severity: normal *** Please type your report below this line *** if you run sisu with the -S flag, on a file that is not found, it goes into directory zip mode (instead of zipping a single file and its associated parts as the request intended) - which if not intended is annoying/ inconvenient as the process is not easily killed and can easily happen (-S is used in conjunction with other flags, and in batch processing) [ * sisu -S [filename] should make a zipped file of document markup and any associated files such as images that go with the document * sisu -S on its own makes a zipped file of the sisu markup contents of the directory and other associated files ] either the program should recognise that a filename has been requested, even though this is not found - so it does not zip the directory, or a confirmation request for directory zipping should be introduced -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages sisu depends on: ii libwebrick-ruby1.3.1+ruby1.8.2-1 Simple HTTP Server Toolkit for Rubii ruby 1.8.2-1 An interpreter of object-oriented ii unzip 5.52-9De-archiver for .zip files ii zip2.32-1Archiver for .zip files Versions of packages sisu recommends: ii hyperestraier1.4.9-1.1 a full-text search system for commii kdissert 1.0.6.c-1.1 mindmapping tool ii keychain 2.6.6-1 key manager for OpenSSH ii librexml-ruby3.1.2.1+ruby1.8.2-1 pure Ruby non-validating XML parseii librmagick-ruby 1.13.0-1ImageMagick API for Ruby ii openssh-client 1:4.3p2-8 Secure shell client, an rlogin/rshii openssl 0.9.8c-4Secure Socket Layer (SSL) binary aii rsync2.6.9-3 fast remote file copy program (likii sisu-pdf 0.48.8-7dependencies to convert SiSU LaTeXii sisu-postgresql 0.48.8-7SiSU dependencies for use with posii sisu-sqlite 0.48.8-7SiSU dependencies for use with sqlii tidy 20051018-1 HTML syntax checker and reformatteii trang20030619-5.1+b1 Multi-format XML schema converter -- no debconf information ~ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407943: sisu: sisupod generation in new directory needs to be executed twice
Package: sisu Version: 0.48.8-7 Severity: normal *** Please type your report below this line *** where sisu -S [filename] is run on a file contained in a directory that has not been used previously the command fails and must be repeated, after which it works (and continues doing so for subsequent occasions) -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages sisu depends on: ii libwebrick-ruby1.3.1+ruby1.8.2-1 Simple HTTP Server Toolkit for Rubii ruby 1.8.2-1 An interpreter of object-oriented ii unzip 5.52-9De-archiver for .zip files ii zip2.32-1Archiver for .zip files Versions of packages sisu recommends: ii hyperestraier1.4.9-1.1 a full-text search system for commii kdissert 1.0.6.c-1.1 mindmapping tool ii keychain 2.6.6-1 key manager for OpenSSH ii librexml-ruby3.1.2.1+ruby1.8.2-1 pure Ruby non-validating XML parseii librmagick-ruby 1.13.0-1ImageMagick API for Ruby ii openssh-client 1:4.3p2-8 Secure shell client, an rlogin/rshii openssl 0.9.8c-4Secure Socket Layer (SSL) binary aii rsync2.6.9-3 fast remote file copy program (likii sisu-pdf 0.48.8-7dependencies to convert SiSU LaTeXii sisu-postgresql 0.48.8-7SiSU dependencies for use with posii sisu-sqlite 0.48.8-7SiSU dependencies for use with sqlii tidy 20051018-1 HTML syntax checker and reformatteii trang20030619-5.1+b1 Multi-format XML schema converter -- no debconf information ~ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407937: sisu i18n, change to use iso-639-2 for language codes
Package: sisu Version: 0.48.8-7 Severity: normal *** Please type your report below this line *** The language codes used are not consistent, and in any event do not follow the iso-639-2 which unless you have good reason not to follow are recommended (see e.g. http://en.wikipedia.org/wiki/List_of_ISO_639-2_codes) Change practice now, as these things are more cumbersome to change later, - it will involve the re-naming of affected marked up files. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages sisu depends on: ii libwebrick-ruby1.3.1+ruby1.8.2-1 Simple HTTP Server Toolkit for Rubii ruby 1.8.2-1 An interpreter of object-oriented ii unzip 5.52-9De-archiver for .zip files ii zip2.32-1Archiver for .zip files Versions of packages sisu recommends: ii hyperestraier1.4.9-1.1 a full-text search system for commii kdissert 1.0.6.c-1.1 mindmapping tool ii keychain 2.6.6-1 key manager for OpenSSH ii librexml-ruby3.1.2.1+ruby1.8.2-1 pure Ruby non-validating XML parseii librmagick-ruby 1.13.0-1ImageMagick API for Ruby ii openssh-client 1:4.3p2-8 Secure shell client, an rlogin/rshii openssl 0.9.8c-4Secure Socket Layer (SSL) binary aii rsync2.6.9-3 fast remote file copy program (likii sisu-pdf 0.48.8-7dependencies to convert SiSU LaTeXii sisu-postgresql 0.48.8-7SiSU dependencies for use with posii sisu-sqlite 0.48.8-7SiSU dependencies for use with sqlii tidy 20051018-1 HTML syntax checker and reformatteii trang20030619-5.1+b1 Multi-format XML schema converter -- no debconf information ~ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407938: sisu: xml output, urls are broken, please use xlink
Package: sisu Version: 0.48.8-7 Severity: normal *** Please type your report below this line *** sisu: xml output, urls are broken or rather not processed, it should be simple to use xlink or the like to make them usable. Please fix. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages sisu depends on: ii libwebrick-ruby1.3.1+ruby1.8.2-1 Simple HTTP Server Toolkit for Rubii ruby 1.8.2-1 An interpreter of object-oriented ii unzip 5.52-9De-archiver for .zip files ii zip2.32-1Archiver for .zip files Versions of packages sisu recommends: ii hyperestraier1.4.9-1.1 a full-text search system for commii kdissert 1.0.6.c-1.1 mindmapping tool ii keychain 2.6.6-1 key manager for OpenSSH ii librexml-ruby3.1.2.1+ruby1.8.2-1 pure Ruby non-validating XML parseii librmagick-ruby 1.13.0-1ImageMagick API for Ruby ii openssh-client 1:4.3p2-8 Secure shell client, an rlogin/rshii openssl 0.9.8c-4Secure Socket Layer (SSL) binary aii rsync2.6.9-3 fast remote file copy program (likii sisu-pdf 0.48.8-7dependencies to convert SiSU LaTeXii sisu-postgresql 0.48.8-7SiSU dependencies for use with posii sisu-sqlite 0.48.8-7SiSU dependencies for use with sqlii tidy 20051018-1 HTML syntax checker and reformatteii trang20030619-5.1+b1 Multi-format XML schema converter -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#407941: sisu: vim syntax highlighting does not capture a footnote shortcut
Package: sisu Version: 0.48.8-7 Severity: minor *** Please type your report below this line *** the shortcut for creating a footnote out of the url for a link is not properly captured by the syntax highlighter i.e. the following makes a link of the enclosed text to the provided url along with a footnote showing the url: {~^ debian bug tracking system }http://www.debian.org/Bugs however the ~^ is not recognised in this situation by the highlighter as part of the markup syntax. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages sisu depends on: ii libwebrick-ruby1.3.1+ruby1.8.2-1 Simple HTTP Server Toolkit for Rubii ruby 1.8.2-1 An interpreter of object-oriented ii unzip 5.52-9De-archiver for .zip files ii zip2.32-1Archiver for .zip files Versions of packages sisu recommends: ii hyperestraier1.4.9-1.1 a full-text search system for commii kdissert 1.0.6.c-1.1 mindmapping tool ii keychain 2.6.6-1 key manager for OpenSSH ii librexml-ruby3.1.2.1+ruby1.8.2-1 pure Ruby non-validating XML parseii librmagick-ruby 1.13.0-1ImageMagick API for Ruby ii openssh-client 1:4.3p2-8 Secure shell client, an rlogin/rshii openssl 0.9.8c-4Secure Socket Layer (SSL) binary aii rsync2.6.9-3 fast remote file copy program (likii sisu-pdf 0.48.8-7dependencies to convert SiSU LaTeXii sisu-postgresql 0.48.8-7SiSU dependencies for use with posii sisu-sqlite 0.48.8-7SiSU dependencies for use with sqlii tidy 20051018-1 HTML syntax checker and reformatteii trang20030619-5.1+b1 Multi-format XML schema converter -- no debconf information ~ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#406280: sample search form is broken (by modifications introduced in -4)
Package: sisu Version: 0.48.10-1 Severity: normal *** Please type your report below this line *** The sample search form no longer works. The modifications to sample search form introduced in -4 break it -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages sisu depends on: ii libwebrick-ruby1.3.1+ruby1.8.2-1 Simple HTTP Server Toolkit for Rub ii ruby 1.8.2-1 An interpreter of object-oriented ii unzip 5.52-9De-archiver for .zip files ii zip2.32-1Archiver for .zip files Versions of packages sisu recommends: ii hyperestraier1.4.9-1.1 a full-text search system for comm ii kdissert 1.0.6.c-1.1 mindmapping tool ii keychain 2.6.6-1 key manager for OpenSSH ii librexml-ruby3.1.2.1+ruby1.8.2-1 pure Ruby non-validating XML parse ii librmagick-ruby 1.13.0-1ImageMagick API for Ruby ii openssh-client 1:4.3p2-8 Secure shell client, an rlogin/rsh ii openssl 0.9.8c-4Secure Socket Layer (SSL) binary a ii rsync2.6.9-3 fast remote file copy program (lik ii sisu-pdf 0.48.10-1 dependencies to convert SiSU LaTeX ii sisu-postgresql 0.48.10-1 SiSU dependencies for use with pos ii sisu-sqlite 0.48.10-1 SiSU dependencies for use with sql ii tidy 20051018-1 HTML syntax checker and reformatte ii trang20030619-5.1+b1 Multi-format XML schema converter -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#406281: sample search form is broken (by modifications introduced in -4)
Package: sisu Version: 0.48.8-6 Severity: normal *** Please type your report below this line *** The sample search form no longer works. The modifications to sample search form introduced in -4 break it -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages sisu depends on: ii libwebrick-ruby1.3.1+ruby1.8.2-1 Simple HTTP Server Toolkit for Rub ii ruby 1.8.2-1 An interpreter of object-oriented ii unzip 5.52-9De-archiver for .zip files ii zip2.32-1Archiver for .zip files Versions of packages sisu recommends: ii hyperestraier1.4.9-1.1 a full-text search system for comm ii kdissert 1.0.6.c-1.1 mindmapping tool ii keychain 2.6.6-1 key manager for OpenSSH ii librexml-ruby3.1.2.1+ruby1.8.2-1 pure Ruby non-validating XML parse ii librmagick-ruby 1.13.0-1ImageMagick API for Ruby ii openssh-client 1:4.3p2-8 Secure shell client, an rlogin/rsh ii openssl 0.9.8c-4Secure Socket Layer (SSL) binary a ii rsync2.6.9-3 fast remote file copy program (lik ii sisu-pdf 0.48.10-1 dependencies to convert SiSU LaTeX ii sisu-postgresql 0.48.10-1 SiSU dependencies for use with pos ii sisu-sqlite 0.48.10-1 SiSU dependencies for use with sql ii tidy 20051018-1 HTML syntax checker and reformatte ii trang20030619-5.1+b1 Multi-format XML schema converter -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#406282: sisu-sqlite: package suggests on libdbd-sqlite which is not found in testing
Package: sisu-sqlite Version: 0.48.8-6 Severity: minor *** Please type your report below this line *** sisu-sqlite: package suggests on libdbd-sqlite which is not found in testing -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages sisu-sqlite depends on: ii libdbd-sqlite-ruby0.1.1-2Ruby/DBI driver for SQLite ii libdbi-ruby 0.1.1-2Database Independent Interface for ii libdbm-ruby 1.8.2-1DBM interface for Ruby ii sisu 0.48.10-1 electronic document collection gen ii sqlite2.8.17-1 command line interface for SQLite Versions of packages sisu-sqlite recommends: ii libfcgi-ruby1.8 0.8.7-3FastCGI library for Ruby -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#406284: sisu-postgresql: package suggests libdbd-pgsql which is not found in testing
Package: sisu-postgresql Version: 0.48.8-6 Severity: minor *** Please type your report below this line *** -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.17-2-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages sisu-postgresql depends on: ii libdbd-pg-ruby0.1.1-2Ruby/DBI PostgreSQL driver ii libdbi-ruby 0.1.1-2Database Independent Interface for ii libdbm-ruby 1.8.2-1DBM interface for Ruby ii postgresql-8.18.1.6-1object-relational SQL database, ve ii sisu 0.48.8-6 electronic document collection gen Versions of packages sisu-postgresql recommends: ii libfcgi-ruby1.8 0.8.7-3FastCGI library for Ruby -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403037: sisu: output, landscape pdf object/paragraph numbers missing in left column
Package: sisu Version: 0.48.8-1 Severity: normal *** Please type your report below this line *** Generated output, landscape pdf object/paragraph numbers missing in left column. Bug appears to have been introduced somewhere between versions 0.47 and 0.48 -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-1-486 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages sisu depends on: ii libwebrick-ruby1.3.1+ruby1.8.2-1 Simple HTTP Server Toolkit for Rubii ruby 1.8.2-1 An interpreter of object-oriented ii unzip 5.52-9De-archiver for .zip files ii zip2.32-1Archiver for .zip files Versions of packages sisu recommends: ii hyperestraier1.4.4-1 a full-text search system for commii kdissert 1.0.6.c-1 mindmapping tool ii keychain 2.6.6-1 key manager for OpenSSH ii librexml-ruby3.1.2.1+ruby1.8.2-1 pure Ruby non-validating XML parseii librmagick-ruby 1.13.0-1ImageMagick API for Ruby ii openssh-client 1:4.3p2-7 Secure shell client, an rlogin/rshii openssl 0.9.8c-2Secure Socket Layer (SSL) binary aii rsync2.6.9-3 fast remote file copy program (likii sisu-pdf 0.48.8-1dependencies to convert SiSU LaTeXii sisu-postgresql 0.48.8-1SiSU dependencies for use with posii sisu-sqlite 0.48.8-1SiSU dependencies for use with sqlii tidy 20051018-1 HTML syntax checker and reformatteii trang20030619-5.1+b1 Multi-format XML schema converter -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#403042: sisu: generated cgi sample search forms (postgresql and sqlite), no limit provided for number of matches returned
Package: sisu Version: 0.48.8-1 Severity: normal *** Please type your report below this line *** The generated cgi sample search forms (for postgresql and sqlite), have no limit provided for number of matches returned, which can lead to problems with large match sets in large databases. -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.18-1-486 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages sisu depends on: ii libwebrick-ruby1.3.1+ruby1.8.2-1 Simple HTTP Server Toolkit for Rubii ruby 1.8.2-1 An interpreter of object-oriented ii unzip 5.52-9De-archiver for .zip files ii zip2.32-1Archiver for .zip files Versions of packages sisu recommends: ii hyperestraier1.4.4-1 a full-text search system for commii kdissert 1.0.6.c-1 mindmapping tool ii keychain 2.6.6-1 key manager for OpenSSH ii librexml-ruby3.1.2.1+ruby1.8.2-1 pure Ruby non-validating XML parseii librmagick-ruby 1.13.0-1ImageMagick API for Ruby ii openssh-client 1:4.3p2-7 Secure shell client, an rlogin/rshii openssl 0.9.8c-2Secure Socket Layer (SSL) binary aii rsync2.6.9-3 fast remote file copy program (likii sisu-pdf 0.48.8-1dependencies to convert SiSU LaTeXii sisu-postgresql 0.48.8-1SiSU dependencies for use with posii sisu-sqlite 0.48.8-1SiSU dependencies for use with sqlii tidy 20051018-1 HTML syntax checker and reformatteii trang20030619-5.1+b1 Multi-format XML schema converter -- no debconf information ~ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#391068: Fwd: Bug#391068: Can not be installed if texlive is installed
Thank you for the detailed bug report. What now? Is that bug in sisu-pdf or in some texlive-package or latex-ucs-package? At the present time I can tell you that sisu pdf generation works fine with texlive installed (without the need to install sisu-pdf with which there is indeed a conflict), [I am not yet certain of the subdivision of texlive packages and the bare minimum requirement, but] It works for me with the following installed: i texlive - TeX Live: A decent selection of the TeX li i A texlive-base - TeX Live: Essential programs and files i A texlive-base-bin - TeX Live: Essential binaries i texlive-common- TeX Live: Base component i A texlive-context - TeX Live: ConText macro package i A texlive-doc-base - TeX Live: Base documentation i A texlive-fonts-recommended - TeX Live: Recommended fonts i A texlive-latex-base- TeX Live: Basic LaTeX packages i texlive-latex-extra - TeX Live: LaTeX supplementary packages i A texlive-latex-recommended - TeX Live: LaTeX recommended packages i A texlive-metapost - TeX Live: MetaPost (and Metafont) drawing i A texlive-pdfetex - TeX Live: pdfTeX i A texlive-pictures - TeX Live: Drawing and graphing packages I will work my way through the dependencies for package sisu-pdf, (and may end up having to have two separate conflicting bundles of dependencies for sisu-pdf one for tetex and the other for texlive, I do not know at this stage) Hope this helps, and again thanks for the report. Ralph Amissah -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#389123: diakonos: Default configuration file isn't detected
Mathieu Petit-Clair wrote: Package: diakonos Version: 0.8.2-1 Severity: important This otherwise nice package installs a default configuration file as /etc/diakonos/diakonos.conf, but this path isn't valid as far as Diakonos is concerned ... : Thank you, the package has been rebuilt as diakonos-0.8.2-2 and the default config (diakonos.conf) has been placed in /etc (upload has been requested). Ralph Amissah -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386015: ITP: diakonos -- a customizable, usable console-based text editor
Package: wnpp Owner: Ralph Amissah [EMAIL PROTECTED] Severity: wishlist *** Please type your report below this line *** ITP: rant -- a flexible ruby based make * Package name: diakonos Version : 0.8.2 Upstream Author : Pistos Christou [EMAIL PROTECTED] * URL : http://purepistos.net/diakonos/ * License : GPL2 Programming Lang: Ruby Description : customizable, usable console-based text editor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#386015: ITP: diakonos -- a customizable, usable console-based text editor
Package: wnpp Owner: Ralph Amissah [EMAIL PROTECTED] Severity: wishlist *** Please type your report below this line *** correction: ITP: diakonos -- a customizable, usable console-based text editor STRIKE error: -{ITP: rant -- a flexible ruby based make}- * Package name: diakonos Version : 0.8.2 Upstream Author : Pistos Christou [EMAIL PROTECTED] * URL : http://purepistos.net/diakonos/ * License : GPL2 Programming Lang: Ruby Description : customizable, usable console-based text editor -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380034: Request for the inclusion of manyfoot.sty in tetex-extra
On 27/07/06, Ralf Stubner [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] wrote: [there is some personal interest, sisu (sisu-pdf) has come to depend on the presence of manyfoot.sty, and though there will be little problem working with texlive, there seems no good reason why the choice of either tetex or texlive should be precluded for this reason alone (i.e. the lack of a useful and recognised latex package manyfoot in tetex)... please]. Actually in Debian the user is able to choose whether to use teTeX or TeX Live. And it is even possible to add packages from TeX Live to a teTeX installation (or the other way round, but that is less interesting). However, for this to work it is necessary for depending packages to provide suitable alternatives. At the moment sisu-pdf depends on: tetex-bin tetex-extra texlive-latex-extra It would be good if you would change this into tetex-bin | texlive-base-bin tetex-extra | texlive-latex-extra texlive-latex-extra Thank you, I will do as you suggest in future packaging, and will look towards primarily using texlive. My request for the addition to tetex is to enable me to continue to provide users the option of using tetex, as it works fine but for the absence of the single manyfoot.sty (i.e. at present this is the reason texlive-latex-extra is needed, and i would still prefer the option of not needing it, or rather choosing between either if possible) (I am not completly sure what your actual dependencies are on the LaTeX level. Please cross check.) will do, thank you. As Frank said, teTeX is dead upstream, so it is quite likely that TeX Live will be the TeX system of choice on Debian in the not so far future. teTeX is dead long live TeX Live... or something like that, all's well. cheerio ralf :-) ralph -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#380034: Request for the inclusion of manyfoot.sty in tetex-extra
Package: tetex-base Version: 3.0-20 Severity: wishlist Request for the inclusion of manyfoot.sty in tetex-extra. A number of scholarly writings need multiple footnote streams. manyfoot.sty is a known and documented latex package: documented in The LaTeX Companion 2nd ed. pages 122-125. (it is currently to be found on the Debian system I believe in texlive-latex-extra). [there is some personal interest, sisu (sisu-pdf) has come to depend on the presence of manyfoot.sty, and though there will be little problem working with texlive, there seems no good reason why the choice of either tetex or texlive should be precluded for this reason alone (i.e. the lack of a useful and recognised latex package manyfoot in tetex)... please]. Thanks, Ralph Amissah -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#379725: problem upgrading hyperestraier, (upgrade fails)
Package: hyperestraier Version: 1.3.3-1 Severity: important Fails to upgrade with error message: Errors were encountered while processing: /var/cache/apt/archives/hyperestraier_1.3.3-1_i386.deb localepurge: Disk space freed in /usr/share/locale: 2160K E: Sub-process /usr/bin/dpkg returned an error code (1) A package failed to install. Trying to recover: ... A similar problem existed with upgrading to 1.2.5-1, and it persisted. I have kept the package on hold and not retried the upgrade. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#374873: Improved package description
Thanks for the bug report. Will look into: Jens Seidel wrote: Package: vim-sisu Version: 0.41.6 Severity: minor Hi, the package description contains: SiSU vim syntax highlighter and folds but I would expect (attention, I'm not a native English speaker) SiSU vim syntax highlighter and folder Not sure, will have to look into, a folder is usually understood as another word for something like a directory. Vim help discusses the feature under fold :help fold (the syntax highlighter though is now contained in Vim 7... though a copy is retained in the package for earlier versions of vim) I wonder also about Home page http://www.jus.uio.no/sisu According to http://www.us.debian.org/doc/developers-reference/ch-best-pkging-practices.en.html#s-bpp-upstream-info it should be Homepage: http://www.jus.uio.no/sisu thanks, will be corrected in next release Jens Thanks, Ralph -- email: [EMAIL PROTECTED] SiSU: http://www.jus.uio.no/sisu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#369366: ITP: rant -- a flexible ruby based make
Package: wnpp Owner: Ralph Amissah [EMAIL PROTECTED] Severity: wishlist *** Please type your report below this line *** ITP: rant -- a flexible ruby based make * Package name: rant Version : 0.5.6 Upstream Author : Stefan Lang [EMAIL PROTECTED] * URL : http://make.rubyforge.org/ * License : LGPL Programming Lang: Ruby Description : flexible ruby based make Similar to make, the rant commandline tool reads a file called Rantfile, which contains task definitions. Unlike make, however, an Rantfile is just a valid script written in the Ruby programming language. Since Ruby comes with many useful libraries and is portable across many different operating systems, it is easy to write portable Rantfiles. rant --help provides a list of options rant -T provides a list of tasks in an existing Rantfile [i use this, and have made a preliminary package, available via: deb http://www.jus.uio.no/sisu/archive unstable main deb-src http://www.jus.uio.no/sisu/archive unstable main upload sponsor welcome] -- System Information: Debian Release: testing/unstable APT prefers unstable APT policy: (500, 'unstable'), (500, 'stable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-1-686 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#357188: Package: installation-reports
Written in response to After using the Debian-Installer, please send us an installation report, even if there weren't any problems. the feedback link is to http://d-i.alioth.debian.org/manual/en.i386/ch05s03.html#submit-bug the suggestion and link found on http://www.debian.org/devel/debian-installer/ Following that suggestion it was more general than a bug report, and more like user feedback. Bug report may indeed not be the right place for this type of feedback. If such feedback is desired, perhaps this link/suggestion should be to updated to suggest some place different. If such feedback is a waste of time, perhaps the suggestion should be removed. (it is why for example i mention things like the lack of screen encountered as an issue when i then needed to set up the network I was left without after the installation.) A couple of comments below, but the installations were smooth. Thanks. On 16/03/06, Christian Perrier [EMAIL PROTECTED] wrote: on the whole a very smooth installation, a few notes * it found and installed over wireless pcmcia card, however postinstall wireless card was not set up for use I leave this opened in case this could be reassigned to a d-i package. This is actually the only item I find relevant to the installer in the report. * touchpad/mouse settings no good, (no acceleration and painfully slow movement) much better response with generic mousedriver, xorg.conf needs manual reconfigure The following does not work Identifier Synaptics Touchpad Driver synaptics Replaced with Identifier Generic Mouse Driver mouse and appropriate settings. This should be reported against the xserver-xorg source package. * Humbly suggest, the program screen should be part of the default installation for those who use it. This should be reported against the screen package but honestly I see no reason for it. oh, does this mean that screen is available... i recall typing screen -a in a console and not finding it, perhaps i am mistaken. * I forget the selections, standard, laptop and desktop used and work fine, bringing up xorg (and installing gnome desktop) standard + laptop appears to install xorg, but is not configured to work as easily when a display manager and alternative window manager is to be installed. I don't understand the point here. Question, if X11 is installed for the standard installation without the desktop installation, is it not possible to have xorg configured so that it works in pretty much the same way, and all you would need to do is install a display and window manager to have the distro working with X, I mean the setting are configured correctly when you choose to install gnome, (and X11 seems to be installed without the need to install the gnome desktop). I have not explored, what is expected of the standard installation without desktop. I thought this would be a convenient state to have the installation in, if it was not incompatible with intent. -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEGPv51OXtrMAUPS0RAtQTAJ9LNGYf4SsLEgTmCGiCVfqxp64mPACgvf6H nEYoRkA9Xj9PDlnxEc//UDw= =zyEB -END PGP SIGNATURE- -- email: [EMAIL PROTECTED] SiSU: http://www.jus.uio.no/sisu
Bug#357188: Package: installation-reports
Package: installation-reports After using the Debian-Installer, please send us an installation report, even if there weren't any problems. Boot method: CD Image version: 200615 http://www.debian.org/devel/debian-installer/ http://cdimage.debian.org/cdimage/daily-builds/daily/arch-latest/i386/iso-cd/debian-testing-i386-netinst.iso Date: 20060315 (three installation two separate partitions, one repeat, testing) Machine: Sony Vaio PCG-FX805 Processor: AMD Athlon K something Memory: Partitions: df -Tl FilesystemType 1K-blocks Used Available Use% Mounted on /dev/hda6 reiserfs 5855432 3464976 2390456 60% / (unstable/upgrade) tmpfstmpfs 128344 0128344 0% /dev/shm /dev/hda3 reiserfs19534436 14409200 5125236 74% /home tmpfstmpfs 1024096 10144 1% /dev /dev/hda8 reiserfs 3614476 1754776 1859700 49% /mnt/a8 (unstable/install) /dev/hda1 reiserfs 5855432 2691444 3163988 46% /mnt/a1 (unstable/install) Output of lspci: :00:00.0 Host bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133] (rev 03) :00:01.0 PCI bridge: VIA Technologies, Inc. VT8363/8365 [KT133/KM133 AGP] :00:07.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South] (rev 40) :00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06) :00:07.2 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1a) :00:07.3 USB Controller: VIA Technologies, Inc. VT82x UHCI USB 1.1 Controller (rev 1a) :00:07.4 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 40) :00:07.5 Multimedia audio controller: VIA Technologies, Inc. VT82C686 AC97 Audio Controller (rev 50) :00:07.6 Communication controller: VIA Technologies, Inc. AC'97 Modem Controller (rev 30) :00:0a.0 CardBus bridge: Texas Instruments PCI1420 :00:0a.1 CardBus bridge: Texas Instruments PCI1420 :00:0e.0 FireWire (IEEE 1394): Texas Instruments TSB12LV26 IEEE-1394 Controller (Link) :00:10.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) :01:00.0 VGA compatible controller: ATI Technologies Inc Rage Mobility P/M AGP 2x (rev 64) Output of lspci -n: :00:00.0 0600: 1106:0305 (rev 03) :00:01.0 0604: 1106:8305 :00:07.0 0601: 1106:0686 (rev 40) :00:07.1 0101: 1106:0571 (rev 06) :00:07.2 0c03: 1106:3038 (rev 1a) :00:07.3 0c03: 1106:3038 (rev 1a) :00:07.4 0601: 1106:3057 (rev 40) :00:07.5 0401: 1106:3058 (rev 50) :00:07.6 0780: 1106:3068 (rev 30) :00:0a.0 0607: 104c:ac51 :00:0a.1 0607: 104c:ac51 :00:0e.0 0c00: 104c:8020 :00:10.0 0200: 10ec:8139 (rev 10) :01:00.0 0300: 1002:4c4d (rev 64) Base System Installation Checklist: [O] = OK, [E] = Error (please elaborate below), [ ] = didn't try it Initial boot worked:O Configure network HW: O Config network: O Detect CD: O Load installer modules: O Detect hard drives: O Partition hard drives: O Create file systems:O Mount partitions: O Install base system:O Install boot loader:O Reboot: O Comments/Problems: on the whole a very smooth installation, a few notes * it found and installed over wireless pcmcia card, however postinstall wireless card was not set up for use * touchpad/mouse settings no good, (no acceleration and painfully slow movement) much better response with generic mousedriver, xorg.conf needs manual reconfigure The following does not work Identifier Synaptics Touchpad Driver synaptics Replaced with Identifier Generic Mouse Driver mouse and appropriate settings. * Humbly suggest, the program screen should be part of the default installation for those who use it. * I forget the selections, standard, laptop and desktop used and work fine, bringing up xorg (and installing gnome desktop) standard + laptop appears to install xorg, but is not configured to work as easily when a display manager and alternative window manager is to be installed. Description of the install, in prose, and any thoughts, comments and ideas you had during the initial install. -- email: [EMAIL PROTECTED] SiSU: http://www.jus.uio.no/sisu
Bug#295638: rdiff-backup: appears to have disappeared
Package: rdiff-backup Version: 0.13.4-4 Severity: grave Justification: renders package unusable rdiff-backup is not installed within normal paths, the previous version is removed, and there is no new version available for execution. -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.8-2004 Locale: LANG=C, LC_CTYPE=C (charmap=ISO-8859-1) (ignored: LC_ALL set to en_GB) Versions of packages rdiff-backup depends on: ii python2.3 2.3.5-1An interactive high-level object-o ii rdiff 0.9.7-1Binary diff tool for signature-bas -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]