Am 29.02.20 um 16:33 schrieb Mike Gabriel:
> Until now, I mostly avoided writing .symbols files for C++ shared libs.
Solve the problem, but let some maybe important informations pass through.
> But I am now. Thanks to all pkg-kde-tools hackers for the symbols
> helper. Much appreciated.
A maybe a
Hi Otto,
i'm doing this for years now (LXQt)
To sum it up:
* there are no special rules, but i suggest to keep your hats strictly
separated
* if there are some doubts upstream - just think how you would feel with
a release with your downstream hat on
* if you release something upstream and have t
Am 08.02.20 um 16:15 schrieb Svante Signell:
>
> Anything else?
>
Yes, you forget something - as long the discussion culture in Debian
stays this way i'm not motivated to start my NM process again. Waste of
time to join a bunch of unripe kids. Sorry, but i find no other words
with my limited en
On 01.11.19 02:33, Thomas Goirand wrote:
...the bigger question is: why systemd-sysusers is part of systemd, and
not a standalone thing, which we could make an essential package. If we
want it to be part of a package standard toolkit, it means systemd
becomes an essential package, which isn't
k on it.
> As much as I understand, we never wrote or decided we would. We just
> need to accept patches to add or fix sysv-rc scripts. What makes you
> think sysv-rc scripts are mandatory?
Good question - if these things are not mandatory nothing needs to
change.
>
> Thomas Goirand (zigo)
>
--
Alf Gaida
BDBF C688 EFAD BA89 5A9F 464B CD28 0A0B 4D72 827C
Package: wnpp
Severity: wishlist
Owner: Alf Gaida
* Package name: lxqt-organizer
Version : 0.1.0
Upstream Author : crispinalan
* URL : https://github.com/lxqt/lxqt-organizer
* License : LGPL
Programming Lang: C++
Description : LXQt Pim, right now only
On 06.10.19 08:18, Attila Szalay wrote:
> That option means that the system will create not only the binary
> .amd.changes but another changes too which contains only the source
> packages. And I would like to use this method to be sure the package
> compiles, to be able to run the lintian agains
On 05.10.19 23:14, Andrey Rahmatullin wrote:
> On Sat, Oct 05, 2019 at 10:02:54PM +0200, Alf Gaida wrote:
>>>> that is miss something - my point is: Why do you invoke pbuilder (read
>>>> the same question about sbuild too) to create pure source packages?
>>&g
On 05.10.19 21:48, Andrey Rahmatullin wrote:
> On Sat, Oct 05, 2019 at 08:06:56PM +0200, Alf Gaida wrote:
>> that is miss something - my point is: Why do you invoke pbuilder (read
>> the same question about sbuild too) to create pure source packages?
> To make sure they bui
On 05.10.19 19:48, Attila Szalay wrote:
> Hi,
>
> I'm struggling with it for a while now and I couldn't find the
> solution. I have a package maintained with git-buildpackage. And now,
> that I "cannot" upload binary packages I tried to compile the new
> version with the option to create a source
Sorry Gary,
i just make a mistake - you can't relicense MIT(X11) stuff - it would
work only with some BSD files. You could modify the license (just as in
ncurses) and be done with - i would like to recommend not to do so.
Cheers
Alf
Plain no. If they are really interested they would know that they can
use every MIT part under GPL because of license compatibilty. Things
change dramatically if you would consider to change the licenses of the
files - if one would contribute to your now forked files the original
project would have
On 15.09.19 00:05, Russ Allbery wrote:
> We have more agreement here, although there are a lot of details hidden in
> what "forcing" really means. But there's a huge space between "don't
> force other people to use non-free software to contribute to Debian" and
> "forbid using non-free software
nd, i will be verbose about - with
every contributor who will left debian alone after me. Promised.
Before there are false assumtions that i'm searching any consensus in
this unbelivable bullshit - no - i don't. I'll only stepping aside
and see debian and debians ideas die. An cry si
s Software in the sense of DFSG - so the servers we are running should
be allowed to use the newest firmware and processor patches they need)
Cheers Alf
> Thomas Goirand (zigo)
>
--
Alf Gaida
BDBF C688 EFAD BA89 5A9F 464B CD28 0A0B 4D72 827C
On 13.09.19 17:55, Russ Allbery wrote:
> There seems to be an obvious ordering issue here, namely that it's very
> weird to insist on the first (which has been the topic of this thread)
> before we insist on the second.
I wouldn't see it as an ordering issue - my POV is that each of these
issues
On 13.09.19 15:10, Simon Richter wrote:
> Hi,
>
> On Fri, Sep 13, 2019 at 02:51:47PM +0200, Alf Gaida wrote:
>
>> Is it really so hard to understand? Github, Gitlab and other service are
>> just tools. I don't care if they are free or non-free.
> For Debian, fr
On 9/13/19 10:18 AM, Bastian Blank wrote:
> On Thu, Sep 12, 2019 at 06:34:42PM +0200, Alf Gaida wrote:
>> Regarding the workflow and participation - it might be a problem that
>> one need an account for github or other non-free services - it's easy:
> You also need accou
github or bitbucket as non-free - in
this case please drop the whole LXQt from debian, we will continue to
use github.com in near future and are not planning a change right now.
Cheers Alf
--
Alf Gaida
BDBF C688 EFAD BA89 5A9F 464B CD28 0A0B 4D72 827C
important python2 projects that are not migrated
right now - and i will migrate them if really needed because it is no
fun to do so - so it depends on Debian - but i'm dead without both
projects, so i'm in fact prepared, only to lazy to do it now.
> thanks,
> Ian.
>
Cheers Alf
--
Alf Gaida
BDBF C688 EFAD BA89 5A9F 464B CD28 0A0B 4D72 827C
Package: wnpp
Severity: wishlist
Owner: Alf Gaida
* Package name: lxqt-kcm-integration
Version : 0.0.1
Upstream Author : Alf Gaida
* URL : https://github.com/lxqt/lxqt-kcm-integration
* License : (LGPL2+)
Programming Lang: (desktop files)
Description
Am Mittwoch, den 28.08.2019, 17:57 +0200 schrieb Thomas Goirand:
> However, there's still a way too much web interaction with it, compared
> to what we do with a simple "git review" with gerrit.
Not we - you. Please don't expect that people have the same opinion. I like any
kind of nice interfaces.
changelog functionality, this will
come later. And with right written commits it should work well with the
Debian BTS - so best of both worlds.
Cheers
--
Alf Gaida
BDBF C688 EFAD BA89 5A9F 464B CD28 0A0B 4D72 827C
eral times. Ok - i had no
problem with the 30 y.o. things and pull requests - there was no SCM
involved.
--
Alf Gaida
BDBF C688 EFAD BA89 5A9F 464B CD28 0A0B 4D72 827C
Am Dienstag, den 27.08.2019, 19:18 +0200 schrieb Adam Borowski:
> New stuff is always better. Go Electron!
>
Like it or not - the idea of pull requests (Github) or merge requests (Gitlab)
isn't exactly new. It might surprise you that people outside of debian are used
to use it a lot. Anyways, it'
alsa, it seems to me that using merge requests is
common sense and should not need any mention. Otherwise - if one is
happy to send patches via BTS - why not, as long one don't bother me
with. And this it a two way thing - i will not bother other people with
patches via BTS (nicer for: if not
On 09.08.19 12:06, Ansgar wrote:
>
> Having sysvinit might make things a bit easier for Hurd/kFreeBSD, but
> it's not an absolute requirement for such a port to exist.
>
> Ansgar
>
Thanks Ansgar, this is the user deep in me - i like things to easy as
possible. More verbose: I will apply all patch
On 09.08.19 15:51, Tomas Pospisek wrote:
>
> FWIW (I mean it, this is just anecdotical evidence): I have been
> recently upgrading a lot of containers and host and I have been unable
> to make lxc guest with systemd inits even start.
>
> Also, I have been having problems with ssh sessions taking
i - i just use it - and i'm happy that it
goes out of my way most of the time - on desktop and servers. And i'm
an old fart, so i know the time before systemd well - to be honest, if
someone would turn back time i would abandon Linux and go back to some
sane system like Windows. I just don&#
On 07.08.19 19:00, Marc Haber wrote:
> Marc, who is trying to have neutral view on systemd and has managed to
> be seen as a fanboi by systemd haters and as a hater by the systemd
> community, and now fully expects the CoC to be used to be silenced
Marc, i don't hope so - you are not alone. Fo
On Wed, Jul 03, 2019 at 01:49:13PM +0100, Ian Jackson wrote:
> The main difficulty now with getting dgit push adopted is that
> maintainers don't see the benefit *to themselves* and it is always
> harder to get someone to see a benefit *to someone else*.
Ok, that describe me. I see benefits in an
It will confuse me because in 2021 I will expect release 2021 .
Furthermore, will .7 stand for July ?
I assume it's about point releases (which, again, Ubuntu doesn't do
AFAIK).
The keyword will be education - i wrote some times ago: Let people use
wht they are happy with - it will take a blog
Only a last thought: Didn't we have really important problems to solve?
It might be only me, but i see the discussion as a minor variation of
bike shedding.
To sum it up: Some people like codenames, some not, same for numbers -
the real question is: Does it really matters?
Over and out
Alf
On 25.06.19 17:48, Michael Stone wrote:
oldoldstable has the value of demonstrating some of what's wrong with
the current system
Can you please explain, i don't get it - maybe i to new at this. For me
file like /etc/apt/sources.lists.d/debian.list:
deb http://ftp.debian.org/debian/ old
Only a few remarks as former simple user and now maintainer:
* Please don't mix things: release names has a value, distribution names
like oldoldstable, oldstable, stable, testing, unstable has their value too
* the value is that they never change - they are convenient. Especially
if one use uns
> A guest account in Debian LDAP does not get a Salsa account, at least
> not an usable one. Currently only users in the Debian group are
> allowed.Hmm - so salsa is useless at all - i don't think so. Change
your pov and see it otherwise: A guest can open a project - all members
of the Debian g
I think such a GR would be a collosal waste of time. This issue is
not important enough. In particular, because the consensus is *not*
GR's can be man made a collosal waste of time.
Well, a GR can be quick and it would help to know where people stand
instead of having a few vocal people decid
On 13.05.19 15:39, Holger Levsen wrote:
Maybe we could also make the "should" stronger:
- new packages (except if they are ment to become build-depends of
debhelper)*must* either use dh or cdbs.
- old packages should be switched to dh (or cdbs).
And then turn this "should" into a "must" for
On 13.04.19 15:07, Andrey Rahmatullin wrote:
On Sat, Apr 13, 2019 at 12:59:19PM +, Holger Levsen wrote:
I see no point whatsoever in 3.0 (native).
What's the point/advantage of native packages?
No need to make a separate orig tarball.
Can't agree more, there are places where 3.0 (quilt|git
DUR is fine, DPA is fine PPA is not - as it is used before in a totally
different context.
The idea just to require git is really nice, putting all the things into
a single file is not. Not even Arch does it. (patches, install, config
...) - so the default debian dir should be enough.
Please
On 07.04.19 17:40, gregor herrmann wrote:
I'm one of those people.
And I still don't know what "an AUR-like service" is, or what
"packaging scripts" are.
After reading the intro at
https://wiki.archlinux.org/index.php/Arch_User_Repository I guess,
translated to Debian terms, we are talking abo
>> I think it would be good to hear from any derivatives in this
>> position. We should probably ask them more formally than by having a
>> horrible flamewar on -devel ...
With my siduction dev hat on i want to have usrmerge as soon as
possible. Built the last months with usrmerge activated and c
On Sat 24 Nov 2018 at 04:29PM +0100, Guido Günther wrote:
> The experimental distribution is a good place for work in
> progress. Maybe the rules for automatic rejects can be relaxed for
> experimental so a package can go into the archive (and have e.g. the BTS
> used for that version) if the main
git push --tags --force - if one have the needed rights and the remote
settings allow it.
Cheers Alf
Wow - we should wait a few days and there will be more comments about
this issue than users of this package. Impressive.
To be honest - i don't really like the "humor" and the names of the
package and the applications, but i fear that this heatened discussion
does more harm than the package itself
Package: wnpp
Severity: wishlist
Owner: Alf Gaida
* Package name: feathernotes
Version : 0.4.5
Upstream Author : Pedram Pourang, a.k.a. Tsu Jan tsujan2...@gmail.com
* URL : https://github.com/tsujan/FeatherNotes
* License : GPL
Programming Lang: C
Package: wnpp
Severity: wishlist
Owner: Alf Gaida
* Package name: lxqt-archiver
Version : 0.1.0
Upstream Author : PCMan
* URL : https://github.com/lxqt/lxqt-archiver/
* License : GPL2+
Programming Lang: C++
Description : Simple & lightweight Qt
Package: wnpp
Severity: wishlist
Owner: Alf Gaida
* Package name: nm-tray
Version : 0.3.0
Upstream Author : Palo Kisa
* URL : https://github.com/palinek/nm-tray
* License : GPL-2.0+
Programming Lang: C++
Description : a simple NetworkManager front end
Package: wnpp
Severity: wishlist
Owner: Alf Gaida
* Package name: qt5-engines-kvantum
Version : 10.5
Upstream Author : Pedram Pourang
* URL : https://github.com/tsujan/Kvantum
* License : GPL-3.0+
Programming Lang: C++, etc
Description : SVG-based
Russ, thanks, convinced.
On 06.12.2017 00:15, Russ Allbery wrote:
> It's not quite that simple. Once it's included in the default
> sources.list, those packages show up in apt-cache search and other tools,
> or in aptitude browsing. Then, when looking for a package to solve a
> particular proble
On 05.12.2017 10:33, Jonas Meurer wrote:
> 3. We should consider the a firmware subsection to non-free in our
>repositories. This would allow users to use non-free firmware while
>not adding sources for other non-free software on their systems.
>
> Cheers
> jonas
I see this a little bit d
On 05.12.2017 00:11, Adam Borowski wrote:
> How exactly firmware is not software?
> We may take a concession and offer non-free or parts of non-free more
> prominently (as it's needed on modern x86, all wifi cards I've seen, etc),
> but let's not declare that non-software.
>
> Thus, until the situa
ient. We should clearly state why we prefer the free
ones. But we should not hide the non-free ones and should have them on
the same site. With a clear statement why these images are not prefered.
Cheers
Alf Gaida (agaida)
On 01.12.2017 16:53, Ian Jackson wrote:
> Simon McVittie writes ("Re: Debian Stretch new user report (vs Linux Mint)"):
>> I find it interesting that we're having this conversation at the same
>> time as a thread about how there should be a configuration option that
>> denies our users the opportun
Package: wnpp
Severity: wishlist
Owner: Alf Gaida
* Package name: featherpad
Version : 0.6
Upstream Author : Tsu Jan
* URL : https://github.com/tsujan/FeatherPad
* License : GPL
Programming Lang: C++
Description : FeatherPad is a lightweight Qt5 plain
Package: wnpp
Severity: wishlist
Owner: Alf Gaida
* Package name: sddm-config-editor
Version : 0.1
Upstream Author : Yaohan Chen
* URL : https://github.com/hagabaka/sddm-config-editor
* License : ASL
Programming Lang: C++
Description : Graphical
Package: wnpp
Severity: wishlist
Owner: Alf Gaida
* Package name : lxqt-themes-extra
Version : 0.11.96
Upstream Author : Alf Gaida
* URL : https://anonscm.debian.org/cgit/pkg-lxqt/lxqt-themes-extra.git/
* License : LGPL
Programming Lang: n.A.
Description : Extra themes for LXQt
Package: wnpp
Severity: wishlist
Owner: Alf Gaida
* Package name: lxqt-themes
Version : 0.11.96
Upstream Author : Alf Gaida
* URL : http://github.com/lxde/lxqt-themes
* License : LGPL
Programming Lang: n.A.
Description : Upstream Themes for LXQt
Package: wnpp
Severity: wishlist
Owner: Alf Gaida
* Package name: fswatch
Version : 1.9.96
Upstream Author : Enrico M. Crisostomo
* URL : https://github.com/emcrisostomo/fswatch
* License : GPL-3+
Programming Lang: C, C++
Description : File change
Package: wnpp
Severity: wishlist
Owner: Alf Gaida
* Package name: lxqt-build-tools
Version : 0.1.0
Upstream Author : Luís Pereira
* URL : https://github.com/lxde/lxqt-build-tools
* License : LGPL-2.1+ and BSD-3-clause
Programming Lang: cmake
Description
Package: wnpp
Severity: wishlist
Owner: Alf Gaida
* Package name: pavucontrol-qt
Version : 0.1.0
Upstream Author : Hong Jen-Yee (PCMan)
* URL : https://github.com/lxde/pavucontrol-qt
* License : GPL
Programming Lang: C++
Description : pavucontrol-qt
Package: wnpp
Severity: wishlist
Owner: Alf Gaida
* Package name: xfwm-theme-breeze
Version : 0.1.0
Upstream Author : Ramón Cahenzli
* URL : https://github.com/psy-q/xfwm-theme-breeze
* License : GPL2
Programming Lang: etc.
Description : A clone of
Package: wnpp
Severity: wishlist
Owner: Alf Gaida
* Package name: meteo-qt
Version : 0.9.3
Upstream Author : Dimitrios Glentadakis
* URL : https://github.com/dglent/meteo-qt
* License : GPL
Programming Lang: Python
Description : Application to display
Package: wnpp
Severity: wishlist
Owner: Alf Gaida
* Package name: lxqt-l10n
Version : 0.10.9~beta
Upstream Author : LXQt team
* URL : https://github.com/lxde/translations
* License : (LGPL)
Programming Lang: (etc.)
Description : Language packages for
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
--- Please fill out the fields below. ---
Package name: nomacs
Version: 2.4.4
Upstream Author: Markus Diem , Stefan Fiel
, Florian Kleber
URL: http://nomacs.org/
License: GPL, LGPL and BS
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
Package name: lxqt-metapackages
Version: 0.9.0
Upstream Author: Alf Gaida
URL: http://anonscm.debian.org/cgit/pkg-lxqt/lxqt-metapackages.git/
License: GPL-2
Description: Metapackage
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
--- Please fill out the fields below. ---
Package name: lximage-qt
Version: 0.4.0
Upstream Author: Hong Jen Yee (PCMan)
URL: https://github.com/lxde/lximage-qt
License: GPL-2.0+ and LGPL-2
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
--- Please fill out the fields below. ---
Package name: lxqt-sudo
Version: 0.9.0
Upstream Author: Palo Kisa
URL: https://github.com/lxde/lxqt-sudo
License: LGPL-2.1
Description: Sudo f
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
--- Please fill out the fields below. ---
Package name: qlipper
Version: 5.0.0
Upstream Author: Petr Vanek
URL: https://github.com/pvanek/qlipper
License: GPL-2.0+
Description: Lightwe
Package: wnpp
Severity: wishlist
X-Debbugs-CC: debian-devel@lists.debian.org
--- Please fill out the fields below. ---
Package name: screengrab
Version: 1.95
Upstream Author: Artem Galichkin
URL: https://github.com/QtDesktop/screengrab
License: GPL-2.0+
Descrip
Package: wnpp
Severity: wishlist
Owner: Alf Gaida
* Package name: lxqt-admin
Version : 0.8.0
Upstream Author : LXQt team
* URL : http://lxqt.org
* License : (GPL, LGPL)
Programming Lang: (C++)
Description : Admin tools for LXQt
Admin tools for LXQt
Package: wnpp
Severity: wishlist
Owner: Alf Gaida
* Package name: lxqt-about
Version : 0.8.0
Upstream Author : LXQt team
* URL : http://lxqt.org/
* License : (GPL, LGPL)
Programming Lang: (C++)
Description : The LXQt About-Screen
(long description
72 matches
Mail list logo
