Thanks to Rolf Leggewie, Pastebinit 0.10 is now in Debian (unstable and testing) and has been synced in Intrepid.
I can now use the time I previously spent on packaging Pastebinit (not that much ...) to actually work on it and add new pastebins.
For those of you who don't know what Pastebinit is, here is the description taken from the Debian package :
pastebinit is a command-line tool to send data to a "pastebin": a web site which allows its users to upload snippets of text for public viewing.
It can receive data from a pipe or from a file passed as argument.
It supports these pastebins:
- http://*.pastebin.com
- http://pastebin.mozilla.org
- http://rafb.net
- http://yourpaste.net
- http://paste.ubuntu.com
- http://*.paste.f-box.org
- http://*.1t2.us
- http://paste.stgraber.org
It's a very useful tool on servers and I also use it a lot with thin clients to easily submit debugging informations.
Examples could be:
- pastebinit /etc/X11/xorg.conf
- ps aux | pastebinit -
- free | pastebinit -b http://paste.ubuntu.com -
Bugs can be reported on Launchpad
Since it's scheduled to be
Since it's scheduled to be available in Intrepid, any chance of it being made available in the hardy-backports?
I could compile it myself to be sure, but I'm one of those silly buggers that prefers precompiled packages whenever possible.
As it's a python script, you
As it's a python script, you don't need to recompile it to work on your computer.
You can simply download the package from Debian or Ubuntu and install it on Hardy. It'll work without any problem as nothing depends on a package version existing only in Intrepid and as it's not binary, it's not library-dependent either.
http://archive.ubuntu.com/ubuntu/pool/universe/p/pastebinit/pastebinit_0.10-1_all.deb
Paste2
It would be exceptional if it could support paste2 -- http://www.paste2.org :)
It's the fastest of them all.
Done in rev 45
Done in rev 45
rafb.net :D
So happy my patch got accepted - I can now use my pastebin of choice!
<3 Pastebinit
I have to say thanks for creating such a great tool. We get a lot of use out if it in #ubuntu, it makes asking for information so much easier.
Intrepid?
So after reading the article, i issue a `apt-cache search pastebin` in my ubuntu box to find that:
- There is a program called upstreamdev (with canoe-gnome and kayak-kde frontends) that writes log files to a pastebin server and/or a bugtracker
- Pida, the python IDE, supports pastebin
- Webboard, a mix of knotes with pastebin support for collaborative edition of sourcecode and debug that even has a gnome-panel integration
- pastebininit 0.9 is included in universe/misc (ie. lives in the universe repositories). If you a) use ubuntu b) do not want to compile and c) do not want to install intrepid/a intrepid package right now THEN use this package.
If I recall correctly at the
If I recall correctly at the time I started working on Pastebinit, the only existing one was webboard and it was a GUI tool. The goal of pastebinit is to have a comand line tool not depending on any GUI lib or package.
Pastebinit 0.9 is in Hardy's universe (I'm the one who uploaded it), I just wanted to say that 0.10 is now out (as I'm upstream) and that Debian is now handling the packaging. You don't need to compile a Python software (so b) doesn't apply) and as it doesn't contain any binary part you can install any pastebinit package without any problem.
pastebinit and terminal readouts
Hello,
I like using this for certain things , it is fast and convenient, however.. when we do support for compiz fusion we often need the terminal read out of certain commands...ex lspci | grep -i vga.
I cannot get this to go to pastebin. I know it must me my interpretation of the arguments.
i have tried lspci | grep -i vga | pastebinit
that ^^ gives me only a list of arguments
pastebinit lspci | grep -i vga gives me " cannot read from lspci.
Am i misunderstanding the functionality of pastebinit? is it strictly for reading only onboard text files... pa ax | grep compiz | pastebinit << works... or am I not understanding the arguments? :)
the latter seems more likely :)
coz
Hi, I have recently fixed
Hi,
I have recently fixed some problems with pipes, you should try the current version from bzr.
http://bazaar.launchpad.net/~pastebinit-developers/pastebinit/trunk
small bug on MAN
hi there.
If u wish i may report it on LP.
the pastebinit MAN page doenst show the -j option, while the cli help does.
Also i was unable to make that work.
Thanks so much for this nice tool.
Hi, feel free to report it on
Hi, feel free to report it on Launchpad so I don't forget about it next time I update the code.
auto-update from trunk
bu the way, whats the best way of auto-updating from trunk?
i just jumped from the 0.9 on my system to trunk, and would like to be it up to date.
would it be possible to have it on a PPA?
Easiest is just to get the
Easiest is just to get the pastebinit file from the bzr branch.
A PPA would of course be a possible way to provide updates but we usually tend to just upload a new release to Debian and Ubuntu when we consider the code stable. I don't like the idea to publish testing packages (as in code we know may break).
Support paste.debian.net
I'd like very much if it could support paste.debian.net
Hi
First, sorry for my bad English, I'm German^^
I really love this project, and would like to help, if there is any way to do so, you can mail me.
My favorite pastebin is http://cxg.de/ and because it wasn't added yet, i did it on my own
elif website == "http://cxg.de" :
params['page']="/index.py"
params['name']=user
params['description']=title
params['style']="pastie" #the color format, i like this one best
params['data']=content
params['lexer']="guess_lexer" #This is for auto guessing the lang, use "TextLexer" for plain text
params['file']=""
suggestions
sorry for my bad english, my native language is germany.
Is it possible to save my defaults (for instance, my favorite paste-site, my name) in a configuration file (maybe in ~/.pastebinit) to reduce the effort?
Regards, Andreas
I have found the
I have found the .pastebinit.xml, but i can't found it in the docs, only in the source. I think, it should be described in the docs, or?
Regards, Andreas
You are right, this should be
You are right, this should be documented. I'll think of doing so for the next release.
Thanks
Post new comment