Please test: pkgutils-0.1.5-4

[Neal ManBear]

We can leave the name as-is for now.     

[KernelKarter]

Updated SRPM is here: http://db.tt/WaXOYKIY

-- Eddie

[Neal ManBear]

I will look at it later, Eddie.     

[KernelKarter]

I've encountered a problem/possible bug:

If I right-click on a .tar.gz archive in Dolphin and then select "Re-compress as tar.xz", it works but the re-compressed archive has an extension of .tar.xz.arkWriting. Just a simple matter then of removing .arkWriting from the end of the archive name. I can reproduce this by executing /usr/bin/recompress_to_tarxz <name_of_archive_to_recompress> in a terminal. I've had a look at the script but I'm lost and would appreciate a bit of help with this, thanks.

-- Eddie

[Archie]

I've encountered a problem/possible bug:

If I right-click on a .tar.gz archive in Dolphin and then select "Re-compress as tar.xz", it works but the re-compressed archive has an extension of .tar.xz.arkWriting. Just a simple matter then of removing .arkWriting from the end of the archive name. I can reproduce this by executing /usr/bin/recompress_to_tarxz <name_of_archive_to_recompress> in a terminal. I've had a look at the script but I'm lost and would appreciate a bit of help with this, thanks.

-- Eddie

Eddie, that could be tar -cJf in action and you should Reload the Dolphin window before removing any trailing arkWriting. arkWriting simply means that the command had not been completed. Changing the name of the temporary file .tar.xz.arkWriting may corrupt the final tar.xz file.

It happens ... so leave it to do what it does and if you suspect that the archiving process is complete, do a Reload. If the filename is still the same with the trailing arkWriting open SystemMonitor (press Ctrl+Esc) and check.

If nothing else happens, delete the file with the trailing arkWriting and try again. Do not rename it. This can be a cause for failures in packages.

Other than that, if you need to understand the script, it is best to wait for the author, travisN000 to reply but I think he's on some reconstruction project.

UTSL,
Archie

[Neal ManBear]

KernelKarter,     
The larger the archive, the longer it will take to recompress. I have waited for quite a while for this to be completed. (I didn't time it. LOL) Patience is the trick.      

[Archie]

pkgutils is such a small app and I suspect that the Dolphin window did not auto-refresh, or ...

[KernelKarter]

I've encountered a problem/possible bug:

If I right-click on a .tar.gz archive in Dolphin and then select "Re-compress as tar.xz", it works but the re-compressed archive has an extension of .tar.xz.arkWriting. Just a simple matter then of removing .arkWriting from the end of the archive name. I can reproduce this by executing /usr/bin/recompress_to_tarxz <name_of_archive_to_recompress> in a terminal. I've had a look at the script but I'm lost and would appreciate a bit of help with this, thanks.

-- Eddie

Eddie, that could be tar -cJf in action and you should Reload the Dolphin window before removing any trailing arkWriting. arkWriting simply means that the command had not been completed. Changing the name of the temporary file .tar.xz.arkWriting may corrupt the final tar.xz file.

It happens ... so leave it to do what it does and if you suspect that the archiving process is complete, do a Reload. If the filename is still the same with the trailing arkWriting open SystemMonitor (press Ctrl+Esc) and check.

If nothing else happens, delete the file with the trailing arkWriting and try again. Do not rename it. This can be a cause for failures in packages.

Other than that, if you need to understand the script, it is best to wait for the author, travisN000 to reply but I think he's on some reconstruction project.

UTSL,
Archie

I can see that the process completes because when I execute the script from a terminal, I get dropped back to the command prompt. Just to be certain, the script is not listed in SystemMonitor, neither is ark and neither is tar.

OK, I've tried it again and again and again with Dolphin's right-click menu and in a terminal on a couple of different .tar.gz archives (491K and 2054K) and the process definitely completes but the .arkWriting extension never gets removed.

-- Eddie

[Neal ManBear]

Exit/quit dolphin. Wait for just a bit. Start dolphin.     

[Archie]

After restarting Dolphin and the filename is is still with the trailing arkWriting, ls on Konsole and if that is really what it comes to then I can only think that something in the script is broken.

It would be best you do a diff with the previous version so you can check what changed.

[KernelKarter]

Well, gentlemen, I've solved it but I cannot figure out what's going on here:

I was re-compressing the archives on a NTFS partition (one that I share with Windows). As soon as I tried it on a ext4 partition, everything worked as it should. I don't know whether to feel elated, embarassed or just disappear down a hole 

-- Eddie

[Neal ManBear]

  ntfs is a windows file system. Please do not try to package or any other related work on any windows file system. Use ext4 or ext3 for your packaging work.     

[Archie]

Well, gentlemen, I've solved it but I cannot figure out what's going on here:

I was re-compressing the archives on a NTFS partition (one that I share with Windows). As soon as I tried it on a ext4 partition, everything worked as it should. I don't know whether to feel elated, embarassed or just disappear down a hole  

-- Eddie

Don't worry about it, Eddie. We've all gone gone that road. Most important now is to get experience.

A good packager always test his packages himself. When he's confident that it is good and has no issues, he may ask for further test. This way you develop a good reputation. Now, not all packages that you tested and proved to be good on your system will be true for others. This is where the real challenge of trouble shooting begins and this is where our group can get involved.

To be perfectly honest with you, Eddie ... and I hope you don't mind this little bit of "classy" teaching ... I've also repackaged pkgutils because the KDE scripts don't work for me on this big task we have at the moment. So, what I have is pkgutils-0.1.6-3 ... and since this package is maintained by a friend, travisN000, I would tell him what changed and leave it to him to update.

Of course, when a package is in need of an update and the maintainer is kinda slow on the rebound, be my guess ... update it. After all, these are for our community's benefit, and not for some sort of personal glory.

Peace and much respect,
Archie

[KernelKarter]

Well, gentlemen, I've solved it but I cannot figure out what's going on here:

I was re-compressing the archives on a NTFS partition (one that I share with Windows). As soon as I tried it on a ext4 partition, everything worked as it should. I don't know whether to feel elated, embarassed or just disappear down a hole  

-- Eddie

Don't worry about it, Eddie. We've all gone gone that road. Most important now is to get experience.

I'm learning fast 

A good packager always test his packages himself. When he's confident that it is good and has no issues, he may ask for further test. This way you develop a good reputation. Now, not all packages that you tested and proved to be good on your system will be true for others. This is where the real challenge of trouble shooting begins and this is where our group can get involved.

Yes, understood.

To be perfectly honest with you, Eddie ... and I hope you don't mind this little bit of "classy" teaching ... I've also repackaged pkgutils because the KDE scripts don't work for me on this big task we have at the moment. So, what I have is pkgutils-0.1.6-3 ... and since this package is maintained by a friend, travisN000, I would tell him what changed and leave it to him to update.

So in other words, inform the packager of your changes and leave it up to them to update the package but use your own "personal" package until the "official" package appears in the repos.

Of course, when a package is in need of an update and the maintainer is kinda slow on the rebound, be my guess ... update it. After all, these are for our community's benefit, and not for some sort of personal glory.

This is the bit that's causing me a bit of concern because I made a couple of observations here and then followed the instructions I was given and look what's happened 

-- Eddie

[Archie]

Of course, when a package is in need of an update and the maintainer is kinda slow on the rebound, be my guess ... update it. After all, these are for our community's benefit, and not for some sort of personal glory.

This is the bit that's causing me a bit of concern because I made a couple of observations here and then followed the instructions I was given and look what's happened 

Let me try an explain this in the best way that I can.

You've packaged the tool and it works for you. That's a good thing.

You've posted a link so it can be tested. Neal said, he'll look at it later.

Neal has a pretty good idea of what other packagers (at least the ones that are helping at the moment) are doing ... and we are really quite busy.

You see, the package you updated is not a priority at the moment, which is why Neal will look at it later.

Other users learning to package may download your update and take a look (Open Source advantage over Proprietary) ... maybe some have some other enhancements to add ... maybe add a better GUI.

By the time our present lead dev gets to it at its state, it might change ... changelog. There can be several changes made by different people and everything should be added on the changelog unless of course one rather not add their names.

In the end it is really up to the maintainer to add a text file CREDITS or CHANGES ... sometimes we forget. ... why am I thinking of AS?? 

Now, Eddie, I'm sure you'll understand that it takes more than one acceptable package to join the ranks. But if you are persistent and keep coming up with good packages and updates, who knows?

I hope all this makes good sense to you because I surely do not want to repeat myself again.

Peace and much respect,
Archie