Bug#372560: cdbs bug, I think
Hi, gandalf is failing to build with missing Makefile, but it's most probably because ./configure isn't invoked. Why is cdbs not calling ./configure anymore? regards, junichi -- [EMAIL PROTECTED],netfort.gr.jp} Debian Project -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#372766: thai-system is not installable in sid as it depends on unavailable nonlock
Package: thai-system Severity: serious Version: 3 Hi thai-system is uninstallable in sid as there is no nonlock in unstable (anymore). Cheers Luk -- Luk Claes - http://people.debian.org/~luk - GPG key 1024D/9B7C328D Fingerprint: D5AF 25FB 316B 53BB 08E7 F999 E544 DE07 9B7C 328D signature.asc Description: OpenPGP digital signature
Bug#372560: It's not a cdbs bug
Hi, After some investigations it seems, it is *not* a cdbs bug but a file provided by the tarball (the config.status one). If this file is removed from the tarball, gandalf build well. I can prepare a QA upload (since it is orphaned) but i don't know what is the best solution, removing the file during initial clean or removing this file and upload a new tarball without this file. Cheers. -- It is a wise father that knows his own child. -- William Shakespeare, "The Merchant of Venice" pgplDZEnksfv7.pgp Description: PGP signature
Bug#372560: It's not a cdbs bug
On Sun, Jun 11, 2006, Julien Louis wrote: > After some investigations it seems, it is *not* a cdbs bug but a file provided > by the tarball (the config.status one). If this file is removed from the > tarball, gandalf build well. I can prepare a QA upload (since it is orphaned) > but i don't know what is the best solution, removing the file during initial > clean or removing this file and upload a new tarball without this file. There is an RM: pending bug on gandalf. Is there a need to fix this bug? -- adn Mohammed Adnène Trojette
Bug#372780: OpenBSD can't boot via yaboot on powerpc (no dualboot possible)
Package: yaboot
Version: 1.3.13-5
Severity: normal
OpenBSD can't boot via yaboot on powerpc. Dualboot doesn't work.
This bug is common to all versions of debian (stable,
testing, unstable).
boot-procedure in general
-
After poweron the bios of a new world powerpc looks
for a nvram-variable, in order to examine, which
programm is to boot at first place.
The powerpc-bios is called "open firmware". "New world"
is called the architecture of the newer powerpc's.
If debian is installed, the open firmware finds the
complete path to the debian-bootlooder and boots.
The debian-bootloader is called "ofboot.b". Notice
the last two chars ".b".
This programm is written in forth, because open
firmware is able to interpret it.
The debian-bootloader ofboot.b has to be found in
a special partition, which is called "new world
boot partition".
ofboot.b displays a small menu. The user has to
strike a single key, in order to boot an os.
The key "b" forces ofboot to load & start the openbsd
bootloader, which is called "ofwboot". Notice the
char "w".
ofwboot is the original openbsd-bootloader.
the bug
---
ofboot.b tranfers to ofwboot the complete path to the
openbsd-kernel. The user configured this path in /etc/yaboot.conf,
something like bsd=/dev/...
yaboot.conf is the "alias" of lilo.conf on powerpc.
For example:
If your openbsd-installation resides on partition 7,
ofboot.b transfers "hd0:7,/bsd" or something more
cryptical to ofwboot. (ofboot.b uses a notation,
which open firmware understands. Sometimes this
notation looks very cryptical.)
Transferring this parameter to ofwboot is a bug,
because ofwboot doesn't want to know a complete path.
ofwboot has a built-in automatic, to look for the
openbsd-partition.
ofwboot searches for the last openbsd-partition on
the disk and tries to boot it. It does not matter,
how much openbsd-installations exist. It does not
matter, on which partition openbsd was installed.
ofwboot allways looks for the openbsd-partition,
which is the last on the disk.
ofwboot searches only in that partition. ofwboot
needs only a path relativ to that partition.
In the example, ofwboot finds the openbsd-partition
7 and tries to boot the kernel with the name
"hd0:7,/bsd", which is not used, because the kernel
is named "bsd" on "/". In this example the correct
path has to be "/bsd". That path will be useable
by ofwboot.
But you can't specify that path. You got an error,
when you run ybin.
ybin is the 'alias' of lilo for powerpc.
workaround for the non-root-user
--
While poweron hold the four keys "win/apple", "alt",
"o" and "f" at the same time. Release the keys after
the appearing of the open firmware message.
On the open firmware prompt type in
"boot hd0:5,/ofwboot /bsd", if your partition "5" on
disk 0 is your new world boot partition and the
openbsd-partition has a kernel named "bsd" under "/".
You don't need to specify the path to the openbsd
partition (in my example 7), because ofwboot finds
it without further help. (And ofwboot finds only one,
if there are more of them. ofwboot finds the last one).
quick & dirty fix
-
ofboot.b is not visible as part of the debian-package
yaboot.
ofboot.b is generated on the fly by running ybin.
ybin calls "/usr/lib/yaboot/ofboot" as subprogramm.
Notice the missing ".b" at the end.
ofboot generates the file ofboot.b and stores it
in the new world boot partition.
In order to change ofboot.b you have to change
ofboot.
Fixing the bug is easy.
Cut the complete-path-specification in line 114 of
"/usr/lib/yaboot/ofboot".
old & buggy line 114:
# [ "$1" = "ybsd" ] && BOOT="load-base release-load-area \"
${4}${5%/*}/${5##*/},/bsd\" \$boot"
new & working line 114:
[ "$1" = "ybsd" ] && BOOT="load-base release-load-area \"
${4},ofwboot /bsd\" \$boot"
Ofcourse you have to run ybin another time after changing
/usr/lib/yaboot/ofboot.
a better solution
-
Change the use of the path-parameter "bsd=" in yaboot.conf.
Let this parameter point to the openbsd-kernel relativ
to the openbsd-partition.
In my example let the user use "bsd-kernel=/bsd"
and not "bsd=/dev/hda..."
And please change the hardcoded name of the openbsd-kernel.
ofboot allways set the name to "bsd". But that is not good.
If you compile a new openbsd-kernel, you usually
rename the old working kernel to "bsd.generic" or
"bsd.old".
If the new kernel doesn't work, you need a fallback, but
cannot use yaboot. Yaboot is only able to boot "bsd" and
not any otherwise named openbsd-kernel.
further information
---
Testet on Mac mini with debian-testing (01.Jun-2006).
Thank you for your passion to read this long text.
Yours
Peter Voigt
peter.voigt1 aht gmx.net
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Bug#372560: It's not a cdbs bug
Le Dim 11 Juin 2006 17:30, Mohammed Adnène Trojette a écrit : > On Sun, Jun 11, 2006, Julien Louis wrote: > > After some investigations it seems, it is *not* a cdbs bug but a > > file provided by the tarball (the config.status one). If this file > > is removed from the tarball, gandalf build well. I can prepare a QA > > upload (since it is orphaned) but i don't know what is the best > > solution, removing the file during initial clean or removing this > > file and upload a new tarball without this file. > > There is an RM: pending bug on gandalf. Is there a need to fix this > bug? definitely not -- ·O· Pierre Habouzit ··O[EMAIL PROTECTED] OOOhttp://www.madism.org pgpYOSUf6YaGX.pgp Description: PGP signature
ttf-thryomanes_1.2-2_i386.changes ACCEPTED
Accepted: ttf-thryomanes_1.2-2.diff.gz to pool/main/t/ttf-thryomanes/ttf-thryomanes_1.2-2.diff.gz ttf-thryomanes_1.2-2.dsc to pool/main/t/ttf-thryomanes/ttf-thryomanes_1.2-2.dsc ttf-thryomanes_1.2-2_all.deb to pool/main/t/ttf-thryomanes/ttf-thryomanes_1.2-2_all.deb Announcing to debian-devel-changes@lists.debian.org Closing bugs: 366206 Thank you for your contribution to Debian. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processing of ttf-thryomanes_1.2-2_i386.changes
ttf-thryomanes_1.2-2_i386.changes uploaded successfully to localhost along with the files: ttf-thryomanes_1.2-2.dsc ttf-thryomanes_1.2-2.diff.gz ttf-thryomanes_1.2-2_all.deb Greetings, Your Debian queue daemon -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#366206: marked as done (ttf-thryomanes: dangling symlinks / typo)
Your message dated Sun, 11 Jun 2006 19:02:10 -0700 with message-id <[EMAIL PROTECTED]> and subject line Bug#366206: fixed in ttf-thryomanes 1:1.2-2 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) --- Begin Message --- Package: ttf-thryomanes Version: 1:1.2-1 Severity: normal this package includes 3 dangling symlinks: /bin/ls: /var/lib/defoma/gs.d/dirs/fonts/thryn___.ttf: No such file or directory /bin/ls: /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType/thryn___.ttf: No such file or directory /bin/ls: /var/lib/defoma/fontconfig.d/T/Thryomanes-Normal.ttf: No such file or directory all of these point to /usr/share/fonts/truetype/thryomanes/thryn___.ttf whereas the file they're probably meant to point to is called /usr/share/fonts/truetype/thryomanes/thryrg__.ttf best, Florian -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (650, 'testing'), (600, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.15-max Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Versions of packages ttf-thryomanes depends on: ii defoma0.11.8-0.1 Debian Font Manager -- automatic f ii xutils6.9.0.dfsg.1-6 X Window System utility programs ttf-thryomanes recommends no packages. -- no debconf information signature.asc Description: Digital signature --- End Message --- --- Begin Message --- Source: ttf-thryomanes Source-Version: 1:1.2-2 We believe that the bug you reported is fixed in the latest version of ttf-thryomanes, which is due to be installed in the Debian FTP archive: ttf-thryomanes_1.2-2.diff.gz to pool/main/t/ttf-thryomanes/ttf-thryomanes_1.2-2.diff.gz ttf-thryomanes_1.2-2.dsc to pool/main/t/ttf-thryomanes/ttf-thryomanes_1.2-2.dsc ttf-thryomanes_1.2-2_all.deb to pool/main/t/ttf-thryomanes/ttf-thryomanes_1.2-2_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Adeodato Simó <[EMAIL PROTECTED]> (supplier of updated ttf-thryomanes package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Mon, 12 Jun 2006 03:33:55 +0200 Source: ttf-thryomanes Binary: ttf-thryomanes Architecture: source all Version: 1:1.2-2 Distribution: unstable Urgency: medium Maintainer: Debian QA Group <[EMAIL PROTECTED]> Changed-By: Adeodato Simó <[EMAIL PROTECTED]> Description: ttf-thryomanes - A Unicode font covering Latin, Greek, Cyrillic and IPA Closes: 366206 Changes: ttf-thryomanes (1:1.2-2) unstable; urgency=medium . * QA upload. * Fix hints file to refer to thryrg__.ttf instead of thryn___.ttf, which was causing dangling symlinks under /var/lib/defoma. Make prerm invoke defoma-font purge-all for upgrade as well, otherwise future changes in the hints file won't get fully reflected in the filesystem, and do it once more in preinst if upgrading from 1:1.2-1 or older. (Closes: #366206) * Update Standards-Version to 3.7.2 (no changes needed). Files: 6d45130e973decd5e9bbd007b05d8172 681 x11 optional ttf-thryomanes_1.2-2.dsc 7171c4cda6be58b0713d9baa7bdf6e2d 3443 x11 optional ttf-thryomanes_1.2-2.diff.gz d227d911b40bc62c5e22ad2bd4b3c890 751274 x11 optional ttf-thryomanes_1.2-2_all.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Signed by Adeodato Simó <[EMAIL PROTECTED]> iEYEARECAAYFAkSMx9cACgkQOzsxEBcMRN0cDQCg2k5f3UYZ/lrwLo2d6bEQ8Mf8 tnEAnRYnSXfKNoYgHXeHz/L2enOfHL5N =UFWW -END PGP SIGNATURE- --- End Message ---
Bug#372835: blackbook: Dead upstream, please create new upstream
Package: blackbook Severity: wishlist This is a warning to any adopter of the package: it's dead upstream, and so you'll want to make a new upstream if you adopt it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#372836: c2hs: New upstream available
Package: c2hs Severity: wishlist If anyone adopts this, they should be aware that there's a new upstream (0.14.5). -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (499, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.15-1-686 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
