Outdated packages and arch-etiquette

I have a question about arch-etiquette. I looked froward an answer around, but did not find it.
If one or more apps in the repos are out-of-date from a lot if time (a couple of months), have been already flagged as out-of-date, but nobody seems to care, is it wise and polite to email directly the maintainer? Or is it a rude behaviour I should avoid, since any maintainer has a well-established priorities list?
In this specific case, the apps I care about are xchat and moc (maintained by the same person), but I would like to know how I should behave in any other analogous situation.
Thanks for any tip.

Would it be possible, in the future (possible) integration with AUR, to have a list of comments to each package in the official repos?
The comments should be editable only by the maintainers, if there's something to tell about that package (or users start sending out-of-date mails). The webpage is a good place to put such comments because the web interface is the only place these notifications can be sent from. Also, it might be a good place to display install comments (the ones in post_install for example).
This way communication problems as the ones described above might be avoided.

Similar Messages

Development packages in Arch [SOLVED]

Hi all,
I need some development packages to build some programs, but I cannot seem to find them in Arch. I was wondering if anyone knew if they existed.
Examples are:
freetype2-devel
libjpeg-devel
xorg-x11-devel
Obviously if you ignore the -devel part, I can almost always find every single package in Arch. For example freetype and libjpeg and xorg are here, but their -devel counterparts are missing. As these are required to build packages, and Arch sometimes requires us to do so, how can they be missing?
Thanks

I just missed your post! Was about to come here and thank you for the solution
Cheers miqorz

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.

List of packages with arch-specific patches

Considering moving over from Fedora, having just learned about how many Fedora-specific patches are in their repositories. (Installing vanilla glibc from source bricks my Fedora 22 installs, without incorporating the Fedora-specific patches - which was easy to do, but prefer not to...)
I'd much prefer to run cleaner vanilla packages, particularly so I can install from svn/git source to fix bugs I run into before they're released.
Hoping there is a list (or an easy way to get a list) of the packages that arch has put arch-specific patches into. i.e. Installing through pacman will be a modified version from the actual upstream release of that version. Totally OK to answer my question outside the context of AUR, because I suspect the list grows when including that.
Linux From Scratch has a list of what patches are required for their system. It's bash, bc memory leak, bzip2, coreutils, glibc, kbd backspace, mpfr, readline, and sysvinit. (Beyond Linux From Scratch has a lot more, and its "list" is visible at http://www.linuxfromscratch.org/patches/blfs/ )
Hoping there's a (short) list like that for arch as well. Partially so if I'm installing unreleased source, I know whether I need to incorporate the arch-specific patches (like building my own package for packman) rather than just make install.
Last edited by jamespharvey20 (2015-06-09 07:55:06)

I don't think you'll ever need to install unreleased sources as they end up in testing pretty quick. Have a look at https://wiki.archlinux.org/index.php/Arch_Build_System for tips how to modify the official packages.
As for the list, it's pretty easy to construct. The following is a list of core-packages that have .patch files included in their repo, with the number representing the number of patches:
for f in packages/*/repos/core-x86_64/*.patch; do f=${f#packages/}; echo ${f%%/*} ; done|sort|uniq -c|sort -rn
10 libsasl
9 systemd
6 make grub
7 linux-lts
4 libarchive crda
3 vi pam mdadm kbd isdn4k-utils iproute2
2 texinfo shadow openssl openssh nss nfs-utils gcc
1 xinetd wpa_supplicant usbutils rpcbind psmisc ppp pcre p11-kit openldap net-tools mpfr mkinitcpio-nfs-utils mkinitcpio-busybox m4 lvm2 logrotate linux linux-atm librpcsecgss libffi krb5 keyutils jfsutils iptables hdparm gzip grep glibc glib2 gdbm efibootmgr e2fsprogs coreutils bzip2 bridge-utils binutils bash gnutls
Last edited by Spider.007 (2015-06-09 11:11:30)

Pkgman - a bash script for local package and PKGBUILD management

hi all,
here is a script which manages a local repository and lets you edit
PKGBUILDs and other related files, automatically generates checksums,
build packages, add them to your local repo and so on.
it also has AUR support for submitting tarballs, leaving comments, etc.
get it from here:
http://sourceforge.net/projects/pkgman/
and AUR package:
http://aur.archlinux.org/packages.php?ID=17100
you need abs, curl and pacman and optionally namcap and desktop-file-utils.
RTFM online:
http://sourceforge.net/apps/mediawiki/p … n_man_page
first of all copy the pkgman.conf and AUR.conf files from /usr/share/pkgman to ~/.config/pkgman/ or ${XDG_CONFIG_HOME}/pkgman - if ${XDG_CONFIG_HOME} is set,
edit these two files and then run
pkgman --runmefirst
pkgman doesn´t install anything. if you want it just builds the package and moves it to your local repository. install it then with pacman.
it also has no dependency handling. there are many other tools which provide this.
the main intention was to keep track of package versions, different PKGBUILD versions and own AUR submitted tarballs; also to keep a clean local repository and clean build directories.
pkgman is stable now. i´m using it for months without any issues.
however, if there are problems or feedback please post them here.
vlad
changelog:
version 2.4:
*pkgman now respects the PKGDEST and SRCDEST variables from makepkg.conf. (though it still moves the src.tar.gz and .pkg.tar.gz to package backup directory).
version 2.5:
*pkgman uses PKGDEST if SRCDEST not set in makepkg.conf.
version 2.6 -> r26:
*changed version system: version 2.6 is now r26!
*minor changes: > pkgman uses now the $SHELL variable.
> new and more comprehensible manpage description (thanks to bender02)
version r27:
*changed SRCDEST since it's only a cache dir. all files (pkg.tar.gz and src.tar.gz) go to PKGDEST.
version r28:
*added new variable ShellCommand to pkgman.conf. Default is $SHELL.
*One might use an external application (like screen or xterm) to switch to build directory and edit files simultaneously.
version r30:
*minor changes. nothing crucial
r32: *OverwriteExistingPackage isn't used anymore. one can delete it from ~/.config/pkgman/pkgman.conf.
*minor changes
version r33:
*"-l|--list" also shows installed package version and available ABS/AUR PKGBUILD version for given package.
*"-a|--abs" can now also be used with other options (like "-e")
r39: * when backing up src.tarballs it asks whether to backup the source file or not
* more detailed "--list" option - also shows if package is installed or not and available ABS/AUR version
* added prompt to clean up directory after makepkg
* when checking pkg.tar.gz also possibility to check for conflicts with files of already installed packages
* use $PAGER instead of less
* --help directly shows the manpage
* --shorthelp shows a brief usage overview
* added a custom prompt, but only when using bash (is somehow experimental - works fine here for me)
* minor internal changes
* pkgman also reads ~/.aurvote file for getting aur name and password. if one already uses aurvote then there is no need for the
~/.config/pkgman/AUR.conf file.
r40: * new manual page & rewrite of usage function
* both option "--flush" and "--flushall" were omitted in favor of the more versatile "--cleanup" option
* pkgman <packagename> checks now if <packagename> is owned by user
* backup option after each editing
* added license
* minor internal changes
r41: * just small bug fixes, nothing crucial.
r42: * more bugs fixed.
r45: * new options added:
> --listversions: list local and available versions of installed packages from LocalPackages directory
> --getownpackages: synchronize local own packages with AUR
* added new variable in pkgman.conf:
> ListOutputInPager: output of, for example, "--list" or "--own" is piped into $PAGER
* added a new optional dependency "desktop-file-utils" for validating desktop entry files
* also supports now auto-generation of sha sums not only md5
* internal fixes due to AUR interface changes:
> use of json interface
> correct parsing of package category
* added 2 proto files (located under /usr/share/pacman):
> proto.desktop: a template for *.desktop files
> PKGBUILD-lib32.proto: a template for lib32 packages for x86_64
* some code changes and fixes
r46: * added new option to pkgman.conf (AutoGenerateSums).
> if AutoGenerateSums=no then pkgman asks whether to generate checksums or not.
> if set to yes it behaves like in former versions.
r52: * "--getownpackages" with more than 100 packages works again
* added new option "--cachecopy":
For each package in CacheCopyList (new variable in pkgman.conf) get existing package from pacman's cache directory - if
CopyPkgFromCache (new variable in pkgman.conf) is set to yes - and/or create a source tarball of PKGBUILD and related files from ABS -
if CopySrcFromABS (new variable in pkgman.conf) is set to yes - and copy them to package backup directory.
* added new variables to pkgman.conf:
> "CacheCopyList=file" - batch backup file, one package per line - default location is "$HOME/.config/pkgman/package.list".
> "CopySrcFromABS=[yes|no]"
> "CopyPkgFromCache=[yes|no]"
* some bugfixes
* docs completed
* CacheCopyList should look like
package1
package2
#this is a comment
! this too
package3
!package4
r54: * renamed "--listversions" option to "--diffversions". makes more sense!
from the man page:
pkgman --diffversions
Show differing ABS/AUR versions of installed packages from LocalPackages.
r55: * minor changes.
r57: * testing release
* added a new option "--rollback":
"pkgman <packagename> --rollback" - checks http://arm.kh.nu for available package versions,
lets you choose one, fetches the package and
moves it to the <packagename> backup directory (if "--repoadd" is used).
r59: * stable release
* new option "--rollback" (see r57):
it checks http://arm.kh.nu (Arch Rollback Machine) for available package versions,
downloads chosen file and moves it to local repository (if "-r|--repoadd" is used).
* posting files/comments/etc to AUR should work now again.
r65: *stable release
* new option "-M,--meta" to create metapackages and add them and their dependencies to local repository.
it searches for deps inside the backup directories, pacman's cache and if the packages are not available, it tries to fetch the missing
dependencies from the Arch Rollback Machine site (http://arm.kh.nu).
r66: * minor fixes
r68: * some bugfixes
* "--repoadd" and "--Reporemove" now accurately removes old packages from LocalRepository
r69: * small bugfixes when listing packages with similar names
* curl retries now 5 times if connection is not established
r75: * "--cachecopy" does not try to dl sourcefiles when backing up ABS PKGBUILDs
* some work on package splitting
* further internal changes
r76: * minor mistakes with "ln" purged
r79: * mostly small changes
* "--cleanup" now also removes uninstalled packages from LocalRepository
r81 & r80: * added AUR v1.6.0 support (use more json)
* small ARM changes ("--rollback")
r85:
* pkgman supports pkg.tar.xz packages
* some code rewrite, bugs purged (hopefully)
r113:
* pkgman now supports building split packages through makepkg.
If you already use pkgman you need to rerun "pkgman --runmefirst" after updating.
* new "-t,--template" option ("pkgman <packagename> --template <alt. packagename> [--pkgbuildversion <version>] [options]").
Useful to create a new PKGBUILD and use an existing one as a template.
* new option: "--conf /path/to/alternate/conf/file" - Specify another configuration file.
* pkgman now uses ${XDG_CONFIG_HOME}/pkgman or $HOME/.config/pkgman - if first not set - as the default location for its conf files.
r116:
* check inet conection when submitting src tarballs to AUR
* some bugs
* updated manpage on sf
For further details please read the manual page.
Last edited by DonVla (2010-04-28 11:56:59)

I'm having some troubles with it (perhaps missing dependencies, and forgotten hardcoded dirs?):
jan@aconcagua 8:20PM ~ % pkgman --runmefirst
/usr/bin/pkgman: line 77: /home/jan/apps/skripte/archscripts/pkgman/share/pkgman/color.bash: No such file or directory
/usr/bin/pkgman: line 1293: initcolor: command not found
/usr/bin/pkgman: line 312: highlight: command not found
/usr/bin/pkgman: line 312: error: command not found
/usr/bin/pkgman: line 313: highlight: command not found
/usr/bin/pkgman: line 313: error: command not found
/usr/bin/pkgman: line 314: highlight: command not found
/usr/bin/pkgman: line 314: error: command not found
/usr/bin/pkgman: line 315: highlight: command not found
/usr/bin/pkgman: line 315: error: command not found
/usr/bin/pkgman: line 317: error: command not found
/usr/bin/pkgman: line 318: error: command not found
/usr/bin/pkgman: line 321: highlight: command not found
/usr/bin/pkgman: line 321: msg: command not found
/usr/bin/pkgman: line 329: list: command not found
/usr/bin/pkgman: line 332: list: command not found
/usr/bin/pkgman: line 332: list: command not found
touch: cannot touch `/bin/.pkgman.registered': Permission denied
/usr/bin/pkgman: line 332: list: command not found
/usr/bin/pkgman: line 332: list: command not found
/usr/bin/pkgman: line 332: list: command not found
/usr/bin/pkgman: line 332: list: command not found
/usr/bin/pkgman: line 332: list: command not found
/usr/bin/pkgman: line 337: msg: command not found
curl: option --output: requires parameter
curl: try 'curl --help' or 'curl --manual' for more information
^C/usr/bin/pkgman: line 209: cleanoutput: command not found
/usr/bin/pkgman: line 209: cleanoutput: command not found
(I terminated with ctrl-c).
EDIT: errors resolved by correcting the path $HOME/apps/skripte/archscripts/pkgman/share/pkgman to /usr/share/pkgman in the pkgman itself.
Last edited by bender02 (2008-05-23 01:28:58)

OS X and Arch dual-boot on MBP - bootloader error

I have a Macbook Pro 9,2, and I dual-boot OS X and Arch. My main Arch partition is encrypted with an LVM on LUKS setup, and my main OS X partition is encrypted with Firevault 2. I run the vanilla Arch kernel, and I use xfce as my DE. I use refind as my boot manager, and grub as the bootloader for the Arch partition. This setup has worked flawlessly for several months. I update my Arch system once per week, and last Sunday was a large update since xfce got a large overhaul (in terms of program and config files). However, since the update I cannot boot into OS X (I am posting this here instead of an OS X forum since no change occurred to the OS X system so the problem must be with a change to my Arch system).
When I attempt to boot into OS X, I am asked for my password to decrypt the partition, but then I get the following error message:
efiboot loaded from device: Acpi (PNP0A03,0)/Pci(1F12)/SATA(0,0)/HD(Part3.Sig698A
48BA-88E6-471C-9359-AD63C7EEBE74
boot file path: \System\Library\CoreServices\boot.efi
............Read error 0x6
Error loading kernel cache (0x6)
Error: Aborted returned from boot.efi
*Hit any key to continue*
Starting boot.efi
Using load options ''
efiboot loaded from device: Acpi (PNP0A03,0)/Pci(1F12)/SATA(0,0)/HD(Part3.Sig698A
48BA-88E6-471C-9359-AD63C7EEBE74
boot file path: \com.apple.recovery.boot\boot.efi
.............Read error 0x6
Error loading kernel cache (0x6)
Error: Aborted returned from boot.efi
*Hit any key to continue*
When I hit a key, I get taken back to the refind menu. If I choose OS X again, I get the same error. This cycle can be repeated ad nauseam. Booting into my Arch partition, on the other hand, works just fine, with one hiccup. While usability does not seem to be reduced, after I input my password to decrypt the Arch partition, and before I see the tty1 login, I (since Sunday) occasionally get the following error message that I have never had before:
19.636262] [drm:crypt_set_fifo_underrun_reporting] *ERROR* uncleared pch fifo underrun on pch transcoder
19.636264] [drm:crypt_serr_int_handler] *ERROR* PCH transcoder A FIFO underrun
19.331860] ata1.00: exception Emask 0x50 SAct 0x1100 SErr 0x280900 action 0x6 frozen
19.331927] ata1.00: irq_stat 0x08000000, interface fatal error
19.331974] ata1: SError: {UnrecovData HostInt 10B8B BadCRC }
19.332821] ata1.00: failed command: READ FPDMA QUEUED
19.332866] ata1.00: cmd 60/00:40:70:c1:01/01:00:24:00:00/40 tag 8 ncq 131072 in
19.332866] res 40/00:60:b0:55:2a/00:00:24:00:00/40 Emask 0x50 (ATA bus error)
19.332176] ata1.00: status: { DRDY }
The "READ FPDMA QUEUED" line and those below it repeat a few time with different numbers following "cmd" and "res," but then after a few moments the messages clear off the screen and I arrive at my tty1 login screen and from there everything in Arch (including my now-upgraded DE) works normally. This error does not occur during all boots, but I cannot discern any pattern behind when I see it and when I do not. The OS X error and failure to boot occurs every time I try to boot into OS X.
I have learned a lot as an Arch user, but this problem is beyond me. Google has not been particularly friendly, understandably so given the peculiarity of the problem and my setup. I have not yet tried undoing the update I did on Sunday because (a) it would be a pain since there were >30 packages that were upgraded, and (b) I have no evidence that the upgrade was actually causative of this issue, though I may eventually attempt the downgrade out of desperation if I cannot find a solution. Note that the update I keep referencing did not including a kernel update.
I appreciate any advice or insight that you can offer.

I don't have much in the way of a solution for your problem, but to start with, what were the > 30 packages? In particular, was grub/refind updated (or anything else that would likely touch your efi partition? I know from my own messing with refind, that you can potentially 'damage' your partition layout with certain commands which maybe causing osx not to boot...
Then again, the errors may have nothing to do with your arch installation and maybe indicative of a different problem all together. Normal procedure is at this point is to backup your complete disk (clone/mirror it, read up on how to do that especially with regards to the encryption systems used), and try to diagnose for any problems the mbp maybe having.
You could use an apple rescue cd (that may no longer be available with newer mbp , I have no idea..) or maybe use a different harddisk and install osx there and see if you can get everything running 'normally' thus ruling out any funky errors with the hw. check apple's recovery options if need be.
I guess you'll just have to fiddle about a bit and try to more closely determine what the actual problem is. and again, backup your stuff!

Question about some packages in arch

Hello
Where do I report/ask about packages in arch *like in AUR there is a comment section*
The reason is because well the package (sdl) didn't had PulseAudio support so I was wondering where to report it and KTorrents didn't bring any plug-ins with the package (plus I can't compile it since there is a phonon error I don't get)
sorry if this wasn't the section,
Thanks

alright, thanks fukawi2, wonder
well, i'm compiling them alright, but not ABS *need to read the wiki*
Last edited by akurashy (2009-08-16 15:30:33)

Info about the linux-firmware package and rt2780-usb-fw

Hello,
I have a have question about the linux-firmware package in the repo.
Recently there was an update for this package and when I checked its contents I saw that it also updates rt2870usb-fw.
Maybe I am a bit confused about the all kernel modules / firmware, but since I need to compile the latest kernel (linux-mainline from AUR) to get my buffalo wireless usb work(my rt2870 is supported from rc4), would it be possible to update only this package and use the kernel in the arch repo?
I can't test it myself because I am out of town for while.
Thank you

Hello,
I have a have question about the linux-firmware package in the repo.
Recently there was an update for this package and when I checked its contents I saw that it also updates rt2870usb-fw.
Maybe I am a bit confused about the all kernel modules / firmware, but since I need to compile the latest kernel (linux-mainline from AUR) to get my buffalo wireless usb work(my rt2870 is supported from rc4), would it be possible to update only this package and use the kernel in the arch repo?
I can't test it myself because I am out of town for while.
Thank you

How to handle outdated packages from repo by own hand ?

Hi
I would like to have packages that I use frequently to be fresh - for example - Krusader is 1.70.0 in arch but there is pretty stable beta - 1.80.0beta2 the same thing with gmpc/libmpd/qtcurve-kde3|gtk2 - these packages are outdated. My question is how to handle this in good way ? I mean make PKGBUILDs in /var/aur/local but what if package in repo will be updated ? I simply don't want to wait for these packages because I've chosed ARCH for no outdated packages but now I see there are some... Anyone have a good advice for me ? Now when I make my own PKGBUILDs of these packages with every pacman -Syu I get error: package-name is newer than package in [repo] bla bla bla

try one of the aur build script proggies, they compare the aur to the current in the repositories I think?
Have you tried putting the packages like krusader on the ignorepkg list in pacman.conf?

HT2476 new Mac mini, outdated iDVD and iMovie HD with OSX 10.8.2; fix ?

I have a brand new Mac mini and during set up I imported settings from a Macbook running 10.5.8; now the iDVD and iMovie HD apps are outdated and the settings do not allow updates to the current version compatible with OSX Mountain Lion 10.8.2;
How do I fix this?

In my case, the .dmg can only be installed if iLife 08 is installed, so I install iLife 08 (nothing works from that in ML, but it doesn't matter), then install the 6.04 .dmg, and then update the entire iLife with 09 and then 11, running software update in between. At that point, every app works. During that process, the new iMovie versions will be installed and automatically create a previous version folder for 6.04.
Right now I have a Powerbook G4.
I'll be purchasing a new iMac (Mountain Lion) in the coming months. I would like to put both iMovie HD6 and the last version of iDVD on it. I've read numerous threads on the iDVD installation. I'm trying to make sure I understand all the steps to getting both applications installed and working correctly.
I have the install disks for
iLife 08 (says it can install on both PPC and Intel Macs)
iLife 09 (with iDVD)
iLife 11 (older version with iDVD)
I certainly remember disliking iMovie 7 and therefore used the download from Apple to revert back to 6.0.4 on my Powerbook. I did a search and happened to find in my Library an installer package labeled iMovie HD6 (the file info says version 6.0.4 and it's dated Feb 2008). Is this what I would have used to go back to iMovie HD6 from iMovie 7? I also found a ton of other installer packages that I had no idea my powerbook must have automatically saved. Included were numerous iDVD 7 update installers.
So would I take these steps on the new iMac with Mountain Lion?
Use the iLife 08 disk to do a custom install of only iMovie (or does the 6.0.4 installer only work if you've installed the entire iLife 08?)
Run the installer package iMovieHD6 to revert from iMovie 7 to HD6
Use the iLife 09 disk to do a custom install of iDVD
Update iDVD by running the update packages and then using the iLife 11 disk to ensure I get all the themes available for iDVD
Run software update to bring everything up-to-date
I happened to do an install of only iDVD from iLife 11 (iDVD) on another IMac running Mountain Lion and found that I had no choice but to install iPhoto along with it. Since that was an older version I then had to do a reinstall of the current iPhoto from the App store.
Do these steps sound logical?

OpenVZ and Arch

i am in progress of migrating my servers from gentoo to arch. i am trying to build an openvz host os in arch, simply because its easier to maintain than gentoo and less needlessly complex IMO. this package:
http://aur.archlinux.org/packages.php?ID=23922
has been abandoned as of today, although i am building it as we speak anyway. this package:
http://aur.archlinux.org/packages.php?ID=15789
will not compile on either x64 or 686. is there no interest in this technology? should i be looking into other technology, such as LXC as the author of the first PKGBUILD has championed? we use XEN at work on many servers, and frankly, i find it to be overkill and/or lacking in many areas, especially since all the containers are lightweight services and exclusively linux. what are others doing in ther virtualization arena with arch linux? i would really like my host os to be arch, and would rather not compile/create an openvz kernel PKGBUILD from hand, or custom modify existing/abandoned ones.
what is the general consensus here? can we get an official openvz kernel into the repositories?

well after looking into dshauer's post here:
http://lxc.teegra.net/
cited in the post when orphaning the openvz packages, and after reading coutless other articles, i decided to go that route (LXC) as well; LXC seems to be a solid attempt to make openvz unecessary, and utilizes all the container stuff that has entered the kernel recently. i just needed to recompile the kernel26 abs package with these config vars enabled, as stated in dshauer's post:
CONFIG_GROUP_SCHED=y
CONFIG_FAIR_GROUP_SCHED=y
CONFIG_RT_GROUP_SCHED=y
CONFIG_CGROUP_SCHED=y
CONFIG_CGROUPS=y
CONFIG_CGROUP_NS=y
CONFIG_CGROUP_FREEZER=y
CONFIG_CGROUP_DEVICE=y
CONFIG_CPUSETS=y
CONFIG_PROC_PID_CPUSET=y
CONFIG_CGROUP_CPUACCT=y
CONFIG_RESOURCE_COUNTERS=y
CONFIG_CGROUP_MEM_RES_CTLR=y
CONFIG_CGROUP_MEM_RES_CTLR_SWAP=y
CONFIG_MM_OWNER=y
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
CONFIG_USER_NS=y
CONFIG_PID_NS=y
CONFIG_NET_NS=y
CONFIG_NET_CLS_CGROUP=y
CONFIG_SECURITY_FILE_CAPABILITIES=y
can these options be enabled by default in the standard kernel package? seem to just be namespace support for various things, and control groups for resource management.

SELinux and Arch

Hi there,
I'm trying to install and setup SELinux on my Arch box. (Because SELinux is topic of my bachelor research and Arch is my favourit distro)
So after reading Arch and Gentoo SELinux wikis I installed SELinux enabled kernel and other SELinux stuff, compiled and loaded Reference Policy and relabeled FS.
Now I can load SELinux and set it to enforcing mode, which seems to be working, though it needs some finetuning at next stage. Though to finish current research stage I need to load SELinux at boot. From what I read it is done by sysvinit patched for use with SELinux, which is also available in [comunity]. Problem is that patched sysvinit fails to load the policy and kernel panics. Acording to Gentoo wiki sysvinit needs to be linked to libselinux, mine from package community/selinux-sysvinit 2.86-1 seems not to be. :-/
Sooo, the question is, does it work for anybody? I guess if not, then there is something wrong with the package and some finetuning might solve that. Or maybe I'm doing something wrong, please help me to determine what.

karlo wrote:Hi, SELinux is also a topic of my research. I'm writing refpolicy editor and everything was fine till I wanted to compile refpolicy ( refpolicy-2.20091117 ) and set this policy as a default in Fedora12 (by the way, sources of default policy in Fedora are not public, are they? ). After following steps published on http://oss.tresys.com/projects/refpolic … eRefpolicy my system is not booting. Some daemons failed to run (eg. HAL). selinux=0 in grub helps but is not the solution. Selinux is set to run in permissive mode. Has someone any ideas what's wrong and how to fix it?
Hello,
this may be a little late, but have you tried to follow Arch Linux SELinux guide, here on wiki? Last time I tried it, it worked -- if you are doing your research at Arch Linux.
Fedora source can be found, they have src.rmp. The sources itself are normal refpolicy, but there are some huge patches. I wasn't able to compile that even on Fedora though.
As for SELinux at Arch I have gathered some requests and will be trying to make it better in the summer.

Debian Sid and Arch

Is it fair to compare Debian Sid and Arch, as they bother rolling releases?
If so, how come is Arch so much more stable than Debian Sid. seen as Arch has a handful of developers VS Debian with a over a thousand?
Or is that the answer itself?

From Wikipedia:
Software packages in development are either uploaded to the project branch named unstable, also known as sid, or the experimental branch. Software packages uploaded to unstable are normally versions stable enough to be released by the original upstream developer, but with the added Debian-specific packaging and other modifications introduced by Debian developers. These additions may be new and untested. Software not ready yet for the unstable branch is typically placed in the experimental branch.
So unless its in experimental repo, it is in unstable and if one wanted to use Debian nearer the edge then SID would be the way esp when Sarge was out for a few years and no Etch was in sight.
Yet Sid is very unstable from my few times I played with it
The main thing for me is Arch stays pretty up to date with such a few developers yet Debian cant with so many, just seems odd.
Then one needs to use Ubuntu that tries to tame Debian every 6 months, just odd that Debian could not do what Arch does with so few DEV's?
I think I may be missing the bigger picture of debian?
Last edited by habtool (2007-10-25 11:07:42)

Rubix - yet another distro based on Slackware and Arch Linux

Today I was reading DistroWatch and saw info about Rubix.
This distro is based on Slackware and Arch Linux.
What do you think about this?

I tried it.
I really liked the install. Very simple and straightforward.
I didn't like fact that the rubix installer installs only one package at a time (and pulls in the deps of course), so the install is rather slow.
I also didn't like the repo structure. Seems cumbersome.
bonuses:
e17 installed easy, and just worked.
packages available are pretty reasonable
I really like the modifications rubix has made to rc.conf and some of the inits
There is some type of community repository
The distro seems to have a clear focus, and I like many of the security aspects.
bummers:
extra rc<int>.d directories
No gdm. boo-hiss.
No gnome (I get it. this is slackware. boo-hiss).
My fonts looked ugly. This one is such a huge deal for me, that I consider it a showstopper. Might be the fact that I installed it in vmware, but most distros have little issue with this. <caveat. I think arch fonts suck too. I have never had good looking fonts in arch...which is why I have only really used it as a server.>
Did I mention I didn't like the repo structure? It made the simple act of updating pacman repos (pacman -Sy) slow and painful.

Palaver speech recognition app packaged for Arch

Palaver (formerly Ubuntu-Speech-Recognition), has been packaged for Arch:
https://aur.archlinux.org/packages/palaver-git/
The git repo is located here:
https://github.com/JamezQ/Palaver
A great video demo of what is possible can be found here:
http://www.techdrivein.com/2013/02/ubun … -demo.html
This is shaping up to be an interesting project, and as long as it keeps on a good development track, could become the Siri of Linux (don't laugh, it could!)
The current code is beta, and will be going through restructuring changes as it moves from git to launchpad, so expect a lot of changes in the near future.
The beta can actually do quite a lot at the moment, especially if you add your own dictionary (which is very easy to do BTW).
Oh, and just a warning regarding privacy, the application uses Googles speech recognition, and requires a network connection to work. Your voice command is recorded locally and deciphered on Google servers.......
Cheers.

Xyne wrote:
Padfoot wrote:Oh, and just a warning regarding privacy, the application uses Googles speech recognition, and requires a network connection to work. Your voice command is recorded locally and deciphered on Google servers........
Oh well. Aside from the privacy concerns* I am also disappointed that it is just a wrapper around a web service. A local speech recognition engine would be even more impressive.
Thanks for the privacy warning.
* Seriously, sending speech samples to Google so that they can store and analyse them is crazy to me. Do you really want to live in a future of interactive advertisements that can identify you by voice alone and associate it with everything else that you have ever done online? A conversation with a friend at a bus stop may one day trigger targeted ads that reveal things about you that you consider private. I do not understand how so many people can be completely ok with having their private lives catalogued for companies and governments just to get some non-essential services in return. Beyond that having such tools lying around when your government eventually becomes oppressive will ensure its longevity at everyone's expense. Open, democratic societies have an unpatched memory leak that requires a hard reboot every so often.
I completely understand, and while a local engine would be teriffic, the only one I can think of on Linux with any potential is sphinx. Unfortunately, (last time I checked) it's not in an easily useable state, yet. I should check out the pace of development on that project. Of course, I would be delighted to be proven wrong on this project.
And while this in no way is intended to dispell any privacy concerns, or justify any possible motives of the companies providing online deciphering, I am guessing this is exactly whar Siri does on Apple products. Also, as Palaver is currently targeting Ubuntu (while still being agnostic enough to easily work on any distro), It needs to have a small footprint considering the push at Ubuntu towards mobile devices. Unfortunately, mobile devices do not lend to local storage of the many samples in multiple languages required to perform the deciphering.
Cheers.
[EDIT] While Palaver is a wrapper around an online service, the wrapper is limited to sending the voice sample and getting a string of text back, the application performs the task of deciphering the meaning of the text and taking the appropriate action based on local dictionaries and plugins.[/EDIT]
Last edited by Padfoot (2013-03-23 22:21:13)

Outdated packages and arch-etiquette

Similar Messages

Maybe you are looking for