Debian

I'm trying to "build" (see below) a package for another architecture. I made it through (by disabling, frankly) most of the steps.

Long story short, I end up running something like this:

debuild -us -uc --host-type riscv64-linux-gnu -d -C/dev/null

but debuild keeps failing on this line:

[...]
make[1]: Leaving directory '/home/netvor/.cache/mkittool/debstuff/build/zigdev-0.0.0+t20240906145412.egg.gbc271d0'
   dh_shlibdeps -a
   dh_installdeb
   dh_gencontrol
   dh_md5sums
   dh_builddeb
dpkg-deb: building package 'zigdev' in '../zigdev_0.0.0+t20240906145412.egg.gbc271d0-1_riscv64.deb'.
 dpkg-genbuildinfo -O../zigdev_0.0.0+t20240906145412.egg.gbc271d0-1_riscv64.buildinfo
 dpkg-genchanges -C/dev/null -O../zigdev_0.0.0+t20240906145412.egg.gbc271d0-1_riscv64.changes
dpkg-genchanges: info: including full source code in upload
 dpkg-source --after-build .
dpkg-buildpackage: info: full upload (original source is included)
debuild: fatal error at line 1062:
can't open zigdev_0.0.0+t20240906145412.egg.gbc271d0-1_amd64.changes for reading: No such file or directory

So the *_amd64.changes file does not exist, but *_riscv64.changes does:

zigdev-0.0.0+t20240906145412.egg.gbc271d0
zigdev_0.0.0+t20240906145412.egg.gbc271d0-1.debian.tar.xz
zigdev_0.0.0+t20240906145412.egg.gbc271d0-1.dsc
zigdev_0.0.0+t20240906145412.egg.gbc271d0-1_amd64.build
zigdev_0.0.0+t20240906145412.egg.gbc271d0-1_riscv64.buildinfo
zigdev_0.0.0+t20240906145412.egg.gbc271d0-1_riscv64.changes
zigdev_0.0.0+t20240906145412.egg.gbc271d0-1_riscv64.deb
zigdev_0.0.0+t20240906145412.egg.gbc271d0.orig.tar.gz

Building with amd64 architecture finishes correctly *_amd64.changes exists and is used.

First, do I really need this .changes file? (I'm not planning to upload this to Debian archive.) And if so, how to make debuild use the correct file?

The environment (when calling env inside rules file) looks like this:

ASFLAGS=
CFLAGS=-g -O2 -ffile-prefix-map=/home/netvor/.cache/mkittool/debstuff/build/zigdev-0.0.0+t20240906145412.egg.gbc271d0=. -fstack-protector-strong -Wformat -Werror=format-security
CPPFLAGS=-Wdate-time -D_FORTIFY_SOURCE=2
CXXFLAGS=-g -O2 -ffile-prefix-map=/home/netvor/.cache/mkittool/debstuff/build/zigdev-0.0.0+t20240906145412.egg.gbc271d0=. -fstack-protector-strong -Wformat -Werror=format-security
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/11111/bus
DEBEMAIL=Me <[email protected]>
DEB_BUILD_ARCH=amd64
DEB_BUILD_ARCH_ABI=base
DEB_BUILD_ARCH_BITS=64
DEB_BUILD_ARCH_CPU=amd64
DEB_BUILD_ARCH_ENDIAN=little
DEB_BUILD_ARCH_LIBC=gnu
DEB_BUILD_ARCH_OS=linux
DEB_BUILD_GNU_CPU=x86_64
DEB_BUILD_GNU_SYSTEM=linux-gnu
DEB_BUILD_GNU_TYPE=x86_64-linux-gnu
DEB_BUILD_MULTIARCH=x86_64-linux-gnu
DEB_BUILD_OPTIONS=notest parallel=8
DEB_HOST_ARCH=riscv64
DEB_HOST_ARCH_ABI=base
DEB_HOST_ARCH_BITS=64
DEB_HOST_ARCH_CPU=riscv64
DEB_HOST_ARCH_ENDIAN=little
DEB_HOST_ARCH_LIBC=gnu
DEB_HOST_ARCH_OS=linux
DEB_HOST_GNU_CPU=riscv64
DEB_HOST_GNU_SYSTEM=linux-gnu
DEB_HOST_GNU_TYPE=riscv64-linux-gnu
DEB_HOST_MULTIARCH=riscv64-linux-gnu
DEB_RULES_REQUIRES_ROOT=binary-targets
DEB_TARGET_ARCH=riscv64
DEB_TARGET_ARCH_ABI=base
DEB_TARGET_ARCH_BITS=64
DEB_TARGET_ARCH_CPU=riscv64
DEB_TARGET_ARCH_ENDIAN=little
DEB_TARGET_ARCH_LIBC=gnu
DEB_TARGET_ARCH_OS=linux
DEB_TARGET_GNU_CPU=riscv64
DEB_TARGET_GNU_SYSTEM=linux-gnu
DEB_TARGET_GNU_TYPE=riscv64-linux-gnu
DEB_TARGET_MULTIARCH=riscv64-linux-gnu
DFLAGS=-frelease
DH_INTERNAL_BUILDFLAGS=1
DH_INTERNAL_OPTIONS=
DH_INTERNAL_OVERRIDE=dh_auto_install
FAKED_MODE=unknown-is-root
FAKEROOTKEY=2071757222
FCFLAGS=-g -O2 -ffile-prefix-map=/home/netvor/.cache/mkittool/debstuff/build/zigdev-0.0.0+t20240906145412.egg.gbc271d0=. -fstack-protector-strong
FFLAGS=-g -O2 -ffile-prefix-map=/home/netvor/.cache/mkittool/debstuff/build/zigdev-0.0.0+t20240906145412.egg.gbc271d0=. -fstack-protector-strong
GCJFLAGS=-g -O2 -ffile-prefix-map=/home/netvor/.cache/mkittool/debstuff/build/zigdev-0.0.0+t20240906145412.egg.gbc271d0=. -fstack-protector-strong
GPG_AGENT_INFO=/run/user/11111/gnupg/S.gpg-agent:0:1
HOME=/home/netvor
LANG=en_US.UTF-8
LC_COLLATE=C
LDFLAGS=-Wl,-z,relro
LD_LIBRARY_PATH=/usr/lib/x86_64-linux-gnu/libfakeroot:/usr/lib64/libfakeroot:/usr/lib32/libfakeroot
LD_PRELOAD=libfakeroot-sysv.so
LOGNAME=netvor
MAKEFLAGS=w
MAKELEVEL=2
MFLAGS=-w
OBJCFLAGS=-g -O2 -ffile-prefix-map=/home/netvor/.cache/mkittool/debstuff/build/zigdev-0.0.0+t20240906145412.egg.gbc271d0=. -fstack-protector-strong -Wformat -Werror=format-security
OBJCXXFLAGS=-g -O2 -ffile-prefix-map=/home/netvor/.cache/mkittool/debstuff/build/zigdev-0.0.0+t20240906145412.egg.gbc271d0=. -fstack-protector-strong -Wformat -Werror=format-security
PATH=/usr/sbin:/usr/bin:/sbin:/bin:/usr/bin/X11
PREFIX=/usr
PWD=/home/netvor/.cache/mkittool/debstuff/build/zigdev-0.0.0+t20240906145412.egg.gbc271d0
SOURCE_DATE_EPOCH=1456533483
TERM=rxvt-unicode
ZIGDEV_ZIG_VERSION=0.13.0
ZIGSITE=/opt/zigdev
ZIGSITE_PREP=debian/tmp/opt/zigdev

Open "spoiler" below to read more about my goals. Since the fact I don't actually want to build Zig properly here might confuse and annoy people, I wrote my reasoning below.

Good day,

This morning I just updated my machines, and I cant help to think that the updates got 'less' in a way?

Normally if I would update my machines on a daily or weekly manner, I would have a big list of updates that can be applied, today, not as much.

I'm running testing/sid on two machines, and LMDE/sid on another.

Would like to know if anyone experience something similar. If that is the case, I wonder if the xz backdoor gave the devs a scare of their lives.

Blessings.

Hello ! I recently switched to linux on my laptop and I'm currently on testing (trixie) and since I changed my audio set-up to have a headset for a call and a Bluetooth speaker for media etc my laptop's speakers aren't appearing anymore in pulse audio.

I must admit I'm a bit clueless on what to do to solve this issue, any help would be appreciated, I tried to find stuff online but nothing really seemed to match my issue as when the Bluetooth speaker is connected everything works fine. I'm trying to stick to the "don't execute it if you don't understand it" and well I don't want to worsen the issue.

Thanks in advance for any help !

Ever since I upgraded, the HDD light has been burning constantly even though the upgrade is complete. Is this normal? The process systemd-journal seems to be active, does that mean that logging all the changes is what's going on?

It's a pitiful Atom system with 2 cores, 2Gb RAM, and a single spinning HDD.

EDIT: Some service got installed that conflicted with pihole. plus I screwed up my sources.list.

Everything was working fine, but I just HAD to update.

How to install KDE Plasma 6 on Debian 12

Is there a way to get a report for historic network activity? Right now, I've installed sysstat and learning to use that. My search engine searching has got some results, but when I read about some programs that monitor activity, I'm not sure if I am overlooking something or if they don't offer it or if I have combed the doc files enough so figured I'd ask here.

I'm teaching myself how to run my own server. Starting with storage needs and then seeing how it goes from there. I'm hoping to find a way to get a report of past traffic/activity specifically.

Running Debian 12.

I'm having some trouble with suspend not working properly on my laptop, which has one of those Nvidia/Intel hybrid graphics systems. I run Debian 12 on it, with Gnome under Wayland.

Sometimes, my laptop will not go to sleep properly and just stay turned on. However, the screen will be black, and it won't respond to anything. The only thing I can do in this situation is a hard reset.

I say sometimes, because most of the time it works correctly and I just can't reproduce this bug. It might happen twice a day, but sometimes it won't happen for a week. I have a feeling Nvidia is the culprit here, but I was wondering if anyone else ran into this and knows a bit more about what's going on here?

Hi, I do rarely posting things on lemmy or frankly speaking this is my first time. I hope this meet this sub rules, despite it's a Spirallinux (it's still debian right?) problem or possible a framework system problem.

A strange problem appears when I install a steam game and try to start it. When the game tries to launch, the screen just freezes for a moment with the logo of the game start screen. After a few seconds the screen went black and the cursor poped up without the possibillity getting to the tty.

At first I had an system with an encrypted disk. When I installed Baldur's Gate on my system and started the game, the system crashes and the only thing I could do was pushing the power button. After reboot trying to enter my passphrase, the encryption manager always reported me that I entered the wrong phrase. I gave up since I couldn't even manage my snaps to rollback. I thought it was a critical bug from the game.

When I deleted my drive and tried to set up a new system I gave another game a chance. This time it was The Talos principle 2. Same problem. The system crashed with the only option pushing the power button. But this time I installed my system without encryption so I could enter my snaps on boot. The problem here is that several of the latest snaps were corrupted. Only the older ones were still working (snaps from 2 or 3 days ago).

The newer ones reports shows failing to start some podman-restart.service, podman-auto-update.service and networking.service.

Steam is from the debian repository.

My system: OS: Spirallinux (Debian 12) Kernel: Backport 6.5.0

Laptop: Framework 13 AMD Ryzen 7040 Series Ram: 64GB Firmware: 3.03

I don't know how to troubleshoot this problem. I hope I can find some help here. Thanks for any tips and help!

If you like Debian and like to help make it better, and also want to use testing please review this guide where I try to cover many common things and improve your experience:

https://makedebianfunagainandlearnhowtodoothercoolstufftoo.computer/doku.php?id=start

Thanks for being a Debian testing user :)

Hi,

I do believe from time to time there are important updates that need you to reboot your server, but how often? I'm thinking about kernel updates, let's say every month... What are you practices and recommendations?

As the title states whenever I try to login and start the desktop environment (xfce4 and dwm) I get kicked back to the login screen with no error message. Beforehand I was messing around with configuring dwm. I've tried updating through the tty and deleting dwmblocks (which is what I was messing with before all this)

Here's the Xorg log: https://paste.debian.net/hidden/2936c842/

Here's the output when running startxfce4:

usr/bin/startxfce4: Starting X server

(EE)
Fatal server error:
(EE) Server is already active for display 0
                if this server is no longer running, remove /tmp/.X0-lock and start again.
(EE)
(EE)
Please consult the X.org foundation support at http://wiki.x.org for help.
(EE)
Authorization required, but no authorization protocol specified

xinit: giving up
xinit: unable to connect to C server: Resource temporarily unavailable
xinit: server error

So, not so long ago I have made a switch from Win 10 to Linux Mint on my older laptop. I like it, and I have decided to switch to Linux also on my main desktop (to be honest, I've realized I don't actually do anything Windows-specific I can't do on Linux). I am thinking of trying Debian. I know it's not the best for total newbies, but I am willing to commit time to learn a thing or two to make it work to my needs (which are not many). I am just worried - would I be able to setup up my two monitors to work? From what I read, it's not that easy, so that worries me a bit (although, it's nothing which would stop me from the switch). Can anyone provide an opinion about it, please? Many thanks in advance.

Any immutable OS with xfce/cinnamon de available.

Hey guys, I have been using manjaro KDE Plasma for a while and netspeed widget has been a huge part of how I manage my limited data. I recently moved to debian 12 KDE Plasma and everything has been working smoothly but i can't get the Netspeed widget to work. it just shows zeros, no incoming traffic, and outgoing traffic values. Is there a way to fix this ?

I have this Debian server that won't stop crashing. It crashes once every 2 or 3 days. Everything's up to date, the cpu is good and prime 95 never finds any problems. The ram is good and I've run every ram test there is and never found anything wrong. I just can't get it to stop crashing and it's driving me insane.

I used to have an arduino connected to the motherboard's reset jumper and then set up a bash script as a systemctl service that sent a signal to the arduino every 10 seconds and if the arduino didn't receive a signal after 30 seconds it forces a reboot. This doesn't even automate the process of restarting after a crash because too often, the server will crash just lightly enough that everything except that autorestart bash script service stops working so it won't reboot. It does double amount the time the server works without manual intervention though which is better than nothing but not good enough.

Other than just randomly installing different distros until I find one that doesn't do this (reinstalling an os and then setting all the server stuff back up is very time consuming), what can I do to troubleshoot/solve/stop or otherwise do anything about these crashes?

cross-posted from: https://lemmy.world/post/647174

Woo Hoo! No need for snap anymore. We pure Debian users are no longer limited to just LXC anymore (https://wiki.debian.org/LXD). Thanks to all the dev's (especially Mathias Gibbens) for all the hard work on this.

Now... time for me to explore pure Debian servers to displace Proxmox/LXC for some use cases.

Why use a server-oriented distro for desktop? If the goal is stability, wouldn't something like Linux Mint, Ubuntu, Zorin, etc. be a better option for desktop?

One of the notable comments made in that Debian release team update is that while RISCV64 (RISC-V 64-bit) isn't yet on the official architecture list, the port is making good progress. For the Debian 13 release in a year and a half to two years out, it's expected to ship RISC-V 64-bit support. The architecture qualification will need to happen later in the Debian Trixie cycle