Bug 512518

I forgot to add, that whatever the future of apt, we should all be grateful to Panu for the love he gave all this years to apt, thanks!

Unfortunately I'm no developer. I too would be very sad to see apt-rpm go. It has served me very well over the years. That and the integration of synaptic.

While yumex and yum have made tremendous strides over the last little while in terms of speed and feature set. Yum still doesn't have a "reinstall" feature and yumex still doesn't seem nearly as intuitive as synaptic.

Despite that I think that yum and yumex have evolved enough to NOT make it a pain in the butt to use. And as much as it does pain me I think its time to say so long. There seems to be only 6 of us monitoring and reporting problems with the progress of apt-rpm and that's another downside of things.

Panu... thank you for the great support over the years. I'm sorry that the time is not there to continue with the development of the program.

If for some reason development would continue I would be one of the first to jump back to apt-rpm. I will miss it.

Eli

Created attachment 362371 [details]
src.rpm with all the pacthes

Attached .src.rpm file includes fixes for most of the open bugs (#511910, #428857, #428855). It also includes some additional fixes (i.e. fixed gpg-plugin, that now automatically asks when a rpm-gpg key is missing) and a few features ("list" and "log" plugins). It was tested under Fedora10 and Fedora11.

Using it I successfully upgraded Fedora10 to Fedora11.

What about working with Synaptic?

I have rpmbuild 4.7.1-1 on my system. When I try to rebuild the package I get the following error

rpmbuild: error while loading shared libraries: librpmbuild-4.6.so: cannot open shared object file: No such file or directory

huh?

> What about working with Synaptic?

In general synaptic may have to be rebuilt from .src.rpm. But for me it worked out of the box (`apt-get install synaptic`).

> rpmbuild: error while loading shared libraries: librpmbuild-4.6.so

I've just tested, it works with rpm-4.7.1-1.fc11.x86_64. What's your output of `rpm -qa | grep rpm`? Here's what I have:


$ rpm -qa | grep rpm-
redhat-rpm-config-9.0.3-11.fc11.noarch
rpm-libs-4.7.1-1.fc11.x86_64
rpm-build-4.7.1-1.fc11.x86_64
rpm-4.7.1-1.fc11.x86_64
rpm-devel-4.7.1-1.fc11.x86_64


$ rpmbuild --rebuild apt-0.5.15lorg3.95-0.git416.5.fc10.src.rpm
Installing apt-0.5.15lorg3.95-0.git416.5.fc10.src.rpm
Executing(%prep): /bin/sh -e /var/tmp/rpm-tmp.28PK1w
+ umask 022
[...]
Wrote: /home/build/rpmbuild/RPMS/x86_64/apt-0.5.15lorg3.95-0.git416.5.fc11.x86_64.rpm
Wrote: /home/build/rpmbuild/RPMS/x86_64/apt-devel-0.5.15lorg3.95-0.git416.5.fc11.x86_64.rpm
Wrote: /home/build/rpmbuild/RPMS/x86_64/apt-python-0.5.15lorg3.95-0.git416.5.fc11.x86_64.rpm
Wrote: /home/build/rpmbuild/RPMS/x86_64/apt-plugins-list-0.5.15lorg3.95-0.git416.5.fc11.x86_64.rpm
Wrote: /home/build/rpmbuild/RPMS/x86_64/apt-plugins-log-0.5.15lorg3.95-0.git416.5.fc11.x86_64.rpm
Wrote: /home/build/rpmbuild/RPMS/x86_64/apt-debuginfo-0.5.15lorg3.95-0.git416.5.fc11.x86_64.rpm
Executing(%clean): /bin/sh -e /var/tmp/rpm-tmp.K00qJy
+ umask 022
+ cd /home/build/rpmbuild/BUILD
+ cd apt-0.5.15lorg3.95.git416
+ rm -rf /home/build/rpmbuild/BUILDROOT/apt-0.5.15lorg3.95-0.git416.5.fc10.x86_64
+ exit 0

rpm -qa | grep rpm-
yum-plugin-rpm-warm-cache-1.1.22-1.fc11.noarch
rpm-libs-4.7.1-1.fc11.x86_64
rpm-devel-4.7.1-1.fc11.x86_64
deltarpm-3.4-16.fc11.x86_64
rpm-python-4.7.1-1.fc11.x86_64
rpm-4.7.1-1.fc11.x86_64
redhat-rpm-config-9.0.3-11.fc11.noarch
rpm-build-4.7.1-1.fc11.x86_64

and

ls -l /usr/lib64/*rpm*
lrwxrwxrwx 1 root root     20 2009-09-24 20:14 /usr/lib64/librpmbuild.so -> librpmbuild.so.0.0.0
lrwxrwxrwx 1 root root     20 2009-09-24 20:14 /usr/lib64/librpmbuild.so.0 -> librpmbuild.so.0.0.0
-rwxr-xr-x 1 root root 159280 2009-07-24 08:07 /usr/lib64/librpmbuild.so.0.0.0
lrwxrwxrwx 1 root root     17 2009-09-24 20:14 /usr/lib64/librpmio.so -> librpmio.so.0.0.0
lrwxrwxrwx 1 root root     17 2009-09-24 20:14 /usr/lib64/librpmio.so.0 -> librpmio.so.0.0.0
-rwxr-xr-x 1 root root 187936 2009-07-24 08:07 /usr/lib64/librpmio.so.0.0.0
lrwxrwxrwx 1 root root     15 2009-09-24 20:14 /usr/lib64/librpm.so -> librpm.so.0.0.0
lrwxrwxrwx 1 root root     15 2009-09-24 20:14 /usr/lib64/librpm.so.0 -> librpm.so.0.0.0
-rwxr-xr-x 1 root root 449928 2009-07-24 08:07 /usr/lib64/librpm.so.0.0.0


There is no

librpmbuild-4.6.so

There is something screwy with the installation on one of my computers

Its working on another

When I figure it out, I will let you know

Then probably you have either broken "rpmbuild" package (librpmbuild-4.6.so was used by rpmbuild in F10), or you have several of them. Check `which rpmbuild`, `locate rpmbuild`, `ldd /usr/bin/rpmbuild`...

There was a duplicate sitting in /bin. Removed and everything seems to working just fine.

Thanks... I will be testing it over the next couple of weeks and letting you know how things go.

This is absolutely great. Looking very forward to having an working apt-get synaptic combo again.

OK.... On one coupter... This seems to be working. Latest Synaptic SRPM from koji was rebuilt and also seems to working. This is on one computer. No crash no muss no fuss.

Testing continues


Thank you so very much for this :)

First problem

apt-get update
apt-get dist-upgrade

The following packages will be DOWNGRADED
   libdca (0.0.5-4.fc11 => 0.0.5-4.fc11)
0 upgraded, 0 newly installed, 1 downgraded, 0 removed and 0 not upgraded.
Need to get 0B/113kB of archives.
After unpacking 0B of additional disk space will be used.
Do you want to continue? [Y/n] y
Checking GPG signatures...               ############################## [100%]
Committing changes...
Preparing                                ############################## [100%]
        package libdca-0.0.5-4.fc11.x86_64 is already installed
E: Error while running transaction
E: Handler silently failed

The package is from rpmfusion

oh... forgot to mention this problem occurs with the 64 bit package. The 32bit version on the x86_64 bit platform seems to be OK.

Problem No. 2

E: Repository model not found for http://download.redhat.fedora.com/pub/ fedora/linux/updates/11/x86_64/

I get the above message even though the repodata directory clearly sits under the path mentioned above

The same is true for Everything repository and updates-testing

> E: Repository model not found for http://download.redhat.fedora.com/pub/
> fedora/linux/updates/11/x86_64/

First, "download.REDHAT.FEDORA.com" is definitely an incorrect path. It should be "download.FEDORA.REDHAT.com". Second, `fedora-package-config-apt` contains pathes to download.fedoraproject.org, so it could be you edited them manually and made a mistake there.

Check your configuration files. If you're using rpmfusion they should be like that:
$ egrep -vhr '^(#|$)' /etc/apt/sources.list*
repomd http://download.fedoraproject.org/pub/ fedora/linux/releases/$(VERSION)/Everything/$(ARCH)/os/
repomd http://download.fedoraproject.org/pub/ fedora/linux/updates/$(VERSION)/$(ARCH)/
repomd http://download1.rpmfusion.org free/fedora/releases/$(VERSION)/Everything/$(ARCH)/os
repomd http://download1.rpmfusion.org free/fedora/updates/$(VERSION)/$(ARCH)
repomd http://download1.rpmfusion.org nonfree/fedora/releases/$(VERSION)/Everything/$(ARCH)/os
repomd http://download1.rpmfusion.org nonfree/fedora/updates/$(VERSION)/$(ARCH)

Also you can run:
$ rpm -V apt fedora-package-config-apt rpm
to check, that nothing is broken in your packages.

>The following packages will be DOWNGRADED
>   libdca (0.0.5-4.fc11 => 0.0.5-4.fc11)

Could be a repository conflict (when same package included in different repositories and packaged differently). Check out your:
$ rpm -qa | grep libdca
$ apt-cache showpkg libdca | head

Also it could be you can just reinstall it wherever it comes from:
$ apt-get install --reinstall libdca

computers are so much better at multitasking then people. :)

Sorry about the dumb mistake

Question....

I currently get output like the following from apt-get:

0 upgraded, 0 newly installed, 0 removed and 6 not upgraded


without further info. How do I find out what packages are not being upgraded?

OK... So as is apt-get seems to work well.

However, in the interim, yum has caught up and for day to day package management seems to have surpassed apt-get in one genuinely important way.

deltarpms.


Yum has become much quicker than it used to be and it has become important (IMHO) that apt-get fully support delta rpms because the time that is saved by it is enormous.

There are a couple of other features that I would like to see included in apt-get, but that's another wish list :)

But... I do have to say.... Well done. apt-get is working again. Long live apt-get :)

> 0 upgraded, 0 newly installed, 0 removed and 6 not upgraded

Was it after `apt-get upgrade`? The `upgrade` command does not install new packages neither it removes packages. It's probably supposed to be safe to run from cron-scripts since it only updates existing packages. If newer version of the package requires something that is not installed, such package won't be upgraded.

To upgrade them all there's:
# apt-get dist-upgrade
It will try to solve all the dependencies, remove conflicting packages and install required new ones.

It you want just to see what's going to be downloaded, but don't want the download to begin yet, you can run (even from regular user account):
# apt-get dist-upgrade --print-uris
(can also be used on a PC without internet connection)


> it has become important that apt-get fully support delta rpms

Deltarpms support is in the apt-rpm official roadmap. I'm not sure what are current plans of Panu Matilainen. I've sent him an email but had not received a response yet.

Yes of course its from

   apt-get upgrade

and

  apt-get dist-upgrade

I always use dist-upgrade for the reason you mentioned. However, I still get the message sometimes that apt-get isn't going to "upgrade" something, which could also be a downgrade by the way, without any further information. This kinda bugs me as apt-get sees a package it wants to handle but can't because it is... I have no idea why and would like to.

Very good news about deltarpms.

Panu... If your listening.... And I know you are :) and without asking for any kind of commitment could you confirm that your working on it please.

I have yet to see the patched version applied and updates available. Its been a long time since the patch submitted has been tested. I don't seem to have any trouble with apt-get as is.

Wouldn't it be good to get a working version out there? Or, is there some other problem that I'm not aware of?

I think Sergey made a great job with rectifying the current issues with apt-rpm, and we may have this one time fix in the package, but if this doesn't go upstream, then the project is still dead and kept artificially alive.

Perhaps Sergey could talk with Panu or post on the apt-rpm list to get commit access?

That would be good. Sergey did make a great job of it. And I would dearly love to see apt-rpm active in Fedora again. How about it? Panu? Sergey? :)

This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Just upgraded to Fedora 12 and noticed that apt was included and was this fixed build.

Thank you. Thank you. Thank you.

Long live apt-rpm

While the work from Sergey gives some relief, apt-rpm still needs to be revived on an upstream level, so I'm not closing this bug, yet.

Its really great that the current version of apt has been added to the Fedora 12 repository.

Would you be so kind as to push it to the Fedora 11 updates as well.

Thank you.

This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle.
Changing version to '13'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

I was going write the same thing so I decide to use this report because already have lot of information, that support my request I also  would like retire Fedora-package-config-apt [1]  

And I'd like pack apt of Debian [2]

[1]
https://bugzilla.redhat.com/show_bug.cgi?id=1462485

[2]
https://copr.fedorainfracloud.org/coprs/sergiomb/debs/package/apt/

Hi Sergio, as stated in bug 228427 we share the same intention. I'm OK with recycling this bug report for your needs, I will also contact you offline to coordinate this change.

I'd rather people not recycle old bugs that already served their purpose. Opening new ones doesn't cost anything.
But nevermind that, I'm outta here.