Arch Linux Newsletter for June 04, 2008 Discussion

http://archlinux.org/static/newsletters … un-02.html
Here we are going to discuss any questions, suggestions or random talk about the newsletter for June 04, 2008. Feel free to contribute with ideas and suggestions.
As always thanks for your support,
In the name of the Arch Linux Newsletter Team
Eduardo "kensai" Romero

kensai wrote:
[vEX] wrote:I also think it should have been made clear that Tremuluos is only available for i686 and you need to enable the Community repository (I think it's enabled by default now, but I bet some people have it disabled).
Ok fixed everything but the interview, since I don't like correcting people in interviews, he is from Germany so English might not be his first language, still I always like Interviews to be left untouched.
Oh, and check it out now, I updated the Tremulous article with your note. ;)
Yeah, I feel the same way about the interview, it's just that previously in some interviews small typos have had [sic] next to them to point out the editor being aware of them.
weseven wrote:
Update: [vEX] from the forums pointed out: "it should have been made clear that Tremuluos is only available for i686 and you need to enable the Community repository (I think it's enabled by default now, but I bet some people have it disabled)."
false.
trem is for x86_64 too. the backport client you linked is only for i686, but if you search a bit on google, you can find svn client versions for 64 too.
playing trem on an arch64 laptop :)
Oh, I didn't spend much time searching for it, I just checked what's available in the Arch repositories, so in one way I'm still correct. It'd be nice to see a package (be it in Extra/Community or AUR) for us 64-bit users.
Last edited by [vEX] (2008-06-05 12:07:03)

Similar Messages

Arch Linux Newsletter for July 01, 2008, Discussion.

http://archlinux.org/static/newsletters … ul-07.html
Here we are going to discuss any questions, suggestions or random talk about the newsletter for June 04, 2008. Feel free to contribute with ideas and suggestions.
As always thanks for your support,
In the name of the Arch Linux Newsletter Team
Eduardo "kensai" Romero

Misfit138 wrote:
kensai wrote:
Dusty wrote:apparently people are more loyal to the Arch brand than the tux brand. :-D
Those people have not seen an angry penguin charging at them.
I most certainly am. Philosophically, I resent using the penguin kernel.
It's just that Arch is so damn good, it has spoiled me for anything else.
-->Same Here<--
The linux kernel can drive me crazy sometimes...
Hmmm, do you want to start ArchBSD Misfit? That is, FreeBSD + Pacman goodness + updated rc.conf?
I shouldn't have suggested that, I don't have the time to be a dev for anything right now.

Unofficial Arch Linux Newsletter for February, 2009

I don't want to step on anyones toes (sorry Kensai and pressh if I did), but I had a few things to say to the community, and some people were getting impatient, so here's a little unofficial Arch Linux Newsletter for February. Looking forward to the next official one!
If anyone wants to comment (constructive criticism, rants, hate mail, whatever) feel free to post.
Last edited by Ghost1227 (2009-02-04 09:31:39)

Dusty wrote:
pressh wrote:As I want to change a few things in the newsletter and Eduardo maybe too,
Did this make anybody else giggle? I want to change a few things with Eduardo myself... :-D
ah crap
[edit]
of course I meant to say that I want to change some things in both the newsletter and Eduardo
[edit2]
btw. Dusty, if you have any input on this in any way it is much appreciated. just let me know.
Last edited by pressh (2009-02-04 13:58:35)

Arch Linux Newsletter December 2009?

For those of you who didn't see my email on the Arch General mailing list, here's the situation with the Arch Linux Newsletter/Arch Linux Magazine. As many of you know, Kensai recently moved and got married and I recently moved and have been trying to find a job. My situation led to me having difficulty finding the time to dedicate to the Newsletter/Magazine that I have in the past. Combined with Kensai's absence (and as such, our inability to post anything even if we had a completed issue), this caused the lack of our great publication for the last few months. Thankfully, the situation has been rectified and we are now preparing for our next issue. Unfortunately, this solution has come at a cost. Our fearless leader has decided to step down from his position in order to dedicate more time to his new-found family and I can't say I blame him. As such, we wish Kensai the best and hope that once his life calms down him start contributing again, even if in just a small way.
After much deliberation (alright, so maybe I'm exaggerating a little bit), the Arch Linux development team has graciously decided that they want to keep me on as editor of our official publication. As such, I am preparing for the release of our next issue! I would like to see us make a comeback to where we left off and then some. I want to see more community contributions and writers, and I want to get the Schwag report back. I want more sections and special features and I even have a few surprises in store for you all down the road a bit.
This improvement is going to be a big project and I can't do it alone. If any of you, our loyal readers, are willing to contribute please step up and say so. Leave a message here, join me in #archlinux-magazine on freenode, or send me an email at [email protected]. You don't have to have a mass media background or immense technical knowledge, I can find a way for anyone to contribute. Help us make the new Arch Linux Newsletter/Arch Linux Magazine the best one yet!

kensai wrote:Is so hard to say good bye, guys thanks for all the support you have given me all this time, without this wonderful community I would have never done all I did. I hope one day I will come back, when things get more stable, cause you know, when starting something new the start is a mess most of the time until things settle down.
Don't think of it as a "good bye", but as a "See you soon". I'll bet you'll be back once you're settled in (which may or may not happen faster than you expect). Either way, best of luck for now and the future, and don't sweat the small things, chances are time will fix most of the small messes.
and to ghost: Do you have a rough estimate of when we might be getting started on the newsletter and such?

About the future of Arch Linux Newsletter.

Hi,
As you may have noticed, I have taken the job to make the Arch Linux weekly newsletter a possibility again. I the time I've been doing them, we speak of about 3 weeks, I have enjoyed writing them and have received very positive comments from the community that reads them. I would like to thank all of you personally for the support, you are the community and yours are the newsletter. But, as you all may have noticed the newsletter has been in an unchanged format for quite a long time. I mean, I just added the Humor section thats all, I know there is an email address to which you can all write your suggestions to, but I find people communicate and express themselves better on the forums.
So what I will ask of you, dear readers, suggestions of sections I should add/remove/edit, I will appreciate your constructive criticism in general. Express your thoughts in this thread to help me make a better more quality newsletter.
In other news, the newsletter won't be weekly no more, as Jason Chu and I have talked about, is easier to maintain a 2 time a month newsletter than 4 times a month, also the Arch Linux Developers/Community doesn't make that much noise as the other major distributions, we tend to be a bit quieter. The bright side is, the newsletter will be written with more time at hand, more stuff to write about, and will contribute to a better quality overall.
What has been suggested so far and I will work out on the next issue of the newsletter?
* Change the Bugs stats to not reflect the overall percentage but the actual bugs opened and closed that week.
As Roman Kyrylych points out: "They show a summary of status field "Progress" in open reports, but in 99% this field goes straight from 0% to 100%, so the overall number is always very low and doesn't really show anything".
So I wait for your suggestions as well.;)

Hi again,
I ask for your opinion again on the subject of the stats section in the newsletter, Do you find this an important part that should stay there?
I mean, this is going to be the most tedious, time-taking and in my opinion useless section I will have to write for the newsletter. I do want to bring a high quality newsletter but I feel this part doesn't contribute to the quality of the newsletter at all, Why?
* Newsletters that include this section are mostly from distributions that has point releases and not rolling releases.
* The number will always increase with minimum decrease because as a rolling release system Arch Linux is every package keep being updated everyday to newer versions, opening and closing more bugs by itself.
* People might not be interested in how many bugs are and how many are closed every week, since this numbers aren't even provided on the bug system itself.
Please give this a consideration and tell me your opinions.

Arch Linux newsletter: Featuring an interview with Judd Vinet.

Is time again for another interview, this one will feature in the newsletter scheduled for release on December 3, 2007. This time, the interview will be, with the creator and former leader of the Arch Linux Operating System, Judd Vinet. Following the style of the interview with Aaron Griffin, the ones asking the questions will be the community. Please, read below for the guidelines.
Guidelines: (Please, follow them)
* You may post as many questions as you want, just try to put them all in a single post.
* You may post humor questions, but please, try to include serious questions as well.
* This thread needs to be kept clean, so don't go Off-Topic, or Dusty will have no mercy on us. (Maybe a Taco will make him reconsider)
* apeiro can ask Judd Vinet any questions he feels he would like to hear answered.
* phrakture is not banned from asking neither.
* If you bought Judd Vinet's leather pants, you can't ask for your money back.
Now, on with the questions.
Thanks
Eduardo "kensai" Romero

I know is hard to make good questions to Judd Vinet, even harder when the community didn't had the same level of interaction they had with Aaron Griffin. As he were more accessible to the users. Judd Vinet is not to blame for this, he just didn't had enough time. So, this post is to ask you guys, to keep posting questions, think hard of any good questions the media would like to ask Judd Vinet because of his retirement as a leader of the Arch Linux OS.
If not enough questions are asked by the end of this week, I'll have to proceed with another interview and postpone Judd Vinet's interview for the next scheduled newsletter after that, December 17, 2007. So please, cooperation is needed, this is going to be the first interview after his retirement as the leader of Arch. Thanks.

Arch Linux skin for xmms/bmp/audacious

This is a simple skin for xmms/bmp/audacious with an Arch Linux look (based on a skin for Debian).
You can get it from here. Untar it in the Skins subdir (for audacious this is ~/.local/share/audacious/Skins/).
F

Thanks
Just paste the .tar.gz to ~/.xmms/Skins
No root-permission needed
(show hidden files!:))

Is Arch Linux right for me?

Arch seems like a pretty awesome distro, and I think I would like it a lot. But is it right for me?
I was first introduced to Linux and Unix-based systems last summer when I took a course at my local community college. Since then, I have installed Ubuntu on my HP laptop. In the past months, I have learned and taught myself a lot about the way linux works: downloading and installing software, Unix command line prompt, etc.
Ubuntu is a fantastic distro for linux beginners, but I feel like I'm ready to take the next step and I'm always itching to see a little more of what goes on behind the scenes. I read a guide on Arch over at LifeHacker and skimmed the "Getting Started" guide on Arch Wiki and I generally understood everything that was going on; nothing seemed way over my head. So I think I could handle Arch. What do you guys think?
If you think I should take Arch for a spin, is it practical to install it as my main OS on my main machine? Should I dual-boot it next to Ubuntu or similar? I am planning on building a PC this summer and am currently debating over which OS to use; Arch is a main candidate. My main uses for this computer will be surfing the net, listening to music (integration with my iPod would be great), a little video editing, some casual gaming, and general programming/tinkering with my computer.
I know y'all probably get a lot of these but I appreciate your feedback.

Check out the Beginner's Guide and The Arch Way in the wiki. It's important to note that what really distinguishes Arch from most other distros is that it isn't a distro in the most common sense of the term. Ubuntu, Fedora, SuSE, Sabayon, Mandriva, PCLOS, etc. have graphical installers that pre-configure everything for you; the choices are made for you, and you'll have to work around anything you don't find to your liking. You can easily add and remove programs, but always limited by what they've provided: packages that are patched in order to work in the way they've deemed appropriate, and an init system that's opaque to users (remember the fuss over certain graphics drivers not rendering Plymouth splashes correctly? I've never had that issue in Arch). Arch, on the other hand, is essentially a set of tools--the Arch Installation Framework, a couple init scripts, about six config files (give or take), repos, the ABS tree, the kernel and a package manager--that allow a user to craft their own operating system to their liking. A couple of the things I just mentioned are even optional as it is; at least three of those config files have never been touched by me, as I don't need them. Combine this sense of freedom and control with the DIY philosophy (which I find empowering as well, but hell--I enjoy research, learning and problem solving) and the close-knit community, and you've got my favorite distro. Ultimately, it's the choices of the developers that make a distro what it is; the software--at least in principle--rarely changes. In the case of Arch, most everything comes straight from upstream, goes in the testing repo briefly, then ends up in the standard repo, only altered if deemed necessary for security or basic functionality.
I left Ubuntu after switching to KDE and finding Kubuntu not to my liking; I also found that many of the "conveniences" of Ubuntu (and the 9-12 other distros I tried afterward) just got in the way. For example, why use the Ubuntu USB Startup Disk Creator or Unetbootin when "dd" is faster and easier? How much frustration could I have avoided installing the Catalyst driver in Ubuntu or SuSE if I'd done so manually (with a number of console commands I can count on one hand) rather than mess around with a GUI, thus knowing exactly what I did wrong? To me, it just seems better to start with what I absolutely need and build up piecemeal, rather than add a bunch of crap I don't need/want/even know is there in the first place and hide it all behind extra GUI's, then try and pick it apart. Ultimately, you make Arch what you want it to be. No one can tell you if it's right for you, or if you should install it (there are rare cases where folks here would flat-out say "No," but yours doesn't seem to be one of 'em ). Check out those wiki articles I mentioned; if it seems like something that interests you, give it a whirl!

New Arch Linux Logo for HP?

Hi i released 3D Arch Logos and the reaction was... that 2 peoples asked me to this:
Brutal !!! fresh
by code933k on: 05/03/2007, 15:16
code933k code933k
Home
It is amazing the effect that you've achieved with arch's logo. I was thinking some days ago if it would be possible to change the unpolished perspective of the official logo at arch's home page.
I wonder if you hadn't proposed this well proportioned, clear, and good angled image as the new official logo.
Arch is one of the best distros so you deserve double grats.
I hope to see more of your artwork soon. I drink to make other people interesting.
goood fresh
by spookykid on: 05/04/2007, 3:24
spookykid spookykid
Home
i agree you defenetely should post it in arch forums and see where it goes from there. would you mind posting the source? (original files)spookykidisthinking!
Here the thread:
http://gnome-look.org/usermanager/searc … n=contents
Here the logo:
http://www.2blabla.ch/stuff/Linux/Wallp … -color.png
Question: have the Arch Logo Designer intrest for my 3D logo?

root_tux_linux wrote:
I created that pic with cinema 4D on wine...
and now i change to blender or alias maya 7.0 ^^
Btw. Im a noobie in 3D world ^^
Well, I'm in a similiar situation atm. I used cinema4D a few years ago but stopped mainly because of my switch to linux.
I didn't want to use c4d under wine (and was unable to start it with recent wine version anyway..) and was kind of scared by blenders UI.
After reading a few tutorials my fear is gone and I start to enjoy using blender
Try it out! You'll like it...

Arch Linux Support for Atmel ATmega168

I'm thinking about buying this ATmega168: http://www.amazon.com/NerdKits-USB-Micr … B001I08PK8
I'm wondering if the avrdude, binutils-avr, and gcc-avr packages (http://www.archlinux.org/packages/?q=avr) will work with it... Does anyone know?
Last edited by tony5429 (2011-11-24 02:06:40)

not only yes. but heck yes. I use D.) All of the above on every AVR micro I have (including the ATmega168). sparkfun.com has a really good tutorial for getting started. I suggest it. (it is a windows tutorial, but the exact same software works the same on any PC.) One benefit of this tutorial is that it provides a fantastic skeleton makefile for all of your future AVR programming needs.
oh yeah, and AVRFreaks.com is another really good resource. I do quite a bit of work with AVR micro's. so if you ever have any specific questions feel free to PM me.

Arch Linux for Google Compute Engine

Hi Arch users,
I’ve created a tool that can create an Arch Linux image for Google Compute Engine. It has the compute-image-packages software preinstalled so basic GCE integration works.
I’m working to improve the boot times and shrink the image since it’s a bit larger than I’d like it to be. You can follow the instructions below to boot a virtual machine running Arch.
The source code is hosted on Github: https://github.com/GoogleCloudPlatform/ … ge-builder, pull requests welcome!
I've already built one today and has been made public on Cloud Storage at gs://jeremyje/arch-stable/arch-v20140906.tar.gz
Instructions to boot a VM with the image:
1. Create a project or pick an existing one. Turn on Compute Engine.
https://console.developers.google.com/
Click "Create project"
Enter a project name and project id.
Go to Compute > Compute Engine
If necessary, enable billing.
2. Add the Arch Image to your Project
Go to Compute > Compute Engine > Images
Click "New image"
Name: arch-v20140906
Description: Arch Linux built on 2014-09-06
Source Type: Cloud Storage object
Cloud Storage Object Path: gs://jeremyje/arch-stable/arch-v20140906.tar.gz
3. Create an Arch Linux instance.
Go to https://console.developers.google.com/
Select your project.
Compute > Compute Engine > VM instances > Add Instance
Select a zone, machine type, and select the “arch-v20140906” image.
You can SSH into the VM by clicking on the SSH button after you create it.
If you like command line here's the equivalent.
Google Cloud SDK: https://developers.google.com/cloud/sdk/
# Install Python2
pacman -S python2
# Install Cloud SDK
export CLOUDSDK_PYTHON=/usr/bin/python2
curl https://sdk.cloud.google.com | bash
echo “export CLOUDSDK_PYTHON=/usr/bin/python2” >> ~/.bashrc
source ~/.bashrc
# Login, create a project
gcloud auth login
# Add the image to your project.
gcloud compute images create archlinux gs://jeremyje/arch-stable/arch-v20140906.tar.gz --description “Arch Linux built on 2014-09-06”
# Create the instance booting Arch
gcloud compute instances create archvm --zone us-central1-a --machine-type f1-micro --image arch-v20140906
Lastly, there’s no official support for these images but if you find a problem please file a bug or submit a fix on Github.

Hi! Do you have any update of your Arch image?
Thank you

Archmobile: Arch Linux for ARM Devices

Hello,
I want to introduce our Operating System for ARM Devices, that's running on the OpenMoko NeoFreerunner, but we want to support more Devices.
We from http://archmobile.org port Arch Linux on ARM, and we want to give you the simple Freedom which has Arch Linux x86 for ARM.
We can already SSH on our Freerunners, and we nearly have X working. One of the Devs already uses our OS as Daily-Phone with QT Extended.
If you want to know more about us, or you want to try out our System visit us at http://archmobile.org !
The first Snapshot is already at http://naeg.archmobile.org/snapshots/ available. This Snapshot works on the Freerunner and you can SSH into your phone and play a lil bit with our OS Also you can install the System with our Installation Script we provide, to get a really up-to-date System and not configured.
It would be great if other people with other ARM Devices would contact us on IRC(on freenode #arch-arm) and we will try to support your ARM Device too. New Developer are always welcome
I think it would be awesome if we get some support from the official Arch Linux. An Entry in the list of Arch Related Projects would be great.
Feel free to talk about that.
Greetings, naeg - alias rott_at

Thanks for your tips to make the wiki better. I will edit the pages to avoid any confusion you've had. Although I won't do all the changes (e.g. remove $ and #). But I will then make a note which should clarify it.
markc wrote:
Some errors I encountered...
# touch /_Archlinux_ARM
/bin/touch: setting times of `_Archlinux_ARM': Invalid argument
This issue is known with a x86_64 host. I don't know where it originates from as i686 host is fine. Use this binary instead: http://stanny.homelinux.org/touch [1]. This is my home FTP. Thus it might not be available 24/7.
markc wrote:checking dependency style of gcc... /bin/touch: setting times of `sub/conftst1.h': Invalid argument
Should be fixed using the touch binary I provided.
markc wrote:bsdtar: Failed to set default locale
Unsupported ioctl: cmd=0xffffffff80046601
bsdtar: Couldn't list extended attributes: Function not implemented
The error in the first line might be solved by configuring your locales correctly. The error below is issued by qemu.
While this is annoying it doesn't appear to cause any harm. Just ignore it. You'll find other ioctls not being supported by qemu and we expect them to be fixed along with qemu's development.
edit:
[1] I moved it to a permanent location: http://archmobile.org/~harlekin/touch
Last edited by harlekin (2009-07-30 22:16:59)

First alternative skin for the Neuf Box 4 : Arch Linux skin !

Since the last firmware version of the Neuf Box 4, it is now possible to customize its web interface with skins.
As I've not seen any skin yet, I decided to make my own, base on the design of archlinux.org.
The result is here : Arch Linux skin for the NB4
with details on how to use it.
Tell me what you think

Would you be willing to post a larger image? That one is so tiny that it is hard to see. It seems like a great project, and from what I can see, it looks good.
When I first read the description, "integrated access device" sounded like some corporate/marketing drivel. But, it seems like a great device: "DSL modem that supports ADSL, ADSL2+, and fiber connections. It also integrates a a WiFi access point and three-port Ethernet switch, an RJ-11 phone jack with analog-to-IP phone network adapter, a print server for USB printers (two host ports are provided), a USB device port for USB networking with a PC, and a special Ethernet port for connection to an available TV decoder box."
Wow.

Arch Linux (and general Linux) graphics and artists community

TheBodziO has started a discussion about the (Arch) linux graphics community. That gives me an idea. It would be nice to create an online (sub)community dedicated to graphics, DTP, and photography centered around Arch Linux. For now, I can only offer some ideas, my experience in graphics and DTP, and lots of hosting space on a non-dedicated server.
The ideas for the (sub)community:
* an open forum for discussion, not just Arch-related but 'graphics on Linux' in general
* a wiki for Linux artists
* a gallery (d'oh!)
* an Arch LiveCD for graphics artists
* a dedicated graphics repository
If you have suggestions and/or are interested to participate, please post below.

For start I want to say that I'm content that the new thread have been started to discuss the matters of cooperation of designers and developers communities. It's a good sign.
As foxbunny said the whole idea is *much* more than another art repository. I thought about creating a common ground - a meeting point - for both developers and designers. Developers have the skills to code. Designers have needs and ideas how to speed up/ease their work. Developers create tools that designers use and designers provide feedback and ideas. What I think free software world lacks is an organized way to provide the pan-project and pan-distro connection between these groups.
To illustrate the whole thing on a simple example: let's assume that I'd love to have a possibility to lock some operations on elements of my project with password. It's because my work will be given to someone else who will be responsible for placing a text in proper places on the design. I don't want to see him to move or delete something accidentally. It's possible that also some other designers will find that feature useful too. Then maybe some developer will be willing to implement that. The trouble is, that if I propose that feature and encourage its implementation in gimp, I would have to repeat the same process for scribus for example. But the idea is common. I want to state it once and see who will catch the bait . To some extent it will promote deeper integration between different projects.
Today graphic designers have the tools for editing vector graphics, raster graphics some page design tools. These tools often use the same methodologies! There are bezier curves in gimp, inkscape, scribus... whatever yet they are implemented redundantly. Perhaps thanks to one thoughts sharing panel it will be possible to come with some common solutions. Maybe some common libraries or platforms will emerge in time? I think that mentioned meeting point will keep us close to unix philosophy: do it for a single purpose and do it well. In other words I think that it will allow us to have powerful building blocks on which something even better than today state of the art apps could be build.
I want to at least start some discussion about the issue. Hopefully this will be only a beginning.
First I want to ask: do you believe that a subcommunity of archers that would be responsible for communication between the developers and designers would be useful? If so then we could more precisely state our goals and code of conduct.
Designers experience is of the essence if we want to make free software usable for demanding "art" community.
Last edited by TheBodziO (2007-10-28 20:35:15)

Debtap - A script to convert .deb packages to Arch Linux packages

I wrote this script in my free time to help people who, for any reason, want to convert a .deb to an Arch Linux package. It works in a similar way with alien (which converts .deb packages to .rpm packages and vice versa), but, unlike alien, it is focused on accuracy of conversion, trying to translate Debian/Ubuntu packages names to the correct Arch Linux packages names and store them in the dependencies fields of the .PKGINFO metadata in the final package. In other words, it won't only create an Arch package with the data of the original .deb package, but also it will try to create a valid and as accurate as possible .PKGINFO metadata file in the converted package. It uses pkgfile and pacman utilities to achieve this accuracy. The final package can be installed like any local Arch Linux package. Debtap is now available on AUR!
FAQ
Q: What "debtap" stands for?
A: DEB To Arch (Linux) Package
Q: Isn't better to download an official package or write a PKGBUILD in case I need to compile a package or convert a .deb package to an Arch Linux package?
A: Sure it is, and I truely encourage you to do so. Debtap was written to create packages that either cannot be compiled (closed source packages) or cannot be built from AUR for various reasons (error during compiling or unavailable files), as a quick 'n' dirty solution and an extra option for creating Arch Linux packages for Arch Linux users.
Q: So debtap will help me only in case I need to convert specific .deb packages to Arch Linux packages?
A: No. In case you need to write a new PKGBUILD for a package that already exists in the Debian/Ubuntu distributions, by converting its .deb package to Arch package with debtap, thanks to the packages names translator function inside the script, it can help you determine which dependencies are needed for the package you write the PKGBUILD for and complete the necessary fields.
Q: What are the minimum requirements to run this script?
A: You need to have installed these dependencies: bash, binutils (provides ar utility for extracting .deb package), pkgfile, and fakeroot. You must run at least once (preferably recently) "debtap -u" to create/update pkgfile and debtap database (you do this with root privileges).
Q: Debtap needs a lot of time to convert a package. So, why this is happening?
A: Like I said, debtap is focused on accuracy. It won't just unpack a .deb package and then repackage its data to an Arch Linux package, ignoring metadata. Depending on the speed of your processor and the package itself, conversion can take from a few seconds to several minutes.
Q: During conversion I get several warning messages, why?
A: Debtap cannot be 100% accurate for several reasons, the main reason for this is the complexity of packages names. If you want to check the freshly generated .PKGINFO and .INSTALL (this is optional file) metadata files or even fix the untranslated packages names inside .PKGINFO, debtap offers you the option to edit these files before compressing the final package.
Q: How do I use debtap?
A: The syntax is quite simple actually: debtap [option] package_filename
For example: debtap world-of-goo-demo_1.0_i386.deb
Any recommendations or questions for debtap are welcomed!
Last edited by helix (2015-05-21 22:54:17)

Hi helix. I've had trouble trying to use your script with ubuntu software from The Open University
debtap OpenUniversity-ubuntu-0.1.3.20130104.deb
==> Extracting package data...
==> Fixing possible directories structure differencies...
==> Generating .PKGINFO file...
debtap OpenUniversity-ubuntu-0.1.3.20130104.deb
==> Extracting package data...
==> Fixing possible directories structure differencies...
==> Generating .PKGINFO file...
:: Enter Packager name:
NewPepper2013
:: Enter package license (you can enter multiple licenses comma seperated):
closed
:: If you want to edit .PKGINFO file, press (1) For vi (2) For nano (3) For a cu stom editor or any other key to continue:
==> Generating .MTREE file...
==> Creating final package...
xz: unrecognized option '--1-any.pkg.tar'
xz: Try `xz --help' for more information.
mv: cannot stat â*.xzâ: No such file or directory
==> Removing leftover files...
==> Package successfully created!
The software is called NewPepper 2013 but i've not been able to find it online except on the ou website.

Arch Linux Newsletter for June 04, 2008 Discussion

Similar Messages

Maybe you are looking for