Bug#1070778: indi-armadillo-platypus: Add Appstream metainfo announcing HW support
Package: indi-armadillo-platypus Version: 1.0+20221226082641-2 Tags: patch Here is a patch for indi-armadillo-platypus to add Appstream metainfo XML announcing the hardware handled by this package. Including this information in the package will ensure programs mapping hardware to packages using Appstream information, like the isenkram package, will know that this package is useful on machines where the USB IDs are discovered. It will also solve the appstream-metadata-missing-modalias-provide lintian issue. diff --git a/debian/com.github.indilib.indi-3rdparty.metainfo.xml b/debian/com.github.indilib.indi-3rdparty.metainfo.xml new file mode 100644 index 000..48bfdf6 --- /dev/null +++ b/debian/com.github.indilib.indi-3rdparty.metainfo.xml @@ -0,0 +1,16 @@ + + + com.github.indilib.indi-3rdparty + MIT + indi-armadillo-platypus + INDI driver for Lunatico Astronomia Armadillo and Platypus + +This package contains the INDI driver for Armadillo and +Playtypus from Lunatico Astronomia. +This driver is compatible with any INDI client such as KStars +or Xephem. + + +usb:v16C0p09B1d* + + diff --git a/debian/indi-armadillo-platypus.install b/debian/indi-armadillo-platypus.install new file mode 100644 index 000..ee3cc69 --- /dev/null +++ b/debian/indi-armadillo-platypus.install @@ -0,0 +1 @@ +debian/com.github.indilib.indi-3rdparty.metainfo.xml usr/share/metainfo
Bug#1070776: android-sdk: Update Appstream metainfo XML modalias list
* +usb:v18D1p4E20d* +usb:v18D1p4E22d* +usb:v18D1p4E24d* +usb:v18D1p4E30d* +usb:v18D1p4E40d* +usb:v18D1p4E42d* +usb:v18D1p4EE0d* +usb:v18D1p4EE2d* +usb:v18D1p4EE4d* +usb:v18D1p4EE6d* +usb:v18D1p4EE7d* +usb:v18D1p4EE8d* +usb:v18D1p4EE9d* +usb:v18D1p4EECd* +usb:v18D1p5201d* +usb:v18D1p5203d* +usb:v18D1p5208d* +usb:v18D1p9024d* +usb:v18D1p9025d* +usb:v18D1pD001d* +usb:v18D1pD002d* +usb:v18D1pD00Dd* +usb:v18D1pD10Ad* usb:v1949p0006d* usb:v1949p0008d* usb:v1949p0022d* +usb:v1949p0232d* +usb:v1949p0234d* usb:v1949p0298d* usb:v1949p0338d* +usb:v1949p033Bd* +usb:v1949p03A8d* +usb:v1949p03C8d* +usb:v1949p03CBd* +usb:v1949p05E0d* +usb:v1949p05E2d* +usb:v1949p05E4d* +usb:v1949p05E8d* +usb:v1949p0658d* +usb:v1949p2048d* +usb:v19CFp0001d* +usb:v19D2p0306d* +usb:v19D2p0310d* +usb:v19D2p0501d* +usb:v19D2p1275d* usb:v19D2p1351d* +usb:v19D2p1352d* usb:v19D2p1353d* usb:v19D2p1354d* usb:v19D2p1355d* +usb:v19D2p1373d* +usb:v19D2p1432d* +usb:v19D2p1485d* +usb:v19D2p1489d* +usb:v19D2pFFB0d* +usb:v19D2pFFB2d* +usb:v19D2pFFC0d* +usb:v19D2pFFC1d* +usb:v19D2pFFC7d* +usb:v19D2pFFC9d* +usb:v19D2pFFCBd* +usb:v19D2pFFCDd* +usb:v19D2pFFCFd* +usb:v19D2pFFD1d* usb:v1BBBp00F2d* usb:v1BBBp0167d* +usb:v1BBBp0C01d* +usb:v1BBBp4EE7d* +usb:v1D4Dp5035d* +usb:v1F3Ap1000d* usb:v1F3Ap1001d* usb:v1F3Ap1002d* usb:v1F3Ap1003d* @@ -88,22 +304,101 @@ usb:v1F3Ap1007d* usb:v1F3Ap1008d* usb:v1F3Ap1009d* +usb:v1F3Ap1010d* usb:v1F3ApEFE8d* usb:v2207pd* +usb:v2207p0006d* usb:v2207p0010d* +usb:v2207p0013d* +usb:v2207p0017d* +usb:v2207p0018d* +usb:v22B8p2D66d* +usb:v22B8p2E24d* +usb:v22B8p2E25d* +usb:v22B8p2E33d* +usb:v22B8p2E51d* +usb:v22B8p2E76d* +usb:v22B8p2E80d* +usb:v22B8p2E81d* +usb:v22B8p2E84d* +usb:v22B8p2EA4d* +usb:v22B8p2EB7d* +usb:v22B8p41DBd* +usb:v22B8p428Cd* +usb:v22B8p4362d* +usb:v22B8p70A9d* +usb:v22B8p70AEd* +usb:v22B8p70AFd* +usb:v22B8p70B1d* +usb:v22B8p70B3d* +usb:v22B8p70B5d* +usb:v22B8p710Ed* +usb:v22D9p200Ed* +usb:v22D9p2024d* +usb:v22D9p2026d* +usb:v22D9p2028d* +usb:v22D9p2764d* +usb:v22D9p2767d* +usb:v22D9p2769d* +usb:v22D9p2771d* +usb:v22D9p2772d* +usb:v22D9p2774d* +usb:v2717p0368d* +usb:v2717p1218d* +usb:v2717p1228d* +usb:v2717p1248d* +usb:v2717p1268d* +usb:v2717p1318d* +usb:v2717p1328d* +usb:v2717p1368d* +usb:v2717p803Ed* +usb:v2717p9015d* +usb:v2717p9024d* +usb:v2717p9039d* +usb:v2717p904Ed* +usb:v2717pFF08d* +usb:v2717pFF18d* +usb:v2717pFF28d* +usb:v2717pFF40d* +usb:v2717pFF48d* +usb:v2717pFF68d* +usb:v2717pFF88d* +usb:v271Dp3F11d* usb:v271DpBF39d* +usb:v2833p0186d* usb:v2916p9139d* +usb:v2A45p0C01d* usb:v2A45p0C02d* +usb:v2A45p201Cd* usb:v2A47p0C02d* usb:v2A47p2008d* +usb:v2A48p5101d* +usb:v2A70p4EE2d* +usb:v2A70p4EE6d* +usb:v2A70p4EE7d* +usb:v2A70p9011d* +usb:v2A70p9012d* +usb:v2A70p9024d* +usb:v2A70p904Dd* +usb:v2A70p904Ed* +usb:v2A70p90BBd* +usb:v2A70pD001d* usb:v2A96p201Dd* +usb:v2AE5p9015d* +usb:v2AE5p9024d* +usb:v2AE5p9039d* +usb:v2AE5p904Ed* +usb:v2AE5p90BBd* +usb:v2AE5p90DCd* usb:v2B0Ep610Dd* usb:v2E17pC009d* usb:v2E17pC030d* +usb:v2E8Ep96E7d* usb:v8087p07EFd* usb:v8087p09EFd* -usb:v8087p09EFd* usb:v8087p0A16d* +usb:v8087p0A5Dd* +usb:v8087p0A65d* usb:v8087p2A65d* -- Happy hacking Petter Reinholdtsen
Bug#1040375: marked as pending in simplescreenrecorder
Control: tag -1 pending Hello, Bug #1040375 in simplescreenrecorder reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/multimedia-team/simplescreenrecorder/-/commit/469d4dff951437e022d39bff10e9c4a3cbf8a0d4 Added 0010-plthook.patch from upstream to fix segfault in libssr-glinject.so. Closes: #1040375 (this message was generated automatically) -- Greetings https://bugs.debian.org/1040375
Bug#1040375: /usr/lib/x86_64-linux-gnu/simplescreenrecorder/libssr-glinject.so: Segmentation fault when used with anything
[Bernhard Übelacker]
> As far as I see the crash happens because it wants to print this message:
>
> 57 GLINJECT_PRINT("Error: Can't open libdl.so!");
>
> But unfortunately libstdc++ seems not yet prepared to output the
> error.
Thank you very much for the analysis and links. I applied the upstream
patch to the Debian package build, and it sure seem to fix the
segfault. Will need to do some more testing, and will upload a fixed
package later.
--
Happy hacking
Petter Reinholdtsen
Bug#1040375: /usr/lib/x86_64-linux-gnu/simplescreenrecorder/libssr-glinject.so: Segmentation fault when used with anything
[Bernhard Übelacker]
> As far as I see the crash happens because it wants to print this message:
>
> 57 GLINJECT_PRINT("Error: Can't open libdl.so!");
>
> But unfortunately libstdc++ seems not yet prepared to output the
> error.
Thank you very much for the analysis and links. I applied the upstream
patch to the Debian package build, and it sure seem to fix the
segfault. Will need to do some more testing, and will upload a fixed
package later.
--
Happy hacking
Petter Reinholdtsen
Bug#1040375: /usr/lib/x86_64-linux-gnu/simplescreenrecorder/libssr-glinject.so: Segmentation fault when used with anything
[Bernhard Übelacker]
> As far as I see the crash happens because it wants to print this message:
>
> 57 GLINJECT_PRINT("Error: Can't open libdl.so!");
>
> But unfortunately libstdc++ seems not yet prepared to output the
> error.
Thank you very much for the analysis and links. I applied the upstream
patch to the Debian package build, and it sure seem to fix the
segfault. Will need to do some more testing, and will upload a fixed
package later.
--
Happy hacking
Petter Reinholdtsen
Bug#981754: Interest in taking over the dkopp Debian package
[Hill Ma] > I made a merge request for 7.7 here: > https://salsa.debian.org/debian/dkopp/-/merge_requests/3 This process seem to have completely stopped. I found some lingering changes in https://salsa.debian.org/debian/dkopp >, diverting from the current package in the archive. I am working to clean this up. If you want me to sponsor the upload, my sponsoring preferences are available from http://www.hungry.com/~pere/debian-sponsoring.html >. -- Happy hacking PEtter Reinholdtsen
Bug#981754: Interest in taking over the dkopp Debian package
[Hill Ma] > I made a merge request for 7.7 here: > https://salsa.debian.org/debian/dkopp/-/merge_requests/3 This process seem to have completely stopped. I found some lingering changes in https://salsa.debian.org/debian/dkopp >, diverting from the current package in the archive. I am working to clean this up. If you want me to sponsor the upload, my sponsoring preferences are available from http://www.hungry.com/~pere/debian-sponsoring.html >. -- Happy hacking PEtter Reinholdtsen
Bug#1030231: hugs: toInteger (minBound :: Int) incorrect on 64bit
[Claude Heiland-Allen 2023-02-01] > The problem is in src/bignums.c, because -INT_MIN == INT_MIN. > > Attached patch fixes the problem for me on aarch64 and x86_64. Currently hugs98 is orphaned in Debian. Your fix seem like a patch for upstream. Did you try to submit it to the upstream project? -- Happy hacking Petter Reinholdtsen
Bug#1030231: hugs: toInteger (minBound :: Int) incorrect on 64bit
[Claude Heiland-Allen 2023-02-01] > The problem is in src/bignums.c, because -INT_MIN == INT_MIN. > > Attached patch fixes the problem for me on aarch64 and x86_64. Currently hugs98 is orphaned in Debian. Your fix seem like a patch for upstream. Did you try to submit it to the upstream project? -- Happy hacking Petter Reinholdtsen
Bug#1070263: uuu: Add Appstream metainfo XML with hardware mapping
Package: uuu Version: 1.5.141-1 Tags:patch Here is a patch for mfgtools to add Appstream metainfo XML announcing the hardware handled by this package. Including this information in the package will ensure programs mapping hardware to packages using Appstream information, like the isenkram package, will know that this package is useful on machines where the USB IDs are discovered. diff --git a/debian/copyright b/debian/copyright index 5911c26..8003583 100644 --- a/debian/copyright +++ b/debian/copyright @@ -14,6 +14,29 @@ Files: debian/* Copyright: 2020 Henry-Nicolas Tourneur License: BSD-3-clause +Files: debian/uuu.metainfo.xml +Copyright: 2024 Petter Reinholdtsen +License: MIT + Permission is hereby granted, free of charge, to any person obtaining + a copy of this software and associated documentation files (the + "Software"), to deal in the Software without restriction, including + without limitation the rights to use, copy, modify, merge, publish, + distribute, sublicense, and/or sell copies of the Software, and to + permit persons to whom the Software is furnished to do so, subject to + the following conditions: + . + The above copyright notice and this permission notice shall be + included in all copies or substantial portions of the Software. + . + THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, + EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF + MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND + NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS + BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN + ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN + CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE + SOFTWARE. + License: BSD-3-clause Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: diff --git a/debian/uuu.install b/debian/uuu.install new file mode 100644 index 000..c4e0bfd --- /dev/null +++ b/debian/uuu.install @@ -0,0 +1 @@ +debian/uuu.metainfo.xml usr/share/metainfo diff --git a/debian/uuu.metainfo.xml b/debian/uuu.metainfo.xml new file mode 100644 index 000..5da0baf --- /dev/null +++ b/debian/uuu.metainfo.xml @@ -0,0 +1,49 @@ + + + com.github.NXPmicro.mfgtools + MIT + mfgtools + Freescale/NXP I.MX Chip image deploy tools + +Universal update utility for I.MX CPUs. It can be used to +e.g. burn uboot or a rootfs into the emmc. + + +usb:v1FC9p012Fd* +usb:v1FC9p0129d* +usb:v1FC9p0147d* +usb:v15A2p004Fd* +usb:v1FC9p013Ed* +usb:v1FC9p0146d* +usb:v1FC9p014Ad* +usb:v1FC9p014Bd* +usb:v1FC9p014Ed* +usb:v1FC9p015Dd* +usb:v15A2p0076d* +usb:v15A2p0054d* +usb:v15A2p0061d* +usb:v15A2p0063d* +usb:v15A2p0071d* +usb:v15A2p007Dd* +usb:v15A2p0080d* +usb:v1FC9p0128d* +usb:v1FC9p0126d* +usb:v1FC9p0135d* +usb:v1FC9p0134d* +usb:v1FC9p012Bd* +usb:v0525pB4A4d* +usb:v0525pB4A4d* +usb:v1FC9p0151d* +usb:v0525pB4A4d* +usb:v3016p1001d* +usb:v3016p1001d* +usb:v066Fp9AFEd* +usb:v066Fp9BFFd* +usb:v1FC9p0153d* +usb:v0525pA4A5d* +usb:v18D1p0D02d* +usb:v3016p0001d* +usb:v1FC9p0152d* +usb:v0483p0AFBd* + + -- Happy hacking Petter Reinholdtsen
Bug#1070262: msi-keyboard: Adjust udev access rights from 'everyone' to 'console user'
Package: msi-keyboard
Version: 1.1-2
Tags: patch
The current udev role grant access to the device for everyone when the
hardware is inserted. I believe a better approach is to only grant
access to the console user using the 'uaccess' tag. Here is a patch to
adjust the access role.
diff --git a/99-msi.rules b/99-msi.rules
index 81d21ba..1946dca 100644
--- a/99-msi.rules
+++ b/99-msi.rules
@@ -1 +1 @@
-SUBSYSTEM=="usb", ATTRS{idVendor}=="1770", ATTRS{idProduct}=="ff00",
MODE="0666"
+SUBSYSTEM=="usb", ATTRS{idVendor}=="1770", ATTRS{idProduct}=="ff00",
TAG+="uaccess"
--
Happy hacking
Petter Reinholdtsen
Bug#1070261: msi-keyboard: Add Appstream metainfo XML with hardware mapping
Package: msi-keyboard Version: 1.1-2 Tags: patch Here is a patch for msi-keyboard to add Appstream metainfo XML announcing the hardware handled by this package. Including this information in the package will ensure programs mapping hardware to packages using Appstream information, like the isenkram package, will know that this package is useful on machines where the USB IDs are discovered. diff --git a/debian/copyright b/debian/copyright index 69828c7..7402d29 100644 --- a/debian/copyright +++ b/debian/copyright @@ -13,6 +13,29 @@ Files: debian/* Copyright: 2015 Giulio Paci License: BSD-3-clause +Files: debian/msi-keyboard.metainfo.xml +Copyright: 2024 Petter Reinholdtsen +License: MIT + Permission is hereby granted, free of charge, to any person obtaining + a copy of this software and associated documentation files (the + "Software"), to deal in the Software without restriction, including + without limitation the rights to use, copy, modify, merge, publish, + distribute, sublicense, and/or sell copies of the Software, and to + permit persons to whom the Software is furnished to do so, subject to + the following conditions: + . + The above copyright notice and this permission notice shall be + included in all copies or substantial portions of the Software. + . + THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, + EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF + MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND + NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS + BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN + ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN + CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE + SOFTWARE. + License: BSD-3-clause Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions diff --git a/debian/msi-keyboard.install b/debian/msi-keyboard.install index 7061c7e..6d6e917 100644 --- a/debian/msi-keyboard.install +++ b/debian/msi-keyboard.install @@ -1 +1,2 @@ msi-keyboard /usr/bin +debian/msi-keyboard.metainfo.xml usr/share/metainfo diff --git a/debian/msi-keyboard.metainfo.xml b/debian/msi-keyboard.metainfo.xml new file mode 100644 index 000..8e6845f --- /dev/null +++ b/debian/msi-keyboard.metainfo.xml @@ -0,0 +1,17 @@ + + + com.github.bparker06.msi-keyboard + MIT + msi-keyboard + command line tool to change MSI steelseries keyboards color setup + +This command line tool allows one to change the color setup of +MSI steelseries keyboards, found on some MSI laptop. The tool +supports changing operational mode of keyboard backlight and +changing color and intensity of specific areas. + + + +usb:v1770pFF00d* + + -- Happy hacking Petter Reinholdtsen
Bug#1070260: msi-keyboard: Please make git repository available on salsa?
Package: msi-keyboard Version: 1.1-2 At the moment, the package metadata point to https://anonscm.debian.org/cgit/collab-maint/msi-keyboard.git >, which no longer work. Please move it to salsa.debian.org. I can help with the conversion, if you want me to. -- Happy hacking Petter Reinholdtsen
Re: [Freedombox-discuss] FreeedomBox data leakage, firewall issues.
[A. F. Cano] > I have long noticed that there is usually some data going out of the > external interface. I have always assumed it was housekeeping stuff, > such as dns. However, Cockpit is now showing data going out at 1 Mbps > and receiving at 300-400 Mpbs. Something is going on that looks very > suspicious. It seem very different from mine, which is behind NAT-ing and only available via pagekite. As far as I can tell, only Tor and pagekite traffic is present when I run 'iftop'. Did you try to press 'p' to get the port number displayed? Any idea if it is TCP or UDP? My 'sudo lsof -i|grep EST|grep -v localhost' only show pagekite after I stopped tor. -- Happy hacking Petter Reinholdtsen ___ Freedombox-discuss mailing list Freedombox-discuss@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/freedombox-discuss
Re: [Freedombox-discuss] Serving NTP from my FreedomBox
[Sandy Harris] > What would it take to set up Freedom Box on Devuan, a Debian fork > without systemd? Hard work and spare time. Please let us know how it went. > Has anyone done this? I have not. -- Happy hacking Petter Reinholdtsen ___ Freedombox-discuss mailing list Freedombox-discuss@alioth-lists.debian.net https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/freedombox-discuss
Bug#1021470: xsok: reproducible-builds: build path embedded in /usr/games/xsok
[Vagrant Cascadian] > Still appears to be an issue, though tests.reproducible-builds.org is no > longer testing build path variations. Downgrading the severity > accordingly. Hm, then I do not understand the fix. As far as I can tell, the default build flags are used. Perhaps you can take a look at this orphaned package in https://salsa.debian.org/debian/xsok > and commit a fix that really solve the issue. I plan a new upload tomorrow to push the latest git changes into unstable. -- Happy hacking Petter Reinholdtsen
Bug#1021470: xsok: reproducible-builds: build path embedded in /usr/games/xsok
[Vagrant Cascadian] > Still appears to be an issue, though tests.reproducible-builds.org is no > longer testing build path variations. Downgrading the severity > accordingly. Hm, then I do not understand the fix. As far as I can tell, the default build flags are used. Perhaps you can take a look at this orphaned package in https://salsa.debian.org/debian/xsok > and commit a fix that really solve the issue. I plan a new upload tomorrow to push the latest git changes into unstable. -- Happy hacking Petter Reinholdtsen
Bug#661461: ITA: unadf -- Extract files from an Amiga Disk File dump (.adf)
[John Paul Adrian Glaubitz] > I started working on this, but I got stuck because of the fact that > the upstream package is actually not just unadf but a whole library > that might need different treatment. Aha. I hope you can use the git repo I created as a base. :) -- Happy hacking Petter Reinholdtsen
Bug#661461: ITA: unadf -- Extract files from an Amiga Disk File dump (.adf)
[John Paul Adrian Glaubitz] > I started working on this, but I got stuck because of the fact that > the upstream package is actually not just unadf but a whole library > that might need different treatment. Aha. I hope you can use the git repo I created as a base. :) -- Happy hacking Petter Reinholdtsen
Re: ITA: unadf -- Extract files from an Amiga Disk File dump (.adf)
[John Paul Adrian Glaubitz] > I started working on this, but I got stuck because of the fact that > the upstream package is actually not just unadf but a whole library > that might need different treatment. Aha. I hope you can use the git repo I created as a base. :) -- Happy hacking Petter Reinholdtsen
Bug#661461: ITA: unadf -- Extract files from an Amiga Disk File dump (.adf)
Hi, [John Paul Adrian Glaubitz 2020-05-10] > I would like to adopt this package. There is a new upstream available and the > repository has been moved to Github with some recent activity [1]. What came out of this intent? I just migrated the package to a git repository on https://salsa.debian.org/debian/unadf >. -- Happy hacking Petter Reinholdtsen
Bug#661461: ITA: unadf -- Extract files from an Amiga Disk File dump (.adf)
Hi, [John Paul Adrian Glaubitz 2020-05-10] > I would like to adopt this package. There is a new upstream available and the > repository has been moved to Github with some recent activity [1]. What came out of this intent? I just migrated the package to a git repository on https://salsa.debian.org/debian/unadf >. -- Happy hacking Petter Reinholdtsen
Re: ITA: unadf -- Extract files from an Amiga Disk File dump (.adf)
Hi, [John Paul Adrian Glaubitz 2020-05-10] > I would like to adopt this package. There is a new upstream available and the > repository has been moved to Github with some recent activity [1]. What came out of this intent? I just migrated the package to a git repository on https://salsa.debian.org/debian/unadf >. -- Happy hacking Petter Reinholdtsen
Bug#1049680: freedink-dfarc: Fails to build binary packages again after successful build
I had a look at this issue, and the cause is in src/Makefile.am, which intentionally list several files both in both dfarc_SOURCES and BUILT_SOURCES. The problematic files are generated but stored in the tarball to save a build dependencuy (wxglade). I am not sure how to avoid this problem, and left it to someone with more time to spend on it. :) -- Happy hacking Petter Reinholdtsen
Bug#1049680: freedink-dfarc: Fails to build binary packages again after successful build
I had a look at this issue, and the cause is in src/Makefile.am, which intentionally list several files both in both dfarc_SOURCES and BUILT_SOURCES. The problematic files are generated but stored in the tarball to save a build dependencuy (wxglade). I am not sure how to avoid this problem, and left it to someone with more time to spend on it. :) -- Happy hacking Petter Reinholdtsen
Bug#938934: ITA: freedink -- humorous top-down adventure and role-playing game
Dear Keiran, What happened with your intention to adapt FreeDink? -- Happy hacking Petter Reinholdtsen
Bug#938934: ITA: freedink -- humorous top-down adventure and role-playing game
Dear Keiran, What happened with your intention to adapt FreeDink? -- Happy hacking Petter Reinholdtsen
Bug#700412: O: kst -- A KDE application used for displaying scientific data
[Petter Reinholdtsen] > I noticed a git repository for this package on Salsa, > https://salsa.debian.org/science-team/kst.git >. On closer examination, I notice the versions from 2.0.3-5 to 2.0.8-5 are missing in the git repository, and an independent import of the 2.0.8 upstream version has been done. I believe a complete remake if the git repository would have to be done for it to be a good base for further maintenance in Debian and is creating a new repository based on the uploaded packages instead. -- Happy hacking Petter Reinholdtsen
Bug#700412: O: kst -- A KDE application used for displaying scientific data
[Petter Reinholdtsen] > I noticed a git repository for this package on Salsa, > https://salsa.debian.org/science-team/kst.git >. On closer examination, I notice the versions from 2.0.3-5 to 2.0.8-5 are missing in the git repository, and an independent import of the 2.0.8 upstream version has been done. I believe a complete remake if the git repository would have to be done for it to be a good base for further maintenance in Debian and is creating a new repository based on the uploaded packages instead. -- Happy hacking Petter Reinholdtsen
Bug#700412: O: kst -- A KDE application used for displaying scientific data
I noticed a git repository for this package on Salsa, https://salsa.debian.org/science-team/kst.git >. -- Happy hacking Petter Reinholdtsen
Bug#700412: O: kst -- A KDE application used for displaying scientific data
I noticed a git repository for this package on Salsa, https://salsa.debian.org/science-team/kst.git >. -- Happy hacking Petter Reinholdtsen
Bug#1070082: ponyprog: Add Appstream metainfo announcing HW support
Package: ponyprog Version: 3.1.1+ds-1 Tags: patch Here is a patch for ponyprog to add Appstream metainfo XML announcing the hardware handled by this package. The list of USB IDs in the modalias list was fetched from udev/rules.d/90-ponyprog.rules. I was unsure if the disabled entries should be included, but thought it best to keep the in the list. Including this information in the package will ensure programs mapping hardware to packages using Appstream information, like the isenkram package, will know that this package is useful on machines where the USB IDs are discovered. diff --git a/debian/copyright b/debian/copyright index 0115ef0..fc33ab3 100644 --- a/debian/copyright +++ b/debian/copyright @@ -28,6 +28,29 @@ Copyright: 2015-2017, Winfried Simon 2017, Mykhailo Lytvyn License: LGPL-2.1 +Files: debian/ponyprog.metainfo.xml +Copyright: 2024 Petter Reinholdtsen +License: MIT + Permission is hereby granted, free of charge, to any person obtaining + a copy of this software and associated documentation files (the + "Software"), to deal in the Software without restriction, including + without limitation the rights to use, copy, modify, merge, publish, + distribute, sublicense, and/or sell copies of the Software, and to + permit persons to whom the Software is furnished to do so, subject to + the following conditions: + . + The above copyright notice and this permission notice shall be + included in all copies or substantial portions of the Software. + . + THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, + EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF + MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND + NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS + BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN + ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN + CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE + SOFTWARE. + License: GPL-2+ This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by diff --git a/debian/ponyprog.install b/debian/ponyprog.install index 7f876ad..d6bf4f6 100644 --- a/debian/ponyprog.install +++ b/debian/ponyprog.install @@ -1,3 +1,4 @@ icons/ponyprog.svg usr/share/icons/hicolor/scalable/apps lib/udev/rules.d/90-ponyprog.rules usr +debian/ponyprog.metainfo.xml usr/share/metainfo diff --git a/debian/ponyprog.metainfo.xml b/debian/ponyprog.metainfo.xml new file mode 100644 index 000..3cc3bad --- /dev/null +++ b/debian/ponyprog.metainfo.xml @@ -0,0 +1,41 @@ + + + com.github.lancos.ponyprog + MIT + ponyprog + Serial device programmer + +PonyProg is a serial device programmer software with a user +friendly GUI framework available for Windows and Linux. It's +purpose is reading and writing every serial device. With PonyProg +and SI-Prog you can program Wafercard for SAT, eeprom within GSM, +TV or CAR-RADIO. Furthermore it can be used as a low cost starter +kit for PIC and AVR. + +Ponyprog supports AVR, SPI eeprom, AVR micro, 12C bus 8bit +eeprom, PIC 16 micro, PIC 12 micro, AT89S micro and SDE2506 eeprom +family chips. + +You can open any HEX, e2p, mot, csm, rom, eep, bin files and +burn them to uC or PIC. You can even backup the old program on the +chip using Ponyprog. Ponyprog enables the user to write, verify +and erase data on the microchip. + +Also setting fuse bits and locks using Ponyprog is +possible. You can save any HEX file to BIN file or eep file, BIN +file to HEX file or MOT file and vice versa so you can use +Ponyprog as converter too. Ponyprog offers serial or parallel port +programming for uC's. You can even change polarity of control +lines without touching the wires using I/O port setup. + +Using Ponyprog together with generic USB2serial adapters is +currently not possible! There are plans on upstream to use libusb +to add such functionality. + + +usb:v1A86p5523d* +usb:v1A86p7523d* +usb:v1A86p5512d* +usb:v0403p6E38d* + + -- Happy hacking Petter Reinholdtsen
Re: [Emc-developers] LinuxCNC gathering in Norway - July 5th-7th 2024
[Andy Pugh] > Is anyone else coming? I can recommend it :-) There is still plenty room for more participants. :) I am happy to tell that we have secured some sponsoring from Debian and NUUG Foundation, which in addition to the leftover funds from last years gathering, should provide funding for at least some food. :) We are still looking for more sponsors. Get in touch if you know of any candiates. :) -- Happy hacking Petter Reinholdtsen ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
Bug#1070051: xr-hardware: Add Appstream metainfo with hardware mappins
Package: xr-hardware
Version: 1.1.1-1
Tags: patch
It would be very nice if programs using the Appstream metainfo to locate
relevant package, would know which hardware is supported by this
package. This way programs like isenkram would propose the xr-hardwrae
package when a relevant USB device is inserted.
I started with the /usr/lib/udev/rules.d/70-xrhardware.rules file and
used its listed USB IDs to generate the modalias entries in the metainfo
XML. There were a few entries I did not understand (the KERNELS==
entries), so these are not represented in the XML.
Please apply this to a future upload of xr-hardware.
diff --git a/debian/copyright b/debian/copyright
index 88fbd06..11ba17d 100644
--- a/debian/copyright
+++ b/debian/copyright
@@ -52,6 +52,29 @@ Files: xrhardware/db.py
Copyright: 2019-2024, Collabora, Ltd. and the xr-hardware contributors
License: BSL-1.0
+Files: debian/xr-hardware.metainfo.xml
+Copyright: 2024 Petter Reinholdtsen
+License: MIT
+ Permission is hereby granted, free of charge, to any person obtaining
+ a copy of this software and associated documentation files (the
+ "Software"), to deal in the Software without restriction, including
+ without limitation the rights to use, copy, modify, merge, publish,
+ distribute, sublicense, and/or sell copies of the Software, and to
+ permit persons to whom the Software is furnished to do so, subject to
+ the following conditions:
+ .
+ The above copyright notice and this permission notice shall be
+ included in all copies or substantial portions of the Software.
+ .
+ THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
+ EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
+ MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+ NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS
+ BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN
+ ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
+ CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+ SOFTWARE.
+
License: BSL-1.0
Boost Software License - Version 1.0 - August 17th, 2003
.
diff --git a/debian/xr-hardware.install b/debian/xr-hardware.install
index 59f1f7b..aa7a1ea 100644
--- a/debian/xr-hardware.install
+++ b/debian/xr-hardware.install
@@ -1 +1,2 @@
70-xrhardware.rules ${env:deb_udevdir}/rules.d/
+debian/xr-hardware.metainfo.xml usr/share/metainfo
diff --git a/debian/xr-hardware.metainfo.xml b/debian/xr-hardware.metainfo.xml
new file mode 100644
index 000..3210f48
--- /dev/null
+++ b/debian/xr-hardware.metainfo.xml
@@ -0,0 +1,66 @@
+
+
+ org.freedesktop.gitlab.monado.utilities.xr-hardware
+ MIT
+ xr-hardware
+ udev rules files for normal user access to XR input
+ devices
+
+This package contains a udev rules file to permit access to
+virtual reality (VR) and augmented reality (AR), collectively
+"XR", interaction devices as a normal user.
+
+
+usb:v1532p0300d*
+usb:v0BB4p2C87d*
+usb:v0BB4p0309d*
+usb:v28DEp2101d*
+usb:v28DEp2102d*
+usb:v28DEp2300d*
+usb:v28DEp2000d*
+usb:v1532p0B00d*
+usb:v0BDAp57E8d*
+usb:v16D0p0515d*
+usb:v0483p5750d*
+usb:v28E9p028Ad*
+usb:v28E9p0302d*
+usb:v0483p0021d*
+usb:v2833p0001d*
+usb:v2833p0021d*
+usb:v2833p2021d*
+usb:v2833p0201d*
+usb:v2833p0031d*
+usb:v2833p0211d*
+usb:v2833p0051d*
+usb:v04E8pA500d*
+usb:v2B1Cp0200d*
+usb:v2B1Cp0201d*
+usb:v2B1Cp0202d*
+usb:v2B1Cp0203d*
+usb:v2B1Cp0100d*
+usb:v2B1Cp0101d*
+usb:v054Cp09AFd*
+usb:v054Cp03D5d*
+usb:v054Cp0C5Ed*
+usb:v054Cp0CDEd*
+usb:v054Cp0E46d*
+usb:v1004p6374d*
+usb:v045Ep0659d*
+usb:v04E8p7310d*
+usb:v04E8p7312d*
+usb:v03F0p0367d*
+usb:v03F0p0C6Ad*
+usb:v03F0p0580d*
+usb:v17EFpB801d*
+usb:v04B4p6504d*
+usb:v0502pB0D6d*
+usb:v413CpB0D5d*
+usb:v0408pB5D5d*
+usb:v1209p9D0Fd*
+usb:v0486p573Cd*
+usb:v05A9p0680d*
+usb:v3318p0424d*
+usb:v3318p0428d*
+usb:v3318p0432d*
+
+
--
Happy hacking
Petter Reinholdtsen
Bug#1049988: bookworm-pu: package riemann-c-client/1.10.4-2
[Romain Tartière 2024-02-09] > In case I missed something and the ball is in my court, please point me > to the next move because I obviously missed it! I suspect your next move is to track down a sponsor willing to upload your version to Debian. Such sponsor would be a Debian developer able to sign your uploads. It sound a bit like you would like to adapt this package and maintain it in Debian using a sponsor. My personal sponsoring preferences are listed on http://www.hungry.com/~pere/debian-sponsoring.html >. I plan to make a git repository for the Debian packaging now. -- Happy hacking Petter Reinholdtsen
Bug#1049988: bookworm-pu: package riemann-c-client/1.10.4-2
[Romain Tartière 2024-02-09] > In case I missed something and the ball is in my court, please point me > to the next move because I obviously missed it! I suspect your next move is to track down a sponsor willing to upload your version to Debian. Such sponsor would be a Debian developer able to sign your uploads. It sound a bit like you would like to adapt this package and maintain it in Debian using a sponsor. My personal sponsoring preferences are listed on http://www.hungry.com/~pere/debian-sponsoring.html >. I plan to make a git repository for the Debian packaging now. -- Happy hacking Petter Reinholdtsen
Bug#334773: kguitar crashes after startup if compiled with libtse3
[Tommaso Moroni 2005-10-19] > While ackaging kguitar I found that, if I compile it > with libtse3 support, kguitar crashes after startup, while > the same package compiled without libtse3 works normally. Thank you for the bug geport. > If there's anything I can do to help you, just ask! Perhaps you can try to run it using valgrind, to see where and why it crashes? The crash seem to be heap related. -- Happy hacking Petter Reinholdtsen
Bug#334773: kguitar crashes after startup if compiled with libtse3
[Tommaso Moroni 2005-10-19] > While ackaging kguitar I found that, if I compile it > with libtse3 support, kguitar crashes after startup, while > the same package compiled without libtse3 works normally. Thank you for the bug geport. > If there's anything I can do to help you, just ask! Perhaps you can try to run it using valgrind, to see where and why it crashes? The crash seem to be heap related. -- Happy hacking Petter Reinholdtsen
Bug#1069989: bmusb: Add Appstream metainfo announcing HW support
[Steinar H. Gunderson] > Thanks for the patch. I assume this is also suitable for upstream? Sure. > It would probably be more useful I package v4l2proxy, which has been > part of bmusb for a while; it would allow “anything” to go use it, > although with some local setup. I believe Nageru is the only other > software that uses bmusb right now. Make sense to me. :) >> +usb:v1EDBpBD3Bd* >> +usb:v1EDBpBD4Fd* > > Can you say something about where these values come from? Is it base64 > somehow? It is the USB IDs listed in 70-bmusb.rules, in modalias glob format. -- Happy hacking Petter Reinholdtsen
Bug#1056146: xsok possibly contains non-DFSG-free data files
[Doug Beeferman 2023-11-22] > Hello, > > I'm the author of Cyberbox and I grant permission for Cyberbox to be > redistributed without any restriction, including with modifications or in > derived works. Thank you for letting me know. Is it the correct understanding that Cuberbox is licensed with the same license as the rest of xsok, ie with GPL version 2 or later at the receivers choice? -- Happy hacking Petter Reinholdtsen
Bug#1056146: xsok possibly contains non-DFSG-free data files
[Doug Beeferman 2023-11-22] > Hello, > > I'm the author of Cyberbox and I grant permission for Cyberbox to be > redistributed without any restriction, including with modifications or in > derived works. Thank you for letting me know. Is it the correct understanding that Cuberbox is licensed with the same license as the rest of xsok, ie with GPL version 2 or later at the receivers choice? -- Happy hacking Petter Reinholdtsen
Bug#1056146: xsok possibly contains non-DFSG-free data files
[Doug Beeferman 2023-11-22] > Hello, > > I'm the author of Cyberbox and I grant permission for Cyberbox to be > redistributed without any restriction, including with modifications or in > derived works. Thank you for letting me know. Is it the correct understanding that Cuberbox is licensed with the same license as the rest of xsok, ie with GPL version 2 or later at the receivers choice? -- Happy hacking Petter Reinholdtsen
Bug#528875: please add info-dir-section to your info files
[Norbert Preining 2009-05-16] > Can you please add an info dir entry to the texinfo files of your package > to fix these warnings. The package is now orphaned. A patch to add such entry would be most welcome. :) -- Happy hacking Petter Reinholdtsen
Bug#528875: please add info-dir-section to your info files
[Norbert Preining 2009-05-16] > Can you please add an info dir entry to the texinfo files of your package > to fix these warnings. The package is now orphaned. A patch to add such entry would be most welcome. :) -- Happy hacking Petter Reinholdtsen
Bug#1069989: bmusb: Add Appstream metainfo announcing HW support
Package: bmusb Version: 0.7.7-1 Tags: patch Here is a patch for bmusb to add Appstream metainfo XML announcing the hardware handled by this package. I was a bit unsure if it should be attached to the library or -dev package, but concluded that the -dev package seem more useful for endusers than the library package on its own. Including this information in the package will ensure programs mapping hardware to packages using Appstream information, like the isenkram package, will know that this package is useful on machines where the USB IDs are discovered. diff --git a/bmusb.metainfo.xml b/bmusb.metainfo.xml new file mode 100644 index 000..341fd90 --- /dev/null +++ b/bmusb.metainfo.xml @@ -0,0 +1,21 @@ + + + no.gunderson.bmusb + MIT + bmusb + userspace driver for Blackmagic USB3 video capture cards + +bmusb is a userspace driver for Blackmagic's USB3 series of +video capture and playback cards (although only the capture part +is currently supported), in particular the Intensity Shuttle +(HDMI) and UltraStudio SDI cards. These are not currently served +by Blackmagic's own Linux drivers. + +bmusb is not API- or ABI-compatible with Blackmagic's +drivers. + + +usb:v1EDBpBD3Bd* +usb:v1EDBpBD4Fd* + + diff --git a/debian/libbmusb-dev.install b/debian/libbmusb-dev.install index b62ef39..a8fe4a0 100644 --- a/debian/libbmusb-dev.install +++ b/debian/libbmusb-dev.install @@ -2,3 +2,4 @@ usr/lib/*/*.so usr/lib/*/*.a usr/lib/*/pkgconfig/*.pc usr/include/bmusb/*.h +usr/share/metainfo/bmusb.metainfo.xml diff --git a/debian/libbmusb6.lintian-overrides b/debian/libbmusb6.lintian-overrides new file mode 100644 index 000..eab9833 --- /dev/null +++ b/debian/libbmusb6.lintian-overrides @@ -0,0 +1,2 @@ +# The metainfo XML is in the -dev package +libbmusb6: appstream-metadata-missing-modalias-provide usr/lib/udev/rules.d/70-bmusb.rules --- bmusb-0.7.7.orig/Makefile 2024-04-28 06:04:57.0 + +++ bmusb-0.7.7/Makefile2024-04-28 06:06:31.387282170 + @@ -9,6 +9,7 @@ PREFIX := /usr DEB_MULTIARCH_TRIPLET := $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) LIBDIR := $(PREFIX)/lib/$(DEB_MULTIARCH_TRIPLET) +METAINFODIR := $(PREFIX)/share/metainfo UDEVDIR ?= $(shell $(PKG_CONFIG) --variable udevdir udev) UDEVDIR ?= /lib/udev LIB := libbmusb.a @@ -44,6 +45,7 @@ $(DESTDIR)$(LIBDIR) \ $(DESTDIR)$(LIBDIR)/pkgconfig \ $(DESTDIR)$(PREFIX)/include/bmusb \ + $(DESTDIR)$(METAINFODIR) \ $(DESTDIR)$(UDEVDIR)/rules.d $(INSTALL) -m 755 $(LIB) $(SOLIB) $(DESTDIR)$(LIBDIR) $(LN) -sf $(SOLIB) $(DESTDIR)$(LIBDIR)/$(SONAME) @@ -52,5 +54,6 @@ sed 's/@DEB_MULTIARCH_TRIPLET@/$(DEB_MULTIARCH_TRIPLET)/' < bmusb.pc > $(DESTDIR)$(LIBDIR)/pkgconfig/bmusb.pc chmod 0644 $(DESTDIR)$(LIBDIR)/pkgconfig/bmusb.pc chown root:root $(DESTDIR)$(LIBDIR)/pkgconfig/bmusb.pc + $(INSTALL) -m 644 bmusb.metainfo.xml $(DESTDIR)$(METAINFODIR) $(INSTALL) -m 644 70-bmusb.rules $(DESTDIR)$(UDEVDIR)/rules.d -- Happy hacking Petter Reinholdtsen
Bug#1069971: git-buildpackage: import-dsc/import-dscs fail with TypeError: Parser must be a string or character stream, not NoneType
Package: git-buildpackage
Version: 0.9.30
When trying to bootstrap a git repository with the snapshotted uploads
of nitpick using 'gbp import-dscs', this fail with the following error:
File Imakefile is read-only; trying to patch anyway
File XPICsim is read-only; trying to patch anyway
File pu_defs.h is read-only; trying to patch anyway
File pu_lib.c is read-only; trying to patch anyway
Traceback (most recent call last):
File "/usr/bin/gbp", line 149, in
sys.exit(supercommand())
^^
File "/usr/bin/gbp", line 145, in supercommand
return module.main(args)
^
File "/usr/lib/python3/dist-packages/gbp/scripts/import_dscs.py", line 180,
in main
if importer.importdsc(dscs[0]):
^^^
File "/usr/lib/python3/dist-packages/gbp/scripts/import_dscs.py", line 72, in
importdsc
return import_dsc.main(['import-dsc'] + self.args + [dsc.dscfile])
^^^
File "/usr/lib/python3/dist-packages/gbp/scripts/import_dsc.py", line 531, in
main
apply_debian_patch(repo, sources[0], dsc, commit, options)
File "/usr/lib/python3/dist-packages/gbp/scripts/import_dsc.py", line 175, in
apply_debian_patch
author = get_author_from_changelog(source.unpacked)
^^
File "/usr/lib/python3/dist-packages/gbp/scripts/import_dsc.py", line 116, in
get_author_from_changelog
date = rfc822_date_to_git(dch.date, fuzzy=True)
File "/usr/lib/python3/dist-packages/gbp/git/__init__.py", line 44, in
rfc822_date_to_git
d = dateutil.parser.parse(rfc822_date, fuzzy=fuzzy)
^^^
File "/usr/lib/python3/dist-packages/dateutil/parser/_parser.py", line 1368,
in parse
return DEFAULTPARSER.parse(timestr, **kwargs)
^^
File "/usr/lib/python3/dist-packages/dateutil/parser/_parser.py", line 640,
in parse
res, skipped_tokens = self._parse(timestr, **kwargs)
^^
File "/usr/lib/python3/dist-packages/dateutil/parser/_parser.py", line 719,
in _parse
l = _timelex.split(timestr) # Splits the timestr into tokens
^^^
File "/usr/lib/python3/dist-packages/dateutil/parser/_parser.py", line 201,
in split
return list(cls(s))
^^
File "/usr/lib/python3/dist-packages/dateutil/parser/_parser.py", line 69, in
__init__
raise TypeError('Parser must be a string or character stream, not '
TypeError: Parser must be a string or character stream, not NoneType
A simple way to reproduce it is to download the nitpic_0.1-1.dsc source
package and try to import it into a fresh 'git init' directory like
this:
gbp import-dsc --pristine-tar ../nitpic_0.1-1.dsc
I suspect the problem is the d/changelog entry:
nitpic (0.1-1) unstable; urgency=low
* Initial release.
-- Fri, 7 Feb 1997 00:02:50 -0500
Perhaps it is unable to handle no name in front of the mail address?
--
Happy hacking
Petter Reinholdtsen
Bug#864522: bmusb: please add Vcs-* headers to debian/control
[Holger Levsen 2017-06-09] > please add the following headers to the source stanza in debian/control: I agree, it would be great with a pointer to the current git repository. Steinar, something you can have a look at? -- Happy hacking Petter Reinholdtsen
Bug#1031512: docbook-defguide: non-free GFDL-licensed files
[Bastian Germann 2023-02-17] > Some files in the package are licensed under the non-free variant of the GFDL > with explicit Invariant Section. > Please repack to remove them. I had a look to try to locate the files, but failed to find them. Which files did you have in mind? As the package is orphaned now, you can perhaps help out identifying them by creating a machine readable d/copyright file listing the problematic files? -- Happy hacking Petter Reinholdtsen >
Bug#1031512: docbook-defguide: non-free GFDL-licensed files
[Bastian Germann 2023-02-17] > Some files in the package are licensed under the non-free variant of the GFDL > with explicit Invariant Section. > Please repack to remove them. I had a look to try to locate the files, but failed to find them. Which files did you have in mind? As the package is orphaned now, you can perhaps help out identifying them by creating a machine readable d/copyright file listing the problematic files? -- Happy hacking Petter Reinholdtsen >
Bug#1031512: docbook-defguide: non-free GFDL-licensed files
[Bastian Germann 2023-02-17] > Some files in the package are licensed under the non-free variant of the GFDL > with explicit Invariant Section. > Please repack to remove them. I had a look to try to locate the files, but failed to find them. Which files did you have in mind? As the package is orphaned now, you can perhaps help out identifying them by creating a machine readable d/copyright file listing the problematic files? -- Happy hacking Petter Reinholdtsen >
Bug#810419: goldencheetah: please switch to libusb 1.0
An example demonstrating how such migration to libusb 1.0 can be done is found in https://sources.debian.org/src/t2n/0.7-1/debian/patches/1040-libusb1.patch/ >. -- Happy hacking Petter Reinholdtsen
Bug#810419: goldencheetah: please switch to libusb 1.0
An example demonstrating how such migration to libusb 1.0 can be done is found in https://sources.debian.org/src/t2n/0.7-1/debian/patches/1040-libusb1.patch/ >. -- Happy hacking Petter Reinholdtsen
Bug#901454: ctorrent: No bug being fixed, only new feature being proposed..
[Suchkov K.A. 2018-06-13] > upstream of the package is stalled, previous maintainer doesn't respond. Sad to hear. And now this package is orphaned in Debian. > It's implementation of ability Ctorrent client to work with a tracker through > a proxy-server. Packages successfully builded on amd64/i386 archs. I suspect it will be hard to find someone in Debian to take over the responsibility of a new feature not provided by upstream for an orphaned package, and suspect the only way to get this feature included is to find a working upstream project. I am only looking at this package to get its packaging setup migrated to git, and will leave any further development to others. -- Happy hacking Petter Reinholdtsen
Bug#901454: ctorrent: No bug being fixed, only new feature being proposed..
[Suchkov K.A. 2018-06-13] > upstream of the package is stalled, previous maintainer doesn't respond. Sad to hear. And now this package is orphaned in Debian. > It's implementation of ability Ctorrent client to work with a tracker through > a proxy-server. Packages successfully builded on amd64/i386 archs. I suspect it will be hard to find someone in Debian to take over the responsibility of a new feature not provided by upstream for an orphaned package, and suspect the only way to get this feature included is to find a working upstream project. I am only looking at this package to get its packaging setup migrated to git, and will leave any further development to others. -- Happy hacking Petter Reinholdtsen
Bug#456533: Egbbprobe in toga 2
[2007-12-16] > I have asked Daniel to clear the license questions that I have, see below. Was any conclusion reached regarding the licensing of this library? -- Happy hacking Petter Reinholdtsen
Bug#456533: Egbbprobe in toga 2
[2007-12-16] > I have asked Daniel to clear the license questions that I have, see below. Was any conclusion reached regarding the licensing of this library? -- Happy hacking Petter Reinholdtsen
Bug#464122: Forgot filename
[Bartek Kania 2008-02-05]
> Forgot to specify that the problem is in output.c
I suspect the patch you propose is this one:
diff --git a/output.c b/output.c
index dbd85be..b0ab93b 100644
--- a/output.c
+++ b/output.c
@@ -84,7 +84,7 @@ void output()
if (language == PERL) {
fprintf(code_file, "sub new {\n");
if (perl5005flag) {
- fprintf(code_file, " my %s $p = bless [\\%FIELDS], $_[0];\n",
+ fprintf(code_file, " my %s $p = bless [\\%%FIELDS], $_[0];\n",
perl_package);
}
else {
Unfortunately I do not have any way to test if it work or not. Do you
have some test files that can be used to demonstrate the problem?
--
Happy hacking
Petter Reinholdtsen
Bug#464122: Forgot filename
[Bartek Kania 2008-02-05]
> Forgot to specify that the problem is in output.c
I suspect the patch you propose is this one:
diff --git a/output.c b/output.c
index dbd85be..b0ab93b 100644
--- a/output.c
+++ b/output.c
@@ -84,7 +84,7 @@ void output()
if (language == PERL) {
fprintf(code_file, "sub new {\n");
if (perl5005flag) {
- fprintf(code_file, " my %s $p = bless [\\%FIELDS], $_[0];\n",
+ fprintf(code_file, " my %s $p = bless [\\%%FIELDS], $_[0];\n",
perl_package);
}
else {
Unfortunately I do not have any way to test if it work or not. Do you
have some test files that can be used to demonstrate the problem?
--
Happy hacking
Petter Reinholdtsen
Bug#716290: [Mayhem] Bug report on perl-byacc: pbyacc crashes with exit status 139
Control: tags -1 + patch
I believe the following patch fixes the problem, and it was just added
to the Debian package uploaded to the archive.
--- perl-byacc-2.0.orig/main.c
+++ perl-byacc-2.0/main.c
@@ -314,6 +314,12 @@ end_of_option:;
if (language != PERL && perl5005flag)
fprintf(stderr, "%s: Warning: -5 has no effect without Perl mode.\n",
myname);
+if (language == PERL && !perl_package)
+{
+fprintf(stderr, "%s: Perl mode require package name.\n",
+ myname);
+ exit(1);
+}
no_more_options:;
if (i + 1 != argc) usage();
Bug#716290: [Mayhem] Bug report on perl-byacc: pbyacc crashes with exit status 139
Control: tags -1 + patch
I believe the following patch fixes the problem, and it was just added
to the Debian package uploaded to the archive.
--- perl-byacc-2.0.orig/main.c
+++ perl-byacc-2.0/main.c
@@ -314,6 +314,12 @@ end_of_option:;
if (language != PERL && perl5005flag)
fprintf(stderr, "%s: Warning: -5 has no effect without Perl mode.\n",
myname);
+if (language == PERL && !perl_package)
+{
+fprintf(stderr, "%s: Perl mode require package name.\n",
+ myname);
+ exit(1);
+}
no_more_options:;
if (i + 1 != argc) usage();
Bug#1034483: dmidecode: CVE-2023-30630
Any hope to have this CVE issue fixed in stable and oldstable as well? If not, I suspect this BTS report should be closed. -- Happy hacking Petter Reinholdtsen
Bug#1069767: dmidecode: New upstream version 3.6 available
Package: dmidecode Version: 3.5 Severity: wishlist A new version was just released. Start of forwarded message Date: Wed, 24 Apr 2024 14:19:28 +0200 From: Jean Delvare To: dmidecode-de...@nongnu.org Subject: Dmidecode 3.6 has been released Hi all, Dmidecode 3.6 was released today. The changes from 3.5 are as follows: - [PORTABILITY] Use -DALIGNMENT_WORKAROUND on arm. - [PORTABILITY] Read SMBIOS entry point via kenv on DragonFly BSD. - Support for SMBIOS 3.6.0. This includes new memory device types, new processor upgrades, and Loongarch support. - Support for SMBIOS 3.7.0. This includes new port types, new processor upgrades, new slot characteristics and new fields for memory modules. - Add bash completion. - Decode HPE OEM records 197, 239 and 245. - Implement options --list-strings and --list-types. - Update HPE OEM records 203, 212, 216, 221, 233, 236, 237, 238 and 242. - Update Redfish support. - Bug fixes: Fix option --from-dump for user root Fix enabled slot characteristics not being printed - Minor improvements: Print slot width on its own line Use standard strings for slot width This new release is available for download from the usual place: http://download.savannah.gnu.org/releases/dmidecode/dmidecode-3.6.tar.xz http://download.savannah.gnu.org/releases/dmidecode/dmidecode-3.6.tar.xz.sig Please allow for up to 24 hours before the files propagate to all mirrors. -- Jean Delvare SUSE L3 Support End of forwarded message
Bug#264500: fmtools: fmscan patch to allow choice of threshold signal strength (attached)
Control: tags -1 + patch [Gregory P. Smith] 2004-08-08] > The fmscan utility is not nearly as useful as it could be without > this patch. this adds the -t command line option to allow control of > the threshold signal strength that fmscan uses to decide if a station > can be received. please apply to future debian packages of this tool > and submit to the upstream maintainer. Thank you for the patch. I am sad to see it has lingered here for so long. CC to the upstream email address, in the hope that upstream can have a look at the patch in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=264500 >. Not convinced that the old email address still work, but it is worth a try. :) -- Happy hacking Petter Reinholdtsen
Bug#264500: fmtools: fmscan patch to allow choice of threshold signal strength (attached)
Control: tags -1 + patch [Gregory P. Smith] 2004-08-08] > The fmscan utility is not nearly as useful as it could be without > this patch. this adds the -t command line option to allow control of > the threshold signal strength that fmscan uses to decide if a station > can be received. please apply to future debian packages of this tool > and submit to the upstream maintainer. Thank you for the patch. I am sad to see it has lingered here for so long. CC to the upstream email address, in the hope that upstream can have a look at the patch in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=264500 >. Not convinced that the old email address still work, but it is worth a try. :) -- Happy hacking Petter Reinholdtsen
Bug#1069633: Time to remove yasm from Debian?
Package: yasm Version: 1.3.0-4 In https://github.com/yasm/yasm/issues/164 >, the upstream developer of yasm states "I'm still alive, but have moved on to other projects. If someone else wants to take on maintainership, I'd be happy to give them the access to this repo do so (presumably with some kind of transitional period where I would review/approve PRs).". The many open security issues listed on https://security-tracker.debian.org/tracker/source-package/yasm > are all unsolved, and bsed on the statement above and the time duration since it was expressed it seem unlikely that this will change any time soon. Perhaps it is time to remove yasm from Debian and move all reverse build dependencies to use a different assembler? -- Happy hacking Petter Reinholdtsen
Bug#1069633: Time to remove yasm from Debian?
Package: yasm Version: 1.3.0-4 In https://github.com/yasm/yasm/issues/164 >, the upstream developer of yasm states "I'm still alive, but have moved on to other projects. If someone else wants to take on maintainership, I'd be happy to give them the access to this repo do so (presumably with some kind of transitional period where I would review/approve PRs).". The many open security issues listed on https://security-tracker.debian.org/tracker/source-package/yasm > are all unsolved, and bsed on the statement above and the time duration since it was expressed it seem unlikely that this will change any time soon. Perhaps it is time to remove yasm from Debian and move all reverse build dependencies to use a different assembler? -- Happy hacking Petter Reinholdtsen
Bug#767532: shutdown-at-night: Allow systemd to wake up machines in the morning?
I had a closer look, and start to suspect that the rtcwake command is
operating on the same setting as the acpiwakeup() method in the
shutdown-at-night shell script:
# This method might not work if the hardware clock is updated during
# shutdown. Changing /etc/default/hwclock to list HWCLOCKACCESS=yes
# to disable it.
# Based on http://www.mythtv.org/wiki/ACPI_Wakeup >
acpiwakeup() {
wakeuptime="$1"
if [ -e /sys/class/rtc/rtc0/wakealarm ] ; then
when=$(whentowakeup $wakeuptime)
# First reset alarm
echo 0 > /sys/class/rtc/rtc0/wakealarm
# Next, set it to our selected time
echo $when > /sys/class/rtc/rtc0/wakealarm
logger -t shutdown-at-night "scheduled $hostname to turn itself on at
$wakeuptime using /sys/class/rtc/rtc0/wakealarm."
return 0
else
return 1
fi
}
If this is correct, using rtcwake might make this code simpler, but not
add a new way to get the machine to wake up in the morning, which was my
original motivation for creating this issue.
--
Happy hacking
Petter Reinholdtsen
Bug#963921: O: inputlirc -- Zeroconf LIRC daemon using input event devices
[Guus Sliepen] > Ouch that copyright file is old... Use this one: > > https://git.sliepen.org/inputlirc > > Or these mirrors: > > https://github.com/gsliepen/inputlirc > https://gitlab.com/gsliepen/inputlirc Thank you. I've updated https://salsa.debian.org/debian/inputlirc >. -- Happy hacking Petter Reinholdtsen
Bug#963921: O: inputlirc -- Zeroconf LIRC daemon using input event devices
[Guus Sliepen] > Ouch that copyright file is old... Use this one: > > https://git.sliepen.org/inputlirc > > Or these mirrors: > > https://github.com/gsliepen/inputlirc > https://gitlab.com/gsliepen/inputlirc Thank you. I've updated https://salsa.debian.org/debian/inputlirc >. -- Happy hacking Petter Reinholdtsen
Bug#963921: O: inputlirc -- Zeroconf LIRC daemon using input event devices
[Guus Sliepen 2020-06-28] > I'm also the upstream maintainer of this package, if you are interested > in maintaining it you are welcome to take over upstream maintainership > as well. Is there a upstream home page for this project? The one listed in d/copyright did not work (http://svn.sliepen.eu.org/inputlirc/ >). -- Happy hacking Petter Reinholdtsen
Bug#963921: O: inputlirc -- Zeroconf LIRC daemon using input event devices
[Guus Sliepen 2020-06-28] > I'm also the upstream maintainer of this package, if you are interested > in maintaining it you are welcome to take over upstream maintainership > as well. Is there a upstream home page for this project? The one listed in d/copyright did not work (http://svn.sliepen.eu.org/inputlirc/ >). -- Happy hacking Petter Reinholdtsen
Bug#1069116: O: dfc -- display file system usage using graph and colors
Package: wnpp Severity: normal The current maintainer of dfce, Sabino Par , has orphaned this package. Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see http://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Package: dfc Version: 3.1.1-1.2 Priority: optional Section: utils Maintainer: Sabino Par Installed-Size: 130 kB Depends: libc6 (>= 2.34) Homepage: https://github.com/rolinh/dfc Description: display file system usage using graph and colors dfc displays file system space usage using graphs and colors. In some ways, it is a modernized version of df as it is able to use colors, draw graphs and export its output to different formats such as CSV or HTML. -- Happy hacking Petter Reinholdtsen
Bug#1069116: O: dfc -- display file system usage using graph and colors
Package: wnpp Severity: normal The current maintainer of dfce, Sabino Par , has orphaned this package. Maintaining a package requires time and skills. Please only adopt this package if you will have enough time and attention to work on it. If you want to be the new maintainer, please see http://www.debian.org/devel/wnpp/index.html#howto-o for detailed instructions how to adopt a package properly. Some information about this package: Package: dfc Version: 3.1.1-1.2 Priority: optional Section: utils Maintainer: Sabino Par Installed-Size: 130 kB Depends: libc6 (>= 2.34) Homepage: https://github.com/rolinh/dfc Description: display file system usage using graph and colors dfc displays file system space usage using graphs and colors. In some ways, it is a modernized version of df as it is able to use colors, draw graphs and export its output to different formats such as CSV or HTML. -- Happy hacking Petter Reinholdtsen
Bug#1069081: isenkram-cli: usb.py: SyntaxWarning: invalid escape sequence '\s'
[Paul Wise]
>Setting up isenkram-cli (0.56) ...
>/usr/lib/python3/dist-packages/isenkram/usb.py:43: SyntaxWarning: invalid
> escape sequence '\s'
> m = re.match('^([0-9a-f]{4})\s+(\S.*)$', line)
>/usr/lib/python3/dist-packages/isenkram/usb.py:48: SyntaxWarning: invalid
> escape sequence '\s'
> m = re.match('^\t([0-9a-f]{4})\s+(\S.*)$', line)
This is rather strange, as \s is described in
https://docs.python.org/3/library/re.html >:
\s
For Unicode (str) patterns:
Matches Unicode whitespace characters (which includes
[ \t\n\r\f\v], and also many other characters, for example the
non-breaking spaces mandated by typography rules in many
languages).
Matches [ \t\n\r\f\v] if the ASCII flag is used.
For 8-bit (bytes) patterns:
Matches characters considered whitespace in the ASCII character
set; this is equivalent to [ \t\n\r\f\v].
Matches any character which is not a whitespace character. This is
the opposite of \s.
Matches [^ \t\n\r\f\v] if the ASCII flag is used.
Any idea what happend with \s in python 3.12? Perhaps the problem is
a missing 'r' in front of the quotes?
--
Happy hacking
Petter Reinholdtsen
Bug#575781: Please resolve IPv6 gateway too
Control: tags -1 - patch [Philipp Kern 2013-05-04] > Scrap that. We want to implement gethostbyname4, which is what nss-myhostname > does. This returns gaih_addrtuple instead of hostents, which are able to > bear scope IDs. OK. Assume a different patch is needed and remove the patch tag. -- Happy hacking Petter Reinholdtsen
Bug#575781: Please resolve IPv6 gateway too
Control: tags -1 - patch [Philipp Kern 2013-05-04] > Scrap that. We want to implement gethostbyname4, which is what nss-myhostname > does. This returns gaih_addrtuple instead of hostents, which are able to > bear scope IDs. OK. Assume a different patch is needed and remove the patch tag. -- Happy hacking Petter Reinholdtsen
Bug#762336: Please enable hardened build flags
Since the original report and patch, the package have been orphaned, and the rules file changed in a way that make the tested patch no longer apply. I suspect something like the following untested patch might work. diff --git a/debian/rules b/debian/rules index 16aad6f..f55fc4c 100755 --- a/debian/rules +++ b/debian/rules @@ -6,6 +6,9 @@ # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 +DPKG_EXPORT_BUILDFLAGS = 1 +include /usr/share/dpkg/buildflags.mk + configureoptions = --bindir=/usr/sbin/ --sysconfdir=/etc/bandwidthd/ --localstatedir=/var/lib/ p_bwdstatic = bandwidthd @@ -26,7 +29,7 @@ configure-bwdstatic-stamp: cp -f /usr/share/misc/config.sub config.sub dh_autoreconf chmod +x configure - INSTALL='install --strip-program=true' dh_auto_configure -- $(configureoptions) --disable-pgsql + $(shell dpkg-buildflags --export=cmdline) INSTALL='install --strip-program=true' dh_auto_configure -- $(configureoptions) --disable-pgsql touch $@ configure-bwdpgsql: configure-bwdpgsql-stamp I do not dare to apply it without testing. -- Happy hacking Petter Reinholdtsen
Bug#762336: Please enable hardened build flags
Since the original report and patch, the package have been orphaned, and the rules file changed in a way that make the tested patch no longer apply. I suspect something like the following untested patch might work. diff --git a/debian/rules b/debian/rules index 16aad6f..f55fc4c 100755 --- a/debian/rules +++ b/debian/rules @@ -6,6 +6,9 @@ # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 +DPKG_EXPORT_BUILDFLAGS = 1 +include /usr/share/dpkg/buildflags.mk + configureoptions = --bindir=/usr/sbin/ --sysconfdir=/etc/bandwidthd/ --localstatedir=/var/lib/ p_bwdstatic = bandwidthd @@ -26,7 +29,7 @@ configure-bwdstatic-stamp: cp -f /usr/share/misc/config.sub config.sub dh_autoreconf chmod +x configure - INSTALL='install --strip-program=true' dh_auto_configure -- $(configureoptions) --disable-pgsql + $(shell dpkg-buildflags --export=cmdline) INSTALL='install --strip-program=true' dh_auto_configure -- $(configureoptions) --disable-pgsql touch $@ configure-bwdpgsql: configure-bwdpgsql-stamp I do not dare to apply it without testing. -- Happy hacking Petter Reinholdtsen
Bug#804722: git-buildpackage: import-dsc creates impractical merge commits after new upstream releases
Dear package maintainer of git-buildpackage, Do you have an idea when you will find time to look at this patch? [Gioele Barabucci 2024-08-19] > The attached new patch, although still "quick and dirty", improves the > handing of possible modification+deletion conflicts that may arise while > merging the the upstream branch into the Debian branch. -- Happy hacking Petter Reinholdtsen
Bug#980839: rnnoise model training data
According to https://github.com/xiph/rnnoise/releases/tag/v0.2 >, the new version just released was been trained on only publicly available data. Time to see if rnnoise can go into Debian? -- Happy hacking Petter Reinholdtsen
Bug#980839: rnnoise model training data
According to https://github.com/xiph/rnnoise/releases/tag/v0.2 >, the new version just released was been trained on only publicly available data. Time to see if rnnoise can go into Debian? -- Happy hacking Petter Reinholdtsen
Bug#981276: pexec FTCBFS: help2man
[Helmut Grohne 2021-01-28] > pexec fails to cross build from source, because it uses help2man. Given > that pexec has very little dependencies, we can add a native build pass > for generating the manual page before performing the cross build. Please > consider applying the attached patch. I suspect a better fix is to convert the package to use 'dh' first. I tried the trivial conversion but it did not work because the configure script do not understand --runstatedir=/run. I just converted the packaging to git and made it available in https://salsa.debian.org/debian/pexec > if you want to update the package yourself. -- Happy hacking Petter Reinholdtsen
Bug#981276: pexec FTCBFS: help2man
[Helmut Grohne 2021-01-28] > pexec fails to cross build from source, because it uses help2man. Given > that pexec has very little dependencies, we can add a native build pass > for generating the manual page before performing the cross build. Please > consider applying the attached patch. I suspect a better fix is to convert the package to use 'dh' first. I tried the trivial conversion but it did not work because the configure script do not understand --runstatedir=/run. I just converted the packaging to git and made it available in https://salsa.debian.org/debian/pexec > if you want to update the package yourself. -- Happy hacking Petter Reinholdtsen
Bug#1058552: marked as pending in science.js
Control: tag -1 pending Hello, Bug #1058552 in science.js reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/js-team/science.js/-/commit/72d4064d48ae6a0f2c0886ea43cf99b1b2ac5754 Fixed build race condition problem. Patch from James Valleroy. Closes: #1058552 (this message was generated automatically) -- Greetings https://bugs.debian.org/1058552
Bug#810448: nbc: please switch to libusb 1.0
I do not know how to convert the package to use a newer libusb, but just wanted to mention that a patch to convert t2n to use a newer libusb is available in https://bugs.debian.org/810460 >. -- Happy hacking Petter Reinholdtsen
Bug#755437: leocad suggests ldraw-parts since 0.80.3-1
I believe the requestor never received this email, and as @gmail.com reject emails from me, I doubt he will get my email too. [Nicolas Guilbert 2015-02-12] > the leocad package suggests ldraw-parts since 0.80.3-1 which should fix the > issue about the minimal parts set (apt-get install leocad > --install-suggests). > > Concerning the parts not being visible, I cannot reproduce that error. Is it > still a problem? Without more information, I suspect it is not possible to get further with this issue. Perhaps it can be closed? -- Happy hacking Petter Reinholdtsen
Bug#1068710: tiktoken: pybuild-autopkgtest fails with ModuleNotFoundError(s)
Control: reopen -1
[Nick Rosbrook]
> In Ubuntu, I noticed that the autopkgtests were failing for tiktoken[1].
> The failure is due to missing 'pytest' and 'hypothesis' python modules.
> Looking at [2], I see the same failures in Debian. I applied this
> patch in Ubuntu to fix the autopkgtest:
>
> * debian/control: Build-Depends: python3-{pytest,hypothesis}
Are you sure this patch worked in Ubuntu? As far as I can tell, the
autopkgtest script still fail on Debian.
--
Happy hacking
Petter Reinholdtsen
Bug#1068575: nuttcp: Add homepage link to d/control
Package: nuttcp Version: 6.1.2-4 Severity: wishlist Please add a Homepage entry in debian/control for nuttcp. The home page seem to be https://www.nuttcp.org/ >. -- Happy hacking Petter Reinholdtsen
Bug#963524: fixed in debian-policy 4.7.0.0
For the record, and as stated in https://bugs.debian.org/999598 >, I would rather have the description lines back in the changes file to provide the information in the emails presenting uploads, instead of dropping them. I guess this bug report will be closed unsolved instead. -- Happy hacking Petter Reinholdtsen
Bug#963524: fixed in debian-policy 4.7.0.0
For the record, and as stated in https://bugs.debian.org/999598 >, I would rather have the description lines back in the changes file to provide the information in the emails presenting uploads, instead of dropping them. I guess this bug report will be closed unsolved instead. -- Happy hacking Petter Reinholdtsen
Bug#1037114: python3-opensnitch-ui: Desktop notifications should expire
I forgot to mention that the issue is closed upstream. -- Happy hacking Petter Reinholdtsen
Bug#1037114: python3-opensnitch-ui: Desktop notifications should expire
Control: forwarded -1 https://github.com/evilsocket/opensnitch/issues/673 [Gustavo Iñiguez Goya] > This issue was reported here: > https://github.com/evilsocket/opensnitch/issues/673 > > I didn't find a proper way of solving it. Thanks for leting me know. -- Happy hacking Petter Reinholdtsen
Bug#1037282: opensnitch-ebpf-modules: causes opensnitch daemon to crash (SIGSEGV)
[Paul Wise 2024-06-10] > When starting the opensnitch service while opensnitch-ebpf-modules is > installed, the opensnitch daemon crashes with the SIGSEGV error below. I tested a built of new upstream version 1.6.5.1 using the build rules in experimental and a few new build dependencies (golang-github-google-uuid-dev, golang-github-varlink-go-dev, linux-headers-amd64), and with this version there is no segfault in the daemon. I thus suspect this issue can be fixed by updating to the latest upstream version, ref https://bugs.debian.org/1051317 >. -- Happy hacking Petter Reinholdtsen
Re: [Emc-developers] LinuxCNC gathering in Norway - July 5th-7th 2024
[Asle Næss] > As last year Petter and I would like to invite you all to small > LinuxCNC workshop/gathering in Norway this summer for the weekend > starting July 5th 2024. Here is a poster you can put up in areas where potential participants linger. Please visit https://pad.efn.no/p/linuxcnc-2024-norway> and leave your name and email address to join us. Note, formally it is the NUUG Foundation, https://www.nuugfoundation.no/ >, handling the money, not its sister organization NUUG, on recommendation from their accountant. -- Happy hacking Petter Reinholdtsen 2024-linuxcnc-samling.pdf Description: Adobe PDF document 2024-linuxcnc-samling.odt Description: application/vnd.oasis.opendocument.text ___ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
Bug#1066964: ITA: newlib -- C library and math library for embedded systems
[Matthias Klose] >>Do you want to take over my plan to fix the security problem in stable >>as described in https://bugs.debian.org/1066965 >? > > not at all, please go ahead with it. OK. Still waiting for response from the release managers if they want this update or not. No idea when there is movement. Do you plan to update https://salsa.debian.org/debian/newlib.git > with your latest upload? -- Happy hacking Petter Reinholdtsen
Bug#1066964: ITA: newlib -- C library and math library for embedded systems
[Matthias Klose] >>Do you want to take over my plan to fix the security problem in stable >>as described in https://bugs.debian.org/1066965 >? > > not at all, please go ahead with it. OK. Still waiting for response from the release managers if they want this update or not. No idea when there is movement. Do you plan to update https://salsa.debian.org/debian/newlib.git > with your latest upload? -- Happy hacking Petter Reinholdtsen
Bug#1066965: bookworm-pu: package newlib/3.3.0-2
Btw, what is the timeline for approval or rejection for this security upload proposal? -- Happy hacking Petter Reinholdtsen
Bug#1066965: bookworm-pu: package newlib/3.3.0-2
Btw, what is the timeline for approval or rejection for this security upload proposal? -- Happy hacking Petter Reinholdtsen
Bug#1066964: ITA: newlib -- C library and math library for embedded systems
[Petter Reinholdtsen] > I believe I found the correct location in > https://salsa.debian.org/debian/newlib/edit>, where a new path for > the project can be specified. I did not test it yet. Do you want to > move it, or should I give it a try? Another and slightly related question, as I suspect moving the git repo will remove my write access to it. Do you want to take over my plan to fix the security problem in stable as described in https://bugs.debian.org/1066965 >? -- Happy hacking Petter Reinholdtsen
