Package: dream --A Software Digital Radio Mondiale (DRM) receiver (RFP 691685) ITP: dream --A Software Digital Radio Mondiale (DRM) receiver Request for ITP. I will attempt to to package Dream as requested by RFP 691685. This is my first Debian package. I lack the necessary radio receiver to test Dream on air. May someone volunteer to do so? We may need to extend Dream to PulseAudio. Garie Miller
Re: GMiller 2018-08-29 <2b3ad163270be6e46d4d1303be457e69.startmail@startmail.com> I think it is probably not a good idea to maintain something that you are neither using yourself, nor can't test. Does it work with the cheap RTL-SDR sticks? Maybe you get yourself one of those? Christoph
I have discovered that you do not need a local receiver in order to use this software. Please refer to this article on how to use KiwiSDR to route IQ audio into Dream. KiwiSDR setup to use the DREAM Receiver https://ka7u.us/2017/11/17/kiwisdr-setup-to-use-the-dream-receiver/
Hello Jiangzu Kumquat and Christoph, Concerning your subject email on debian-hams@lists.debian.org; The upstream maintainer on SourceForge has been working a problem in getting DReaM to work smoothly in Debian. Please be patient until he has completed his work. Note that the above bug number is still active. 73 Garie Miller, WB9AWA----------------------------------------------------------------------- Take back your privacy. Switch to StartMail.com <https://www.startmail.com/>
Jiangsu Kumquat; Thank You for the reference to the KiwiSDR article. I will try to look into to that since it likely will be helpful. Garie Miller
Dear Jonas: Yes. Dream Bug #907576 requires the newer codec of libfdk-aac-dev 2.0.0 which was also requested by Bug#915386. Without it Dream cannot function per current standards. OK. I will file at Bug#915386. Thank You, Garie Miller
Hello: Completion of Dream Bug#907576 requires the newer codec of libfdk-aac-dev 2.0.0, which has also been requested by Bug#915386 (latest at Github is 2.0.1). Dream cannot function properly with the current 1.6 codec in Debian. Note also that libfdk-aac-dev is part of a larger source code package fdk-aac. Is anyone working to complete 915386? I am willing to try to package it (ie, ITP), subject to my limited experience in Debian. This probably involves uploading the larger package fdk-aac. Suggestions or help is welcome. Thank You, Garie Miller
TNX Christoph OK I have just established an account on Salsa. The particulars are: Full Name Garie Miller Username GMiller Email gmill777@protonmail.com I don't think I registered before unless it was in connection with the Multimedia Team. Let me read up on the procedure then I will push my Dream stuff up. It may take me a few days. I suppose someone will then need to merge. Then later a sponsor. Here is a summary on Dream as best I know. I worked it locally mostly following the Debmake/Debuild procedure 'Guide for Debian Maintainers' M262019. The Debian and Docs directories are complete (with lintian) barring last minute tweaking. I believe src includes commits thru 1339, which best I can tell is vital to support the the new codec and maybe other problems. Last I checked SourceForge there has been no activity since 1339 and February. Anyway, during 'Debuild' object files are generated but compilation fatally stops with file GUI-QT/EvaluationDlg.cpp (I will include some screenshots). The compiler declares this an illegal cast (this in old code dating to 2000. Maybe the compiler is getting stricter?) I would guess this issue is something like trying to make a positive real into an integer. But trying to debug and patch C+ code like this is getting over my head and I would like to solicit input from someone who KNOWS what they are doing. And there are likely to be more of these before it links. The new codec 'libfdk-aac-dev 2.0.1' is currently in Sid. I have an RTL dongle here that I will use for on air testing if we succeed in producing a binary. If we get that far we can then decide if Dream is stable enough for Debian. I invite others to test and give their results too. 73 Garie Miller WB9AWA Sent with [ProtonMail](https://protonmail.com) Secure Email.
Hello Christoph BTW I made a new GPG. My old GPG is about expired and references the old Email. If I understand correctly the package must be signed before I push it. I am reading through various documents on the upload procedure. One problem I see is that dput is expecting a changes file, when of course since compilation failed I don't have one yet. The normal procedure only uploads changes and a few others. In this case you may want access to all my original directory structure, etc (its about 29MB). I don't see any command switches that seem to apply to this case. I may be off in the wrong direction. Any suggestions on where to look? 73 Garie wb9awa Sent with [ProtonMail](https://protonmail.com) Secure Email.
Hi Christoph Hey it just occurred to me I probably need to use git commands for this push to Salsa. I have never worked on line before and didn't think of it. I'm reading a copy of the Git User Manual here and see the push command. 73 Garie Sent with [ProtonMail](https://protonmail.com) Secure Email.
Hi Christoph Thanks for your patience. I thought it pushed last night, but I don't see anything on Salsa this morning. Anyway it insisted that I use: git push --set-upstream ssh://git@salsa.debian.org:debian-hamradio-team/dream.git master It gave two errors, the second in red: error: src refspec master does not match any error: failed to push some refs to 'ssh://git@salsa.debian.org:debian-hamradio-team/dream.git' 73 garie wb9awa Sent with [ProtonMail](https://protonmail.com) Secure Email.
Re: GMiller Uhm. Which branch are you on? Christoph
Christoph I think my problem was that I was not smart enough to unhash my files for the commit. I regenerated the .git file and tried again with: git push --set-upstream ssh://git@salsa.debian.org:debian-hamradio-team/dream.git master It responded with: ssh: Could not resolve hostname salsa.debian.org:debian-hamradio-team: Name or service not known fatal: Could not read from remote repository. Please make sure you have correct access rights and the repository exists. Well I generated my ssh key on this end. I copied it over on salsa. Everything looks set on salsa. I don't see any typos in the hostname. I don't know much about this yet. Is master the correct branch? garie Sent with [ProtonMail](https://protonmail.com) Secure Email.
Re: GMiller
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Try either git@salsa.debian.org:debian-hamradio-team/dream.git
or ssh://git@salsa.debian.org/debian-hamradio-team/dream.git
Christoph
OK I see here in gittutorial. Is GMIller a good name to push my branch (instead of master)? I'm guessing the other problem is that I don't have the Salsa public key. If correct I will have to get it somehow. garie Sent with [ProtonMail](https://protonmail.com) Secure Email.
Re: GMiller Clone the repo to your account on salsa and push it there first. Christoph
Yes the correct host turned out to be when I tried it: ssh://git@salsa.debian.org/debian-hamradio-team/dream.git I had pasted an rsa key the other day. For some reason Salsa responded with an ED25519 and would not authorize. So I had to create and paste an new ED25519 to get authentication. Initially it worked. Now all of the sudden Salsa denies permission on the ED too (for no reason I can think of). I created a new ED and tried to add paste it. The Add button refuses to ungray and add. I deleted the first thinking it might let me add then but no luck. Acts like it's blocking (the button first flashes green then turns gray). My Salsa account got completed as https://salsa.debian.org/GMiller/dream. That may not be quite what was intended. I followed the instructions per the page that popped up for Project ID 52290 (I think this follows what you said in your email). I did a git clone git@salsa.debian.org:GMiller/dream.git. I forget but it may have responded repo already existed, then those commands following which seem to have wiped the COMMIT_EDITMSG file (hope that's not a problem). Then if I interpret this correctly I did (the last line): git push -u (which means --set-upstream) ssh://salsa.debian.org/GMiller/dream.git master aiming for my account. I think that's correct for a start. And of course permission denied again (publickey). Well I beg your patience on this. I'll get it somehow. Getting tired so I'll try again tomorrow. garie Sent with [ProtonMail](https://protonmail.com) Secure Email.
Hi Christoph OK looks like I finally succeeded with the push. I was able to re-add the ED key this morning. I appreciate your patience. This is my complete Dream working file. I also sent the .git but don't see it for some reason. If I recall, Dream has several code errors. The cast issue is maybe the most difficult. I have read casts can be a mess. Anyway I request help in patching these. Meanwhile I am thinking on what to do next. It may be worthwhile if I study the commits on SourceForge. I have just looked at what was on Salsa. Looks like Julian Cable did work on it. No one else unless I missed it. There have been releases and hundreds of commits since those dates. 73 garie wb9awa Sent with [ProtonMail](https://protonmail.com) Secure Email.
Hi Garie, Re: GMiller The push worked, but there's no debian/ directory in there. Also, the .git directory will never appear "inside" the git repo so you can't see it in the gitlab UI. But effectively, you are only pushing the .git/ contents to the server which will extract all the working files from there. I suggest you get it to compile first, without any debianization. Upstream should hopefully be interesting in shipping code that compiles. Christoph
Christoph For the Debian directory look in: Project 52290 Initial commit Dream push to Salsa-Garie Miller 08 19 20 Repository dream/dream-2.2.1+r1339/debian/ I pushed my working directory (with screenshots) both as an 'existing folder' and a '.git repo'. If you have any review comments I would be interested. As for compilation, it compiles upstream for Windoze. I'm not sure they would care to support us and our compile problems. garie Sent with [ProtonMail](https://protonmail.com) Secure Email.
Re: GMiller you decide to commit them) need to be in the root directory of the repo, and the debian directory needs to be /debian. Also, don't add any tarballs (see `pristine-tar` instead, but that is optional), and don't commit .dsc or .buildlog or whatever. The screenshots are likely wrong in the repo as well. Looking over the debian/ dir: Why Section: non-free/hamradio ? copyright: you probably don't want to list all files individually. If all files have the same (C), just add "Files: *". You never build-depend on a C-compiler, that's what build-essential is for. libfaac-dev and libfdk-aac-dev do not exist in unstable. On which distribution did you test that? For the binary: Remove all the lib* (and zlib) dependencies, dpkg-shlibdeps will sort that out automatically. Things in debian/docs do not need to be installed by debian/install. Any COPYING file should be installed by dh_installdocs to /usr/share/doc/$package/copyright.gz, and not under random other filenames. Re debian/tests/: GUI apps are hard to test anyway, so that's entirely optional. Christoph
Hi Christoph TNX for the comments. 1)Yes, I will try to do something about the layout. I see that other projects have debian and src dirs. at top of master. 2)Dream links with non-free libraries. I followed procedure as I understand it. 3)Copywrite. I thought it redundant also. But this is how Debmake generated it. I didn't want to change it without good reason. 4) OK regarding build-depend. I will pick that up in time. 5)libfdk-aac-dev 1.6 is in Buster. The new libfdk-aac-dev 2.0.1 was in Sid unstable last I looked. We must use this. libfaac-dev is non-free. 6)OK regarding lib* depends. 7)OK regarding debian/install. 8)OK regarding COPYING. 9)OK will skip test. I've been reading and looking. The Salsa Web IDE looks good and seems intuitive to use. I thought I might next create branch 'experimental' and try an on-line build using git-buildpackage, gbp or something. The documentation explains how to branch. Problem is when you go to the dashboard, the branch icon they show is missing. I would rather not have to use the command line to branch if I can help it. garie Sent with [ProtonMail](https://protonmail.com) Secure Email.
Hello: I am currently working a project in Salsa (dream ID 52290). Within the project's Web IDE I am currently in need of starting a 'Web Terminal' in order to build and run live testing. The terminal is grayed out and gives this message: 'Configure a .gitlab-webide.yml file in the .gitlab directory to start using the Web Terminal. Learn more.' Well 'Learn More' yields a broken link. Presuming that .gitlab-webide.yml is the correct name, I have been unsuccessful a finding a document or a template dropdown which describes it. Suggestions anyone? Garie Miller Sent with [ProtonMail](https://protonmail.com) Secure Email.
Hello, For the subject project, I have encountered a roadblock while attempting to use the 'Salsa Web Terminal'. I filed Gitlab Issue 233 (see attachments) seeking information to prepare a 'gitlab-webide.yml' file (I searched but could find no documentation on it). The response to 233 says "To upload designs, you'll need to enable LFS and have an admin enable hashed storage". Well, LFS was already enabled in my Dream project and I think hash storage is already enabled too, but could find no way to verify this myself. By 'admin' I'm not sure if he means a 'Gitlab' or a 'Salsa' admin. Anyway, if someone with access could please verify the hashed storage? But my original question remains. Where is documentation concerning a 'gitlab-webide.yml' file? I see nothing in Gitlab or Salsa that describes it. I even spot checked some other Salsa projects thinking they may include one, and that might give me some clues. Can anyone give me some direction on this? Thank you Garie Miller Sent with [ProtonMail](https://protonmail.com/) Secure Email.
Re: GMiller Sorry, I can help you with packaging hamradio software, but please use a normal editor like everyone else. There is no need to bother with funky web stuff, especially if it doesn't work out of the box. Christoph
Hello Christoph I am not sure I understand your comment. Are you saying in effect, don't use a Salsa IDE to build/test the project? Instead use an IDE on my local machine to build/test and develop any code changes? Is that how most Salsa projects are doing it? Thanks for your patience Garie Miller wb9awa Sent with [ProtonMail](https://protonmail.com/) Secure Email.
Garie, TL;DR Use an IDE or text editor on your machine. Local IDEs/text editors are used to develop the vast, vast majority of software. Most developers develop on their own machines instead of in the browser. It doesn't make sense to develop in a browser-based IDE (at least not yet) since they are missing vital functionality. Whole OSes can't be replicated in the browser, whereby the browser greatly limits access to common development tools. Best regards, Brian
Hello Brian Yes pragmatism in retrospect now seems obvious. Now that I think about it, the only functionality it might add to Salsa is the ability to build on line anyway. Thanks for your insight. Now for information, back to DReaM. I'm going to try commenting out a few lines of offending code and see if it compiles. I think this will only affect an obscure feature in the DReam functionality. No experienced programmer has volunteered to help fix the broken code and I'm not smart enough to know how. It will probably work good enough. 73 Garie Miller wb9awa Sent with [ProtonMail](https://protonmail.com/) Secure Email.
Here is a status of Dream for Debian at this time. I have succeeded in compiling Dream for Debian locally. I did this by commenting out files MDI/RSCITagItemDecoders.cpp line 258, MDI/MDITagItem.cpp lines 1106 - 1117 and GUI-Qt/EvaluationDlg.cpp lines 788 - 815. By this means I quieted a fatal compiler "illegal cast" error. This permits the remainder of the code to compile on Ubuntu/Mint 20 using the standard debmake/debuild procedure. AFAIK this only affects the GPS time set function. This compromise may be acceptable for now. I suspect the cast problem would otherwise be difficult to solve and am not expecting to see much in the way of resolution. The resulting build still dies during run time near file GUI-QT/SoundCardSelMenu.cpp line 218. This may be indirectly related to Pulse Audio. This problem is recognized upstream. For instance, see recent SourceForge Dream tickets, especially 230 just for this problem. A patch/commit is needed to fix before Debian (or other Linux OS) testing can continue. Doubtless upstream would appreciate anyone with debug skills who might help out. I note the new xHE codec may still have problems too. Meanwhile, I have completed most of the "Debian" procedural work necessary to submit for Sponsorship. That done as much as possible, I intend to push what I have to Gitlab Salsa (formerly Alioth) Project 7803 as a new branch, just as an assurance of preservation (hopefully within a few days). Should anything happen to me, anyone may complete updates and testing from there and upload to Debian for Sponsorship. Use the new branch in 7803. I also intend to archive my Dream work at Gitlab Salsa Project 52290, since it now seems redundant to maintain it. 52290 does retain some screenshots that will be useful for submission. I will stand by to help with Dream where possible, and for submission to Debian when complete. Garie Miller Sent with [ProtonMail](https://protonmail.com/) Secure Email.
Christoph I created a new branch for my Dream stuff on project 7803 to keep it in one place. Then I thought I would archive my old one on 52290 (not maintaining it). Well it kicked me off the member list on 7803 but still says "my name is taken". I unarchived 52290 but still the same thing. Sorry. I didn't know it would do that just for archiving an old project. I believe you are an admin. Could you restore me as member on 7803? Of course keep my accounts open as might do some new projects if I ever get Dream done. By the way, I have succeeded in getting Dream to compile and install locally per Debian procedures. It still fails in run time due to a PulseAudio problem. So that task is next. Upstream is aware. Garie Miller WB9AWA Sent with [ProtonMail](https://protonmail.com/) Secure Email.
Re: GMiller Done that, hopefully on the correct project with your correct account name :) Nice! Christoph