Date: Sun, 14 Apr 2013 13:46:12 +0000 Subject: Add zarb MLs html archives --- .../20111017/13465627/attachment-0001.html | 151 +++++++++++++++++++++ .../attachments/20111017/13465627/attachment.html | 151 +++++++++++++++++++++ .../20111017/a37ab06c/attachment-0001.asc | 7 + .../attachments/20111017/a37ab06c/attachment.asc | 7 + .../20111017/a562ecf5/attachment-0001.asc | 7 + .../attachments/20111017/a562ecf5/attachment.asc | 7 + .../20111017/db68ac44/attachment-0001.asc | 7 + .../attachments/20111017/db68ac44/attachment.asc | 7 + .../20111017/e5e5fec6/attachment-0001.html | 111 +++++++++++++++ .../attachments/20111017/e5e5fec6/attachment.html | 111 +++++++++++++++ .../20111017/eebac041/attachment-0001.html | 146 ++++++++++++++++++++ .../attachments/20111017/eebac041/attachment.html | 146 ++++++++++++++++++++ 12 files changed, 858 insertions(+) create mode 100644 zarb-ml/mageia-dev/attachments/20111017/13465627/attachment-0001.html create mode 100644 zarb-ml/mageia-dev/attachments/20111017/13465627/attachment.html create mode 100644 zarb-ml/mageia-dev/attachments/20111017/a37ab06c/attachment-0001.asc create mode 100644 zarb-ml/mageia-dev/attachments/20111017/a37ab06c/attachment.asc create mode 100644 zarb-ml/mageia-dev/attachments/20111017/a562ecf5/attachment-0001.asc create mode 100644 zarb-ml/mageia-dev/attachments/20111017/a562ecf5/attachment.asc create mode 100644 zarb-ml/mageia-dev/attachments/20111017/db68ac44/attachment-0001.asc create mode 100644 zarb-ml/mageia-dev/attachments/20111017/db68ac44/attachment.asc create mode 100644 zarb-ml/mageia-dev/attachments/20111017/e5e5fec6/attachment-0001.html create mode 100644 zarb-ml/mageia-dev/attachments/20111017/e5e5fec6/attachment.html create mode 100644 zarb-ml/mageia-dev/attachments/20111017/eebac041/attachment-0001.html create mode 100644 zarb-ml/mageia-dev/attachments/20111017/eebac041/attachment.html (limited to 'zarb-ml/mageia-dev/attachments/20111017') diff --git a/zarb-ml/mageia-dev/attachments/20111017/13465627/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20111017/13465627/attachment-0001.html new file mode 100644 index 000000000..8fd428520 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20111017/13465627/attachment-0001.html @@ -0,0 +1,151 @@ +Hi all,
we have libfaac already packaged

http://ftp.blogdrake.net/mageia/mageia1/free/i586/

It's a dependence of cinelerra
+
Cheers

2011/10/17 Joaquin Mandriva <joaquinmandriva@gmail.com>

+This package is in:

ftp://ftp.blogdrake.net/mageia/mageia1/SRPMS/faac-1.28-1bdk.mga1.src.rpm
+
You can find a list with this package and much more in:
ftp://ftp.blogdrake.net/incoming/MGA/joaquin/mageia.txt

Regards.
+

+2011/10/17 Philippe DIDIER <philippedidier@laposte.net>
+ +andre999 a écrit :
+
> Philippe DIDIER a écrit :
+>> Philippe DIDIER a écrit :
+>>
+>>> Joaquin Mandriva a écrit :
+>>>
+>>>> Hello!
+>>>>
+>>>> My name is Joaquin, belonging to http://blogdrake.net
+>>>> <http://blogdrake.net/> team. I am
+>>>> writing to you because I would like to let you know that we have
+>>>> created a repository with a big amount of good programs for Mageia.
+>>>> Our final target is to upload all of them to the official Mageia's
+>>>> repositories.
+>>>>
+>>>> We are currently uploading all these packages to the Mageia's BS step
+>>>> by step, because there are few people of us to do so. Also, also we
+>>>> don't have too much time because we also take care of Blogdrake,
+>>>> Mageia's news and the translations English to Spanish.
+>>>>
+>>>> Meanwhile, you can use and enjoy our repository in this way:
+>>>>
+>>>> urpmi.addmedia --wget --distrib
+>>>> ftp://ftp.blogdrake.net/mageia/mageia1/i586
+>>>>
+>>>> The x86_64 repository is not finished yet, but you still can add it in
+>>>> this way:
+>>>>
+>>>> urpmi.addmedia --wget --distrib
+>>>> ftp://ftp.blogdrake.net/mageia/mageia1/x86_64
+>>>>
+>>>> Cheers!
+>>>>
+>>> Hello
+>>> Thanks to you...
+>>>
+>>>
+>>> Just one thing to correct : your repos addresses are :
+>>> ftp://ftp.blogdrake.net/mageia/mageia1/free/i586/
+>>> ftp://ftp.blogdrake.net/mageia/mageia1/free/x86_64/
+>>>
+>>> nevertheless I could surf through your repos :
+>>> Some of the rpms you propose reply to rpm requests already done or that
+>>> I was going to write (reading my thoughts ?)
+>>>
+>>> :)
+>>>
+>>> First thing I must say : it's a very good idea to upload these packages
+>>> to the BS and join the packagers team instead of providing third party
+>>> repos that will soon create compatibility problems (as in the past for
+>>> Mandrake and Mandriva with Thac's or MIB or others)
+>>>
+>>> The second thing is : before uploading them you will have to be careful
+>>> with the repos policy (core tainted non-free)
+>>> In your own repo, there is a problematic package : faac (and libfaac0
+>>> libfaac-devel) which is both non-free and tainted ...
+>>> After long dicussions on the mailing list a meeting decision was not to
+>>> provide it at the moment (nor the packages built with it...)
+>>> If a non-free-&-tainted repo is created for Mageia2, in the future, it
+>>> will be then allowed ... wait and see !
+>>>
+>>>
+>>>
+>>>
+>>>
+>> I was thinking about a workaround to the problem of "non-free_&_tainted"
+>> rpms in Mageia
+>>
+>> https://bugs.mageia.org/show_bug.cgi?id=2833
+>>
+>> Some multimedia programs can't correctly handle files containing aac
+>> sound (*.aac *.mp4 *.m4a) because faac and faac-devel are not provided.
+>> And that's really missing !!!
+>>
+>>
+>> They can't and won't be backported to Mageia1 official repos...
+>>
+>> Perhaps a new "non-free& tainted" repo will exist for Mageia2
+>>
+>>
+>> Actually for Mageia1 Blogdrake might provide a third repo for this dozen
+>> of srpms (even if the existence of third repo is not riskless)
+>>
+>> Picking their last spec file from Mageia, and modifying the plf or
+>> tainted conditionnal building options to allow building with
+>> faac-devel... wouldn't be too much difficult and wouldn't bring much
+>> compatibility problems
+>>
+>> If the version number is the same as in mageia repos, a "twisted"
+>> distsuffix would allow to "update" to them from core or tainted version
+>> (the same way as "tainted" distsuffix allows to update from a core
+>> release)
+>> and wouldn't prevent to update to a core or tainted new version later if
+>> provided in official updates repo
+>>
+>>
+>> But... there's the :
+>> https://bugs.mageia.org/show_bug.cgi?id=2317
+>> would it add other problems to this ?
+>>
+>> But too there wouldn't exist QA for them
+>>
+>> What do you think (on Mageia side and on Blogdrake side) ?
+>>
+>
+> A personal POV from the Mageia side --
+> It could be a good way to evaluate the need for a Nonfree+Tainted repo,
+> as well as providing a ready source for those interested in such packages.
+>
+> Maybe another approach could be to try to separate nonfree and tainted
+> parts, so that either
+> - nonfree packages could optionally use "tainted" packages if installed, or
+> - "tainted" packages could optionally use nonfree packages if installed,
+> each in their respective current repos.
+> Which won't work if a particular component is necessarily both nonfree
+> and "tainted".
+
That's the problem : we have already tainted packages ... they have been
+built without faac-devel and don't require faac which is both tainted
+and non-free :-(
+If they are built with faac the binaries become non-free (not LGPL) and
+stay tainted ... (they can't be splitted in parts)
+it's true for avidemux, mencoder, handbrake, audiokonverter, and some
+others (the list is in the bug report
+https://bugs.mageia.org/show_bug.cgi?id=2833)
+ it's an aporia !
+I don't want to argue again about the decision for the Mageia's repos !
+only need to find a way to get working binaries for my purpose... and I
+think I'm not alone to have to work with a quasi standard for multimedia
+files on internet.
+plf allowed that for Mandriva ...
+no third repo allows this for Mageia
+If I'm alone, never mind, I know how to build my own (two lines to
+modify in a spec file and => rpmbuild -ba ... that's all folks! )
+If newcomers try Mageia and has to be taught how to build a rpm, they
+better will use debian or fedora or ubuntu or opensuse that have quasi
+official third repos for this problem...
+
+>
+> my 2 cents :-)
+>
+my 2 λεπτες
+
+

+

diff --git a/zarb-ml/mageia-dev/attachments/20111017/13465627/attachment.html b/zarb-ml/mageia-dev/attachments/20111017/13465627/attachment.html new file mode 100644 index 000000000..8fd428520 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20111017/13465627/attachment.html @@ -0,0 +1,151 @@ +Hi all,
we have libfaac already packaged

http://ftp.blogdrake.net/mageia/mageia1/free/i586/

It's a dependence of cinelerra
+
Cheers

2011/10/17 Joaquin Mandriva <joaquinmandriva@gmail.com>

+This package is in:

ftp://ftp.blogdrake.net/mageia/mageia1/SRPMS/faac-1.28-1bdk.mga1.src.rpm
+
You can find a list with this package and much more in:
ftp://ftp.blogdrake.net/incoming/MGA/joaquin/mageia.txt

Regards.
+

+2011/10/17 Philippe DIDIER <philippedidier@laposte.net>
+ +andre999 a écrit :
+
> Philippe DIDIER a écrit :
+>> Philippe DIDIER a écrit :
+>>
+>>> Joaquin Mandriva a écrit :
+>>>
+>>>> Hello!
+>>>>
+>>>> My name is Joaquin, belonging to http://blogdrake.net
+>>>> <http://blogdrake.net/> team. I am
+>>>> writing to you because I would like to let you know that we have
+>>>> created a repository with a big amount of good programs for Mageia.
+>>>> Our final target is to upload all of them to the official Mageia's
+>>>> repositories.
+>>>>
+>>>> We are currently uploading all these packages to the Mageia's BS step
+>>>> by step, because there are few people of us to do so. Also, also we
+>>>> don't have too much time because we also take care of Blogdrake,
+>>>> Mageia's news and the translations English to Spanish.
+>>>>
+>>>> Meanwhile, you can use and enjoy our repository in this way:
+>>>>
+>>>> urpmi.addmedia --wget --distrib
+>>>> ftp://ftp.blogdrake.net/mageia/mageia1/i586
+>>>>
+>>>> The x86_64 repository is not finished yet, but you still can add it in
+>>>> this way:
+>>>>
+>>>> urpmi.addmedia --wget --distrib
+>>>> ftp://ftp.blogdrake.net/mageia/mageia1/x86_64
+>>>>
+>>>> Cheers!
+>>>>
+>>> Hello
+>>> Thanks to you...
+>>>
+>>>
+>>> Just one thing to correct : your repos addresses are :
+>>> ftp://ftp.blogdrake.net/mageia/mageia1/free/i586/
+>>> ftp://ftp.blogdrake.net/mageia/mageia1/free/x86_64/
+>>>
+>>> nevertheless I could surf through your repos :
+>>> Some of the rpms you propose reply to rpm requests already done or that
+>>> I was going to write (reading my thoughts ?)
+>>>
+>>> :)
+>>>
+>>> First thing I must say : it's a very good idea to upload these packages
+>>> to the BS and join the packagers team instead of providing third party
+>>> repos that will soon create compatibility problems (as in the past for
+>>> Mandrake and Mandriva with Thac's or MIB or others)
+>>>
+>>> The second thing is : before uploading them you will have to be careful
+>>> with the repos policy (core tainted non-free)
+>>> In your own repo, there is a problematic package : faac (and libfaac0
+>>> libfaac-devel) which is both non-free and tainted ...
+>>> After long dicussions on the mailing list a meeting decision was not to
+>>> provide it at the moment (nor the packages built with it...)
+>>> If a non-free-&-tainted repo is created for Mageia2, in the future, it
+>>> will be then allowed ... wait and see !
+>>>
+>>>
+>>>
+>>>
+>>>
+>> I was thinking about a workaround to the problem of "non-free_&_tainted"
+>> rpms in Mageia
+>>
+>> https://bugs.mageia.org/show_bug.cgi?id=2833
+>>
+>> Some multimedia programs can't correctly handle files containing aac
+>> sound (*.aac *.mp4 *.m4a) because faac and faac-devel are not provided.
+>> And that's really missing !!!
+>>
+>>
+>> They can't and won't be backported to Mageia1 official repos...
+>>
+>> Perhaps a new "non-free& tainted" repo will exist for Mageia2
+>>
+>>
+>> Actually for Mageia1 Blogdrake might provide a third repo for this dozen
+>> of srpms (even if the existence of third repo is not riskless)
+>>
+>> Picking their last spec file from Mageia, and modifying the plf or
+>> tainted conditionnal building options to allow building with
+>> faac-devel... wouldn't be too much difficult and wouldn't bring much
+>> compatibility problems
+>>
+>> If the version number is the same as in mageia repos, a "twisted"
+>> distsuffix would allow to "update" to them from core or tainted version
+>> (the same way as "tainted" distsuffix allows to update from a core
+>> release)
+>> and wouldn't prevent to update to a core or tainted new version later if
+>> provided in official updates repo
+>>
+>>
+>> But... there's the :
+>> https://bugs.mageia.org/show_bug.cgi?id=2317
+>> would it add other problems to this ?
+>>
+>> But too there wouldn't exist QA for them
+>>
+>> What do you think (on Mageia side and on Blogdrake side) ?
+>>
+>
+> A personal POV from the Mageia side --
+> It could be a good way to evaluate the need for a Nonfree+Tainted repo,
+> as well as providing a ready source for those interested in such packages.
+>
+> Maybe another approach could be to try to separate nonfree and tainted
+> parts, so that either
+> - nonfree packages could optionally use "tainted" packages if installed, or
+> - "tainted" packages could optionally use nonfree packages if installed,
+> each in their respective current repos.
+> Which won't work if a particular component is necessarily both nonfree
+> and "tainted".
+
That's the problem : we have already tainted packages ... they have been
+built without faac-devel and don't require faac which is both tainted
+and non-free :-(
+If they are built with faac the binaries become non-free (not LGPL) and
+stay tainted ... (they can't be splitted in parts)
+it's true for avidemux, mencoder, handbrake, audiokonverter, and some
+others (the list is in the bug report
+https://bugs.mageia.org/show_bug.cgi?id=2833)
+ it's an aporia !
+I don't want to argue again about the decision for the Mageia's repos !
+only need to find a way to get working binaries for my purpose... and I
+think I'm not alone to have to work with a quasi standard for multimedia
+files on internet.
+plf allowed that for Mandriva ...
+no third repo allows this for Mageia
+If I'm alone, never mind, I know how to build my own (two lines to
+modify in a spec file and => rpmbuild -ba ... that's all folks! )
+If newcomers try Mageia and has to be taught how to build a rpm, they
+better will use debian or fedora or ubuntu or opensuse that have quasi
+official third repos for this problem...
+
+>
+> my 2 cents :-)
+>
+my 2 λεπτες
+
+

+

diff --git a/zarb-ml/mageia-dev/attachments/20111017/a37ab06c/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20111017/a37ab06c/attachment-0001.asc new file mode 100644 index 000000000..9589f0382 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20111017/a37ab06c/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.9 (GNU/Linux) + +iD8DBQBOm1cuT1rWTfpocyQRArOnAJ9OBoJWcg/yuqd47lbr8LDtns/M6gCfRvbV +azGRuOyxCmGS5tDG8E9XSKw= +=o8bg +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20111017/a37ab06c/attachment.asc b/zarb-ml/mageia-dev/attachments/20111017/a37ab06c/attachment.asc new file mode 100644 index 000000000..9589f0382 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20111017/a37ab06c/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.9 (GNU/Linux) + +iD8DBQBOm1cuT1rWTfpocyQRArOnAJ9OBoJWcg/yuqd47lbr8LDtns/M6gCfRvbV +azGRuOyxCmGS5tDG8E9XSKw= +=o8bg +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20111017/a562ecf5/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20111017/a562ecf5/attachment-0001.asc new file mode 100644 index 000000000..f61e118f9 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20111017/a562ecf5/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.9 (GNU/Linux) + +iD8DBQBOm59QT1rWTfpocyQRAg0aAJ93kL/QiCl5677pQJeCAGEIiS+tXQCg7Bf5 +DuQ8m3lK1pgobwc4DwAdAno= +=vGwB +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20111017/a562ecf5/attachment.asc b/zarb-ml/mageia-dev/attachments/20111017/a562ecf5/attachment.asc new file mode 100644 index 000000000..f61e118f9 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20111017/a562ecf5/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.9 (GNU/Linux) + +iD8DBQBOm59QT1rWTfpocyQRAg0aAJ93kL/QiCl5677pQJeCAGEIiS+tXQCg7Bf5 +DuQ8m3lK1pgobwc4DwAdAno= +=vGwB +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20111017/db68ac44/attachment-0001.asc b/zarb-ml/mageia-dev/attachments/20111017/db68ac44/attachment-0001.asc new file mode 100644 index 000000000..dd4513864 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20111017/db68ac44/attachment-0001.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.9 (GNU/Linux) + +iD8DBQBOm3iET1rWTfpocyQRAsjnAKDXuPe6Bg8WIc6yUlFWSrQQ6mXfTQCg/j52 +iWYUMy+Niu9YsyNfZMaPAWQ= +=t7o5 +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20111017/db68ac44/attachment.asc b/zarb-ml/mageia-dev/attachments/20111017/db68ac44/attachment.asc new file mode 100644 index 000000000..dd4513864 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20111017/db68ac44/attachment.asc @@ -0,0 +1,7 @@ +-----BEGIN PGP SIGNATURE----- +Version: GnuPG v1.4.9 (GNU/Linux) + +iD8DBQBOm3iET1rWTfpocyQRAsjnAKDXuPe6Bg8WIc6yUlFWSrQQ6mXfTQCg/j52 +iWYUMy+Niu9YsyNfZMaPAWQ= +=t7o5 +-----END PGP SIGNATURE----- diff --git a/zarb-ml/mageia-dev/attachments/20111017/e5e5fec6/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20111017/e5e5fec6/attachment-0001.html new file mode 100644 index 000000000..bf951b511 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20111017/e5e5fec6/attachment-0001.html @@ -0,0 +1,111 @@ + + + + + + + On 16/10/2011 22:33, Thomas Spuhler wrote: +

On Sunday, October 16, 2011 04:05:52 am Giuseppe Ghibò wrote:
+

On 26/09/2011 17:34, Anssi Hannula wrote:
+

On 26.09.2011 15:47, nicolas vigier wrote:
+

On Sat, 24 Sep 2011, Thomas Spuhler wrote:
+

But are you sure about texlive providing it?
+

+I don't know. It looks like it's not in the texlive package.
+

+My impression (from a few years back I think) is that standalone
+texi2html is the texlive-era replacement for tetex-texi2html.
+

+It's not like this. The misalignment in having multiple versions comes
+from having different source of packages. tetex had it's own texi2html
+(so I guess texlive), which is certified and well QA and integrated with
+that tetex version, so it provides "texi2html". At a certain point newer
+versions of texi2html were placed in contrib because they were newer
+(there were also other packages in this situation, xdvi, prosper, etc.)
+and because of not touching the main tetex package. To handle this kind
+of misalignment a good way to proceed would be to go in the main package
+providing it (i.e. tetex/texlive) and try to merge the newer texi2html
+with the new one, then redoing the tests. This often doesn't happen
+because it takes a lot of amount of time, and require to handle with the
+main and bigger package (texlive/tetex), and people often don't do this
+if they are doing "snack packaging".
+
+The other way, which is to transform everything as "pluggable" (e.g.
+split packages at source, so for instance not having tetex providing
+texi2html) IMHO doesn't provide the same amount of certification,
+because the packager (packager not necessarely means the maintainer)
+just upgrade the version number, without taking care of re-testing, and
+in case he doesn't know in deep about that package what he does as side
+effect is to give away the upstream tetex/texlive certification
+(certification that the included, so older, texi2html package works well
+and has no flaws with the rest of the tetex/texlive distro) in favour of
+a newer version (hoping that if something goes wrong or of some bug some
+end-user would file a bug on bugzilla...).
+
+Bye.
+G.
+

Thanks for the explanation. 
+It seems you are pretty versed in texlive. Would you mind to look as why 
+muscore doesn't build anymore with the current texlive:
+Font metrics written on mscore1-20.tfm.
+Output written on mscore1-20.600gf (18 characters, 7172 bytes).
+Transcript written on mscore1-20.log.
+This is MetaPost, version 1.504 (kpathsea version 6.0.1)
+(../mf2pt1.mp (/usr/share/texmf-dist/metapost/base/mfplain.mp
+Preloading the plain base, version 0.99: preliminaries,
+ basic constants and mathematical macros,
+ macros for converting units,
+ macros and tables for various modes of operation,
+ macros for drawing and filling,
+ macros for proof labels and rules,
+ macros for character and font administration,
+and a few last-minute items.))
+Transcript written on mf2pt1.log.
+Invoking "mpost -mem=mf2pt1 -progname=mpost '\mode:=localfont; mag:=100; 
+bpppix 0.02; input feta20.mf'"...
+
+Sorry, I can't find the 'mf2pt1' preload file; will try 'plain'.This is 
+MetaPost, version 1.504 (kpathsea version 6.0.1)
+(plain.mp
+
+It lloks as if mf2pt1 is missing, The script is available on it's own, put old 
+texlive and tetex didn't show this problem. 
+
+

+ I've not an installation with the package you are talking about + handy to check myself, but you may try to add the following line to + the file `kpsewhich fmtutil.cnf` (backtick included):
+
+ mpost mf2pt1 - + -translate-file=cp227.tcx mf2pt1.mp
+
+ (of course the file mf2pt1.mp should be provided somewhere [it's in + CTAN:tex-archive/support/mf2pt1]), + and then recreate the missed file with: fmtutil --missing (or + --all).
+
+ Bye
+ Giuseppe.
+
+ + diff --git a/zarb-ml/mageia-dev/attachments/20111017/e5e5fec6/attachment.html b/zarb-ml/mageia-dev/attachments/20111017/e5e5fec6/attachment.html new file mode 100644 index 000000000..bf951b511 --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20111017/e5e5fec6/attachment.html @@ -0,0 +1,111 @@ + + + + + + + On 16/10/2011 22:33, Thomas Spuhler wrote: +

On Sunday, October 16, 2011 04:05:52 am Giuseppe Ghibò wrote:
+

On 26/09/2011 17:34, Anssi Hannula wrote:
+

On 26.09.2011 15:47, nicolas vigier wrote:
+

On Sat, 24 Sep 2011, Thomas Spuhler wrote:
+

But are you sure about texlive providing it?
+

+I don't know. It looks like it's not in the texlive package.
+

+My impression (from a few years back I think) is that standalone
+texi2html is the texlive-era replacement for tetex-texi2html.
+

+It's not like this. The misalignment in having multiple versions comes
+from having different source of packages. tetex had it's own texi2html
+(so I guess texlive), which is certified and well QA and integrated with
+that tetex version, so it provides "texi2html". At a certain point newer
+versions of texi2html were placed in contrib because they were newer
+(there were also other packages in this situation, xdvi, prosper, etc.)
+and because of not touching the main tetex package. To handle this kind
+of misalignment a good way to proceed would be to go in the main package
+providing it (i.e. tetex/texlive) and try to merge the newer texi2html
+with the new one, then redoing the tests. This often doesn't happen
+because it takes a lot of amount of time, and require to handle with the
+main and bigger package (texlive/tetex), and people often don't do this
+if they are doing "snack packaging".
+
+The other way, which is to transform everything as "pluggable" (e.g.
+split packages at source, so for instance not having tetex providing
+texi2html) IMHO doesn't provide the same amount of certification,
+because the packager (packager not necessarely means the maintainer)
+just upgrade the version number, without taking care of re-testing, and
+in case he doesn't know in deep about that package what he does as side
+effect is to give away the upstream tetex/texlive certification
+(certification that the included, so older, texi2html package works well
+and has no flaws with the rest of the tetex/texlive distro) in favour of
+a newer version (hoping that if something goes wrong or of some bug some
+end-user would file a bug on bugzilla...).
+
+Bye.
+G.
+

Thanks for the explanation. 
+It seems you are pretty versed in texlive. Would you mind to look as why 
+muscore doesn't build anymore with the current texlive:
+Font metrics written on mscore1-20.tfm.
+Output written on mscore1-20.600gf (18 characters, 7172 bytes).
+Transcript written on mscore1-20.log.
+This is MetaPost, version 1.504 (kpathsea version 6.0.1)
+(../mf2pt1.mp (/usr/share/texmf-dist/metapost/base/mfplain.mp
+Preloading the plain base, version 0.99: preliminaries,
+ basic constants and mathematical macros,
+ macros for converting units,
+ macros and tables for various modes of operation,
+ macros for drawing and filling,
+ macros for proof labels and rules,
+ macros for character and font administration,
+and a few last-minute items.))
+Transcript written on mf2pt1.log.
+Invoking "mpost -mem=mf2pt1 -progname=mpost '\mode:=localfont; mag:=100; 
+bpppix 0.02; input feta20.mf'"...
+
+Sorry, I can't find the 'mf2pt1' preload file; will try 'plain'.This is 
+MetaPost, version 1.504 (kpathsea version 6.0.1)
+(plain.mp
+
+It lloks as if mf2pt1 is missing, The script is available on it's own, put old 
+texlive and tetex didn't show this problem. 
+
+

+ I've not an installation with the package you are talking about + handy to check myself, but you may try to add the following line to + the file `kpsewhich fmtutil.cnf` (backtick included):
+
+ mpost mf2pt1 - + -translate-file=cp227.tcx mf2pt1.mp
+
+ (of course the file mf2pt1.mp should be provided somewhere [it's in + CTAN:tex-archive/support/mf2pt1]), + and then recreate the missed file with: fmtutil --missing (or + --all).
+
+ Bye
+ Giuseppe.
+
+ + diff --git a/zarb-ml/mageia-dev/attachments/20111017/eebac041/attachment-0001.html b/zarb-ml/mageia-dev/attachments/20111017/eebac041/attachment-0001.html new file mode 100644 index 000000000..0a57a150a --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20111017/eebac041/attachment-0001.html @@ -0,0 +1,146 @@ +This package is in:

ftp://ftp.blogdrake.net/mageia/mageia1/SRPMS/faac-1.28-1bdk.mga1.src.rpm
+
You can find a list with this package and much more in:
ftp://ftp.blogdrake.net/incoming/MGA/joaquin/mageia.txt

Regards.

+2011/10/17 Philippe DIDIER <philippedidier@laposte.net>

+andre999 a écrit :
+
> Philippe DIDIER a écrit :
+>> Philippe DIDIER a écrit :
+>>
+>>> Joaquin Mandriva a écrit :
+>>>
+>>>> Hello!
+>>>>
+>>>> My name is Joaquin, belonging to http://blogdrake.net
+>>>> <http://blogdrake.net/> team. I am
+>>>> writing to you because I would like to let you know that we have
+>>>> created a repository with a big amount of good programs for Mageia.
+>>>> Our final target is to upload all of them to the official Mageia's
+>>>> repositories.
+>>>>
+>>>> We are currently uploading all these packages to the Mageia's BS step
+>>>> by step, because there are few people of us to do so. Also, also we
+>>>> don't have too much time because we also take care of Blogdrake,
+>>>> Mageia's news and the translations English to Spanish.
+>>>>
+>>>> Meanwhile, you can use and enjoy our repository in this way:
+>>>>
+>>>> urpmi.addmedia --wget --distrib
+>>>> ftp://ftp.blogdrake.net/mageia/mageia1/i586
+>>>>
+>>>> The x86_64 repository is not finished yet, but you still can add it in
+>>>> this way:
+>>>>
+>>>> urpmi.addmedia --wget --distrib
+>>>> ftp://ftp.blogdrake.net/mageia/mageia1/x86_64
+>>>>
+>>>> Cheers!
+>>>>
+>>> Hello
+>>> Thanks to you...
+>>>
+>>>
+>>> Just one thing to correct : your repos addresses are :
+>>> ftp://ftp.blogdrake.net/mageia/mageia1/free/i586/
+>>> ftp://ftp.blogdrake.net/mageia/mageia1/free/x86_64/
+>>>
+>>> nevertheless I could surf through your repos :
+>>> Some of the rpms you propose reply to rpm requests already done or that
+>>> I was going to write (reading my thoughts ?)
+>>>
+>>> :)
+>>>
+>>> First thing I must say : it's a very good idea to upload these packages
+>>> to the BS and join the packagers team instead of providing third party
+>>> repos that will soon create compatibility problems (as in the past for
+>>> Mandrake and Mandriva with Thac's or MIB or others)
+>>>
+>>> The second thing is : before uploading them you will have to be careful
+>>> with the repos policy (core tainted non-free)
+>>> In your own repo, there is a problematic package : faac (and libfaac0
+>>> libfaac-devel) which is both non-free and tainted ...
+>>> After long dicussions on the mailing list a meeting decision was not to
+>>> provide it at the moment (nor the packages built with it...)
+>>> If a non-free-&-tainted repo is created for Mageia2, in the future, it
+>>> will be then allowed ... wait and see !
+>>>
+>>>
+>>>
+>>>
+>>>
+>> I was thinking about a workaround to the problem of "non-free_&_tainted"
+>> rpms in Mageia
+>>
+>> https://bugs.mageia.org/show_bug.cgi?id=2833
+>>
+>> Some multimedia programs can't correctly handle files containing aac
+>> sound (*.aac *.mp4 *.m4a) because faac and faac-devel are not provided.
+>> And that's really missing !!!
+>>
+>>
+>> They can't and won't be backported to Mageia1 official repos...
+>>
+>> Perhaps a new "non-free& tainted" repo will exist for Mageia2
+>>
+>>
+>> Actually for Mageia1 Blogdrake might provide a third repo for this dozen
+>> of srpms (even if the existence of third repo is not riskless)
+>>
+>> Picking their last spec file from Mageia, and modifying the plf or
+>> tainted conditionnal building options to allow building with
+>> faac-devel... wouldn't be too much difficult and wouldn't bring much
+>> compatibility problems
+>>
+>> If the version number is the same as in mageia repos, a "twisted"
+>> distsuffix would allow to "update" to them from core or tainted version
+>> (the same way as "tainted" distsuffix allows to update from a core
+>> release)
+>> and wouldn't prevent to update to a core or tainted new version later if
+>> provided in official updates repo
+>>
+>>
+>> But... there's the :
+>> https://bugs.mageia.org/show_bug.cgi?id=2317
+>> would it add other problems to this ?
+>>
+>> But too there wouldn't exist QA for them
+>>
+>> What do you think (on Mageia side and on Blogdrake side) ?
+>>
+>
+> A personal POV from the Mageia side --
+> It could be a good way to evaluate the need for a Nonfree+Tainted repo,
+> as well as providing a ready source for those interested in such packages.
+>
+> Maybe another approach could be to try to separate nonfree and tainted
+> parts, so that either
+> - nonfree packages could optionally use "tainted" packages if installed, or
+> - "tainted" packages could optionally use nonfree packages if installed,
+> each in their respective current repos.
+> Which won't work if a particular component is necessarily both nonfree
+> and "tainted".
+
That's the problem : we have already tainted packages ... they have been
+built without faac-devel and don't require faac which is both tainted
+and non-free :-(
+If they are built with faac the binaries become non-free (not LGPL) and
+stay tainted ... (they can't be splitted in parts)
+it's true for avidemux, mencoder, handbrake, audiokonverter, and some
+others (the list is in the bug report
+https://bugs.mageia.org/show_bug.cgi?id=2833)
+ it's an aporia !
+I don't want to argue again about the decision for the Mageia's repos !
+only need to find a way to get working binaries for my purpose... and I
+think I'm not alone to have to work with a quasi standard for multimedia
+files on internet.
+plf allowed that for Mandriva ...
+no third repo allows this for Mageia
+If I'm alone, never mind, I know how to build my own (two lines to
+modify in a spec file and => rpmbuild -ba ... that's all folks! )
+If newcomers try Mageia and has to be taught how to build a rpm, they
+better will use debian or fedora or ubuntu or opensuse that have quasi
+official third repos for this problem...
+
+>
+> my 2 cents :-)
+>
+my 2 λεπτες
+
+

diff --git a/zarb-ml/mageia-dev/attachments/20111017/eebac041/attachment.html b/zarb-ml/mageia-dev/attachments/20111017/eebac041/attachment.html new file mode 100644 index 000000000..0a57a150a --- /dev/null +++ b/zarb-ml/mageia-dev/attachments/20111017/eebac041/attachment.html @@ -0,0 +1,146 @@ +This package is in:

ftp://ftp.blogdrake.net/mageia/mageia1/SRPMS/faac-1.28-1bdk.mga1.src.rpm
+
You can find a list with this package and much more in:
ftp://ftp.blogdrake.net/incoming/MGA/joaquin/mageia.txt

Regards.

+2011/10/17 Philippe DIDIER <philippedidier@laposte.net>

+andre999 a écrit :
+
> Philippe DIDIER a écrit :
+>> Philippe DIDIER a écrit :
+>>
+>>> Joaquin Mandriva a écrit :
+>>>
+>>>> Hello!
+>>>>
+>>>> My name is Joaquin, belonging to http://blogdrake.net
+>>>> <http://blogdrake.net/> team. I am
+>>>> writing to you because I would like to let you know that we have
+>>>> created a repository with a big amount of good programs for Mageia.
+>>>> Our final target is to upload all of them to the official Mageia's
+>>>> repositories.
+>>>>
+>>>> We are currently uploading all these packages to the Mageia's BS step
+>>>> by step, because there are few people of us to do so. Also, also we
+>>>> don't have too much time because we also take care of Blogdrake,
+>>>> Mageia's news and the translations English to Spanish.
+>>>>
+>>>> Meanwhile, you can use and enjoy our repository in this way:
+>>>>
+>>>> urpmi.addmedia --wget --distrib
+>>>> ftp://ftp.blogdrake.net/mageia/mageia1/i586
+>>>>
+>>>> The x86_64 repository is not finished yet, but you still can add it in
+>>>> this way:
+>>>>
+>>>> urpmi.addmedia --wget --distrib
+>>>> ftp://ftp.blogdrake.net/mageia/mageia1/x86_64
+>>>>
+>>>> Cheers!
+>>>>
+>>> Hello
+>>> Thanks to you...
+>>>
+>>>
+>>> Just one thing to correct : your repos addresses are :
+>>> ftp://ftp.blogdrake.net/mageia/mageia1/free/i586/
+>>> ftp://ftp.blogdrake.net/mageia/mageia1/free/x86_64/
+>>>
+>>> nevertheless I could surf through your repos :
+>>> Some of the rpms you propose reply to rpm requests already done or that
+>>> I was going to write (reading my thoughts ?)
+>>>
+>>> :)
+>>>
+>>> First thing I must say : it's a very good idea to upload these packages
+>>> to the BS and join the packagers team instead of providing third party
+>>> repos that will soon create compatibility problems (as in the past for
+>>> Mandrake and Mandriva with Thac's or MIB or others)
+>>>
+>>> The second thing is : before uploading them you will have to be careful
+>>> with the repos policy (core tainted non-free)
+>>> In your own repo, there is a problematic package : faac (and libfaac0
+>>> libfaac-devel) which is both non-free and tainted ...
+>>> After long dicussions on the mailing list a meeting decision was not to
+>>> provide it at the moment (nor the packages built with it...)
+>>> If a non-free-&-tainted repo is created for Mageia2, in the future, it
+>>> will be then allowed ... wait and see !
+>>>
+>>>
+>>>
+>>>
+>>>
+>> I was thinking about a workaround to the problem of "non-free_&_tainted"
+>> rpms in Mageia
+>>
+>> https://bugs.mageia.org/show_bug.cgi?id=2833
+>>
+>> Some multimedia programs can't correctly handle files containing aac
+>> sound (*.aac *.mp4 *.m4a) because faac and faac-devel are not provided.
+>> And that's really missing !!!
+>>
+>>
+>> They can't and won't be backported to Mageia1 official repos...
+>>
+>> Perhaps a new "non-free& tainted" repo will exist for Mageia2
+>>
+>>
+>> Actually for Mageia1 Blogdrake might provide a third repo for this dozen
+>> of srpms (even if the existence of third repo is not riskless)
+>>
+>> Picking their last spec file from Mageia, and modifying the plf or
+>> tainted conditionnal building options to allow building with
+>> faac-devel... wouldn't be too much difficult and wouldn't bring much
+>> compatibility problems
+>>
+>> If the version number is the same as in mageia repos, a "twisted"
+>> distsuffix would allow to "update" to them from core or tainted version
+>> (the same way as "tainted" distsuffix allows to update from a core
+>> release)
+>> and wouldn't prevent to update to a core or tainted new version later if
+>> provided in official updates repo
+>>
+>>
+>> But... there's the :
+>> https://bugs.mageia.org/show_bug.cgi?id=2317
+>> would it add other problems to this ?
+>>
+>> But too there wouldn't exist QA for them
+>>
+>> What do you think (on Mageia side and on Blogdrake side) ?
+>>
+>
+> A personal POV from the Mageia side --
+> It could be a good way to evaluate the need for a Nonfree+Tainted repo,
+> as well as providing a ready source for those interested in such packages.
+>
+> Maybe another approach could be to try to separate nonfree and tainted
+> parts, so that either
+> - nonfree packages could optionally use "tainted" packages if installed, or
+> - "tainted" packages could optionally use nonfree packages if installed,
+> each in their respective current repos.
+> Which won't work if a particular component is necessarily both nonfree
+> and "tainted".
+
That's the problem : we have already tainted packages ... they have been
+built without faac-devel and don't require faac which is both tainted
+and non-free :-(
+If they are built with faac the binaries become non-free (not LGPL) and
+stay tainted ... (they can't be splitted in parts)
+it's true for avidemux, mencoder, handbrake, audiokonverter, and some
+others (the list is in the bug report
+https://bugs.mageia.org/show_bug.cgi?id=2833)
+ it's an aporia !
+I don't want to argue again about the decision for the Mageia's repos !
+only need to find a way to get working binaries for my purpose... and I
+think I'm not alone to have to work with a quasi standard for multimedia
+files on internet.
+plf allowed that for Mandriva ...
+no third repo allows this for Mageia
+If I'm alone, never mind, I know how to build my own (two lines to
+modify in a spec file and => rpmbuild -ba ... that's all folks! )
+If newcomers try Mageia and has to be taught how to build a rpm, they
+better will use debian or fedora or ubuntu or opensuse that have quasi
+official third repos for this problem...
+
+>
+> my 2 cents :-)
+>
+my 2 λεπτες
+
+

-- cgit v1.2.1