Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#298 closed bug (wontfix)

DEB packages have wrong dependencies on amd64

Reported by: admin@… Owned by: somebody
Priority: major Milestone: 3-1-2 and higher
Component: dontKnow Version: 3-1-2
Keywords: deb dependencies Cc:


Updating from ver. 3.1.1 to ver. 3.1.2 on current Debian Lenny amd64 Systems did work, but rendered the installations useless:

$ Singular
/usr/lib/Singular/Singular: error while loading shared libraries: cannot open shared object file: No such file or directory

After installation of libreadline6:

$ Singular 
/usr/lib/Singular/Singular: /lib/ version `GLIBC_2.11' not found (required by /usr/lib/Singular/Singular)

After upgrading libc6 from 2.7-18lenny6 to ver. 2.11.2-7 (Debian Squeeze), the program worked again.

On equally configured i686 systems, the program works with libreadline5 and without the upgrade of libc.

I think, the amd64 package was mistakenly built against the wrong libraries, but if not, I'd recommend to include libreadline6 and a version switch for libc6 to the dependencies and removing libreadline4|libreadline5 from there.

Note that this can be a very nasty problem, if one did not backup a 3.1.1 package anywhere. :-(

Yours, Thomas Kremer

Change History (2)

comment:1 Changed 12 years ago by Oleksandr

Resolution: wontfix
Status: newclosed

Dear Thomas,

could you please try building Singular from sources?


Singular Team

comment:2 in reply to:  1 Changed 12 years ago by admin@…

Dear motsak,

what makes you think anyone 'round here still uses your software after failing to notice this break-all bug for NINE MONTHS, then proceeding by closing it without even having read it?

Do you see any connections between source builds and wrong package dependencies? I don't.

Your deb package for amd64 needs libreadline6 and libc6 (>= 2.11), so it should specify these in its package dependencies.

Yours, Thomas Kremer

Note: See TracTickets for help on using tickets.