[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: pending LilyPond removal from debian release ?

From: Jan Nieuwenhuizen
Subject: Re: pending LilyPond removal from debian release ?
Date: Mon, 21 Jun 2004 22:10:32 +0200
User-agent: Gnus/5.1003 (Gnus v5.10.3) Emacs/21.3 (gnu/linux)

Anthony Fok writes:

> Oops, I didn't see that, but that is sure alarming...

That is sure alarming... 

> Actually, I already uploaded LilyPond 2.2.2-2 last Friday.  Sorry, life
> had been very hectic over the last few months, and it took me about two or
> three days to catch up with the latest happenings with LilyPond and
> finally got it updated the way it is now...  Sorry for leaving LilyPond
> not updated for so long.

Ok.  Thanks for your swift response.

> lilypond (2.2.2-2) unstable; urgency=low
>   * New upstream release.  (Closes: Bug#242861)
>     - Thanks to Pedro Kroeger for providing interim sid packages while
>       I was away for an extended period of time.
>   * Copied some ideas from Ferenc Wagner's LilyPond for woody (Thanks!):
>      - Split out shared data to lilypond-data package.  (Closes: Bug#233406)
>      - Make lilypond-data conflict with earlier lilypond versions.
>      - debian/control: Relaxed autotrace Build-Depends (>= 0.29).
>      - debian/control: Added imagemagick Build-Depends (>=
>   * Added more details to lilypond package description.  (Closes: Bug#245370)

What about the removal report and the gs bug, I assume that this

>   * gs-gpl 8.01 (and gs-afpl 8.14) dies when building LilyPond docs.
>     (Known -sDEVICE=bbox bug in gs 8.01 and newer, see gs-gpl Bug#250290.)
>     Added Build-Conflict-Indep: gs-gpl (>= 8.01) | gs-afpl (Closes: 
> Bug#250622)

takes care of that?

> Since I splitted the package similar to what Ferenc did, it requires
> manual confirmation by Debian's admin, so hopefully you'll see this new
> version on before the end of the week.

Ok, I'll watch for that.

> if possible, please remove these files from the upstream source
> tree:
>       debian/lilypond1.7*.dirs
>       debian/lilypond.dirs
>       debian/postinst
>       debian/prerm
>       debian/postrm

Done.  Will debian users be able to build the package without these
files, or will you send a patch?  [I assume so, just tried 2.2.3 CVS
with the files removed but got another silly error

mv debian/lilypond/usr/share/lilypond/2.2.3/dvips/ \
mv: cannot move `debian/lilypond/usr/share/lilypond/2.2.3/dvips/' 
to `debian/lilypond/etc/texmf/dvips/': Unknown file or directory
make: *** [binary-arch] Error 1
debuild: fatal error at line 763:

but I am assuming this is already fixed somewhere so I'm leaving it for now]

> Many thanks!  :-)

Thank you!

Jan Nieuwenhuizen <address@hidden> | GNU LilyPond - The music typesetter       |

reply via email to

[Prev in Thread] Current Thread [Next in Thread]