Re: How to get a new palo source package into unstable?
Hi Helge! On 01/11/2014 10:37 PM, Helge Deller wrote: Since I'm not a debian-developer, I don't know how to get this package into debian unstable again. What is the usual process to get a new/old package back into debian unstable? Maybe someone of you who has a debian developer rights is willing to upload the source package? I'm mostly finished with palo now. I converted the package to the latest debhelper format, reformatted the copyright file to the new 1.0 format (still need to some missing copyright holders and verify the license is correct for all source files). I also added a README.source to explain what happened with palo after version 1.16. The remaining things are cleaning up the changelog, removing other cruft and updating files like README.Debian. Hope to get it finished by the weekend. I will send you the patches, have you ACK them and upload on Saturday or Sunday. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/530f4e65.7080...@physik.fu-berlin.de
Re: How to get a new palo source package into unstable?
Hi, without any intention to push. :)) I have uploaded a new GNU xorriso-1.3.5.tar.gz which produces the upcomming PALO header version 5 with command line at byte offset 1024 and length limit 1023. See also http://bazaar.launchpad.net/~libburnia-team/libisofs/scdbackup/revision/1112/libisofs/system_area.c http://bazaar.launchpad.net/~libburnia-team/libisofs/scdbackup/revision/1112/doc/boot_sectors.txt The old format as produced by genisoimage can be achieved by xorriso -as mkisofs option -hppa-hdrversion 4 The only open question of mine is what to store as ipl_entry at byte offset 248. Currently it is 0. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2393264222797446...@scdbackup.webframe.org
Re: How to get a new palo source package into unstable?
Hi,
- Will there be a binary template for the first sectors
Is it needed?
The comment in lib/common.h says that it is assembly language
and skips to code. That code would have to stem from some template
file.
But as you stated later in your newest mail, this is not the case.
Another outdated comment in common.h is:
This struct [firstblock] [...] must stay 256 bytes in length!
- What block ranges shall be claimed by how many partitions ?
The partition table is only relevant if the firstblock is on hard disc.
Since you target a bootable CD image it's not relevant and leave it 0.
In the x86 world of ISOLINUX or GRUB2, the ISO images can be
copied onto hard disc (resp. USB stick) and boot from there too.
For that purpose, there are MBR, GPT, and/or Apple Partition Map
at the beginning of the images. (E.g in Debian amd64 ISO images.)
Would similar be possible for HP-PA ?
Would HP-PA boot via USB at all ? (The last PA-RISC i saw was
a HP 735 which quite surely had no USB besides its HIL.)
ipl is the generic name.
genisoimage calls this obviously bootloader.
Can we stay with option name -hppa-bootloader or shall i change
it to -hppa-ipl ?
* kern_sz = 0 or rd_sz = 0 means no kern or ramdisk respectively.
Shall xorriso allow such values ?
No, I think it should not allow that.
We target a bootable install-image. For that kernel and ramdisk is needed,
right?
It is improbable that more users of xorriso HP-PA boot features
arise . Nevertheless, xorriso should not restrict deliberately
what might make sense in special situations.
So if PALO will be able to handle missing kernels (by gracefully
not booting) it might be worth to allow it.
I leave it to you to prescribe these constraints:
- May one of the kernels be missing ?
- May the RAM disk file be missing ?
xorriso (resp. libisofs) will enforce what you decide.
(Currently it wants to see command line and all four files.
Else you get
libisofs: FAILURE : Incomplete HP-PA PALO boot parameters
)
Give me a few days and I will actually test your code and send you
necessary patches (if needed).
All my published HP-PA activities are in this changeset
http://bazaar.launchpad.net/~libburnia-team/libisofs/scdbackup/revision/
You will have to adapt
libisofs/system_area.c:make_hppa_palo_sector()
to your new command line location and length limit.
In my local copy i already reduced the limit for file location
-if (adr64 0x) {
+if (adr64 0x7fff) {
iso_msg_submit(t-image-id, ISO_HPPA_PALO_OFLOW, 0,
- HP-PA PALO boot address exceeds 32 bit);
+ HP-PA PALO boot address exceeds 2 GB);
The API call iso_image_set_hppa_palo() might get even more
parameters, depending on what you decide about
firstblock.flags,
firstblock.ipl_entry
firstblock.kern32_native_sz
firstblock.kern64_native_sz
We will have to define the final prototype before next release
of libisofs. Afterwards it will be immutable. (No release
date is planned so far.)
As for kern*_native_gz:
xorriso can be linked with libz and is then able to uncompress
gzipped file content. So if your gzip.c and inflate.c are
compatible to program gzip, then it would be possible to
count the uncompressed bytes.
Linking of libz happens automatically if libz runtime and its
developement header files are installed when GNU xorriso
gets compiled.
Automatic detection of compressed files should be possible too.
Question is, whether it is always desirable to write kern*_native_gz
if the kernel file is recognized as gzipped.
When all decisions are made, i plan to keep the genisoimage style
production of PALOHDRVERSION 4 and to add a new System area type 5
for PALOHDRVERSION 5.
(See libisofs/libisofs.h , function iso_write_opts_set_system_area(),
options bits 2 to 7.)
There will probably be a new -as mkisofs option -hppa-header-version
with default value 5.
Have a nice day :)
Thomas
--
To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/21240645099121438...@scdbackup.webframe.org
Re: How to get a new palo source package into unstable?
Hi, I wrote: All my published HP-PA activities are in this changeset http://bazaar.launchpad.net/~libburnia-team/libisofs/scdbackup/revision/ For the higher levels of xorriso, there are also http://libburnia-project.org/changeset/5222 http://libburnia-project.org/changeset/5223 But if you need additional info via the user interface, then just hardcode it in libisofs. I will then do the wiring up to the libisofs API and the xorriso CLI. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/3220764509730568...@scdbackup.webframe.org
Re: How to get a new palo source package into unstable?
Hi, i am the developer of xorriso, which meanwhile replaced genisoimage for the ISO image production of most architectures by debian-cd. Are there plans to produce new bootable ISO images for hppa ? If so, will it be done by debian-cd ? If so, are you willing to give xorriso a try ? Steve McIntyre will probably be glad to switch away from genisoimage once more in debian-cd. But we'd need a successful test report. I have now reverse-engineered genisoimage/boot-hppa.c and verified my findings with the images debian-40r5-hppa-businesscard.iso and debian-508-hppa-businesscard.iso. -- This is what i figured out for libisofs/doc/boot_sectors.txt. Please correct me if i'm wrong: HP-PA via PALO for HP PA-RISC Sources: cdrkit-1.1.10/genisoimage/boot-hppa.c by Steve McIntyre st...@einval.com who states Heavily inspired by palo There are five parameters which get encoded into the first 248 bytes of the System Area: cmdline, bootloader, 32-bit kernel, 64-bit kernel, and ramdisk. They are all mandatory. While cmdline is simply a string of at most 127 characters, the other four point to data files inside the ISO image. All numbers are recorded big endian. Boot sector components: Byte Range | Value | Meaning -- | -- | 0 - 1 | 0x8000 | Magic 2 - 5 | PALO | 6 - 7 | 0x0004 | Version || 8 - 11 | kern32_adr | Byte address of the HPPA 32-bit kernel file || genisoimage option -hppa-kernel-32 12 - 15 | kern32_len | Byte count of the HPPA 32-bit kernel file || 16 - 19 | ramdsk_adr | Byte address of the HPPA ramdisk file || genisoimage option -hppa-ramdisk 20 - 23 | ramdsk_len | Byte count of the HPPA ramdisk file || 24 - 141 |cmdline | Command line || genisoimage option -hppa-cmdline || 232 - 235 | kern64_adr | Byte address of the HPPA 64-bit kernel file || genisoimage option -hppa-kernel-64 236 - 239 | kern64_len | Byte count of the HPPA 64-bit kernel file || 240 - 243 | bootld_adr | Byte address of the HPPA bootloader file || genisoimage option -hppa-bootloader 244 - 247 | bootld_len | Byte count of the HPPA bootloader file || -- | -- | --- Some open questions remain. Is there boot firmware documentation available ? Any official terminology to respect ? What is due to HP-PA firmware specs, what is due to PALO ? Especially i wonder whether it is really necessary to have all four files: kernel-32, kernel-64, bootloader, ramdisk or whether it would be ok to set address and length of e.g. kernel-64 to 0 in order to indicate that the image does not have a 64 bit kernel. (genisoimage throws exit_fatal(...) if there is none in the ISO. So libisofs currently insists in seeing all four files if any of them or the command line is given.) --- The -hppa-* functionality of genisoimage is now implemented in xorriso. Uploaded as http://www.gnu.org/software/xorriso/xorriso-1.3.5.tar.gz MD5 caad39471f76dd0df224d5a7dc4688c1 Build it by cd xorriso-1.3.5 ; ./configure ; make It is then executable without make install as ./xorriso/xorriso The following test mock-up delivered a plausible first sector for me: mount -o loop debian-508-hppa-businesscard.iso /mnt # Learn about the used mkisofs options view /mnt/.disk/mkisofs # Use them with xorriso's mkisofs emulation xorriso -as mkisofs \ -r -V 'Debian 5.0.8 hppa Bin-1' \ -o debian-508-hppa-repack.iso -hppa-cmdline '0/vmlinux initrd=0/ramdisk' \ -hppa-kernel-32 install/vmlinux-2.6.26-2-parisc \ -hppa-kernel-64 install/vmlinux-2.6.26-2-parisc64 \ -hppa-bootloader install/iplboot \ -hppa-ramdisk install/initrd.gz \ /mnt (I left out the many Jigdo options. They should work too.) Now i wonder whether debian-508-hppa-repack.iso would boot. --- man xorrisofs describes the mkisofs emulation and now says: -hppa-cmdline text Set the PALO command line for HP-PA. Up to 127 characters are permitted. Note that if one of the -hppa options is given, then the other four must be given with valid parameters, too. -hppa-bootloader iso_rr_path Designate the given path as HP-PA bootloader file. -hppa-kernel-32 iso_rr_path Designate the given path as HP-PA 32 bit kernel file.
Re: How to get a new palo source package into unstable?
Hi Thomas, On 01/14/2014 10:46 AM, Thomas Schmitt wrote: i am the developer of xorriso, which meanwhile replaced genisoimage for the ISO image production of most architectures by debian-cd. Are there plans to produce new bootable ISO images for hppa ? YES, I do have that plan. If so, will it be done by debian-cd ? No idea. If so, are you willing to give xorriso a try ? SURE! Steve McIntyre will probably be glad to switch away from genisoimage once more in debian-cd. But we'd need a successful test report. I have now reverse-engineered genisoimage/boot-hppa.c and verified my findings with the images debian-40r5-hppa-businesscard.iso and debian-508-hppa-businesscard.iso. -- This is what i figured out for libisofs/doc/boot_sectors.txt. Please correct me if i'm wrong: HP-PA via PALO for HP PA-RISC Sources: cdrkit-1.1.10/genisoimage/boot-hppa.c by Steve McIntyre st...@einval.com who states Heavily inspired by palo There are five parameters which get encoded into the first 248 bytes of the System Area: cmdline, bootloader, 32-bit kernel, 64-bit kernel, and ramdisk. They are all mandatory. While cmdline is simply a string of at most 127 characters, the other four point to data files inside the ISO image. All numbers are recorded big endian. Boot sector components: Please take a look at the latest palo bootloader: http://git.kernel.org/cgit/linux/kernel/git/deller/palo.git/ I changed a few things to make it more extensible. Especially look at struct firstblock in http://git.kernel.org/cgit/linux/kernel/git/deller/palo.git/tree/lib/common.h Byte Range | Value | Meaning -- | -- | 0 - 1 | 0x8000 | Magic 2 - 5 | PALO | 6 - 7 | 0x0004 | Version || 8 - 11 | kern32_adr | Byte address of the HPPA 32-bit kernel file || genisoimage option -hppa-kernel-32 12 - 15 | kern32_len | Byte count of the HPPA 32-bit kernel file || 16 - 19 | ramdsk_adr | Byte address of the HPPA ramdisk file || genisoimage option -hppa-ramdisk 20 - 23 | ramdsk_len | Byte count of the HPPA ramdisk file || 24 - 141 |cmdline | Command line || genisoimage option -hppa-cmdline ^^ that changed! || 232 - 235 | kern64_adr | Byte address of the HPPA 64-bit kernel file || genisoimage option -hppa-kernel-64 236 - 239 | kern64_len | Byte count of the HPPA 64-bit kernel file || 240 - 243 | bootld_adr | Byte address of the HPPA bootloader file || genisoimage option -hppa-bootloader 244 - 247 | bootld_len | Byte count of the HPPA bootloader file I added fields for compressed images... IPL entries are missing. A checksum (required by bios) is missing (need to look again!). || -- | -- | --- Some open questions remain. Is there boot firmware documentation available ? It's somewhere on http://parisc-linux.org/documentation/index.html Format is somewhere in the docs below PA-RISC 1.1 Architecture Specifications I think. Any official terminology to respect ? What is due to HP-PA firmware specs, what is due to PALO ? What do you mean by that? Especially i wonder whether it is really necessary to have all four files: kernel-32, kernel-64, bootloader, ramdisk or whether it would be ok to set address and length of e.g. kernel-64 to 0 in order to indicate that the image does not have a 64 bit kernel. If you don't include a 32- *and* 64bit kernel, it will not be a generic installation cd. Some machines don't boot 32bit kernels and vice versa. The palo bootloader chooses the right kernel to boot automatically. (genisoimage throws exit_fatal(...) if there is none in the ISO. So libisofs currently insists in seeing all four files if any of them or the command line is given.) --- The -hppa-* functionality of genisoimage is now implemented in xorriso. Uploaded as http://www.gnu.org/software/xorriso/xorriso-1.3.5.tar.gz MD5 caad39471f76dd0df224d5a7dc4688c1 Build it by cd xorriso-1.3.5 ; ./configure ; make It is then executable without make install as ./xorriso/xorriso I'll test. The following test mock-up delivered a plausible first sector for me: mount -o loop debian-508-hppa-businesscard.iso /mnt # Learn about the used mkisofs options view /mnt/.disk/mkisofs # Use them with xorriso's mkisofs emulation xorriso -as mkisofs \
Re: How to get a new palo source package into unstable?
Hi, Helge Deller wrote: 24 - 141 |cmdline | Command line || genisoimage option -hppa-cmdline ^^ that changed! [...] I added fields for compressed images... IPL entries are missing. A checksum (required by bios) is missing (need to look again!). So the new boot block cannot be produced by existing genisoimage ? I will examine the links you gave me and submit a new description proposal. What is due to HP-PA firmware specs, what is due to PALO ? What do you mean by that? I only had the source code of Steve's boot-hppa.c So i could not distinguish between what is prescribed by HP and what is a decision by PALO developers. Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/18600644875750623...@scdbackup.webframe.org
Re: How to get a new palo source package into unstable?
Hi, it is to early for a new description. I have lots of questions after reading http://git.kernel.org/cgit/linux/kernel/git/deller/palo.git/tree/lib/common.h - Will there be a binary template for the first sectors of the ISO image into which the struct firstblock shall patched ? - Shall xorriso allow kern_sz = 0 or rd_sz = 0 ? - Increment PALOHDRVERSION to 5 ? - What to write into cmdline_old ? - How to determine the uncompressed kernel sizes ? kern32_native_sz , kern64_native_sz - What value to write into flags ? - How to determine the value of ipl_entry ? - What block ranges shall be claimed by how many partitions ? - What sizes of cylinder and head would be appropriate ? (ISOLINUX x86 isohybrid prefers 64 heads/cyl, 32 sectors/head.) - You mentioned a checksum (required by bios) but i cannot spot a trace of it. What checksum algorithm will be used ? - The questions stem from this discussing with myself: The magic number is the assembly-language branch needed to skip over the rest of the structure. To what address does it jump and how does the code get there which shall be executed ? Will the user submit to xorriso a kindof boot block template which contains that code at some higher address ? (ISO 9660 allows up to 32768 user defined bytes at the start of the filesystem.) * kern_sz = 0 or rd_sz = 0 means no kern or ramdisk respectively. Shall xorriso allow such values ? #define PALOHDRVERSION 4 Shouldn't this become 5 now ? Version 4 is already used in the ISOs of Debian 4 and 5. struct firstblock char cmdline_old[128]; /* OLD: Up to 127 bytes of text plus a \0 */ So this is not used any more and should be 0s ? unsigned char pad1[0xf0 - 8 - 9 * sizeof (int) - 128]; /Start nagging mode/ I understand this is a file format. But the reader has no means to determine the writer's sizeof(int). So one will have to fixate the size of the integers rather than accommodating the file format to it. How about using 4 here, and to declare all applicable variables as int32_t resp. uint32_t ? Do you really need the offsets as signed integers ? xorriso will by default put the boot files at low block addresses in the ISO. Nevertheless this can be influenced by the user. Maybe there are valid reasons to put other files before the boot files. So xorriso has to test whether the resulting byte offsets exceed the field size. Unsigned would double the chance that they fit. /End nagging mode/ int kern32_native_sz; /* 32bit kernel: uncompressed file size */ int kern64_native_sz; /* 64bit kernel: uncompressed file size */ How do i determine these two values ? Shall they be handed over by program options ? Shall xorriso uncompress the images and count the bytes ? (What compression algorithm is used ?) unsigned int flags; Does this have a meaning already ? Do we need to pass a value by a program option ? int ipl_entry; How to compute this value ? struct partition part[4]; Argh. MBR-style partition entries. (I see it in part.h and shudder.) What block ranges shall be claimed by those partitions ? (0 to end of ISO image as partition 1 of type 0xf0, other three zero ?) What sizes of cylinder and head would be appropriate ? We have to assume them without knowing the device geometry where the ISO image will end up. (I wonder what happens if PC-BIOS encounters this thing which roughly looks like an MBR.) char cmdline[CMDLINELEN]; /* max 1023 bytes of text plus a \0 */ I assume that this is the new place for the command line. - Have a nice day :) Thomas -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/23407644901140110...@scdbackup.webframe.org
Re: How to get a new palo source package into unstable?
Hi Thomas, On 01/14/2014 02:56 PM, Thomas Schmitt wrote: it is to early for a new description. I have lots of questions after reading http://git.kernel.org/cgit/linux/kernel/git/deller/palo.git/tree/lib/common.h - Will there be a binary template for the first sectors of the ISO image into which the struct firstblock shall patched ? Is it needed? After looking at your code it might be sufficient what you have already. - Shall xorriso allow kern_sz = 0 or rd_sz = 0 ? No. (At least not both = 0) - Increment PALOHDRVERSION to 5 ? Yes, I think we should do that. For that the new palo should be in the repo though... - What to write into cmdline_old ? If version==5, then you should leave it empty. Instead write the cmdline to the end of the struct (which allows max. 1023 bytes). - How to determine the uncompressed kernel sizes ? kern32_native_sz , kern64_native_sz I think we should not take care of the possibility that you can feed compressed binaries in there. Just leave those new fields at zero and use the ones you already implemented. My goal is to rewrite the kernel make process so that it creates a self-extracting kernel image (like other arches do) so that this logic can go away from palo again. That said, I think you can leave your code as-is and put in zeroes here. - What value to write into flags ? Seems 0 is OK. - How to determine the value of ipl_entry ? It's the entry point in the IPL (bootloader) code. It's stored in the ipl file. I need to take a closer look at that again... - What block ranges shall be claimed by how many partitions ? The partition table is only relevant if the firstblock is on hard disc. (The same struct is used for tftp-boot, hard-disc boot and CD boot!). Since you target a bootable CD image it's not relevant and leave it 0. - You mentioned a checksum (required by bios) but i cannot spot a trace of it. What checksum algorithm will be used ? My fault. Checksum is needed for IPL code, not in the firstblock. Just ignore it... - The questions stem from this discussing with myself: The magic number is the assembly-language branch needed to skip over the rest of the structure. No. The firmware checks those two bytes. If they are not 0x80/0x00, then it will not boot from that media. To what address does it jump and how does the code get there which shall be executed ? Those fields define what the firmware loads (from where on media(=ipl_addr), length(=ipl_size) and the offset into the loaded region where it should jump to(=ipl_entry)): int ipl_addr; /* offset 0xf0 */ int ipl_size; int ipl_entry; ipl_addr needs to be 2k aligned on media. ipl_size needs to be a multiple of 4k (I think - needs checking). ipl_entry is offset into that file. ipl is the generic name. For parisc-linux this is what palo provides (iplboot file generated during make). Will the user submit to xorriso a kindof boot block template which contains that code at some higher address ? (ISO 9660 allows up to 32768 user defined bytes at the start of the filesystem.) * kern_sz = 0 or rd_sz = 0 means no kern or ramdisk respectively. Shall xorriso allow such values ? No, I think it should not allow that. We target a bootable install-image. For that kernel and ramdisk is needed, right? #define PALOHDRVERSION 4 Shouldn't this become 5 now ? Version 4 is already used in the ISOs of Debian 4 and 5. yes. struct firstblock char cmdline_old[128]; /* OLD: Up to 127 bytes of text plus a \0 */ So this is not used any more and should be 0s ? Yes. unsigned char pad1[0xf0 - 8 - 9 * sizeof (int) - 128]; /Start nagging mode/ I understand this is a file format. But the reader has no means to determine the writer's sizeof(int). So one will have to fixate the size of the integers rather than accommodating the file format to it. How about using 4 here, and to declare all applicable variables as int32_t resp. uint32_t ? I would like to change it in the palo code, but if you have a copy that's ok. Do you really need the offsets as signed integers ? xorriso will by default put the boot files at low block addresses in the ISO. Nevertheless this can be influenced by the user. Maybe there are valid reasons to put other files before the boot files. So xorriso has to test whether the resulting byte offsets exceed the field size. Unsigned would double the chance that they fit. IIRC all files need to be stored inside the first 2GB of the media. Give me a few days and I will actually test your code and send you necessary patches (if needed). Helge -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52d5b5fb.4040...@gmx.de
Re: How to get a new palo source package into unstable?
Hello Helge! On Sat, Jan 11, 2014 at 10:37:52PM +0100, Helge Deller wrote: as you might have noticed, we did huge progress on the HPPA (PA-RISC) port: http://buildd.debian-ports.org/stats/ Indeed. Congratulations on that! I'm glad to see the HPPA port coming back to life. I'd love to test it myself, but the only PA-RISC machine that I currently know of which is in my vicinity is located inside a laboratory at my physics department and it's still running HP-UX. Might be that it gets scrapped soon and replaced with something more fancy so that I can get hold of it, who knows ;). In order to be able to boot parisc machines, the hppa port needs the palo debian package. PALO is the PA-RISC boot loader and a boot-loader-image generator, similar to lilo on i386 or silo on sparc. Or aboot on the Alpha machines. I've continued to maintain and further develop palo. The new palo git repository is now at: git://git.kernel.org/pub/scm/linux/kernel/git/deller/palo.git and the source should compile and run on all plattforms. A simple checkout and dpkg-buildpackage should work. Thank you very much for doing this (and the hard work of bringing the buildds back to life). Even though I currently don't own a PA-RISC machine, I'm very glad that someone took care of it, such that owners of these machines can still use it with a current Debian release. Since I'm not a debian-developer, I don't know how to get this package into debian unstable again. What is the usual process to get a new/old package back into debian unstable? Maybe someone of you who has a debian developer rights is willing to upload the source package? I'm a Debian Developer with full upload permissions to the archive and would absolutely love to help you get the boot loader (and any other possibly necessary packages) back into Debian. The best is to have the package(s) uploaded to Debian Mentors [1] so I can grab them from there and review them, send you suggestions on improving them and finally upload them. Plus, it would be nice to have access to a PA-RISC machine myself so I can perform a test build and inspect the finished package. Would that be possible? PS: I have noticed that the HPPA builds never include the build log, for example radeontop [2]. Would it be possible to have these enabled as well, so we can easily find out what went wrong when a build failed? Cheers, Adrian [1] http://mentors.debian.net/ [2] http://buildd.debian-ports.org/status/package.php?p=radeontopsuite=sid -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20140112163248.ga10...@physik.fu-berlin.de
Re: How to get a new palo source package into unstable?
On 01/12/2014 02:15 AM, Paul Wise wrote: On Sun, Jan 12, 2014 at 5:37 AM, Helge Deller wrote: I don't know how to get this package into debian unstable again. http://mentors.debian.net/intro-maintainers What is the usual process to get a new/old package back into debian unstable? http://www.debian.org/doc/manuals/developers-reference/pkgs.html#reintroducing-pkgs Paul, thank you for those hints! I'll read through it. Helge -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52d2c502.2090...@gmx.de
Re: How to get a new palo source package into unstable?
Hi Adrian, On 01/12/2014 05:32 PM, John Paul Adrian Glaubitz wrote: On Sat, Jan 11, 2014 at 10:37:52PM +0100, Helge Deller wrote: as you might have noticed, we did huge progress on the HPPA (PA-RISC) port: http://buildd.debian-ports.org/stats/ Indeed. Congratulations on that! I'm glad to see the HPPA port coming back to life. I'd love to test it myself, but the only PA-RISC machine that I currently know of which is in my vicinity is located inside a laboratory at my physics department and it's still running HP-UX. Might be that it gets scrapped soon and replaced with something more fancy so that I can get hold of it, who knows ;). Good thing is, that those machines got pretty cheap now. A Dualcore-C8000 workstation is available on ebay for 100 EUR. In order to be able to boot parisc machines, the hppa port needs the palo debian package. PALO is the PA-RISC boot loader and a boot-loader-image generator, similar to lilo on i386 or silo on sparc. Or aboot on the Alpha machines. I've continued to maintain and further develop palo. The new palo git repository is now at: git://git.kernel.org/pub/scm/linux/kernel/git/deller/palo.git and the source should compile and run on all plattforms. A simple checkout and dpkg-buildpackage should work. Thank you very much for doing this (and the hard work of bringing the buildds back to life). Even though I currently don't own a PA-RISC machine, I'm very glad that someone took care of it, such that owners of these machines can still use it with a current Debian release. Since I'm not a debian-developer, I don't know how to get this package into debian unstable again. What is the usual process to get a new/old package back into debian unstable? Maybe someone of you who has a debian developer rights is willing to upload the source package? I'm a Debian Developer with full upload permissions to the archive and would absolutely love to help you get the boot loader (and any other possibly necessary packages) back into Debian. Thanks! AFAIK the bootloader is the only package which is parisc specific. The best is to have the package(s) uploaded to Debian Mentors [1] so I can grab them from there and review them, send you suggestions on improving them and finally upload them. I uploaded it, and CC'ed you on the request. http://mentors.debian.net/package/palo The info at top of the website is the latest package with most warnings fixed. It would be nice if you could help me (off-list) further on that. Plus, it would be nice to have access to a PA-RISC machine myself so I can perform a test build and inspect the finished package. Would that be possible? Sure, I'll send you login details off-list. If other people here on the list want access, please let me know. PS: I have noticed that the HPPA builds never include the build log, for example radeontop [2]. Would it be possible to have these enabled as well, so we can easily find out what went wrong when a build failed? We had problems with sending mails from the buildds when I started the buildds mid december. Currently we have 5 buildds running: http://unstable.buildd.net/index-hppa.html Since around 2-3 weeks, all buildds except mx3210 do send build logs. I can reschedule a rebuild of radeontop for you, or you can just build it yourself on the machine for which I send you a login. Just let me know. Thanks! Helge -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52d30ad2.8030...@gmx.de
Re: How to get a new palo source package into unstable?
Am 12.01.2014 um 22:36 schrieb Helge Deller del...@gmx.de: PS: I have noticed that the HPPA builds never include the build log, for example radeontop [2]. Would it be possible to have these enabled as well, so we can easily find out what went wrong when a build failed? We had problems with sending mails from the buildds when I started the buildds mid december. Currently we have 5 buildds running: Well, more likely 3 machines with multiple buildd instances running on them... ;) I'm already thinking about how to do multi-cpu support for buildd.net. That would get rid off of having multiple users the update-buildd.net client. But as m68k has no SMP machines it will get difficult... ;) http://unstable.buildd.net/index-hppa.html Since around 2-3 weeks, all buildds except mx3210 do send build logs. What's the problem? Elgar on m68k has problems in receiving mails, so we use a ppp setup (pptp) to tunnel through, but of course you could use that to send mails as well, of course... -- Ciao...// Fon: 0381-2744150 Ingo \X/ http://blog.windfluechter.net gpg pubkey: http://www.juergensmann.de/ij_public_key.asc -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/b4d0aab5-4a67-483c-9c9b-9dee8fcb8...@2014.bluespice.org
Re: How to get a new palo source package into unstable?
On 01/12/2014 11:07 PM, Ingo Jürgensmann wrote: Am 12.01.2014 um 22:36 schrieb Helge Deller del...@gmx.de: PS: I have noticed that the HPPA builds never include the build log, for example radeontop [2]. Would it be possible to have these enabled as well, so we can easily find out what went wrong when a build failed? We had problems with sending mails from the buildds when I started the buildds mid december. Currently we have 5 buildds running: Well, more likely 3 machines with multiple buildd instances running on them... ;) Yes :-) I'm already thinking about how to do multi-cpu support for buildd.net. That would get rid off of having multiple users the update-buildd.net client. But as m68k has no SMP machines it will get difficult... ;) I think it would be easier to support, if the buildd-package would support multiple buildds running on one machine out of the box... http://unstable.buildd.net/index-hppa.html Since around 2-3 weeks, all buildds except mx3210 do send build logs. What's the problem? Elgar on m68k has problems in receiving mails, so we use a ppp setup (pptp) to tunnel through, but of course you could use that to send mails as well, of course... Well, John David Anglin owns the mx3210 machine, and I don't know why he hasn't set up the buildds to send the build logs yet. Maybe traffic? Helge -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52d3180f.1040...@gmx.de
Re: How to get a new palo source package into unstable?
On 12-Jan-14, at 5:32 PM, Helge Deller wrote: Well, John David Anglin owns the mx3210 machine, and I don't know why he hasn't set up the buildds to send the build logs yet. Maybe traffic? As far as I know, mx3210 is sending log. For example, http://buildd.debian-ports.org/status/fetch.php?pkg=swift-imarch=hppaver=2.0%2Bdev6-1stamp=1389546479 Dave -- John David Anglin dave.ang...@bell.net -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/blu0-smtp11a11ddc25dd4693b2fea197...@phx.gbl
Re: How to get a new palo source package into unstable?
Hi Helge! On 01/12/2014 10:36 PM, Helge Deller wrote: Indeed. Congratulations on that! I'm glad to see the HPPA port coming back to life. I'd love to test it myself, but the only PA-RISC machine that I currently know of which is in my vicinity is located inside a laboratory at my physics department and it's still running HP-UX. Might be that it gets scrapped soon and replaced with something more fancy so that I can get hold of it, who knows ;). Good thing is, that those machines got pretty cheap now. A Dualcore-C8000 workstation is available on ebay for 100 EUR. If just had enough room. There are already too many Amigas taking up my space :). Still, I like to support the port as much as I can. I'm a Debian Developer with full upload permissions to the archive and would absolutely love to help you get the boot loader (and any other possibly necessary packages) back into Debian. Thanks! AFAIK the bootloader is the only package which is parisc specific. Ok, good to know. The best is to have the package(s) uploaded to Debian Mentors [1] so I can grab them from there and review them, send you suggestions on improving them and finally upload them. I uploaded it, and CC'ed you on the request. http://mentors.debian.net/package/palo The info at top of the website is the latest package with most warnings fixed. It would be nice if you could help me (off-list) further on that. Will do! I'll answer your separate mail later! Plus, it would be nice to have access to a PA-RISC machine myself so I can perform a test build and inspect the finished package. Would that be possible? Sure, I'll send you login details off-list. If other people here on the list want access, please let me know. Thanks, got them. Will change the password and install my SSH key ASAP. We had problems with sending mails from the buildds when I started the buildds mid december. Currently we have 5 buildds running: http://unstable.buildd.net/index-hppa.html Since around 2-3 weeks, all buildds except mx3210 do send build logs. Ah, glad to hear it has been fixed. Then there's nothing I am worrying about. Are you working together with Ingo Juergensmann to update the buildd status information on buildd.net? I can reschedule a rebuild of radeontop for you, or you can just build it yourself on the machine for which I send you a login. Just let me know. Don't worry about radeontop. I just picked that package as an example to check whether the build logs are still missing or not. This is one of my own packages and the last upload was just done a few weeks ago, so I thought I might check this one to see whether the problem has already been addressed. But when you say the logs are properly uploaded now, I'm happy. So, please don't reschedule the package, it will updated in the very near future anyway. Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52d33683.2020...@physik.fu-berlin.de
Re: How to get a new palo source package into unstable?
On 01/12/2014 11:54 PM, John David Anglin wrote: As far as I know, mx3210 is sending log. For example, http://buildd.debian-ports.org/status/fetch.php?pkg=swift-imarch=hppaver=2.0%2Bdev6-1stamp=1389546479 Perfect then :). Nothing to worry about. Btw, where is hpviz located, I feel the lag. North America, I guess? Adrian -- .''`. John Paul Adrian Glaubitz : :' : Debian Developer - glaub...@debian.org `. `' Freie Universitaet Berlin - glaub...@physik.fu-berlin.de `-GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913 -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52d339c0.3090...@physik.fu-berlin.de
Re: How to get a new palo source package into unstable?
On 12-Jan-14, at 7:56 PM, John Paul Adrian Glaubitz wrote: On 01/12/2014 11:54 PM, John David Anglin wrote: As far as I know, mx3210 is sending log. For example, http://buildd.debian-ports.org/status/fetch.php?pkg=swift-imarch=hppaver=2.0%2Bdev6-1stamp=1389546479 Perfect then :). Nothing to worry about. Btw, where is hpviz located, I feel the lag. North America, I guess? hpviz is in the mountains of New Mexico. mx3210 is in Ottawa, Canada. Dave -- John David Anglin dave.ang...@bell.net -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/blu0-smtp726910bff555b264a9aaef97...@phx.gbl
Re: How to get a new palo source package into unstable?
Helge Deller dixit: Since I'm not a debian-developer, I don't know how to get this package into debian unstable again. Does it build on, and is it useful, on release architectures? (For example, we have mac-fdisk on m68k which is also used on powerpc.) If yes, you can get it into unstable using the normal ways, that is, using a Debian Developer as sponsor, or by becoming DM. If no (such as atari-fdisk on m68k), you can only upload it to the “unreleased” distribution on debian-ports.org. For that, you merely need upload rights (“porter upload”) there, from Aurélien. bye, //mirabilos -- Support mksh as /bin/sh and RoQA dash NOW! ‣ src:bash (268 (291) bugs: 0 RC, 188 (204) IN, 80 (87) MW, 0 FP) ‣ src:dash (89 (106) bugs: 2 RC, 43 (49) IN, 44 (55) MW, 0 FP) ‣ src:mksh (2 bugs: 0 RC, 0 IN, 2 MW, 0 FP, 1 gift) http://qa.debian.org/data/bts/graphs/d/dash.png is pretty red, innit? -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/pine.bsm.4.64l.1401112243060.27...@herc.mirbsd.org
Re: How to get a new palo source package into unstable?
Hi Thorsten, On 01/11/2014 11:46 PM, Thorsten Glaser wrote: Helge Deller dixit: Since I'm not a debian-developer, I don't know how to get this package into debian unstable again. Does it build on, and is it useful, on release architectures? (For example, we have mac-fdisk on m68k which is also used on powerpc.) Yes, it is useful for other architectures like ia32/amd64. With it, you e.g. create the bootable images for parisc. For that it puts together the root file system, the 32- and 64-bit linux kernels and the native bootloader into one file which can be burnt to CD or booted via TFTP. When palo was still in the debian 5.0 it was built for all architectures. If yes, you can get it into unstable using the normal ways, that is, using a Debian Developer as sponsor, or by becoming DM. Either one is fine for me. Maybe it makes more sense if I can become a DM ? If yes, how? If no (such as atari-fdisk on m68k), you can only upload it to the “unreleased” distribution on debian-ports.org. For that, you merely need upload rights (“porter upload”) there, from Aurélien. I did uploaded the palo binary deb package (for hppa) to the unreleased distro. So, it's there since weeks, but for a debootstrap/debian-cd-installation it needs to be at least in unstable too. Helge -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52d1d276.9000...@gmx.de
Re: How to get a new palo source package into unstable?
On Sun, Jan 12, 2014 at 5:37 AM, Helge Deller wrote: I don't know how to get this package into debian unstable again. http://mentors.debian.net/intro-maintainers What is the usual process to get a new/old package back into debian unstable? http://www.debian.org/doc/manuals/developers-reference/pkgs.html#reintroducing-pkgs -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-hppa-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/CAKTje6GQeuMXNcy-Fb-hHMbYGAdkVH+LQ5xxnZpmfzavRjdF=w...@mail.gmail.com
