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
Hello Christoph
>Re: GMiller > 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 n
Installing 'libmono-system-windows-forms4.0-cil' with it's depends solved the
immediate problem. Perhaps I should have installed the -devel package to run my
mono application.
Looking closer I also see Ubuntu is behind Debian in the stable mono release.
Garie Miller
Sent with
Package: mono
Version: 6.8.0.105+dsfg-2
Maintainers: Debian Mono Group
Attempting to run a mono application on command line returns:
Unhandled Exception:
System.IO.FileNotFoundException: Could not load file or assembly
'System.Windows.Forms, Version=4.0.0.0, Culture=neutral,
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
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
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
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
(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
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.
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://g...@salsa.debian.org:debian-hamradio-team/dream.git master
It responded with:
ssh: Could not resolve hostname
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://g...@salsa.debian.org:debian-hamradio-team/dream.git master
It gave two errors, the second in red:
error: src
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)
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,
TNX Christoph
OK I have just established an account on Salsa. The particulars are:
Full Name
Garie Miller
Username
GMiller
Email
gmill...@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
Package: libqtcore4
Version: 4:4.8.7+dsfg-18_amd64.deb
Maintainer: Debian Qt/KDE Maintainers
libqtcore4.deb fails to install when using 'gdebi', giving messages like
'installation failed', 'failed to install all dependencies' and 'Error: Failed
to satisfy all dependencies (broken cache)'.
Hello:
Yes I was aware of the non-GPL license of fdk-aac and the non-free
implications that you mentioned.
I had a short paragraph on that point in my original join request, but
ironically the email got lost during 'save'! When I retyped the
request I forgot to include it (and maybe some
Hello:
I hereby request permission to try to package fdk-aac 2.0.1. This
package also includes libfdk-aac-dev, which currently references
Bug#915386.
My motivation for joining the Multimedia Team is solely the completion
of another Debian Bug#907576. I do not foresee much involvement with
Hello Sebastian:
OK I will give that a try.
A few questions. Bug915386 is just a heads up. It is not really an RFP.
Should I post an RFP or ITP to get things started? Do you suggest
anyone to contact to assemble a 'team'?
Thank you for the offer. If we succeed we will contact you for
Hello:
For your information, below is the posting I made to the subject Debian
Bug#915386:
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
Hello:
For your information, below is the posting that I made to the subject
Debian Bug#915386:
Completion of Dream Bug#907576 requires the newer codec of
libfdk-aac-dev 2.2.0, which has also been requested by Bug#915386
(latest at Github is 2.0.1). Dream cannot function properly with
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
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
--
Take back your privacy. Switch to 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
--
Take back your privacy. Switch to www.StartMail.com
Hello Jiangzu Kumquat and Christoph,
Concerning your subject email on debian-h...@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
Package: hamradio-maintguide
Version: 0.4
Severity: normal
Maintainer: Debian Hamradio Maintainers
Clicking on subject link gives server not found error. Link on
DebianHam web page is also broken.
Garie Miller wb9awa
--
Take back your privacy. Switch to www.StartMail.com
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
27 matches
Mail list logo
