Compare two repos - a table of all all package versions?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I'd like to see and compare versions of all packages in two different repos.
Something like:
libfoo | 1.2 | 1.3
libbar | 2.4 | 3.0
libbaz | ... | ...
Is there some such web?
Or a way to obtain list of all package versions in a repo, so I could compare myself by a script?
The use case is to be able to know what versions will change after system upgrade.
package-management upgrade repository versions
add a comment |
I'd like to see and compare versions of all packages in two different repos.
Something like:
libfoo | 1.2 | 1.3
libbar | 2.4 | 3.0
libbaz | ... | ...
Is there some such web?
Or a way to obtain list of all package versions in a repo, so I could compare myself by a script?
The use case is to be able to know what versions will change after system upgrade.
package-management upgrade repository versions
By definition, all packages will be upgraded after a release upgrade. You probably don't want to check all of them.
– fkraiem
Sep 16 '14 at 13:17
add a comment |
I'd like to see and compare versions of all packages in two different repos.
Something like:
libfoo | 1.2 | 1.3
libbar | 2.4 | 3.0
libbaz | ... | ...
Is there some such web?
Or a way to obtain list of all package versions in a repo, so I could compare myself by a script?
The use case is to be able to know what versions will change after system upgrade.
package-management upgrade repository versions
I'd like to see and compare versions of all packages in two different repos.
Something like:
libfoo | 1.2 | 1.3
libbar | 2.4 | 3.0
libbaz | ... | ...
Is there some such web?
Or a way to obtain list of all package versions in a repo, so I could compare myself by a script?
The use case is to be able to know what versions will change after system upgrade.
package-management upgrade repository versions
package-management upgrade repository versions
edited Mar 24 at 8:49
Sergiy Kolodyazhnyy
75.1k9155327
75.1k9155327
asked Sep 16 '14 at 13:00
Ondra ŽižkaOndra Žižka
93711329
93711329
By definition, all packages will be upgraded after a release upgrade. You probably don't want to check all of them.
– fkraiem
Sep 16 '14 at 13:17
add a comment |
By definition, all packages will be upgraded after a release upgrade. You probably don't want to check all of them.
– fkraiem
Sep 16 '14 at 13:17
By definition, all packages will be upgraded after a release upgrade. You probably don't want to check all of them.
– fkraiem
Sep 16 '14 at 13:17
By definition, all packages will be upgraded after a release upgrade. You probably don't want to check all of them.
– fkraiem
Sep 16 '14 at 13:17
add a comment |
3 Answers
3
active
oldest
votes
Use the tool rmadison for one package version information in different distributions
(well then different repositories)
sudo apt-get install devscriptsrmadison [the package name]
For example,
$ rmadison alsa-utils
and the output looks like [package version distro arch]:
alsa-utils | 1.0.25-1ubuntu5 | precise | source, amd64, armel, armhf, i386, powerpc
alsa-utils | 1.0.25-1ubuntu5.2 | precise-updates | source, amd64, armel, armhf, i386, powerpc
alsa-utils | 1.0.27.2-1ubuntu2 | trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el
alsa-utils | 1.0.28-1ubuntu2 | vivid | source, amd64, arm64, armhf, i386, powerpc, ppc64el
alsa-utils | 1.0.29-0ubuntu1 | wily | source, amd64, arm64, armhf, i386, powerpc, ppc64el
Or you could go to this website to see the lists
http://packages.ubuntu.com/
add a comment |
You can visit Ubuntuupdates as follows:
Search according to packages:

Then click Package Search (you will find differnt versions in page such as shown below):

You can also find possible matches of package name according to version and then click anyone to know more details!

Here package names are only used as example. Hope this helps to find appropriate package-name + PPA according to Ubuntu-release.
add a comment |
For two different repositories, you can compare the Packages files. This file is specific to the release channel (trusty, trusty-updates, etc.), the component (main, multiverse, etc.) and the type of the packages (binary-amd64, source, etc.).
Typically you can locate the file at:
/ubuntu/dists/$CHANNEL/$COMPONENT/binary-$ARCH/Packages{,.gz,.bz2,.xz}
relative to the root of most official mirrors.
An example would be http://mirror.cse.iitk.ac.in/ubuntu/dists/precise/main/binary-amd64/Packages.gz
You can fetch the Packages files you're interested in (uncompress if necessary), grep for Package and Version, then diff the output.
A sample code:
curl -s http://mirror.cse.iitk.ac.in/ubuntu/dists/trusty/main/binary-amd64/Packages.gz | gunzip | grep -E '^(Package|Version)' | awk 'ORS=NR%2?FS:RS {print $2}' > repo-a.txt
curl -s ftp://ftp.iitb.ac.in/distributions/ubuntu/archives/dists/trusty/main/binary-amd64/Packages.gz | gunzip | grep -E '^(Package|Version)' | awk 'ORS=NR%2?FS:RS {print $2}' > repo-b.txt
diff repo-a.txt repo-b.txt
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f524709%2fcompare-two-repos-a-table-of-all-all-package-versions%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
Use the tool rmadison for one package version information in different distributions
(well then different repositories)
sudo apt-get install devscriptsrmadison [the package name]
For example,
$ rmadison alsa-utils
and the output looks like [package version distro arch]:
alsa-utils | 1.0.25-1ubuntu5 | precise | source, amd64, armel, armhf, i386, powerpc
alsa-utils | 1.0.25-1ubuntu5.2 | precise-updates | source, amd64, armel, armhf, i386, powerpc
alsa-utils | 1.0.27.2-1ubuntu2 | trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el
alsa-utils | 1.0.28-1ubuntu2 | vivid | source, amd64, arm64, armhf, i386, powerpc, ppc64el
alsa-utils | 1.0.29-0ubuntu1 | wily | source, amd64, arm64, armhf, i386, powerpc, ppc64el
Or you could go to this website to see the lists
http://packages.ubuntu.com/
add a comment |
Use the tool rmadison for one package version information in different distributions
(well then different repositories)
sudo apt-get install devscriptsrmadison [the package name]
For example,
$ rmadison alsa-utils
and the output looks like [package version distro arch]:
alsa-utils | 1.0.25-1ubuntu5 | precise | source, amd64, armel, armhf, i386, powerpc
alsa-utils | 1.0.25-1ubuntu5.2 | precise-updates | source, amd64, armel, armhf, i386, powerpc
alsa-utils | 1.0.27.2-1ubuntu2 | trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el
alsa-utils | 1.0.28-1ubuntu2 | vivid | source, amd64, arm64, armhf, i386, powerpc, ppc64el
alsa-utils | 1.0.29-0ubuntu1 | wily | source, amd64, arm64, armhf, i386, powerpc, ppc64el
Or you could go to this website to see the lists
http://packages.ubuntu.com/
add a comment |
Use the tool rmadison for one package version information in different distributions
(well then different repositories)
sudo apt-get install devscriptsrmadison [the package name]
For example,
$ rmadison alsa-utils
and the output looks like [package version distro arch]:
alsa-utils | 1.0.25-1ubuntu5 | precise | source, amd64, armel, armhf, i386, powerpc
alsa-utils | 1.0.25-1ubuntu5.2 | precise-updates | source, amd64, armel, armhf, i386, powerpc
alsa-utils | 1.0.27.2-1ubuntu2 | trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el
alsa-utils | 1.0.28-1ubuntu2 | vivid | source, amd64, arm64, armhf, i386, powerpc, ppc64el
alsa-utils | 1.0.29-0ubuntu1 | wily | source, amd64, arm64, armhf, i386, powerpc, ppc64el
Or you could go to this website to see the lists
http://packages.ubuntu.com/
Use the tool rmadison for one package version information in different distributions
(well then different repositories)
sudo apt-get install devscriptsrmadison [the package name]
For example,
$ rmadison alsa-utils
and the output looks like [package version distro arch]:
alsa-utils | 1.0.25-1ubuntu5 | precise | source, amd64, armel, armhf, i386, powerpc
alsa-utils | 1.0.25-1ubuntu5.2 | precise-updates | source, amd64, armel, armhf, i386, powerpc
alsa-utils | 1.0.27.2-1ubuntu2 | trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el
alsa-utils | 1.0.28-1ubuntu2 | vivid | source, amd64, arm64, armhf, i386, powerpc, ppc64el
alsa-utils | 1.0.29-0ubuntu1 | wily | source, amd64, arm64, armhf, i386, powerpc, ppc64el
Or you could go to this website to see the lists
http://packages.ubuntu.com/
edited Aug 13 '15 at 10:17
answered Sep 16 '14 at 13:18
tai271828tai271828
67246
67246
add a comment |
add a comment |
You can visit Ubuntuupdates as follows:
Search according to packages:

Then click Package Search (you will find differnt versions in page such as shown below):

You can also find possible matches of package name according to version and then click anyone to know more details!

Here package names are only used as example. Hope this helps to find appropriate package-name + PPA according to Ubuntu-release.
add a comment |
You can visit Ubuntuupdates as follows:
Search according to packages:

Then click Package Search (you will find differnt versions in page such as shown below):

You can also find possible matches of package name according to version and then click anyone to know more details!

Here package names are only used as example. Hope this helps to find appropriate package-name + PPA according to Ubuntu-release.
add a comment |
You can visit Ubuntuupdates as follows:
Search according to packages:

Then click Package Search (you will find differnt versions in page such as shown below):

You can also find possible matches of package name according to version and then click anyone to know more details!

Here package names are only used as example. Hope this helps to find appropriate package-name + PPA according to Ubuntu-release.
You can visit Ubuntuupdates as follows:
Search according to packages:

Then click Package Search (you will find differnt versions in page such as shown below):

You can also find possible matches of package name according to version and then click anyone to know more details!

Here package names are only used as example. Hope this helps to find appropriate package-name + PPA according to Ubuntu-release.
answered Sep 16 '14 at 13:43
PandyaPandya
20.6k2897157
20.6k2897157
add a comment |
add a comment |
For two different repositories, you can compare the Packages files. This file is specific to the release channel (trusty, trusty-updates, etc.), the component (main, multiverse, etc.) and the type of the packages (binary-amd64, source, etc.).
Typically you can locate the file at:
/ubuntu/dists/$CHANNEL/$COMPONENT/binary-$ARCH/Packages{,.gz,.bz2,.xz}
relative to the root of most official mirrors.
An example would be http://mirror.cse.iitk.ac.in/ubuntu/dists/precise/main/binary-amd64/Packages.gz
You can fetch the Packages files you're interested in (uncompress if necessary), grep for Package and Version, then diff the output.
A sample code:
curl -s http://mirror.cse.iitk.ac.in/ubuntu/dists/trusty/main/binary-amd64/Packages.gz | gunzip | grep -E '^(Package|Version)' | awk 'ORS=NR%2?FS:RS {print $2}' > repo-a.txt
curl -s ftp://ftp.iitb.ac.in/distributions/ubuntu/archives/dists/trusty/main/binary-amd64/Packages.gz | gunzip | grep -E '^(Package|Version)' | awk 'ORS=NR%2?FS:RS {print $2}' > repo-b.txt
diff repo-a.txt repo-b.txt
add a comment |
For two different repositories, you can compare the Packages files. This file is specific to the release channel (trusty, trusty-updates, etc.), the component (main, multiverse, etc.) and the type of the packages (binary-amd64, source, etc.).
Typically you can locate the file at:
/ubuntu/dists/$CHANNEL/$COMPONENT/binary-$ARCH/Packages{,.gz,.bz2,.xz}
relative to the root of most official mirrors.
An example would be http://mirror.cse.iitk.ac.in/ubuntu/dists/precise/main/binary-amd64/Packages.gz
You can fetch the Packages files you're interested in (uncompress if necessary), grep for Package and Version, then diff the output.
A sample code:
curl -s http://mirror.cse.iitk.ac.in/ubuntu/dists/trusty/main/binary-amd64/Packages.gz | gunzip | grep -E '^(Package|Version)' | awk 'ORS=NR%2?FS:RS {print $2}' > repo-a.txt
curl -s ftp://ftp.iitb.ac.in/distributions/ubuntu/archives/dists/trusty/main/binary-amd64/Packages.gz | gunzip | grep -E '^(Package|Version)' | awk 'ORS=NR%2?FS:RS {print $2}' > repo-b.txt
diff repo-a.txt repo-b.txt
add a comment |
For two different repositories, you can compare the Packages files. This file is specific to the release channel (trusty, trusty-updates, etc.), the component (main, multiverse, etc.) and the type of the packages (binary-amd64, source, etc.).
Typically you can locate the file at:
/ubuntu/dists/$CHANNEL/$COMPONENT/binary-$ARCH/Packages{,.gz,.bz2,.xz}
relative to the root of most official mirrors.
An example would be http://mirror.cse.iitk.ac.in/ubuntu/dists/precise/main/binary-amd64/Packages.gz
You can fetch the Packages files you're interested in (uncompress if necessary), grep for Package and Version, then diff the output.
A sample code:
curl -s http://mirror.cse.iitk.ac.in/ubuntu/dists/trusty/main/binary-amd64/Packages.gz | gunzip | grep -E '^(Package|Version)' | awk 'ORS=NR%2?FS:RS {print $2}' > repo-a.txt
curl -s ftp://ftp.iitb.ac.in/distributions/ubuntu/archives/dists/trusty/main/binary-amd64/Packages.gz | gunzip | grep -E '^(Package|Version)' | awk 'ORS=NR%2?FS:RS {print $2}' > repo-b.txt
diff repo-a.txt repo-b.txt
For two different repositories, you can compare the Packages files. This file is specific to the release channel (trusty, trusty-updates, etc.), the component (main, multiverse, etc.) and the type of the packages (binary-amd64, source, etc.).
Typically you can locate the file at:
/ubuntu/dists/$CHANNEL/$COMPONENT/binary-$ARCH/Packages{,.gz,.bz2,.xz}
relative to the root of most official mirrors.
An example would be http://mirror.cse.iitk.ac.in/ubuntu/dists/precise/main/binary-amd64/Packages.gz
You can fetch the Packages files you're interested in (uncompress if necessary), grep for Package and Version, then diff the output.
A sample code:
curl -s http://mirror.cse.iitk.ac.in/ubuntu/dists/trusty/main/binary-amd64/Packages.gz | gunzip | grep -E '^(Package|Version)' | awk 'ORS=NR%2?FS:RS {print $2}' > repo-a.txt
curl -s ftp://ftp.iitb.ac.in/distributions/ubuntu/archives/dists/trusty/main/binary-amd64/Packages.gz | gunzip | grep -E '^(Package|Version)' | awk 'ORS=NR%2?FS:RS {print $2}' > repo-b.txt
diff repo-a.txt repo-b.txt
edited Sep 16 '14 at 14:34
answered Sep 16 '14 at 13:59
murumuru
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f524709%2fcompare-two-repos-a-table-of-all-all-package-versions%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
By definition, all packages will be upgraded after a release upgrade. You probably don't want to check all of them.
– fkraiem
Sep 16 '14 at 13:17