Don't break Debian... except one package? (Angband 4.2.5 in Sid)

JasonMehmel · 2024-07-25 16:19:27

In the process of swapping laptops, I'm trying to run the games I had working on the last machine, and the Angband I had compiled on the last one isn't running on this one, for a few reasons.

Compiling Angband isn't THAT hard, but just annoying enough, because you have to choose among a few options at compiling time, and the last time I went through it also finding a few bugs.

As a Linux user, I shouldn't be afraid of doing the work! But I'm also slightly annoyed that the most recent version isn't in the Stable repos.

Which leads me to the situation... the most recent version is in Sid / Unstable!

I don't really want to add Unstable to my repos entirely, but I am wondering about just loading the 4.2.5 deb from Sid that I was able to snag.

How much am I risking a Franken-Debian if I try that?

brontosaurusrex · 2024-07-25 16:56:27

libc situations seems fine (dep: libc6 (>= 2.34) [not alpha, ia64, sh4]), so you might be ok, depending on how other dependencies play out. (Generally speaking: Don't force any updates on libc).

edit, I made it install like this:

sudo dpkg -i angband-data_4.2.5+dfsg1-1_all.deb
sudo dpkg -i angband_4.2.5+dfsg1-1_amd64.deb
sudo apt-get -f install

And it seems to be working.

Bearded_Blunder · 2024-07-25 17:17:11

What's in backports? If anything?

Have you considered backporting the one from Sid yourself? You'd likely only have to add a source entry to apt which is safe enough.

Simple Backport Creation guide is available & isn't complex if the package will build. No need adding Sid to your main sources or fancy apt pinning that way.

JasonMehmel · 2024-07-25 19:16:38

brontosaurusrex wrote:

libc situations seems fine (dep: libc6 (>= 2.34) [not alpha, ia64, sh4]), so you might be ok, depending on how other dependencies play out. (Generally speaking: Don't force any updates on libc).
edit, I made it install like this:
sudo dpkg -i angband-data_4.2.5+dfsg1-1_all.deb
sudo dpkg -i angband_4.2.5+dfsg1-1_amd64.deb
sudo apt-get -f install
And it seems to be working.

Did you grab those angband debs (and the dfsg debs) from Sid?

And I'm guessing you ran those commands in the same location as the deb files?

JasonMehmel · 2024-07-25 19:18:31

Bearded_Blunder wrote:

What's in backports? If anything?
Have you considered backporting the one from Sid yourself? You'd likely only have to add a source entry to apt which is safe enough.
Simple Backport Creation guide is available & isn't complex if the package will build. No need adding Sid to your main sources or fancy apt pinning that way.

It wasn't in backports (I was hoping!) but I'll take a look at your idea! If I have that right, when I'm done will I have access to that specific Sid / Unstable package as it updates?

Bearded_Blunder · 2024-07-25 19:22:18

JasonMehmel wrote:

brontosaurusrex wrote:
libc situations seems fine (dep: libc6 (>= 2.34) [not alpha, ia64, sh4]), so you might be ok, depending on how other dependencies play out. (Generally speaking: Don't force any updates on libc).
edit, I made it install like this:
sudo dpkg -i angband-data_4.2.5+dfsg1-1_all.deb
sudo dpkg -i angband_4.2.5+dfsg1-1_amd64.deb
sudo apt-get -f install
And it seems to be working.
Did you grab those angband debs (and the dfsg debs) from Sid?
And I'm guessing you ran those commands in the same location as the deb files?

I'd recommend gdebi or doing

sudo apt-get install ./angband-data_4.2.5+dfsg1-1_all.deb ./angband_4.2.5+dfsg1-1_amd64.deb

over dpkg -i followed by apt-get -f
gdebi or installing using apt-get will warn you if it can't satisfy deps apt-get -f has been known to fail & leave systems in a broken state.

Last edited by Bearded_Blunder (2024-07-25 19:22:37)

JasonMehmel · 2024-07-25 20:03:34

Oh, I should also note, it's in Trixie / Testing as well as Sid / Unstable. Though I'm guessing that adding Testing is as problematic as adding Unstable to your repos!

Bearded_Blunder · 2024-07-25 20:53:15

It wasn't in backports (I was hoping!) but I'll take a look at your idea! If I have that right, when I'm done will I have access to that specific Sid / Unstable package as it updates?

You'd have to keep track yourself, though I think there's a package that'd track if the source package got updated so you could backport the newer version darned if I remember the name though, however in due course when you update the entire system to Trixie, it'd get updated just like everything else then.....

And there's apt-cache showsrc angband which should give you clues when you'd have to redo for a newer version.

brontosaurusrex · 2024-07-26 03:09:01

JasonMehmel wrote:

Did you grab those angband debs (and the dfsg debs) from Sid?
And I'm guessing you ran those commands in the same location as the deb files?

Yes and yes.

JasonMehmel · 2024-07-26 16:43:24

Thank you to both Bearded_Blunder and brontosaurusrex... this has been a useful way of examining the issue through the form of focusing on this old-school roguelike!

I think I'll probably try the gdebi install of the .deb files first...

Bearded_Blunder, what would be the benefit of backport creation from testing or unstable, versus just trying to install the .deb files, if it doesn't capture the new updates?

Bearded_Blunder · 2024-07-26 20:02:54

Since it's built against the libraries in stable, you'd be somewhat less likely to get strange issues or incompatibilities that show up instantly or later.

If it builds it ought to work, there's no guarantee of that grabbing the .deb & just installing from testing, if it does work at all grabbing the deb it's possible to add testing, & use apt pinning so that's all you pull from there but it updates (rather like stuff from backports), but there's still no guarantee an update won't break things.

If it doesn't work grabbing the .deb, then the backport creation or compile directly from upstream source may be your only options. That or run testing, or live with the older version in stable.

#1 2024-07-25 16:19:27

Don't break Debian... except one package? (Angband 4.2.5 in Sid)

#2 2024-07-25 16:56:27

Re: Don't break Debian... except one package? (Angband 4.2.5 in Sid)

#3 2024-07-25 17:17:11

Re: Don't break Debian... except one package? (Angband 4.2.5 in Sid)

#4 2024-07-25 19:16:38

Re: Don't break Debian... except one package? (Angband 4.2.5 in Sid)

#5 2024-07-25 19:18:31

Re: Don't break Debian... except one package? (Angband 4.2.5 in Sid)

#6 2024-07-25 19:22:18

Re: Don't break Debian... except one package? (Angband 4.2.5 in Sid)

#7 2024-07-25 20:03:34

Re: Don't break Debian... except one package? (Angband 4.2.5 in Sid)

#8 2024-07-25 20:53:15

Re: Don't break Debian... except one package? (Angband 4.2.5 in Sid)

#9 2024-07-26 03:09:01

Re: Don't break Debian... except one package? (Angband 4.2.5 in Sid)

#10 2024-07-26 16:43:24

Re: Don't break Debian... except one package? (Angband 4.2.5 in Sid)

#11 2024-07-26 20:02:54

Re: Don't break Debian... except one package? (Angband 4.2.5 in Sid)

Board footer