Bug#1065727: ITP: nwg-hello -- GTK3-based greeter for the greetd daemon
Package: wnpp Severity: wishlist Owner: Maytham Alsudany X-Debbugs-Cc: debian-devel@lists.debian.org -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 * Package name: nwg-hello Version : 0.1.7 Upstream Contact: https://github.com/nwg-piotr/nwg-hello/issues * URL : https://github.com/nwg-piotr/nwg-hello * License : Expat Programming Lang: Python Description : GTK3-based greeter for the greetd daemon This program is a part of the nwg-shell project. . Nwg-hello is a GTK3-based greeter for the greetd daemon, written in Python. It is meant to work under a Wayland compositor, like sway or Hyprland. . Features: - Multi-monitor support with gtk-layer-shell; - multi-language support; - background & style customization with css; - automatic selection of the last used session and user; - support for setting environment variables. Another option for greetd, and a great addition to Debian to encourage users to switch to Wayland compositors like sway. -BEGIN PGP SIGNATURE- iQJMBAEBCgA2FiEESl/RzRFQh8wD3DXB1ZeJcgbF8H8FAmXsVy0YHG1heXRoYTh0 aGVkZXZAZ21haWwuY29tAAoJENWXiXIGxfB/x1AQAK/zpikqDXl5m94O5IHUJBJf yuD3S588Ezwk26f/6n5Ole6nSZYkphtYV5VuGFAe2rAE5K+yMz1ivxoAxTk4vL0t ZZYufhz8kQrz2AsfgyENrERgkixmRKvSaY8qJeHgFDJE2Y9VSovIxE7o1XELJJsq vUYYvzAkn414rMrDLSR3tzey/KD9jVsknS97XmsoCjQy50+on95h4WNQsz0hQjrG LkUwU2Q61X8MGO6Zrr09QC5qDEc7yI9fDyyazNR/eD5IER0iH9Zw1xkGFv1Z39HS xmUTn83f8Ztz5s7jLvGerWqiZEvkN8yQTo51dGMv5sjkVliSmXy7WwfdE/P0aU8N HjvFOTD3+PQC9X3VU9z0Vx1mKxAWFRjjzOIvgyzetm3Hd3j0EfHQFyOJhAkyRphY U9oVoTKTKMn9UDykjrkRcMYo7H/3wvr9k597pA+QF8Sy3kby5LEQVpOu1ChkBuG5 m0RDGdTm30eRjf4Zf7J8sLbZnBZK13rPH/1h4ntzIUKFuRYKePCPkXRhzXCvlnyE iZBx1ERLU136rE3HprBcLgstJJ5TmpQxJ3Q9VsIwb9OUK46CQCNH4f9VUS9cLg4q 7OfgJ0Ub7ojZUZzoVB54sv4yqgdwW6TtAtNTgaaN/2/IuOm3efC9yr99AQ/MV4kZ zq/i588Hv4uiFeqFA1GU =5tIY -END PGP SIGNATURE-
a[uto]p[kg]t[ests] on non-any (was: Re: say hello to our studious bookworm)
On Sun, Aug 15, 2021 at 12:02:00AM +0100, Jonathan Wiltshire wrote: > Following the release of bullseye, we can confirm that autopkgtests (when > provided) will continue to be considered across all architectures for > migration to bookworm. In other words, the tests need to succeed on all > release architectures for your package to migrate. Is this just the old "no regressions", or "no fails" as was announced somewhere as the plan for Bookworm? Britney still considers packages that are excluded on some archs¹ to be not fully passing, which currently means depriving such packages from the migration time bonus. But, if "no fails" is indeed your plan... Meow! ¹. ignoring armel mips64el mips s390x. -- ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Imagine there are bandits in your house, your kid is bleeding out, ⢿⡄⠘⠷⠚⠋⠀ the house is on fire, and seven giant trumpets are playing in the ⠈⠳⣄ sky. Your cat demands food. The priority should be obvious...
Re: Bits from the Release Team: say hello to our studious bookworm
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Sun, 2021-08-15 at 00:02 +0100, Jonathan Wiltshire wrote: > Hi, > > On 14th August 2021 we released Debian 11 "bullseye". > > There are too many people who should be thanked for their work on > getting > us to this point to list them all individually, and we would be sure > to > miss some. Nevertheless, we would like to particularly thank the > installer > team, the buildd and ftp teams, the CD team, the publicity team, the > webmasters, the Release Notes editors, porters and all the bug > squashers, > NMUers, package maintainers and translators who have contributed to > making > bullseye a great release of which we should all be proud. > > First point release > === > > As on previous occasions, we anticipate that the first point release > for > bullseye will occur in approximately one month's time. > > Please co-ordinate fixes which you would like to see included in the > point > release with the Stable Release Managers (SRMs) via a "pu" bug against > the > release.debian.org pseudopackage, including a debdiff of the current > and > proposed source packages. Remember to use reportbug unless you enjoy > crafting the metadata by hand. > > Autopkgtests continue to be crucial to migration > > > Following the release of bullseye, we can confirm that autopkgtests > (when > provided) will continue to be considered across all architectures for > migration to bookworm. In other words, the tests need to succeed on > all > release architectures for your package to migrate. > > Start working on bookworm > = > > With the start of the bookworm release cycle, you can now upload to > unstable those changes you've been holding off during the freeze. > Please do > not rush to upload everything all at once, in order to manage load on > the > buildds etc. Automatic testing migration is not yet re-enabled, but > that > will happen during the next few days. > > As with bullseye, we would ask that you co-ordinate particularly large > transitions or changes; if your plans involve major toolchain changes > or > otherwise have the potential to cause problems in unstable for a long > time > (e.g. due to FTBFS issues), please talk to us. We know that there are > a > large number of changes which have been waiting for the release to > happen > and we're keen not to stand in the way of those but would also like to > avoid a number of larger transitions becoming entangled. > > That's it for now; it is time for the celebrations to begin, whether > at a > Release Party[1] or otherwise. :-) > > Thank you everyone for all your hard work! - -- Best regards, Brian T. -BEGIN PGP SIGNATURE- iQJHBAEBCgAxFiEE9fpVo96/flopdKOfgw2Ncu3Nhn0FAmEYccETHGJyaWFuQGhh c2h2YXVsdC5pbwAKCRCDDY1y7c2GfacLD/9hOuSji6aJQprXk05lvJ+mKHhnhCV9 jX6eEN9exJ4v+gtbD62PYoegqUScVCMYR/B49Je4CKIqlh+9EmcjwnURSBtZPA3F dP0wgO2zU9j5P4wwCdLEtY5pKYD5Guxl4pqDEvasuoJqV+1RMtyiHC6X8DUeQgJS O1QtpYgukZEsCaAcQIXFPsI3x3wgMKjiT9WNYLvccknwkEqXikZnvA2T+Dpkijsx N4MidaOf0syVD1bh3X6uiB+r2WbLdT8j0zJ8Og5dqTWsT011PKnMCf4H8z6PIxwp RsMokIabZdn1ul99PTTILPMAMD2oV8E8XMzI49++00PH5bJ14xsHBnIbguaxuDa6 aeOyCNZoWn5gKknEsG0LOkAoagkzvaUUq+ZEBOEKeqbuQDPZU9aMMrlH4gsQVXfJ LEa2h7DNSkShK7NTFugYDaRmec4YFs8CkS7BhbhEvWXaZHMYOaWBcxpzoFaxrJiQ KQfrjxlE/ddI8JFy+KsAQdmM8jE40vNeFf6H/XXrY3Zj6s5rFG87wqaxGW+iVuV/ 1BqpLhXsn8mQN9W+FPHc9zTEco1vDo3fwvDatEWktkNJM/zk2TURG/VBATBd1N+z kansOpHtQ0grEDlhVcYhKBF8XnpmphGGKt4NGN+RE6MYsSa/tErt/bgD6HksVcVa o/HMNFHI8J+PJw== =fGSa -END PGP SIGNATURE-
Hello Pal,
Hello Pal, I am interested to discuss this venture in detail as explained in my previous contact where I expressed my interest in investment cooperation and possibility with you. As a Vice President of a prestigious government owned company; China Railway Construction Corporation (CRCC). I am looking for a possible cooperation with you in your country and the possibility of setting up investments under mutual agreement. Your advise will be very helpful. Regards LIU Chengjun Vice President - CRCC Limited. NO.40 Fuxing Road, Beijing 100855 P.R.China
Hello
Sent from my iPad
Hello
Sent from my iPad
Re: Hello! How can I delete Debian from menu before Windows loading?
On Sat, May 27, 2017 at 08:35:25PM +0200, Didier 'OdyX' Raboud wrote: > Le samedi, 27 mai 2017, 21.01:46 h CEST Александр Макаров a écrit : > > I am thinking to use Debian, but later, because I have no time now. > > > > How can I delete Debian from menu before Windows loading? > > You need to uninstall win32-loader using its' uninstaller, which should be > located in `C:\win32-loader\Uninstall.exe` I think it's more likely it's about grub. Alexandr: does that menu have a blue background? If so, please google "windows restore mbr" and use one of guides that applies to your version of Windows. It'll be easier as your Windows installation is already bootable so you don't need any rescue media. I can't offer you more detailed assistance, though, as I haven't ran Windows outside a VM for a while. I wish you luck if you ever find the time to try Debian again. Meow! -- Don't be racist. White, amber or black, all beers should be judged based solely on their merits. Heck, even if occasionally a cider applies for a beer's job, why not? On the other hand, corpo lager is not a race.
Re: Hello! How can I delete Debian from menu before Windows loading?
Le samedi, 27 mai 2017, 21.01:46 h CEST Александр Макаров a écrit : > Hello! > > I am thinking to use Debian, but later, because I have no time now. > > How can I delete Debian from menu before Windows loading? You need to uninstall win32-loader using its' uninstaller, which should be located in `C:\win32-loader\Uninstall.exe` Cheers, OdyX
Hello! How can I delete Debian from menu before Windows loading?
Hello! I am thinking to use Debian, but later, because I have no time now. How can I delete Debian from menu before Windows loading? Thanks!
Re: Hello: https://manpages.debian.org/man/1/uscan
Le 11/12/2016 à 03:28, Paul Wise a écrit : > You can read about the plans for manpages here: > > https://wiki.debian.org/manpages.debian.org Thank you for the link :) > The debmans software renders manual pages to proper HTML that looked > reasonable to me. According to https://debmans.readthedocs.io/en/latest/design.html#converter, there are several converters so depending which one is used, the generated html will be different. In the source code (debmans/renderer.py), I see classes to call W3M, Mandoc and man2html converters. I saw too that debian-doc is the right list for manpages.d.o so I will go there if I want more details. Stéphane signature.asc Description: OpenPGP digital signature
Re: Hello: https://manpages.debian.org/man/1/uscan
You can read about the plans for manpages here: https://wiki.debian.org/manpages.debian.org The debmans software renders manual pages to proper HTML that looked reasonable to me. -- bye, pabs https://wiki.debian.org/PaulWise
Re: Hello: https://manpages.debian.org/man/1/uscan
Le 06/12/2016 à 16:33, Javier Fernandez-Sanguino a écrit : > The replacement of the service, which is not yet available, will provide > the pages in, I hope, a prettier HTML format. A prettier version of the search area requires only adding css instructions. However, to improve the render of the content of the manpage requires to transform the content of the man page to real html* too. Currently, the content is only wrapped by a tag. Do you plan to do that too (or reuse a library to do it)? *: You can probably make some workarounds but it will be limited and not really maintainable IMO. -- Stéphane signature.asc Description: OpenPGP digital signature
Re: Hello: https://manpages.debian.org/man/1/uscan
Javier Fernandez-Sanguino: > The manpage there is provided through man2html conversion. > ... > The replacement of the service, which is not yet available, > will provide the pages in, I hope, a prettier HTML format. Today I've been playing with an idea about building better HTML pages from POD files for pkg-perl.alioth.debian.org. You can see the preliminary results in this proof of concept: http://pkg-perl.alioth.debian.org/manual_proof-of-concept/autopkgtest.html The same could be done for manpages.debian.org and have a nice, modern, static, responsive website; with [static] search support, PDF, epub, etc... It's built with Sphinx and the wonderful sphinx_rtd_theme (both are already available as stable packages). The only missing piece would be some man2rst converter, though searching for that gives several promising results. Let me know if you'd like more details. Hope this helps! Alex
Re: Hello: https://manpages.debian.org/man/1/uscan
Hello Osamu, On 6 December 2016 at 15:51, Osamu Aoki wrote: > Hi, > > I know the problem is gone but: > > > The URL https://manpages.debian.org/man/1/uscan > > Did you find that reading this extremely long document in manpage is not > what you want? You'd rather read it in html? > > The manpage there is provided through man2html conversion. Well, you can get a PostScript version for a manpage if you prefer, just change the format and resubmit the form (Note: PDF generation does not work currently) > Is it better to have it in html as a part of document? > The replacement of the service, which is not yet available, will provide the pages in, I hope, a prettier HTML format. Regards Javier
Hello: https://manpages.debian.org/man/1/uscan
Hi, I know the problem is gone but: > The URL https://manpages.debian.org/man/1/uscan Did you find that reading this extremely long document in manpage is not what you want? You'd rather read it in html? (Yes, I wrote it into this length) I find it difficult to read long manpages, sometimes. Is it better to have it in html as a part of document? (Currently, no devscripts manpage are available as a part of package.) Just curious, Osamu
Hello Sir
Dear Generous Debian Boss, Thank you very much for your contributions to our planet. You have been very generous. I would like to make a suggestion which Im not sure has been already forseen or noticed and previously suggested. As we are currently developing into a very much raspberry pi programming and developing world, I would like to suggest an online simulator similar to that of Visio in which people can add different kinds of devices like rasperry pi, arduino, beaglebone etc and connect them to various other devices like relays, breadboards, motors etc and run and save their codes. This will not only allow them to practice more with their raspberry pi before going live but will also keep the beginners safe if they are trying to deal with high power or electric currents running through their Pi as.the simulator will regard their project or setup as invalid or unsafe. Thanks and Regards, Richard Barretto
Re: Hello, I have a problem with CPP here
taozhijiang writes:
> I want to using #define / #undef, and want to put them in a single
> macro, some thing like:
> #define DECALRE_TYPE(type) \
> { #undef __curr_type; #define _curr_type type; }
> as we know, this can not passed with CPP, but I need this logical here.
I'm afraid the answer is that you can't do that, since it's not part of
the C programming language. You can't use macro parameters in #define
that way because #define processing happens at too early of a stage in the
compilation process.
> Generally, the problem comes from
> #define ser_field(type, var) \
> ser_new_field(tra, #type, #var, offsetof(struct_type, var))
> I do not want another additional parameter in this macro like
> #define ser_field(type,var,struct_type), and I want a sentence declare
> "current struct type"
> and all later work of ser_field will defaultly use this type.
You can #undef and then #define the ser_field macro with a different
struct_type. I think that's the best solution you'll be able to get while
using only the C preprocessor.
--
Russ Allbery (r...@debian.org)
Hello, I have a problem with CPP here
Hello, all:
I have a program problem, ( may it not have close releationship with
Debian), it described like this:
I want to using #define / #undef, and want to put them in a single
macro, some thing like:
#define DECALRE_TYPE(type) \
{ #undef __curr_type; #define _curr_type type; }
as we know, this can not passed with CPP, but I need this logical here.
Generally, the problem comes from
#define ser_field(type, var) \
ser_new_field(tra, #type, #var, offsetof(struct_type, var))
I do not want another additional parameter in this macro like
#define ser_field(type,var,struct_type), and I want a sentence declare
"current struct type"
and all later work of ser_field will defaultly use this type.
I am not sure whether I can express it clearly, any ideas will be
greately appreciated!
Thanks and B.R.
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52a72046.8010...@gmail.com
Hello!!
http://luis.planapress.org/files/gimgs/cvlr.php?dfg=ghvyq.rbr&ed=fgyut.wswd&fd=awwb
hello!:) My name is Jacalyn...
Hi there! How are u? I'm Jacalyn. I found your fotos in another's account and had the courage to write to you. So if you want to chat with me please, write me something about you Hope you'll answer me. :) Jacalyn -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1328516864.51166.yahoomail...@web122402.mail.ne1.yahoo.com
Re: Hello World!
That's good to hear i hope you have done some reading on the debian website. Each one of us has a role to play irrespective of your background, you can read some of the mailing list archives, and know where to start from. Wishing you the best of luck. 2011/12/23 Arnaud Aliès > Hello debians developers! > I m french, 15 yo > I m very interrested in computer science I already know some > programming langages (python, c++, html, perl...) I have made littles > apps like pythonloic I made my own iphone web app and I m helping in > anon+ project. > Of course I m running debian linux. > I dont think I can help you much but I'd like to see how it goes in a > project like this. > I m very about join this project! > thanks you! > see you > > > -- > To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: > http://lists.debian.org/CAAy5+RG-x1WT7V=xga8q0+_qqx+gqfduscpjnfx0qhinofs...@mail.gmail.com > > -- Prince Annan Koomson Blog <http://annanworld.wordpress.com/> Website <http://annanworld.webs.com/> Twitter <http://twitter.com/pk_annan> Youtube <http://www.youtube.com/surferhttp> <http://twitter.com/pk_annan>Linkedin<http://gh.linkedin.com/pub/prince-annan-koomson/1a/718/786> IBM - Profile<https://www.ibm.com/developerworks/mydeveloperworks/profiles/user/pkannan> +(233) (0) 277 - 154449 We moving de World Proverbs 4:7 Wisdom is the principal thing; therefore get wisdom: and with all thy getting get understanding. CONFIDENTIALITY NOTICE: This email and any attachments are confidential and may also be privileged and is for the sole use of the intended recipient(s). If you are not the addressee or intended recipient, do not disclose, copy, review, distribute, circulate or in any other way or means use or rely on the information contained in this email or any attachments. If received in error, notify the sender immediately and delete this email and any attachments from your system. Emails cannot be guaranteed to be secure or error free as the message and any attachments could be intercepted, corrupted, lost, delayed, incomplete or amended. The owner do not accept liability for damage caused by this email or any attachments and may monitor email traffic. Sender's email address: annan...@gmail.com
Re: Hello World!
Here are some ideas for ways you could get involved in Debian: French translation: http://www.debian.org/international/French http://www.debian.org/international/french/ Writing documentation: http://www.debian.org/doc/ Install the devscripts package and run manpage-alert. You will get a list of packages on your system with commands that have no manual page. Maintaining the website: http://www.debian.org/devel/website/ Maintaining packages: Install the devscripts package and run wnpp-alert. You will get a list of packages on your system that need a new maintainer or need someone to help out. Join the python/perl teams: http://wiki.debian.org/Teams/PythonModulesTeam http://wiki.debian.org/Teams/PythonAppsPackagingTeam http://wiki.debian.org/Teams/DebianPerlGroup Helping with release critical issues: Install the devscripts package and run rc-alert. You will get a list of packages on your system that have a release-critical bug filed against them Help with security issues: http://www.debian.org/security/faq#help Help with infrastructure: You might like to work on the code for qa.debian.org, bugs.debian.org or other development related sites. Help promote Debian: http://wiki.debian.org/Teams/Publicity http://lists.debian.org/debian-publicity/2011/11/msg00054.html Help port Debian packages: https://buildd.debian.org/ -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKTje6FYzSE+opDNh4Nti2T27E9=4My-KF=0wy9xvu-s8au...@mail.gmail.com
Hello World!
Hello debians developers! I m french, 15 yo I m very interrested in computer science I already know some programming langages (python, c++, html, perl...) I have made littles apps like pythonloic I made my own iphone web app and I m helping in anon+ project. Of course I m running debian linux. I dont think I can help you much but I'd like to see how it goes in a project like this. I m very about join this project! thanks you! see you -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAAy5+RG-x1WT7V=xga8q0+_qqx+gqfduscpjnfx0qhinofs...@mail.gmail.com
http://www.gnu.org/s/hello/manual/automake/ ?
>>>>> Adam Borowski writes:
[…]
> GNU's and the inventor of AM_MAINTAINER_MODE's stance:
> http://www.gnu.org/s/hello/manual/automake/maintainer_002dmode.html
BTW, this URI seems to me like a thing to be reported to GNU
webmasters (Cc:'ed.) The Automake manual should be (and it is)
accessible via, e. g.:
http://www.gnu.org/s/automake/manual/html_node/
http://www.gnu.org/software/automake/manual/html_node/
I was also surprised to find that the following URI's are also
valid (but not, e. g., bash/ or tar/):
http://www.gnu.org/s/hello/manual/autoconf/
http://www.gnu.org/s/hello/manual/gettext/
http://www.gnu.org/s/hello/manual/libc/
http://www.gnu.org/s/hello/manual/libtool/
If it was done on purpose, I'd suggest that the respective
“parent” page (http://www.gnu.org/s/hello/manual/) should have
them hyperlinked.
TIA.
[…]
--
FSF associate member #7257
--
To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/86r521mn20.fsf...@gray.siamics.net
Re: removing yada (was: Re: Bug#636016: ITP: goodbye -- next part after 'hello', and a packaging example)
On Sat, Aug 06, 2011 at 05:04:10PM +0100, Tim Retout wrote: > On 31 July 2011 07:53, Steve Langasek wrote: > > It's hard to be sure something like this is a joke when packages like yada > > are still in the archive. > On the subject of yada: since your email, bug #334164 has been > upgraded to RC, yada itself has been orphaned, and I have proposed its > removal to debian-qa. > So if anyone fancies adopting it and arguing in favour of keeping it, > now's the time! If anyone fancies adopting it and arguing in favour of keeping it: get help. It's not too late. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
removing yada (was: Re: Bug#636016: ITP: goodbye -- next part after 'hello', and a packaging example)
On 31 July 2011 07:53, Steve Langasek wrote: > It's hard to be sure something like this is a joke when packages like yada > are still in the archive. On the subject of yada: since your email, bug #334164 has been upgraded to RC, yada itself has been orphaned, and I have proposed its removal to debian-qa. So if anyone fancies adopting it and arguing in favour of keeping it, now's the time! -- Tim Retout -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CADc0ge9K10eGWZqK6svqTKj-F8V5ZUe+QGC114D=a653imw...@mail.gmail.com
Re: Bug#636016: ITP: goodbye -- next part after 'hello', and a packaging example
On Sat, Jul 30, 2011 at 12:17:49PM +0200, Adam Borowski wrote: > Written in a Real Man(tm)'s scripting language with a JIT compiler You should really take advantage of the fact control files are UTF-8 here: > Written in a Real Man™'s scripting language with a JIT compiler (sorely aware that I cannot mock you for this after my mid-freeze doom-wad-shareware upload…) -- Jon Dowland -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110801144159.GB26392@pris
Re: Bug#636016: ITP: goodbye -- next part after 'hello', and a packaging example
On Sat, Jul 30, 2011 at 06:52:20PM +0200, Adam Borowski wrote: > On Sat, Jul 30, 2011 at 12:17:49PM +0200, Adam Borowski wrote: > > * Package name: goodbye > Well, I'm quite surprised that some people didn't take this as a joke. It's hard to be sure something like this is a joke when packages like yada are still in the archive. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature
Re: Bug#636016: ITP: goodbye -- next part after 'hello', and a packaging example
On Sat, Jul 30, 2011 at 12:17:49PM +0200, Adam Borowski wrote: > * Package name: goodbye Well, I'm quite surprised that some people didn't take this as a joke. I've intentionally used over-the-top phrases like "a Real Man(tm)'s scripting language" and so on to make it more obvious, but it seems some folks' sense of humour is not aligned with mine. The package is not a pure waste of time as it has educational value about internals of Debian packages (and perhaps make's quoting rules as well), but it's certainly not meant as something to be followed -- to the contrary, it may point out things that should be banned by the policy. So, my apologies for the confusion. -- 1KB // Yo momma uses IPv4! -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110730165220.ga9...@angband.pl
Re: Bug#636016: ITP: goodbye -- next part after 'hello', and a packaging example
On Sat, Jul 30, 2011 at 12:17:49PM +0200, Adam Borowski wrote:
> Using slow, bloated tools like debhelper and dpkg-dev will cost you precious
> SECONDS when building your package. Multiplied by tens of thousands of
> packages Debian has, this can be a burden on archive rebuilds. Thus, this
> is a proposal and example how to get rid of that inefficiency.
>
> Written in a Real Man(tm)'s scripting language with a JIT compiler, it's
> over two orders of magnitude faster than mainstream packaging techniques.
OK, I bite (although I regret it already…).
In case you really want to upload this to the archive, can you make it
clear in the package description that the packaging practices embodied
by goodbye are just a show off of what can be done, but at the same time
that they are discouraged practices?
No matter how little the risk is, I don't think we want to risk that
people will imitate them in new packages.
--
Stefano Zacchiroli -o- PhD in Computer Science \ PostDoc @ Univ. Paris 7
zack@{upsilon.cc,pps.jussieu.fr,debian.org} -<>- http://upsilon.cc/zack/
Quando anche i santi ti voltano le spalle, | . |. I've fans everywhere
ti resta John Fante -- V. Capossela ...| ..: |.. -- C. Adams
signature.asc
Description: Digital signature
Re: Bug#636016: ITP: goodbye -- next part after 'hello', and a packaging example
On Sat, Jul 30, 2011 at 12:17:49PM +0200, Adam Borowski wrote: > * Package name: goodbye > Git : git://gitorious.org/pkg-goodbye/goodbye.git > > Using slow, bloated tools like debhelper and dpkg-dev will cost you precious > SECONDS when building your package. Multiplied by tens of thousands of > packages Debian has, this can be a burden on archive rebuilds. Thus, this > is a proposal and example how to get rid of that inefficiency. > > Written in a Real Man(tm)'s scripting language with a JIT compiler, it's > over two orders of magnitude faster than mainstream packaging techniques. Sorry for not linking to the .orig tarball (although there's nothing interesting there). Version 0.2 hushes a lintian --pedantic warning about no upstream changelog. We can't have such a stellar example clean with merely the normal options :p dget http://angband.pl/debian/pool/main/g/goodbye/goodbye_0.2-1.dsc About suggestions for clojure and brainf*ck: really, I intended to use an ELF object embedded in debian/rules. The policy says it has to be an executable makefile, but there is no requirement of it being a text file :p Zero bytes and newlines would have to be escaped, but that's nothing new, the tcc version already has to escape the latter. It would satisfy the policy as long as the source would be present and used during build -- but no one says we'd need to stay away from Ken Thompson tricks. There's a bunch of compilers in the archive already which do require themselves to build. -- 1KB // Yo momma uses IPv4! -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110730123646.ga32...@angband.pl
Bug#636016: ITP: goodbye -- next part after 'hello', and a packaging example
Package: wnpp Severity: wishlist Owner: Adam Borowski * Package name: goodbye Upstream Author : myself Git : git://gitorious.org/pkg-goodbye/goodbye.git * License : GPL Programming Lang: C Description : next part after 'hello', and a packaging example Using slow, bloated tools like debhelper and dpkg-dev will cost you precious SECONDS when building your package. Multiplied by tens of thousands of packages Debian has, this can be a burden on archive rebuilds. Thus, this is a proposal and example how to get rid of that inefficiency. Written in a Real Man(tm)'s scripting language with a JIT compiler, it's over two orders of magnitude faster than mainstream packaging techniques. -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110730101749.5824.12147.report...@orthanc.angband.pl
Hello
I wanted to let you know...that the laws of physics are on your side...and that knowing this...I am giving you a gift. Time, is a factor in writing code...that one day will keep up with the speed of light. A dot time dot is the result. The time between dots can vary...and even mean a lot more when the computer is embedded with code.Example...dot time dot frequency dot time dot will end as a code that opens up like a tar file does...or mp3.When the dot is considered...it may be seen as a circle. The circle may rotate if it is half bet or quarter bet.It may rotate right or left...and the light may be different colors. A fiber optic now has code.Open source code. A photo...a video...a picture may be sent whole.And the necessity to code what I for mentioned is now not a necessity. The eye is the clue you are missing at this moment.The eye does the same to some degree.And that's how you send and receive. A globe or a ball is another example. It spins rpm but, the top and bottom are quiet different than the middle.The middle has more area to process code.so you need send two times to equal the middle. Explained...there is another middle...where it will always equal the center middle by using the combined input from two lasers or magnetic heads. The ball then is able to send three times the center middle.The top, bottom and the center middle. Now...what is the ball made of and how is it stable.The answer to this question is not a standard material...but it can range from glass to aluminum.The glass can be an alloy made of copper or even a precious metal exampled by silver.There is much to discover using alloys. Read and write...is liken the old xerox copier...that used light to make a positive or an opposing opposite negative.This copier took the charge and picked up a powered ink.Computers can apply the same methods and even run "near" the speed of light. Knowing what I have reported may be written as a mathematical formula...you then can see the whole picture...as a developer...a programmer...or the end user. I will follow, one day with an explanation of the video card that the computer will one day need.The reason I delay...is I need let you first see what you will see...then you too will see the video card I am thinking about. We are creators...not destroyers.I am asserting that I will never use one erg of energy to create a weapon for the uS.Creators create and never create to destroy what they create. We live by the laws of physics...no matter what your religion is.Money is a waste of labor...and the results are historically proven.I'll not be accusing you, nor do I expect you'll accuse me.Have a good day...even the words I write follow the laws of physics or you would have found them to be unintelligible. We petition and speak as we move our fingers over the keys of the keyboard.Language is everywhere upon this Earth.The abode we live in is a place to learn.From a to z each character of the alphabet can be explained using the laws of physics.We can do this in terms of ergs per or even go further and relate how a good word has a good ending and a bad word diminishes that ending. We are what we eat...in every sense of the term or word. sincerely, George Ronald Adkisson gradk...@lycos.com -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4c8985fd.4060...@lycos.com
Re: hello dear need seo link builder
add me for link exc
Bug#508585: hello
Greetings my dear How are you today, i hope every things is ok with you, i am miss vivian, as is my pleassure to contact you after viewing your e-mail, I am really interest in having communication with you, so if you will have the desire with me so that we can get to know each other better and see what will happened in future. i will be very happy if you can write me back to know all about each other, here is my e-mail(vivianan...@yahoo.com) i will be waiting to hear from you soon, as i wish you all the best for your day. vivian. (vivianan...@yahoo.com) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#508585: hello
Greetings my dear How are you today, i hope every things is ok with you, i am miss vivian, as is my pleassure to contact you after viewing your e-mail, I am really interest in having communication with you, so if you will have the desire with me so that we can get to know each other better and see what will happened in future. i will be very happy if you can write me back to know all about each other, here is my e-mail(vivianan...@yahoo.com) i will be waiting to hear from you soon, as i wish you all the best for your day. vivian. (vivianan...@yahoo.com) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#508585: hello
Greetings my dear How are you today, i hope every things is ok with you, i am miss vivian, as is my pleassure to contact you after viewing your e-mail, I am really interest in having communication with you, so if you will have the desire with me so that we can get to know each other better and see what will happened in future. i will be very happy if you can write me back to know all about each other, here is my e-mail(vivianan...@yahoo.com) i will be waiting to hear from you soon, as i wish you all the best for your day. vivian. (vivianan...@yahoo.com) -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hello dear
Hello dear It sparks my interest to know you better for a nice and lovely relationship full of fun, I am MIRAN JUSTINA by name. i am beautiful single lady, I will appreciate if i read from you soon,for more communications and i will send you my photo for you to know how i look. Awaiting for your reply as soon as possible thanks and take care. my regards MIRAN
Hello
Szia! Találtam egy jó letöltő oldalt legolcsóbb, és nagy tartalom van rajta Filmek, Játékok, Zenék stb... http://speed-ware.no-ip.org Bocsi a zavarásért. Szia, Dóri U.i: én már töltök!. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
HELLO
Greetings, I am Barr. Robert C. Page. I am reaching you to handle an investment portfolio. I am reaching you to assist in repatriating the funds and property left behind by my late client before it will be confiscated by government and declared unserviceable by the bank where the huge deposits were lodged. He died intestate and every attempt to trace any member of his family has proved abortive and unsuccessful. Do note that who you are does not matter and you will be better informed when I hear from you. I want you to respond by sending: 1. Your full names 2. Tel & fax numbers 3. Complete Address Send the above information and I will furnish you with more information about the estate and process of transfer to you. Yours Faithfully, Barrister Robert C. Page esq. London, U.K. N.B: Please respond with your full names, address, phone and fax numbers for the immediate start up of this transaction. Do note that who you are does not matter and you will be better informed when I hear from you.
Hello
hello I'm matty and I wanna be your your friend online. I'm from New york.What's your name? C'mon let's be friend. Bye bye and replied please Sfida subito i tuoi amici online! http://www.jumpy.mediaset.it/Canali_J/Giochi/Directory/Giochi_Multiplayer1.shtml
Re: Hello and request for sponsor (DomainKeys packages)
On Sat, Jun 17, 2006 at 01:13:18PM +0200, Magnus Holmgren wrote: > Greetings, official and unofficial Debian developers! > > So, what do you think, and is anyone willing to sponsor these tiny packages? Hi Magnus, Welcome to Debian! Here are a few notes: 1. you can create debian packages and host them on your site 2. you can join the debian-mentors mailing list for help with debian packageing issues and they can host packages 3. you can try to look for a sponsor for your packages(you did that) 4. you can join the new maintainer process if you want to become part of Debian as a Developer and then eventually upload packages yourself 5. you can join #debian for general packaging help or #debian-devel for more debian specific packaging help on irc 6. read http://planet.debian.org (they sometimes post packaging related things) 7. check out the debian policy manual and other things in http://www.debian.org/devel cheers, Kev -- | .''`. == Debian GNU/Linux == | my web site: | | : :' : The Universal | debian.home.pipeline.com | | `. `' Operating System| go to counter.li.org and | | `-http://www.debian.org/ |be counted! #238656 | | my keysever: pgp.mit.edu | my NPO: cfsg.org | signature.asc Description: Digital signature
Re: Hello and request for sponsor (DomainKeys packages)
You can get a better response on debian-mentors. CCing. andrew On 6/17/06, Magnus Holmgren <[EMAIL PROTECTED]> wrote: Greetings, official and unofficial Debian developers! First, let me introduce myself. I'm a 27-year-old male from Sweden, for the time being living in Linköping where I am (or have been) studying Computer Science and Engineering. My first contact with Debian that I was actually aware of, as well as my first real hands-on experience of Linux system administration and programming, wasn't until 2003, when a study mate of mine, who was the "CIO" of the local student tenants' association, recommended it as the distro of choice if one wanted easy maintenance and security upgrades, which is desirable in a high turnover student association. I have loved Debian and its packaging system ever since. I have been fairly active reporting bugs and submitting patches, I think, both in Debian and upstream, especially since I started running Debian almost exclusively on my own boxes as well. Some are listed on http://www.kibibyte.se/comp/bugs/ (never mind the Swedish). Now I feel that it's time for me to maintain a package or two of my own, and I think I've found the perfect packages to begin with: * libdomainkeys (http://bugs.debian.org/352653), and * libmail-domainkeys-perl (http://bugs.debian.org/373213) The whole DK thing is experimental, but for those wishing to experiment, at least Exim and SpamAssassin are prepared to use these prospective packages. It is also my understanding that Yahoo's license, unlike Microsoft's SenderID license, is quite OK. Is that correct? So, what do you think, and is anyone willing to sponsor these tiny packages? -- Magnus Holmgren[EMAIL PROTECTED], [EMAIL PROTECTED] (No Cc of list mail needed, thanks) -- Andrew Donnellan http://andrewdonnellan.com http://ajdlinux.blogspot.com Jabber - [EMAIL PROTECTED] GPG - hkp://subkeys.pgp.net 0x5D4C0C58 --- Member of Linux Australia - http://linux.org.au Debian user - http://debian.org Get free rewards - http://ezyrewards.com/?id=23484 OpenNIC user - http://www.opennic.unrated.net
Hello and request for sponsor (DomainKeys packages)
Greetings, official and unofficial Debian developers! First, let me introduce myself. I'm a 27-year-old male from Sweden, for the time being living in Linköping where I am (or have been) studying Computer Science and Engineering. My first contact with Debian that I was actually aware of, as well as my first real hands-on experience of Linux system administration and programming, wasn't until 2003, when a study mate of mine, who was the "CIO" of the local student tenants' association, recommended it as the distro of choice if one wanted easy maintenance and security upgrades, which is desirable in a high turnover student association. I have loved Debian and its packaging system ever since. I have been fairly active reporting bugs and submitting patches, I think, both in Debian and upstream, especially since I started running Debian almost exclusively on my own boxes as well. Some are listed on http://www.kibibyte.se/comp/bugs/ (never mind the Swedish). Now I feel that it's time for me to maintain a package or two of my own, and I think I've found the perfect packages to begin with: * libdomainkeys (http://bugs.debian.org/352653), and * libmail-domainkeys-perl (http://bugs.debian.org/373213) The whole DK thing is experimental, but for those wishing to experiment, at least Exim and SpamAssassin are prepared to use these prospective packages. It is also my understanding that Yahoo's license, unlike Microsoft's SenderID license, is quite OK. Is that correct? So, what do you think, and is anyone willing to sponsor these tiny packages? -- Magnus Holmgren[EMAIL PROTECTED], [EMAIL PROTECTED] (No Cc of list mail needed, thanks) pgpqTORqornu4.pgp Description: PGP signature
Sound card issues [WAS: Re: Hello!]
KlarsDev wrote: Hi, i have this problem: I have debian 3.1 sarge installed on my PC, but i encounter some problems with my sound device. My sound card is C-media(external) it works ok, but i have a 5.1 EBODA sound system and i don`t know how to make it work with debian. I tried with alsa but i can only use a 4 channels option. If u could help my on this i would realy appriciate it! Thanks! Hello, A few things: 1. Please use more descriptive subject lines. "Hello!" is a common subject used by spam messages. 2. Your question is exceptionally vague; all we can ascertain is that you have some sort of problem (i.e., you provide no error output). 3. This question is not related to Debian development, but rather is more appropriate for the debian-user list, to which I have directed this message. Regards, -Roberto -- Roberto C. Sanchez http://familiasanchez.net/~roberto -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Hello!
This is a *DEVELOPMENT* mailing list. Send this to debian-user (I've forwarded this) or ask on the Debian forums (http://forums.debian.net). On 6/12/06, KlarsDev <[EMAIL PROTECTED]> wrote: Hi, i have this problem: I have debian 3.1 sarge installed on my PC, but i encounter some problems with my sound device. My sound card is C-media(external) it works ok, but i have a 5.1 EBODA sound system and i don`t know how to make it work with debian. I tried with alsa but i can only use a 4 channels option. If u could help my on this i would realy appriciate it! Thanks! -- Andrew Donnellan http://andrewdonnellan.com http://ajdlinux.blogspot.com Jabber - [EMAIL PROTECTED] GPG - hkp://subkeys.pgp.net 0x5D4C0C58 --- Member of Linux Australia - http://linux.org.au Debian user - http://debian.org Get free rewards - http://ezyrewards.com/?id=23484 OpenNIC user - http://www.opennic.unrated.net -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hello!
Hi, i have this problem:I have debian 3.1 sarge installed on my PC, but i encounter some problems with my sound device. My sound card is C-media(external) it works ok, but i have a 5.1 EBODA sound system and i don`t know how to make it work with debian. I tried with alsa but i can only use a 4 channels option.If u could help my on this i would realy appriciate it!Thanks!
[NOD32: deleted] hello
Mail transaction failed. Partial message is available. Notification from NOD32 Warning: NOD32 Antivirus System for Linux Mail Server found the following infiltrations in this message: file.zip - Win32/Mytob.Y worm - unable to clean - deleted http://www.nod32.com
ウイルス警告 - InterScan for Lotus Notes --> Hello
InterScan has detected a virus during a real-time scan of the email traffic. 日付: 2005/11/29 10:44:00 AM 件名: Hello ウイルス: WORM_MYTOB.A ファイル: doc.scr From: debian-devel@lists.debian.org To: [EMAIL PROTECTED] 処理: 削除済み： Scanned by ScanMail for Lotus Notes 2.6 SP1 with scanengine 7.500-1001 and pattern version 2.971.00 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Hello
Hello!!! My name is Olga. I live in Russia. I have seen your profile and decided to get to know you better. A few words about myself: I am searching serious relationships - if you want just to play with me I ask you not to answer on this letter! But if you want to find LOVE -my email: [EMAIL PROTECTED] I will send my picture after your answer in the next letter. I will wait your answer with great impatience. Hope to hear from you very soon!!! email: [EMAIL PROTECTED] sincere yours, Olga... UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Your message to QNX has been received but it has been quarantined to ensure it is virus free hello
Due to the high volume of messages with zip attachments containing viruses coming into QNX, we have reluctantly decided to quarantine these messages so they can be safely reviewed and passed on if they are determined to be virus free. To expedite your next message to the recipient, and bypass this manual quarantine process, place the words "allow zip file" in the subject line of your message. You may choose to re-send your message (including attachments) immediately including this text in the subject line if it is urgent. We apologize for this inconvenience and we thank you for your cooperation. Questions regarding this message can be sent to mailto:[EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Hello.
On Mon, 26 Aug 2002, David D.W. Downey wrote: > On Tue, Aug 27, 2002 at 03:37:14AM +0300, Nir Peled woke up, and decided to > spew forth: > > I'm SURE you'll have a lot more *customers* If you'll add KDE3.0.3 (Released > > few days ago) I'm also idleing in your server on the OPN network, And if > > you'll join #debian in there you'll see the request for Newer KDE Is big. > > No one likes to compile from source (Which can make a dependencies > > problems). > > So, I know I don't really count for you, but It'll be very nice if you'll > > release an update to KDE. We have customers? We only have users. Please be aware of the distinction.
Re: Hello.
On Tue, Aug 27, 2002 at 03:37:14AM +0300, Nir Peled woke up, and decided to spew forth: > I'm SURE you'll have a lot more *customers* If you'll add KDE3.0.3 (Released > few days ago) I'm also idleing in your server on the OPN network, And if > you'll join #debian in there you'll see the request for Newer KDE Is big. > No one likes to compile from source (Which can make a dependencies problems). > So, I know I don't really count for you, but It'll be very nice if you'll > release an update to KDE. > While this is true, you have to bear in mind both the development cycle timeline as well as the level of bug hunting that takes place in Debian GNU/Linux. Just because the latest and greatest was released the day before does not entitle it to immediate inclusion in Debian. It has a slew of bug testing to go through before it even makes it into the *testing* branch, never mind the stable branch. This is the defining line between Debian and most other distributions. Most other distributions will auto include the latest and greatest with *very* little bug testing (ther than sufficient testing to get it to at least install), whereas Debian GNU/Linux does extensive testing and bug collection *before* it's released. Unstable is the first stop of any application into the Debian stream. Once it's in Unstable, it will be eligible for pipelining further into the system once it's been extensively tested and battered into shape. -- David D.W. Downey <[EMAIL PROTECTED]> Upstream - libpam-pgsql.codecastle.com Debian - Woody: 0.5.2-3 Sid: 0.5.2-5 State - bugs.debian.org/libpam-pgsql "The price of Free Software is Eternal Literacy." "I'd rather die on my feet, than live on my knees." Deloris Clayborn pgpWfIeGQEnzq.pgp Description: PGP signature
KDE 3.0.3 Packages (was: Hello)
On Tue, Aug 27, 2002 at 03:37:14AM +0300, Nir Peled wrote: > Hello, I'm using debian for like 6 months, I used Redhat before. I > gotta say Debian is **A LOT** Better then RH, I like the development > and all. :-) > My only concern is your packages (Not that bad, Just wondering) I'm > wondering why there's only KDE2.2 for stable.. I'm SURE you'll have a > lot more *customers* If you'll add KDE3.0.3 (Released few days ago) > I'm also idleing in your server on the OPN network, And if you'll join > #debian in there you'll see the request for Newer KDE Is big. No one > likes to compile from source (Which can make a dependencies problems). > So, I know I don't really count for you, but It'll be very nice if > you'll release an update to KDE. Perhaps you may be interested in this announcement on DebianPlanet: http://debianplanet.org/node.php?id=778 I don't personally use KDE, but that article and the comments will probably help. Cheers. :) --> Jijo -- Federico Sevilla III : http://jijo.free.net.ph Network Administrator : The Leather Collection, Inc. GnuPG Key ID : 0x93B746BE
Hello.
Hello, I'm using debian for like 6 months, I used Redhat before. I gotta say Debian is **A LOT** Better then RH, I like the development and all. My only concern is your packages (Not that bad, Just wondering) I'm wondering why there's only KDE2.2 for stable.. I'm SURE you'll have a lot more *customers* If you'll add KDE3.0.3 (Released few days ago) I'm also idleing in your server on the OPN network, And if you'll join #debian in there you'll see the request for Newer KDE Is big. No one likes to compile from source (Which can make a dependencies problems). So, I know I don't really count for you, but It'll be very nice if you'll release an update to KDE. Best Regards, Nir peled.
Hello!!!
ENGR.GEORGE MBA. DIRECTOR, MINERALS & NATURAL RESOURCES, SOUTH AFRICAN MINISTRY OF MINING & MINERAL RESOURCES, (SMMR) PRETORIA, REPUBLIC OF SOUTH AFRICA Sir, It is my pleasure to write you this letter on behalf of my colleagues. I have decided to seek a confidential co-operation with you in executing of a deal hereunder for the benefit of all parties, and hope you will keep it confidential because of the nature of this business. I am the Director of Mineral and Natural Resources of the South African Ministry of Mining and Mineral Resources (SMMR) and I have the co-operation of two other top officials, we have in our possession an overdue payment in US funds. The funds represent some percentage of the contract executed on behalf of my ministry by a foreign firm, which we over-invoiced to the amount of US$15,500,000.00 (Fifteen Million Five Hundred Thousand United States Dollars.) Though the actual contract cost has been paid to the original contractor, leaving the excess balance unclaimed. Since the present Government is determined to pay foreign contractors all debts owed, so as to maintain good relationship with other governments. As a result we include our bills for approvals with the co-operation of some officials at the Federal Ministry of Finance. We are seeking your assistance as the Beneficiary of the unclaimed funds, since we are not allowed to operate a foreign account. We hereby propose that, should you be willing to assist us in this transaction your share as compensation will be 30% while my colleagues and I receive 60% and 10% for miscellaneous expenses. This business itself is 100% safe, provided you treat it with utmost confidentiality. I have reposed my confidence in you and hope that you will not disappoint us. Kindly notify me by Email for further details, upon your acceptance of this proposal. Best Regards, Engr. George Mba
Hello,please try again ScanMail has detected a virus!
<>
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
Steven Hanley <[EMAIL PROTECTED]> immo vero scripsit > Just because it seems at the moment that too many translation notifications > are being generated for them to be placed into the bts I wonder if it is > overkill/added complexity to try to use something else, as I would assume the > number of translation notifications happening will not be so high permanently. Don't assume. Take a diff of Packages.gz and see how many of the "original" text seem to change every day, and then talk. There will be quite a lot of translations, and reuploading, and other things, after things have settled down, as it were. regards, junichi -- [EMAIL PROTECTED] http://www.netfort.gr.jp/~dancer
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Wed, Sep 05, 2001 at 02:44:01PM +0200, Michael Bramer wrote: > On Wed, Sep 05, 2001 at 09:49:09PM +1000, Hamish Moffatt wrote: > > On Wed, Sep 05, 2001 at 12:11:56PM +0100, Nick Phillips wrote: > > > I'd have thought that the current situation re. maintainers putting > > > translations into .debs makes it blindingly obvious that requiring them > > > to do so in order for a translation to become available is a bad idea. > > > > Do package descriptions change so regularly that translated descriptions > > couldn't be submitted through the bug tracking system and included > > in the next upload? > > > > Most of my packages have never had their description changed from > > when I first wrote it. It would be better if we could just include > > translated descriptions in the debian/control file. > > See also the other mail: >50 changes in 10 days in main/sid > > But if you include the translation only in the debian/control you have > - delays (maybe we have a override file and can solve this) > - you will have outdated translations (like debconf now) > - you must patch dpkg etc. in a wide way > > We can include the translation in the package. This is not the > problem, but please not in the control file. The translation is no new > information of the package, it is only a translation. Only a other form of > the orignal text. > > Please read the last proposal, I explain a possibly solution in it. I wonder if the translators are over reacting here, yes people seem worried aboout the number of bug reports or whatever translations are generating. However this is because at the moment the translation effort is generating a lot of output. A lot of output is generated in some manner whenever there is a large addition to the distribution. Such as a new port. For example when ia64 porters did a whole lot of automatic bug submissions en masse a few months ago, some people got annoyed at the behavior, however that was an example of a new addition to debian generating a huge number of changes or needs for bug fixing. Thus it is obvious that when adding a lot of brand new shiny translations to packages a lot of bug reports would be generated (or translations notifications or whatever.) However once the translation effort settles down (which I assume will happen at some point, ie when the majority of packages have translated descriptions) the only times you get a whole lot of messages about translation is for each new package added to debian, or if description changes. The second is rare as has been pointed out, and new packages, well everything else about a packagve goes into the bts. Just because it seems at the moment that too many translation notifications are being generated for them to be placed into the bts I wonder if it is overkill/added complexity to try to use something else, as I would assume the number of translation notifications happening will not be so high permanently. As someone has pointed out the translation effort for the strings inside packages outputs to the bts, why not this, afterall once this settles down i would assume description translations would generate a much smaller stream of translations for packages already in debian. See You Steve -- [EMAIL PROTECTED] http://wibble.net/~sjh Look Up In The Sky Is it a bird? No Is it a planeNo Is it a small blue banana? Yes
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
Previously Martin Quinson wrote: > 1) Do the translation Right. > 2) Put the translation in the Debian archive Wrong. `Make the translation available' would be better. Not all packages are in the Debian archive, and they have to be just as useful without being forced to be in there. > 3) Publish the translation, ie make sure it comes to the user hard disk when >the package gets available, even before it gets installed Not sure about that. `Make it possible to access a translation for a specific version of a specific package' would be better. > 4) Use the translation when environment variable is properly set, and when >the user ask dpkg & Cie about a package. Right. > My patch gives a solution to 4, given that you use the gettext solution for > 3, and maybe for 1-3. The ddts give a solution for 1. Right, but 2 and 3 are the interesting ones and 4 is just a technical implementation to access the data. > You want to handle 2 by putting the translation in the package. No, I want it to be possible to have it in the package, but it might be elsewhere as well. Putting all translations in all packages doesn't scale, but having multiple translations in a package can be useful (think packages not in a full archive, for example a vendor shipping debs on a CD). > That's ok, but with which form ? There is at least two solutions: in a > po file located somewhere in debian/ dir, or directly in the control > file. You prefere the second solution, am I right ? For translations inside the package, yes, definitely. > As far as I understand, you want to take the descriptions aways from > the /var/lib/dpkg/status file, and make several files, one per > language. this would make the status DB lighter, and ease the handle > of several languages. I want the status file as it is to change, it contains much more information then dpkg needs to do most of its work. Non-essential data such as descriptions, maintainer info, etc. can be moved to a seperate new file that tools like dpkg-query and frontends can access (dpkg still needs to update it of course). Wichert. -- _ / Nothing is fool-proof to a sufficiently talented fool \ | [EMAIL PROTECTED] http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D |
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Tue, Sep 11, 2001 at 03:47:36PM +0200, Wichert Akkerman wrote: > Previously Martin Quinson wrote: > > Could you please explain what you're thinking about ? I am interessed in > > allowing end user having translation. I don't really care about the way it > > is done[*]. But with such a cryptic mail, it's hard to figure what can be > > done for my perticular problem in your much larger framework... > > I'm not thinking of anything in particular at the moment, mostly just > following the discussion and noting possible issues. > > At this moment translations are simply not on the top of the todo-list > for dpkg, and we already know that we will need some infrastructure to > support them properly that does not exist at the moment. Agreed. > > What do I have to do to be informed about dpkg development ? > > Follow CVS. I also did, but I just subscribed to dpkg-cvs to ease this task. > > [*]: ie, I think gettext does what we need, but if you explain what's wrong > > about that, I'm pretty flexible. > > You've already been told a few times that gettext only does a small (and > simple) part of what is involved. Ok, I'll try to summarize the problem to face. Please correct me if I'm wrong. 1) Do the translation 2) Put the translation in the Debian archive 3) Publish the translation, ie make sure it comes to the user hard disk when the package gets available, even before it gets installed 4) Use the translation when environment variable is properly set, and when the user ask dpkg & Cie about a package. My patch gives a solution to 4, given that you use the gettext solution for 3, and maybe for 1-3. The ddts give a solution for 1. [In the rest, when I say 'You', I don't mean 'You, Wichert', but 'You, dpkg devellopers', or something even larger] I think your opinion about 1 is that it's a translator issue, and I agree. But the "Prefect Solution"(TM) have to take their point of view in account, haven't it ? You want to handle 2 by putting the translation in the package. That's ok, but with which form ? There is at least two solutions: in a po file located somewhere in debian/ dir, or directly in the control file. You prefere the second solution, am I right ? 3 is pretty hard to handle when you put the translation in a po file, and simpler when it's in the control file (but this approach leads to others problems, mainly from the translator point of view). As far as I understand, you want to take the descriptions aways from the /var/lib/dpkg/status file, and make several files, one per language. this would make the status DB lighter, and ease the handle of several languages. Sorry to annoy you all about translating package descriptions, but that's an important point for me. I'm willing to help, and the only answers I get are "you're deadly wrong". So I'm trying to understand how to do it right... Thanks, Mt.
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
Previously Martin Quinson wrote: > Could you please explain what you're thinking about ? I am interessed in > allowing end user having translation. I don't really care about the way it > is done[*]. But with such a cryptic mail, it's hard to figure what can be > done for my perticular problem in your much larger framework... I'm not thinking of anything in particular at the moment, mostly just following the discussion and noting possible issues. At this moment translations are simply not on the top of the todo-list for dpkg, and we already know that we will need some infrastructure to support them properly that does not exist at the moment. > What do I have to do to be informed about dpkg development ? Follow CVS. > [*]: ie, I think gettext does what we need, but if you explain what's wrong > about that, I'm pretty flexible. You've already been told a few times that gettext only does a small (and simple) part of what is involved. Wichert. -- _ / Nothing is fool-proof to a sufficiently talented fool \ | [EMAIL PROTECTED] http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D |
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Wed, Sep 05, 2001 at 12:20:42PM +0100, Nick Phillips wrote: > On Wed, Sep 05, 2001 at 12:00:42PM +0200, Michael Bramer wrote: > > > > It needs to be stored, in /var/lib/dpkg/status, as a single file. This > > > is so > > > that dpkg can make safe updates to it. Trying to sync multiple files is > > > not a > > > simple solution. > > > > no, it does not store there. And I can explain it: > > Well, shouldn't it? Wouldn't it make sense to have the translated description > in there rather than the original one? What if several admins does not speak the same languages ? Mt
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Fri, Sep 07, 2001 at 03:36:32AM +0200, Wichert Akkerman wrote: > Previously Michael Bramer wrote: > > I am right and the translated description don't need be store in the > > status file? > > Yes and no. That is just a side-effect of a possible larger change. Could you please explain what you're thinking about ? I am interessed in allowing end user having translation. I don't really care about the way it is done[*]. But with such a cryptic mail, it's hard to figure what can be done for my perticular problem in your much larger framework... I am willing to (try to) help, but it's hard without a decent information. I'm subscribed on -dpkg since months, and I did not see any related mail either. What do I have to do to be informed about dpkg development ? Bye, Mt. [*]: ie, I think gettext does what we need, but if you explain what's wrong about that, I'm pretty flexible.
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Fri, Sep 07, 2001 at 10:35:06AM +0200, Christian Kurz wrote: > So you want to compare packages from an upstream with packages created > by either someone or a team for a distribution? No, I'm saying that if you're dealing with a package that will be distributed by means over which you have no control, then you are forced to include the translation in the package. If you have control over the distribution methods, then you can integrate the translation system into the distribution system however is most convenient, which almost certainly doesn't mean forcing it into the package in every case. > > If on the other hand you are one of those distributions, distributing > > all sorts of packages, some of which have upstream translations, some of > > which don't, some of whose maintainers are able and willing to spend time > > on translations, some of whose maintainers aren't, then it doesn't make > > sense to set yourselves up in such a way (translations always living in > > packages) that translations will only be available when the maintainer > > does work on them. > > Which creates the situation, that packages in debian will on the one > hand be different then the one you can get from the upstream and on the > other hand it's a violation of our social-contract: No, it doesn't. > So if we correct wrong translation or create a new translation, then we > shall send it to the upstream and inform them. With your suggestion > above, this will only happen, if either the translator is doing this > task also or if the maintainer is taking care of the translation. In all > other cases, where the maintainer is not taking care of the translation, > we'll have a nice violation of that statement. And since the maintainer > is the contact to the upstream and responsible for the debian package, > he shall be involved in the translation. Great. So rather than have a system that enables us to get a working translation, the option for the maintainer to be notified/involved, and otherwise the ability for the translators to send translations upstream, you'd rather keep banging your head against the brick wall that is maintainers just not able/willing/with enough time to deal with, check, integrate translations, and keep *us*, never mind upstream, from getting good translations. Feel free to keep banging your head against any walls you like, but don't complain when you find you're not getting through. > Splitting translation out of upstream packages is in my opinion a bad > thing and should never be done. I was careful to avoid suggesting that such a thing should be done. Although providing a better/alternative translation as an override should be simple. And if a maintainer decides that the upstream translations are worse than useless, then yes, they should be free to remove them, and the translation project should be able to provide alternatives without necessarily causing extra work for the maintainer. > > Fine, no-one is saying that you shouldn't be able to arrange to be notified > > when a particular package has a translation made available. > > And how do you propose to integration this notifications? According to > your statement, everyone can update the translation without having to > hassle with me and that's the point which makes me sad. If a translation is added to the official Debian archive, then it would be simple to arrange to notify any maintainer who wanted to know. If some third party at some random site provides a translation archive, then it's up to them whether they tell you or not. That doesn't mean that we shouldn't provide a mechanism for them to do so. It's free software after all. That means that if someone wants to do a translation, or if they want to run the code through an obfuscator, they don't *have* to tell you. Cheers, Nick -- Nick Phillips -- [EMAIL PROTECTED] Abandon the search for Truth; settle for a good fantasy.
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On 01-09-06 Nick Phillips wrote: > On Thu, Sep 06, 2001 at 07:47:26PM +0200, Christian Kurz wrote: > > > > upstream packages because they are not part of a package? The > > > > translation of the error messages and other messages of a program belong > > > > to the package of it. > > > That depends on whether you're distributing one package or thousands. > > Why do make this dependant on the number of packages? I think that using > > some count like you do, is a bad thing. > Because if you're only distributing one package or small group of packages > (say, KDE), then your focus is making the translations available for all the So you want to compare packages from an upstream with packages created by either someone or a team for a distribution? > people who use that package, whether or not the particular distribution > they got it from has infrastructure to support translations. Hence it makes > sense to put the translations in the package in that case. > If on the other hand you are one of those distributions, distributing > all sorts of packages, some of which have upstream translations, some of > which don't, some of whose maintainers are able and willing to spend time > on translations, some of whose maintainers aren't, then it doesn't make > sense to set yourselves up in such a way (translations always living in > packages) that translations will only be available when the maintainer > does work on them. Which creates the situation, that packages in debian will on the one hand be different then the one you can get from the upstream and on the other hand it's a violation of our social-contract: | software will be widely distributed and used. We will feed back | bug-fixes, improvements, user requests, etc. to the "upstream" authors | of software included in our system. So if we correct wrong translation or create a new translation, then we shall send it to the upstream and inform them. With your suggestion above, this will only happen, if either the translator is doing this task also or if the maintainer is taking care of the translation. In all other cases, where the maintainer is not taking care of the translation, we'll have a nice violation of that statement. And since the maintainer is the contact to the upstream and responsible for the debian package, he shall be involved in the translation. Splitting translation out of upstream packages is in my opinion a bad thing and should never be done. > > > But if we want to be, and are, able to easily add extra translations, or > > > override poor-quality upstream translations (all without causing hassles > > > for > > > maintainers), then why not? > > Because for example I would prefer to be informed if any of my packages > > has a bad upstream translation and some has better one for me. Then I > > can forward and discuss it with the upstream and he can include it maybe > > in the official upstream sources. That way we wouldn't only improve the > > translation for people using debian, but also for people who are using > > some other free operating system and the upstream package. > Fine, no-one is saying that you shouldn't be able to arrange to be notified > when a particular package has a translation made available. And how do you propose to integration this notifications? According to your statement, everyone can update the translation without having to hassle with me and that's the point which makes me sad. Christian -- Debian Developer (http://www.debian.org) 1024/26CC7853 31E6 A8CA 68FC 284F 7D16 63EC A9E6 67FF 26CC 7853 pgpDbHwSPjryI.pgp Description: PGP signature
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
Previously Michael Bramer wrote: > I am right and the translated description don't need be store in the > status file? Yes and no. That is just a side-effect of a possible larger change. Wichert. -- _ / Nothing is fool-proof to a sufficiently talented fool \ | [EMAIL PROTECTED] http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D |
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Thu, Sep 06, 2001 at 07:47:26PM +0200, Christian Kurz wrote: > > > upstream packages because they are not part of a package? The > > > translation of the error messages and other messages of a program belong > > > to the package of it. > > > That depends on whether you're distributing one package or thousands. > > Why do make this dependant on the number of packages? I think that using > some count like you do, is a bad thing. Because if you're only distributing one package or small group of packages (say, KDE), then your focus is making the translations available for all the people who use that package, whether or not the particular distribution they got it from has infrastructure to support translations. Hence it makes sense to put the translations in the package in that case. If on the other hand you are one of those distributions, distributing all sorts of packages, some of which have upstream translations, some of which don't, some of whose maintainers are able and willing to spend time on translations, some of whose maintainers aren't, then it doesn't make sense to set yourselves up in such a way (translations always living in packages) that translations will only be available when the maintainer does work on them. Think about it. > > But if we want to be, and are, able to easily add extra translations, or > > override poor-quality upstream translations (all without causing hassles for > > maintainers), then why not? > > Because for example I would prefer to be informed if any of my packages > has a bad upstream translation and some has better one for me. Then I > can forward and discuss it with the upstream and he can include it maybe > in the official upstream sources. That way we wouldn't only improve the > translation for people using debian, but also for people who are using > some other free operating system and the upstream package. Fine, no-one is saying that you shouldn't be able to arrange to be notified when a particular package has a translation made available. There is a difference between "not requiring a maintainer to be involved in the provision of translations" and "not enabling a maintainer to be involved in the provision of translations". -- Nick Phillips -- [EMAIL PROTECTED] Fine day to work off excess energy. Steal something heavy.
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On 01-09-06 Nick Phillips wrote: > On Thu, Sep 06, 2001 at 01:08:25PM +0200, Christian Kurz wrote: > > On 01-09-05 Nick Phillips wrote: > > > The translation of any part of a package, be it the text of error > > > messages, > > So, shall we now remove all .po files and other translation from > > upstream packages because they are not part of a package? The > > translation of the error messages and other messages of a program belong > > to the package of it. > That depends on whether you're distributing one package or thousands. Why do make this dependant on the number of packages? I think that using some count like you do, is a bad thing. > If upstream includes translations, then we don't have to worry about the > maintainer managing inclusion of whichever languages people happen to write > translations for. > But if we want to be, and are, able to easily add extra translations, or > override poor-quality upstream translations (all without causing hassles for > maintainers), then why not? Because for example I would prefer to be informed if any of my packages has a bad upstream translation and some has better one for me. Then I can forward and discuss it with the upstream and he can include it maybe in the official upstream sources. That way we wouldn't only improve the translation for people using debian, but also for people who are using some other free operating system and the upstream package. Christian -- Debian Developer (http://www.debian.org) 1024/26CC7853 31E6 A8CA 68FC 284F 7D16 63EC A9E6 67FF 26CC 7853 pgpobuT4Njd53.pgp Description: PGP signature
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Wed, Sep 05, 2001 at 10:18:04AM -0400, Vociferous Mole wrote: > I disagree with this. Translation of text that is part of the upstream > source needs[1] to go to/through the maintainer, as it should be > integrated upstream. > > Steve > > [1] Okay, it *could* be sent directly upstream, but often the debian > maintainer has an established relationship to the upstream author, > and may be able to fit them into the package more cleanly. And if the maintainer is in the "no time for translations" camp, then nothing happens. There's no reason why we can't cater for all types of maintainer. -- Nick Phillips -- [EMAIL PROTECTED] You will feel hungry again in another hour.
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Thu, Sep 06, 2001 at 01:08:25PM +0200, Christian Kurz wrote: > On 01-09-05 Nick Phillips wrote: > > The translation of any part of a package, be it the text of error messages, > > So, shall we now remove all .po files and other translation from > upstream packages because they are not part of a package? The > translation of the error messages and other messages of a program belong > to the package of it. That depends on whether you're distributing one package or thousands. If upstream includes translations, then we don't have to worry about the maintainer managing inclusion of whichever languages people happen to write translations for. But if we want to be, and are, able to easily add extra translations, or override poor-quality upstream translations (all without causing hassles for maintainers), then why not? Cheers, Nick -- Nick Phillips -- [EMAIL PROTECTED] Everything will be just tickety-boo today.
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On 01-09-05 Nick Phillips wrote: > The translation of any part of a package, be it the text of error messages, So, shall we now remove all .po files and other translation from upstream packages because they are not part of a package? The translation of the error messages and other messages of a program belong to the package of it. Christian -- Debian Developer (http://www.debian.org) 1024/26CC7853 31E6 A8CA 68FC 284F 7D16 63EC A9E6 67FF 26CC 7853 pgpNVcw3nJbiu.pgp Description: PGP signature
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Thu, Sep 06, 2001 at 08:43:10PM +1000, Hamish Moffatt wrote: > On Wed, Sep 05, 2001 at 02:44:01PM +0200, Michael Bramer wrote: > > See also the other mail: >50 changes in 10 days in main/sid > > In a single package? Huh? no. The description of >50 deb-packages from the debian distribution main/sid/binary-i386 (with >6000 Packages) had changed in the last 10 days. > > But if you include the translation only in the debian/control you have > > - delays (maybe we have a override file and can solve this) > > - you will have outdated translations (like debconf now) > > Yes, such is life. I don't see these as being sufficient reason > to invent a completely new system for dealing with this data. No outdated translations is a very big problem. The system should better show untranslated descriptions than outdated translation. Also the delay is a big problem. And if the the maintainer fast and upload after a change in the translation, we kill all the autobuilder. A translation is no 'data' like Dependes, Description, Package. A translation is only a translation, a other form of the data in a other languages and a other encoding. And we don't need a completely new system for translations! We have a old, very well tested system and we propose to use this system: gettext. Gettext make all the work and we don't need a new system in dpkg and apt. > > - you must patch dpkg etc. in a wide way > > This is not a good excuse. dpkg is a Debian-specific tool, > and so it should be modified if there is good reason to do so. > Don't work around it. I agree with this. If we need new features in dpkg, we should patch it. And yes, we have propose a patch for dpkg. But you should not break the dpkg with a big patch only for translation. Make it smart. Use this -9/+30 patch and you have it. > > We can include the translation in the package. This is not the > > problem, but please not in the control file. The translation is no new > > information of the package, it is only a translation. Only a other form of > > the orignal text. > > I don't see why the distinction is necessary. sorry, it is usefull. Gruss Grisu -- Michael Bramer - a Debian Linux Developer http://www.debian.org PGP: finger [EMAIL PROTECTED] -- Linux Sysadmin -- Use Debian Linux Weiß vielleicht jemand warum ich meine Freundin ständig anrufen soll, seitdem sie ihr neues Handy mit Vibrationsalarm hat? (Volker Flohr in daa'ooo) pgpT2CQTG5mk0.pgp Description: PGP signature
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Wed, Sep 05, 2001 at 02:44:01PM +0200, Michael Bramer wrote: > See also the other mail: >50 changes in 10 days in main/sid In a single package? Huh? > But if you include the translation only in the debian/control you have > - delays (maybe we have a override file and can solve this) > - you will have outdated translations (like debconf now) Yes, such is life. I don't see these as being sufficient reason to invent a completely new system for dealing with this data. > - you must patch dpkg etc. in a wide way This is not a good excuse. dpkg is a Debian-specific tool, and so it should be modified if there is good reason to do so. Don't work around it. > We can include the translation in the package. This is not the > problem, but please not in the control file. The translation is no new > information of the package, it is only a translation. Only a other form of > the orignal text. I don't see why the distinction is necessary. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Wed, Sep 05, 2001 at 10:42:12PM -0500, David Starner wrote: > On Thu, Sep 06, 2001 at 01:08:52AM +0200, [EMAIL PROTECTED] wrote: > > On Wed, 5 Sep 2001, Branden Robinson wrote: > > > > > On Wed, Sep 05, 2001 at 08:46:12PM +0200, Michael Bramer wrote: > > > >The maintainer need not do anything. Maybe he don't know the > > > >translation. The user only use this. This need only the > > > >translators. > > > > > > While we're on the subject, can you get someone to translate your mails > > > into a comprehensible dialect of English? > > > > Branden, please don't be rude. > > True, Branden was rude. But the fact that grisu's emails are sometimes hard > to understand has been a stumbling block for me; it would certainly help to > get a translator/editor for the full blown proposals. sorry, about this problem. Maybe someone can help and translate the proposal. Gruss Grisu -- Michael Bramer - a Debian Linux Developer http://www.debian.org PGP: finger [EMAIL PROTECTED] -- Linux Sysadmin -- Use Debian Linux --== Free Software: Contribute nothing, expect nothing ==-- pgpiIjO3UkQvb.pgp Description: PGP signature
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Wed, Sep 05, 2001 at 03:56:38PM -0500, Adam Heath wrote: > On Wed, 5 Sep 2001, Wichert Akkerman wrote: > > > Previously Nick Phillips wrote: > > > Well, shouldn't it? Wouldn't it make sense to have the translated > > > description > > > in there rather than the original one? > > > > I actually makes more sense to remove even the english description > > from status to another location. > > Note, that there is no reason dpkg could not be modified to read from multiple > status files. what? sorry, but in a other mail you say: > It needs to be stored, in /var/lib/dpkg/status, as a single file. This is so > that dpkg can make safe updates to it. Trying to sync multiple files is not a > simple solution. I am right and the translated description don't need be store in the status file? Gruss Grisu -- Michael Bramer - a Debian Linux Developer http://www.debian.org PGP: finger [EMAIL PROTECTED] -- Linux Sysadmin -- Use Debian Linux "Wie haben andere Linux Benutzer ihr `erstes Mal' mit Linux erlebt??" "Wir haben danach gemeinsam eine Gitanes geraucht und nochmal ueber alles geredet." -- P.Vollmann und Stefanie Teufel in dcolm pgplyEQLoJbS1.pgp Description: PGP signature
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Thu, Sep 06, 2001 at 01:23:12PM +1000, Martijn van Oosterhout wrote: > On Wed, Sep 05, 2001 at 08:46:12PM +0200, Michael Bramer wrote: > >With this the maintainers get some mails from the translator > >project. More like now. Now we only at the start, now we don't make > >a real review process. Now we have only 10 languages. > > I thought there was mention of translations mailing lists where all the > translations are sent to in addition to the maintainer. I thought that was > the review process. yes and no. Now all french translations are send to the debian-i10n-french ML ist. Because of this we have more fr updates like de or pt_BR. But after some time the ddts server will make a own review process. It will send all finish translated description a second time to the translators for a review. Gruss Grisu -- Michael Bramer - a Debian Linux Developer http://www.debian.org PGP: finger [EMAIL PROTECTED] -- Linux Sysadmin -- Use Debian Linux Ja, aber der Bootvorgang ist doch so sch?n mit den Wolken und so. Das st?rt meiner Meinung nach garnicht. (Martin Heinz zum Rebooten von M$-W) pgpCOb2Lao7PM.pgp Description: PGP signature
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Thu, Sep 06, 2001 at 01:08:52AM +0200, [EMAIL PROTECTED] wrote: > On Wed, 5 Sep 2001, Branden Robinson wrote: > > > On Wed, Sep 05, 2001 at 08:46:12PM +0200, Michael Bramer wrote: > > >The maintainer need not do anything. Maybe he don't know the > > >translation. The user only use this. This need only the > > >translators. > > > > While we're on the subject, can you get someone to translate your mails > > into a comprehensible dialect of English? > > Branden, please don't be rude. True, Branden was rude. But the fact that grisu's emails are sometimes hard to understand has been a stumbling block for me; it would certainly help to get a translator/editor for the full blown proposals. -- David Starner - [EMAIL PROTECTED] Pointless website: http://dvdeug.dhis.org "I don't care if Bill personally has my name and reads my email and laughs at me. In fact, I'd be rather honored." - Joseph_Greg
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Wed, Sep 05, 2001 at 08:46:12PM +0200, Michael Bramer wrote: >With this the maintainers get some mails from the translator >project. More like now. Now we only at the start, now we don't make >a real review process. Now we have only 10 languages. I thought there was mention of translations mailing lists where all the translations are sent to in addition to the maintainer. I thought that was the review process. After all, I don't really know enough Dutch to do a lot of translating work, but I know easily enough to check other peoples translations. -- Martijn van Oosterhout http://svana.org/kleptog/ > Magnetism, electricity and motion are like a three-for-two special offer: > if you have two of them, the third one comes free.
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Wed, 5 Sep 2001, Branden Robinson wrote: > On Wed, Sep 05, 2001 at 08:46:12PM +0200, Michael Bramer wrote: > >The maintainer need not do anything. Maybe he don't know the > >translation. The user only use this. This need only the > >translators. > > While we're on the subject, can you get someone to translate your mails > into a comprehensible dialect of English? Branden, please don't be rude. The very fact that grisu's English is not that good, explains why it's so damn important to support translations. -- wouter dot verhelst at advalvas in Belgium This is Linux world. On a quiet day, you can hear Windows reboot.
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Wed, Sep 05, 2001 at 08:46:12PM +0200, Michael Bramer wrote: >The maintainer need not do anything. Maybe he don't know the >translation. The user only use this. This need only the >translators. While we're on the subject, can you get someone to translate your mails into a comprehensible dialect of English? -- G. Branden Robinson| One man's "magic" is another man's Debian GNU/Linux | engineering. "Supernatural" is a [EMAIL PROTECTED] | null word. http://people.debian.org/~branden/ | -- Robert Heinlein pgpX0kyKT5HN9.pgp Description: PGP signature
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Wed, 5 Sep 2001, Wichert Akkerman wrote: > Previously Nick Phillips wrote: > > Well, shouldn't it? Wouldn't it make sense to have the translated > > description > > in there rather than the original one? > > I actually makes more sense to remove even the english description > from status to another location. Note, that there is no reason dpkg could not be modified to read from multiple status files.
Re: Hello
> would even dare try it. I have decided to offer windows and siding > to you, at our basic cost. In other words, I'm going to offer you > windows and siding for no personal profit whatsoever! This will I am quite sorry, but I have no desire to install Windows. That is why I use Linux. However, I have never heard of Siding - does it only work on Windows - or is it platform independent? Thank you, Constantine
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Wed, Sep 05, 2001 at 08:46:12PM +0200, Michael Bramer wrote: >Sorry, but if some maintainers complain about this mails (without >real work on there site) now, they don't make a good work in the >future. To be honest, I find it more annoying getting form mails like the notifications than to get mails which require some action on my part. -- "You grabbed my hand and we fell into it, like a daydream - or a fever." pgpGVGOrQc5Gi.pgp Description: PGP signature
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Wed, Sep 05, 2001 at 09:13:00AM -0500, Branden Robinson wrote: > On Wed, Sep 05, 2001 at 09:49:09PM +1000, Hamish Moffatt wrote: > > Do package descriptions change so regularly that translated descriptions > > couldn't be submitted through the bug tracking system and included > > in the next upload? > > That doesn't serve the purpose of hijacking pieces of the maintainer's > package away from him, which, as you'll note, is the foundational > premise of Michael Bramer's entire proposal. > > He doesn't want the maintainer involved at all, except to sit by > helplessly and get flooded with emails notifying him that his package > has been modified yet again. sorry, branden. 1.) you speak only about the 1. proposal 2.) In the last proposal, I propose a way to include the translation in the package. This proposal has some improvments and is more exact. 3.) I don't flooded the maintainer. 4.) In this list and per PM I get some request about this mails. If I hadn't support this mails, some maintainers whould have wept. 5.) I ask yesterday if we should stop this mails, and only some make this request. 6.) I and some other translators get some 'Thanks' after the notifcation mail. This is not wrong in all ways. 7.) This notification mails are like the mails from the BTS or from katie 8.) This mails are not helplessly. I know some translators, who get improvments from the maintainer. 9.) If you right and this mails are useless, we should put the maintainer out of the loop. But you are wrong. Some maintainers are very active and help the translators. 10.) Make you the request to send this all to the BTS? If we make the translations, we have two excesses: - we put the maintainer really in the loop (without a override file) With this the maintainers get some mails from the translator project. More like now. Now we only at the start, now we don't make a real review process. Now we have only 10 languages. In this case the maintainer must make the whole work after the translation. Sorry, but if some maintainers complain about this mails (without real work on there site) now, they don't make a good work in the future. - we put the maintainer out of the loop The maintainer need not do anything. Maybe he don't know the translation. The user only use this. This need only the translators. I don't propose one of this excesses now. I post a proposal with both sites. Gruss Grisu -- Michael Bramer - a Debian Linux Developer http://www.debian.org PGP: finger [EMAIL PROTECTED] -- Linux Sysadmin -- Use Debian Linux «Computers are like air conditioners -- they stop working properly if i you open WINDOWS» pgppMJua4uT92.pgp Description: PGP signature
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
Previously Nick Phillips wrote: > Well, shouldn't it? Wouldn't it make sense to have the translated description > in there rather than the original one? I actually makes more sense to remove even the english description from status to another location. Wichert. -- _ / Nothing is fool-proof to a sufficiently talented fool \ | [EMAIL PROTECTED] http://www.liacs.nl/~wichert/ | | 1024D/2FA3BC2D 576E 100B 518D 2F16 36B0 2805 3CB8 9250 2FA3 BC2D |
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Thu, Sep 06, 2001 at 01:07:40AM +1000, Martijn van Oosterhout wrote: > > The description is part of the package, can we agree on that one? > > What is the difference between a translated description and the > > original one, except for which language it is written in? The original, canonical, description is part of the package, and a necessary part at that. Others aren't. They're just different representations of the original one, and don't *need* to be provided by the maintainer. If the maintainer chooses to provide, obtain, manage translations, fine. If not, also fine. The translations are not a necessary part of the package, they are related to it, and could be provided however is most convenient for the situation at hand - not necessarily in one big lump. > Well, all descriptions are in english by default and there is no real reason > to store every description for every package on every machine/archive. Exactly. > > The package is the responsibility of the maintainer, and s/he has the > > final words on all aspects of how it should be packaged (subject to > > policy, of course). To me, it looks like you want this changed, which > > I think is a bad idea. > > But then the maintainer has to take full responsibility to maintain the > translations. And several maintainers have said they don't even want to know > about new translations since they can be added without any action on their > part. Exactly again. If translations are available both from the maintainer and from a separate translation archive, it should be up to the user to decide which they want to use. That would allow for all sorts of flexibility - as I said before, you could even have different "translations" in the same language. I can think of at least one way in which this could be useful. Cheers, Nick -- Nick Phillips -- [EMAIL PROTECTED] Someone whom you reject today, will reject you tomorrow.
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Wed, Sep 05, 2001 at 03:22:47PM +0200, Tollef Fog Heen wrote: > * Nick Phillips > > | The translation of any part of a package, be it the text of error messages, > | the text in control, or the text in debconf templates, does not need to > | be part of the package, and hence certainly shouldn't have to be. The > | translations can easily be completely abstracted from the package itself, > | and that relieves the maintainer from having to have anything to do with > them. > > The description is part of the package, can we agree on that one? > What is the difference between a translated description and the > original one, except for which language it is written in? Well, all descriptions are in english by default and there is no real reason to store every description for every package on every machine/archive. > The package is the responsibility of the maintainer, and s/he has the > final words on all aspects of how it should be packaged (subject to > policy, of course). To me, it looks like you want this changed, which > I think is a bad idea. But then the maintainer has to take full responsibility to maintain the translations. And several maintainers have said they don't even want to know about new translations since they can be added without any action on their part. I actually quite like the idea of allowing the farming of parts of a package to other people. And since most people can't read more than a language or two, it seems silly to require them to keep every translation up-to-date. It not like any functionality is being changed, just some text. -- Martijn van Oosterhout http://svana.org/kleptog/ > Magnetism, electricity and motion are like a three-for-two special offer: > if you have two of them, the third one comes free.
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Wed, Sep 05, 2001 at 09:49:09PM +1000, Hamish Moffatt wrote: > Do package descriptions change so regularly that translated descriptions > couldn't be submitted through the bug tracking system and included > in the next upload? That doesn't serve the purpose of hijacking pieces of the maintainer's package away from him, which, as you'll note, is the foundational premise of Michael Bramer's entire proposal. He doesn't want the maintainer involved at all, except to sit by helplessly and get flooded with emails notifying him that his package has been modified yet again. -- G. Branden Robinson|I have a truly elegant proof of the Debian GNU/Linux |above, but it is too long to fit [EMAIL PROTECTED] |into this .signature file. http://people.debian.org/~branden/ | pgpufZruavAvI.pgp Description: PGP signature
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On 05-Sep-01, 07:09 (EDT), Nick Phillips <[EMAIL PROTECTED]> wrote: > If you look at it logically, *everything* that has to do with translations > is quite distinct from the other tasks relating to package maintenance. > > The translation of any part of a package, be it the text of error messages, > the text in control, or the text in debconf templates, does not need to > be part of the package, and hence certainly shouldn't have to be. The > translations can easily be completely abstracted from the package itself, > and that relieves the maintainer from having to have anything to do with them. I disagree with this. Translation of text that is part of the upstream source needs[1] to go to/through the maintainer, as it should be integrated upstream. Steve [1] Okay, it *could* be sent directly upstream, but often the debian maintainer has an established relationship to the upstream author, and may be able to fit them into the package more cleanly.
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
* Nick Phillips | The translation of any part of a package, be it the text of error messages, | the text in control, or the text in debconf templates, does not need to | be part of the package, and hence certainly shouldn't have to be. The | translations can easily be completely abstracted from the package itself, | and that relieves the maintainer from having to have anything to do with them. The description is part of the package, can we agree on that one? What is the difference between a translated description and the original one, except for which language it is written in? The package is the responsibility of the maintainer, and s/he has the final words on all aspects of how it should be packaged (subject to policy, of course). To me, it looks like you want this changed, which I think is a bad idea. -- Tollef Fog Heen You Can't Win
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Wed, Sep 05, 2001 at 09:49:09PM +1000, Hamish Moffatt wrote: > Do package descriptions change so regularly that translated descriptions > couldn't be submitted through the bug tracking system and included > in the next upload? Apparently maintainers regularly fail to do anything with them at all for ages. Besides which there is no real *need* for the maintainers to be required to take action to make translations available. > Most of my packages have never had their description changed from > when I first wrote it. It would be better if we could just include > translated descriptions in the debian/control file. The descriptions are just one of the parts of a package that needs to be translated. It would make more sense to consider the way to deal with *all* the text in the package that needs to be translated. Why put the translations in the control file? Why not just make available (either in the package, or elsewhere, depending on the means by which the package is to be distributed, and the maintainer's knowledge and inclination) the translations for the whole package in one place? Cheers, Nick, who is waiting for someone to tell him he's completely wrong. -- Nick Phillips -- [EMAIL PROTECTED] Tonight's the night: Sleep in a eucalyptus tree.
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Wed, Sep 05, 2001 at 09:49:09PM +1000, Hamish Moffatt wrote: > On Wed, Sep 05, 2001 at 12:11:56PM +0100, Nick Phillips wrote: > > I'd have thought that the current situation re. maintainers putting > > translations into .debs makes it blindingly obvious that requiring them > > to do so in order for a translation to become available is a bad idea. > > Do package descriptions change so regularly that translated descriptions > couldn't be submitted through the bug tracking system and included > in the next upload? > > Most of my packages have never had their description changed from > when I first wrote it. It would be better if we could just include > translated descriptions in the debian/control file. See also the other mail: >50 changes in 10 days in main/sid But if you include the translation only in the debian/control you have - delays (maybe we have a override file and can solve this) - you will have outdated translations (like debconf now) - you must patch dpkg etc. in a wide way We can include the translation in the package. This is not the problem, but please not in the control file. The translation is no new information of the package, it is only a translation. Only a other form of the orignal text. Please read the last proposal, I explain a possibly solution in it. Gruss Grisu -- Michael Bramer - a Debian Linux Developer http://www.debian.org PGP: finger [EMAIL PROTECTED] -- Linux Sysadmin -- Use Debian Linux "We just typed make..." -- (Stephen Lambrigh, Director of Server Product Marketing at Informix about porting their Database to Linux) pgpnEyGGJwokg.pgp Description: PGP signature
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Wed, Sep 05, 2001 at 01:13:35PM +0200, Radovan Garabik wrote: > On Wed, Sep 05, 2001 at 12:00:42PM +0200, Michael Bramer wrote: > > > If we talk about translation, this is not a big problem. You must only > > use gettext all the time. Maybe we can throw away the 'maintainer > > name' problem with this. (You know it: maintainer fields with > > ÖÄÜöüüßåñïééõú... in the name.) > > > > We need only one .po file, like this > > msgid "Werner Mueller <[EMAIL PROTECTED]>" > > megstr "Werner Mülller <[EMAIL PROTECTED]>" > > And the german User see the 'right' Name of this maintainer all the > > time. > > except that I would suggest to do it the other way round, having > the proper full name as original, and individual languages > will transform the name according to their established charset. > (So that all latin 1 and latin 2 languages does not need to translate > the proper form Werner Müller, but latin 2 languages will > ASCIIfy Javier Fernandez-Sanguino Peña into Pena, and koi8-r > languages (russian) will use ASCII only form of both) this is ok. This was not a proposal. it was only a first thought and should show, that gettext can make more (and not only Descriptions...) Gruss Grisu -- Michael Bramer - a Debian Linux Developer http://www.debian.org PGP: finger [EMAIL PROTECTED] -- Linux Sysadmin -- Use Debian Linux "We just typed make..." -- (Stephen Lambrigh, Director of Server Product Marketing at Informix about porting their Database to Linux) pgpDlbQuuhk0H.pgp Description: PGP signature
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
Le Wed, Sep 05, 2001 at 12:20:42PM +0100, Nick Phillips écrivait: > > > It needs to be stored, in /var/lib/dpkg/status, as a single file. This > > > is so [...] > > no, it does not store there. And I can explain it: > > Well, shouldn't it? Wouldn't it make sense to have the translated description > in there rather than the original one? Status is for installed packages, what about packages that are not yet installed ? Adam has an opinion, but while I agree that we may allow people to put translated field in the control file, it's not the way that Debian should use ... for all the reasons repeated over and over. Grisu's initial solution is the best on the different points. Check my summary somewhere else on this list. Cheers, -- Raphaël Hertzog -+- http://strasbourg.linuxfr.org/~raphael/ Le bouche à oreille du Net : http://www.beetell.com Naviguer sans se fatiguer à chercher : http://www.deenoo.com Formation Linux et logiciel libre : http://www.logidee.com
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Wed, Sep 05, 2001 at 12:20:42PM +0100, Nick Phillips wrote: > On Wed, Sep 05, 2001 at 12:00:42PM +0200, Michael Bramer wrote: > > > > It needs to be stored, in /var/lib/dpkg/status, as a single file. This > > > is so > > > that dpkg can make safe updates to it. Trying to sync multiple files is > > > not a > > > simple solution. > > > > no, it does not store there. And I can explain it: > > Well, shouldn't it? Wouldn't it make sense to have the translated description > in there rather than the original one? (I hope I understand it right...) No, don't touch the files in /var/lib/dpkg/*. Don't insert the translation, don't replace the orignal with the translation. We should support not only one language, see should support more languages at the same time with dpkg and with a nice fallback path. And if we don't change the files in /var/lib/dpkg/, we don't need a big patch in dpkg. dpkg is a core element in debian and it must be stable. If we change a lot, we break (maybe) a lot. This is not nice. Gruss Grisu -- Michael Bramer - a Debian Linux Developer http://www.debian.org PGP: finger [EMAIL PROTECTED] -- Linux Sysadmin -- Use Debian Linux Ein Prompt! Um Himmelswillen! Ein Prompt!! HILF pgpp7bt9qrP3Y.pgp Description: PGP signature
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Wed, Sep 05, 2001 at 12:11:56PM +0100, Nick Phillips wrote: > I'd have thought that the current situation re. maintainers putting > translations into .debs makes it blindingly obvious that requiring them > to do so in order for a translation to become available is a bad idea. Do package descriptions change so regularly that translated descriptions couldn't be submitted through the bug tracking system and included in the next upload? Most of my packages have never had their description changed from when I first wrote it. It would be better if we could just include translated descriptions in the debian/control file. Hamish -- Hamish Moffatt VK3SB <[EMAIL PROTECTED]> <[EMAIL PROTECTED]>
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Wed, Sep 05, 2001 at 12:00:42PM +0200, Michael Bramer wrote: > If we talk about translation, this is not a big problem. You must only > use gettext all the time. Maybe we can throw away the 'maintainer > name' problem with this. (You know it: maintainer fields with > ÖÄÜöüüßåñïééõú... in the name.) > > We need only one .po file, like this > msgid "Werner Mueller <[EMAIL PROTECTED]>" > megstr "Werner Mülller <[EMAIL PROTECTED]>" > And the german User see the 'right' Name of this maintainer all the > time. except that I would suggest to do it the other way round, having the proper full name as original, and individual languages will transform the name according to their established charset. (So that all latin 1 and latin 2 languages does not need to translate the proper form Werner Müller, but latin 2 languages will ASCIIfy Javier Fernandez-Sanguino Peña into Pena, and koi8-r languages (russian) will use ASCII only form of both) -- --- | Radovan Garabik http://melkor.dnp.fmph.uniba.sk/~garabik/ | | __..--^^^--..__garabik @ melkor.dnp.fmph.uniba.sk | --- Antivirus alert: file .signature infected by signature virus. Hi! I'm a signature virus! Copy me into your signature file to help me spread!
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Wed, Sep 05, 2001 at 12:00:42PM +0200, Michael Bramer wrote: > > It needs to be stored, in /var/lib/dpkg/status, as a single file. This is > > so > > that dpkg can make safe updates to it. Trying to sync multiple files is > > not a > > simple solution. > > no, it does not store there. And I can explain it: Well, shouldn't it? Wouldn't it make sense to have the translated description in there rather than the original one? -- Nick Phillips -- [EMAIL PROTECTED] Slow day. Practice crawling.
Re: ddts: notification about pt_BR-translation of the hello-debhelper description
On Wed, Sep 05, 2001 at 10:41:53AM +0200, Christian Kurz wrote: > On 01-09-04 Nick Phillips wrote: > > On Tue, Sep 04, 2001 at 09:06:04PM +0200, Michael Bramer wrote: > > I don't expect most maintainers to be able or inclined to keep track of > > a shedload of different translations, and those who are that keen should > > May I ask if you are aware about the ongoing translation of the debconf > templates via the bts? If yes, would you mind explaining what's the > difference between keeping track of thsoe translation/bugreports and > keeping track of the package translation via a simple ddts mail? Yes. Ideally, the maintainer should not have to be involved in those translations either... If you look at it logically, *everything* that has to do with translations is quite distinct from the other tasks relating to package maintenance. The translation of any part of a package, be it the text of error messages, the text in control, or the text in debconf templates, does not need to be part of the package, and hence certainly shouldn't have to be. The translations can easily be completely abstracted from the package itself, and that relieves the maintainer from having to have anything to do with them. It would also be very simple to have another subdirectory in the debian area of the source into which any translations over which the maintainer did wish to keep control could be placed (this would also be useful for sending packages independently of any archive/CD set). The fact that some maintainers want control of some of the translations in their package should not force translators to rely on maintainers, and should not force upon all maintainers the task of managing translations. Translations do not "belong" in the package. It should be possible to include translations in a package, but I don't see that this is a sensible way to do it by default, all the time. Cheers, Nick [hoping I've not missed something that means I'm making a prize tit of myself] -- Nick Phillips -- [EMAIL PROTECTED] You will soon forget this.
