-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello,
It would be nice, if you could remove the package "strongswan_thermi" from the AUR. I botched up the package name there.
Regards
Noel Kuntze
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQIcBAEBCAAGBQJTEIwZAAoJEDg5KY9j7GZYdrgP/2rCoI0Sxy2IT2v3OjHFRPh9
G8CGjzqvnyTOCcBaAUwOybl7q/co/vr7vkObBph+vSN/vF1UhFAOIEfLXBqMRRLa
cjGBdfP2OZdfnbKbAkdp7m0g53xlByIBlfq6jx7Bw1gTlT/r2dJTcPU1zQn+Yfbo
TTdX+eK7XOYvWdG9+HfDpY9yth469qaYHBuOQRoF1FIa9V69n+H8WMxx0IrE/pcV
dgMIGPw1HwpUEH+FFoSPSfdiv9H9zJckI7YrMEkZL68vwZ/wwDbJDchiIF9JuBj5
JASZEFYsQIKQVeGEU7w9O4hz47ci0R1sGZSlUoZK6lyTI+o6OTBipRXEUMcO2R5K
932oePBM4CqCxJbtk+7ULj2amhvArOw2KeQBok1vfT1VN5g7p6fo6cCZd7dQ9ZVF
HxrkK+TbfmRAXSKLLn9GzQKbD0kc6nZp2MgiXJN8hFNsvl2stiMKKtsBSxesb44a
aAS7foAqvt+bxgU2f8k91E4xybOJNKDYeOq+KQ0KlivuE93LrIiq8rdScFci1Tjh
KWHfJrxawkI/ApJZZ9aYnYqsGHBIkPbQ6DVdR2hdj6ym9lA4FUvtoTuWVceeUI7g
mvtt+iyr41v64l/+u3xAThL/3iA19SMDWe9tofQ/LBHvmoV3+tvALc/V3YwU5F61
9JIaFlkBxduBC2OqpkG2
=OWC4
-----END PGP SIGNATURE-----
=== Signoff report for [community-testing] ===
https://www.archlinux.org/packages/signoffs/
There are currently:
* 0 new packages in last 24 hours
* 0 known bad packages
* 0 packages not accepting signoffs
* 0 fully signed off packages
* 4 packages missing signoffs
* 0 packages older than 14 days
(Note: the word 'package' as used here refers to packages as grouped by
pkgbase, architecture, and repository; e.g., one PKGBUILD produces one
package per architecture, even if it is a split package.)
== Incomplete signoffs for [community] (4 total) ==
* gitg-0.3.2-1 (i686)
0/1 signoffs
* python2-systemd-209-1 (i686)
0/1 signoffs
* gitg-0.3.2-1 (x86_64)
0/2 signoffs
* python2-systemd-209-1 (x86_64)
0/2 signoffs
== Top five in signoffs in last 24 hours ==
1. djgera - 7 signoffs
2. thomas - 7 signoffs
3. pierre - 6 signoffs
4. dan - 2 signoffs
Hello,
I just discovered a tool called `q` [1] and I have done a PKGBUILD to
try it. As it can be a useful to someone else, I was going to push it to
AUR.
But there exists already a package called `q` [2] (yeah, 26 letters are
not enough for all packages) so the usual way is to call the new one
otherwise regarding to its function. But in this particular case I think
it worth a reflexion; Regarding to the fact that:
- The package is orphan
- There is no vote for the package
- There is no comment on the package
- The package doesn't build anymore, at least on my computer
- The upstream project was named `q-lang` [3]
- There is a similar AUR package (correctly) named `q-lang` [4] which
provides the same software with same version.
- The upstream project is announced «no longer supported» [3] and
replaced by `pure` [5] which has also its own AUR package [6].
A) It is allowed to replace the existing `q` package with a completely
different software?
B) If yes, what is the best way to do it:
- Adopt it, then push a new PKGBUILD
- Ask for deletion, then push a new one. (May be useless here: no
comment/vote, but still "first submitted date" field will remain)
>From what I know, the only noticeable effect will be for the people who
have tho existing software installed and use an AUR helper: during an
update, a message can indicate that their package is more recent than
the AUR one. Eventually the day when the version of the new software
will be higher than the old one, the old software will be replaced by
the new one. But the probability of people still using it is very low I
think.
Any thoughts?
Regards,
Fabien
[1] https://github.com/harelba/q
[2] https://aur.archlinux.org/packages/q
[3] http://q-lang.sourceforge.net/
[4] https://aur.archlinux.org/packages/q-lang
[5] http://purelang.bitbucket.org/
[6] https://aur.archlinux.org/packages/pure/
=== Signoff report for [community-testing] ===
https://www.archlinux.org/packages/signoffs/
There are currently:
* 0 new packages in last 24 hours
* 0 known bad packages
* 0 packages not accepting signoffs
* 0 fully signed off packages
* 4 packages missing signoffs
* 0 packages older than 14 days
(Note: the word 'package' as used here refers to packages as grouped by
pkgbase, architecture, and repository; e.g., one PKGBUILD produces one
package per architecture, even if it is a split package.)
== Incomplete signoffs for [community] (4 total) ==
* gitg-0.3.2-1 (i686)
0/1 signoffs
* python2-systemd-209-1 (i686)
0/1 signoffs
* gitg-0.3.2-1 (x86_64)
0/2 signoffs
* python2-systemd-209-1 (x86_64)
0/2 signoffs
== Top five in signoffs in last 24 hours ==
1. bisson - 4 signoffs
2. dreisner - 2 signoffs
3. djgera - 2 signoffs
4. thomas - 1 signoffs