[Pkg-utopia-maintainers] Audio Transcription Service Provider

[Rachel Morgan]

Hello,
Do you need someone reliable to transcribe both your short term and
long term projects?  Or do you need an accurate transcript for your
audio or video?    
Allow us to transcribe your audio and provide you accurate
transcripts and let us help you reach your business/project goals through
the help of our transcription services.   
What are our goals with each transcript?   


Speed


Accuracy


Confidentiality


   Each transcript is properly formatted. Strict grammar and
punctuation rules are adhered to and of course, file security is something
we take very seriously.   
Have any transcription queries? Send me a message. Let's discuss
what you need to get done.  We will address any concerns you have.
  
- Professional transcription 
- Accurate and thorough 
- Beautifully transcribed documents. 
- Grammar, spelling and jargon thoroughly checked  

We have transcribed within most industries:   


Medical transcription


Technological


Academic


Lectures


Business


Groups


Legal


Research interviews


 more...   
Skilled with international accents and prompt response.  Our
pricing is better or comparable to individual service provider.  In
addition we also assist in APA Style formatting for research papers. 
Please note we don’t conduct research but assist only in formatting
of the papers.
Regards,Rachel Morgan



___
Pkg-utopia-maintainers mailing list
Pkg-utopia-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers

[Pkg-utopia-maintainers] Bug#910637: installation failure

[Simon McVittie]

Control: tags 910637 = stretch
Control: retitle 910637 Fails to install in lxc container: fork() failed: 
Resource temporarily unavailable
Control: reassign 910637 avahi-daemon 0.6.32-2
Control: affects 910637 libnss-mdns

On Wed, 10 Oct 2018 at 13:56:36 +0200, Harald Dunkel wrote:
> I did not ask for Avahi at all.

Not directly, but libnss-mdns requires avahi-daemon and can't work
without it.

> The unwanted Avahi daemon complains about missing or broken mdns
> support:
> 
>   Failed to start Avahi mDNS/DNS-SD Stack.

Ah, I see. You're misunderstanding that message: "Avahi mDNS/DNS-SD
Stack" is just a description of avahi-daemon (Avahi is an implementation
of the mDNS and DNS-SD protocols). Avahi doesn't require libnss-mdns,
but libnss-mdns requires Avahi.

This looks like the same issue as  so
I'm reassigning it.

Workaround: edit /etc/avahi/avahi-daemon.conf and comment out all the
lines starting with "rlimit-".

smcv

___
Pkg-utopia-maintainers mailing list
Pkg-utopia-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers

[Pkg-utopia-maintainers] Processed: Re: Bug#910637: installation failure

[Debian Bug Tracking System]

Processing control commands:

> tags 910637 = stretch
Bug #910637 [libnss-mdns] installation failure
Added tag(s) stretch; removed tag(s) moreinfo.
> retitle 910637 Fails to install in lxc container: fork() failed: Resource 
> temporarily unavailable
Bug #910637 [libnss-mdns] installation failure
Changed Bug title to 'Fails to install in lxc container: fork() failed: 
Resource temporarily unavailable' from 'installation failure'.
> reassign 910637 avahi-daemon 0.6.32-2
Bug #910637 [libnss-mdns] Fails to install in lxc container: fork() failed: 
Resource temporarily unavailable
Bug reassigned from package 'libnss-mdns' to 'avahi-daemon'.
No longer marked as found in versions nss-mdns/0.10-8.
Ignoring request to alter fixed versions of bug #910637 to the same values 
previously set
Bug #910637 [avahi-daemon] Fails to install in lxc container: fork() failed: 
Resource temporarily unavailable
Marked as found in versions avahi/0.6.32-2.
> affects 910637 libnss-mdns
Bug #910637 [avahi-daemon] Fails to install in lxc container: fork() failed: 
Resource temporarily unavailable
Added indication that 910637 affects libnss-mdns

-- 
910637: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910637
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-utopia-maintainers mailing list
Pkg-utopia-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers

Re: [Pkg-utopia-maintainers] Bug#906016: transition: gjs built with mozjs60

[Emilio Pozuelo Monfort]

Control: tags -1 confirmed

On 10/10/2018 12:41, Simon McVittie wrote:
> On Wed, 10 Oct 2018 at 10:13:32 +0200, Emilio Pozuelo Monfort wrote:
>> On 05/10/2018 10:10, Simon McVittie wrote:
>>> The new mozjs version does not work on s390x, so to make gjs migrate,
>>> we will need to do architecture-specific removals (I'm not sure whether
>>> this should be from testing or unstable) of binaries from at least
>>> [some] source packages
> 
> I assume these removals will need to be requested *after* we have uploaded
> gjs 1.54.x (the branch that uses mozjs60) to unstable, otherwise they
> will just get rebuilt on s390x at their next upload. Is that correct?

Yes.

> When it's time to do those removals, should we be asking the ftp team
> to remove s390x binaries from unstable, or asking the release team to
> remove s390x binaries from testing?

From unstable against the ftp.debian.org metapackage.

>>> Is there a better way we can deal with packages like gdm3 (which require
>>> gnome-shell at runtime) [...] Perhaps a (slightly spurious) Build-Depends
>>> on gjs?
>>
>> A build-dep would be preferred, either on gjs or gnome-shell or whatever you
>> deem appropriate.
> 
> We've been adding build-dependencies on gjs as our way to stop non-working
> s390x binaries from coming back. Jeremy says he'll NMU the various
> Architecture: any GNOME Shell extensions to add this, if necessary.
> 
>> My only question: is cjs moving to mozjs60 too, so that we can remove 
>> mozjs52?
> 
> Not in the short term. Moving to a new mozjs version is a major change
> that needs to be coordinated with cjs upstream. Unfortunately, cjs
> upstream seem to be refusing to consider any request coming from Debian
> until unrelated (?) bugs are fixed in NetworkManager in stable (if I'm
> understanding correctly). See 
> (trigger warning: hostility towards Debian as a project, and Debian
> maintainers as representatives of Debian).
> 
> libproxy1-plugin-mozjs (a proxy-auto-configuration backend for libproxy)
> was recently reintroduced and also uses mozjs52, although meta-gnome3
> still depends on libproxy1-plugin-webkit instead, for its better security
> support. Laurent, was there a particular reason for reintroducing the
> mozjs plugin while we are discussing a move from mozjs52 to mozjs60,
> and would its addition be OK to revert? It seems that it tends to make
> libproxy crash whenever run by a gjs app in a non-GNOME environment:
> . As with cjs,
> porting libproxy to mozjs60 should happen upstream or not at all.
> 
> policykit-1 in experimental also uses mozjs52, so even if gjs, cjs and
> libproxy are all dealt with somehow (ported or removed, as appropriate),
> I would like to keep mozjs52 in unstable until policykit-1 moves to
> mozjs60 (which, again, should happen upstream or not at all). If gjs,
> cjs and libproxy all stop using mozjs52, then it would be OK to remove
> it from testing, and leave it unstable-only for policykit-1's benefit,
> with an artificial RC bug to stop it from migrating.

Ok. We no longer have mozjs or mozjs24 in sid so I can leave with keeping
mozjs52 if necessary. Obviously if those rdeps can be ported for buster, then
all the better.

Please go ahead.

Emilio

___
Pkg-utopia-maintainers mailing list
Pkg-utopia-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers

[Pkg-utopia-maintainers] Bug#910637: installation failure

[Harald Dunkel]

Hi Simon,

I did not ask for Avahi at all. The command line was

apt install libnss-mdns

The unwanted Avahi daemon complains about missing or broken mdns
support:

Failed to start Avahi mDNS/DNS-SD Stack.

My impression was that I cannot install mdns because it relies
upon avahi, and that I cannot install avahi, because it needs
a working mdns. Catch 22.


Regards
Harri

___
Pkg-utopia-maintainers mailing list
Pkg-utopia-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers

[Pkg-utopia-maintainers] Bug#910670: Bug#910670: network-manager-openvpn: unable to import valid configuration file

[Bruno BEAUFILS]

On Tue, Oct 09, 2018 at 04:55:59PM +0200, Michael Biebl wrote:
> Can you attach the .ovpn file to this bug report?

Yes. Attached to this email.

-- 
Bruno BEAUFILS
# Copier-coller à partir d'ici, et modifiez la partie auth-user-pass si vous ne 
voulez pas avoir à taper votre mot de passe à chaque fois.
# 8<--

# C'est nous qui prenons l'initiative de nous connecter au serveur.
client

# On route de l'IP, on ne fait pas de l'ethernet.
dev tun

# Certains réseaux ont en fait une MTU bien inférieure à 1450. Dire aux 
connexions
# TCP d'être très conservatives, pour que ça marche plus ou moins partout.
mssfix 1300
# En UDP, on peut s'assurer que ça passe de toutes façons en fragmentant au 
besoin
# quand ça dépasse.
# fragment 1300
# Idéalement, ça devrait être détecté tout seul, mais c'est loin de toujours 
fonctionner...
# mtu-disc yes

# Il est préférable d'utiliser udp, le résultat fonctionne mieux. Il est
# cependant notable que les restrictions d'accès Internet laissent souvent
# plus facilement passer tcp. Essayer donc udp, et seulement s'il ne fonctionne
# pas, essayer tcp.

# Les adresses des serveurs.

remote vpn.fdn.fr 1194
server-poll-timeout 3
explicit-exit-notify


remote vpn-rw.fdn.fr 53
server-poll-timeout 3
explicit-exit-notify


remote vpn.fdn.fr 1194 tcp
server-poll-timeout 3 


remote vpn-rw.fdn.fr 80 tcp
server-poll-timeout 3


remote vpn-rw.fdn.fr 443 tcp
server-poll-timeout 3


remote vpn-rw.fdn.fr 993 tcp
server-poll-timeout 3


remote vpn-rw.fdn.fr 22 tcp
server-poll-timeout 3

# Cette dernière tentative implique la mise en place de stunnel: 
https://wiki-adh.fdn.fr/travaux:stunnel et vous permet de passer à travers de 
nombreux réseau.
# Néanmoins, cela doit rester une solution de dernier recours car:
# 1- le débit se trouve fortement réduit
# 2- cela mobilise beaucoup plus de ressources serveur

remote 127.0.0.1 11944 tcp
server-poll-timeout 10



# Éventuellement, on peut avoir besoin de passer par un proxy http, décommenter 
cette ligne en mettant l'adresse et le port du proxy.
#http-proxy 192.0.2.1 8080

# Pour windows: utiliser route.exe.
route-method exe

# Attendre un peu avant d'ajouter les routes.
route-delay 2

# Ne pas utiliser un port local statique, on est client de toutes façons.
nobind

# Garder la clé en mémoire, pour ne pas avoir besoin de la relire lors d'un
# redémarrage.
persist-key
# On peut éventuellement ne pas tuer l'interface du tunnel lors d'un 
redémarrage, mais cela pose problème pour
# résoudre le nom de domaine du serveur si les résolutions DNS passent par le 
VPN, et aussi si au redémarrage
# on change de serveur (changement de passerelle).
#persist-tun

# Faire passer tout le trafic via le VPN:
redirect-gateway def1
# Mais pas le trafic local:
route 10.0.0.0 255.0.0.0 net_gateway
route 172.16.0.0 255.240.0.0 net_gateway
route 192.168.0.0 255.255.0.0 net_gateway
# Ajouter éventuellement d'autres routes locales, par exemple vers votre cache 
DNS

# Activer IPv6
tun-ipv6
# et faire passer tout le trafic IPv6 via le VPN:
route-ipv6 ::/1
route-ipv6 8000::/1

# On peut aussi vouloir plutôt router seulement quelques destinations, par
# exemple ici tout Gitoyen:
#route 80.67.160.0 255.255.224.0

# Envoyer un login et un mot de passe. Pour éviter de taper à la main login
# et mot de passe, vous pouvez ajouter à droite de "auth-user-pass" le nom d'un
# fichier contenant ces deux informations, une par ligne.
auth-user-pass

# Un minimum de debug, c'est toujours bien.
verb 3

# Certificat permettant de vérifier que c'est bien à FDN que
# l'on se connecte et donc à qui on donne notre mot de passe.
verify-x509-name *.fdn.fr name

-BEGIN CERTIFICATE-
MIIHPTCCBSWgAwIBAgIBADANBgkqhkiG9w0BAQQFADB5MRAwDgYDVQQKEwdSb290
IENBMR4wHAYDVQQLExVodHRwOi8vd3d3LmNhY2VydC5vcmcxIjAgBgNVBAMTGUNB
IENlcnQgU2lnbmluZyBBdXRob3JpdHkxITAfBgkqhkiG9w0BCQEWEnN1cHBvcnRA
Y2FjZXJ0Lm9yZzAeFw0wMzAzMzAxMjI5NDlaFw0zMzAzMjkxMjI5NDlaMHkxEDAO
BgNVBAoTB1Jvb3QgQ0ExHjAcBgNVBAsTFWh0dHA6Ly93d3cuY2FjZXJ0Lm9yZzEi
MCAGA1UEAxMZQ0EgQ2VydCBTaWduaW5nIEF1dGhvcml0eTEhMB8GCSqGSIb3DQEJ
ARYSc3VwcG9ydEBjYWNlcnQub3JnMIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIIC
CgKCAgEAziLA4kZ97DYoB1CW8qAzQIxL8TtmPzHlawI229Z89vGIj053NgVBlfkJ
8BLPRoZzYLdufujAWGSuzbCtRRcMY/pnCujW0r8+55jE8Ez64AO7NV1sId6eINm6
zWYyN3L69wj1x81YyY7nDl7qPv4coRQKFWyGhFtkZip6qUtTefWIonvuLwphK42y
fk1WpRPs6tqSnqxEQR5YYGUFZvjARL3LlPdCfgv3ZWiYUQXw8wWRBB0bF4LsyFe7
w2t6iPGwcswlWyCR7BYCEo8y6RcYSNDHBS4CMEK4JZwFaz+qOqfrU0j36NK2B5jc
G8Y0f3/JHIJ6BVgrCFvzOKKrF11myZjXnhCLotLddJr3cQxyYN/Nb5gznZY0dj4k
epKwDpUeb+agRThHqtdB7Uq3EvbXG4OKDy7YCbZZ16oE/9KTfWgu3YtLq1i6L43q
laegw1SJpfvbi1EinbLDvhG+LJGGi5Z4rSDTii8aP8bQUWWHIbEZAWV/RRyH9XzQ
QUxPKZgh/TMfdQwEUfoZd9vUFBzugcMd9Zi3aQaRIt0AUMyBMawSB3s42mhb5ivU
fslfrejrckzzAeVLIL+aplfKkQABi6F1ITe1Yw1nPkZPcCBnzsXWWdsC4PDSy826
YreQQejdIOQpvGQpQsgi3Hia/0PsmBsJUUtaWsJx8cTLc6nloQsCAwEAAaOCAc4w
ggHKMB0GA1UdDgQWBBQWtTIb1Mfz4OaO873SsDrusjkY0TCBowYDVR0jBIGbMIGY
gBQWtTIb1Mfz4OaO873SsDrusjkY0aF9pHsweTEQMA4GA1UEChMHUm9vdCBDQTEe

[Pkg-utopia-maintainers] Bug#910728: network-manager-openvpn-gnome: TLS authentication does not get saved

[Christoph Haas]

Package: network-manager-openvpn-gnome
Version: 1.8.6-1
Severity: important

Dear Maintainer,

suddenly the TLS authentication feature with an additional key file
and the key direction is dropped from the configuration.

I can re-enter the information and save but when opening the config
dialog again that information is gone. I cannot use OpenVPN connections
that require TLS pre-authentication any more.

*** Reporter, please consider answering these questions, where appropriate ***

   * What led up to the situation?
   * What exactly did you do (or not do) that was effective (or
 ineffective)?
   * What was the outcome of this action?
   * What outcome did you expect instead?

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: buster/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-rc2+ (SMP w/4 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8), 
LANGUAGE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages network-manager-openvpn-gnome depends on:
ii  libc62.27-6
ii  libglib2.0-0 2.58.1-2
ii  libgtk-3-0   3.24.1-2
ii  libnm0   1.12.4-1
ii  libnma0  1.8.18-2
ii  libsecret-1-00.18.6-3
ii  network-manager-openvpn  1.8.6-1

network-manager-openvpn-gnome recommends no packages.

network-manager-openvpn-gnome suggests no packages.

-- no debconf information

___
Pkg-utopia-maintainers mailing list
Pkg-utopia-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers

[Pkg-utopia-maintainers] flatpak-builder_1.0.1-1~bpo9+1_source.changes ACCEPTED into stretch-backports

[Debian FTP Masters]

Accepted:

-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256

Format: 1.8
Date: Thu, 04 Oct 2018 18:53:47 +0100
Source: flatpak-builder
Binary: flatpak-builder flatpak-builder-tests
Architecture: source
Version: 1.0.1-1~bpo9+1
Distribution: stretch-backports
Urgency: medium
Maintainer: Utopia Maintenance Team 

Changed-By: Simon McVittie 
Description:
 flatpak-builder - Flatpak application building helper
 flatpak-builder-tests - Application deployment framework for desktop apps 
(tests)
Changes:
 flatpak-builder (1.0.1-1~bpo9+1) stretch-backports; urgency=medium
 .
   * Rebuild for stretch-backports.
 - debian/gbp.conf: Adjust for this branch
 .
 flatpak-builder (1.0.1-1) unstable; urgency=medium
 .
   * New upstream release
   * Standards-Version: 4.2.1
   * Install the upstream NEWS and README.md files
   * d/flatpak-builder-tests.lintian-overrides: Silence some overzealous
 package-contains-documentation-outside-usr-share-doc tags
Checksums-Sha1:
 39c9c1286ca336cdb5604b6ec65ad26461532dad 2817 
flatpak-builder_1.0.1-1~bpo9+1.dsc
 e1e131a2462b442cded33c3a93dd507f98136ef0 5888 
flatpak-builder_1.0.1-1~bpo9+1.debian.tar.xz
 40f95aa61a18ef5419728fe86a29b2512a362e80 10409 
flatpak-builder_1.0.1-1~bpo9+1_source.buildinfo
Checksums-Sha256:
 44d1117fda13339c1f2ecc01c8d23fd9e541aa0642d8561985cb14e3d91d74cd 2817 
flatpak-builder_1.0.1-1~bpo9+1.dsc
 ca5e85955eb44acb132b6100c3804315d194b5116777f39bfb9a1a337b43bd3c 5888 
flatpak-builder_1.0.1-1~bpo9+1.debian.tar.xz
 5549f7b075d165594360c2f1f94f2988210916ad77140a0a44d39fdfd4c8feef 10409 
flatpak-builder_1.0.1-1~bpo9+1_source.buildinfo
Files:
 82f435721c4904b5a581552f9e1bddb8 2817 devel optional 
flatpak-builder_1.0.1-1~bpo9+1.dsc
 821d1aa9182f79bf4c82ed270f05b3ec 5888 devel optional 
flatpak-builder_1.0.1-1~bpo9+1.debian.tar.xz
 61d5d63dde9af43cb828ea5b33b6ca49 10409 devel optional 
flatpak-builder_1.0.1-1~bpo9+1_source.buildinfo

-BEGIN PGP SIGNATURE-

iQIzBAEBCAAdFiEENuxaZEik9e95vv6Y4FrhR4+BTE8FAlu80YMACgkQ4FrhR4+B
TE8fxQ//amJbrmx9WBwQ0aBwiBhcDhyTcZaGh0s9kioY+fRTUO2ZqSCpk5xWOd8R
OhNY6PG8S40Kldznuv2PtU8QFuvxL0l5GWT3ZMIhw+doycaD/rNa0LKg3gSNEwt1
hMg0mwHmh/1DreltiHUSn8vCYxPuy2nvgGZiE7sm46lcDvkhut7deo2lGKoMVvzn
e12GGN/cdJUguPtz2ZVdcEwJVE2yr4EhgnrB/CWlErAeykioW0D+BOp58bCX3z9z
i/XKACH5xXfcBIxYWW/blUL04iSslQdyPJUv9JQj0tAlzCoaIxVMzkt/92zpOrqr
gEGHtz8XyKvXqU3c/UkTDs4SR+B8WL2tu7/XFpukHnb+Y2YYxhgZr/XdGmp76Cuu
4GZhS67ZV6G7cHlNT5wafg+VYRPX7OW3bavSIxkdg7BOEvzcu/dfEKJ7VHZKMMy5
84+s85wqHqZcGQPNwpbNfEoVApiRWTXtk0DU1OK5LHPBNlpwffLGyt1AS+AAsvDR
e9WRJg/5Sfsg57F5XkZq4F8JWPI499z0Ao31iGC55qSGpvD/RSIfr4q79Ew4+RUH
rJap3z531iJ6aFOWQr2NUDV/E0XGKgHcAJA0Q6RblQDuK/QDNwUezjfqHynGobWK
Oc7ezMdvden1jW66vF4+xe/qHutFSrSEZzca8roNS8Hz+FqFfzQ=
=B1BC
-END PGP SIGNATURE-


Thank you for your contribution to Debian.

___
Pkg-utopia-maintainers mailing list
Pkg-utopia-maintainers@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-utopia-maintainers