Re: [ubuntu-studio-devel] Fwd: Bug#888657: ladish: should this package be removed?

2018-01-28 Thread Len Ovens

On Sun, 28 Jan 2018, Ross Gammon wrote:


It is very likely that ladish/gladish will be removed from the Debian archive
soon, as it is not maintained upstream, and needs to be ported away from GTK2.

Whilst we can probably keep it a little longer in Ubuntu, unless someone steps 
up
to take over maintenance (and do the porting work), it will be lost eventually.


Best to let it go. The current maintainer has suggested that it will not 
be updated and deserves retirement. The New thing in session managers is 
NSM... also not being taken care of and not in the debian repos anyway.


--
Len Ovens
www.ovenwerks.net


--
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel


Fwd: heads up: new bind9 from debian drops lwresd

2018-01-28 Thread Andreas Hasenack
Hi,

the new bind9 packages from debian 
dropped the lightweight resolver (lwres) in version 1:9.11.2+dfsg-1:

  * Remove lwresd as it has been deprecated by upstream anyway


Upstream dropped it in bind 9.12.x, but it still exists in the 9.11 code
base:

http://ftp.isc.org/isc/bind9/9.12.0/RELEASE-NOTES-bind-9.12.0.html

   - The lightweight resolver daemon and library (lwresd and liblwres) have
   been removed. [RT #45186]

I checked ubuntu bionic and the only thing depending on the lwresd package
is libnss-lwres, and libnss-lwres is not required by anything else.

Both lwresd and libnss-lwres are in universe.

rmadison shows libnss-lwres has been at verison 0.93 since precise at
least. It seems to come from here nowadays: ftp://sources.
redhat.com/pub/glibc/old-releases/ (that directory path is a hint).

It's very likely we will follow Debian on this, but I wanted to reach out
first to see if there are any objections, heavy users of this resolver,
etc. I don't think we need yet another resolver, but better check.

Thanks
-- 
ubuntu-devel mailing list
ubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel


Re: [ubuntu-studio-devel] Fwd: Bug#888657: ladish: should this package be removed?

2018-01-28 Thread Ralf Mardorf
On Sun, 28 Jan 2018 17:37:27 +0100, Ralf Mardorf wrote:
>On Sun, 28 Jan 2018 16:52:45 +0100, Ross Gammon wrote:
>>Hi All,
>>
>>It is very likely that ladish/gladish will be removed from the Debian
>>archive soon, as it is not maintained upstream, and needs to be ported
>>away from GTK2.
>>
>>Whilst we can probably keep it a little longer in Ubuntu, unless
>>someone steps up to take over maintenance (and do the porting work),
>>it will be lost eventually.
>>
>>Do we have good alternatives?
>
>We always had the best alternative over all those session manager crap,
>by writing a script to launch apps, move them to the wanted workspace,
>make connections for everything, as long as MIDI interfaces shouldn't
>share the same name. However, when e.g. using two or more identical
>envy24 PCI cards as MIDI interfaces, there anyway is no solution to
>handle the issue, other than each time after a session was started, to
>manually reconnect all MIDI connections. Appart from writing scripts,
>audio session managment never was a Linux domain, IOW ladish/gladish
>and Co. (Claudia), was crap from the very beginning. Nice for me Linux
>audio misfit to hear that I'm proven right and all the loud-mouth hobby
>engineers at LAU are proven wrong, since it's plausible that nowbody
>wants to maintain this crap. It's not nice that GTK2 seems to go the
>way of the dodo bird, since GTK3 is garbage, e.g. see
>https://lists.ubuntu.com/archives/ubuntu-users/2018-January/293310.html
>and
>https://lists.ubuntu.com/archives/ubuntu-users/2018-January/293311.html
>and follow-ups.
>

Or take a look at
https://mail.gnome.org/archives/evolution-list/2018-January/msg00123.html
and follow-ups.

The only good news is that even the completely broken discontinued
ROXTerm still is more usable than all other VTE-based and not
VTE-based GUI terminal emus.

-- 
https://www.schneier.com/blog/archives/2018/01/spectre_and_mel_1.html

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel


Re: [ubuntu-studio-devel] Fwd: Bug#888657: ladish: should this package be removed?

2018-01-28 Thread Ralf Mardorf
On Sun, 28 Jan 2018 16:52:45 +0100, Ross Gammon wrote:
>Hi All,
>
>It is very likely that ladish/gladish will be removed from the Debian
>archive soon, as it is not maintained upstream, and needs to be ported
>away from GTK2.
>
>Whilst we can probably keep it a little longer in Ubuntu, unless
>someone steps up to take over maintenance (and do the porting work),
>it will be lost eventually.
>
>Do we have good alternatives?  

We always had the best alternative over all those session manager crap,
by writing a script to launch apps, move them to the wanted workspace,
make connections for everything, as long as MIDI interfaces shouldn't
share the same name. However, when e.g. using two or more identical
envy24 PCI cards as MIDI interfaces, there anyway is no solution to
handle the issue, other than each time after a session was started, to
manually reconnect all MIDI connections. Appart from writing scripts,
audio session managment never was a Linux domain, IOW ladish/gladish
and Co. (Claudia), was crap from the very beginning. Nice for me Linux
audio misfit to hear that I'm proven right and all the loud-mouth hobby
engineers at LAU are proven wrong, since it's plausible that nowbody
wants to maintain this crap. It's not nice that GTK2 seems to go the
way of the dodo bird, since GTK3 is garbage, e.g. see
https://lists.ubuntu.com/archives/ubuntu-users/2018-January/293310.html
and
https://lists.ubuntu.com/archives/ubuntu-users/2018-January/293311.html
and follow-ups.

-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel


[ubuntu-studio-devel] Fwd: Bug#888657: ladish: should this package be removed?

2018-01-28 Thread Ross Gammon
Hi All,

It is very likely that ladish/gladish will be removed from the Debian
archive soon, as it is not maintained upstream, and needs to be ported
away from GTK2.

Whilst we can probably keep it a little longer in Ubuntu, unless someone
steps up to take over maintenance (and do the porting work), it will be
lost eventually.

Do we have good alternatives?

Regards,

Ross

On 01/28/2018 04:18 PM, James Cowgill wrote:

> Hi,
>
> On 28/01/18 14:16, treb...@tuxfamily.org wrote:
>> Le 2018-01-28 14:38, Simon McVittie a écrit :
>>> Source: flowcanvas
>>> Severity: important
>>> User: debian...@lists.debian.org
>>> Usertags: proposed-removal
>>> Control: clone -1 -2
>>> Control: reassign -2 ladish
>>> Control: retitle -2 ladish: should this package be removed?
>>>
>>> flowcanvas depends on numerous obsolete GNOME 2-era libraries
>>> (e.g. #885095) and hasn't had a maintainer upload since 2009. Its
>>> upstream
>>> website says:
>>>
>>>     **Note**: FlowCanvas is dead, long live Ganv!
>>>
>>> ganv is also in Debian as src:ganv; it's orphaned in Debian, but appears
>>> to have commit activity upstream.
>>>
>>> flowcanvas has one reverse-dependency in Debian, gladish (src:ladish),
>>> whose most recent maintainer upload was in 2014. web.archive.org says
>>> the ladish.org website has been down since mid 2014.
>> ladish looks to be maintained by alessio (last commit 20 Apr 2017) here :
>> https://github.com/alessio/ladish/
>> (the same goes laditools as well)
> You failed to mention that there has only been one non-merge commit to
> that repository since 2014.
>
> The truth is unless someone is willing to do the porting work, these
> packages are not going to survive whether they are "maintained" or not.
>
> James
>
>
>
> ___
> pkg-multimedia-maintainers mailing list
> pkg-multimedia-maintain...@lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers




 Forwarded Message 
Subject:Bug#888657: ladish: should this package be removed?
Resent-Date:Sun, 28 Jan 2018 15:21:07 +
Resent-From:James Cowgill 
Resent-To:  debian-bugs-d...@lists.debian.org
Resent-CC:  Debian Multimedia Maintainers

Date:   Sun, 28 Jan 2018 15:18:47 +
From:   James Cowgill 
Reply-To:   James Cowgill , 888...@bugs.debian.org
To: treb...@tuxfamily.org, 888...@bugs.debian.org



This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--AA3wuwQJSNwemsa02U8VM82aeUyfz5se2
Content-Type: multipart/mixed; boundary="1YV4OwYIGUSyBHwRCivLLmp4QKWC5OJpX";
 protected-headers="v1"
From: James Cowgill 
To: treb...@tuxfamily.org, 888...@bugs.debian.org
Message-ID: <11a6d485-873f-cc85-95e9-85d0883d2...@debian.org>
Subject: Re: Bug#888657: ladish: should this package be removed?
References: <20180128133835.ga30...@perpetual.pseudorandom.co.uk>
 <3bf1d8b4332cfb002543a077da7ab...@tuxfamily.org>
 <20180128133835.ga30...@perpetual.pseudorandom.co.uk>
 
In-Reply-To: 

--1YV4OwYIGUSyBHwRCivLLmp4QKWC5OJpX
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Hi,

On 28/01/18 14:16, treb...@tuxfamily.org wrote:
> Le 2018-01-28 14:38, Simon McVittie a =C3=A9crit=C2=A0:
>> Source: flowcanvas
>> Severity: important
>> User: debian...@lists.debian.org
>> Usertags: proposed-removal
>> Control: clone -1 -2
>> Control: reassign -2 ladish
>> Control: retitle -2 ladish: should this package be removed?
>>
>> flowcanvas depends on numerous obsolete GNOME 2-era libraries
>> (e.g. #885095) and hasn't had a maintainer upload since 2009. Its
>> upstream
>> website says:
>>
>> =C2=A0=C2=A0=C2=A0 **Note**: FlowCanvas is dead, long live Ganv!
>>
>> ganv is also in Debian as src:ganv; it's orphaned in Debian, but appea=
rs
>> to have commit activity upstream.
>>
>> flowcanvas has one reverse-dependency in Debian, gladish (src:ladish),=

>> whose most recent maintainer upload was in 2014. web.archive.org says
>> the ladish.org website has been down since mid 2014.
>=20
> ladish looks to be maintained by alessio (last commit 20 Apr 2017) here=
 :
> https://github.com/alessio/ladish/
> (the same goes laditools as well)

You failed to mention that there has only been one non-merge commit to
that repository since 2014.

The truth is unless someone is willing to do the porting work, these
packages are not going to survive whether they are "maintained" or not.

James


--1YV4OwYIGUSyBHwRCivLLmp4QKWC5OJpX--

--AA3wuwQJSNwemsa02U8VM82aeUyfz5se2
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-BEGIN PGP SIGNATURE-


[ubuntu-studio-devel] Testing Team Leader Role in Ubuntu Studio

2018-01-28 Thread Ross Gammon
Hi All,

This is a call for assistance with Testing in Ubuntu Studio.

I am currently finding it very difficult to put the time I would like
into fulfilling the role I took on some time ago, to be the Test Team
Lead for Ubuntu Studio. Therefore, I am looking for volunteers to join
the team (if not members already), and take over as Test Team Leader
after 18.04 (Bionic) LTS is released.

There is some information about the team on the wiki here:
https://wiki.ubuntu.com/UbuntuStudio/TestingTeamPage

There is also a need to be available for release tasks during the times
we are working on the next release, or there is an update to an LTS
release. Some of the things that need to be done for a release are
listed here:
https://wiki.ubuntu.com/UbuntuStudio/DevEvents/Release

As a summary, the role involves:
- Managing the Manual Test Cases at http://packages.qa.ubuntu.com/
- Being the Release Manager at the appropriate points in the test cycle:
http://iso.qa.ubuntu.com/
https://wiki.ubuntu.com/BionicBeaver/ReleaseSchedule
- Announcing the coming tests and encouraging others to take part in the
tests.
- Triaging bugs found during the test campaigns.
- Writing the Release Notes & helping the documentation team with text
for the announcements.

I still plan to be a member of the team to help out where I can, and to
assist the new Test Lead develop into the role. But would like to spend
what spare time I have, concentrating on getting more evidence of
uploads to Ubuntu for my Developer application.

If you would like to help out, please apply to be a member of the
testing team on Launchpad (https://launchpad.net/~ubuntustudio-testing),
and let us know on the developers list that you would like to volunteer.

Lets all chip in to help make the next (and future) Ubuntu Studio
releases a success.

Regards,

Ross Gammon
US Test Team Lead



signature.asc
Description: OpenPGP digital signature
-- 
ubuntu-studio-devel mailing list
ubuntu-studio-devel@lists.ubuntu.com
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-devel