|
View:
New views
9 Messages
—
Rating Filter:
Alert me
|
|
|
kullervo and tipaHi,
one of my packages failed to build on kullervo: http://buildd.debian-ports.org/fetch.php?pkg=moon-buggy&arch=m68k&ver=1.0.51-6&stamp=1248131390&file=log&as=raw The error is here: Setting up tipa (1.3-14) ... Running mktexlsr. This may take some time... done. dpkg-trigger: dpkg-trigger must be called from a maintainer script (or with a --by-package option) dpkg: error processing tipa (--configure): subprocess post-installation script returned error exit status 2 I am not sure why tipa is installed, it seems to be only recommended and on my amd64/sid chroot it was not installed. Does the m68k buildd install recommended packages by default? In any case, this looks like a tipa bug to me. Christian -- To UNSUBSCRIBE, email to debian-68k-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: kullervo and tipaHi Christian,
> Hi, > one of my packages failed to build on kullervo: > http://buildd.debian-ports.org/fetch.php?pkg=moon-buggy&arch=m68k&ver=1.0.51-6&stamp=1248131390&file=log&as=raw > > The error is here: > > Setting up tipa (1.3-14) ... > Running mktexlsr. This may take some time... done. > dpkg-trigger: dpkg-trigger must be called from a maintainer script (or with a --by-package option) > dpkg: error processing tipa (--configure): > subprocess post-installation script returned error exit status 2 > > I am not sure why tipa is installed, it seems to be only recommended and on > my amd64/sid chroot it was not installed. Does the m68k buildd install > recommended packages by default? In any case, this looks like a tipa bug to No, they should not be installed by default. I'll look into removing tipa. Michael -- To UNSUBSCRIBE, email to debian-68k-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: kullervo and tipaHi,
> Setting up tipa (1.3-14) ... > Running mktexlsr. This may take some time... done. > dpkg-trigger: dpkg-trigger must be called from a maintainer script (or with a --by-package option) > dpkg: error processing tipa (--configure): > subprocess post-installation script returned error exit status 2 > > I am not sure why tipa is installed, it seems to be only recommended and on > my amd64/sid chroot it was not installed. Does the m68k buildd install > recommended packages by default? In any case, this looks like a tipa bug to > me. tipa does some trickery with tex update scripts and the comments indicate they tried to avoid running dpkg-trigger. Maybe a m68k tex version problem. Michael -- To UNSUBSCRIBE, email to debian-68k-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: kullervo and tipaHi All,
> > Setting up tipa (1.3-14) ... > > Running mktexlsr. This may take some time... done. > > dpkg-trigger: dpkg-trigger must be called from a maintainer script (or with a --by-package option) > > dpkg: error processing tipa (--configure): > > subprocess post-installation script returned error exit status 2 > > > > I am not sure why tipa is installed, it seems to be only recommended and on > > my amd64/sid chroot it was not installed. Does the m68k buildd install > > recommended packages by default? In any case, this looks like a tipa bug to > > me. > > tipa does some trickery with tex update scripts and the comments indicate they > tried to avoid running dpkg-trigger. Maybe a m68k tex version problem. I had the same problem trying to dist-upgrade the unstable chroot on kullervo, this time it was texlive-base that complained. x11-common didn't install because dpkg doesn't support 'Breaks'. Running dpkg --configure --pending inside the chroot configured texlive fine, so it's the host dpkg version that is insufficient. Both crest and kullervo are running dpkg 1.13.25 in the host filesystem. Any known caveats against upgrading dpkg on etch-m68k to the testing version? Michael -- To UNSUBSCRIBE, email to debian-68k-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: kullervo and tipaOn Sat, Aug 01, 2009 at 02:35:08AM +0200, Michael Schmitz wrote:
> > tipa does some trickery with tex update scripts and the comments indicate they > > tried to avoid running dpkg-trigger. Maybe a m68k tex version problem. > > I had the same problem trying to dist-upgrade the unstable chroot on kullervo, > this time it was texlive-base that complained. x11-common didn't install because > dpkg doesn't support 'Breaks'. Running dpkg --configure --pending inside the > chroot configured texlive fine, so it's the host dpkg version that is > insufficient. > > Both crest and kullervo are running dpkg 1.13.25 in the host filesystem. Any > known caveats against upgrading dpkg on etch-m68k to the testing version? I put the minimal set of packages together at [0]. There's an email on this list about it in April. It works for me. [0] deb http://ftp.debian-ports.org/~smarenka/lenny-buildd ./ Peace, Stephen -- Stephen R. Marenka If life's not fun, you're not doing it right! <stephen@...> -- To UNSUBSCRIBE, email to debian-68k-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: kullervo and tipaHi Stephen,
> > Both crest and kullervo are running dpkg 1.13.25 in the host filesystem. Any > > known caveats against upgrading dpkg on etch-m68k to the testing version? > > I put the minimal set of packages together at [0]. There's an email on > this list about it in April. It works for me. > > [0] deb http://ftp.debian-ports.org/~smarenka/lenny-buildd ./ Thanks - I do recall the initial discussion regarding the future of debian-m68k, but have apparently missed the message on the minimal package set. Upgrading kullervo now ... (I had to update tzdata before it would have a chance tp work). Michael -- To UNSUBSCRIBE, email to debian-68k-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: kullervo and tipaHi All,
> Upgrading kullervo now ... (I had to update tzdata before it would have a chance > tp work). crest and kullervo are updated - kullervo managed to lose build-essential in the chroot though. My bad ... I'll try to fix from the snapshots - failing that. I will mirror the crest chroot over to kullervo. May take a while though. I have given back the backlog of failed packages that had been listed as building on kullervo and crest, hoping that some will be buildable now. Michael -- To UNSUBSCRIBE, email to debian-68k-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: kullervo and tipaOn Sun, Aug 09, 2009 at 07:49:09AM +0200, Michael Schmitz wrote:
> Hi All, > > > Upgrading kullervo now ... (I had to update tzdata before it would have a chance > > tp work). > > crest and kullervo are updated - kullervo managed to lose build-essential in the > chroot though. My bad ... > > I'll try to fix from the snapshots - failing that. I will mirror the crest > chroot over to kullervo. May take a while though. I had to do that recently on zlin2. I thought I documented it and sent it to the list, but I don't have a reference. I did use the snapshots [0]. It didn't take long as I recall. [0] http://ftp.debian-ports.org/debian-snapshot/ Peace, Stephen -- Stephen R. Marenka If life's not fun, you're not doing it right! <stephen@...> -- To UNSUBSCRIBE, email to debian-68k-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
|
|
Re: kullervo and tipaHi,
> > crest and kullervo are updated - kullervo managed to lose build-essential in the > > chroot though. My bad ... > > > > I'll try to fix from the snapshots - failing that. I will mirror the crest > > chroot over to kullervo. May take a while though. > > I had to do that recently on zlin2. I thought I documented it and sent > it to the list, but I don't have a reference. I did use the snapshots > [0]. It didn't take long as I recall. Your mail on the libgcc2 thread mentioned snapshots, that's where I got that idea :-) If it doesn take long, that's what I'll do. Cheers, Michael -- To UNSUBSCRIBE, email to debian-68k-REQUEST@... with a subject of "unsubscribe". Trouble? Contact listmaster@... |
| Free embeddable forum powered by Nabble | Forum Help |