[aur-general] old tarball recovery?
Feeling incredibly daft about this... I adjusted the PKGBUILD for a module i maintain and uploaded it straight away after buildng succesfully. It thus overwrote the old tarball which contained the PKGBUILD plus a patch and an install script. In a stroke of brilliance I then proceeded to delete my local build files and try the new PKGBUILD via yaourt.... Needless to say it doesn't work. This is about as stupid as it gets. I'm having photorec trying to recover the local files but I'm not particularly hopeful. Any chance of recovery on the server? The package is fsaa1655g. - Chochem
On Tue, Oct 14, 2008 at 6:29 PM, Mads Michelsen <chochem@gmail.com> wrote:
Feeling incredibly daft about this...
I adjusted the PKGBUILD for a module i maintain and uploaded it straight away after buildng succesfully. It thus overwrote the old tarball which contained the PKGBUILD plus a patch and an install script. In a stroke of brilliance I then proceeded to delete my local build files and try the new PKGBUILD via yaourt.... Needless to say it doesn't work. This is about as stupid as it gets. I'm having photorec trying to recover the local files but I'm not particularly hopeful. Any chance of recovery on the server? The package is fsaa1655g.
- Chochem
There are no backups or anything made of AUR packages and as soon as you upload a package the entire directory on the server gets blown away to make way for the new one. I don't think you have a very good chance of recovery outside of your own hard drive. -- Callan Barrett
On Tue, 14 Oct 2008 12:29:57 +0200 Mads Michelsen <chochem@gmail.com> wrote:
Feeling incredibly daft about this...
I adjusted the PKGBUILD for a module i maintain and uploaded it straight away after buildng succesfully. It thus overwrote the old tarball which contained the PKGBUILD plus a patch and an install script. In a stroke of brilliance I then proceeded to delete my local build files and try the new PKGBUILD via yaourt.... Needless to say it doesn't work. This is about as stupid as it gets. I'm having photorec trying to recover the local files but I'm not particularly hopeful. Any chance of recovery on the server? The package is fsaa1655g.
- Chochem
Uhm looks like I got lucky... Browsing through the trash can (I'm not proud) I found an old tarball from god knows where. Here's to not taking the trash out :) Problem solved.
On Tue, Oct 14, 2008 at 1:02 PM, Mads Michelsen <chochem@gmail.com> wrote:
On Tue, 14 Oct 2008 12:29:57 +0200 Mads Michelsen <chochem@gmail.com> wrote:
Feeling incredibly daft about this...
I adjusted the PKGBUILD for a module i maintain and uploaded it straight away after buildng succesfully. It thus overwrote the old tarball which contained the PKGBUILD plus a patch and an install script. In a stroke of brilliance I then proceeded to delete my local build files and try the new PKGBUILD via yaourt.... Needless to say it doesn't work. This is about as stupid as it gets. I'm having photorec trying to recover the local files but I'm not particularly hopeful. Any chance of recovery on the server? The package is fsaa1655g.
- Chochem
Uhm looks like I got lucky... Browsing through the trash can (I'm not proud) I found an old tarball from god knows where. Here's to not taking the trash out :) Problem solved.
next time you can also try for example google cache. in the google search bar type 'cache:http://aur.archlinux.org/packages/fsaa1655g/fsaa1655g/' to see which files were there, and to view for example the PKGBUILD in cache you type 'cache:http://aur.archlinux.org/packages/fsaa1655g/fsaa1655g/PKGBUILD' in the google search bar. Ronald
participants (3)
-
Callan Barrett
-
Mads Michelsen
-
Ronald van Haren