Sponsored Content
Operating Systems Linux Debian Upgrading Ubuntu Server (10.04) using do-release-upgrade Post 302913302 by rbatte1 on Friday 15th of August 2014 06:43:12 AM
Old 08-15-2014
What errors are you getting? Are they just a space issue, because an upgrade will not help in this case or various others.

Please show us what you do to generate an error & the error message and we can consider what is really going on. Please paste code, input & output/errors in CODE tags.




Thanks, in advance,
Robin
 

6 More Discussions You Might Find Interesting

1. Ubuntu

upgrading from ubuntu 710 gusty to the new release from synaptic ?

i notice when i was in the synaptic manage the other day that the new release KDE 4 was there can i upgrade from synaptic or do i need to download the files from a different source? currently running kubuntu 7.10 gusty and haven't seened any kind of updates come through that gave me the option to... (1 Reply)
Discussion started by: ksnovice
1 Replies

2. Ubuntu

Ubuntu upgrade

ive been using Ubuntu 7.10 for about 3 weeks now and i love it more than any other linux operating system. ive been watching the countdown to the upgrade of ubuntu 8.04. has any one tried out the 8.04 beta at all. if so, did u think it is worth upgrading my box to 8.04 or should i keep it at... (13 Replies)
Discussion started by: Texasone
13 Replies

3. Ubuntu

Problems after upgrade to ubuntu 11.04

We had Ubuntu Server 10.10, after upgrade to Ubuntu Server 11.04 some applications doesn't works by example "Printing" on "Sysmte- Administration" and User Administration GUI, how can I fix it? (2 Replies)
Discussion started by: dmejias
2 Replies

4. UNIX for Dummies Questions & Answers

terminator shell not working after upgrading ubuntu linux

Terminator is a program that allows users to set up flexible arrangements of GNOME terminals. It has stopped working for me after upgrading to ubuntu 11.10. it does not give prompt to type anything. Just stuck with /bin/bash in the title. I removed and installed again, same... (2 Replies)
Discussion started by: analyst
2 Replies

5. Ubuntu

Upgrade a package on Ubuntu

Hi, I want to upgrade a package to a specified version on Ubuntu, can you please shed some light? I know we can do it with but jere i want to upgrade the package to a specified version. Can someone please assist? Thanks (1 Reply)
Discussion started by: prash358
1 Replies

6. Ubuntu

Ubuntu 16.04 - upgrade to ZFS 0.7?

What is the recommended way to upgrade ZFS on Ubuntu 16.04? i have read this thread, but the PPA is not safe? Ubuntu 16.04, ZFS 0.7.3 anyone got it running? : zfs (7 Replies)
Discussion started by: kebabbert
7 Replies
GIT-SHOW-REF(1) 						    Git Manual							   GIT-SHOW-REF(1)

NAME
git-show-ref - List references in a local repository SYNOPSIS
git show-ref [-q|--quiet] [--verify] [--head] [-d|--dereference] [-s|--hash[=<n>]] [--abbrev[=<n>]] [--tags] [--heads] [--] [<pattern>...] git show-ref --exclude-existing[=<pattern>] < ref-list DESCRIPTION
Displays references available in a local repository along with the associated commit IDs. Results can be filtered using a pattern and tags can be dereferenced into object IDs. Additionally, it can be used to test whether a particular ref exists. The --exclude-existing form is a filter that does the inverse, it shows the refs from stdin that don't exist in the local repository. Use of this utility is encouraged in favor of directly accessing files under the .git directory. OPTIONS
--head Show the HEAD reference. --tags, --heads Limit to only "refs/heads" and "refs/tags", respectively. These options are not mutually exclusive; when given both, references stored in "refs/heads" and "refs/tags" are displayed. -d, --dereference Dereference tags into object IDs as well. They will be shown with "^{}" appended. -s, --hash[=<n>] Only show the SHA-1 hash, not the reference name. When combined with --dereference the dereferenced tag will still be shown after the SHA-1. --verify Enable stricter reference checking by requiring an exact ref path. Aside from returning an error code of 1, it will also print an error message if --quiet was not specified. --abbrev[=<n>] Abbreviate the object name. When using --hash, you do not have to say --hash --abbrev; --hash=n would do. -q, --quiet Do not print any results to stdout. When combined with --verify this can be used to silently check if a reference exists. --exclude-existing[=<pattern>] Make git show-ref act as a filter that reads refs from stdin of the form "^(?:<anything>s)?<refname>(?:^{})?$" and performs the following actions on each: (1) strip "^{}" at the end of line if any; (2) ignore if pattern is provided and does not head-match refname; (3) warn if refname is not a well-formed refname and skip; (4) ignore if refname is a ref that exists in the local repository; (5) otherwise output the line. <pattern>... Show references matching one or more patterns. Patterns are matched from the end of the full name, and only complete parts are matched, e.g. master matches refs/heads/master, refs/remotes/origin/master, refs/tags/jedi/master but not refs/heads/mymaster nor refs/remotes/master/jedi. OUTPUT
The output is in the format: <SHA-1 ID> <space> <reference name>. $ git show-ref --head --dereference 832e76a9899f560a90ffd62ae2ce83bbeff58f54 HEAD 832e76a9899f560a90ffd62ae2ce83bbeff58f54 refs/heads/master 832e76a9899f560a90ffd62ae2ce83bbeff58f54 refs/heads/origin 3521017556c5de4159da4615a39fa4d5d2c279b5 refs/tags/v0.99.9c 6ddc0964034342519a87fe013781abf31c6db6ad refs/tags/v0.99.9c^{} 055e4ae3ae6eb344cbabf2a5256a49ea66040131 refs/tags/v1.0rc4 423325a2d24638ddcc82ce47be5e40be550f4507 refs/tags/v1.0rc4^{} ... When using --hash (and not --dereference) the output format is: <SHA-1 ID> $ git show-ref --heads --hash 2e3ba0114a1f52b47df29743d6915d056be13278 185008ae97960c8d551adcd9e23565194651b5d1 03adf42c988195b50e1a1935ba5fcbc39b2b029b ... EXAMPLE
To show all references called "master", whether tags or heads or anything else, and regardless of how deep in the reference naming hierarchy they are, use: git show-ref master This will show "refs/heads/master" but also "refs/remote/other-repo/master", if such references exists. When using the --verify flag, the command requires an exact path: git show-ref --verify refs/heads/master will only match the exact branch called "master". If nothing matches, git show-ref will return an error code of 1, and in the case of verification, it will show an error message. For scripting, you can ask it to be quiet with the "--quiet" flag, which allows you to do things like git show-ref --quiet --verify -- "refs/heads/$headname" || echo "$headname is not a valid branch" to check whether a particular branch exists or not (notice how we don't actually want to show any results, and we want to use the full refname for it in order to not trigger the problem with ambiguous partial matches). To show only tags, or only proper branch heads, use "--tags" and/or "--heads" respectively (using both means that it shows tags and heads, but not other random references under the refs/ subdirectory). To do automatic tag object dereferencing, use the "-d" or "--dereference" flag, so you can do git show-ref --tags --dereference to get a listing of all tags together with what they dereference. FILES
.git/refs/*, .git/packed-refs SEE ALSO
git-ls-remote(1), git-update-ref(1), gitrepository-layout(5) GIT
Part of the git(1) suite Git 1.8.3.1 06/10/2014 GIT-SHOW-REF(1)
All times are GMT -4. The time now is 11:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy